Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 4421

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. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-52 28/11/02 No. 77 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 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-53 28/11/02 No. 77 Table 5-24. Register number assignments Register Number 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 (other air-air information) 0F16 Reserved (ACAS) Data link capability report 1116-1616 Extension to data link capability report Common usage GICB capability report 1816-1F16 Mode S specific services capability reports Aircraft identification Aircraft registration number Antenna positions Reserved (antenna position) Reserved (static aircraft parameter) Aircraft type 2616-2F16 Unassigned ACAS active resolution advisory (RA) 3116-3F16 Unassigned Aircraft intention Next waypoint identifier Next waypoint position Next waypoint information Meteorological routine air report Meteorological hazard report Flight management system Mode 1 Flight management system Mode 2 VHF channel report 4916-4F16 Unassigned Track and turn report Position report coarse 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-54 28/11/02 No. 77 Table 5-25. MSP channel number assignments 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 Current trajectory change point Next trajectory change point Aircraft operational coordination message Aircraft operational status 6616-6F16 Reserved for extended squitter 7016-7516 Reserved for future downlink parameters 7616-E016 Unassigned E116-E216 Reserved for Mode S byte E316-F016 Unassigned F116-F216 Military applications F316-FF16 Unassigned 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 Register Number Assignment 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-55 28/11/02 No. 77 FIGURES FOR CHAPTER 5 Figure 5-1. The SD field structure Figure 5-2. DCE substate hierarchy For DI = 1 TMS IIS MBS MES LOS RSS SPARE LAS For DI = 7 TMS IIS RRS SPARE LOS SPARE SPARE LAS Note.— States r1, p4 and d1 (shown circled) are states that provide access to the lower levels of the DCE substate hierarchy. 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 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-56 28/11/02 No. 77 Figure 5-3. CALL REQUEST by ADLP packet Figure 5-4. CALL REQUEST by GDLP packet Figure 5-5. CALL ACCEPT by ADLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=0 FILL2 P FILL SN CH LAM AG S FS F LV UD 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 4 5 6 7 DP=0 MP=1 SP=1 ST=1 FILL2 TC SN CH AM AG S FILL F LV UD 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-57 28/11/02 No. 77 Figure 5-6. CALL ACCEPT by GDLP packet Figure 5-7. CLEAR REQUEST by ADLP packet Figure 5-8. CLEAR REQUEST by GDLP packet 4 5 6 7 DP=0 MP=1 SP=1 ST=1 FILL FILL SN CH AM AG S FILL F LV UD 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 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 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-58 28/11/02 No. 77 Figure 5-9. CLEAR CONFIRMATION by ADLP packet Figure 5-10. CLEAR CONFIRMATION by GDLP packet Figure 5-11. DATA packet Figure 5-12. INTERRUPT packet 4 5 6 7 DP=0 MP=1 SP=1 ST=3 FILL2 TC SN CH AM AG 4 5 6 7 DP=0 MP=1 SP=1 ST=3 FILL TC SN CH AM AG 4 5 6 7 DP=1 M SN FILL1 PS PR CH LV UD 4 5 6 7 DP=0 MP=1 SP=3 ST=1 FILL2 S F SN CH LV UD 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-59 28/11/02 No. 77 Figure 5-13. INTERRUPT CONFIRMATION packet Figure 5-14. REJECT packet Figure 5-15. RECEIVE READY packet Figure 5-16. RECEIVE NOT READY packet Figure 5-17. RESET REQUEST packet 4 5 6 7 DP=0 MP=1 SP=3 ST=3 SS=0 FILL2 SN CH FILL 4 5 6 7 DP=0 MP=1 SP=3 ST=3 SS=1 FILL2 SN CH PR 4 5 6 7 DP=0 MP=1 SP=2 ST=0 FILL2 FILL SN CH PR 4 5 6 7 DP=0 MP=1 SP=2 ST=1 FILL2 FILL SN CH PR 4 5 6 7 DP=0 MP=1 SP=2 ST=2 FILL2 FILL SN CH FILL RC DC 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-60 28/11/02 No. 77 Figure 5-18. RESET CONFIRMATION packet Figure 5-19. ROUTE packet Figure 5-20. MULTIPLEX packet 4 5 6 7 DP=0 MP=1 SP=2 ST=3 FILL2 FILL SN CH FILL 4 5 6 7 DP=0 MP=1 SP=3 ST=0 OF IN RTL RT ODL OD 4 5 6 7 DP=0 MP=1 SP=3 ST=2 FILL2 LENGTH FIRST PACKET LENGTH LAST PACKET LENGTH = 0 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-61 28/11/02 No. 77 Figure 5-21. SHORT FORM MSP packet Figure 5-22. LONG FORM MSP packet 4 5 6 7 DP=0 MP=0 M/CH FILL1 UD 4 5 6 7 DP=0 MP=1 SP=0 L M/SN FILL2 M/CH UD 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-62 28/11/02 No. 77 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 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 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-63 28/11/02 No. 77 APPENDIX TO CHAPTER 5. DATA FORMATS AND CONTROL PARAMETERS FOR COMMUNICATIONS VIA MODE S SPECIFIC SERVICES TECHNICAL SUPPORT FOR SSR MODE S AIR-GROUND DATA LINK This appendix defines data formats and control parameters that shall be used for communications using Mode S specific services. Appendix 1 is arranged in the following manner: Section 1 List of acronyms Section 2 Data formats for transponder registers Section 3 Formats for Mode S specific protocols (MSP) Section 4 Mode S broadcast protocols Note.— Guidance material on possible data sources, the use of control parameters, and the protocols involved is given in the Manual on Mode S Specific Services (Doc 9688). 1. LIST OF ACRONYMS ACAS Airborne collision avoidance system ADLP Airborne data link processor ADS-B Automatic dependent surveillance-broadcast ATN Aeronautical telecommunication network ATS Air traffic service A/V Aircraft/vehicle BDS Comm-B data selector CPR Compact position reporting ELM Extended length message GDLP Ground data link processor GICB Ground-initiated Comm-B GFM General formatter/manager GNSS Global navigation satellite system II Interrogator identifier MA Message, Comm-A MB Message, Comm-B MC Message, Comm-C MD Message, Comm-D MSP Mode S specific protocol NUCP Navigational uncertainty category — position NUCR Navigational uncertainty category — rate RNP Required navigation performance SI Surveillance identifier SLM Standard length message SPI Special position identification SSR Secondary surveillance radar TIS Traffic information service UTC Coordinated universal time 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-64 28/11/02 No. 77 2. DATA FORMATS FOR TRANSPONDER REGISTERS 2.1 REGISTER ALLOCATION Applications shall use the allocated register numbers as shown in the table below: Register No. Assignment Minimum update rate Not valid N/A Unassigned N/A Linked Comm-B, segment 2 N/A Linked Comm-B, segment 3 N/A Linked Comm-B, segment 4 N/A Extended squitter airborne position 0.2 s Extended squitter surface position 0.2 s Extended squitter status 1.0 s Extended squitter identification and type 15.0 s Extended squitter airborne velocity 0.2 s 0A16 Extended squitter event-driven information variable 0B16 Air/air information 1 (aircraft state) 1.0 s 0C16 Air/air information 2 (aircraft intent) 1.0 s 0D16-0E16 Reserved for air/air state information To be determined 0F16 Reserved for ACAS To be determined Data link capability report <4.0 s (see 2.1.3) 1116-1616 Reserved for extension to data link capability reports 5.0 s Common usage GICB capability report 5.0 s 1816-1F16 Mode S specific services capability reports 5.0 s Aircraft identification 5.0 s Aircraft and airline registration markings 15.0 s Antenna positions 15.0 s Reserved for antenna position 15.0 s Reserved for aircraft parameters 15.0 s Aircraft type 15.0 s 2616-2F16 Unassigned N/A ACAS active resolution advisory see ACAS SARPs (4.3.8.4.2.2) 3116-3F16 Unassigned N/A Aircraft intention 1.0 s Next waypoint identifier 1.0 s Next waypoint position 1.0 s 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-65 28/11/02 No. 77 2.1.1 The details of the data to be entered into the assigned registers shall be as defined in the following pages of this section. The above table specifies the minimum update rates at which the appropriate transponder register(s) shall be reloaded with valid data. If the defined update rate is not maintained, the status bit (if provided) shall indicate that the data in that field are invalid. 2.1.2 The time between the availability of the data at the SSE and the time that the data are processed and appear in the relevant transponder register shall be less than the minimum update rate specified in the table above. 2.1.3 Recommendation.—The time between the availability of data at the SSE and the time that the data are processed and appears in the relevant transponder register should be as short as possible. Next waypoint information 0.5 s Meteorological routine air report 1.0 s Meteorological hazard report 1.0 s Reserved for flight management system Mode 1 To be determined Reserved for flight management system Mode 2 To be determined VHF channel report 5.0 s 4916-4F16 Unassigned N/A Track and turn report 1.0 s Position report coarse 0.5 s Position report fine 0.5 s Air-referenced state vector 0.5 s Waypoint 1 5.0 s Waypoint 2 5.0 s Waypoint 3 5.0 s 5716-5E16 Unassigned N/A 5F16 Quasi-static parameter monitoring 0.5 s Heading and speed report 1.0 s Extended squitter emergency/priority status 1.0 s Current trajectory change point 1.7 s Next trajectory change point 1.7 s Aircraft operational coordination message 2.0 s or 5.0 s (2.3.10.1) Aircraft operational status 1.7 s 6616-6F16 Reserved for extended squitter N/A 7016-7516 Reserved for future aircraft downlink parameters N/A 7616-E016 Unassigned N/A E116-E216 Reserved for Mode S byte N/A E316-F016 Unassigned N/A F116-F216 Military applications 15 s F316-FF16 Unassigned N/A Register No. Assignment Minimum update rate 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-66 28/11/02 No. 77 2.1.4 The register number shall be equivalent to the Comm-B data selector (BDS) value used to address that register, (see 3.1.2.6.11.2.1 of Annex 10, Volume IV). Register 0A16 shall not be used for GICB or ACAS cross-link read-out. The data link capability report (register number 1016) shall be updated within one second of the data changing and at least every four seconds thereafter. 2.2 GENERAL CONVENTIONS ON DATA FORMATS 2.2.1 VALIDITY OF DATA The bit patterns contained in the 56-bit transponder registers shall be considered as valid application data only if: 1) the data link capability report is contained in register number 1016. This is indicated by bit 25 of the data link capability report contained in register number 1016 being set to “ONE”. 2) the GICB service corresponding to the application is shown as “supported” by the corresponding bit in the GICB capability report register numbers 1716 to 1C16 being set to “ONE”. Note 1.— The intent of the capability bits in register number 1716 is to indicate that useful data are contained in the corresponding transponder register. For this reason, each bit for a register is cleared if data becomes unavailable (2.5.4.1) and set again when data insertion into the register resumes. Note 2.— A bit set in register numbers 1816 to 1C16 indicates that the application using this register has been installed on the aircraft. These bits are not cleared to reflect the real-time loss of an application, as is done for register number 1716 (2.5.4.2). 3) the data value is valid at the time of extraction. This is indicated by a data field status bit (if provided). When this status bit is set to “ONE”, the data field(s) which follow, up to the next status bit, are valid. When this status bit is set to “ZERO”, the data field(s) are invalid. 2.2.2 REPRESENTATION OF NUMERICAL DATA Numerical data shall be represented as follows: 1) Numerical data shall be represented as binary numerals. When the value is signed, 2’s complement representation shall be used, and the bit following the status bit shall be the sign bit. 2) Unless otherwise specified, whenever more bits of resolution are available from the data source than in the data field into which that data are to be loaded, the data shall be rounded to the nearest value that can be encoded in that data field. 3) In all cases where a status bit is used it shall be set to “ONE” to indicate VALID and to “ZERO” to indicate INVALID. Note.— This facilitates partial loading of the registers. 4) When present, a switch bit shall indicate which of two alternative data types is being used to update the parameter in the transponder register. 5) Bit numbering in the MB field shall be as specified in Annex 10, Volume IV (3.1.2.3.1.3). 6) Registers containing data intended for broadcast Comm-B shall have the broadcast identifier located in the eight most significant bits of the MB field. Note.— Tables are numbered Table 2-X where “X” is the decimal equivalent of the BDS code to which the format applies. 2.2.3 RESERVED FIELDS Unless specified in this Annex, these bit fields shall be reserved for future allocation by ICAO. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-67 28/11/02 No. 77 2.3 EXTENDED SQUITTER FORMATS This section defines the formats and coding that shall be used for extended squitter ADS-B messages. When the extended squitter capability is implemented as an extended squitter/non-transponder device (ES/NT, Annex 10, Volume IV, 3.1.2.8.7), the convention for register numbering shall not apply. The data content and the transmit times shall be the same as specified for the transponder case. 2.3.1 FORMAT TYPE CODES The format type code shall differentiate the Mode S extended squitter messages into several classes as specified in the following table: “TYPE” Subfield Code Definitions (DF = 17 or 18) Type code Format Horizontal protection limit, (HPL) 95% Containment radius, µ and v, on horizontal and vertical position error Altitude type (2.3.2.4) NUC_P No position information Baro altitude or no altitude information Identification (Category Set D) Not applicable Identification (Category Set C) Not applicable Identification (Category Set B) Not applicable Identification (Category Set A) Not applicable Surface position HPL < 7.5 m µ < 3 m No altitude information Surface position HPL < 25 m 3 m < µ < 10 m No altitude information Surface position HPL < 185.2 m (0.1 NM) 10 m < µ < 92.6 m (0.05 NM) No altitude information Surface position HPL > 185.2 m (0.1 NM) (0.05 NM) 92.6 m < µ No altitude information Airborne position HPL < 7.5 m µ < 3 m Baro altitude Airborne position 7.5 m < HPL < 25 m 3 m < µ < 10 m Baro altitude Airborne position 25 m < HPL < 185.2 m (0.1 NM) 10 m < µ < 92.6 m (0.05 NM) Baro altitude Airborne position 185.2 m (0.1 NM) < HPL < 370.4 m (0.2 NM) 92.6 m (0.05 NM) < µ < 185.2 m (0.1 NM) Baro altitude Airborne position 380.4 m (0.2 NM) < HPL < 92.6 m (0.5 NM) 185.2 m (0.1 NM) < µ < 463 m (0.25 NM) Baro altitude Airborne position 26 m (0.5 NM) < HPL < 185.2 m (1.0 NM) 463 m (0.25 NM) < µ < 92.6 m (0.5 NM) Baro altitude Airborne position 185.2 m (1.0 NM) < HPL < 370.4 m (2.0 NM) 92.6 m (0.5 NM) < µ < 185.2 km (1.0 NM) Baro altitude Airborne position 7.704 km (2.0 NM) < HPL < 18.52 km (10 NM) 1.852 km (1.0 NM) < µ < 9.26 km (5.0 NM) Baro altitude Airborne position 18.52 km (10 NM) < HPL < 37.04 km (20 NM) 9.26 km (5.0 NM) < µ < 18.52 km (10.0 NM) Baro altitude Airborne position HPL > 37.04 km (20 NM) 8.52 km (10.0 NM) < µ Baro altitude Airborne velocity Not applicable Not applicable Difference between “Baro altitude” and “GNSS height (HAE) or GNSS altitude (MSL)” (2.3.5.7) N/A Airborne position HPL < 7.5 m µ < 3 m and v < 4 m GNSS height (HAE) Airborne position HPL < 25 m µ < 10 m and v < 15 m GNSS height (HAE) 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-68 28/11/02 No. 77 The 95 per cent containment limit, µ, on horizontal position error shall be derived from, HFOM (horizontal figure of merit). Likewise, the 95 per cent containment limit, v, on vertical position error shall be derived from, VFOM (vertical figure of merit). The horizontal protection level (HPL) shall be derived from AHIL (autonomous horizontal integrity limit). Note.— The term “broadcast” when applied to extended squitter, refers to a spontaneous transmission by the transponder. This is distinct from the Comm-B broadcast protocol. 2.3.2 AIRBORNE POSITION FORMAT The airborne position squitter format shall be formatted as specified in the definition of BDS 0,5. Additional details are specified in the following paragraphs. 2.3.2.1 COMPACT POSITION REPORTING (CPR) FORMAT (F) In order to achieve coding that is unambiguous worldwide, CPR shall use two format types, known as even and odd. This 1-bit field (bit 22) shall be used to define the CPR format type. F = 0 shall denote an even format coding, while F = 1 shall denote an odd format coding (2.6.7). 2.3.2.2 TIME SYNCHRONIZATION (T) This 1-bit field (bit 21) shall indicate whether or not the time of applicability of the message is synchronized with UTC time. T = 0 shall denote that the time is not synchronized to UTC. T = 1 shall denote that the time of applicability is synchronized to UTC time. Synchronization shall only be used for airborne position messages having the top two horizontal position precision categories (format types codes 9, 10, 20 and 21). When T = 1, the time of validity in the airborne position message format shall be encoded in the 1-bit F field which, in addition to CPR format type, indicates the 0.2 second time tick for UTC time of position validity. The F bit shall alternate between 0 and 1 for successive 0.2 second time ticks, beginning with F = 0 when the time of applicability is an exact even-numbered UTC second. 2.3.2.3 LATITUDE/LONGITUDE The latitude/longitude field in the airborne position message shall be a 34-bit field containing the latitude and longitude of the aircraft airborne position. The latitude and longitude shall each occupy 17 bits. The airborne latitude and longitude encodings shall contain the high-order 17 bits of the 19-bit CPR-encoded values defined in 2.6. Note.— The unambiguous range for the local decoding of airborne messages is 666 km (360 NM). The positional accuracy maintained by the airborne CPR encoding is approximately 5.1 metres. The latitude/longitude encoding is also a function of the CPR format value (the “F” bit) described above. Airborne position HPL > 25 m µ > 10 m or v > 15 m GNSS height (HAE) Reserved Reserved for test purposes Reserved for surface system status 25 - 27 Reserved Extended squitter aircraft status Current/next trajectory change point Aircraft operational coordination Aircraft operational status “TYPE” Subfield Code Definitions (DF = 17 or 18) Type code Format Horizontal protection limit, (HPL) 95% Containment radius, µ and v, on horizontal and vertical position error Altitude type (2.3.2.4) NUC_P 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-69 28/11/02 No. 77 2.3.2.3.1 Extrapolating position (when T = 1) If T is set to one, airborne position messages with format type codes 9, 10, 20 and 21 shall have times of applicability which are exact 0.2 s UTC epochs. In that case, the F bit shall be 0 if the time of applicability is an even-numbered 0.2 s UTC epoch, or 1 if the time of applicability is an odd-numbered 0.2 s UTC epoch. Note.— In such a case, an “even-numbered 0.2 s epoch” means an epoch which occurs an even number of 200-ms time intervals after an even-numbered UTC second. An “odd-numbered 0.2 s epoch” means an epoch which occurs an odd number of 200-ms time intervals after an even-numbered UTC second. Examples of even-numbered 0.2 s UTC epochs are 12.0 s, 12.4 s, 12.8 s, 13.2 s, 13.6 s, etc. Examples of odd-numbered UTC epochs are 12.2 s, 12.6 s, 13.0 s, 13.4 s, 13.8 s, etc. The CPR-encoded latitude and longitude that are loaded into the airborne position register shall comprise an estimate of the aircraft/vehicle (A/V) position at the time of applicability of that latitude and longitude, which is an exact 0.2 s UTC epoch. The register shall be loaded no earlier than 150 ms before the time of applicability of the data being loaded, and no later than 50 ms before the time of applicability of that data. This timing shall ensure that the receiving ADS-B system may recover the time of applicability of the data in the airborne position message, as follows: 1) If F = 0, the time of applicability shall be the nearest even-numbered 0.2 s UTC epoch to the time that the airborne position message is received. 2) If F = 1, the time of applicability shall be the nearest odd-numbered 0.2 s UTC epoch to the time that the airborne position message is received. Recommendation.— If the airborne position register is updated at its minimum (every 200 ms), that register should be loaded 100 ms before the time of applicability. The register should then be reloaded, with data applicable at the next subsequent 0.2 s UTC epoch, 100 ms before that next subsequent 0.2 s epoch. Note 1.— In this way, the time of transmission of an airborne position message would never differ by more than 100 ms from the time of applicability of the data in that message. By specifying “100 ms ± 50 ms” rather than 100 ms exactly, some tolerance is allowed for variations in implementation. Note 2.— The position may be estimated by extrapolating the position from the time of validity of the fix (included in the position fix) to the time of applicability of the data in the register (which, if T = 1, is an exact 0.2 s UTC time tick). This may be done by a simple linear extrapolation using the velocity provided with the position fix and the time difference between the position fix validity time and the time of applicability of the transmitted data. Alternatively, other methods of estimating the position, such as alpha-beta trackers or Kalman filters, may be used. Every 200 ms, the contents of the position registers shall be updated by estimating the A/V position at the next subsequent 0.2 s UTC epoch. This process shall continue with new position fixes as they become available from the source of navigation data. 2.3.2.3.2 Extrapolating position (when T = 0) T shall be set to zero if the time of applicability of the data being loaded into the position register is not synchronized to any particular UTC epoch. In that case, the position register shall be reloaded with position data at intervals that are no more than 200 ms apart. The position being loaded into the register shall have a time of applicability that is never more than 200 ms different from any time during which the register holds that data. Note.— This may be accomplished by loading the airborne position register at intervals that are, on average, no more than 200 ms apart, with data for which the time of applicability is between the time the register is loaded and the time that it is loaded again. (Shorter intervals than 200 ms are permitted, but not required.) If T = 0, receiving ADS-B equipment shall accept airborne position messages as being current as of the time of receipt. The transmitting ADS-B equipment shall reload the airborne position register with updated estimates of the A/V position, at intervals that are no more than 200 ms apart. The process shall continue with new position reports as they become available. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-70 28/11/02 No. 77 2.3.2.3.3 Timeout when new position data are unavailable In the event that the navigation input ceases, the extrapolation described in 2.3.2.3.1 and 2.3.2.3.2 shall be limited to no more than two seconds. At the end of this timeout of two seconds, all fields of the airborne position register, except the altitude field, shall be cleared (set to zero). When the appropriate register fields are cleared, the zero type code field shall serve to notify ADS-B receiving equipment that the data in the latitude and longitude fields are invalid. 2.3.2.4 ALTITUDE This 12-bit field shall provide the aircraft altitude. Depending on the type code, this field shall contain either: 1) Barometric altitude encoded in 25 or 100 foot increments (as indicated by the Q bit) or, 2) GNSS height above ellipsoid (HAE). “Baro-Altitude” shall be interpreted as barometric pressure altitude, relative to a standard pressure of 1013.25 hectopascals (29.92 in Hg). It shall not be interpreted as baro corrected altitude. Format type code 20 to 22 shall be reserved for the reporting of GNSS height (HAE) which represents the height above the surface of the WGS-84 ellipsoid and may be used when baro altitude is not available. Note.— GNSS altitude (MSL) is not accurate enough for use in the position report. 2.3.2.5 SINGLE ANTENNA FLAG (SAF) This 1-bit field shall indicate the type of antenna system that is being used to transmit extended squitters. SAF = 1 shall signify a single transmit antenna. SAF = 0 shall signify a dual transmit antenna system. At any time that the diversity configuration cannot guarantee that both antenna channels are functional, then the single antenna subfield shall be set to ONE. 2.3.2.6 SURVEILLANCE STATUS The surveillance status field in the airborne position message format shall encode information from the aircraft’s Mode A code and SPI condition indication as specified in Annex 10, Volume IV, 3.1.2.8.6.3.1.1. 2.3.3 SURFACE POSITION FORMAT The surface position squitter shall be formatted as specified in the definition of register number 0616 in the following paragraphs. 2.3.3.1 MOVEMENT This 7-bit field shall provide information on the ground speed of the aircraft. A non-linear scale shall be used as defined in the following table where speeds are given in km/h (kt). Encoding Meaning Quantization no information available aircraft stopped (ground speed < 0.2315 km/h (0.125 kt)) 2-8 0.2315 km/h (0.125 kt) < ground speed < 1.852 km/h (1 kt) (in 0.2315 km/h (0.125 kt) steps) 9-12 1.852 km/h (1 kt) < ground speed < 3.704 km/h (2 kt) (in 0.463 km/h (0.25 kt) steps) 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-71 28/11/02 No. 77 2.3.3.2 GROUND TRACK (TRUE) 2.3.3.2.1 Ground track status This 1-bit field shall define the validity of the ground track value. Coding for this field shall be as follows: 0 = invalid and 1 = valid. 2.3.3.2.2 Ground track value This 7-bit (14-20) field shall define the direction (in degrees clockwise from true north) of aircraft motion on the surface. The ground track shall be encoded as an unsigned angular weighted binary numeral, with an MSB of 180 degrees and an LSB of 360/128 degrees, with zero indicating true north. The data in the field shall be rounded to the nearest multiple of 360/128 degrees. 2.3.3.3 COMPACT POSITION REPORTING (CPR) FORMAT (F) The 1-bit (22) CPR format field for the surface position message shall be encoded as specified for the airborne message. That is, F = 0 shall denote an even format coding, while F = 1 shall denote an odd format coding (2.6.7). 2.3.3.4 TIME SYNCHRONIZATION (T) This 1-bit field (21) shall indicate whether or not the time of applicability of the message is synchronized with UTC time. T = 0 shall denote that the time is not synchronized to UTC. T = 1 shall denote that time of applicability is synchronized to UTC time. Synchronization shall only be used for surface position messages having the top two horizontal position precision categories (format type codes 5 and 6). When T = 1, the time of validity in the surface message format shall be encoded in the 1-bit F field which (in addition to CPR format type) indicates the 0.2 second time tick for UTC time of position validity. The F bit shall alternate between 0 and 1 for successive 0.2 second time ticks, beginning with F = 0 when the time of applicability is an exact even-numbered UTC second. 2.3.3.5 LATITUDE/LONGITUDE The latitude/longitude field in the surface message shall be a 34-bit field containing the latitude and longitude coding of the aircraft’s surface position. The latitude (Y) and longitude (X) shall each occupy 17 bits. The surface latitude and longitude encodings shall contain the low-order 17 bits of the 19-bit CPR-encoded values defined in 2.6. Note.— The unambiguous range for local decoding of surface messages is 166.5 km (90 NM). The positional accuracy maintained by the surface CPR encoding is approximately 1.25 metres. The latitude/longitude encoding is also a function of the CPR format value (the “F” bit) described above. 13-38 3.704 km/h (2 kt) < ground speed < 27.78 km/h (15 kt) (in 0.926 km/h (0.5 kt) steps) 39-93 27.78 km/h (15 kt) < ground speed < 129.64 km/h (70 kt) (in 1.852 km/h (1.0 kt) steps) 94-108 129.64 km/h (70 kt) < ground speed < 185.2 km/h (100 kt) (in 3.704 km/h (2.0 kt) steps) 109-123 185.2 km/h (100 kt) < ground speed < 324.1 km/h (175 kt) (in 9.26 km/h (5.0 kt) steps) ground speed > 324.1 km/h (175 kt) Reserved Reserved Reserved Encoding Meaning Quantization 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-72 28/11/02 No. 77 2.3.3.5.1 Extrapolating position (when T = 1) This extrapolation shall conform to 2.3.2.3.1 (substitute “surface” for “airborne” where appropriate). 2.3.3.5.2 Extrapolating position (when T = 0) This extrapolation shall conform to 2.3.2.3.2 (substitute “surface” for “airborne” where appropriate). 2.3.3.5.3 Timeout when new position data are unavailable This timeout shall conform to 2.3.2.3.3 (substitute “surface” for “airborne” where appropriate). 2.3.4 IDENTIFICATION AND CATEGORY FORMAT The identification and category squitter shall be formatted as specified in the definition of BDS 0,8. 2.3.5 AIRBORNE VELOCITY FORMAT The airborne velocity squitter shall be formatted as specified in the definition of register number 0916 and in the following paragraphs. 2.3.5.1 SUBTYPES 1 AND 2 Subtypes 1 and 2 of the airborne velocity format shall be used when the transmitting aircraft’s velocity over ground is known. Subtype 1 shall be used at subsonic velocities while subtype 2 shall be used when the velocity exceeds 1 022 kt. This message shall not be broadcast if the only valid data are the intent change flag and the IFR capability flag (2.3.5.3, 2.3.5.4). After initialization, the broadcast shall be suppressed by loading register 0916 with all zeros and then discontinuing the updating of the register until data input is available again. The supersonic version of the velocity coding shall be used if either the east-west OR north-south velocities exceed 1 022 kt. A switch to the normal velocity coding shall be made if both the east-west AND north-south velocities drop below 1 000 kt. 2.3.5.2 SUBTYPES 3 AND 4 Subtypes 3 and 4 of the airborne velocity format shall be used when the transmitting aircraft’s velocity over ground is not known. These subtypes substitute airspeed and heading for the velocity over ground. Subtype 3 shall be used at subsonic velocities, while subtype 4 shall be used when the velocity exceeds 1 022 kt. This message shall not be broadcast if the only valid data are the intent change flag and the IFR capability flag (2.3.5.3, 2.3.5.4). After initialization, broadcast shall be suppressed by loading register 0916 with all zeros and then discontinuing the updating of the register until data input is available again. The supersonic version of the velocity coding shall be used if the airspeed exceeds 1 022 kt. A switch to the normal velocity coding shall be made if the airspeed drops below 1 000 kt. 2.3.5.3 INTENT CHANGE FLAG IN AIRBORNE VELOCITY MESSAGES An intent change event shall be triggered 4 seconds after the detection of new information being inserted in registers 4,0 to 4,2. The code shall remain set for 18 ± 1 second following an intent change. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-73 28/11/02 No. 77 Intent change flag coding: 0 = no change in intent 1 = intent change Note 1.— Register 4316 is not included since it contains dynamic data which will be continuously changing. Note 2.— A four-second delay is required to provide for settling time for intent data derived from manually set devices. 2.3.5.4 IFR CAPABILITY FLAG (IFR) IN AIRBORNE VELOCITY MESSAGES The IFR capability flag shall be a 1-bit (bit 10) subfield in the subtypes 1, 2, 3 and 4 airborne velocity messages. IFR = 1 shall signify that the transmitting aircraft has a capability for applications requiring ADS-B equipage class A1 or above. Otherwise, IFR shall be set to 0. 2.3.5.5 MAGNETIC HEADING IN AIRBORNE VELOCITY MESSAGES 2.3.5.5.1 Magnetic heading status This 1-bit field shall define the availability of the magnetic heading value. Coding for this field shall be: 0 = not available and 1 = available. 2.3.5.6 MAGNETIC HEADING VALUE This 10-bit field shall contain the aircraft magnetic heading (in degrees clockwise from magnetic north) when velocity over ground is not available. The magnetic heading shall be encoded as an unsigned angular weighted binary numeral with an MSB of 180 degrees and an LSB of 360/1 024 degrees, with zero indicating magnetic north. The data in the field shall be rounded to the nearest multiple of 360/1 024 degrees. 2.3.5.7 DIFFERENCE FROM BARO ALTITUDE IN AIRBORNE VELOCITY MESSAGES This 8-bit field shall contain the signed difference between barometric and GNSS altitude. (Coding for this field shall be as indicated in Tables 2-9a and 2-9b.) The difference between baro altitude and GNSS height above ellipsoid (HAE) shall be used if available. If GNSS HAE is not available, GNSS altitude (MSL) shall be used when airborne position is being reported using format type codes 11 through 18. If airborne position is being reported using format type code 9 or 10, only GNSS (HAE) shall be used. For format type code 9 or 10, if GNSS (HAE) is not available, the field shall be coded with all zeros. The basis for the baro altitude difference (either GNSS (HAE) or GNSS altitude MSL) shall be used consistently for the reported difference. 2.3.6 STATUS REGISTER FORMAT The status register shall be formatted as specified in the definition of register number 0716 and in the following paragraphs. 2.3.6.1 PURPOSE Unlike the other extended squitter registers, the contents of this register shall not be broadcast. The purpose of this register shall be to serve as an interface between the transponder function and the general formatter/manager function (GFM, 2.5). The two fields defined for this format shall be the transmission rate subfield and the altitude type subfield. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-74 28/11/02 No. 77 2.3.6.2 TRANSMISSION RATE SUBFIELD (TRS) This field is only used for a transponder implementation of extended squitter. The TRS shall be used to notify the transponder of the aircraft motion status while on the surface. If the aircraft is moving, the surface position squitter shall be broadcast at a rate of twice per second, and identity squitters at a rate of once per 5 seconds. If the aircraft is stationary, the surface position squitter shall be broadcast at a rate of once per 5 seconds and the identity squitter at a rate of once per 10 seconds. The algorithm specified in the definition of register number 0716 shall be used by the GFM (2.5) to determine motion status and the appropriate code shall be set in the TRS subfield. The transponder shall examine the TRS subfield to determine which rate to use when it is broadcasting surface squitters. 2.3.6.3 ALTITUDE TYPE SUBFIELD (ATS) This field shall only be used for a transponder implementation of extended squitter. The transponder shall load the altitude field of the airborne position squitter from the same digital source as used for addressed replies. Note.— This is done to minimize the possibility that the altitude in the squitter is different from the altitude that would be obtained by direct interrogation. If the GFM (2.5) inserts GNSS height (HAE) into the airborne position squitter, it shall instruct the transponder not to insert the baro altitude into the altitude field. The ATS subfield shall be set to ONE for this purpose. 2.3.7 EVENT-DRIVEN PROTOCOL The event-driven protocol register shall be as specified in the definition of register numbers 0A16 in 2.5.5 and in the following paragraphs. 2.3.7.1 PURPOSE The event-driven protocol shall be used as a flexible means to support the broadcast of messages beyond those defined for position, velocity, and identification. Note.— These typically will be messages that are broadcast regularly for a period of time based on the occurrence of an event. An example is the broadcast of emergency/priority status every second during a declared aircraft emergency. A second example is the periodic broadcast of intent information for the duration of the operational condition. 2.3.8 EMERGENCY/PRIORITY STATUS The emergency/priority status squitter shall be formatted as specified in the definition of register number 6116 and in the following paragraphs. 2.3.8.1 TRANSMISSION RATE This message shall be broadcast once per second for the duration of the emergency. 2.3.8.2 MESSAGE DELIVERY Message delivery shall be accomplished using the event-driven protocol (2.3.7). The broadcast of this message shall take priority over the event-driven protocol broadcast of all other message types, as specified in 2.5.5.3. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-75 28/11/02 No. 77 2.3.9 CURRENT/NEXT TRAJECTORY CHANGE POINT (TCP/TCP+1) The current/next trajectory change point (TCP) squitter shall be formatted as specified in the definition of register numbers 6216 and 6316 and in the following paragraphs. 2.3.9.1 TRANSMISSION RATE This message shall be broadcast once per 1.7 seconds for the duration of the operation. 2.3.9.2 MESSAGE DELIVERY Message delivery shall be accomplished using the event-driven protocol (2.3.7). 2.3.9.3 TRAJECTORY POINT/LEG TYPE This 4-bit (7-10) subfield shall be used to identify the type of TCP for which data are being provided in the message. The TCP type subfield shall be encoded as follows: If the trajectory point/leg can be classified in more than one of the categories identified in the table above, then the type having the largest encoded value shall be used. 2.3.9.4 TCP DATA VALID This 1-bit (11) subfield shall be used to indicate the validity of the TCP/TCP+1 message. A value of ONE shall indicate a valid message. A value of ZERO shall indicate an invalid message. Encoding Meaning No specific trajectory change point description information “Straight” (geodesic) course to a “fly by” waypoint “Straight” (geodesic) course to a “fly over” waypoint “Straight” (geodesic) course to a “speed change” waypoint “Straight” (geodesic) course to a “vertical speed change” waypoint Arc course to a “fly by” waypoint Arc course to a “fly over” waypoint Arc course to a “speed change” waypoint Arc course to a “vertical speed change” waypoint Holding pattern to a holding fix Course FROM the waypoint, termination point unknown Reserved for future use Reserved for future use Reserved for future use Reserved for future use Reserved for future use 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-76 28/11/02 No. 77 2.3.9.5 TCP FORMAT This 1-bit (12) subfield shall indicate whether the TCP is specified as position and time (4D), or position only (3D). A value ZERO shall indicate a 4D TCP. A value ONE shall indicate a 3D TCP. The 3D TCP/TCP+1 format shall be used if the distance to the TCP/TCP+1 is greater than 160 NM from the current position of the aircraft transmitting the TCP/TCP+1 message. 2.3.9.6 TCP/TCP + 1 ALTITUDE This 10-bit subfield (13-22) shall be used to provide the binary encoded altitude of the current TCP/TCP+1 message. The altitude subfield shall be encoded as follows: 2.3.9.7 TCP/TCP + 1 LATITUDE 2.3.9.7.1 4D TCP latitude This 14-bit (23-36) subfield shall be used to provide the airborne CPR encoded latitude for the 4D TCP or TCP + 1 message. Encoding of the 4D TCP/TCP + 1 latitude data shall be accomplished as specified in 2.6.3. 2.3.9.7.2 3D TCP latitude This 17-bit (23-39) subfield shall be used to provide the angular weighted binary encoded latitude for the 3D TCP or TCP + 1 message. The latitude shall be encoded as a 17-bit two’s complement signed binary numeral in which the LSB (bit 39) has a weight of 2-17 times 360 degrees. North latitudes shall have a positive sign, and south latitudes shall have a negative sign. 2.3.9.8 TCP/TCP + 1 LONGITUDE 2.3.9.8.1 4D TCP/TCP + 1 longitude This 14-bit (37-50) subfield shall be used to provide the airborne CPR encoded longitude for the 4D TCP or TCP + 1 message. Encoding of the 4D TCP/TCP +1 longitude data shall be accomplished as specified in 2.6.3. TCP/TCP + 1 ALTITUDE Coding (binary) Coding (decimal) Meaning (TCP altitude in feet) 00 0000 0000 No TCP altitude information available 00 0000 0001 TCP altitude is ZERO 00 0000 0010 TCP altitude = 128 feet 00 0000 0011 TCP altitude = 256 feet *** *** *** 11 1111 1110 TCP altitude = 130 688 feet 11 1111 1111 TCP altitude > 130 752 feet 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-77 28/11/02 No. 77 2.3.9.8.2 3D TCP/TCP + 1 longitude This 17-bit (40-56) subfield shall be used to provide the angular weighted binary encoded longitude for the 3D TCP or TCP + 1 message. The field shall be encoded as a 17-bit two’s complement signed binary numeral, in which the LSB (bit 56) has a weight of 2-17 times 360 degrees. The prime (Greenwich) meridian shall be defined as zero longitude. Longitudes to the east of Greenwich shall be positive, and those to the west of Greenwich shall be negative. 2.3.9.9 TCP/TCP + 1 TIME-TO-GO (TTG) This 6-bit (51-56) subfield shall be used to provide the binary encoded time-to-go to the TCP or TCP + 1 message. The TCP timeto-go subfield shall be encoded as follows: 2.3.10 AIRCRAFT OPERATIONAL COORDINATION MESSAGE The aircraft operational coordination message squitter shall be formatted as specified in the definition of register number 6416 and in the following paragraphs. 2.3.10.1 TRANSMISSION RATE This message shall be broadcast once per 5 seconds for the duration of the operation, except that it shall be broadcast once per 2 seconds for 30 seconds when the message content changes. 2.3.10.2 MESSAGE DELIVERY Message delivery shall be accomplished using the event-driven protocol (2.3.7). 2.3.10.3 PAIRED ADDRESS This 24-bit (9-32) subfield shall be used to provide the ICAO 24-bit address of the aircraft that the ADS-B transmitting aircraft is paired with when participating in coordinated operations with another aircraft. 2.3.10.4 RUNWAY THRESHOLD SPEED This 5-bit subfield (33-37) shall be used to provide the runway threshold speed of the aircraft. Encoding of the subfield shall be as follows: TCP/TCP + 1 time-to-go (TTG) Coding (binary) Coding (decimal) Meaning (TCP/TCP + 1 time-to-go in minutes) 00 0000 No TCP time-to-go information available 00 0001 TCP time-to-go is ZERO 00 0010 TCP time-to-go = 0.25 minutes 00 0011 TCP time-to-go = 0.50 minutes *** *** *** 11 1110 TCP time-to-go = 15.25 minutes 11 1111 TCP time-to-go > 15.375 minutes 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-78 28/11/02 No. 77 Note.— The encoding shown in the table represents positive magnitude data only. 2.3.10.5 ROLL ANGLE SIGN This 1-bit (38) subfield shall be used to provide the direction or sign of the roll angle of the aircraft. Encoding of the subfield shall be as follows: 2.3.10.6 ROLL ANGLE This 5-bit subfield (39-43) shall be used to provide the roll angle of the aircraft. Encoding of the subfield shall be as follows: Note.— The encoding shown in the table represents positive magnitude data only. The direction is given completely by the roll angle sign bit. RUNWAY THRESHOLD SPEED Coding (binary) Coding (decimal) Meaning (Runway threshold speed in knots) 0 0000 No runway threshold speed information available 0 0001 Runway threshold speed < 100 knots 0 0010 Runway threshold speed = 100 knots 0 0011 Runway threshold speed = 105 knots 0 0100 Runway threshold speed = 110 knots *** *** *** 1 1110 Runway threshold speed = 240 knots 1 1111 Runway threshold speed > 242.5 knots ROLL ANGLE SIGN BIT Coding Meaning Roll angle is +, i.e. right wing down Roll angle is –, i.e. left wing down ROLL ANGLE Coding (binary) Coding (decimal) Meaning (Roll angle in degrees) 0 0000 No roll angle information available 0 0001 Roll angle is ZERO 0 0010 Roll angle = 1.0 degree 0 0011 Roll angle = 2.0 degrees *** *** *** 1 1110 Roll angle = 29.0 degrees 1 1111 Roll angle > 29.5 degrees 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-79 28/11/02 No. 77 2.3.10.7 GO-AROUND This 2-bit (44-45) subfield shall be used to indicate the condition when the aircraft is executing a go-around. Encoding of the subfield shall be as follows: 2.3.10.8 ENGINE-OUT This 2-bit (46-47) subfield shall be used to indicate an engine-out condition on the aircraft. Encoding of the subfield shall be as follows: 2.3.11 AIRCRAFT OPERATIONAL STATUS The aircraft operational status message squitter shall be formatted as specified in the definition of register number 6416 and in the following paragraphs. 2.3.11.1 TRANSMISSION RATE This message shall be broadcast once per 1.7 seconds for the duration of the operation. 2.3.11.2 MESSAGE DELIVERY Message delivery shall be accomplished using the event-driven protocol (2.3.7). 2.3.11.3 EN-ROUTE OPERATIONAL CAPABILITIES (CC-4) This 4-bit (9-12) subfield shall be used to indicate en-route operational capabilities of the ADS-B transmitting system to other aircraft as specified by the following encoding. GO-AROUND SUBFIELD Coding Meaning No information Aircraft IS NOT executing a “go-around” Aircraft IS executing a “go-around” Reserved ENGINE-OUT SUBFIELD Coding Meaning No information Aircraft IS NOT experiencing an engine-out condition Aircraft IS experiencing an engine-out condition Reserved 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-80 28/11/02 No. 77 2.3.11.4 TERMINAL AREA OPERATIONAL CAPABILITIES (CC-3) This 4-bit (13-16) subfield shall be used to indicate terminal area operational capabilities of the ADS-B transmitting system to other aircraft as specified by the following encoding. CC-4 ENCODING: EN-ROUTE OPERATIONAL CAPABILITIES CC-4 CODING Bit 9, 10 Bit 11, 12 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved CC-3 ENCODING: TERMINAL AREA OPERATIONAL CAPABILITIES CC-3 CODING Bit 13, 14 Bit 15, 16 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-81 28/11/02 No. 77 2.3.11.5 APPROACH AND LANDING OPERATIONAL CAPABILITIES (CC-2) This 4-bit (17-20) subfield shall be used to indicate approach and landing operational capabilities of the ADS-B transmitting system to other aircraft as specified by the following encoding. 2.3.11.6 SURFACE OPERATIONAL CAPABILITIES (CC-1) This 4-bit (21-24) subfield shall be used to indicate surface operational capabilities of the ADS-B transmitting system to other aircraft as specified by the following encoding. CC-2 ENCODING: APPROACH AND LANDING OPERATIONAL CAPABILITIES CC-2 CODING Bit 17, 18 Bit 19, 20 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved CC-1 ENCODING: SURFACE OPERATIONAL CAPABILITIES CC-1 CODING Bit 21, 22 Bit 23, 24 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-82 28/11/02 No. 77 2.3.11.7 EN-ROUTE OPERATIONAL CAPABILITY STATUS (OM-4) This 4-bit (25-28) subfield shall be used to indicate the en-route operational capability status of the ADS-B transmitting system to other aircraft as specified by the following encoding. 2.3.11.8 TERMINAL AREA OPERATIONAL CAPABILITY STATUS (OM-3) This 4-bit (29-32) subfield shall be used to indicate the terminal area operational capability status of the ADS-B transmitting system to other aircraft as specified by the following encoding. 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved OM-4 ENCODING: EN-ROUTE OPERATIONAL CAPABILITY STATUS OM-4 CODING Bit 25, 26 Bit 27, 28 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved OM-3 ENCODING: TERMINAL AREA OPERATIONAL CAPABILITY STATUS OM-3 CODING Bit 29, 30 Bit 31, 32 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-83 28/11/02 No. 77 2.3.11.9 APPROACH AND LANDING OPERATIONAL CAPABILITY STATUS (OM-2) This 4-bit (33-36) subfield shall be used to indicate the approach and landing operational capability status of the ADS-B transmitting system to other aircraft as specified by the following encoding. 2.3.11.10 SURFACE OPERATIONAL CAPABILITY STATUS (OM-1) This 4-bit (37-40) subfield shall be used to indicate the surface operational capability status of the ADS-B transmitting system to other aircraft as specified by the following encoding. 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved OM-2 ENCODING: APPROACH AND LANDING OPERATIONAL CAPABILITY STATUS OM-2 CODING Bit 33, 34 Bit 35, 36 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved OM-1 ENCODING: SURFACE OPERATIONAL CAPABILITY STATUS OM-1 CODING Bit 37, 38 Bit 39, 40 MEANING 0 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-84 28/11/02 No. 77 2.4 EXTENDED SQUITTER INITIALIZATION AND TIMEOUT Initialization and timeout functions for extended squitter broadcast shall be performed by the transponder and are specified in Annex 10, 3.1.2. Note.— A description of these functions is presented in the following paragraphs to serve as reference material for the section on the general formatter/manager (GFM) (see 2.5). 2.4.1 INITIATION OF EXTENDED SQUITTER BROADCAST At power-up initialization, the transponder shall commence operation in a mode in which it broadcasts only acquisition squitters. The transponder shall initiate the broadcast of extended squitters for airborne position, surface position, airborne velocity and aircraft identification when data are inserted into register numbers 0516, 0616, 0916 and 0816, respectively. This determination shall be made individually for each squitter type. The insertion of altitude or surveillance status data into register number 0516 by the transponder shall not satisfy the minimum requirement for broadcast of the airborne position squitter. Note.— This suppresses the transmission of extended squitters from aircraft that are unable to report position, velocity or identity information. 2.4.2 REGISTER TIMEOUT The transponder shall clear all but the altitude and surveillance status subfields in the airborne position register (register 0516) and all 56 bits of the surface position, squitter status and airborne velocity registers (register numbers 0616, 0716 and 0916) if these registers are not updated within two seconds of the previous update. This timeout shall be determined separately for each of these registers. The insertion of altitude or surveillance status data by the transponder into these registers shall not qualify as a register update for the purposes of this timeout condition. Note 1.— These registers are cleared to prevent the reporting of outdated position, velocity and squitter rate information. Note 2.— The identification register, 0816, is not cleared since it contains data that rarely changes in flight and is less frequently updated. The event-driven register, 0A16 or equivalent transmit register, does not need to be cleared since its contents are only broadcast once each time that the register is loaded (2.5.5). Note 3.— During a register timeout event, the ME field of the extended squitter may contain all zeros, except for any data inserted by the transponder. 0 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 0 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 1 1 0 0 Reserved 0 1 Reserved 1 0 Reserved 1 1 Reserved 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-85 28/11/02 No. 77 2.4.3 TERMINATION OF EXTENDED SQUITTER BROADCAST If input to the register for a squitter type stops for 60 seconds, broadcast of that extended squitter type shall be discontinued until data insertion is resumed. The insertion of altitude by the transponder satisfies the minimum requirement for continuing to broadcast the airborne position squitter. Note 1.— Until timeout, a squitter type may contain an ME field of all zeros. Note 2.— Continued transmission for 60 seconds is required so that receiving aircraft will know that the data source for the message has been lost. 2.5 GENERAL FORMATTER/MANAGER (GFM) The general formatter/manager (GFM) shall format messages for insertion in the transponder registers. Note.— In addition to data formatting, there are other tasks that are performed by this function. 2.5.1 NAVIGATION SOURCE SELECTION The GFM shall be responsible for the selection of the default source for aircraft position and velocity, the commanded altitude source, and for the reporting of the associated position and altitude errors. 2.5.2 LOSS OF INPUT DATA The GFM shall be responsible for loading the registers for which it is programmed at the required update rate. If for any reason data are unavailable for a time equal to twice the update interval or 2 seconds (whichever is greater), the GFM shall zero old data (on a per field basis) and insert the resulting message into the appropriate register. For register 0516 and 0616, a loss of position data shall cause the GFM to set the format type code to zero as the means of indicating “no position data” since all zeros in the latitude/longitude fields is a legal value. 2.5.3 SPECIAL PROCESSING FOR FORMAT TYPE CODE ZERO 2.5.3.1 SIGNIFICANCE OF FORMAT TYPE CODE EQUAL TO ZERO Format type code 0 shall signify “no position information”. This shall be used when the latitude/longitude information is not available or invalid and still permit the reporting of baro altitude loaded by the transponder. Note 1.— The principal use of this message is to provide ACAS the ability to passively receive altitude. Note 2.— Special handling is required for the airborne and surface position messages because a CPR encoded value of all zeros in the latitude/longitude field is a valid value. 2.5.3.2 BROADCAST OF FORMAT TYPE CODE EQUAL TO ZERO Format type code 0 shall only be set by the following events: 1) An extended squitter register monitored by the transponder (register numbers 0516, 0616, 0716 and 0916) has not been loaded by the GFM for 2 seconds. In this case, the transponder shall clear the entire 56 bits of the register that timed out. In the case of the airborne position register, the altitude subfield shall only be zeroed if no altitude data are available. Transmission of the extended squitter that broadcasts the timed out register shall itself stop in 60 seconds. Broadcast of this extended squitter shall resume when the GFM begins to insert data into the register. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-86 28/11/02 No. 77 2) The GFM determines that all navigation sources that can be used for the extended squitter airborne or surface position message are either missing or invalid. In this case, the GFM shall clear the format type code and all other fields of the airborne or surface position message and insert this zeroed message in the appropriate register. This shall only be done once so that the transponder can detect the loss of data insertion and suppress the broadcast of the related squitter. Note.— In all of the above cases, a format type code of zero contains a message of all zeros. The only exception is the airborne position format that may contain barometric altitude and surveillance status data as set by the transponder. There is no analogous case for the other extended squitter message types, since a zero value in any of the fields indicates no information. 2.5.3.3 RECEPTION OF FORMAT TYPE CODE EQUAL TO ZERO If a squitter with a format type code equal to zero is received, it shall be checked to see if the altitude is present. If the altitude is not present, the message shall be discarded. An extended squitter containing format type code zero shall only be used to update the altitude of an aircraft already in track. 2.5.4 TRANSPONDER CAPABILITY REPORTING The GFM shall be responsible for setting the transponder capability register numbers 1016, and 1816 to 1C16. It shall also clear individual bits in register number 1716 in the event of a loss of a data source or an application. A particular bit shall remain set if at least one field in the corresponding register message is being updated. 2.5.4.1 COMMON USAGE CAPABILITY REPORT (REGISTER NUMBER 1716) A bit in register number 1716 shall be cleared if there is a loss of corresponding input data (2.5.2) and shall be set when data insertion into the register resumes. Bit 36 of register 1016 shall be toggled to indicate a change of capability. 2.5.4.2 MODE S SPECIFIC SERVICES CAPABILITY REPORT (REGISTER NUMBERS 1816 to 1C16) A bit set in one of these registers shall indicate that the service loading the register indicated by that bit has been installed on the aircraft. In this regard, these bits shall not be cleared to reflect a real time loss of an application, as is done for register 1716. 2.5.4.3 TRANSPONDER MONITORING As indicated in 2.4, the transponder’s role in this process shall be to serve as a backup in the event of the loss of GFM functionality. For this reason, the transponder shall: 1) clear the extended squitter registers (0516, 0616, 0716 and 0916) if they have not been updated in 2 seconds. 2) clear all of the registers loaded by the GFM if it detects a loss of GFM capability (e.g. a bus failure). In this case, it would also clear all of the bits in register number 1716 since a bit in this register means “application installed and operational”. The transponder shall not clear the other capability register numbers (1816 to 1C16) since they are intended to mean only “application installed”. 2.5.5 HANDLING OF EVENT-DRIVEN PROTOCOL The event-driven interface protocol provides a general purpose interface into the transponder function for messages beyond those that are regularly transmitted all the time (provided input data are available). This protocol shall operate by having the transponder broadcast a message once each time the event-driven register is loaded by the GFM. Note.— This gives the GFM complete freedom in setting the update rate (up to a maximum) and duration of broadcast for applications such as emergency status and intent reporting. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-87 28/11/02 No. 77 In addition to formatting, the GFM shall control the timing of message insertion so that it provides the necessary pseudo-random timing variation and does not exceed the maximum transponder broadcast rate for the event-driven protocol. 2.5.5.1 TRANSPONDER SUPPORT FOR EVENT-DRIVEN MESSAGES A message shall only be transmitted once by the transponder each time that register number 0A16 is loaded. Transmission shall be delayed if the transponder is busy at the time of insertion. Note 1.— Delay times are short. They are usually a maximum of several milliseconds for the longest transponder transaction. The maximum transmission rate for the event-driven protocol shall be limited by the transponder to twice per second. If a message is inserted in the event-driven register and cannot be transmitted due to rate limiting, it shall be held and transmitted when the rate limiting condition has cleared. If a new message is received before transmission is permitted, it shall overwrite the earlier message. Note 2.— The squitter transmission rate and the duration of squitter transmissions are application dependent. The minimum rate and duration consistent with the needs of the application should be chosen. 2.5.5.2 GFM USE OF EVENT-DRIVEN PROTOCOL An application that selects the event-driven protocol shall notify the GFM of the format type and required update rate. The GFM shall then locate the necessary input data for this format type and begin inserting data into register number 0A16 at the required rate. The GFM shall also insert this message into the register for this format type. This register image shall be maintained to allow read-out of this information by air-ground or air-air register read-out. When broadcast of a format type ceases, the GFM shall clear the corresponding register assigned to this message. The maximum rate that shall be supported by the event-driven protocol is twice per second from one or a collection of applications. For each event-driven format type being broadcast, the GFM shall retain the time of the last insertion into register number 0A16. The next insertion shall be scheduled at a random interval that shall be uniformly distributed over the range of the update interval ± 0.1 second (using a time quantization no greater than 15 ms) relative to the previous insertion into register number 0A16 for this format type. The GFM shall monitor the number of insertions scheduled in any one second interval. If more than two would occur, it shall add a delay as necessary to ensure that the limit of two messages per second is observed. 2.5.5.3 EVENT-DRIVEN PRIORITY If the event-driven message transmission rate must be reduced in order not to exceed the maximum rate specified in 2.5.5.2, transmission priority shall be assigned as follows: 1) If the emergency/priority status message (2.3.8) is active, it shall be transmitted at the specified rate of once per second. Other active event-driven messages shall be assigned equal priority for the remaining capacity. 2) If the emergency/priority status message is not active, transmission priority shall be allocated equally to all active eventdriven messages. 2.5.6 DERIVATION OF MODE FIELD BITS FOR AIRCRAFT INTENTION PARAMETERS For aircraft architectures that do not present the GFM with a dedicated status word (containing the mode field definitions associated with aircraft intention parameters), the GFM shall derive the status from each of the appropriate FCC status words in order to set the respective bits in each of the mode fields of the register number 4016. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-88 28/11/02 No. 77 2.6 LATITUDE/LONGITUDE CODING USINGCOMPACT POSITION REPORTING (CPR) 2.6.1 PRINCIPLE OF THE CPR ALGORITHM The Mode S extended squitters use compact position reporting (CPR) to encode latitude and longitude efficiently into messages. Notes.—

Source: https://magyarkozlony.hu/hivatalos-lapok/4c6310a937d14bac566ee9c9d944896656c292dd/dokumentumok/5a6ac3c6db12e692ae41096677ad5f072d2cc9f3/letoltes