Publication: Magyar Közlöny
Issue: MK-2009-104 (Year: 2009, Number: 104)
Era: 2004-2010
Section: 
Paragraph Index: 1907

b) GDLP state transitions when the terms in parenthesis are used and the XDCE or XDLP preceding them are omitted. 5.3.2 Diagnostic and cause codes. The table entries for certain conditions indicate a diagnostic code that shall be included in the packet generated when entering the state indicated. The term, “D = ,” shall define the diagnostic code. When “A = DIAG ”, the action taken shall be to generate an ISO 8208 DIAGNOSTIC packet and transfer it to the DTE; the diagnostic code indicated shall define the entry in the diagnostic field of the packet. The cause field shall be set as specified in 5.2.6.3.3. The reset cause field shall be set as specified in ISO 8208. Note 1.— The tables provided below specify state requirements in the following order: 5-3 DCE special cases 5-4 DTE effect on DCE restart states 5-5 DTE effect on DCE call setup and clearing states 5-6 DTE effect on DCE reset states 5-7 DTE effect on DCE interrupt transfer states 5-8 DTE effect on DCE flow control transfer states 5-9 XDCE effect on DCE restart states 5-10 XDCE effect on DCE call setup and clearing states 5-11 XDCE effect on DCE reset states 5-12 XDCE effect on DCE interrupt transfer states 5-15 GDLP (ADLP) effect on ADCE (GDCE) packet layer ready states 5-16 GDLP (ADLP) effect on ADCE (GDCE) call setup and clearing states 5-17 GDLP (ADLP) effect on ADCE (GDCE) reset states 5-18 GDLP (ADLP) effect on ADCE (GDCE) interrupt transfer states 5-19 GDLP (ADLP) effect on ADCE (GDCE) flow control transfer states 5-20 DCE effect on ADCE (GDCE) call setup and clearing states 5-21 DCE effect on ADCE (GDCE) reset states 5-22 DCE effect on ADCE (GDCE) interrupt transfer states Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-46 Note 2.— All tables specify both ADLP and GDLP actions. Note 3.— Within the Mode S subnetwork, states p6 and d2 are transient states. Note 4.— References to “notes” in the state tables refer to table-specific notes that follow each state table. Note 5.— All diagnostic and cause codes are interpreted as decimal numbers. Note 6.— An SVC between an ADCE and a GDCE may be identified by a temporary and/or permanent channel number, as defined in 5.2.5.1.2. 5.4 MODE S PACKET FORMATS 5.4.1 Formats. The Mode S packet formats shall be as specified in Figures 5-3 to 5-22. 5.4.2 Significance of control fields. The structure of the format control fields used in Mode S packets shall be as specified in Figure 5-23. The significance of all control fields used in these packet formats shall be as follows: Field symbol Definition AG Address, Ground; the 8-bit binary representation of the ground DTE address (5.2.3.1.3.1) AM Address, Mobile; the 4-bit binary representation of the last two BCD digits of the mobile DTE address (5.2.3.1.3.2) CC Clearing cause as defined in ISO 8208 CH Channel number (1 to 15) DC Diagnostic code as defined in ISO 8208 DP Data packet type (Figure 5-23) F S-bit sequence, first packet flag FILL Fill field FILL1 Has a length of 6 bits for a non-multiplexed packet in a downlink SLM frame; otherwise it is 0 bit FILL2 Has a length of 0 bit for a non-multiplexed packet in a downlink SLM frame and for a multiplexing header; otherwise it is 2 bits FIRST PACKET The contents of the first of the multiplexed packets FS Fast select present IN Initialization bit L “More bit” for long-form MSP packets as specified in 5.2.7.4 LAST PACKET The contents of the last of the multiplexed packets Part I Annex 10 — Aeronautical Communications I-5-47 22/11/07 LENGTH The length of a multiplexed packet in bytes expressed as an unsigned binary number LV User data field length; number of user bytes as specified in 5.2.2.3.1 M “More bit” for SVC DATA packets as specified in 5.2.5.1.4.1 M/CH MSP channel number MP MSP packet type (Figure 5-23) M/SN Sequence number; the sequence number for the long form MSP packet OD Optional data ODL Optional data length OF Option flag P Priority field PR Packet receive sequence number PS Packet send sequence number RC Resetting cause code as defined in ISO 8208 RT Route table as defined in 5.2.5.3.3.8 RTL Route table length expressed in bytes S “More bit” for CALL REQUEST, CALL ACCEPT, CLEAR REQUEST and INTERRUPT packets as specified in 5.2.5.1.4.2 SN Sequence number; the sequence number for this packet type SP Supervisory packet (Figure 5-23) SS Supervisory subset number (Figure 5-23) ST Supervisory type (Figure 5-23) TC Temporary channel number (1 to 3) UD User data field Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-48 TABLES FOR CHAPTER 5 Table 5-1. ADLP Mode S subnetwork timers Timer name Timer label Nominal value Reference Channel retirement Active channel-ADLP Interrogator interrogation Interrogator link Link frame cancellation L-bit delivery-ADLP Packet resequencing and S-bit delivery Tr Tx Ts Tz Tc Tm Tq 600 s 420 s 60 s 30 s 60 s 120 s 60 s 5.2.8.3.1 5.2.8.3.2 5.2.8.1.2 5.2.7.1.1.4.2, 5.2.8.1.3.2 5.2.2.1.1.4.5 5.2.7.4.3 5.2.6.9 Table 5-2. DCE actions at state transition DCE state State definition Action that shall be taken when entering the state r1 PACKET LEVEL READY Return all SVCs to the p1 state (see p1 state explanation). r2 DTE RESTART REQUEST Return each SVC to the p1 state (see p1 state explanation). Issue a RESTART CONFIRMATION to the DTE. r3 DCE RESTART REQUEST Issue a RESTART REQUEST to the DTE. Unless entered via the r2 state, send a RESTART REQUEST to the reformatting process. p1 READY Release all resources assigned to SVC. Break the correspondence between the DTE/DCE SVC and the ADCE/GDCE SVC (the ADCE/GDCE SVC may not yet be in the p1 state). p2 DTE CALL REQUEST Determine if sufficient resources exist to support request; if so, allocate resources and forward CALL REQUEST packet to reformatting process; if not, enter DCE CLEAR REQUEST to DTE state (p7). Determination of resources and allocation is as defined in ISO 8208. p3 DCE CALL REQUEST Determine if sufficient resources exist to support request; if so allocate resources and forward CALL REQUEST packet to DTE; if not, send a CLEAR REQUEST packet to the reformatting process. Determination of resources and allocation is as defined in ISO 8208. p4 DATA TRANSFER No action. p5 CALL COLLISION Reassign outgoing call to another SVC (the DTE in its call collision state ignores the incoming call) and enter the DCE CALL REQUEST state (p3) for that new SVC. Enter the p2 state to process the CALL REQUEST from the DTE. p6 DTE CLEAR REQUEST Release all resources assigned to SVC, send a CLEAR CONFIRMATION packet to the DTE and enter p1 state. p7 DCE CLEAR REQUEST to DTE Forward CLEAR REQUEST packet to DTE. d1 FLOW CONTROL READY No action. d2 DTE RESET REQUEST Remove DATA packets transmitted to DTE from window; discard any DATA packets that represent partially transmitted M-bit sequences and discard any INTERRUPT packet awaiting transfer to the DTE; reset all window counters to 0; set any timers and retransmission parameters relating to DATA and INTERRUPT transfer to their initial value. Send RESET CONFIRMATION packet to DTE. Return SVC to d1 state. d3 DCE RESET REQUEST to DTE Remove DATA packets transmitted to DTE from window; discard any DATA packets that represent partially transmitted M-bit sequences and discard any INTERRUPT packet awaiting transfer to the DTE; reset all window counters to 0; set any timers and retransmission parameters relating to DATA and INTERRUPT transfer to their initial value. Forward RESET REQUEST packet to DTE. Part I Annex 10 — Aeronautical Communications I-5-49 22/11/07 DCE state State definition Action that shall be taken when entering the state i1 DTE INTERRUPT READY No action. i2 DTE INTERRUPT SENT Forward INTERRUPT packet received from DTE to reformatting process. jl DCE INTERRUPT READY No action. j2 DCE INTERRUPT SENT Forward INTERRUPT packet received from reformatting process to DTE. f1 DCE RECEIVE READY No action. f2 DCE RECEIVE NOT READY No action. g1 DTE RECEIVE READY No action. g2 DTE RECEIVE NOT READY No action. Table 5-3. DCE special cases Received from DTE DCE special cases Any state Any packet less than 2 bytes in length (including a valid data link level frame containing no packet) A=DIAG D=38 Any packet with an invalid general format identifier A=DIAG D=40 Any packet with a valid general format identifier and an assigned logical channel identifier (includes a logical channel identifier of 0) See Table 5-4 Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-50 Table 5-4. DTE effect on DCE restart states DCE restart states (see Note 5) Packet received from DTE PACKET LEVEL READY (see Note 1) r1 DTE RESTART REQUEST r2 DCE RESTART REQUEST r3 Packets having a packet type identifier shorter than 1 byte and logical channel identifier not equal to 0 See Table 5-5 A=ERROR S=r3 D=38 (see Note 4) A=DISCARD Any packet, except RESTART, REGISTRATION (if supported) with a logical channel identifier of 0 A=DIAG D=36 A=DIAG D=36 A=DIAG D=36 Packet with a packet type identifier which is undefined or not supported by DCE See Table 5-5 A=ERROR S=r3 D=33 (see Note 4) A=DISCARD RESTART REQUEST, RESTART CONFIRMATION, or REGISTRATION (if supported) packet with a logical channel identifier unequal to 0 See Table 5-5 A=ERROR S=r3 D=41 (see Note 4) A=DISCARD RESTART REQUEST A=NORMAL (forward) S=r2 A=DISCARD A=NORMAL S=p1 or d1 (see Note 2) RESTART CONFIRMATION A=ERROR S=r3 D=17 (see Note 6) A=ERROR S=r3 D=18 (see Note 4) A=NORMAL S=p1 or d1 (see Note 2) RESTART REQUEST OR RESTART CONFIRMATION packet with a format error A=DIAG D=38, 39, 81 or 82 A=DISCARD A=ERROR D=38, 39, 81 or 82 REGISTRATION REQUEST or REGISTRATION CONFIRMATION packets (see Note 3) A=NORMAL A=NORMAL A=NORMAL REGISTRATION REQUEST or REGISTRATION CONFIRMATION packet with a format error (see Note 3) A=DIAG D=38, 39, 81 or 82 A=ERROR S=r3 D=38, 39, 81 or 82 (see Note 4) A=ERROR D=38, 39, 81 or 82 Call setup, call clearing, DATA, interrupt, flow control, or reset packet See Table 5-5 A=ERROR S=r3 D=18 A=DISCARD NOTES: 1. The Mode S subnetwork has no restart states. Receipt of a RESTART REQUEST causes the DCE to respond with a RESTART CONFIRMATION. The RESTART REQUEST packet is forwarded to the reformatting process, which issues clear requests for all SVCs associated with the DTE. The DCE enters the r3 state only as a result of an error detected on the DTE/DCE interface. 2. The SVC channels are returned to state p1, the permanent virtual circuits (PVC) channels are returned to state d1. 3. The use of the registration facility is optional on the DTE/DCE interface. 4. No action is taken within the Mode S subnetwork. 5. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets generated as a result of this action, DISCARD indicates that the received packet is to be cleared for the XDLP buffers, and INVALID indicates that the packet/state combination cannot occur. 6. The error procedure consists of entering the r3 state, and sending a RESTART REQUEST to the reformatting process. Part I Annex 10 — Aeronautical Communications I-5-51 22/11/07 Table 5-5. DTE effect on DCE call setup and clearing states DCE call setup and clearing states (see Note 5) Packet received from DTE READY p1 DTE CALL REQUEST p2 DCE CALL REQUEST p3 DATA TRANSFER p4 CALL COLLISION p5 (see Notes 1 and 4) DTE CLEAR REQUEST p6 DCE CLEAR REQUEST to DTE p7 Packets having a packet type identifier shorter than 1 byte A=ERROR S=p7 D=38 A=ERROR S=p7 D=38 (see Note 2) A=ERROR S=p7 D=38 (see Note 2) See Table 5-6 A=ERROR S=p7 D=38 (see Note 2) A=ERROR S=p7 D=38 (see Note 2) A=DISCARD Packets having a packet type identifier which is undefined or not supported by DCE A=ERROR S=p7 D=33 A=ERROR S=p7 D=33 (see Note 2) A=ERROR S=p7 D=33 (see Note 2) See Table 5-6 A=ERROR S=p7 D=33 (see Note 2) A=ERROR S=p7 D=33 (see Note 2) A=DISCARD RESTART REQUEST, RESTART CONFIRMATION or REGISTRATION packet with logical channel identifier unequal to 0 A=ERROR S=p7 D=41 A=ERROR S=p7 D=41 (see Note 2) A=ERROR S=p7 D=41 (see Note 2) See Table 5-6 A=ERROR S=p7 D=41 (see Note 2) A=ERROR S=p7 D=41 (see Note 2) A=DISCARD CALL REQUEST A=NORMAL S=p2 (forward) A=ERROR S=p7 D=21 (see Note 2) A=NORMAL S=p5 A=ERROR S=p7 D=23 (see Note 2) A=ERROR S=p7 D=24 (see Note 2) A=ERROR S=p7 D=25 (see Note 2) A=DISCARD CALL ACCEPT A=ERROR S=p7 D=20 A=ERROR S=p7 D=21 (see Note 2) A=NORMAL S=p4 (Forward) or A=ERROR S=p7 D=42 (see Notes 2 and 3) A=ERROR S=p7 D=23 (see Note 2) A=ERROR S=p7 D=24 (see Notes 2 and 4) A=ERROR S=p7 D=25 (see Note 2) A=DISCARD CLEAR REQUEST A=NORMAL S=p6 A=NORMAL S=p6 (forward) A=NORMAL S=p6 (forward) A=NORMAL S=p6 (forward) A=NORMAL S=p6 (forward) A=DISCARD A=NORMAL S=p1 (do not forward) CLEAR CONFIRMATION A=ERROR S=p7 D=20 A=ERROR S=p7 D=21 (see Note 2) A=ERROR S=p7 D=22 (see Note 2) A=ERROR S=p7 D=23 (see Note 2) A=ERROR S=p7 D=24 (see Note 2) A=ERROR S=p7 D=25 (see Note 2) A=NORMAL S=p1 (do not forward) DATA, interrupt, flow control or reset packets A=ERROR S=p7 D=20 A=ERROR S=p7 D=21 (see Note 2) A=ERROR S=p7 D=22 (see Note 2) See Table 5-6 A=ERROR S=p7 D=24 (see Note 2) A=ERROR S=p7 D=25 (see Note 2) A=DISCARD Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-52 DCE call setup and clearing states (see Note 5) Packet received from DTE READY p1 DTE CALL REQUEST p2 DCE CALL REQUEST p3 DATA TRANSFER p4 CALL COLLISION p5 (see Notes 1 and 4) DTE CLEAR REQUEST p6 DCE CLEAR REQUEST to DTE p7 NOTES: 1. On entering the p5 state, the DCE reassigns the outgoing call to the DTE to another channel (no CLEAR REQUEST is issued) and responds to incoming DTE call as appropriate with a CLEAR REQUEST or CALL ACCEPT packet. 2. The error procedure consists of performing the actions specified when entering the p7 state (including sending a CLEAR REQUEST packet to the DTE) and additionally sending a CLEAR REQUEST packet to the XDCE (via the reformatting process). 3. The use of the fast select facility with a restriction on the response prohibits the DTE from sending a CALL ACCEPT packet. 4. The DTE in the event of a call collision must discard the CALL REQUEST packet received from the DCE. 5. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. Part I Annex 10 — Aeronautical Communications I-5-53 22/11/07 Table 5-6. DTE effect on DCE reset states DCE reset states (see Note 2) Packet received from DTE FLOW CONTROL READY d1 RESET REQUEST by DTE d2 DCE RESET REQUEST to DTE d3 Packet with a packet type identifier shorter than 1 byte A=ERROR S=d3 D=38 (see Note 1) A=ERROR S=d3 D=38 (see Note 1) A=DISCARD Packet with a packet type identifier which is undefined or not supported by DCE A=ERROR S=d3 D=33 (see Note 1) A=ERROR S=d3 D=33 (see Note 1) A=DISCARD RESTART REQUEST, RESTART CONFIRMATION, or REGISTRATION (if supported) packet with logical channel identifier unequal to 0 A=ERROR S=d3 D=41 (see Note 1) A=ERROR S=d3 D=41 (see Note 1) A=DISCARD RESET REQUEST A=NORMAL S=d2 (forward) A=DISCARD A=NORMAL S=d1 (do not forward) RESET CONFIRMATION A=ERROR S=d3 D=27 (see Note 1) A=ERROR S=d3 D=28 (see Note 1) A=NORMAL S=d1 (do not forward) INTERRUPT packet See Table 5-7 A=ERROR S=d3 D=28 (see Note 1) A=DISCARD INTERRUPT CONFIRMATION packet See Table 5-7 A=ERROR S=d3 D=28 (see Note 1) A=DISCARD DATA or flow control packet See Table 5-8 A=ERROR S=d3 D=28 (see Note 1) A=DISCARD REJECT supported but not subscribed to A=ERROR S=d3 D=37 (see Note 1) A=ERROR S=d3 D=37 (see Note 1) A=DISCARD NOTES: 1. The error procedure consists of performing the specified actions when entering the d3 state (which includes forwarding a RESET REQUEST packet to the DTE) and sending a RESET REQUEST packet to the XDCE (via the formatting function). 2. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets generated as a result of this action, DISCARD indicates that the received packet is to be cleared for the XDLP buffers, and INVALID indicates that the packet/state combination cannot occur. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-54 Table 5-7. DTE effect on DCE interrupt transfer states DTE/DCE interrupt transfer states (see Note 2) Packet received from DTE DTE INTERRUPT READY i1 DTE INTERRUPT SENT i2 INTERRUPT (see Note 1) A=NORMAL S=i2 (forward) A=ERROR S=d3 D=44 (see Note 3) DTE/DCE interrupt transfer states (see Note 2) Packet received from DTE DCE INTERRUPT READY j1 DCE INTERRUPT SENT j2 INTERRUPT CONFIRMATION (see Note 1) A=ERROR S=d3 D=43 (see Note 3) A=NORMAL S=j1 (forward) NOTES: 1. If the packet has a format error, then the error procedure applies (see Note 3). Interrupt packets with user data greater than 32 bytes should be treated as a format error. 2. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. 3. The error procedure consists of performing the specified actions when entering the d3 state (which includes forwarding a RESET REQUEST packet to the DTE) and sending a RESET REQUEST packet to the XDCE (via the reformatting process). Part I Annex 10 — Aeronautical Communications I-5-55 22/11/07 Table 5-8. DTE effect on DCE flow control transfer states DCE flow control transfer states (see Notes 2 and 3) Packet received from DTE DCE RECEIVE READY f1 DCE RECEIVE NOT READY f2 DATA packet with less than 4 bytes when using modulo 128 numbering A=ERROR S=d3 D=38 (see Note 4) A=DISCARD DATA packet with invalid PR A=ERROR S=d3 D=2 (see Note 4) A=ERROR S=d3 D=2 (see Note 4) DATA packet with valid PR but invalid PS or user data field with improper format A=ERROR S=d3 D=1 (invalid PS) D=39 (UD > max negotiated length) D=82 (UD unaligned) (see Note 4) A=DISCARD (process PR data) DATA packet with valid PR with M-bit set to 1 when the user data field is partially full A=ERROR S=d3 D=165 (see Note 4) A=DISCARD (process PR data) DATA packet with valid PR, PS and user data field format A=NORMAL (forward) A=DISCARD (process PR data) DCE flow control transfer states (see Notes 2 and 3) Packet received from DTE DTE RECEIVE READY g1 DTE RECEIVE NOT READY g2 RR, RNR, or REJECT packet with less than 3 bytes when using modulo 128 numbering (see Note 1) A=DISCARD A=DISCARD RR, RNR, or REJECT packet with an invalid PR A=ERROR S=d3 D=2 (see Note 4) A=ERROR S=d3 D=2 (see Note 4) RR packet with a valid PR A=NORMAL A=NORMAL S=g1 RNR packet with a valid PR A=NORMAL S=g2 A=NORMAL REJECT packet with a valid PR A=NORMAL A=NORMAL S=g1 NOTES: 1. The reject procedures are not required. 2. The RR, RNR and REJECT procedures are a local DTE/DCE matter and the corresponding packets are not forwarded to the XDCE. 3. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. 4. The error procedure consists of performing the specified actions when entering the d3 state (which includes forwarding a RESET REQUEST packet to the DTE) and sending a RESET REQUEST packet to the XDCE (via the reformatting process). Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-56 Table 5-9. XDCE effect on DCE restart states DCE restart states (see Note) Packet received from XDCE PACKET LEVEL READY r1 DTE RESTART REQUEST r2 DCE RESTART REQUEST r3 CALL REQUEST See Table 5-10 Send CLEAR REQUEST to reformatting process with D=244 Send CLEAR REQUEST to reformatting process with D=244 CALL ACCEPT, CLEAR REQUEST, DATA, INTERRUPT, INTERRUPT CONFIRMATION, RESET REQUEST See Table 5-10 A=DISCARD A=DISCARD Note.— Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. Table 5-10. XDCE effect on DCE call setup and clearing states DCE call setup and clearing states (see Note) Packet received from XDCE READY p1 DTE CALL REQUEST p2 DCE CALL REQUEST p3 DATA TRANSFER p4 CALL COLLISION p5 DTE CLEAR REQUEST p6 DCE CLEAR REQUEST to DTE p7 CALL REQUEST A=NORMAL S=p3 (forward) INVALID INVALID INVALID INVALID INVALID INVALID CALL ACCEPT A=DISCARD A=NORMAL S=p4 (forward) INVALID INVALID INVALID A=DISCARD A=DISCARD CLEAR REQUEST A=DISCARD A=NORMAL S=p7 (forward) A=NORMAL S=p7 (forward) A=NORMAL S=p7 (forward) INVALID A=DISCARD A=DISCARD DATA, INTERRUPT, INTERRUPT CONFIRMATION, or RESET REQUEST A=DISCARD INVALID INVALID See Table 5-11 INVALID A=DISCARD A=DISCARD Note.— Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. Part I Annex 10 — Aeronautical Communications I-5-57 22/11/07 Table 5-11. XDCE effect on DCE reset states DCE reset states (see Note) Packet received from XDCE FLOW CONTROL READY d1 DTE RESET REQUEST d2 DCE RESET REQUEST to DTE d3 RESET REQUEST A=NORMAL S=d3 (forward) A=NORMAL S=d1 (forward) A=DISCARD INTERRUPT See Table 5-12 A=DISCARD A=DISCARD INTERRUPT CONFIRMATION See Table 5-12 A=DISCARD INVALID DATA A=NORMAL (forward) A=DISCARD A=DISCARD Note.— Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. Table 5-12. XDCE effect on DCE interrupt transfer states DCE interrupt transfer states (see Note) Packet received from XDCE DTE INTERRUPT READY i1 DTE INTERRUPT SENT i2 INTERRUPT CONFIRMATION INVALID A=NORMAL S=i1 (forward) DCE interrupt transfer states (see Note) Packet received from XDCE DCE INTERRUPT READY j1 DCE INTERRUPT SENT j2 INTERRUPT A=NORMAL S=j2 (forward) INVALID Note.— Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-58 Table 5-13. GDLP Mode S subnetwork timers Timer name Timer label Nominal value Reference Active channel-GDLP L-bit delivery-GDLP Packet resequencing and S-bit delivery Tx Tm Tq 300 s 120 s 60 s 5.2.8.3.2 5.2.7.4.3 5.2.6.9 Table 5-14. XDCE actions at state transition XDCE state State definition Action that shall be taken when entering the state r1 PACKET LEVEL READY Return all SVCs to the p1 state. p1 READY Release all resources assigned to the SVC. Break the correspondence between the ADCE/GDCE SVC and the DTE/DCE SVC (the DTE/DCE SVC may not yet be in a p1 state). p2 GDLP(ADLP) CALL REQUEST Determine if sufficient resources exist to support request; if so allocate resources and forward Mode S CALL REQUEST packet to reformatting process; if not, enter ADCE(GDCE) CLEAR REQUEST to GDLP(ADLP) state (p7). p3 ADCE(GDCE) CALL REQUEST Determine if sufficient resources exist to support request; if so, allocate resources and forward Mode S CALL REQUEST packet to frame processing; if not, send Mode S CLEAR REQUEST to reformatting process and go to state p1. Do not forward the Mode S CALL REQUEST to the peer XDCE. p4 DATA TRANSFER No action. p6 GDLP(ADLP) CLEAR REQUEST Release all resources, send a Mode S CLEAR CONFIRMATlON packet to the peer XDCE and enter the p1 state. p7 ADCE(GDCE) CLEAR REQUEST to GDLP(ADLP) Forward Mode S CLEAR REQUEST packet to the peer XDCE via frame processing. d1 FLOW CONTROL READY No action. d2 GDLP(ADLP) RESET REQUEST Remove Mode S DATA packets transmitted to peer XDCE from window; discard any DATA packets that represent partially transmitted M-bit sequences and discard any Mode S INTERRUPT packets awaiting transfer to the peer XDCE; reset all flow control window counters to 0 (5.2.6.7.1). Send Mode S RESET CONFIRMATION packet to the peer XDCE. Return SVC to d1 state. Forward Mode S RESET REQUEST packet to reformatting process. d3 ADCE(GDCE) RESET REQUEST to GDLP(ADLP) Remove Mode S DATA packets transmitted to peer XDCE from window; discard any DATA packets that represent partially transmitted M-bit sequences and discard any Mode S INTERRUPT packets awaiting transfer to the peer XDCE; reset all flow control window counters to 0 (5.2.6.7.1). Forward Mode S RESET REQUEST packet to peer XDCE via frame processing. i1 GDLP(ADLP) INTERRUPT READY No action. i2 GDLP(ADLP) INTERRUPT SENT Forward Mode S INTERRUPT packet received from peer XDCE to the reformatting process. j1 ADCE(GDCE) INTERRUPT READY No action. j2 ADCE(GDCE) INTERRUPT SENT Forward Mode S INTERRUPT packet received from the reformatting process. f1 ADCE(GDCE) RECEIVE READY No action. f2 ADCE(GDCE) RECEIVE NOT READY No action. g1 GDLP(ADLP) RECEIVE READY No action. g2 GDLP(ADLP) RECEIVE NOT READY No action. Part I Annex 10 — Aeronautical Communications I-5-59 22/11/07 Table 5-15. GDLP (ADLP) effect on ADCE (GDCE) packet layer ready states ADCE (GDCE) states (see Notes 1 and 3) Packet received from GDLP (ADLP) (see Note 2) PACKET LEVEL READY r1 CH=0 with no TC present (see Note 4) or CH=0 in a CALL ACCEPT by ADLP packet A=DISCARD Unassigned packet header A=DISCARD Call setup, call clearing, DATA, interrupt, flow control, or reset See Table 5-16 NOTES: 1. The XDCE state is not necessarily the same state as the DTE/DCE interface. 2. All packets from the peer XDLP have been checked for duplication before evaluation as represented by this table. 3. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. 4. Where CH=0 and a valid TC is present in a CLEAR REQUEST by ADLP or GDLP packet or a CLEAR CONFIRMATION by ADLP or GDLP packet, it is handled as described in 5.2.5.1.2.3 and Table 5-16. Table 5-16. GDLP (ADLP) effect on ADCE (GDCE) call setup and clearing states ADCE (GDCE) call setup and clearing States (See Notes 1, 7 and 8) Packet received from GDLP (ADLP) (see Note 2) READY p1 GDLP (ADLP) CALL REQUEST p2 ADCE (GDCE) CALL REQUEST p3 DATA TRANSFER p4 GDLP (ADLP) CLEAR REQUEST p6 ADCE (GDCE) CLEAR REQUEST to GDLP (ADLP) p7 Format error (see Note 3) A=ERROR (see Note 10) S=p7 D=33 (see Note 9) A=ERROR S=p7 D=33 (see Note 6) A=ERROR S=p7 D=33 (see Notes 6 and 9) See Table 5-17 A=ERROR S=p7 D=25 (see Note 6) A=DISCARD CALL REQUEST A=NORMAL (5.2.6.3.1) S=p2 (forward request to DCE) A=ERROR S=p7 D=21 (see Note 6) Not applicable (see Note 4) Not applicable (see Note 4) A=ERROR S=p7 D=25 (see Note 6) A=DISCARD CALL ACCEPT A=ERROR S=p7 D=20 (see Note 10) A=ERROR S=p7 D=21 (see Note 6) A=NORMAL (5.2.6.3.1) S=p4 (forward to DCE), or A=ERROR S=p7 D=42 (see Note 6) A=ERROR S=p7 D=23 (see Note 6) A=ERROR S=p7 D=25 (see Note 6) A=DISCARD Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-60 ADCE (GDCE) call setup and clearing States (See Notes 1, 7 and 8) Packet received from GDLP (ADLP) (see Note 2) READY p1 GDLP (ADLP) CALL REQUEST p2 ADCE (GDCE) CALL REQUEST p3 DATA TRANSFER p4 GDLP (ADLP) CLEAR REQUEST p6 ADCE (GDCE) CLEAR REQUEST to GDLP (ADLP) p7 CLEAR REQUEST A=NORMAL (5.2.6.3.3) S=p6 (do not forward) A=NORMAL (5.2.6.3.3) S=p6 (forward to DCE) A=NORMAL (5.2.6.3.3) S=p6 (forward to DCE) A=NORMAL (5.2.6.3.3) S=p6 (forward to DCE) A=DISCARD A=NORMAL (5.2.6.3.3) S=p1 (do not forward) CLEAR CONFIRMATION A=ERROR S=p7 D=20 (see Note 10) A=ERROR S=p7 D=21 (see Note 6) A=ERROR S=p7 D=22 (see Note 6) A=ERROR S=p7 D=23 (see Note 6) A=ERROR S=p7 D=25 (see Note 6) A=NORMAL (5.2.6.3.3) S=p1 (do not forward) DATA, interrupt, flow control or reset packets A=ERROR S=p7 D=20 (see Note 10) A=ERROR S=p7 D=21 (see Notes 6 and 9) A=ERROR S=p7 D=22 (see Notes 5 and 6) See Table 5-17 A=ERROR S=p7 D=25 (see Note 6) A=DISCARD NOTES: 1. The XDCE is not necessarily in the same state as the DTE/DCE interface. 2. All packets from the peer XDLP have been checked for duplication before evaluation as represented by this table. 3. A format error may result from an S-bit sequence having a first or intermediate packet shorter than the maximum length, or else from an invalid LV field in a CALL REQUEST, CALL ACCEPT, CLEAR REQUEST or INTERRUPT packet. There are no other detectable Mode S format errors. 4. The ADCE assigns all channel numbers used between the ADLP and GDLP, hence call collisions are not possible. When a CALL REQUEST by GDLP packet is received bearing a temporary channel number associated with an SVC in the p4 state, the association of the temporary to permanent channel number is broken (5.2.5.1.2.3). 5. Not applicable to the GDLP. 6. The error procedure consists of performing the actions specified when entering the p7 state (including sending a CLEAR REQUEST packet to the peer XDLP) and additionally sending a CLEAR REQUEST packet to the DCE (via the reformatting process). 7. Table entries are defined as follows: A = action to be taken, S = the state to be entered, D = the diagnostic code to be used in packets 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 packet/state combination cannot occur. 8. The number in parentheses below an “A = NORMAL” table entry is the paragraph number in this document that defines the actions to be taken to perform normal processing on the received packet. If no paragraph number is referenced, the normal processing is defined in the table entry. 9. An error condition is declared and transfer to the p7 state is possible only if the ground DTE address is known unambiguously. Otherwise the action is to discard the packet.

Source: https://magyarkozlony.hu/hivatalos-lapok/1f7c6b0e16b4b71a92e5ad24416008bbe2e26aab/dokumentumok/710811d1f7f958a2990684d0cbf918e84f5497e5/letoltes