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-28 Technical Provisions for Mode S Services and Extended Squitter B.2.5.2 LOSS OF INPUT DATA The GFM shall handle loss of input data as specified in §A.2.5.2. B.2.5.3 SPECIAL PROCESSING FOR FORMAT TYPE CODE ZERO Special processing for format TYPE Code zero shall be performed as specified in §A.2.5.3. B.2.5.4 TRANSPONDER CAPABILITY REPORTING Transponder capability reporting shall be performed as specified in §A.2.5.4. B.2.5.5 HANDLING OF EVENT-DRIVEN PROTOCOL The event-driven interface protocol provides a general purpose interface into the transponder function for messages beyond those that are regularly transmitted all the time (provided input data are available). This protocol shall operate by having the transponder broadcast a message once each time the event-driven register is loaded by the GFM. Note.— This gives the GFM complete freedom in setting the update rate (up to a maximum) and duration of broadcast for applications such as emergency status and intent reporting. In addition to formatting, the GFM shall control the timing of message insertion so that it provides the necessary pseudorandom timing variation and does not exceed the maximum transponder broadcast rate for the event-driven protocol. B.2.5.5.1 TRANSPONDER SUPPORT FOR EVENT-DRIVEN MESSAGES Transponder support for event-driven messages shall be as specified in §A.2.5.5.1. B.2.5.5.2 GFM USE OF EVENT-DRIVEN PROTOCOL GFM use of the event-driven protocol shall be as specified in §A.2.5.5.2. B.2.5.5.3 EVENT-DRIVEN MESSAGE TRANSMISSION SCHEDULING FUNCTION Draft The event-driven message scheduling function shall ensure that the total event-driven message rate does not exceed 2 transmitted messages per second. The event-driven message scheduling function shall apply the following rules as a means of prioritizing the event-driven message transmissions and limiting the transmission rates: a) the event-driven message scheduling function shall reorder, as necessary, pending event-driven messages according to the following message priorities, listed below in descending order from highest to lowest priority. 1) When an extended squitter aircraft status message is active for the broadcast of an emergency/priority condition (type=28 and subtype=1), or an ACAS RA broadcast (type=28, subtype=2), that message shall continue to be transmitted at random intervals that are uniformly distributed over the range of 0.7 to 0.9 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-29 seconds, relative to the previous aircraft status message for the duration of the emergency or RA condition if the target state and status message is not being broadcast. If the target state and status message with subtype=zero (0) is being broadcast, then the aircraft status shall be broadcast at random intervals that are uniformly distributed over the range of 2.4 to 2.6 seconds relative to the previous aircraft status message for the duration of the emergency conditions established in accordance with Tables B-2-97a and B-2-97b. 2) Reserved for future use. 3) Reserved for future use. 4) When an aircraft operational status message is active (type=31 and subtype=0) and there has been a change in one or more of the message parameters within the past 24 seconds that results in a higher update rate-reporting requirement, the aircraft operational status message shall be transmitted at the rate specified in §B.2.3.10.1. 5) When a target state and status message is active for the broadcast of target state information (message type=29 and subtype=0) the target state and status message shall be transmitted at random intervals that are uniformly distributed over the range of 1.2 to 1.3 seconds relative to the previous target state and status message for as long as target state information is available and valid. 6) Reserved for future use. 7) When an aircraft operational status message is active (type=31 and subtype=0) and there has been no change in the message parameters that would require an increased broadcast rate, the aircraft operational status message shall be transmitted at the rate specified in §B.2.3.10.1. 8) This priority level applies as a default to any event-driven message type and subtype combination not specifically identified at a higher priority level above. Event-driven messages of this default priority level shall be delivered to the transponder on a first-in-first-out basis at equal priority. b) the event-driven message scheduling function shall limit the number of event-driven messages provided to the transponder to two (2) messages per second. Draft c) if (b) results in a queue of messages awaiting delivery to the transponder, the higher priority pending messages, according to (a) above shall be delivered to the transponder for transmission before lower priority messages. d) if (b) results in a queue of messages awaiting delivery to the transponder, new Event-Driven messages shall directly replace older messages of the same exact type and subtype (where a subtype is defined) that are already in the pending message queue. The updated message shall maintain the same position in the message queue as the pending message that is being replaced. e) if (b) above results in a queue of messages awaiting delivery to the transponder, then pending message(s) shall be deleted from the message transmission queue if not delivered to the transponder for transmission, or not replaced with a newer message of the same message Type and Subtype, within the Message Lifetime value 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:
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: Appendix A A-89 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 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 163: 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 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:
Appendix C C-39 Notes.— DRAFT - W
Page 229 and 230:
Appendix C C-41 Notes.— DRAFT - W
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?