Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

A-10 Technical Provisions for Mode S Services and Extended Squitter A.2.3.2.3.3 Time-out when new position data are unavailable In the event that the navigation input ceases, the extrapolation described in §A.2.3.2.3.1 and §A.2.3.2.3.2 shall be limited to no more than two seconds. At the end of this time-out of two seconds, all fields of the airborne position register, except the altitude field, shall be cleared (set to zero). When the appropriate register fields are cleared, the zero TYPE Code field shall serve to notify ADS-B receiving equipment that the data in the latitude and longitude fields are invalid. A.2.3.2.4 ALTITUDE This 12-bit field 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). Barometric altitude shall be interpreted as barometric pressure-altitude, relative to a standard pressure of 1 013.25 hectopascals (29.92 in Hg). It shall not be interpreted as barometric corrected altitude. Format TYPE Code 20 to 22 shall be reserved for the reporting of GNSS height (HAE) which represents the height above the surface of the WGS-84 ellipsoid and may be used when barometric altitude is not available. Note.— GNSS altitude (MSL) is not accurate enough for use in the position report. A.2.3.2.5 SINGLE ANTENNA FLAG (SAF) This 1-bit field shall indicate the type of antenna system that is being used to transmit extended squitters. SAF=1 shall signify a single transmit antenna. SAF=0 shall signify a dual transmit antenna system. At any time that the diversity configuration cannot guarantee that both antenna channels are functional, then the single antenna subfield shall be set to ONE. A.2.3.2.6 SURVEILLANCE STATUS Draft The surveillance status field in the airborne position message format shall encode information from the aircraft’s Mode A code and SPI condition indication as specified in Annex 10, Volume IV, §3.1.2.8.6.3.1.1. A.2.3.3 SURFACE POSITION FORMAT The surface position squitter shall be formatted as specified in the definition of register number 0616 in the following paragraphs. A.2.3.3.1 MOVEMENT DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris This 7-bit field shall provide information on the ground speed of the aircraft. The minimum update rate of this field, as well as the ground track (true) field, shall be once per 1.3s, whereas the minimum update rate of all other fields of register 0616 shall be once per 0.2s. A non-linear scale shall be used as defined in the following table where speeds are given in km/h and kt. 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-11 Encoding Meaning Quantization 0 No information available 1 Aircraft stopped (ground speed < 0.2315 km/h (0.125 kt)) 2 ― 8 0.2315 km/h (0.125 kt) ≤ ground speed < 1.852 km/h (1 kt) (in 0.2315 km/h (0.125 kt) steps) 9 ― 12 1.852 km/h (1 kt) ≤ ground speed < 3.704 km/h (2 kt) (in 0.463 km/h (0.25 kt) steps) 13 ― 38 3.704 km/h (2 kt) ≤ ground speed < 27.78 km/h (15 kt) (in 0.926 km/h (0.5 kt) steps) 39 ― 93 27.78 km/h (15 kt) ≤ ground speed < 129.64 km/h (70 kt) (in 1.852 km/h (1.0 kt) steps) 94 ― 108 129.64 km/h (70 kt) ≤ ground speed < 185.2 km/h (100 kt) (in 3.704 km/h (2.0 kt) steps) 109 ― 123 185.2 km/h (100 kt) ≤ ground speed < 324.1 km/h (175 kt) (in 9.26 km/h (5.0 kt) steps) 124 Ground speed ≥ 324.1 km/h (175 kt) 125 Reserved 126 Reserved 127 Reserved A.2.3.3.2 GROUND TRACK (TRUE) A.2.3.3.2.1 Ground track status This 1-bit field shall define the validity of the ground track value. Coding for this field shall be as follows: 0=invalid and 1=valid. The minimum update rate of this field, as well as the movement field, shall be once per 1.3s, whereas the minimum update rate of all other fields of register 0616 shall be once per 0.2s. A.2.3.3.2.2 Ground track value Draft This 7-bit (14-20) field shall define the direction (in degrees clockwise from true north) of aircraft motion on the surface. The ground track shall be encoded as an unsigned angular weighted binary numeral, with an MSB of 180 degrees and an LSB of 360/128 degrees, with zero indicating true north. The data in the field shall be rounded to the nearest multiple of 360/128 degrees. A.2.3.3.3 COMPACT POSITION REPORTING (CPR) FORMAT (F) The 1-bit (22) CPR format field for the surface position message shall be encoded as specified for the airborne message. That is, F=0 shall denote an even format coding, while F=1 shall denote an odd format coding (see §AC.2.6.7). A.2.3.3.4 TIME SYNCHRONIZATION (T) This 1-bit field (21) shall indicate whether or not the time of applicability of the message is synchronized with UTC time. T = 0 shall denote that the time is not synchronized to UTC. T = 1 shall denote that time of applicability is synchronized to UTC time. Synchronization shall only be used for surface position messages having the top two horizontal position precision categories (format TYPE Codes 5 and 6). When T = 1, the time of validity in the surface message format shall be encoded in the 1-bit F field which (in addition to CPR format type) indicates the 0.2s time tick for UTC time of position validity. The F bit shall alternate between 0 and 1 for successive 0.2s time ticks, beginning with F = 0 when the time of applicability is an exact even-numbered UTC 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 31 and 32: Appendix A A-7 TYPE Code Format Hor
Page 33: 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 85 and 86:
Appendix A A-61 MB FIELD DRAFT - Wo
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

Create successful ePaper yourself

Delete template?

Save as template?