Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

CD-26 Technical Provisions for Mode S Services and Extended Squitter Figure CD-8. Determination of globally unambiguous position from a T = 0 and T = 1 report. CD.2.4.7.8 SUMMARY OF CPR ENCODING CHARACTERISTICS The CPR encoding characteristics are summarized as follows: Lat/lon encoding 17 bits for each Nominal airborne resolution 5.1 metres Nominal surface resolution 1.2 metres Maximum unambiguous encoded range, airborne 333 km (180 NM) Maximum unambiguous encoded range, surface 83 km (45 NM) Draft Provision for globally unique coding using two reports from a T = 0 and T = 1 report. Zone no. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Equator Transition latitude (degrees) Greenwich meridian Zone no. T = 0 (Even) zone boundary T = 1 (Odd) zone boundary Table CD-4. Transition latitudes Transition latitude (degrees) Actual target position T = 0 (Even) zone and T = 1 (Odd) zone locations coincide Zone no. T = 0 (Even) zone location T = 1 (Odd) zone location Transition latitude (degrees) Zone no. Transition latitude (degrees) 59 10.4704713 44 42.8091401 29 61.0491777 14 76.3968439 58 14.8281744 43 44.1945495 28 62.1321666 13 77.3678946 57 18.1862636 42 45.5462672 27 63.2042748 12 78.3337408 56 21.0293949 41 46.8673325 26 64.2661652 11 79.2942823 55 23.5450449 40 48.1603913 25 65.3184531 10 80.2492321 54 25.8292471 39 49.4277644 24 66.3617101 9 81.1980135 53 27.9389871 38 50.6715017 23 67.3964677 8 82.1395698 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix CD CD-27 Zone no. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Transition latitude (degrees) Zone no. Transition latitude (degrees) Zone no. Transition latitude (degrees) Zone no. Transition latitude (degrees) 52 29.9113569 37 51.8934247 22 68.4232202 7 83.0719944 51 31.7720971 36 53.0951615 21 69.4424263 6 83.9917356 50 33.5399344 35 54.2781747 20 70.4545107 5 84.8916619 49 35.2289960 34 55.4437844 19 71.4598647 4 85.7554162 48 36.8502511 33 56.5931876 18 72.4588454 3 86.5353700 47 38.4124189 32 57.7274735 17 73.4517744 2 87.0000000 46 39.9225668 31 58.8476378 16 74.4389342 45 41.3865183 30 59.9545928 15 75.4205626 CD.3. IMPLEMENTATION GUIDELINES FOR APPLICATIONS CD.3.1 DATAFLASH CD.3.1.1 OVERVIEW Dataflash is a service which announces the availability of information from air-to-ground on an event-triggered basis. This is an efficient means of downlinking information which changes occasionally and unpredictably. A contract is sent to the airborne application through the Mode S transponder and the ADLP using an uplink Mode S specific protocol (MSP) (MSP 6, SR = 1) as specified in Annex 10 Volume III, Appendix to Chapter 5. This uplink MSP packet contains information specifying the events which should be monitored regarding the changes of data in a transponder register. When the event occurs, this is announced to the ground installation using the AICB protocol. The ground installation may then request the downlink information which takes the form of a downlink MSP packet on channel 3 constituted of one or two linked Comm-B segments. The second segment is a direct copy of the relevant transponder register specified in the contract. The ground system with the embedded dataflash application should determine if an aircraft supports the dataflash protocol as follows: Draft • if bit 25 of transponder register 1016 is set to 1, the system will extract transponder register 1D16, then, • if bit 6 and bit 31 of transponder register 1D16 are set to 1, then the aircraft supports the dataflash service. CD.3.1.2 MINIMUM NUMBER OF CONTRACTS The minimum number of contracts activated simultaneously that can be supported by the airborne installation should be at least 64. In the case of a software upgrade of existing installations, at least 16 dataflash contracts should be supported. CD.3.1.3 CONTRACT REQUEST FOR A TRANSPONDER REGISTER NOT SERVICED BY THE AIRBORNE INSTALLATION On the receipt of a dataflash service request, a downlink dataflash message should immediately be announced to the ground regardless of any event criteria. This message is used by the ground system to confirm that the service has been initiated. The message will only consist of one segment. In the case of a service request for an unavailable transponder register, the message sent to the ground should only contain bits 1 to 40 of the downlink message structure with a CI field value of 2. This value will indicate to the ground system that the service request cannot be honored because of the unavailability of the transponder register. The service will then be terminated by the airborne dataflash function, and the ground system should notify the user which has initiated the request that the service request cannot be honored by the airborne installation. 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:
Page 77 and 78:
Page 79 and 80:
Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
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:
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: DRAFT - Working Paper ASP TSGWP11-0
Page 287 and 288: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 291 and 292: Appendix CD CD-7 too many broadcast
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 307 and 308: Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 309: DRAFT - Working Paper ASP TSGWP11-0
Page 315 and 316: Appendix CD CD-31 CD.4 IMPLEMENTATI
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?