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

5.2.6.2.1 Upon receipt of a packet from the peer XDCE,
the packet shall be forwarded or not forwarded to the DCE
(via the reformalting process) according to he parenthetical
instructions contained in Tables 5-15 to 5-19. If no parenthetical
instruction is listed or if the parenthetical instruction
indicates "do not forward" the packet shall be discarded.
5.2.6.2.2 Upon receipt of a packet from the DCE (via
REQUEST to DTE state, p7).
5.2.6.3.3.2 If the XDCE receives a Mode S CALL
ICEQUEST packet from the peer XDCE (via frame processing)
which it cannot support, it shall enter the state p7.
5.2.6.3.3.3 A means shall be provided to advise the DTE
whether an SVC has been cleared due to the action of the peer
DTE or due to a problem within the subnetwork itself.
5.2.6.3.3.4 Recommendation.- The requirement of
5.2.6.3.3.3 should he satisfied by setting bir 8 of the cause
Feld to I to indicate that the problem originated in the
Mode S subnetwork and not in the DTE. The diagnostic and
cause codes should be set as follows:
a) no channel number available, DC = 71, CC = 133;
b) buffer space not available, DC = 71, CC = 133;
c) DTE not operational, DC = 162, CC = 141; and
d) link failure, DC = 225, CC = 137.
the reformatting process), the shall be forwarded or not 5.2.6.3.3.5 If the ADLP receives a Mode S ROUTE
forwarded to the peer XDCE according to the parenthetical packet with the IN bit set to ONE, the ADLP shall perform
5/11/98
No. 73
Annex 20 - Aeronautical Telecommunications Volume III
local inicializacion by clearing Mode S SVCs associated with
the DTE addresses contained in the ROUTE packet. If thc
GDLP receives a search request (Table 5-23) from an ADLP,
the GDLP shall perform local initialization by clcaring
Mode S SVCs associated with that ADLP. Local initialization
shall be accomplished by:
a) releasing all allocated resources associated with these
SVCs (including the resequencing buffers);
b) returning these SVCs to the ADCE ready state @I);
and
c) sending Mode S CLEAR REQUEST packets for these
SVCs to the DCE (via the reformatting process) for
transfer to the DTE.
Note.- This action will allow all IS0 8208 SVCs attached
to the Mode S SVCs to be cleared and return to their ready
states (PI).
5.2.6.3.4 Clear conjrmation. When the XDCE receives
a Mode S CLEAR CONFIRMATION packet, the remaining
allocated resources to manage the SVC shall be released
(including the resequencing buffers) and the SVC shall be
returned to che pl state. Mode S CLEAR CONFlRMATION
packets shall not be transferred to the reformatting process.
5.2.6.3.5 Clear collision. 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 trcat an Sbit
sequence of Mode S CALL REQUEST, CALL ACCEPT
and CLEAR REQUEST packets as a single entity.
5.2.6.4 DATA TRANSFER AND INTERRUPT PROCEDURES
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 assigned to the data packets.
5.2.6.4.1.2 To transfer packets, the SVC shall be in a
FLOW CONTROL READY state (dl).
5.2.6.4.2.1 The maximum size of Mode S packets shall
be 152 bytes in the uplink direction and 160 bytes in the
downlink direction for installations that have full uplink and
downlink ELM capability. The maximum downlink packet size
for level four transponders with less than 16 segment downlink
ELM capability shall be 10 bytes times the maxilnum number
of downlink ELM segments that the transponder specifies in
its data link capability report. If there is no ELM capability,
the maximum Mode S packcl size shall be 28 bytes.
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 SlZE
5.2.6.4.3.1 The flow control window size of the Mode S
subnetwork shall be independent of that used on the DTE/DCE
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
　
中國(guó)航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：附件10--航空電信an10_v3_1ed_amend_73(23)