Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

C-34 Technical Provisions for Mode S Services and Extended Squitter C.2.3.10.6 Navigation Integrity Category (NIC) and NIC Supplement-A The first 5-bit field (“ME” bits 1 – 5, Message bits 33 – 37) in every Mode S Extended Squitter Message contains the format TYPE Code. The format TYPE Code differentiates the 1090ES Messages into several classes: Airborne Position, Airborne Velocity, Surface Position, Identification and Category, Aircraft Intent, Aircraft Status, etc. In addition, the format TYPE Code also encodes the Navigation Integrity Category (NIC) value of the source used for the position report. The NIC Supplement-A is a 1-bit (“ME” bit 44, Message bit 76) subfield in the Aircraft Operational Status Message that is used in conjunction with the TYPE Code and NIC value to allow surveillance applications to determine whether the reported geometric position has an acceptable level of integrity containment region for the intended use. The NIC integrity containment region is described horizontally using the radius of containment, RC. The format TYPE Code also differentiates the Airborne Messages as to the type of their altitude measurements: barometric pressure altitude or GNSS height (HAE). The 5-bit encoding for format TYPE Code and NIC values conforms to the definition contained in Table C-28. If an update has not been received from an on-board data source for the determination of the TYPE Code value based on the radius of containment within the past 2 seconds, then the TYPE Code value shall be encoded to indicate that RC is “Unknown.” NIC Value Table C-28. Navigation Integrity Category (NIC) Encoding Radius of Containment (RC) Airborne Surface Airborne Position TYPE Code NIC Supplement Codes A B Surface Position TYPE Code NIC Supplement Codes A C 0 RC unknown 0, 18 or 22 0 0 0, 8 0 0 1 RC < 20 NM (37.04 km) 17 0 0 N/A N/A N/A 2 RC < 8 NM (14.816 km) 16 0 0 N/A N/A N/A 3 RC < 4 NM (7.408 km) 16 1 1 N/A N/A N/A 4 RC < 2 NM (3.704 km) 15 0 0 N/A N/A N/A 5 RC < 1 NM (1852 m) 14 0 0 N/A N/A N/A RC < 0.6 NM (1111.2 m) 13 1 1 8 0 1 6 RC < 0.5 NM (926 m) 13 0 0 N/A N/A N/A RC < 0.3 NM (555.6 m) 13 0 1 8 1 0 7 RC < 0.2 NM (370.4 m) 12 0 0 8 1 1 8 RC < 0.1 NM (185.2 m) 11 0 0 7 0 0 9 RC < 75m 11 1 1 7 1 0 10 RC < 25m 10 or 21 0 0 6 0 0 11 RC < 7.5m 9 or 20 0 0 5 0 0 12 Reserved 13 Reserved 14 Reserved 15 Reserved Notes.— DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Draft 1. “N/A” means “This NIC value is not available in the ADS-B Surface Position Message formats.” 2. NIC Supplement-A is broadcast in the Aircraft Operational Status Message, “ME” bit 44 (Message bit 76, see Figure C-10). NIC Supplement-B is broadcast in the Airborne Position Message, “ME” bit 8 (Message bit 40, see Figure C-1). NIC Supplement-C is broadcast in the Surface Capability Class (CC) Code Subfield of the Aircraft Operational Status Message, “ME” bit 20 (Message bit 52, see Table C-24). 3. A non-excluded satellite failure requires that the RC be set to Unknown along with the NAC P parameter being set to ZERO to indicate that the position has been determined to be invalid (see §C.2.3.1.1.3 and §C.2.3.1.2.4). DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Appendix C C-35 C.2.3.10.7 Navigation Accuracy Category for Position (NACP) This 4-bit (“ME” bits 45 – 48, Message bits 77 – 80) subfield shall be used to announce 95% accuracy limits for the horizontal position (and for some NAC P values, the vertical position) that is being currently broadcast in Airborne Position and Surface Position Messages. Encoding of the subfield shall be as shown in Table C- 13. If an update has not been received from an on-board data source for NAC P within the past 2 seconds, then the NAC P subfield shall be encoded as a value indicating “Unknown Accuracy.” C.2.3.10.8 Geometric Vertical Accuracy (GVA) This 2-bit (“ME” bits 49 – 50, Message bits 81 – 82) subfield in the Airborne Operational Status Message (Subtype=0) shall be encoded as shown in Table C-29, and set by using the Vertical Figure of Merit (VFOM) (95%) from the GNSS position source used to encode the geometric altitude field in the Airborne Position Message. Table C-29. Encoding of the Geometric Vertical Accuracy (GVA) Subfield in Aircraft Operational Status Messages GVA Encoding Meaning (decimal) (meters) 0 Unknown or > 150 meters 1 ≤ 150 meters 2 ≤ 45 meters 3 Reserved Note.— For the purposes of this Manual, values for 0, 1 and 2 are encoded. Decoding values for 3 should be treated as < 45 meters until future versions of this Manual redefine the value. C.2.3.10.9 Source Integrity Level (SIL) This 2-bit (“ME” bits 51 – 52, Message bits 83 – 84) subfield is defined for the Target State and Status Message in §C.2.3.9.11 and Table C-15, and remains the same in the Operational Status Message. C.2.3.10.10 Barometric Altitude Integrity Code (NICBARO) Draft This 1-bit (“ME” bit 53, Message bit 85) subfield shall be used to indicate whether or not the barometric pressure altitude being reported in the Airborne Position Message (§C.2.3.2) has been cross-checked against another source of pressure altitude. The NICBARO subfield shall be encoded as shown in Table C-14. If an update has not been received from an on-board data source for NICBARO within the past 2 seconds, then the NICBARO subfield shall be encoded as a value of ZERO (0). C.2.3.10.11 Aircraft Length and Width Codes This 4-bit (“ME” bits 21 – 24, Message bits 53 – 56) subfield shall be used in the Surface Aircraft Operational Status Message (Subtype=1) to describe the amount of space that an Aircraft or Ground Vehicle occupies. The A/V Length and Width Code shall be based on the actual dimensions of the transmitting Aircraft or Surface Vehicle as specified in Table C-30. Once the actual Length and Width of the A/V has been determined, each A/V shall be assigned the smallest A/V Length and Width Code from Table C-30 for which the actual length is less than or equal to the upper bound length for that Length/Width Code, and for which the actual width is less than or equal to the upper bound width for that Length/Width Code. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Page 1 and 2:
DRAFT - Working Paper ASP TSGWP11-0
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Appendix A A-7 TYPE Code Format Hor
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Appendix A A-13 The supersonic vers
Page 39 and 40:
Appendix A A-15 The transponder sha
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Appendix A A-41 MB FIELD DRAFT - Wo
Page 67 and 68:
Appendix A A-43 MB FIELD 1 MSB TRAN
Page 69 and 70:
Page 71 and 72:
Appendix A A-47 MB FIELD 1 2 3 4 5
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Appendix A A-97 a) the PI sends a T
Page 123 and 124:
Appendix A A-99 This subfield shall
Page 125 and 126:
Appendix A A-101 These channels hav
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Appendix A A-109 A.4. MODE S BROADC
Page 135 and 136:
Appendix A A-111 Note 1.— This st
Page 137 and 138:
Page 139 and 140:
Appendix B B-3 TYPE code Subtype co
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Appendix B B-17 Coding (Binary) (De
Page 155 and 156:
Appendix B B-19 a) ACAS operational
Page 157 and 158:
Appendix B B-21 Subfield Coding: DR
Page 159 and 160:
Appendix B B-23 Coding (Binary) (De
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Appendix B B-33 MB FIELD DRAFT - Wo
Page 171 and 172: Appendix B B-35 MB FIELD DRAFT - Wo
Page 177 and 178: Appendix B B-41 CF value ICAO/Mode
Page 179 and 180: DRAFT - Working Paper ASP TSGWP11-0
Page 193 and 194: Appendix C C-5 Table C-2. “TYPE
Page 199 and 200: Appendix C C-11 C.2.3.2.2 Time Sync
Page 213 and 214: Appendix C C-25 Notes.— DRAFT - W
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221: Appendix C C-33 Msg Bit # "ME” Bi
Page 231 and 232: Appendix C C-43 Notes. — DRAFT -
Page 239 and 240: Appendix C C-51 3. The decoded posi
Page 245 and 246: Appendix C C-57 B Reports to have k
Page 247 and 248: Appendix C C-59 Register 0516 DRAFT
Page 253 and 254: Appendix C C-65 Register 0A16 Figur
Page 259 and 260: Appendix C C-71 Table C-37. CF Fiel
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Appendix CD CD-3 ACTIONS EVENTS DRA
Page 289 and 290:
Page 291 and 292:
Appendix CD CD-7 too many broadcast
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Appendix CD CD-13 CD.2.4.4.1.2 Poss
Page 299 and 300:
Appendix CD CD-15 D.2.4.4.2.1.2 A32
Page 301 and 302:
Appendix CD CD-17 AP/FD mode V/S-FP
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 309 and 310:
Page 311 and 312:
Appendix CD CD-27 Zone no. DRAFT -
Page 313 and 314:
Page 315 and 316:
Appendix CD CD-31 CD.4 IMPLEMENTATI
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Appendix DE DE-7 c. for GNSS, the p
Page 327 and 328:
Appendix DE DE-9 MB FIELD DRAFT - W
Page 329 and 330:
Appendix DE DE-11 MB FIELD DRAFT -
show all

Technical Provisions for Mode S Services and Extended Squitter

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?