Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

A-6 Technical Provisions for Mode S Services and Extended Squitter A.2.3.1 FORMAT TYPE CODES The format TYPE Code shall differentiate the Mode S extended squitter messages into several classes as specified in the following table: TYPE Code Format 0 No position information 1 2 3 4 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Identification (Category Set D) Identification (Category Set C) Identification (Category Set B) Identification (Category Set A) “TYPE” Subfield Code Definitions (DF = 17 or 18) Horizontal protection limit (HPL) 95% Containment radius, µ and v, on horizontal and vertical position error Altitude type (see §A.2.3.2.4) Barometric altitude or no altitude information Not applicable Not applicable Not applicable Not applicable 5 Surface position HPL < 7.5 m µ < 3 m No altitude information 9 6 Surface position HPL < 25 m 3 m ≤ µ < 10 m No altitude information 8 7 Surface position 8 Surface position HPL < 185.2 m (0.1 NM) HPL > 185.2 m (0.1 NM) 10 m ≤ µ < 92.6 m (0.05 NM) NUCP No altitude information 7 (0.05 NM) 92.6 m ≤ µ No altitude information 6 9 Airborne position HPL < 7.5 m µ < 3 m Barometric altitude 9 10 Airborne position 7.5 m ≤ HPL < 25 m 3 m ≤ µ < 10 m Barometric altitude 8 11 Airborne position 12 Airborne position 13 Airborne position 14 Airborne position 15 Airborne position 16 Airborne position 17 Airborne position 25 m ≤ HPL < 185.2 m (0.1 NM) 10 m ≤ µ < 92.6 m (0.05 NM) Barometric altitude 7 Draft 185.2 m (0.1 NM) ≤ HPL < 370.4 m (0.2 NM) 370.4 m (0.2 NM) ≤ HPL < 926 m (0.5 NM) 926 m (0.5 NM) ≤ HPL < 1 852 m (1.0 NM) 1 852 m (1.0 NM) ≤ HPL < 3 704 m (2.0 NM) 3.704 km (2.0 NM) ≤ HPL < 18.52 km (10 NM) 18.52 km (10 NM) ≤ HPL < 37.04 km (20 NM) 92.6 m (0.05 NM) ≤ µ < 185.2 m (0.1 NM) 185.2 m (0.1 NM) ≤ µ < 463 m (0.25 NM) 463 m (0.25 NM) ≤ µ < 926 m (0.5 NM) 926 m (0.5 NM) ≤ µ < 1 852 m (1.0 NM) 1.852 km (1.0 NM) ≤ µ < 9.26 km (5.0 NM) 9.26 km (5.0 NM) ≤ µ < 18.52 km (10.0 NM) Barometric altitude 6 Barometric altitude 5 Barometric altitude 4 Barometric altitude 3 Barometric altitude 2 Barometric altitude 1 18 Airborne position HPL ≥ 37.04 km (20 NM) 18.52 km (10.0 NM) ≤ µ Barometric altitude 0 19 Airborne velocity Not applicable Not applicable Difference between “Barometric altitude” and “GNSS height (HAE) or GNSS altitude (MSL)” DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris 0 N/A
Appendix A A-7 TYPE Code Format Horizontal protection limit (HPL) 95% Containment radius, µ and v, on horizontal and vertical position error Altitude type (see §A.2.3.2.4) (2.3.5.7) 20 Airborne position HPL < 7.5 m µ < 3 m and v < 4 m GNSS height (HAE) 9 21 Airborne position HPL < 25 m µ < 10 m and v < 15 m GNSS height (HAE) 8 22 Airborne position HPL ≥ 25 m µ > 10 m or v ≥ 15 m GNSS height (HAE) 0 23 Reserved for test purposes 24 Reserved for surface system status 25 – 27 Reserved 28 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Extended squitter aircraft emergency priority status 29 Reserved 30 Reserved 31 Aircraft operational status In normal operating conditions, HPL or HIL information is available from the navigation data source and shall be used to determine the format TYPE Code. The TYPE Code for airborne and surface position messages shall be determined based on the availability of integrity and/or accuracy information as defined below: a) If horizontal protection level (HPL) information is available from the navigation data source, then the transmitting ADS-B system shall use HPL and Altitude Type to determine the TYPE Code used in the Airborne Position Message in accordance with the above table. b) If HPL (or HIL) is temporarily not available from the navigation data source, then the transmitting ADS-B system shall use HFOM (95% bound on the horizontal position error), VFOM (95% bound on the vertical position error), and Altitude Type to determine the TYPE Code used in the Airborne Position Message in accordance with the above table. NUCP Draft c) If position data is available but the associated accuracy and/or integrity is unknown (i.e., the conditions in a) and b) above are not applicable), then the transmitting ADS-B system shall use for airborne position messages TYPE Code 18 or 22, depending on the altitude type, and for surface position messages TYPE Code 8 in accordance with the above table. Note 1.— The term “broadcast”, when applied to extended squitter, refers to a spontaneous transmission by the transponder. This is distinct from the Comm-B broadcast protocol. Note 2.— The Type Code allows users to determine whether the quality of the position is good enough for the intended application. Note 3.— Airborne Position Messages with Type Code 18 or 22 (NUCP=0), and Surface Position Messages with Type Code 8 (NUCP=6, HPL≥185.2m, μ≥92.6m) are not appropriate to support most ADS-B applications since these Type Codes indicate the accuracy and integrity of the broadcast position is unknown. Messages with these Type Codes are typically transmitted from installations where the ADS-B position is obtained from sources with no accompanying integrity information. Note 4.— It is recommended that Version 0 extended squitter messages with Type Codes 8, 18 or 22 only be used 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 29: DRAFT - Working Paper ASP TSGWP11-0
Page 37 and 38: Appendix A A-13 The supersonic vers
Page 39 and 40: Appendix A A-15 The transponder sha
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 79 and 80: Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Appendix A A-57 MB FIELD DRAFT - Wo
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:
DRAFT - Working Paper ASP TSGWP11-0
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:
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?