曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
2. All packets from thc peer XDLP have been checked for duplication before evaluation as represented by this table.
3. An invalid PR value is one which is less than the PR value (modulo 16) of thc last packet sent by the peer XDLP, or greater
than the PS value of the next data packet to be transmitted by the XDLP
4. An invalid PS value is one which is different from the next expected vali~e [or PS.
5. An invalid LV subfield is one which represents a value that is too large for the size of thc segment rcccived.
6. Table entries are defined as follows: A = action to be taken, S = the statc to be entered, D = the diagnostic code to be used
in packels generated as a result of this action, DISCARD indicates that the received packet is to be cleared from the XDLP
buffers, and INVALID indicates that the packetlstate combination cannot occur.
7. The number in parentheses below an "A = NORMAL" table e n 0 is the paragraph number in this document that defines the
actions to be takcn to 1)elform normal processing on the received packet. If no paragraph numbcr is referenced, the normal
processing is defined in the table entry.
8. The error procedure consists or pelforming thc spccified actions when entering the d3 state (which includes fonvarding a
RESET REQUEST packet to the peer XDLP) and sending a RESET REQUEST packet to the DCE (via the reformatting
proccss).
9. RR, RNR, and REJECT packets have no end-to-cnd significance and are nor forwarded to the DCE.
Annex 30 - Aeronautical Tebcommunicutions
Table 5-20. DCE effect on ADCE (GDCE) call setup and clearing states
7/11/96
No. 71
Packet reccived from
DCE
(see Notes 2 & 4)
ADCE (GDCE) call setup and clearing states (see Notes 1, 7 and 8)
ADCE
(GDCE)
GDLP ADCE GDLP to GDLP
(ADLP) (GDCE) (ADLP) (ADLP)
CALL CALL DATA CLEAR CLEAR
READY REQUEST REQUEST TRANSFER REQUEST REQUEST
P 1 ~2 ~3 P4 ~6 ~7
CALL REQUEST A=NORMAL INVALID INVALID INVALID INVALID INVALID
(see Note 6) (5.2.6.3.1) (see Note 5) (see Note 3) (see Note 3) (see Note 3) (see Note 3)
S=p3
(forward)
CALL ACCEPT A=DISCARD A=NORMAL INVALID INVALID A=DISCARD A=DISCARD
(see Note 4) S=p4 (see Note 3) (see Note 3)
(forward)
CLEAR REQUEST A=DISCARD A=NORMAL A=NORMAL A=NORMAL A=DISCARD A=DISCARD
(see Note 4) (5.2.6.3.3) (5.2.6.3.3) (5.2.6.3.3)
S=p7 S=p7 S=p7
(forward) (forward) (forward)
DATA INTERRUPT A=DISCARD INVALID INVALID See Table A=DISCARD A=DISCARD
or RESET packets (see Note 3) (see Note 3) 5-2 1
(see Note 4)
NOTES:
1. The XDCE is not necessarily in the same state as the DTEIDCE interface.
2. This is Ihe DTE packct received via the DCE after all DTUDCE processing has occurred. Procedures local to the DTElDCE
interface (such ar RR, RNR, md REJECT if in effect), do not affect the XDCE di~ctlyA. ll error procedures as documented
in IS0 8208 have been performed. Hence certain packets arc rejected by the interface and an not represented in this table.
3. Thc DCE in its protocol operation with thc DTE will detect this error condition, hence the erroneous packet can bc said never
to "reach" the XDCE; see also Note 2.
4. The channel number for the DTFYDCE need not be thc same channel numbcr used for the ADCEIGDCE; a packet from the
DTE which contains a channel number is associated with an airlground channel by means of a previously cshblished crossreferencu
~ ~ b lIef .n one exists then the DTE/DCE channel by definition references ;in airlground channel in the pl state.
5. The ADCE assigns all channel numnkrs \ ~ s bde tween the ADI-P and GDLP; hence call collisions (denoted p5 IS0 8208) m
nor possible; sec also Note 4.
6. A CALL REQUEST frorn the DTE can never Ix associated with an XDCE channel number which is not in the pl state.
7 . Table cntries are defincd a? Follows: A = action to be taken, S = the stale to be entered, D = the diagnostic code to be used in
packets gcnerared as a result of this action, DISCARD indicates that thc received packet is to be cleared from the XDLP
buffers, and INVALID indicates that the packetlsrate combination cannot occur
8. The number in parentheses below an 'A = NORMAL-" table cnuy is the paragraph number in this doculllent that defines the
actions to be taken to perfonn normal processing on the received packet. If no paragraph number is referenced, the normal
processing is defined in the table entry.
Annex 10 - Aeronuutical Telecommunications
Table 5-21. DCE effect on ADCE (GDCE) reset states
Volume ZII
7/11/96
No. 71
Packet received from DCE
ADCE (GDCE) reset states
(see Notes 1, 4 and 5)
ADCE (GDCE)
RESET
now CONTROL GDLP (ADLP) REQUEST
READY RESET REQUEST to GDLP (ADLP)
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_71(44)
