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

6. 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. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-62 Table 5-18. GDLP (ADLP) effect on ADCE (GDCE) interrupt transfer states ADCE/GDCE interrupt transfer states (see Notes 1, 3 and 4) Packet received from GDLP (ADLP) (see Note 2) GDLP (ADLP) INTERRUPT READY i1 GDLP (ADLP) INTERRUPT SENT i2 INTERRUPT (see Note 6) A=NORMAL (5.2.6.4.5) S=i2 (forward to DCE) A=ERROR S=d3 D=44 (see Note 5) ADCE (GDCE) interrupt transfer states (see Notes 1, 3 and 4) Packet received from GDLP (ADLP) (see Note 2) ADCE (GDCE) INTERRUPT READY j1 ADCE (GDCE) INTERRUPT SENT j2 INTERRUPT CONFIRMATION A=ERROR S=d3 D=43 (see Note 5) A=NORMAL (5.2.6.4.5) S=j1 (forward confirmation to DCE) 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. 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. 4. 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. 5. The error procedure consists of performing the specified actions when entering the d3 state (which includes forwarding a RESET REQUEST packet to the peer XDLP) and sending a RESET REQUEST packet to the DCE (via the reformatting process). 6. User data length for INTERRUPT packets greater than 32 bytes, or an out of sequence INTERRUPT packet, are considered as errors. Table 5-19. GDLP (ADLP) effect on ADCE (GDCE) flow control transfer states ADCE (GDCE) flow control transfer states (see Notes 1, 6 and 7) Packet received from GDLP (ADLP) (see Note 2) ADCE (GDCE) RECEIVE READY f1 ADCE (GDCE) RECEIVE NOT READY f2 DATA packet with invalid PR (see Note 3) A=ERROR S=d3 D=2 (see Note 8) A=ERROR S=d3 D=2 (see Note 8) DATA packet with valid PR, invalid PS or LV subfield (see Notes 4 and 5) A=DISCARD, but process the PR value and send REJECT packet containing the expected PS value (see Note 5) A=DISCARD, but process the PR value and send REJECT packet containing the expected PS value when busy condition ends Part I Annex 10 — Aeronautical Communications I-5-63 22/11/07 DATA packet with valid PR, PS and LV subfield A=NORMAL (5.2.6.4.4) (forward) A=PROCESS, if possible; or A=DISCARD, but process the PR value and send REJECT containing the expected PS value when busy condition ends ADCE (GDCE) flow control transfer states (see Notes 1, 6 and 7) Packet received from GDLP (ADLP) (see Note 2) GDLP (ADLP) RECEIVE READY g1 GDLP (ADLP) RECEIVE NOT READY g2 RR, RNR, REJECT packet with invalid PR (see Note 3) A=ERROR S=d3 D=2 (see Note 8) A=ERROR S=d3 D=2 (see Note 8) RR with valid PR field (see Note 9) A=NORMAL (5.2.6.5) A=NORMAL (5.2.6.6) S=g1 RNR with valid PR value (see Note 9) A=NORMAL (5.2.6.5) S=g2 A=NORMAL (5.2.6.6) REJECT with valid PR (see Note 9) A=NORMAL (5.2.6.5) A=NORMAL (5.2.6.6) S=g1 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. An invalid PR value is one which is less than the PR value (modulo 16) of the 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 value for PS. 5. An invalid LV subfield is one which represents a value that is too large for the size of the segment received. In the event of an LV field error which gives rise to a loss of confidence in the correctness of the other fields in the packet, the packet is discarded without any further action. 6. 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. 7. 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. 8. The error procedure consists of performing the specified actions when entering the d3 state (which includes forwarding a RESET REQUEST packet to the peer XDLP) and sending a RESET REQUEST packet to the DCE (via the reformatting process). 9. RR, RNR, and REJECT packets have no end-to-end significance and are not forwarded to the DCE.

Source: https://magyarkozlony.hu/hivatalos-lapok/bfd0d67db9f223889f627fd618725b03526630e2/dokumentumok/d5234fd7275da04023366ab8a434989962a31bdf/letoltes