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 A-92 Technical Provisions for Mode S Services and Extended Squitter A.3.2.2.2.3 Traffic information block Each TIS traffic data message shall contain two 21-bit traffic information blocks whose structure is shown below. The six fields in a traffic information block shall describe one TIS alert aircraft. One TIS traffic data message shall be able to define one or two alert aircraft. Note.— A number ‘n’ of TIS traffic data messages may be uplinked in a given scan to convey information on up to 2n alert aircraft. Traffic bearing Traffic range Relative altitude Altitude rate Traffic heading Traffic status A.3.2.2.2.3.1 Traffic bearing 6 bits 4 bits 5 bits 2 bits 3 bits 1 bit The 6-bit traffic bearing field shall contain the bearing angle from the own-aircraft heading to the alert aircraft, quantized in 6 degree increments. The valid range for the traffic bearing field shall be 0 to 59 (with the exception described below). Note.— Since this bearing angle is defined by TIS with respect to its measured own-aircraft heading, corrections from an airborne heading source can be applied. If there is only one alert aircraft in a given TIS traffic data message, the traffic bearing field in the unused traffic information block shall be set to the value 63 (a bearing angle greater than 360 degrees) and the remainder of the bits in the traffic information block shall be ignored. This shall be termed as a “null alert” block. A.3.2.2.2.3.2 Traffic range The 4-bit traffic range field shall contain the distance between own-aircraft and the alert aircraft. A non-linear range encoding shall be used to minimize the number of bits required for this field as follows: Traffic range value (r) Range (in increments of 230 m (0.125 NM)) Draft 0 0 < r ≤ 1 1 1 < r ≤ 3 2 3 < r ≤ 5 3 5 < r ≤ 7 4 7 < r ≤ 9 5 9 < r ≤ 11 6 11 < r ≤ 13 7 13 < r ≤ 15 8 15 < r ≤ 18 9 18 < r ≤ 22 10 22 < r ≤ 28 11 28 < r ≤ 36 12 36 < r ≤ 44 13 44 < r ≤ 52 14 52 < r ≤ 56 15 r > 56 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 A A-93 A.3.2.2.2.3.3 Relative altitude The 5-bit relative altitude field shall contain the difference in altitude between the own-aircraft and the alert aircraft. A non-linear encoding shall be used to minimize the number of bits required for this field. A special encoding value shall be used to indicate that the alert aircraft has no reported altitude. By convention, a positive value in the relative altitude field shall indicate that the alert aircraft is above the own-aircraft. Relative altitude shall be given by: where altitudes are indicated in feet. The TIS encoding for relative altitude shall be: Relative altitude = AltitudeAlert aircraft – AltitudeOwn-aircraft Relative altitude value (alt) Relative altitude (feet) 0 0 ≤ alt ≤ +100 1 +100 < alt ≤ +200 2 +200 < alt ≤ +300 3 +300 < alt ≤ +400 4 +400 < alt ≤ +500 5 +500 < alt ≤ +600 6 +600 < alt ≤ +700 7 +700 < alt ≤ +800 8 +800 < alt ≤ +900 9 +900 < alt ≤ +1 000 10 +1 000 < alt ≤ +1 500 11 +1 500 < alt ≤ +2 000 12 +2 000 < alt ≤ +2 500 13 +2 500 < alt ≤ +3 000 14 +3 000 < alt ≤ +3 500 15 +3 500 < alt 16 No reported altitude 17 –100 ≤ alt < 0 18 –200 ≤ alt < –100 19 –300 ≤ alt < –200 20 –400 ≤ alt < –300 21 –500 ≤ alt < –400 22 –600 ≤ alt < –500 23 –700 ≤ alt < –600 24 –800 ≤ alt < –700 25 –900 ≤ alt < –800 26 –1 000 ≤ alt < –900 27 –1 500 ≤ alt < –1 000 28 –2 000 ≤ alt < –1 500 29 –2 500 ≤ alt < –2 000 30 –3 000 ≤ alt < –2 500 31 alt < –3 000 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 71 and 72: Appendix A A-47 MB FIELD 1 2 3 4 5
Page 75 and 76: DRAFT - Working Paper ASP TSGWP11-0
Page 79 and 80: Appendix A A-55 MB FIELD 1 BDS A,8
Page 115: 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 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:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?