曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
Note.- Transponders will not output all-call and ACAS
information on this interface.
5.2.3.3.1.2 The ADLP shall accept control information
from the transponder indicating the status of downlink transfers.
This shall include:
a) Comm-B close-out;
b) Comm-B broadcast time-out; and
c) downlink ELM close-out.
5.2.3.3.1 -3 The ADLP shall have access to information
defining the communication capability of the Mode S transponder
with which it is operating. This information shall be
used to generate the data link capability report (5.2.9).
5.2.3.3.2 A D P TO TRANSPONDER
5.2.3.3.2.1 , The ADLP shall provide an indication of
protocol type to the transponder in connection with data transferred
from the ADLP to the transponder. This shall include
the following types of protocols:
a) ground-initiated Comm-B:
5.2.3.4.1.1 The GDLP shall accept an indication of
protocol type frorn the interrogator in connection with data
transferred frorn the interrogator to the GDLP. This shall
include the following types of protocols:
a) ground-initiated Comm-B;
b) air-initiated Comm-B;
c) air-initiated Comm-B broadcast: and
d) downlink ELM.
The GDLP shall also accept the BDS code used to identify the
ground-initiated Comm-B segment.
5.2.3.4.1.2 The GDLP shall accept control information
from the interrogator indicating the status of uplink transfers
and the status of the addressed Mode S aircraft.
5.2.3.4.2 GDLP to interrogatot; The GDLP shall provide
an indication of protocol type to the interrogator in
connection with data transferred from the GDLP to the
interrogator. This shall include the following types of
protocols:
a) Comm-A interrogation;
b) Comm-A broadcast interrogation;
c) uplink ELM; and
d) ground-initiated Comrn-B request.
The GDLP shall also provide the BDS code for the groundinitiated
Comrn-I3 protocol.
b) air-initiated Comm-B;
5.2.4 DCE operation
c) multisite-directed Comm-B;
d) Comm-B broadcast;
e) downlink ELM; and
f) multisite-directed downlink ELM.
Note.- The DCE process within the XDLP acts as a peer
process ro the DTE. The DCE supports the operations of the
DTE with the capability specified in 5.2.3.1.4. The following
requirements do not specfi f o m t definitions andflow control
on the DTWDCE intevace. The specifications and definitions
in IS0 8208 apply for these cases.
5/11/98
No. 73
Part I Annex 10 - Aeronautical Telecommunications
5.2.4.1 State transitions. The DCE shall operate as a
state machine. Upon entering a state, the DCE shall pcrform
the actions specified in Table 5-2. State transitions and
additional action(s) shall be as specified in Table 5-3 through
Table 5- 12.
Note.- The next state transition (ifany) that occurs when
the DCE receives a packet from the DTE is spec$ed by
Table 5-3 through Table 5-8. These tables are organized
according to the hierarchy illustrated in Figure 5-2. The same
transitions are defined in Table 5-9 through Table 5-12 when
the DCE receives a packet from the XDCE (via the
reformatting process).
5.2.4.2.1 Upon receipt of a packet from the DTE, the
packet shall be forwarded or not forwarded to the XDCE (via
the reformatting process) according to the parenthelical instructions
contained in Tables 5-3 to 5-8. If no parenthetical
instruction is listed or if the parenthetical instruction indicates
"do not forward, the packet shall be discarded.
5.2.4.2.2 Upon receipt of a packet from the XDCE (via
the reformatting process), the packet shall be forwarded or not
forwarded to the DTE according to the parenthetical instructions
contained in Tables 5-9 to 5-12. If no parenthetical
instruction is listed or if the parenthetical instruction indicates
"do not forward, the packet shall be discarded.
c) maintain sufficient buffer space for two Mode S
subnetwork INTERRUPT packets of 35 bytes each,
(user data field plus control information), one in each
direction, for each SVC;
d) maintain sufficient resequencing buffer space for
storing thirty-one Mode S subnetwork packets of 152
bytes each in the uplink direction per SVC for a
transponder with uplink ELM capability or 28 bytes
otherwisc; and
e) maintain sufficient buffer space for the temporary
storage of at least one Mode S packet of 160 bytes
undergoing M-bit or S-bit processing in each direction
per SVC.
5.2.5.1.1.1.3 The ADLP shall be capable of maintaining
a buffer of 1 600 bytes in each direction to be shared among
all MSPs.
5.2.5.1.1.2 CDEP buffer requirements
5.2.5.1 .1.2.1 Recornmendation.- The GDLP should be
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_73(13)
