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-94 Technical Provisions for Mode S Services and Extended Squitter C.5.3.2.2 Movement Notes.— 1. The quantization in the Movement subfield conveyed in Version Two (2) Surface Position Messages is different than the Movement subfield contained in Version One (1). The encoding of the Version One (1) Movement subfield is the same as that contained in Version Zero (0) and is defined in §A.2.3.3.1. Note.— 2. ADS-B Applications must use the version number to properly decode the Movement subfield. C.5.3.2.3 ADS-B Version Number Note.— The format of the Aircraft Operational Status Message differs between the ADS-B Version One (1) Message format shown in Table B-2-101 and the ADS-B Version Two (2) Message format specified in §C.2.3.10 of this Manual. There are additional parameters in ADS-B Version Two (2) Aircraft Operational Status Messages that are not contained in ADS-B Version One (1) Messages. A ADS-B Version Two (2) Receiving Subsystem willshall, as a default, assume the received messages are using ADS-B Version Zero (0) Message format unless, or until, an Aircraft Operational Status Message is received and the ADS-B Version Number is confirmed to be other than Zero (0). However, inIn the case of a ADS-B Version Two (2) Subsystem’s reception of an Aircraft Operational Status Message, the ADS-B Receiving Subsystem will shall decode “ME” bits 41-43 and determine if the target aircraft is broadcasting messages that are ADS-B Version Zero (0), Version One (1), or Version Two (2), or higher, and then decode the remainder of the message in accordance with the message format applicable to that ADS-B Version Number. Note.— The ADS-B Version Number determined from the decoding of the Version Number subfield of the Aircraft Operational Status message must be retained and associated with the specific target since it is used in determining the applicable formats to be used for the decoding of the other message types. C.5.3.2.4 Emitter Category The ADS-B Report Assembly Function will shall extract “TYPE” and “ADS-B Emitter Category” from the Aircraft Identification and Category Message (Table A-2-8) and encode the “Emitter Category” field. The Emitter Category conveyed in the Aircraft Identification and Category Message is shall be mapped into the ADS-B Report, Emitter Category field as specified by Table A-2-8. However, it must be noted that in Draft Note.— In the ADS-B Version One (1) Aircraft Identification and Category Message, the Emitter Category subfield conveys a subset of the Emitter Categories allowed by the ADS-B Report. C.5.3.2.5 A/V Length and Width Code This parameter is onlyshall be included in the ADS-B Report when reporting on an aircraft or vehicle that is on the airport surface using the coding specified in Table C-46. When no A/V Length and Width Code is available, the A/V Length and Width Code parameter will shall not be included in the ADS-B Report. 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-95 Table C-46. Version One (1) “Aircraft/Vehicle Length and Width Code” Decoding A/V - L/W Code (Decimal) Length Code ME ME ME Bit 21 Bit 22 Bit 23 Width Code ME Bit 24 Upper-Bound Length and Width for Each Length/Width Code Length Width (meters) (meters) 0 0 0 0 0 No Data or Unknown 1 0 0 0 1 15 23 2 3 0 0 1 0 1 25 28.5 34 4 5 0 1 0 0 1 35 33 38 6 7 0 1 1 0 1 45 39.5 45 8 9 1 0 0 0 1 55 45 52 10 11 1 0 1 0 1 65 59.5 67 12 13 1 1 0 0 1 75 72.5 80 14 15 1 1 1 0 1 85 80 90 Note.— In Appendix B encoding of decimal ZERO (0) A/V Length/Width Code was specified as Length=15 meters and Width=11.5 meters. However, there may be ADS-B Transmitting Subsystems implemented that are consistent with the interpretation of the ICAO SARPs of defining an ALL ZERO condition to be interpreted as “No Data or Unknown.” Version TWO (2) ADS-B Reports based on receiving an ALL ZERO A/V Length/Width Code from a Version One (1) Transmitting Subsystem will be reported as “Unknown.” C.5.3.2.6 Emergency/Priority Status The Emergency/Priority Status conveyed in the Aircraft Status Message (Table B-2-101) and the Target State and Status Message (Table B-2-98) will shall be directly mapped into the ADS-B Report, Emergency/Priority Status field. Draft C.5.3.2.7 Capability Codes The ADS-B Report Assembly Function will shall extract the “Capability Class Codes” data from Aircraft Operational Status Messages and the Target State and Status Messages and provide the Capability Class Codes to the user application in the ADS-B Report. When valid “Capability Class” data is not available for a given parameter, then the Capability Class data sent to the user application for that parameter is shall be set to ALL ZEROs. When an ADS-B Report is generated and when the only received update to the “Capability Class” data has come from a Target State and Status Message, the reported value of all Capability Class parameters are shall be based on the most recently received Operational Status Message, except updated with the data (i.e., TCAS parameter) received in the subsequent Target State and Status Message. C.5.3.2.8 Source Integrity Level (SIL) The Source Integrity Level (SIL) defines the probability of the integrity containment region described by the NIC parameter being exceed for the selected geometric position source, including any external signals used by the source. In ADS-B Version One (1), the Surveillance Integrity Level parameter represented this probability as well as other elements of integrity. The Surveillance Integrity Level may have also included the reliability of the aircraft systems given by a failure rate corresponding to the equipment design 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: DRAFT - Working Paper ASP TSGWP11-0
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 281: 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 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?