Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

B-42 Technical Provisions for Mode S Services and Extended Squitter B.3.4.2 TIS-B SURFACE POSITION MESSAGE The TIS-B surface position ME field shall be formatted as specified in Table B-3-2. B.3.4.2.1 MOVEMENT DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris This field shall be set as specified in §B.2.3.3.1 B.3.4.2.2 GROUND TRACK (TRUE) B.3.4.2.2.1 Ground track status This field shall be set as specified in §B.2.3.3.2.1. B.3.4.2.2.2 Ground track angle This field shall be set as specified in §B.2.3.3.2.2. B.3.4.2.3 ICAO/MODE A FLAG (IMF) FOR THE SURFACE POSITION MESSAGE This one-bit field (bit 21) shall indicate the type of identity associated with the aircraft data reported in the TIS-B message. Coding is specified in §B.3.4.1.1. B.3.4.2.4 COMPACT POSITION REPORTING (CPR) FORMAT (F) This field shall be set as specified in §A.2.3.3.3. B.3.4.2.5 LATITUDE/LONGITUDE Draft The Latitude/Longitude fields in the TIS-B fine Surface Position Message shall be set as specified in §A.2.3.3.5. B.3.4.3 IDENTIFICATION AND CATEGORY MESSAGE The TIS-B identification and category ME field shall be formatted as specified in Table B-3-3. This message shall only be used for aircraft identified with an ICAO 24-bit address. B.3.4.3.1 AIRCRAFT IDENTIFICATION CODING This field shall be set as specified in the definition of BDS 0,8. B.3.4.4 VELOCITY MESSAGE The TIS-B Velocity ME field shall be formatted as specified in Tables B-3-4a and B-3-4b. 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-43 B.3.4.4.1 SUBTYPE FIELD Subtypes 1 and 2 shall be used for the velocity message when velocity over ground is reported. Subtypes 3 and 4 shall be used when airspeed and heading are reported. Subtype 2 (the supersonic version of the velocity coding) shall be used if either the east-west OR north-south velocities exceed 1 022 knots. A switch to subtype 1 (the normal velocity coding) shall be made if both the east-west AND northsouth velocities drop below 1 000 knots. Subtype 4 (the supersonic version of the airspeed coding) shall be used if airspeed exceeds 1 022 knots. A switch to subtype 3 (the normal airspeed coding) shall be made if the airspeed drops below 1 000 knots. B.3.4.4.2 ICAO/MODE A FLAG (IMF) FOR THE VELOCITY MESSAGE This one-bit field (bit 9) shall indicate the type of identity associated with the aircraft data reported in the TIS-B message. Coding is specified in §B.3.4.1.1. B.3.4.5 COARSE AIRBORNE POSITION MESSAGE The TIS-B coarse airborne position ME field shall be formatted as specified in Table B-3-5. Note.— This message is used if the surveillance source for TIS-B is not of high enough quality to justify the use of the fine formats. An example of such a source is a scanning beam Mode S interrogator. B.3.4.5.1 ICAO/MODE A FLAG (IMF) FOR THE COARSE AIRBORNE POSITION MESSAGE This one-bit field (bit 1) shall indicate the type of identity associated with the aircraft data reported in the TIS-B message in §B.3.4.1.1. B.3.4.5.2 SERVICE VOLUME ID (SVID) Draft The 4-bit SVID field shall identify the TIS-B site that delivered the surveillance data. Note 1.— In the case where TIS-B messages are being received from more than one TIS-B service, the Service ID can be used to select coarse messages from a single service. This will prevent the TIS-B track from wandering due to the different error characteristics associated with the different services. Note 2.— The SVID is defined by the service provider. B.3.4.5.3 PRESSURE-ALTITUDE This 12-bit field shall provide the aircraft pressure-altitude. This field shall contain barometric altitude encoded in 25- or 100-foot increments (as indicated by the Q Bit). B.3.4.5.4 GROUND TRACK STATUS This one bit (ME bit 20) field shall define the validity of the ground track value. Coding for this field shall be as follows: 0=not valid and 1=valid. 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: DRAFT - Working Paper ASP TSGWP11-0
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 169 and 170: Appendix B B-33 MB FIELD DRAFT - Wo
Page 177: 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 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221 and 222: Appendix C C-33 Msg Bit # "ME” Bi
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?