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 C-30 Technical Provisions for Mode S Services and Extended Squitter (3). Change in TCAS RA Active/NAC P/SIL/NIC SUPP Data with No Target State and Status: If there has been a change in the TCAS RA Active, NAC P, SIL or NIC SUPP information provided in the Airborne Aircraft Operational Status Message (TYPE=31, Subtype=0), and Target State and Status Messages are NOT being broadcast, then the Airborne Aircraft Operational Status Messages (TYPE=31, Subtype=0) shall be broadcast at random intervals that are uniformly distributed over the range of 0.7 to 0.9 seconds relative to the previous Airborne Aircraft Operational Status Message for a period of 24 ±1 seconds. b. Surface Aircraft Operational Status Messages (TYPE=31, Subtype=1) shall be broadcast at the rates given in the following subparagraphs when aircraft operational status information is valid and when in the ON-Ground state; (1). Aircraft/Vehicle Not Moving: If the aircraft/vehicle is on-ground and NOT moving, then Surface Aircraft Operational Status Messages (TYPE=31, Subtype=1) shall be broadcast at random intervals that are uniformly distributed over the range of 4.8 to 5.2 seconds relative to the previous Surface Aircraft Operational Status Message for as long as data is available to satisfy the requirements of subparagraph “b.” above. (2). Aircraft/Vehicle Is Moving but No Change in NIC SUPP/NAC/SIL Data: If the Aircraft/Vehicle IS Moving and there has been no change in the NICSUPP, NAC, or SIL data provided in the Surface Aircraft Operational Status Message (TYPE=31, Subtype=1), then the messages shall be broadcast at random intervals that are uniformly distributed over the range of 2.4 to 2.6 seconds relative to the previous Surface Aircraft Operational Status Message for as long as data is available to satisfy the requirements of subparagraph “b.” above. (3). Aircraft/Vehicle Is Moving With Change in NIC SUPP/NAC/SIL Data: If the Aircraft/Vehicle IS Moving and there has been a change in the NICSUPP, NAC, or SIL data provided in the Surface Aircraft Operational Status Message (TYPE=31, Subtype=1), then the messages shall be broadcast at random intervals that are uniformly distributed over the range of 0.7 to 0.9 seconds relative to the previous Surface Aircraft Operational Status Message for a period of 24 ±1 secondsfor as long as data is available to satisfy the requirements of subparagraph “b.” above. C.2.3.10.2 Message Delivery Draft Message delivery is independent of the Event-Driven protocol and is classified as a Periodic Status Message. Note.— In previous Editions of this Manual, the Operational Status Message was delivered using the Event-Driven protocol. C.2.3.10.3 Capability Class (CC) Codes This 16-bit (“ME” bits 9 – 24, Message bits 41 – 56) subfield in the Airborne Aircraft Operational Status Message (Subtype=0) or 12-bit (“ME” bits 9 – 20, Message bits 41 – 52) subfield in the Surface Aircraft Operational Status Message (Subtype=1) shall be used to report the operational capability of the aircraft. Encoding of the CC subfield shall be defined as specified in Table C-23 and Table C-24. For an ADS-B Transmitting Subsystem compliant with this Manual, if an update has not been received from an on-board data source within the past 2 seconds for any data element of the Capability Class Codes subfield, then the data associated with that data element shall be considered invalid and so reflected in the encoding of that message element to reflect “No Capability” or “Unknown” capability. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Msg Bit # “ME” Bit # Appendix C C-31 Content = 0,0 Table C-23. Airborne Capability Class (CC) Code for Version 2 Systems 41 42 43 44 45 46 47 48 49 50 51 52 53 – 56 9 10 11 12 13 14 15 16 17 18 19 20 21 -- 24 TCAS Operational 0,1 Reserved 1,0 Reserved 1,1 Reserved Subfield Coding: 1090ES IN Reserved = 0,0 1. TCAS Operational = 0: TCAS/ACAS is NOT Operational = 1: TCAS/ACAS IS Operational 2. 1090ES IN (1090 MHz Extended Squitter) = 0: Aircraft has NO 1090ES Receive capability = 1: Aircraft has 1090ES Receive capability ARV TS TC 3. ARV (Air-Referenced Velocity Report Capability) = 0: No capability for sending messages to support Air Referenced Velocity Reports = 1: Capability of sending messages to support Air-Referenced Velocity Reports. 4. TS (Target State Report Capability) = 0: No capability for sending messages to support Target State Reports = 1: Capability of sending messages to support Target State Reports UAT IN 5. TC (Target Change Report Capability) = 0: No capability for sending messages to support Trajectory Change Reports = 1: Capability of sending messages to support TC+0 Report only = 2: Capability of sending information for multiple TC reports = 3: Reserved 6. UAT IN (Universal Access Transceiver) = 0: Aircraft has No UAT Receive capability = 1: Aircraft has UAT Receive capability Msg Bit # “ME” Bit # DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Content = 0,0 Subfield Coding: Reserved for ADS-R Reserved [4] Draft Table C-24. Surface Capability Class (CC) Code for Version 2 Systems 41 42 43 44 45 46 47 48 49 --- 51 52 9 10 11 12 13 14 15 16 17 --- 19 20 Reserved = 0 0,1 Reserved 1,0 Reserved 1,1 Reserved 1090ES IN Reserved = 0,0 1. 1090ES IN (1090 MHz Extended Squitter) = 0: Aircraft has NO 1090ES Receive capability = 1: Aircraft has 1090ES Receive capability B2 Low UAT IN NACV [3] DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris NIC Supplement-C [1]
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: DRAFT - Working Paper ASP TSGWP11-0
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 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 217: DRAFT - Working Paper ASP TSGWP11-0
Page 221 and 222: 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 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?