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-58 Technical Provisions for Mode S Services and Extended Squitter 2. The update and output of both ADS-B Reports when Extended Squitter Messages are received with the duplicate ICAO 24-bit address results in additional overhead since output of both ADS-B Reports possibly occurs upon message reception. However, this approach gives ADS-B applications the ability to associate information with the correct ADS-B Report if they choose to attempt to correlate using the additional provided information. The duplicate address condition shall be cleared after 60 seconds has elapsed with no Position Message update for a Participant with an ADS-B Report identified in the duplicate address condition. The relevant ADS-B Report for the Participant shall be deleted from the Report Output Storage Buffer. Output of the remaining ADS-B Report shall contain a State Vector Report with the Duplicate Address Flag set to “OFF”. Note.— After clearing the duplicate address condition, the ADS-B Report for the aircraft/vehicle that continues to receive Position Messages that pass the local CPR reasonableness test, as well as other 1090ES ADS-B Messages, is retained and updated as per RTCA DO-260B, §2.2.10.4. C.2.6.10.4.3 Duplicate Address Report Capacity The ADS-B Receiving Subsystem shall be capable of maintaining and processing a minimum of three concurrent duplicate address Reports. Note.— The required capacity includes duplicate address Reports from both ADS-B and ADS-R targets. Since duplicate address situations are expected to be infrequent events, the ability to handle three duplicate address Reports is expected to be sufficient. C.2.7 FORMATS FOR EXTENDED SQUITTER The Extended Squitter messages shall be formatted as defined in the following tables. Note.— In some cases, ARINC 429 labels are referenced for specific message fields. These references are only intended to clarify the field content, and are not intended as a requirement to use these ARINC 429 labels as the source for the message field. Draft DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix C C-59 Register 0516 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Figure C-1. Extended Squitter Airborne Position 1 2 Purpose: To provide accurate airborne position information. 3 FORMAT TYPE CODE 4 (§C.2.3.1) Surveillance Status Coding 5 0 = no condition information 6 7 SURVEILLANCE STATUS 1 = permanent alert (emergency condition) 2 = temporary alert (change in Mode A identity code other 8 NIC SUPPLEMENT-B (§C.2.3.2.5) than emergency condition 9 10 3 = SPI condition 11 ALTITUDE Codes 1 and 2 take precedence over code 3. 12 Specified by the Format TYPE Code 13 14 (1) the altitude code (AC) as specified in §2.2.13.1.2 of 15 DO-181D (EUROCAE ED-73C §3.17.1.b), but with 16 the M-bit removed (Ref ARINC 429 Label 203), or 17 18 (2) GNSS Height (HAE) (Ref. ARINC 429 Label 370) 19 20 21 TIME (T) (§C.2.3.2.2) 22 CPR FORMAT (F) (§C.2.3.2.1) 23 MSB 24 25 26 27 28 29 30 CPR ENCODED LATITUDE 31 32 (CPR Airborne Format §C.2.6.1 to §C.2.6.10) 33 34 35 36 37 38 39 LSB 40 MSB 41 42 43 44 45 46 47 CPR ENCODED LONGITUDE 48 49 (CPR Airborne Format §C.2.6.1 to §C.2.6.10) 50 51 52 53 54 55 56 LSB Note.— When horizontal position information is unavailable, but altitude information is available, the Airborne Position Message is transmitted with a Format TYPE Code of ZERO in bits 1-5 and the barometric pressure altitude in bits 9 to 20. If neither horizontal position nor barometric altitude information is available, then all 56 bits of Register 0516 are ZEROed. The ZERO Format TYPE Code field indicates that Latitude and Longitude information is unavailable, while the ZERO altitude field indicates that altitude information is unavailable. Draft 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:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Appendix B B-33 MB FIELD DRAFT - Wo
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Appendix B B-41 CF value ICAO/Mode
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Appendix C C-5 Table C-2. “TYPE
Page 195 and 196: DRAFT - Working Paper ASP TSGWP11-0
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 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: Appendix C C-57 B Reports to have k
Page 249 and 250: Appendix C C-61 Register 0716 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 287 and 288: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 291 and 292: Appendix CD CD-7 too many broadcast
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?