Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

B-10 Technical Provisions for Mode S Services and Extended Squitter B.2.3.6 STATUS REGISTER FORMAT The status register shall be formatted as specified in §A.2.3.6. B.2.3.7 EVENT-DRIVEN PROTOCOL The event-driven protocol register shall be as specified in §A.2.3.7. B.2.3.8.1 EMERGENCY/PRIORITY STATUS B.2.3.8.1.1 Format B.2.3.8 AIRCRAFT STATUS The aircraft status squitter that conveys emergency/priority status information shall be formatted as specified in the definition of transponder register 6116, Table B-2-97a. B.2.3.8.1.2 Transmission rate This message shall be broadcast at random intervals that are uniformly distributed between 0.7 and 0.9 seconds for the duration of the emergency. B.2.3.8.1.3 Message delivery Message delivery shall be accomplished using the event-driven protocol (see §A.2.3.7). The broadcast of this message shall not take priority over the ACAS RA broadcast but shall take priority over all other event-driven message types, as specified in §B.2.5.5.3. B.2.3.8.2 ACAS RA BROADCAST B.2.3.8.2.1 Format DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Draft The aircraft status squitter that conveys ACAS RA broadcast information shall be formatted as specified in the definition of transponder register 6116, Table B-2-97b. B.2.3.8.2.2 Transmission rate This message shall be broadcast at random intervals that are uniformly distributed between 0.7 and 0.9 seconds for the duration of the emergency. B.2.3.8.2.3 Message delivery Message delivery shall be accomplished using the event-driven protocol (see §A.2.3.7). The broadcast of this message shall take priority over the emergency/priority status broadcast and all other event-driven message types, as specified in §B.2.5.5.3. 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-11 B.2.3.9 RESERVED FOR TARGET STATE AND STATUS INFORMATION The target state and status information squitter shall be formatted as specified in the definition of register 6216 and in the following paragraphs: B.2.3.9.1 TRANSMISSION RATE The Target State and Status Message shall be broadcast at random intervals uniformly distributed over the range of 1.2 to 1.3 seconds for the duration of the operation. B.2.3.9.2 MESSAGE DELIVERY Extended Squitter Message delivery shall be accomplished using the event-driven protocol (see §A.2.3.7). B.2.3.9.3 VERTICAL DATA AVAILABLE/SOURCE INDICATOR This 2-bit (ME bits 8 — 9, Message bits 40 — 41) subfield shall be used to identify if aircraft vertical state information is available and present as well as the data source for the vertical data when present in the subsequent subfields. Encoding shall be defined as specified in the following table. Any message parameter associated with vertical target state for which an update has not been received from an on-board data source with the past 5 seconds shall be considered invalid and so indicated in the Vertical Data Available/Source Indicator subfield. Coding (Binary) (Decimal) Meaning 00 0 No valid Vertical Target State data is available 01 1 Autopilot control panel selected value, such as Mode Control Panel (MCP) or Flight Control Unit (FCU) Draft 10 2 Holding altitude 11 3 FMS/RNAV system B.2.3.9.4 TARGET ALTITUDE TYPE This one bit (ME bit 10, Message bit 42) subfield shall be used to identify whether the altitude reported in the “Target Altitude” subfield is referenced to mean sea level (MSL) or to a flight level (FL). A value of ZERO (0) shall indicate target altitude referenced to pressure-altitude (flight level). A value of ONE (1) shall indicate a target altitude referenced to barometric corrected altitude (mean sea level). B.2.3.9.5 TARGET ALTITUDE CAPABILITY This 2-bit subfield (ME bits 12 — 13, Message bits 44 — 45) shall be used to describe the aircraft’s capabilities for providing the data reported in the target altitude subfield. The target altitude capability subfield shall be encoded as specified in the following table. 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: Appendix A A-71 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 145: 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 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?