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-96 Technical Provisions for Mode S Services and Extended Squitter by each Mode S ground interrogator that acquires the aircraft if the Mode S capability report indicates that the aircraft carries MSP data link services. Bit 2 of the MSP capability report register 1D16 shall be set to “ONE” if TIS support is desired; otherwise, the bit shall be set to “ZERO”. Setting and resetting this bit shall be done in conjunction with the generation of TIS “service connect requests” (TSCR) and “service disconnect requests” (TSDR) downlink messages as specified in section §A.4.3.2 for downlink broadcast identifier 0216. A.3.2.2.4.3 Keep-alive timer In the absence of TIS traffic data messages, TIS keep-alive messages shall be uplinked by the Mode S ground interrogator. The TIS airborne processor shall keep a timer that measures the time interval between TIS uplink messages received. The timer shall be reset each time a TIS uplink message is received. If this “keep-alive” timer reaches 60 seconds (the “keep-alive” time parameter for TIS), the TIS ground-to-air service shall be declared to have failed and TIS support is no longer available from the Mode S ground interrogator. Note.— The data link service processing for TIS must receive periodic uplink messages from the Mode S ground interrogator in order to ensure that the ground-to-air link is maintained and that the ground TIS support is continuing. A.3.2.2.4.4 TIS principal interrogator code protocol Note.— Each TIS uplink message is accompanied by a 4-bit interrogator identifier (II) code or a 6-bit surveillance identifier (SI) code (contained in the SD field) that identifies which Mode S ground interrogator (or interrogator cluster) generated it. The II or SI code shall be used to generate a 7-bit ILAB code. If the Mode S ground interrogator is identified via a 4-bit II code, then the high-order three bits of the ILAB shall be cleared to zero and the II code shall be contained in the low-order 4 bits of the ILAB. Otherwise, if the Mode S ground interrogator is identified via a 6-bit SI code, then the high-order bit of the ILAB shall be set to one and the SI code shall be contained in the low-order 6 bits of the ILAB. At any given moment, only one Mode S ground interrogator shall be declared as the “principal interrogator” (PI). In areas having overlapping Mode S coverage by interrogators with different ILAB codes, an “alternate interrogator” (AI) shall also be declared. The TIS protocol for handling ILAB codes shall be as defined below. A.3.2.2.4.5 TIS display generation Draft If TIS messages are received from more than one interrogator at a time, only those TIS messages from the interrogator currently declared as the PI shall be displayed to the pilot. TIS messages from interrogators other than the PI shall be discarded, except for the AI processing described below. A.3.2.2.4.6 Alternate interrogator (AI) identification The ILAB code of the most recently received TIS message not from the PI shall be retained as the AI. In the case that no TIS messages have been received from interrogators other than the PI (as described below), no current AI shall be defined. The AI definition shall be initialized to the “none state” when TIS is enabled (TSCR) or disabled (TSDR) by the pilot. A.3.2.2.4.7 Principal interrogator (PI) identification The ILAB code of the first Mode S ground interrogator to respond to the TSCR downlink message with a TIS uplink message becomes the PI. The PI shall be retained until either: DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix A A-97 a) the PI sends a TIS “goodbye” uplink message; or b) there is a TIS “keep-alive” time-out on the PI. In either case, the AI (if one is present) shall be promoted to PI and its TIS messages shall now be displayed. A new AI shall now be identified. If there was no available AI, no PI is now available and the airborne TIS processor shall be in the “no TIS supported” state. This state shall continue until a TIS message (either traffic or keep-alive) is received from a Mode S ground interrogator. When such an uplink message is received, the ILAB code associated with the message shall become the PI and the airborne processing shall resume the display of TIS. The PI definition shall be initialized to the “none” state when TIS is enabled (TSCR) or disabled (TSDR) by the pilot. (Reserved for ground-to-air alert) The description of this channel has not yet been developed. (Reserved for ground-derived position) The description of this channel has not yet been developed. A.3.2.3 UPLINK MSP CHANNEL 3 A.3.2.4 UPLINK MSP CHANNEL 4 A.3.2.5 UPLINK MSP CHANNEL 5: ACAS SENSITIVITY LEVEL CONTROL The description of this channel has not yet been developed. Bit 5 in Register 1D16 shall be set to zero at all times. Notes.— 1. This service allows ground stations to control the Sensitivity Level of ACAS by sending a message to the transponder for delivery to ACAS. This service is required when a transponder supports an ACAS installation. Refer to Annex 10, Vol. IV §4.3.8.4.2 for complete requirements. 2. ACAS installed and operational is communicated in the Data Link Capability Report (Register 1016). Therefore, this service is not required to be marked in Register 1D16. A.3.2.6.1 PURPOSE Draft A.3.2.6 UPLINK MSP CHANNEL 6: DATAFLASH This service shall provide a means of requesting access to services supported by the aircraft. When implemented, bit 6 of the register accessed by BDS code 1,D shall be set to a 1. A.3.2.6.2 FORMAT DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris The request shall be transferred in an uplink MSP packet with the channel number set to 6 and, in the case of a long form MSP packet, with SP set to “ZERO”. The first byte of the user data field shall contain a service request (SR) header. The contents and format of the service request are specified by the application. 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 119: DRAFT - Working Paper ASP TSGWP11-0
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:
Appendix B B-35 MB FIELD DRAFT - Wo
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?