曝光臺 注意防騙 網(wǎng)曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費(fèi)者

Mode S CALL REQUEST from the peer XDCE (via frame
processing), the Mode S CALL REQUEST shall be sent to the
reformatting process.
5.2.6.3.2 Aborting a call request. If the DTE andor the
peer XDCE abort a call before they have received a CALL
ACCEPT packet, they shall indicate this condition by issuing
5.2.6.3.3.1 If the XDCE receives a Mode S. CALL
REQUEST from the reformatting process that it cannot
support, it shall initiate a Mode S CLEAR REQUEST packet
that is sent to the DCE (via the reformatting process) for
transfer to the DTE (the DCE thus enters the DCE CLEAR
REQUEST to DTE state, p7). The diagnostic and cause codes
shall be set as follows:
a) no channel number available, DC = 71, CC = 133;
b) buffer space nor available, DC = 7 1, CC = 133; and
c) DTE not operational, DC = 162, CC = 141.
In all cases, bit 8 of the cause field shall be set to 1 to indicate
that the problem originated in the Mode S subnetwork and not
the DIE.
5.2.6.3.3.2 IF the XDCE receives a Mode S CALL
REQUEST packet from the peer XDCE (via frame processing)
which it cannot support, it shall enter the state p7. The cause
field shall be as specified above.
5.2.6.3.4 Clear confirmation. When the XDCE receives
a Mode S CLEAR CONmRMATION packet, the remaining
allocated resources to manage the SVC shall be released and
the SVC shall be returned to the pl state. Mode S CLEAR
CONFIRMATION packets shall not be transferred to the
reformatting process.
5.2.6.3.5 Clear coIIision. A clear collision occurs at the
XDCE when it receives a Mode S CLEAR REQUEST packet
from the DCE (via the reformatting process) and then receives
a Mode S CLEAR REQUEST packet from the peer XDCE (or
vice versa). In this event, the XDCE does not expect to
receive a Mode S CLEAR CONFIRMATION packet for this
SVC and shall consider the clearing complete.
5.2.6.3.6 Packetprocessing. The XDCE shall treat an Sbit
sequence of Mode S CALL REQUEST, CALL ACCER
and CLEAR REQUEST packets as a single entity.
5.2.6.4 DATA TRGNSFER AND INTERRUPT PROCEDURES
5.2.6.4.1 GENERALPR OVISIONS
5.2.6.4.1.1 Data transfer and interrupt procedures shall
apply independently to each SVC. The contents of the user
data field shall be passed transparently to the DCE or to the
peer XDCE. Data shall be transferred in the order dictated by
the sequence numbers assigncd to the data packets.
7/11/96
No. 71
Annex 10 - Aeronautical Telecommunications Volume IIZ
5.2.6.4.1.2 To transfer packets, the SVC shall be in a 5.2.6.4.4.4 When the sequence number (PS) of the next
FLOW CONTROL READY state (dl). Mode S DATA packet to be sent is in the range
PR 2 PS < PR + 14 (modulo 16), the sequence number shall
be defined to be "in the window" and the XDCE shall be
5.2.6.4.2 MODE 3 PACKET SIZE aathorized to transmit the packet. Otherwise, the sequence
number (PS) of the packet shall be defined to be "outside the
5.2.6.4.2.1 The maximum size of Mode S packets shall and the XDCE not transmit the packet to the
be 152 bytes in the uplink direction and 160 bytes in the peer XDCE.
downlink direction for installations that have full. uplink and
downlink ELM capability. The maximum downlink Gcket size 5.2.6.4.4.5 When the sequence number (PS) of the
for level four transponders with less than 16 segment downlink packet received is next in sequence and within the window,
ELM capability shall be 10 bytes times the maximum number the ~ CshaEll ac cept this packet, Receipt of a packet with
of downlink ELM segments that the transponder specifies in a PS:
its data link capability report. If there is no ELM capability,
the maximum Mode S packet size shall be 28 bytes. a) outside the window; or
5.2.6.4.2.2 The Mode S subnetwork shall allow packets
of less than the maximum size to be transferred.
5.2.6.4.3 FLOW CONTROL WINDOW SIZE
5.2.6.4.3.1 The flow control window size of the Mode
S subnetwork shall be independent of that used on the
DTTEfl3CE interface. The Mode S subnetwork window size
shall be 15 packets in the uplink and downlink directions.
5.2.6.4.4 svc FLOW CONTROL
5.2.6.4.4.1 Flow control shall be managed by means of
a sequence number for received packets (PR) and one for
packets that have been sent (PS). A sequence number (PS)
shall be assigned for each Mode S DATA packet generated by
the XDLP for each SVC. The first Mode S DATA packet
transferred by the XDCE to frame processing when the SVC
has just entered the flow control ready state shall be numbered
zero. The first Mode S packet received from the peer XDCE
after an SVC has just entered the flow control ready state shall
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：附件10--航空電信an10_v3_1ed_amend_71(27)