曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

5.2.6.3.
5.2.5.3.4.2 Data packet type (DP). This field shall be set
to 0.
5.2.5.3.4.3 MSPpacket type (MP). This field shall be set
to 1.
Fields shown in the packet format. and not specified in the
following paragraphs shall bc set as specified in 5.2.5.2.1 and
5.2.5.2.6. This packet shall be processed as specified in
5.2.6.3.
5.2.5.3.5.2 Data pucket type (DP). This field shall be set
to 0.
5.2.5.3.5,3 MSPpacket type (MP). This field shall be set
to 1.
5.2.5.3.5.4 Supervisory packet (SP). This field shall be
set to 1.
5.2.5.3.5.5 Supervisory type (ST). This field shall be set
to 3.
5.2.5.3.6 MODE S RESET CONFIRMATION
5.2.5.3.6.1 Packet format. The format for this packet
shall be a follows:
Fields shown in the packet format and not specified in the
following paragraphs shall be set as specified in 5.2.5.2.1. This
packet shall be processed as specified in Table 5-14.
5.2-5.3.6.2 Data packet type (DP). This field shall be set
to 0.
5.2.5.3-6.3 MSPpacket type (Mu. This field shall be set
to 1.
5.2.5.3.6.4 Supervisory packet (SP). This field shall be
set to 2.
5.2.5.3.6.5 Supervisory type (ST). This field shall be set
to 3.
5.2.5.3.4.4 Supervisory packet (SP). This field shall be
set to 1.
5.2.5.3.7 MoqE S REJECT
5.2.5.3.4.5 Supervisory type (ST). This field shall be set
to 3.
5.2.5.3.5 MODE S CLEAR CONFIRMATION BY GDLP
5.2.5.3,7.1 Packet format. The format for this packet
shall be as follows:
511 1/98
No. 73
D P l
5.2.5.3.5.1 Packet format. The format for this packet
MP:1 SP:2
shall be as follows:
FILL2:O or 2
ST:2 SS:2
SN:6 CH:4 PR:4
Part I Annex 10 - Aeronautical Telecommunications
Fields shown in the packet format and not specified in the instructions contained in Tables 5-20 to 5-22. If no parenfollowing
paragraphs shall be set as specified in 5.2.5.2.1. This thetical instruction is listed or if the parenthetical instruction
packet shall be processed as specified in 5.2.6.8. indicates "do not forward" the packet shall be discarded.
5.2.5.3.7.2 Data packet type (DP). This field shall be set
to 0.
5.2.5.3.7.3 MSPpacket tyye (MP). This field shall be set
to 1.
5.2.5.3.7.4 Supervisory packet (SP). This field shall be
set to 3.
5.2.5.3.7.5 Supervisory type (ST). This field shall be set
to 3.
5.2.5.3.7.6 Supervisory subset (SS). This field shall be
set to 1.
5.2.5.3.7.7 Packet receive sequence number (PR). This
field shall be set as specified in 5.2.6.4.4.
5.2.6 XDCE operation
5.2.6.3 SVC CALL SETUP AND
CLEAR PROCEDURE
5.2.6.3.1 Setup procedures. Upon receipt of a CALL
REQUEST from the DCE or peer XDCE, the XDLP shall
determine if sufficient resources exist to operate the SVC. This
shall include: sufficient buffer space (refer to 5.2.5.1.1 for
buffer requirements) and an available pl state SVC. Upon
acceptance of the CALL REQUEST from the DCE (via the
reformatting process), the Mode S CALL REQUEST packet
shall be forwarded to frame processing. Upon acceptance of a
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 and/or the
peer XDCE abort a call before they have received a CALL
ACCEPT packet, they shall indicate this condition by issuing
a CLEAR REQUEST packet. hwedures for handling these
cases shall be as specified in Table 5-16 and Table 5-20.
Note.- The ADCE process within the ADLP acts as a
peer process to the GDCE process in the GDLP 5.2.6.3.3 VIRTUAL CALL CLEARING
5.2.6.1 State transitions. The XDCE shall operate as a 5.2.6.3.3.1 If the XDCE receives a Mode S CALL
state machine. Upon entering a state, the XDCE shall perfom REQUEST from the process that it cannot
the actions specified in Table 5-14. State transition and support, it shall initiate a Mode C ~ E R~EQRUE ST packet
additional action($) shall be as specified in Table 5-15 through that is sent to the DCE (via the process) for
Table 5-22. transfer to the DTE (the DCE thus enters the DCE CLEAR
Note 1.- The next state transition ( S f any) that occurs
when the XDCE receives a packet from the peer XDCE is
specified by Table 5-15 through Table 5-19. The same
transitions are dejined in TabIe 5-20 through TabIe 5-22 when
the XDCE receives a packet from the DCE (via the reforrnatting
process).
Note 2.- The XDCE state hierarchy is the same as for the
DCE as presented in Figure 5-2, except that states r2, r3 and
p5 are omitted.
5.2.6.2 DISPOSITlON OF PACKETS
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：附件10--航空電信an10_v3_1ed_amend_73(22)