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-20 Technical Provisions for Mode S Services and Extended Squitter C.2.3.7.3.1.1 “Emergency/Priority Status Message” Broadcast Rates When Transmission of Mode A Code is Disabled When the Mode A Code transmission is disabled as per §C.2.3.7.3.1, the following transmit rates apply: a. The “Emergency/Priority Status Message” (TYPE=28, Subtype=1) shall be broadcast at random intervals that are uniformly distributed over the range of 0.7 to 0.9 seconds relative to the previous “Emergency/Priority Status” for the duration of the emergency condition which is established by any value other than ZERO in the “Emergency/Priority Status” subfield. Note.— Emergency conditions resulting from the Mode A Code being set to 7500, 7600 or 7700 are covered by the requirements in §C.2.3.7.3.1.2. b. In the case where there is no emergency condition established by a ZERO value in the “Emergency/Priority Status” subfield, then the “Emergency/Priority Status Message” shall not be broadcast. C.2.3.7.3.1.2 Emergency/Priority Status Message” Broadcast Rates When Transmission of Mode A Code is Enabled When the Mode A Code transmission is enabled as per §C.2.3.7.3.1, the following transmit rates apply: a. The “Emergency/Priority Status” (TYPE=28, Subtype=1) shall be broadcast at random intervals that are uniformly distributed over the range of 0.7 to 0.9 seconds relative to the previous “Emergency/Priority Status” under the following conditions: i. For a duration of 24 ±1 seconds following a Mode A Code change by the pilot except if the Mode A Code is changed to 7500, 7600 or 7700. Note.— The case where the Mode A Code is set to 7500, 7600 or 7700, the transmission of the emergency condition is covered by ”ii”. below. Setting the Mode A Code to 7500, 7600 or 7700 is indicated by a Permanent Alert in the “Surveillance Status” field (value of 1) (see Figure C-1). A change in the Mode A Code, except to 7500, 7600 or 7700, is indicated by a Temporary Alert in the “Surveillance Status” subfield (value of 2) (see Figure C-1). ii. For the duration of an emergency condition by any non-ZERO value in the “Emergency/Priority Status” subfield, if the emergency code is cleared by the pilot changing the Mode A Code to other than 7500, 7600 or 7700, the broadcast of the “Emergency/Priority Status” Message shall be continued for 24 ±1 seconds as “i” above. Draft b. In the absence of conditions specified in “a” above, the “Emergency/Priority Status” Message shall be broadcast at random intervals that are uniformly distributed over the range of 4.8 to 5.2 seconds relative to the previous “Emergency / Priority Status” Message. C.2.3.7.3.2 Message Delivery The Aircraft Status (TYPE=28) Emergency/Priority Status (Subtype=1) Message delivery shall be accomplished using the Event-Driven protocol (§C.2.3.7). The broadcast of this message takes priority over the Event-Driven protocol broadcasts of all other message types, except for the ADS-B Aircraft Status TCAS RA Broadcast Message (TYPE=28, Subtype=2), which 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.8 PERIODIC STATUS MESSAGES Operational Status Messages and Target State and Status Messages are Periodic Status Messages that are broadcast independently in the same manner as the Airborne Position, Surface Position, Airborne Velocity and Aircraft Identification Messages. In previous Editions of this Manual, Operational Status and Target State and Status Messages were included under the event-driven protocol and subject to the hard limit of 2 transmissions per second in any second as per §C.2.5.4. Analysis is provided that verifies that the 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-21 combination of Periodic Status Messages and Event-Driven Messages does not exceed 2 messages per second averaged over 60 seconds. C.2.3.9 TARGET STATE AND STATUS INFORMATION Register 62 16 contains an exact bit-for-bit duplicate of the Target State and Status Extended Squitter Message (TYPE=29 and Subtype=1), and shall be formatted as specified in Figure C-9, and described in the following paragraphs. C.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. A summary of the transmission rates for all extended squitters is shown in Table C-35. Note.— In previous Editions of this Manual, the Target State and Status Message was delivered using the Event-Driven protocol. C.2.3.9.2 Source Integrity Level (SIL) Supplement The “SIL Supplement” (Source Integrity Level Supplement) subfield is a 1-bit (“ME” bit 8, Message bit 40) field that defines whether the reported SIL probability is based on a “per hour” probability or a “per sample” probability as defined in Table C-6. Table C-6. “SIL Supplement” Subfield Encoding Coding Meaning 0 Probability of exceeding NIC radius of containment is based on “per hour” 1 Probability of exceeding NIC radius of containment is based on “per sample” ► Per Hour: The probability of the reported geometric position laying outside the NIC containment radius in any given hour without an alert or an alert longer than the allowable time-to-alert. Note.— The probability of exceeding the integrity radius of containment for GNSS position sources are based on a per hour basis, as the NIC will be derived from the GNSS Horizontal Protection Level (HPL) which is based on a probability of 1x10 -7 per hour. Draft ► Per Sample: The probability of a reported geometric position laying outside the NIC containment radius for any given sample. Note.— The probability of exceeding the integrity radius of containment for IRU, DME/DME and DME/DME/LOC position sources may be based on a per sample basis. C.2.3.9.3 Selected Altitude Type The “Selected Altitude Type” subfield is a 1-bit (“ME” bit 9, Message bit 41) field that shall be used to indicate the source of Selected Altitude data that is being used to encode “ME” bits 10 – 20 (Message bits 42 – 52). Encoding of the “Selected Altitude Type” is defined in Table C-7. Whenever there is no valid MCP / FCU or FMS Selected Altitude data available, then the “Selected Altitude Type” subfield is set to ZERO (0). 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 207: 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 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?