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 C-74 Technical Provisions for Mode S Services and Extended Squitter C.3.4.5.5 Ground Track Angle This 5-bit (“ME” bits 21 – 25) field shall define the direction (in degrees clockwise from true north) of aircraft motion. The ground track shall be encoded as an unsigned angular weighted binary numeral, with an MSB of 180 degrees and an LSB of 360/32 degrees, with ZERO (0) indicating true north. The data in the field shall be rounded to the nearest multiple of 360/32 degrees. C.3.4.5.6 Ground Speed This 6-bit (“ME” bits 26 – 31) field shall define the aircraft speed over the ground. Coding of this field shall be as specified in Table C-38. Table C-38. TIS-B Aircraft Speed Over-the-Ground Coding Meaning (Binary) (Decimal) (Ground Speed in knots) 00 0000 0 No Ground Speed information available 00 0001 1 Ground Speed < 16 knots 00 0010 2 16 knots ≤ GS < 48 knots 00 0011 3 48 knots ≤ GS < 80 knots *** *** *** 11 1110 62 1936 knots ≤ GS < 1968 knots 11 1111 63 GS ≥ 1968 knots Notes.— 1. The encoding shown in the table represents Positive Magnitude data only. 2. Raw data used to establish the Ground Speed Subfield will normally have more resolution (i.e., more bits) than that required by the Ground Speed Subfield. When converting such data to the Ground Speed Subfield, the accuracy of the data must be maintained such that it is not worse than ±½ LSB where the LSB is that of the Ground Speed Subfield. C.3.4.5.7 Latitude/Longitude The Latitude/Longitude fields in the TIS-B Coarse Airborne Position Message shall be set as specified in §C.2.3.2.3, except that the 12-bit form of CPR coding shall be used. Draft C.3.5 TIS-B AND ADS-R MANAGEMENT MESSAGES The TIS-B/ADS-R Management Messages shall use Extended Squitter format DF=18 and CF=4 to provide information related to the provision of the TIS-B and/or ADS-R Service Volume in the specific airspace being serviced by the local ground broadcast site(s). The TIS-B/ADS-R Management Message shall be used to provide a specific announcement of the Service Volume and the service availability in local airspace where the TIS-B and/or ADS-R service is being supported by the ground infrastructure. C.3.6 TIS-B REPORT GENERATION The information received in TIS-B Messages shall be reported directly to applications, with one exception. The exception is latitude-longitude position information, which is CPR-encoded when it is received, and must be decoded before reporting. In order to accomplish CPR decoding, it is necessary to track received messages, so that even-format and odd-format messages can be combined to determine the latitude and longitude of the target. In the most common case, a particular target will result in TIS-B Message receptions or ADS-B Message receptions, but not both. It is possible, however, for both types of messages to be received for a single target. If this happens, the TIS-B information is processed and reported independently of the ADS-B receptions and reporting. 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 C C-75 As TIS-B Messages are received, the information is reported to applications. All received information elements, other than position, shall be reported directly, including all reserved fields for the TIS-B fine format messages and the entire message content (i.e., including the complete 88-bit content of the DF, CF, AA and “ME” fields of the Extended Squitter Message) of any received TIS-B Management Message (Table C-37, for CF=4). The reporting format is not specified in detail, except that the information content shall be the same as the information content received. The report shall be issued within 0.5 seconds of the message reception. Draft 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: DRAFT - Working Paper ASP TSGWP11-0
Page 213 and 214: Appendix C C-25 Notes.— DRAFT - W
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221 and 222: Appendix C C-33 Msg Bit # "ME” Bi
Page 231 and 232: Appendix C C-43 Notes. — DRAFT -
Page 239 and 240: Appendix C C-51 3. The decoded posi
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 253 and 254: Appendix C C-65 Register 0A16 Figur
Page 259 and 260: Appendix C C-71 Table C-37. CF Fiel
Page 261: 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 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?