Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris B-8 Technical Provisions for Mode S Services and Extended Squitter B.2.3.5.1 SUBTYPES 1 AND 2 Subtypes 1 and 2 shall be used as specified in §A.2.3.5.1. B.2.3.5.2 SUBTYPES 3 AND 4 Subtypes 3 and 4 shall be used as specified in §A.2.3.5.2. B.2.3.5.3 INTENT CHANGE FLAG IN AIRBORNE VELOCITY MESSAGES The intent change flag shall be formatted as specified in §A.2.3.5.3. B.2.3.5.4 IFR CAPABILITY FLAG (IFR) IN AIRBORNE VELOCITY MESSAGES The IFR capability flag shall be formatted as specified in §A.2.3.5.4. B.2.3.5.5 NAVIGATION ACCURACY CATEGORY FOR VELOCITY (NACV) This 3-bit (ME bits 11-13, Message bits 43-45) subfield shall indicate the navigation accuracy category for velocity (NACV). The ADS-B transmitting subsystem shall accept, via an appropriate data interface, data from which the own-vehicle navigation accuracy category for velocity (NACV) may be determined, and it shall use such data to establish the NACV subfields in transmitted ADS-B airborne velocity messages. B.2.3.5.5.1 If the external data source provides 95 per cent accuracy figures of merit for horizontal and vertical velocity [HFOMR (horizontal figure of merit for velocity) and VFOMR (vertical figure of merit for velocity)], then the ADS-B transmitting subsystem shall determine the value of the NACV field in the airborne velocity messages, subtypes 1, 2, 3 and 4 as specified in the following table. Draft NACV value (Decimal) HFOMR value VFOMR value 4 HFOMR < 0.3 m/s (0.984 fps) AND VFOMR < 0.46 m/s (1.5 fps) 3 HFOMR < 1 m/s (3.28 fps) AND VFOMR < 1.52 m/s (5.0 fps) 2 HFOMR < 3 m/s (9.84 fps) AND VFOMR < 4.57 m/s (15.0 fps) 1 HFOMR < 10 m/s (32.8 fps) AND VFOMR < 15.24 m/s (50 fps) 0 HFOMR unknown or HFOMR ≥ 10 m/s (32.8 fps) OR VFOMR unknown or VFOMR ≥ 15.24 m/s (50 fps) Note.— The tests in the table are to be applied in the order shown, from the most stringent test (for NACV = 4) to the least stringent (for NACV = 0). That is, if HFOMR and VFOMR do not satisfy the conditions for NACV = 4, then they are tested against the conditions for NACV = 3. If they do not satisfy the conditions for NACV = 3, they are tested against the conditions for NACV = 2, and so on. B.2.3.5.5.2 If the external data source does not provide HFOMR and VFOMR, the 95 per cent accuracy figures of merit for horizontal and vertical velocity, but it does provide 95 per cent accuracy figures of merit for the horizontal and vertical 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-9 positions [HFOM, horizontal figure of merit for position, and VFOM, vertical figure of merit for position], then the following tables shall be used to determine the NACV value to be inserted in the Airborne Velocity message. The following table shall be used if the position and velocity are obtained from a GNSS/GBAS or GNSS/SBAS receiver (Global Navigation Satellite System with Ground Based Augmentation System or with Satellite Based Augmentation System) when that receiver is operating in GBAS or SBAS mode. NACV value (Decimal) HFOM and VFOM values 4 HFOM ≤ 1 m and VFOM ≤ 5.85 ft 3 (HFOM > 1 m or VFOM > 5.85 ft) and HFOM ≤ 4.5 m, and VFOM ≤ 23.3 ft 2 (HFOM > 4.5 m or VFOM > 23.3 ft) and HFOM ≤ 14.5 m, and VFOM ≤ 73.3 ft 1 (HFOM > 14.5 m or VFOM > 73.3 ft) and HFOM ≤ 49.5 m, and VFOM ≤ 248 ft 0 HFOM > 49.5 m or VFOM > 248 ft B.2.3.5.5.3 The following table shall be used if the position and velocity are obtained from a GNSS receiver operating in autonomous mode (that is, without GBAS or SBAS differential corrections). NACV value (Decimal) HFOM and VFOM values 2 HFOM ≤ 125 m, and VFOM ≤ 585 ft 0 HFOM > 475 m or VFOM > 2 335 ft 1 (HFOM > 125 m or VFOM > 585 ft) and HFOM ≤ 475 m, and VFOM ≤ 2 335 ft Draft B.2.3.5.5.4 If the external source of position and velocity data provides neither 95 per cent bounds on the accuracy of the velocity data (HFOMR and VFOMR) nor 95 per cent bounds on the accuracy of the position data (HFOM and VFOM), then the transmitting ADS-B device shall set the value of the NACV field in the Airborne Velocity Messages to zero. B.2.3.5.6 HEADING IN AIRBORNE VELOCITY MESSAGES The heading in the airborne velocity message shall be formatted as specified in §A.2.3.5.6. Note.— The reference direction for heading (whether True North or Magnetic North) is indicated in the Horizontal Reference Direction (HRD) field of the Aircraft Operational Status Message (see §B.2.3.10.13). B.2.3.5.7 DIFFERENCE FROM BAROMETRIC ALTITUDE IN AIRBORNE VELOCITY MESSAGES The difference from barometric altitude field shall be formatted as specified in §A.2.3.5.7. 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: Appendix A A-69 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 and 140: Appendix B B-3 TYPE code Subtype co
Page 143: DRAFT - Working Paper ASP TSGWP11-0
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 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

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

Delete template?

Save as template?