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

10. The receipt of a packet smaller than the maximum packet size with M-bit = 1 will cause a reset to be generated and the remainder of the sequence will be discarded. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-64 Table 5-20. DCE 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 DCE (see Notes 2 and 4) READY p1 GDLP (ADLP) CALL REQUEST p2 ADCE (GDCE) CALL REQUEST p3 DATA TRANSFER p4 GDLP (ADLP) CLEAR REQUEST p6 ADCE (GDCE) to GDLP (ADLP) CLEAR REQUEST p7 CALL REQUEST (see Note 6) A=NORMAL (5.2.6.3.1) S=p3 (forward) INVALID (see Note 5) INVALID (see Note 3) INVALID (see Note 3) INVALID (see Note 3) INVALID (see Note 3) CALL ACCEPT (see Note 4) A=DISCARD A=NORMAL S=P4 (forward) INVALID (see Note 3) INVALID (see Note 3) A=DISCARD A=DISCARD CLEAR REQUEST (see Note 4) A=DISCARD A=NORMAL (5.2.6.3.3) S=p7 (forward) A=NORMAL (5.2.6.3.3) S=p7 (forward) A=NORMAL (5.2.6.3.3) S=p7 (forward) A=DISCARD A=DISCARD DATA, INTERRUPT or RESET packets (see Note 4) A=DISCARD INVALID (see Note 3) INVALID (see Note 3) See Table 5-21 A=DISCARD A=DISCARD NOTES: 1. The XDCE is not necessarily in the same state as the DTE/DCE interface. 2. This is the DTE packet received via the DCE after all DTE/DCE processing has occurred. Procedures local to the DTE/DCE interface (such as RR, RNR, and REJECT if in effect), do not affect the XDCE directly. All error procedures as documented in ISO 8208 have been performed. Hence certain packets are rejected by the interface and are not represented in this table. 3. The DCE in its protocol operation with the DTE will detect this error condition, hence the erroneous packet can be said never to “reach” the XDCE; see also Note 2. 4. The channel number for the DTE/DCE need not be the same channel number used for the ADCE/GDCE; a packet from the DTE which contains a channel number is associated with an air/ground channel by means of a previously established cross-reference table. If none exists then the DTE/DCE channel by definition references an air/ground channel in the p1 state. 5. The ADCE assigns all channel numbers used between the ADLP and GDLP; hence call collisions (denoted p5 ISO 8208) are not possible; see also Note 4. 6. A CALL REQUEST from the DTE can never be associated with an XDCE channel number which is not in the p1 state. 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. Part I Annex 10 — Aeronautical Communications I-5-65 22/11/07 Table 5-21. DCE effect on ADCE (GDCE) reset states ADCE (GDCE) reset states (see Notes 1, 4 and 5) Packet received from DCE FLOW CONTROL READY d1 GDLP (ADLP) RESET REQUEST d2 ADCE (GDCE) RESET REQUEST to GDLP (ADLP) d3 RESET REQUEST A=NORMAL (5.2.6.7) S=d3 (forward) A=NORMAL (5.2.6.7) S=d1 (forward) A=DISCARD RESET CONFIRMATION INVALID (see Note 3) INVALID (see Note 3) INVALID (see Note 3) INTERRUPT See Table 5-22 A=DISCARD Hold interrupt until Mode S reset complete INTERRUPT CONFIRMATION See Table 5-22 A=DISCARD INVALID (see Note 3) DATA (see Note 2) A=NORMAL (5.2.6.4) (forward) A=DISCARD Hold data until Mode S reset complete NOTES: 1. The XDCE is not necessarily in the same state as the DTE/DCE interface. 2. This is the DTE packet received via the DCE after all DTE/DCE processing has occurred. Procedures local to the DTE/DCE interface (such as RR, RNR, and REJECT if in effect), do not affect the XDCE directly. All error procedures as documented in ISO 8208 have been performed. Hence certain packets are rejected by the interface and are not represented in this table. 3. The DCE in its protocol operation with the DTE will detect this error condition, hence the erroneous packet can be said never to “reach” the XDCE; see also Note 2. 4. 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. 5. 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. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-66 Table 5-22. DCE effect on ADCE (GDCE) interrupt transfer states ADCE (GDCE) interrupt transfer state (see Notes 1, 4 and 5) Packet received from DCE (see Note 2) GDLP (ADLP) INTERRUPT READY i1 GDLP (ADLP) INTERRUPT SENT i2 INTERRUPT CONFIRMATION INVALID (See Note 3) A=NORMAL (5.2.6.4.5) S=i1 (forward) ADCE (GDCE) interrupt transfer states (see Notes 1, 4 and 5) Packet received from DCE (see Note 2) ADCE (GDCE) INTERRUPT READY j1 ADCE (GDCE) INTERRUPT SENT j2 INTERRUPT A=NORMAL (5.2.6.4.5) S=j2 (forward) INVALID (see Note 3) NOTES: 1. The XDCE is not necessarily in the same state as the DTE/DCE interface. 2. This is the DTE packet received via the DCE after all DTE/DCE processing has occurred. Procedures local to the DTE/DCE interface (such as RR, RNR, and REJECT if in effect), do not affect the XDCE directly. All error procedures as documented in ISO 8208 have been performed. Hence certain packets are rejected by the interface and are not represented in this state. 3. The DCE in its protocol operation with the DTE will detect this error condition, hence the erroneous packet can be said never to “reach” the XDCE; see also Note 2. 4. 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. 5. 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. Part I Annex 10 — Aeronautical Communications I-5-67 22/11/07 Table 5-23. Broadcast identifier number assignments Uplink broadcast identifier Assignment Others Not valid Reserved (differential GNSS correction) Not valid Reserved for ACAS (RA broadcast) Reserved for ACAS (ACAS broadcast) Unassigned Downlink broadcast identifier Assignment FE16 FF16 Others Not valid Reserved (traffic information service) Data link capability report Aircraft identification Update request Search request Unassigned Table 5-24. Register number assignments Transponder register No. Assignment Not valid Unassigned Linked Comm-B, segment 2 Linked Comm-B, segment 3 Linked Comm-B, segment 4 Extended squitter airborne position Extended squitter surface position Extended squitter status Extended squitter identification and type Extended squitter airborne velocity 0A16 Extended squitter event-driven information 0B16 Air/air information 1 (aircraft state) 0C16 Air/air information 2 (aircraft intent) 0D16-0E16 Reserved for air/air state information 0F16 Reserved for ACAS Data link capability report 1116-1616 Reserved for extension to data link capability reports Common usage GICB capability report 1816-1F16 Mode S specific services capability reports Aircraft identification Aircraft and airline registration markings Antenna positions Reserved for antenna position Reserved for aircraft parameters Aircraft type 2616-2F16 Unassigned ACAS active resolution advisory 3116-3F16 Unassigned Selected vertical intention Next waypoint identifier Next waypoint position Next waypoint information Meteorological routine air report Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-68 Transponder register No. Assignment Meteorological hazard report Reserved for flight management system Mode 1 Reserved for flight management system Mode 2 VHF channel report 4916-4F16 Unassigned Track and turn report Position report coarse Position report fine Air-referenced state vector Waypoint 1 Waypoint 2 Waypoint 3 5716-5E16 Unassigned 5F16 Quasi-static parameter monitoring Heading and speed report Extended squitter emergency/priority status Reserved for target state and status information Reserved for extended squitter Reserved for extended squitter Aircraft operational status 6616-6F16 Reserved for extended squitter 7016-7516 Reserved for future aircraft downlink parameters 7616-E016 Unassigned E116-E216 Reserved for Mode S BITE E316 Transponder type/part number E416 Transponder software revision number E516 ACAS unit part number E616 ACAS unit software revision number E716-F016 Unassigned F116 Military applications F216 Military applications F316-FF16 Unassigned Note.— In the context of Table 5-24, the term “aircraft” can be understood as “transponder carrying aircraft”, “pseudo-aircraft (e.g. an obstacle)” or “vehicle”. Part I Annex 10 — Aeronautical Communications I-5-69 22/11/07 Table 5-25. MSP channel number assignments Uplink channel number Assignment 8–63 Not valid Reserved (specific services management) Reserved (traffic information service) Reserved (ground-to-air alert) Reserved (ground derived position) ACAS sensitivity level control Reserved (ground-to-air service request) Reserved (air-to-ground service response) Unassigned Downlink channel number Assignment 8–63 Not valid Reserved (specific services management) Unassigned Reserved (data flash) Reserved (position request) Unassigned Reserved (ground-to-air service response) Reserved (air-to-ground service request) Unassigned Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-70 FIGURES FOR CHAPTER 5 For DI = 1 TMS IIS MBS MES LOS RSS SPARE LAS For DI = 7 TMS IIS RRS SPARE LOS SPARE SPARE LAS Figure 5-1. The SD field structure Figure 5-2. DCE substate hierarchy Note.— States 1, 4 and 1 (shown circled) are states that provide access to the lower levels of the DCE substate hierarchy. r p d Interrupt and control states Data transfer states Call setup and clearing states Ready and restart states r1 r2 r3 p1 p2 p3 p4 p5 p6 p7 d1 d2 d3 f 2 f 1 g1 g2 i1 i2 j1 j2 Part I Annex 10 — Aeronautical Communications I-5-71 22/11/07 4 5 6 7 DP=0 MP=1 SP=1 ST=0 FILL2 P FILL SN CH LAM AG S FS F LV UD Figure 5-3. CALL REQUEST by ADLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=0 FILL P FILL SN FILL TC AM AG S FS F LV UD Figure 5-4. CALL REQUEST by GDLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=1 FILL2 TC SN CH AM AG S FILL F LV UD Figure 5-5. CALL ACCEPT by ADLP packet Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-72 4 5 6 7 DP=0 MP=1 SP=1 ST=1 FILL FILL SN CH AM AG S FILL F LV UD Figure 5-6. CALL ACCEPT by GDLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=2 FILL2 TC SN CH AM AG CC DC S FILL F LV UD Figure 5-7. CLEAR REQUEST by ADLP packet Part I Annex 10 — Aeronautical Communications I-5-73 22/11/07 4 5 6 7 DP=0 MP=1 SP=1 ST=2 FILL TC SN CH AM AG CC DC S FILL F LV UD Figure 5-8. CLEAR REQUEST by GDLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=3 FILL2 TC SN CH AM AG Figure 5-9. CLEAR CONFIRMATION by ADLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=3 FILL TC SN CH AM AG Figure 5-10. CLEAR CONFIRMATION by GDLP packet Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-74 4 5 6 7 DP=1 M SN FILL1 PS PR CH LV UD Figure 5-11. DATA packet 4 5 6 7 DP=0 MP=1 SP=3 ST=1 FILL2 S F SN CH LV UD Figure 5-12. INTERRUPT packet 4 5 6 7 DP=0 MP=1 SP=3 ST=3 SS=0 FILL2 SN CH FILL Figure 5-13. INTERRUPT CONFIRMATION packet 4 5 6 7 DP=0 MP=1 SP=3 ST=3 SS=1 FILL2 SN CH PR Figure 5-14. REJECT packet Part I Annex 10 — Aeronautical Communications I-5-75 22/11/07 4 5 6 7 DP=0 MP=1 SP=2 ST=0 FILL2 FILL SN CH PR Figure 5-15. RECEIVE READY packet 4 5 6 7 DP=0 MP=1 SP=2 ST=1 FILL2 FILL SN CH PR Figure 5-16. RECEIVE NOT READY packet 4 5 6 7 DP=0 MP=1 SP=2 ST=2 FILL2 FILL SN CH FILL RC DC Figure 5-17. RESET REQUEST packet 4 5 6 7 DP=0 MP=1 SP=2 ST=3 FILL2 FILL SN CH FILL Figure 5-18. RESET CONFIRMATION packet Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-76 4 5 6 7 DP=0 MP=1 SP=3 ST=0 OF IN RTL RT ODL OD Figure 5-19. ROUTE packet 4 5 6 7 DP=0 MP=1 SP=3 ST=2 FILL2 LENGTH FIRST PACKET LENGTH LAST PACKET LENGTH = 0 Figure 5-20. MULTIPLEX packet Part I Annex 10 — Aeronautical Communications I-5-77 22/11/07 4 5 6 7 DP=0 MP=0 M/CH FILL1 UD Figure 5-21. SHORT FORM MSP packet 4 5 6 7 DP=0 MP=1 SP=0 L M/SN FILL2 M/CH UD Figure 5-22. LONG FORM MSP packet Annex 10 — Aeronautical Communications Volume III 22/11/07 I-5-78 DP[1] • DATA PACKET MP[1] • SHORT MSP SP[2] • LONG MSP ST[2] • CALL REQUEST • CALL ACCEPT • CLEAR REQUEST • CLEAR CONFIRMATION ST[2] • RECEIVE READY • RECEIVE NOT READY • RESET REQUEST • RESET CONFIRMATION ST[2] • ROUTE • INTERRUPT • MULTIPLEX SS[2] • INTERRUPT CONFIRMATION • REJECT • UNASSIGNED • UNASSIGNED LEGEND: DP = DATA packet type MP = MSP packet type SP = SUPERVISORY packet ST = SUPERVISORY type SS = SUPERVISORY subset Figure 5-23. Control fields used in MODE S packets ___________________ ANNEX 10 — VOLUME III I-6-1 22/11/07 CHAPTER 6. VHF AIR-GROUND DIGITAL LINK (VDL) 6.1 DEFINITIONS AND SYSTEM CAPABILITIES Note 1.— The very high frequency (VHF) digital link (VDL) Mode 2 and the VDL Mode 4 provide data service capabilities. The VDL Mode 3 provides both voice and data service capabilities. The data capability is a constituent mobile subnetwork of the aeronautical telecommunication network (ATN). In addition, the VDL may provide non-ATN functions. Standards and Recommended Practices (SARPs) for the VDL are defined and referenced below. Note 2.— Additional information on VDL is contained in the Manuals on VHF VDL Mode 2, VDL Mode 3 and VDL Mode 4 Technical Specifications (Docs 9776, 9805 and 9816). Note 3.— Sections 6.1.2 to 6.8.2 contain Standards and Recommended Practices for VDL Modes 2 and 3. Section 6.9 contains Standards and Recommended Practices for VDL Mode 4. 6.1.1 Definitions Automatic dependent surveillance-broadcast (ADS-B). A means by which aircraft, aerodrome vehicles and other objects can automatically transmit and/or receive data such as identification, position and additional data, as appropriate, in a broadcast mode via a data link. Broadcast. A transmission of information relating to air navigation that is not addressed to a specific station or stations. Burst. A time-defined, contiguous set of one or more related signal units which may convey user information and protocols, signalling, and any necessary preamble. Current slot. The slot in which a received transmission begins. Data circuit-terminating equipment (DCE). A DCE is a network provider equipment used to facilitate communications between DTEs. Data link entity (DLE). A protocol state machine capable of setting up and managing a single data link connection. Data link service (DLS) sublayer. The sublayer that resides above the MAC sublayer. For VDL Mode 4, the DLS sublayer resides above the VSS sublayer. The DLS manages the transmit queue, creates and destroys DLEs for connectionoriented communications, provides facilities for the LME to manage the DLS, and provides facilities for connectionless communications. Data terminal equipment (DTE). A DTE is an endpoint of a subnetwork connection. Extended Golay Code. An error correction code capable of correcting multiple bit errors. Frame. The link layer frame is composed of a sequence of address, control, FCS and information fields. For VDL Mode 2, these fields are bracketed by opening and closing flag sequences, and a frame may or may not include a variable-length information field. Annex 10 — Aeronautical Communications Volume III 22/11/07 I-6-2 Gaussian filtered frequency shift keying (GFSK). A continuous-phase, frequency shift keying technique using two tones and a Gaussian pulse shape filter. Global signalling channel (GSC). A channel available on a worldwide basis which provides for communication control. Link. A link connects an aircraft DLE and a ground DLE and is uniquely specified by the combination of aircraft DLS address and the ground DLS address. A different subnetwork entity resides above every link endpoint. Link layer. The layer that lies immediately above the physical layer in the Open Systems Interconnection protocol model. The link layer provides for the reliable transfer of information across the physical media. It is subdivided into the data link sublayer and the media access control sublayer. Link management entity (LME). A protocol state machine capable of acquiring, establishing and maintaining a connection to a single peer system. An LME establishes data link and subnetwork connections, “hands-off” those connections, and manages the media access control sublayer and physical layer. An aircraft LME tracks how well it can communicate with the ground stations of a single ground system. An aircraft VME instantiates an LME for each ground station that it monitors. Similarly, the ground VME instantiates an LME for each aircraft that it monitors. An LME is deleted when communication with the peer system is no longer viable. M burst. A management channel data block of bits used in VDL Mode 3. This burst contains signalling information needed for media access and link status monitoring. Media access control (MAC). The sublayer that acquires the data path and controls the movement of bits over the data path. Mode 2. A data-only VDL mode that uses D8PSK modulation and a carrier sense multiple access (CSMA) control scheme. Mode 3. A voice and data VDL mode that uses D8PSK modulation and a TDMA media access control scheme. Mode 4. A data-only VDL mode using a GFSK modulation scheme and self-organizing time division multiple access (STDMA). Physical layer. The lowest level layer in the Open Systems Interconnection protocol model. The physical layer is concerned with the transmission of binary information over the physical medium (e.g. VHF radio). Quality of service. The information relating to data transfer characteristics used by various communication protocols to achieve various levels of performance for network users. Reed-Solomon code. An error correction code capable of correcting symbol errors. Since symbol errors are collections of bits, these codes provide good burst error correction capabilities. Self-organizing time division multiple access (STDMA). A multiple access scheme based on time-shared use of a radio frequency (RF) channel employing: (1) discrete contiguous time slots as the fundamental shared resource; and (2) a set of operating protocols that allows users to mediate access to these time slots without reliance on a master control station. Slot. One of a series of consecutive time intervals of equal duration. Each burst transmission starts at the beginning of a slot. Subnetwork connection. A long-term association between an aircraft DTE and a ground DTE using successive virtual calls to maintain context across link handoff. Subnetwork dependent convergence function (SNDCF). A function that matches the characteristics and services of a particular subnetwork to those characteristics and services required by the internetwork facility. Subnetwork entity. In this document, the phrase “ground DCE” will be used for the subnetwork entity in a ground station communicating with an aircraft; the phrase “ground DTE” will be used for the subnetwork entity in a ground router Part I Annex 10 — Aeronautical Communications I-6-3 22/11/07 communicating with an aircraft station; and, the phrase “aircraft DTE” will be used for the subnetwork entity in an aircraft communicating with the station. A subnetwork entity is a packet layer entity as defined in ISO 8208. Subnetwork layer. The layer that establishes, manages and terminates connections across a subnetwork. System. A VDL-capable entity. A system comprises one or more stations and the associated VDL management entity. A system may either be an aircraft system or a ground system. Time division multiple access (TDMA). A multiple access scheme based on time-shared use of an RF channel employing:

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