Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

C-84 Technical Provisions for Mode S Services and Extended Squitter C.4.5 ADS-R REPORT PROCESSING ADS-R Reports are to be maintained and output for DF=18, with CF=6 ADS-R Messages. ADS-R Reports are to be provided for both ADS-B Version ONE (1) and Version TWO (2) formatted ADS-R Messages in accordance with the message formats provided in §C.4. C.5 Provisions for Backward Compatibility with Version 0 and Version 1 ADS-B Systems This section defines: DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris C.5.1 INTRODUCTION C.5.1.1 PURPOSE OF THIS SECTION a) the formats and coding for Extended Squitter ADS-B Messages that are broadcast by ADS-B Version Zero (0), RTCA DO-260/EUROCAE ED-102 conformant 1090 MHz ADS-B Subsystems; b) the formats and coding for extended squitter ADS-B Messages that are broadcast by ADS-B Version One (1), RTCA DO-260A conformant 1090 MHz ADS-B Subsystems; c) how the ADS-B report generation function of ADS-B Version Two (2) 1090 MHz ADS-B Receiving Subsystems is to utilize messages received from targets that are broadcasting with either ADS-B Version Zero (0) or ADS-B Version One (1) message formats. C.5.1.2 MESSAGE VERSION NUMBER The ADS-B Version Number for all 1090 MHz ADS-B Messages originating for each specific ADS-B target is shall be determined from the decoding of the ADS-B Version Number subfield of the Aircraft Operational Status Message. An ADS-B Version Two (2) Receiving Subsystem shall initially assumes that the messages conform to ADS-B Version Zero (0) message formats, until or unless, a received ADS-B Version Number data indicates otherwise. The ADS-B Version Number is shall be retained and associated with all messages from that specific target. This ADS-B Version Number is shall be used for determining the applicable message formats to be applied for the decoding of all 1090 MHz ADS-B Messages received from that target. Draft C.5.2 1090 MHZ ADS-B VERSION ZERO (0) MESSAGE PROCESSING C.5.2.1 ADS-B VERSION ZERO (0) MESSAGE TYPES Table C-39 provides specifies those ADS-B Version Zero (0) (i.e., originating from a 1090 MHz ADS-B Transmitting Subsystem conformant to the requirements of Appendix A) 1090 MHz ADS-B Messages that are toshall be used for ADS-B report generation by a ADS-B Version Two (2) conformant 1090 MHz ADS-B Receiving Subsystem. Note.— Table C-39 lists only those ADS-B Version Zero (0) 1090 MHz ADS-B Message types that are required to be received and used for ADS-B report generation by a ADS-B Version Two (2) 1090 MHz ADS- B Receiving Subsystems. The other ADS-B Version Zero (0) ADS-B Messages Types defined in Appendix A, including Messages Types 29 and 30, are not to be used by ADS-B Version Two (2) ADS-B Receiving Subsystems for the purpose of ADS-B report generation. 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-85 Message Format TYPE Code(s) 1 through 4 Table C-39. Version Zero (0) ADS-B Message Types Assignment Nominal Broadcast Rate Extended Squitter Identification and Category 5.0 s airborne/10.0 s surface 5 through 8 Extended Squitter Surface Position 0.5 s in motion/5.0 s stationary 9 through 18 and 20 through 22 Extended Squitter Airborne Position 0.5 s 19 Extended Squitter Airborne Velocity 0.5 s 28 Extended Squitter Aircraft Status (e.g., emergency/priority) 1.0 s 31 Aircraft Operational Status 1.7 s C.5.2.1.1 Message TYPE Codes The first 5-bit field in every 1090 MHz ADS-B Message shall contains the message format TYPE. As shown in Table C-40, the TYPE Code (i.e., format type) is shall be used to differentiate the ADS-B Messages into several classes: airborne position, airborne velocity, surface position, identification, aircraft status, etc. Notes.— 1. The general definition for all ADS-B Messages Types used for ADS-B Version Zero (0) ADS-B Messages has been retained for ADS-B Version One (1) and ADS-B Version Two (2) Messages. It must be noted for ADS-B Version Zero (0) ADS-B Messages, format TYPE Code 29 was defined but the corresponding messages are not to be transmitted. For ADS-B Version Zero (0) ADS-B Subsystems, TYPE Code 29 was associated with intent messages conveying Trajectory Change Point (TCP) information. Although the message formats for TCP related messages were defined within Appendix A, the requirements and the associated test procedures prohibited the broadcast of such messages. 2. Appendix A defined TYPE Code 30 for Aircraft Operational Coordination Messages. The requirements and associated provisions for Aircraft Operational Coordination Messages have now been withdrawn by this Edition of this Manual. Although Appendix A (i.e., Version Zero) conformant implementations are not prohibited from transmitting Aircraft Operational Coordination Messages (i.e., using TYPE Code 30), ADS-B Version Two (2) conformant ADS-B Receiving Subsystems have no requirement for the reception and processing of these broadcasts. Draft ADS-B Version Two (2) ADS-B Receiving Subsystems will shall process ADS-B Messages based only on the reception of ADS-B Version Zero (0) ADS-B Messages with ADS-B Message TYPE Code values of 0 through 22, 28 and 31. 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: DRAFT - Working Paper ASP TSGWP11-0
Page 227 and 228: Appendix C C-39 Notes.— DRAFT - W
Page 229 and 230: Appendix C C-41 Notes.— DRAFT - W
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 271: 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 315 and 316: Appendix CD CD-31 CD.4 IMPLEMENTATI
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?