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-92 Technical Provisions for Mode S Services and Extended Squitter Version 0 Airborne Velocity Message SUBTYPE Table C-45. Track/Heading and HRD Subfield Airborne Velocity Message “Magnetic Heading Status Bit” Surface Position Message “Ground Track Status Bit” N/A N/A 0 1 or 2 N/A 1 3 or 4 0 N/A 3 or 4 1 N/A Meaning No Valid Track/ Heading or Heading Direction Reference information available Ground Track being reported Heading relative to true north being reported Heading relative to magnetic north being reported ADS-B Report True/Magnetic Heading subfield encoding Notes.— 1. When no valid data is available the “Track/Heading and HRD” parameter may be reported as ALL ZEROs. 2. When receiving ADS-B Version Two (2) Messages, the Track/Heading and HRD information are conveyed within the Operation Status Message. However, when receiving ADS-B Version Zero (0) Messages the equivalent information can be determined for airborne aircraft from the value of the “Subtype” subfield and for Subtype=3 or 4 messages the value of the “Magnetic Heading Status Bit” of the Airborne Velocity Message (Table A-2-9b). When a target aircraft/vehicle is on the surface, a value of 01 should be reported when a Surface Position Message (Table A-2-6) is received with the “Heading/Ground Track Status Bit” set to a value of ONE (1) indicating that the valid ground track data is provided. 3. ADS-B Version Zero (0) Airborne Velocity Messages, Subtypes 3 and 4 always report Heading relative to Magnetic North, never relative to True North. C.5.2.3 AIR REFERENCED VELOCITY REPORTS Draft The requirements for Air Referenced Velocity (ARV) Reports shall apply to the ARV Report Assembly requirements when the target aircraft is broadcasting either ADS-B Version Zero (0) or Version Two (2) Message formats (Table A-2-9b). C.5.2.4 TARGET STATUS REPORTS Appendix A defines a message format using message TYPE Code 29 to convey Aircraft Trajectory Intent information in the form of Trajectory Change Point (TCP) information. A 1090 MHz ADS-B Receiving Subsystem conforming to this Manual does shall not use any message with a TYPE Code of 29 that is received from a ADS-B Version Zero (0) Transmitting Subsystem for the purpose of report generation. Note.— Prior to generation of a Target Status Report, the 1090 MHz ADS-B Receiving Subsystem must positively confirm that any received message with a TYPE Code of 29 has originated from a target aircraft with an ADS-B Version Number other than Zero (0). The ADS-B Version Number can be determined from the contents of the ADS-B Version Number subfield (see §C.2.3.10.5) of the Aircraft Operational Status Message. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris 00 01 00 11
DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Appendix C C-93 C.5.3 1090 MHZ ADS-B VERSION 1 MESSAGE PROCESSING C.5.3.1 ADS-B VERSION ONE (1) MESSAGE TYPES Note.— ADS-B Version One (1) (i.e., 1090 MHz ADS-B Transmitting Subsystem conformant to Appendix B) 1090 MHz ADS-B Messages are the same basic message types as ADS-B Version Two (2). Some messages have different formats and contain additional or eliminated message subfields. For example, the Target State and Status Message changed between ADS-B Version One (1) to ADS-B Version Two (2). ADS-B Version One (1) Transmitting Subsystems use Subtype Zero (0) for the Target State and Status Message, and ADS-B Version Two (2) Transmitting Subsystems use Subtype One (1) to maintain backward compatibility. ADS-B Version Two (2) Receiving Subsystems do not generate ADS-B Reports from ADS-B Version One (1) Target State and Status Messages, but utilize the accuracy and integrity parameters in the Message. See Appendix B for ADS-B Version One (1) Message formats. ADS-B Version One (1) Transmitting Subsystems do not broadcast the Extended Squitter Aircraft Status Message (Subtype 2), the 1090ES TCAS Resolution Advisory (RA) Message. C.5.3.1.1 Message TYPE Codes The first 5-bit field in every 1090 MHz ADS-B Message contains the message format TYPE. The TYPE Code (i.e., format type) is shall be used to differentiate the messages into several classes: airborne position, airborne velocity, surface position, identification, aircraft status, etc. The general definition for all ADS-B Messages Types used for ADS-B Version One (1) Messages has been retained for ADS-B Version Two (2) Messages. C.5.3.2 VERSION TWO (2) ADS-B REPORTS GENERATED USING VERSION ONE (1) MESSAGES Note.— The following subparagraphs summarize the ADS-B Report generation requirements for ADS-B Version Two (2) systems when receiving ADS-B Version One (1) ADS-B Messages. The contents of ADS-B Reports are composed primarily from the information received from airborne aircraft in Airborne Position Messages and Airborne Velocity Messages or for aircraft/vehicles on the airport surface in Surface Position Messages. Many of the parameters contained within these messages are encoded the same, and occupy the same positions with the overall message structure, for both ADS-B Version One (1) and for ADS-B Version Two (2) Messages. However, in a few cases the decoding and/or report assembly processing must be handled differently for ADS-B Version One (1) Messages as compared to that required by this Manual for ADS-B Version Two (2) Messages. The following subparagraphs describe the required use of ADS-B Version One (1) Messages for ADS-B Report generation by a ADS-B Version Two (2) compliant ADS-B Receiving Subsystem. Draft C.5.3.2.1 Navigation Integrity Category (NIC) As defined by Table C-2, ADS-B Version Two (2) Surface and Airborne Position Messages have associated with each specific ADS-B Message TYPE Code a corresponding Horizontal Containment Limit (RC) and Navigation Integrity Category (NIC). The TYPE Code is used along with the NIC Supplement-A in the Operational Status Message to decode the NIC. The Surface and Airborne Position Message TYPE Codes associated with ADS-B Version One (1) 1090 MHz ADS-B Messages along with the NIC Supplement-A are shall be used to map to the NIC values shown in Table B-2 for the purpose of generating ADS-B Reports. 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:
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 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 279: 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?