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-94 Technical Provisions for Mode S Services and Extended Squitter A.3.2.2.2.3.4 Altitude rate The 2-bit altitude rate field shall indicate whether the alert aircraft is climbing, descending, or level. An altitude rate of 500 ft/min shall be used as a threshold. The encoding of the TIS altitude rate field shall be: A.3.2.2.2.3.5 Traffic heading Altitude rate field value Altitude rate 0 Unused 1 Climbing (>500 ft/min) 2 Descending (>500 ft/min) 3 Level The 3-bit traffic heading field shall contain the heading of the alert aircraft quantized to 45-degree increments. This heading shall be based on the Mode S ground interrogator track for the alert aircraft. Note.— The coarse quantization of traffic heading is sufficient to aid the pilot receiving the TIS alert message to visually acquire the traffic alert aircraft. A.3.2.2.2.3.6 Traffic status The 1-bit traffic status field shall identify the type of alert represented by this traffic information block. A status value of “ZERO” shall indicate a “proximity” alert and a status value of “ONE” shall indicate a “threat” alert. A.3.2.2.2.4 Handling multiple TIS alerts As described above, the traffic data information for a given scan shall consist of one or more TIS traffic data messages. The last traffic information block of the last TIS uplink message for this scan shall be a null-alert block if there is an odd number of alert aircraft in this message. The null-alert condition shall be indicated by the value 63 decimal in the traffic bearing field of the traffic information block. Draft A.3.2.2.2.4.1 The TIS traffic information blocks within a given TIS traffic data message shall be arranged with the highest priority alerts first. All traffic information blocks with the status “threat” shall precede traffic information blocks with the status “proximity”. Within a status class, the traffic information blocks shall be put in order of increasing traffic range. Note.— This ordering ensures that the most critical traffic alerts will be at the head of the list of traffic information blocks. Therefore, TIS will report on the most significant aircraft up to the limit of the number of messages transferable in one scan. A.3.2.2.3 TIS TRAFFIC DATA MESSAGES GROUPING MECHANISM A.3.2.2.3.1 The mechanism for grouping TIS traffic data messages for a given scan shall be based on the message type field in each message as described in §3.2.2.2. A.3.2.2.3.2 Since the Mode S Comm-A protocol can deliver multiple copies of the same message, the initial step in message grouping shall be a check to eliminate duplicate messages. This shall be accomplished by a bit comparison of successive messages received with the same message type. 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-95 A.3.2.2.3.3 After duplicate elimination, the TIS traffic data for a given grouping shall always begin with a “first” segment message. This message shall contain the own-heading value for the group. Additional TIS traffic data messages in the grouping (if present) shall be structured as indicated in the table below: Number of traffic aircraft Structure of group 1 First 2 First 3 First and final 4 First and final 5 First, 1 intermediate, and final 6 First, 1 intermediate, and final 7 First, 2 intermediates, and final 8 First, 2 intermediates, and final etc. First, intermediates, and final A.3.2.2.3.4 The receipt of a “first” segment shall start the formation of a message group. Subsequent TIS traffic data uplink messages shall be added to the group until one of the following conditions occurs: a) a TIS uplink of type “final” is received (the final is part of the group); b) a TIS uplink of type “first” segment, “keep-alive”, or “goodbye” is received; or c) more than 6 seconds have elapsed since the start of the group. A.3.2.2.3.5 All the traffic blocks in the TIS traffic data message group (1 to n) shall form the display for the current time. A new group shall then be initiated by the receipt of another TIS traffic data uplink “first” segment message. TIS traffic data uplink messages of type “intermediate” or “final” shall be ignored if a new group has not been initiated by receipt of a “first” segment. A.3.2.2.4 TIS ESTABLISHMENT/DISCONNECTION PROTOCOLS Draft The processing required to establish/disconnect TIS with Mode S ground interrogators when coverage boundaries are crossed shall be based upon information contained in the capability registers within the aircraft’s Mode S transponder as well as two specific TIS uplink messages. A.3.2.2.4.1 Mode S capability report Transponder register 1016 within the Mode S transponder shall contain bits that indicate the capability level of the aircraft with respect to Mode S functions. This register shall be read by each Mode S ground interrogator that acquires the aircraft. Bit 25 of this register shall be set to “ONE” if the aircraft carries any MSP data link services (i.e. TIS). Note.— This bit merely indicates the presence of MSP data link services on board the aircraft — it does NOT indicate whether any of these services are in use by the aircrew at a given time. A.3.2.2.4.2 MSP capability report Transponder registers 1D16 to 1F16 within the Mode S transponder contain bits which indicate the dynamic state of certain MSP data services on board the aircraft (where defined in applications, e.g. TIS). These registers shall be read 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: Appendix A A-45 MB FIELD DRAFT - Wo
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 117: 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 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?