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-12 Technical Provisions for Mode S Services and Extended Squitter The position data that is loaded into the Airborne Position register shall be an estimate of the A/V position at the Time of Applicability. Note 3.— The position may be estimated by extrapolating the position from the time of validity of the fix (included in the position fix) to the Time of Applicability of the data in the register (which, if T=1, is an exact 0.2 UTC time tick). This may be done by a simple linear extrapolation using the velocity provided with the position fix and the time difference between the position fix validity time and the Time of Applicability of the transmitted data. Alternatively, other methods of estimating the position, such as alpha-beta trackers or Kalman filters, may be used. Every 200 ms, the contents of the position registers shall be updated by estimating the A/V position at the next subsequent 0.2 second UTC epoch. This process shall continue with new position fixes as they become available from the source of navigation data. C.2.3.2.3.2 Extrapolating Position (When T=0) “T” shall be set to ZERO (0) if the Time of Applicability of the data being loaded into the position register is not synchronized to any particular UTC epoch. The position being transmitted must have a Time of Applicability that is no greater than 100 milliseconds from the time of transmission. Additionally, the position register shall be re-loaded with position data at intervals that are no more than 200 ms apart. This ensures that the position contained in the position registers will have a Time of Applicability that is never more than 200 ms different from any time during which the register holds that data. If the transmitted position data is loaded from the position register, the position register shall be updated such that the 100 millisecond performance is achieved. Note.— This may be accomplished by loading the Airborne Position register at intervals that are no more than 200 ms apart, with data for which the Time of Applicability is between the time the register is loaded and the time that it is loaded again. For example, loading the register at 200 millisecond intervals would require that the time of applicability at register load time is exactly 100 milliseconds ahead of the register load time. Greater flexibility in the time of applicability at register load time is provided by increasing the update rate. If “T” is ZERO (0), then ADS-B Receiving Subsystems shall accept Airborne Position Messages as being current as of the Time of Receipt. Updating the position data as above ensures that the ADS-B Transmitting Subsystem does not induce more than 100 milliseconds of timing error into the transmitted position data. C.2.3.2.3.3 Time-Out When New Position Data is Unavailable Draft In the event that the navigation input ceases, the extrapolation described in §C.2.3.2.3.1 and §C.2.3.2.3.2 shall be limited to no more than two (2) seconds. At the end of this timeout of two seconds, all fields of the Airborne Position register, except the altitude field, shall be cleared (set to ZERO). Note.— The altitude field, bits 9 to 20 of the register, would only be cleared if current altitude data were no longer available. With the appropriate register fields cleared, the broadcast of the ZERO TYPE Code field shall serve to notify ADS-B Receiving Subsystems that the data in the Latitude and Longitude fields are invalid. C.2.3.2.4 Altitude This 12-bit field (“ME” bits 9 – 20, Message bits 41 – 52) shall provide the aircraft altitude. Depending on the TYPE Code, this field shall contain either: 1. Barometric altitude encoded in 25 or 100 foot increments (as indicated by the Q Bit) or, 2. GNSS height above ellipsoid (HAE). Note.— GNSS altitude MSL is not accurate enough for use in the position report. 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-13 C.2.3.2.5 NIC Supplement-B The first 5-bit field (“ME” bits 1 – 5, Message bits 33 – 37) in every Mode S Extended Squitter Message contains the format TYPE Code. The format TYPE Code differentiates the 1090ES Messages into several classes: Airborne Position, Airborne Velocity, Surface Position, Identification and Category, Aircraft Intent, Aircraft Status, etc. In addition, the format TYPE Code also encodes the Navigation Integrity Category (NIC) value of the source used for the position report. The NIC Supplement-B is a 1-bit (“ME” bit 8, Message bit 40) subfield in the Airborne Position Message that is used in conjunction with the TYPE Code and NIC value to allow surveillance applications to determine whether the reported geometric position has an acceptable level of integrity containment region for the intended use. The NIC integrity containment region is described horizontally using the radius of containment, RC. The format TYPE Code also differentiates the Airborne Messages as to the type of their altitude measurements: barometric pressure altitude or GNSS height (HAE). The 5-bit encoding for format TYPE Code and related NIC values conforms to the definition contained in Table C-28. If an update has not been received from an on-board data source for the determination of the TYPE Code value based on the radius of containment within the past 2 seconds, then the TYPE Code value shall be encoded to indicate that RC is “Unknown.” C.2.3.3 SURFACE POSITION FORMAT The Surface Position squitter shall be formatted as specified in the definition of Register 0616 in Figure C-2, and described in the following paragraphs. C.2.3.3.1 Movement This 7-bit field (“ME” bits 6 – 12, Message bits 38 – 44) shall provide information on the Ground Speed of the aircraft. A non-linear scale shall be used as defined in the Table C-3, where speeds are given in km/h (kt). Table C-3. Coding of the Movement Field Coding (Decimal) Meaning Quantization 0 No Movement Information Available 1 Aircraft Stopped (Ground Speed = 0 knots) 2 0 knots < Ground Speed ≤ 0.2315 km/h (0.125 kt) 3 - 8 0.2315 km/h (0.125 kt) < Ground Speed ≤ 1.852 km/h (1 kt) 0.2700833 km/h steps 9 - 12 1.852 km/h (1 kt) < Ground Speed ≤ 3.704 km/h (2 kt) 0.463 km /h (0.25 kt) steps 13 - 38 3.704 km/h (2 kt) < Ground Speed ≤ 27.78 km/h (15 kt) 0.926 km/h (0.50 kt) steps 39 - 93 27.78 km/h (15 kt) < Ground Speed ≤ 129.64 km/h (70 kt) 1.852 km/h (1.00 kt) steps 94 - 108 129.64 km/h (70 kt) < Ground Speed ≤ 185.2 km/h (100 kt) 3.704 km/h (2.00 kt) steps 109 - 123 185.2 km/h (100 kt) < Ground Speed ≤ 324.1 km/h (175 kt) 9.26 km/h (5.00 kt) steps 124 324.1 km/h (175 kt) < Ground Speed 125 Reserved for Aircraft Decelerating 126 Reserved for Aircraft Accelerating 127 Reserved for Aircraft Backing-Up Draft C.2.3.3.2 Heading C.2.3.3.2.1 Heading/Ground Track Status This one bit field (“ME” bit 13, Message bit 45) shall define the validity of the Heading/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:
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: DRAFT - Working Paper ASP TSGWP11-0
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 and 178: Appendix B B-41 CF value ICAO/Mode
Page 193 and 194: Appendix C C-5 Table C-2. “TYPE
Page 199: 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 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: Appendix C C-61 Register 0716 DRAFT
Page 251 and 252:
Appendix C C-63 Register 0916 DRAFT
Page 253 and 254:
Appendix C C-65 Register 0A16 Figur
Page 255 and 256:
Page 257 and 258:
Appendix C C-69 Register 6516 DRAFT
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?