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-102 Technical Provisions for Mode S Services and Extended Squitter A.3.3.3.2.5 In the case of a request from the ground to terminate the service for a particular register, the termination of the service shall be confirmed by announcing to the ground an MSP packet on downlink channel 3, as shown in Table A-3-2, and with a value of 4 in the CI field. A.3.3.3.2.6 In the case of a request from the ground to terminate the service for all contracts to a particular II code, the termination of the service shall be confirmed by announcing to the ground an MSP packet on downlink channel 3, as shown in Table A-3-2, and with a value of 5 in the CI field. A.3.3.3.2.7 When the transponder register service fails for an established contract, the contract shall be terminated by the airborne application. This will be indicated by announcing to the ground an MSP packet on the downlink channel 3, as shown in Table A-3-2, and with a value of 7 in the CI field. Transponder register service shall be deemed to have failed when any of the parameters specified to be monitored in the negotiation of the contract are not being updated at the specified minimum rate. A.3.3.3.2.8 When a contract is refused due to an invalid value of the EC field in the contract request, this shall be indicated by announcing to the ground an MSP packet on downlink channel 3, as shown in Table A-3-2, and with a value of 15 in the CI field. A.3.3.3.2.9 If any message is not extracted from the transponder by a ground interrogator within 30 seconds, the aircraft subnetwork shall cancel the message and generate a delivery failure notice (i.e. the TZ timer expires), which shall be delivered to the aircraft MSP service provider. When a delivery failure notice is received the service shall be automatically terminated by the dataflash function with no indication to the ground system. Note.— This is to prevent the transponder message queues being blocked when the ground interrogator stops supplying the message extraction service, either due to a fault or loss of cover. It is the responsibility of the ground application to monitor the dataflash service taking this into account. A.3.3.3.2.10 When the transponder has not been selectively interrogated by a Mode S interrogator with a particular II code for 60 seconds (determined by monitoring the IIS subfield in all accepted Mode S interrogations), all dataflash contracts related to that II code shall be cancelled with no indication to the ground system. A.3.3.3.3 SERVICE PROVISION Draft On the receipt of a dataflash request, the requested parameters shall be monitored and transferred to the ground using the Mode S air-initiated protocols directed to the II code that was contained in the requesting interrogation. In order to prevent the flooding of the transponder with dataflash messages, an upper limit of ten messages in a six-second period shall be imposed. When the limit of ten messages within a six-second period is reached, further messages shall be queued until they can be sent. Messages queued in this way shall respond with a CI field value of 6. If, after initiating a dataflash message to the ground, the change criterion is met again prior to the message being entered into the transponder for announcement, the message is considered stale and shall be replaced by the most up-to-date information. A.3.3.3.4 DOWNLINK MESSAGE STRUCTURE The information shall be transferred in a downlink MSP packet with the channel number M/CH = 3. The format is shown in Table A-3-2. The first two bytes of the user data (UD) field shall contain a dataflash header (DH) which shall be identical to the DH field that was contained in the request for service. A.3.3.3.4.1 Bits 17 to 31 of UD form the II code contract report (CR) field in which each bit shall indicate that at least one contract is active with the II code, which the bit represents when it is set to a ONE; otherwise, there are no active contracts with that II code. 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-103 A.3.3.3.4.2 Bits 32 to 36 of UD are not assigned. A.3.3.3.4.3 Bits 37 to 40 of UD form the contract information (CI) field which shall be interpreted as follows: CI field value Meaning 0 Response to existing contract 1 New contract established 2 New contract not accepted, or existing contract terminated, due to no transponder register data service 3 New contract not accepted due to maximum number of contracts already being serviced 4 Contract terminated for the DH in this response due to a request from the ground 5 All contracts terminated for the II code that delivered the MSP packet having an EC value of 15 that requested this response 6 Response has been queued due to the limit of six dataflash messages in a ten second period 7 Contract terminated due to failure of the register data service 8 to 14 UnassignedReserved 15 New contract not accepted due to invalid number in EC field of requested uplink MSP packet A.3.3.3.4.3.1 When the CI field is equal to ZERO, the response shall be as requested by the RDS field in the dataflash header of the contract (see §A.3.2.6.3.1.2.2). When the CI field is not equal to ZERO, the response shall only contain bits 1 to 40 of the user data field on downlink MSP 3 (see Table A-3-2). A.3.3.3.5 DATA EXTRACTION BY MODE S GROUND STATIONS Draft The dataflash transaction shall be announced as a downlink frame in response to interrogations UF 4, 5, 20, or 21. The transaction announced shall be either a single segment Comm-B frame or a two segment Comm-B frame, as requested by the contract negotiations. The air-directed Comm-B first segment shall contain the MSP header, dataflash header, and control information for that particular contract. In the case of a contract for a single segment response, if the data is required, it is acquired directly by the ground station extracting the register in question. (Reserved for position request) The description of this channel has not yet been developed. A.3.3.4 DOWNLINK MSP CHANNEL 4 A.3.3.5 DOWNLINK MSP CHANNEL 5 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: DRAFT - Working Paper ASP TSGWP11-0
Page 77 and 78: Appendix A A-53 MB FIELD DRAFT - Wo
Page 79 and 80: Appendix A A-55 MB FIELD 1 BDS A,8
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: 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 177 and 178:
Appendix B B-41 CF value ICAO/Mode
Page 179 and 180:
Page 181 and 182:
Appendix B B-45 MB FIELD DRAFT - Wo
Page 183 and 184:
Page 185 and 186:
Appendix B B-49 MB FIELD DRAFT - Wo
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?