Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

B-4 Technical Provisions for Mode S Services and Extended Squitter TYPE code 29 Subtype code NIC supplement Format (message type) Horizontal containment radius limit (RC) 0 Target state and status information (§B.2.3.9) 1 — 3 Reserved 30 0 — 7 Reserved 31 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris 0 — 1 Aircraft operational status (§B.2.3.10) 2 — 7 Reserved Navigation integrity category (NIC) Altitude type Notes Note 1.— “Barometric altitude” refers to barometric pressure-altitude, relative to a standard pressure of 1 013.25 hectopascals (29.92 in Hg). It does not refer to barometric corrected altitude. Note 2.— TYPE Codes 20 to 22 or TYPE Code 0 are to be used when valid “Barometric altitude” is not available. Note 3.— After initialization, when horizontal position information is not available but altitude information is available, the airborne position message is transmitted with a TYPE Code of ZERO in bits 1-5, the barometric pressurealtitude in bits 9 to 20, and bits 22 to 56 set to ZERO. If neither horizontal position nor barometric altitude information is available, then all 56 bits of Register 05 {HEX} are set to ZERO. The ZERO (binary 00000) TYPE Code field indicates that latitude and longitude information is not available, while the ZERO altitude field indicates that altitude information is not available. Note 4.— If the position source is an ARINC 743A GNSS receiver, then the ARINC 429 data “label 130” data word from that receiver is a suitable source of information for RC, the horizontal integrity containment radius. (The label 130 data word is variously called HPL (Horizontal Protection Limit) or HIL (Autonomous Horizontal Integrity Limit) in different documents). Note 5.— This TYPE Code value implies limits for both RC (horizontal containment limit) and VPL (Vertical Protection Limit). If either of these limits is not satisfied, then a different value for the TYPE Code is selected. Note 6.— The “NIC supplement” field in the Aircraft Operational Status Message (see §B.2.3.10) enables the Report Assembly Function in ADS-B Receiving Subsystems to determine whether the ADS-B Transmitting Subsystem is announcing NIC = 8 (RC < 0.1 NM) or NIC = 9 (RC < 75 m). Note 7.— The “NIC supplement” field in the Aircraft Operational Status Message (see §B.2.3.10) enables the Report Assembly Function in ADS-B Receiving Subsystems to determine whether the ADS-B Transmitting Subsystem is announcing NIC = 2 (RC < 8 NM) or NIC = 3 (RC < 4 NM). Draft Note 86.— The term “broadcast” as used in this appendix, refers to a spontaneous transmission by the transponder. This is distinct from the Comm-B broadcast protocol. Note 7.— The position quality in Version 1 extended squitter messages is provided by the Navigational Accuracy Category (NACP), Navigational Integrity Category (NIC), NIC Supplement, and Surveillance Integrity Level (SIL) parameters. Note 8.— NACP provides an indication of position accuracy, while SIL, NIC, and the NIC Supplement in combination provide an indication of the integrity associated with the broadcast position. NACP, SIL, and the NIC Supplement are transmitted in the Extended Squitter Aircraft Operational Status Message. NACP and SIL are also transmitted in the Target State and Status Message. NIC is determined from the message Type Code. The NIC Supplement is used with some values of NIC to distinguish between two possible values of the containment radius. In the absence of the NIC Supplement the higher NIC containment radius should be used. 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 B B-5 Note 9.— Version 1 position messages with Type Codes 8, 18, or 22, and position messages associated with SIL of 0 or NACP of 0 are not appropriate to support most ADS-B applications since the accuracy or integrity of the position broadcast in these messages is unknown by the transmitting device. Note 10.— It is recommended that Version 1 extended squitter messages with unknown accuracy or integrity only be used if either the position accuracy or integrity can be verified by other means, or the application has no specific requirements for these parameters. B.2.3.1.1 AIRBORNE POSITION MESSAGE TYPE CODE B.2.3.1.1.1 Airborne position message TYPE Code if containment radius is available Note.— If the position information comes from a GNSS receiver that conforms to the ARINC 743A Characteristic, a suitable source of information for the containment radius (RC), is ARINC 429 label 130 from that GNSS receiver. If RC (containment radius) information is available from the navigation data source, then the transmitting ADS-B subsystem shall determine the TYPE Code (the value of the TYPE subfield) of airborne position messages as follows. a) If current valid horizontal position information is not available to the ADS-B Transmitting Subsystem, then the TYPE subfield of Airborne Position Messages shall be set to ZERO (0). b) If valid horizontal position and barometric pressure-altitude information are both available to the ADS-B Transmitting Subsystem, then the ADS-B Transmitting Subsystem shall set the TYPE subfield of Airborne Position Messages to a value in the range from 9 to 18 in accordance with the table of §B.2.3.1. c) If valid horizontal position information is available to the ADS-B Transmitting Subsystem, but valid barometric pressure-altitude information is not available, and valid geometric altitude information is available, the ADS-B Transmitting Subsystem shall set the TYPE subfield of Airborne Position Messages to a value in the range from 20 to 22 depending on the containment radius RC and vertical protection limit VPL in accordance with the table of §B.2.3.1. d) If valid horizontal position information is available to the ADS-B Transmitting Subsystem, but neither valid barometric altitude information nor valid geometric altitude information is available, the ADS-B Transmitting Subsystem shall set the TYPE subfield in Airborne Position Messages to a value in the range from 9 to 18 depending on the containment radius RC in accordance with the table of §B.2.3.1. (In that case, the ALTITUDE subfield of the Airborne Position Messages would be set to all ZEROs in order to indicate that valid altitude information is not available.) Draft B.2.3.1.1.2 Airborne position message TYPE Code if containment radius is not available If RC (containment radius) information is NOT available from the navigation data source, then the ADS-B Transmitting Subsystem shall indicate NIC=0 by selecting a TYPE Code of 0, 18, or 22 in the Airborne Position Messages, as follows: a) the ADS-B Transmitting Subsystem shall set the TYPE subfield to ZERO (0) if valid horizontal position information is not available; and b) the ADS-B Transmitting Subsystem shall set the TYPE subfield to 18 if valid pressure-altitude information is available, or if neither valid pressure-altitude nor valid geometric altitude information is available. If valid pressure-altitude is not available, but valid geometric altitude information is available, the ADS-B Transmitting Subsystem shall set the TYPE subfield to 22. 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: Appendix A A-65 MB FIELD DRAFT - Wo
Page 115 and 116: DRAFT - Working Paper ASP TSGWP11-0
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 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 139: Appendix B B-3 TYPE code Subtype co
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 169 and 170: Appendix B B-33 MB FIELD DRAFT - Wo
Page 177 and 178: Appendix B B-41 CF value ICAO/Mode
Page 191 and 192:
Page 193 and 194:
Appendix C C-5 Table C-2. “TYPE
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Appendix C C-11 C.2.3.2.2 Time Sync
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Appendix C C-25 Notes.— DRAFT - W
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Msg Bit # “ME” Bit # Appendix C
Page 221 and 222:
Appendix C C-33 Msg Bit # "ME” Bi
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Appendix C C-43 Notes. — DRAFT -
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Appendix C C-51 3. The decoded posi
Page 241 and 242:
Page 243 and 244:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix C C-65 Register 0A16 Figur
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Appendix C C-71 Table C-37. CF Fiel
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
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

Create successful ePaper yourself

Delete template?

Save as template?