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

15. The address shall be extracted from the two least significant digits of the called DTE address contained in the ISO 8208 packet and converted to binary representation. 5.2.5.2.2.2 Translation into ISO 8208 packets 5.2.5.2.2.2.1 Translation. Reception by the ADLP reformatting process of a Mode S CALL REQUEST by GDLP packet (or an S-bit sequence of packets) from the ADCE shall result in the generation of a corresponding ISO 8208 CALL REQUEST packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.2.1 with the exceptions as specified in 5.2.5.2.2.2.2. 5.2.5.2.2.2.2 Called DTE, calling DTE address and length fields. The called DTE address shall be composed of the aircraft address and the value contained in the AM field of the Mode S packet, converted to BCD (5.2.3.1.3.2). The calling DTE address shall be the ground DTE address contained in the AG field of the Mode S packet, converted to BCD. The length field shall be as defined in ISO 8208. Part I Annex 10 — Aeronautical Communications I-5-21 22/11/07 5.2.5.2.3 CALL ACCEPT BY ADLP 5.2.5.2.3.1 Translation into Mode S packets 5.2.5.2.3.1.1 Translated packet format. Reception by the ADLP reformatting process of an ISO 8208 CALL ACCEPT packet from the local DCE shall result in the generation of corresponding Mode S CALL ACCEPT by ADLP packet(s) (as determined by S-bit processing (5.2.5.1.4.2)) as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 TC:2 SN:6 CH:4 AM:4 AG:8 S:1 FILL:2 F:1 LV:4 UD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. 5.2.5.2.3.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.3.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.3.1.4 Supervisory packet (SP). This field shall be set to 1. 5.2.5.2.3.1.5 Supervisory type (ST). This field shall be set to 1. 5.2.5.2.3.1.6 Temporary channel number (TC). The TC value in the originating Mode S CALL REQUEST by GDLP packet shall be returned to the GDLP along with the channel number (CH) assigned by the ADLP. 5.2.5.2.3.1.7 Channel number (CH). The field shall be set equal to the channel number assigned by the ADLP as determined during the CALL REQUEST procedures for the Mode S connection. 5.2.5.2.3.1.8 Address, mobile and address, ground. The AM and AG values in the originating Mode S CALL REQUEST by GDLP packet shall be returned in these fields. When present, DTE addresses in the ISO 8208 CALL ACCEPT packet shall be ignored. 5.2.5.2.3.2 Translation into ISO 8208 packets 5.2.5.2.3.2.1 Translation. Reception by the GDLP reformatting process of a Mode S CALL ACCEPT by ADLP packet (or an S-bit sequence of packets) from the GDCE shall result in the generation of a corresponding ISO 8208 CALL ACCEPT packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.3.1 with the exceptions as specified in 5.2.5.2.3.2.2. 5.2.5.2.3.2.2 Called DTE, calling DTE address and length fields. Where present, the called DTE address shall be composed of the aircraft address and the value contained in the AM field of the Mode S packet, converted to BCD (5.2.3.1.3.2). Where present, the calling DTE address shall be the ground DTE address contained in the AG field of the Mode S packet, converted to BCD. The length field shall be as defined in ISO 8208. Note.— The called and calling DTE addresses are optional in the corresponding ISO 8208 packet and are not required for correct operation of the Mode S subnetwork. 5.2.5.2.4 CALL ACCEPT BY GDLP 5.2.5.2.4.1 Translation into Mode S packets 5.2.5.2.4.1.1 Translated packet format. Reception by the GDLP reformatting process of an ISO 8208 CALL ACCEPT packet from the local DCE shall result in the generation of corresponding Mode S CALL ACCEPT by GDLP packet(s) (as determined by S-bit processing (5.2.5.1.4.2)) as follows: Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-22 DP:1 MP:1 SP:2 ST:2 FILL:2 FILL:2 SN:6 CH:4 AM:4 AG:8 S:1 FILL:2 F:1 LV:4 UD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. 5.2.5.2.4.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.4.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.4.1.4 Supervisory packet (SP). This field shall be set to 1. 5.2.5.2.4.1.5 Supervisory type (ST). This field shall be set to 1. 5.2.5.2.4.1.6 Address, mobile and address, ground. The AM and AG values in the originating Mode S CALL REQUEST by ADLP packet shall be returned in these fields. When present, DTE addresses in the ISO 8208 CALL ACCEPT packet shall be ignored. 5.2.5.2.4.2 Translation into ISO 8208 packets 5.2.5.2.4.2.1 Translation. Reception by the ADLP reformatting process of a Mode S CALL ACCEPT by GDLP packet (or an S-bit sequence of packets) from the ADCE shall result in the generation of a corresponding ISO 8208 CALL ACCEPT packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.4.1 with the exceptions as specified in 5.2.5.2.4.2.2. 5.2.5.2.4.2.2 Called DTE, calling DTE address and length fields. Where present, the calling DTE address shall be composed of the aircraft address and the value contained in the AM field of the Mode S packet, converted to BCD (5.2.3.1.3.2). Where present, the called DTE address shall be the ground DTE address contained in the AG field of the Mode S packet, converted to BCD. The length field shall be as defined in ISO 8208. Note.— The called and calling DTE addresses are optional in the corresponding ISO 8208 packet and are not required for correct operation of the Mode S subnetwork. 5.2.5.2.5 CLEAR REQUEST BY ADLP 5.2.5.2.5.1 Translation into Mode S packets 5.2.5.2.5.1.1 Translated packet format. Reception by the ADLP reformatting process of an ISO 8208 CLEAR REQUEST packet from the local DCE shall result in the generation of a corresponding Mode S CLEAR REQUEST by ADLP packet(s) (as determined by S-bit processing (5.2.5.1.4.2)) as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 TC:2 SN:6 CH:4 AM:4 AG:8 CC:8 DC:8 S:1 FILL:2 F:1 LV:4 UD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1 and 5.2.5.2.2. 5.2.5.2.5.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.5.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.5.1.4 Supervisory packet (SP). This field shall be set to 1. Part I Annex 10 — Aeronautical Communications I-5-23 22/11/07 5.2.5.2.5.1.5 Channel number (CH): If a channel number 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.2.5.1.6 Temporary channel (TC): If a channel number has been allocated during the call acceptance phase, then TC shall be set to zero, otherwise it shall be set to the value used in the CALL REQUEST by GDLP. 5.2.5.2.5.1.7 Supervisory type (ST). This field shall be set to 2. 5.2.5.2.5.1.8 Address, ground or address, mobile. The AG and AM values in the originating Mode S CALL REQUEST by ADLP or CALL REQUEST by GDLP packets shall be returned in these fields. When present, DTE addresses in the ISO 8208 CLEAR REQUEST packet shall be ignored. 5.2.5.2.5.1.9 Clearing cause (CC) and diagnostic code (DC) fields. These fields shall be transferred without modification from the ISO 8208 packet to the Mode S packet when the DTE has initiated the clear procedure. If the XDLP has initiated the clear procedure, the clearing cause field and diagnostic field shall be as defined in the state tables for the DCE and XDCE (see also 5.2.6.3.3). The coding and definition of these fields shall be as specified in ISO 8208. 5.2.5.2.5.2 Translation into ISO 8208 packets 5.2.5.2.5.2.1 Translation. Reception by the GDLP reformatting process of a Mode S CLEAR REQUEST by ADLP packet (or an S-bit sequence of packets) from the local GDCE shall result in the generation of a corresponding ISO 8208 CLEAR REQUEST packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.5.1 with the exceptions specified in 5.2.5.2.5.2.2 and 5.2.5.2.5.2.3. 5.2.5.2.5.2.2 Called DTE, calling DTE and length fields. These fields shall be omitted in the ISO 8208 CLEAR REQUEST packet. 5.2.5.2.5.2.3 Clearing cause field. This field shall be set taking account of 5.2.6.3.3. 5.2.5.2.6 CLEAR REQUEST BY GDLP 5.2.5.2.6.1 Translation into Mode S packets 5.2.5.2.6.1.1 Translated packet format. Reception by the GDLP reformatting process of an ISO 8208 CLEAR REQUEST packet from the local DCE shall result in the generation of corresponding Mode S CLEAR REQUEST by GDLP packet(s) (as determined by S-bit processing (5.2.5.1.4.2)) as follows: DP:1 MP:1 SP:2 ST:2 FILL:2 TC:2 SN:6 CH:4 AM:4 AG:8 CC:8 DC:8 S:1 FILL:2 F:1 LV:4 UD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1, 5.2.5.2.2 and 5.2.5.2.5. 5.2.5.2.6.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.6.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.6.1.4 Supervisory packet (SP). This field shall be set to 1. 5.2.5.2.6.1.5 Channel number (CH): If a channel number has been allocated during the call acceptance phase, then CH shall be set to that value, otherwise it shall be set to zero. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-24 5.2.5.2.6.1.6 Temporary channel (TC): If a channel number has been allocated during the call acceptance phase, then TC shall be set to zero, otherwise it shall be set to the value used in the CALL REQUEST by GDLP. 5.2.5.2.6.1.7 Supervisory type (ST). This field shall be set to 2. 5.2.5.2.6.2 Translation into ISO 8208 packets 5.2.5.2.6.2.1 Translation. Reception by the ADLP reformatting process of a Mode S CLEAR REQUEST by GDLP packet (or an S-bit sequence of packets) from the local ADCE shall result in the generation of a corresponding ISO 8208 CLEAR REQUEST packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.6.1. 5.2.5.2.6.2.2 Called DTE, calling DTE and length fields. These fields shall be omitted in the ISO 8208 CLEAR REQUEST packet. 5.2.5.2.7 DATA 5.2.5.2.7.1 Translation into Mode S packets 5.2.5.2.7.1.1 Translated packet format. Reception by the XDLP reformatting process of ISO 8208 DATA packet(s) from the local DCE shall result in the generation of corresponding Mode S DATA packet(s) as determined by M-bit processing (5.2.5.1.4.1), as follows: DP:1 M:1 SN:6 FILL1:0 or 6 PS:4 PR:4 CH:4 LV:4 UD:v 5.2.5.2.7.1.2 Data packet type (DP). This field shall be set to 1. 5.2.5.2.7.1.3 M field (M). A value of 1 shall indicate that the packet is part of an M-bit sequence with more packets in the sequence to follow. A value of 0 shall indicate that the sequence ends with this packet. The appropriate value shall be placed in the M-bit field of the Mode S packet. Note.— See 5.2.5.1.4 and ISO 8208 for a complete explanation. 5.2.5.2.7.1.4 Sequence number (SN). The sequence number field shall be set as specified in 5.2.5.2.1.1.7. 5.2.5.2.7.1.5 Packet send sequence number (PS). The packet send sequence number field shall be set as specified in 5.2.6.4.4. 5.2.5.2.7.1.6 Packet receive sequence number (PR). The packet receive sequence number field shall be set as specified in 5.2.6.4.4. 5.2.5.2.7.1.7 Channel number (CH). The channel number field shall contain the Mode S channel number that corresponds to the incoming ISO 8208 DATA packet channel number. 5.2.5.2.7.1.8 User data length (LV). This field shall indicate the number of full bytes used in the last SLM or ELM segment as defined in 5.2.2.3.1. 5.2.5.2.7.1.9 Fill (FILL1). This field shall be set as specified in 5.2.5.2.1.1.11. 5.2.5.2.7.1.10 User data (UD). The user data shall be transferred from the ISO 8208 packet to the Mode S packet utilizing the M-bit packet assembly processing as required. Part I Annex 10 — Aeronautical Communications I-5-25 22/11/07 5.2.5.2.7.2 Translation into ISO 8208 packets. Reception by the XDLP reformatting process of Mode S DATA packet(s) from the local XDCE shall result in the generation of corresponding ISO 8208 DATA packet(s) to the local DCE. The translation from Mode S packet(s) to the ISO 8208 packet(s) shall be the inverse of the processing defined in 5.2.5.2.7.1. 5.2.5.2.8 INTERRUPT 5.2.5.2.8.1 Translation into Mode S packets 5.2.5.2.8.1.1 Translated packet format. Reception by the XDLP reformatting process of an ISO 8208 INTERRUPT packet from the local DCE shall result in the generation of corresponding Mode S INTERRUPT packet(s) (as determined by S-bit processing (5.2.5.1.4.2)) as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 S:1 F:1 SN:6 CH:4 LV:4 UD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. 5.2.5.2.8.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.8.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.8.1.4 Supervisory packet (SP). This field shall be set to 3. 5.2.5.2.8.1.5 Supervisory type (ST). This field shall be set to 1. 5.2.5.2.8.1.6 User data length (LV). This field shall be set as specified in 5.2.2.3.1. 5.2.5.2.8.1.7 User data (UD). The user data shall be transferred from the ISO 8208 packet to the Mode S packet using the S-bit packet reassembly processing as required. The maximum size of the user data field for an INTERRUPT packet shall be 32 bytes. 5.2.5.2.8.2 Translation into ISO 8208 packets. Reception by the XDLP reformatting process of Mode S INTERRUPT packet(s) from the local XDCE shall result in the generation of a corresponding ISO 8208 INTERRUPT packet to the local DCE. The translation from the Mode S packet(s) to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.8.1. 5.2.5.2.9 INTERRUPT CONFIRMATION 5.2.5.2.9.1 Translation into Mode S packets 5.2.5.2.9.1.1 Translated packet format. Reception by the XDLP reformatting process of an ISO 8208 INTERRUPT CONFIRMATION packet from the local DCE shall result in the generation of a corresponding Mode S INTERRUPT CONFIRMATION packet as follows: DP:1 MP:1 SP:2 ST:2 SS:2 FILL2:0 or 2 SN:6 CH:4 FILL:4 Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. 5.2.5.2.9.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.9.1.3 MSP packet type (MP). This field shall be set to 1. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-26 5.2.5.2.9.1.4 Supervisory packet (SP). This field shall be set to 3. 5.2.5.2.9.1.5 Supervisory type (ST). This field shall be set to 3. 5.2.5.2.9.1.6 Supervisory subset (SS). This field shall be set to 0. 5.2.5.2.9.2 Translation into ISO 8208 packets. Reception by the XDLP reformatting process of a Mode S INTERRUPT CONFIRMATION packet from the local XDCE shall result in the generation of a corresponding ISO 8208 INTERRUPT CONFIRMATION packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.9.1. 5.2.5.2.10 RESET REQUEST 5.2.5.2.10.1 Translation into Mode S packets 5.2.5.2.10.1.1 Translated packet format. Reception by the XDLP reformatting process of an ISO 8208 RESET REQUEST packet from the local DCE shall result in the generation of a corresponding Mode S RESET REQUEST packet as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 FILL:2 SN:6 CH:4 FILL:4 RC:8 DC:8 Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. 5.2.5.2.10.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.2.10.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.2.10.1.4 Supervisory packet (SP). This field shall be set to 2. 5.2.5.2.10.1.5 Supervisory type (ST). This field shall be set to 2. 5.2.5.2.10.1.6 Reset cause code (RC) and diagnostic code (DC). The reset cause and diagnostic codes used in the Mode S RESET REQUEST packet shall be as specified in the ISO 8208 packet when the reset procedure is initiated by the DTE. If the reset procedure originates with the DCE, the DCE state tables shall specify the diagnostic fields coding. In this case, bit 8 of the reset cause field shall be set to 0. 5.2.5.2.10.2 Translation into ISO 8208 packets. Reception by the XDLP reformatting process of a Mode S RESET packet from the local XDCE shall result in the generation of a corresponding ISO 8208 RESET packet to the local DCE. The translation from the Mode S packet to the ISO 8208 packet shall be the inverse of the processing defined in 5.2.5.2.10.1. 5.2.5.2.11 ISO 8208 RESTART REQUEST to Mode S CLEAR REQUEST. The receipt of an ISO 8208 RESTART REQUEST from the local DCE shall result in the reformatting process generating a Mode S CLEAR REQUEST by ADLP or Mode S CLEAR REQUEST by GDLP for all SVCs associated with the requesting DTE. The fields of the Mode S CLEAR REQUEST packets shall be set as specified in 5.2.5.2.5 and 5.2.5.2.6. Note.— There are no restart states in the Mode S packet layer protocol. 5.2.5.3 PACKETS LOCAL TO THE MODE S SUBNETWORK Note.— Packets defined in this section do not result in the generation of an ISO 8208 packet. Part I Annex 10 — Aeronautical Communications I-5-27 22/11/07 5.2.5.3.1 MODE S RECEIVE READY 5.2.5.3.1.1 Packet format. The Mode S RECEIVE READY packet arriving from an XDLP is not related to the control of the DTE/DCE interface and shall not cause the generation of an ISO 8208 packet. The format of the packet shall be as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 FILL:2 SN:6 CH:4 PR:4 Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. The packet shall be processed as specified in 5.2.6.5. 5.2.5.3.1.2 Data packet type (DP). This field shall be set to 0. 5.2.5.3.1.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.3.1.4 Supervisory packet (SP). This field shall be set to 2. 5.2.5.3.1.5 Supervisory type (ST). This field shall be set to 0. 5.2.5.3.1.6 Packet receive sequence number (PR). This field shall be set as specified in 5.2.6.4.4. 5.2.5.3.2 MODE S RECEIVE NOT READY 5.2.5.3.2.1 Packet format. The Mode S RECEIVE NOT READY packet arriving from an XDLP is not related to the control of the DTE/DCE interface and shall not cause the generation of an ISO 8208 packet. The format of the packet shall be as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 FILL:2 SN:6 CH:4 PR:4 Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. The packet shall be processed as specified in 5.2.6.6. 5.2.5.3.2.2 Data packet type (DP). This field shall be set to 0. 5.2.5.3.2.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.3.2.4 Supervisory packet (SP). This field shall be set to 2. 5.2.5.3.2.5 Supervisory type (ST). This field shall be set to 1. 5.2.5.3.2.6 Packet receive sequence number (PR). This field shall be set as specified in 5.2.6.4.4. 5.2.5.3.3 MODE S ROUTE 5.2.5.3.3.1 Packet format. The format for the packet shall be as follows: DP:1 MP:1 SP:2 ST:2 OF:1 IN:1 RTL:8 RT:v ODL:0 or 8 OD:v Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1. The packet shall only be generated by the GDLP. It shall be processed by the ADLP as specified in 5.2.8.1.2 and shall have a maximum size as specified in 5.2.6.4.2.1. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-28 5.2.5.3.3.2 Data packet type (DP). This field shall be set to 0. 5.2.5.3.3.3 MSP packet type (MP). This field shall be set to 1. 5.2.5.3.3.4 Supervisory packet (SP). This field shall be set to 3. 5.2.5.3.3.5 Supervisory type (ST). This field shall be set to 0. 5.2.5.3.3.6 Option flag (OF). This field shall indicate the presence of the optional data length (ODL) and optional data (OD) fields. OF shall be set to 1 if ODL and OD are present. Otherwise it shall be set to 0. 5.2.5.3.3.7 Initialization bit (IN). This field shall indicate the requirement for subnetwork initialization. It shall be set by the GDLP as specified in 5.2.8.1.2 d). Note.— Initialization causes the clearing of any open SVCs associated with the DTE addresses contained in the ROUTE packet. This is needed to assure that all channels are closed at acquisition and for initialization following recovery after a GDLP failure. 5.2.5.3.3.8 Route table length (RTL). This field shall indicate the size of the route table, expressed in bytes. 5.2.5.3.3.9 Route table (RT) 5.2.5.3.3.9.1 Contents. This table shall consist of a variable number of entries each containing information specifying the addition or deletion of entries in the II code-DTE cross-reference table (5.2.8.1.1). 5.2.5.3.3.9.2 Entries. Each entry in the route table shall consist of the II code, a list of up to 8 ground DTE addresses, and a flag indicating whether the resulting II code-DTE pairs shall be added or deleted from the II code-DTE cross-reference table. A route table entry shall be coded as follows: II:4 AD:1 ND:3 DAL:v 5.2.5.3.3.9.3 Interrogator identifier (II). This field shall contain the 4-bit II code. 5.2.5.3.3.9.4 Add/delete flag (AD). This field shall indicate whether the II code-DTE pairs shall be added (AD = 1) or deleted (AD = 0) from the II code-DTE cross-reference table. 5.2.5.3.3.9.5 Number of DTE addresses (ND). This field shall be expressed in binary in the range from 0 to 7 and shall indicate the number of DTE addresses present in DAL minus 1 (in order to allow from 1 to 8 DTE addresses). 5.2.5.3.3.9.6 DTE address list (DAL). This list shall consist of up to 8 DTE addresses, expressed in 8-bit binary representation. 5.2.5.3.3.10 Optional data length (ODL). This field shall contain the length in bytes of the following OD field. 5.2.5.3.3.11 Optional data (OD). This variable length field shall contain optional data. 5.2.5.3.4 MODE S CLEAR CONFIRMATION BY ADLP 5.2.5.3.4.1 Packet format. The format for this packet shall be as follows: Part I Annex 10 — Aeronautical Communications I-5-29 22/11/07 DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 TC:2 SN:6 CH:4 AM:4 AG:8 Fields shown in the packet format and not specified in the following paragraphs shall be set as specified in 5.2.5.2.1 and 5.2.5.2.5. This packet shall be processed as specified in 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 MSP packet type (MP). This field shall be set to 1. 5.2.5.3.4.4 Supervisory packet (SP). This field shall be set to 1. 5.2.5.3.4.5 Channel number (CH): If a channel number 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.4.6 Temporary channel (TC): If a channel number has been allocated during the call acceptance phase, then TC shall be set to zero, otherwise it shall be set to the value used in the CALL REQUEST by GDLP. 5.2.5.3.4.7 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.5.1 Packet format. The format for this packet shall be as follows: DP:1 MP:1 SP:2 ST:2 FILL:2 TC:2 SN:6 CH:4 AM:4 AG:8 Fields shown in the packet format and not specified in the following paragraphs shall be 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 packet type (DP). This field shall be set to 0. 5.2.5.3.5.3 MSP packet 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 Channel number (CH): If a channel number 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.5.6 Temporary channel (TC): If a channel number has been allocated during the call acceptance phase, then TC shall be set to zero, otherwise it shall be set to the value used in the CALL REQUEST by GDLP. 5.2.5.3.5.7 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 as follows: DP:1 MP:1 SP:2 ST:2 FILL2:0 or 2 FILL:2 SN:6 CH:4 FILL:4 Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-30 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 MSP packet type (MP). 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.7 MODE S REJECT 5.2.5.3.7.1 Packet format. The format for this packet shall be as follows: DP:1 MP:1 SP:2 ST:2 SS:2 FILL2:0 or 2 SN:6 CH:4 PR:4 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 5.2.6.8. 5.2.5.3.7.2 Data packet type (DP). This field shall be set to 0. 5.2.5.3.7.3 MSP packet type (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 Note.— The ADCE process within the ADLP acts as a peer process to the GDCE process in the GDLP. 5.2.6.1 State transitions. The XDCE shall operate as a state machine. 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 (if 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 defined in Table 5-20 through Table 5-22 when the XDCE receives a packet from the DCE (via the reformatting 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. Part I Annex 10 — Aeronautical Communications I-5-31 22/11/07 5.2.6.2 DISPOSITION OF PACKETS 5.2.6.2.1 Upon receipt 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 to 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 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 p1 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. Procedures for handling these cases shall be as specified in Table 5-16 and Table 5-20. 5.2.6.3.3 VIRTUAL CALL CLEARING 5.2.6.3.3.1 If the XDCE receives a Mode S CALL REQUEST from the reformatting process that it cannot support, it shall initiate a Mode S CLEAR REQUEST packet that is sent to the DCE (via the reformatting process) for 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 receives a Mode S CALL REQUEST packet from the 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 of the cause field to 1 to indicate that the problem originated in the Mode S subnetwork and not in the DTE. The diagnostic and cause codes should be set as follows:

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