曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
5.2.5.3.5.3 MSP packet type (MP). This field shall be set to 0.
to I .
5.2.5.3.7.3 MSP packet type (MI.')T.h is field shall be set
5.2.5.3.5.4 Supervisory packet (SP). This field shall be set to 1.
to I.
5.2.5.3.7.4 Supervisory packet (SF'). This ficld shall be set
5.2.5.3.5.5 Chun~zeln unzber (CH): Jf a channel number to 3.
has been allocated during the call acceptance phase, then CH
shall be set to that value, otherwise it shall be set to zero. 5.2.5.3.7.5 S~ipervisoryr ype (ST). This field shall be set lo
3.
5.2.5.3.5.6 E m p o r a ~ch unnel (TC):I f a channel number
has been allocalcd during the call acceptance phase, lhen TC
shall be set to zero, olhcrwise it shall be set to the value used
in the CALL REQUEST by GDLP.
5.2.5.3.7.6 S~tpervisorys ubset (SS). This field shall be set
to I .
5.2.5.3.7.7 Pucket receive sequence number (PR). This
5.2.5.3.5.7 S~~pervisohq;p~e (ST). This field shall be scl field shall be set as specified in 5.2.6.4.4.
to 3.
5.2.5.3.6 MODE S RESET CONHRMATION 5.2.6 XDCE operation
5.2.5.3.6.1 Pucker fonilur. The format for this packet shall Note.- The ADCE process within the ADLP acts us u peer
bc as follows: pmae.ss to the GDCE process in the GDLI?
Part I Alirtex 10 - Aeronautical T~lecnrnrnunicutions
5.2.6.1 State transitions. The XDCE shall operatc as a
state rnachjne. Upon entering a state, the XDCE shall perform
the actions specified in Table 5-14, State transition and
additional action(s) shall be as specified in Table 5-15 through
Table 5-22.
Note 1.- The next state transition (ifany) tlzat occurs when
the XDCE receives a packet from the peer XDCE is specfled
by Table 5-15 through Table 5-19. The same transitions are
defined in Table 5-20 tlzro~~gTha hle 5-22 when the XDCE
receives a packet from' the DCE (via the rejormatting process).
Note 2.- The XDCE state hierarchy is the sanzc as for tlze
DCE as presented in Figure 5-2, except that states r2, r3 and
p5 are omitted.
5.2.6.2 DISPOSITIOONF PACKETS
5.2.6.2.1 Upon rcccipt of a packet from the peer XDCE,
the packet shall be forwarded or not forwarded to the DCE (via
the reformatting process) according to the 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 the
reformatting process), the packet shall be forwarded or not
forwarded lo the peer XDCE according to the parenthetical
instructions contained in Tables 5-20 to 5-22. If no parenthetical
instruction is listed or if the parenthetical instruction
indicates "do not forward" the packet shall be discarded.
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 suficient 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 Ahorring LL cnll rcqlrcst. If the DTE andor the
peer XDCE abo~t a call before they have received a CALL,
ACCEPT packet, they shall indicate this condition by issuing
a CLEAR REQIJEST packet Procedures for handling these
cascs shall be as specified in TJ'able 5- 16 and Table 5-20.
5 2.6.3.3.1 If the XDCE recelves a Mode S CALL
REQUEST from the reformatting process that il cannot
support, it shall initiate a Mode S CLEAR REQUEST packet
that is sent to the DCE (via the reformatling process) [or
transfer to the DTE (the DCE thus enters the DCE CLEAR
REQUEST to DTE state, p7).
5.2.6.3.3.2 If the XDCE rcceives a Mode S CALL
REQUEST packet from thc 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 be satisfied by setting bit 8 oj- tlze cause Beld
to I to indicate that tlze 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;
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_77(25)
