Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

A-100 Technical Provisions for Mode S Services and Extended Squitter EC field value Meaning 6 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris 112 bits of CQ plus CT follows ST. Same as for EC values 4 and 5 above except: report only when the threshold is crossed (in either direction). 7 to 14 Not assignedReserved 15 Cancel all contracts for the II code in this request. A.3.2.6.3.1.4.2 Stable time field (ST) 4 bits The ST field shall be the 4 bits following the EC field. The decimal value of ST shall indicate in seconds how long the changed data have been stable, to within the change quanta specified in the CQ field, before a message shall be initiated. A value of “ZERO” in this subfield shall indicate that there is no minimum stable time and any change immediately initiates a message. The significance of the ST shall be dependent on which EC mode is being used. For EC Modes 4 and 5, regarding stability whilst above/below a threshold, if a parameter value remains above/below the defined threshold for greater than the ST time then a dataflash message shall be generated even if the value does not remain stable to within one quantum. Subsequent quantum changes which are stable for greater than the ST time shall generate further dataflash messages until the value falls below/rises above the threshold. A.3.2.6.3.1.5 Change fields — change quanta (CQ) and change threshold (CT) These fields shall be present when indicated in EC. For a transponder register service (i.e. for BDS1 and BDS2 from 1 to 255 inclusive), CQ shall be contained in bits 41 to 96 of the MSP 6 user data field. CT, when required, shall be contained in bits 97 to 152 of the MSP 6 user data field. The quantum value in the CQ field shall be indicated in the same units and resolution as those specified for the register being monitored. It shall specify the amount by which the parameter must change, from its value at the initialization of the contract, and thereafter from the value last reported by a dataflash response, in order to trigger a new dataflash response on downlink MSP channel 3 (see Table A-3-1). A.3.2.6.3.2 Local system management Draft The purpose of the local system management is to provide a particular ground-air service request that can be defined locally to meet particular requirements (such as for ground station “remote setting” of parameters at the far-field monitor). (Reserved for response to air-to-ground service request) The description of this channel has not yet been developed. (Reserved for trajectory negotiation) The description of this channel has not yet been developed. A.3.2.7 UPLINK MSP CHANNEL 7 A.3.2.8 UPLINK MSP CHANNEL 8 A.3.2.9 UPLINK MSP CHANNELS 9 TO 63 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix A A-101 These channels have not been assigned. A.3.3 DOWNLINK MSP CHANNELS The following sections are numbered A.3.3.X, where “X” is the decimal number equivalent to the downlink MSP channel number. This is done to allow definitions of the hitherto undefined formats to be inserted without affecting paragraph numbers. A.3.3.1 DOWNLINK MSP CHANNEL 1 (Reserved for specific services management) The description of this channel has not yet been developed. This channel has not been assigned. A.3.3.3.1 PURPOSE DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris A.3.3.2 DOWNLINK MSP CHANNEL 2 A.3.3.3 DOWNLINK MSP CHANNEL 3 Dataflash is a service which announces the availability of information from air-to-ground on an event-triggered basis. When implemented, bit 31 of the register accessed by BDS code 1,D shall be set to a 1. Note.— This is an efficient means of downlinking information which changes occasionally and unpredictably. A.3.3.3.2 SERVICE INITIATION AND TERMINATION Draft A.3.3.3.2.1 The dataflash service shall be initiated or discontinued by a service request and is received on uplink MSP channel 6 with a decimal value of ONE in the service request (SR) header, which is contained in the first byte of the user data field. This indicates that the rest of the user data field shall contain a dataflash request. On the receipt of such a request, a dataflash message from the register concerned with the request shall immediately be made available and announced to the ground regardless of the setting of the RDS field in the contract request and of any event criteria. The response shall be as follows. A.3.3.3.2.2 When the requested register is being serviced, the contract shall be established and an MSP packet as specified in Table A-3-2 shall be announced to the ground on MSP channel 3. The CI field must be set to a value of 1. The message shall be used by the ground system to confirm that the service has been initiated. A.3.3.3.2.3 If the requested register is not being serviced, the contract shall not be established. This shall be indicated by announcing the MSP packet on downlink MSP channel 3 to the ground containing only bits 1 to 40 as specified in Table A-3-2, and with a value of 2 in the CI field. A.3.3.3.2.4 If the maximum number of contracts that can be supported is already established, then the new contract shall be refused. This shall be indicated by announcing to the ground an MSP packet on downlink channel 3, as specified in Table A-3-2, and with a value of 3 in the CI field. 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 73 and 74: Appendix A A-49 MB FIELD DRAFT - Wo
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 121 and 122: Appendix A A-97 a) the PI sends a T
Page 123: Appendix A A-99 This subfield shall
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 175 and 176:
Appendix B B-39 MB FIELD DRAFT - Wo
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?