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-18 Technical Provisions for Mode S Services and Extended Squitter C.2.3.6 AIRCRAFT STATUS REGISTER FORMAT The Aircraft Status register shall be formatted as specified in the definition of Register 07 16 in Figure C-3, and described in the following paragraphs. C.2.3.6.1 Purpose Note.— Unlike the other Extended Squitter registers, the contents of this register are not broadcast. The purpose of this register is to serve as an interface between the transponder function and the General Formatter/Manager function (GFM, §C.2.5). The two fields defined for this format are the Transmission Rate Subfield and the Altitude Type Subfield. C.2.3.6.2 Transmission Rate Subfield (TRS) This field shall only be 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 0716 shall be used by the GFM (§C.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. C.2.3.6.3 Altitude Type Subfield (ATS) This field shall only be used for a transponder implementation of Extended Squitter. Note.— The transponder normally loads the altitude field of the airborne position squitter from the same digital source as used for addressed replies. 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 (§C.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 used for this purpose. Draft C.2.3.7 EVENT-DRIVEN PROTOCOL A message inserted in Register 0A16 (or an equivalent transmit register) shall be broadcast once by the transponder at the earliest opportunity. Formats for messages using this protocol shall be identical to those defined for Register 6116 (see Figure C-7). Note.— The GFM (§C.2.5) is responsible for ensuring pseudo-random timing, priority and for observing the maximum transmission rate for this register of 2 per second. Additional details are specified in §C.2.5.4 and in the following paragraphs. A summary of the transmission rates for all extended squitters is shown in Table C-35. C.2.3.7.1 Purpose Note.— The Event-Driven protocol is intended as a flexible means to support the broadcast of messages beyond those defined for position, velocity, and identification. These typically will be messages that are broadcast regularly for a period of time based on the occurrence of an event and/or having a variable broadcast rate as determined by processes external to the transponder. Two examples are: (1) the broadcast of Emergency/Priority Status at a periodic rate during a declared aircraft emergency, and (2) the broadcast of TCAS Resolution Advisory data during a declared event. 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-19 C.2.3.7.2 TCAS Resolution Advisory (RA) Broadcast The 1090ES TCAS RA Broadcast Message contains the same information as the RA message readout using the GICB protocol, including the aircraft ICAO 24-bit Address. A ground-based 1090ES receiver with an omni-directional receiving capability can provide TCAS RA Messages to the ground systems much sooner than with a scanning beam antenna. The TCAS RA information is defined as a Subtype=2 of the existing 1090ES Aircraft Status Message. The airborne aircraft broadcast rates and priorities for the TCAS RA Broadcast Message are defined below. The format for broadcasting a 1090ES Aircraft Status Message with TCAS RA Message content (1090ES Message TYPE=28, Subtype=2) is defined here in Figure C-8b. C.2.3.7.2.1 Transmission Rate The ADS-B Aircraft Status (TYPE=28) TCAS RA Broadcast Message (Subtype=2) shall be broadcast starting within 0.5 seconds after the transponder notification of the initiation of a TCAS Resolution Advisory. The ADS-B Aircraft Status (TYPE=28) TCAS RA Broadcast Message (Subtype=2) shall be broadcast using the Event-Driven Protocol at random intervals that are uniformly distributed over the range of 0.7 to 0.9 seconds for the duration of the TCAS Resolution Advisory. A summary of the transmission rates for all extended squitters is shown in Table C-35. C.2.3.7.2.2 Message Delivery ADS-B Aircraft Status TCAS RA Broadcast Message delivery is accomplished using the Event-Driven protocol. The broadcast of the TCAS RA Broadcast Message shall be terminated 24 ±1 seconds after the Resolution Advisory Termination (RAT) flag (see §4.3.8.4.2.2.1.3 of ICAO Annex 10, Volume IV) transitions from ZERO (0) to ONE (1). The broadcast of the ADS-B Aircraft Status TCAS RA Broadcast Message takes priority over the Emergency/Priority Status broadcast, and all other Event-Driven Message types, as specified in §C.2.5.4.3. C.2.3.7.3 Emergency/Priority Status and Mode A Code Register 6116 contains an exact bit-for-bit duplication of the Emergency/Priority Status information that is broadcast using an Event-Driven Aircraft Status Extended Squitter Message (TYPE=28 and Subtype=1). Subtype=1 is used specifically to provide Emergency/Priority Status information and the broadcast of the Mode A (4096) Code. The contents of Register 6116 shall be formatted as specified in Figure C-8a, and described in the following paragraphs. Draft C.2.3.7.3.1 Transmission Rate The Aircraft Status (TYPE=28) Emergency/Priority Status ADS-B Message (Subtype=1) shall be broadcast using the Event–Driven protocol. The rate of transmission varies depending on other conditions. If the transmission of the Mode A Code is disabled, the transmission of the “Emergency/Priority Status Message” occurs only when an emergency condition is active. When the transmission of the Mode A Code is enabled, the transmission rate of the “Emergency/Priority Status Message” depends on whether the Mode A Code is changed, or if an emergency condition is active. When the Mode A Code is set to “1000,” the 1090ES Transmitting Subsystem shall disable the transmission of the Mode A Code and broadcast the “Emergency/Priority Message” in accordance with §C.2.3.7.3.1.1 only when an emergency is declared. Otherwise, the Mode A Code transmission is enabled and the broadcast rates of §C.2.3.7.3.1.2 apply. A summary of the transmission rates for all extended squitters is shown in Table C-35. Note.— The use of Mode A Code “1000” for this purpose is in accordance with the provision to disable the transmission of the Mode A Code on 1090ES. This will occur at such time that the ATC systems no longer depend on the Mode A Code to identify aircraft. 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: 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 205: DRAFT - Working Paper ASP TSGWP11-0
Page 213 and 214: Appendix C C-25 Notes.— DRAFT - W
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
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 257 and 258:
Appendix C C-69 Register 6516 DRAFT
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?