Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

C-42 Technical Provisions for Mode S Services and Extended Squitter C.2.4.4 TERMINATION OF EXTENDED SQUITTER BROADCAST If input to Register 05 16, or 06 16 stops for 60 seconds, broadcast of the associated Extended Squitter type shall be discontinued until data insertion is resumed. The insertion of altitude by the transponder shall satisfy the minimum requirement for continuing to broadcast the airborne position squitter. If input to Register 09 16 stops for 2.6 seconds, broadcast of the associated Extended Squitter type shall be discontinued until data insertion is resumed. Notes.— DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris 1. Until timeout, an Extended Squitter type may contain an “ME” field of ALL ZEROs. 2. Continued transmission for 60 seconds is required so that receiving aircraft will know that the data source for the message has been lost. C.2.4.5 REQUIREMENTS FOR NON-TRANSPONDER DEVICES Non-Transponder Devices shall provide the same functionality for initialization, Register timeout and broadcast termination as specified for the transponder case in §C.2.4.1 through §C.2.4.3. a. A Non-Transponder Device shall not broadcast acquisition squitters, and b. A Non-Transponder Device operating on the surface shall continue to broadcast DF=18 Messages with the TYPE Code=0 at a rate specified for the Surface Position Message, even though it has lost its navigation input. Note.— Continued broadcast of the Surface Position Message is needed to support the operation of surface multi-lateration systems. C.2.5 GENERAL FORMATTER/MANAGER (GFM) Note.— The General Formatter/Manager (GFM) is the name that will be used to refer to the function that formats messages for insertion in the Extended Squitter registers. In addition to data formatting, there are other tasks that have to be performed by this function. C.2.5.1 NAVIGATION SOURCE SELECTION Draft The GFM shall be responsible for the selection of the default source for aircraft position and velocity, the commanded altitude source, and for the reporting of the associated position and altitude errors. C.2.5.2 LOSS OF INPUT DATA The GFM shall be responsible for loading the registers for which it is programmed at the required update rate. If for any reason data is unavailable for a time equal to twice the update interval or 2 seconds (whichever is greater), the GFM shall ZERO old data (on a per field basis) and insert the resulting message into the appropriate register. Note.— For Register 0516 and 0616 a loss of position data would cause the GFM to set the Format TYPE Code to ZERO as the means of indicating “no position data” since ALL ZEROs in the lat/lon fields is a legal value. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix C C-43 Notes. — DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris C.2.5.3 SPECIAL PROCESSING FOR FORMAT TYPE CODE ZERO C.2.5.3.1 Significance of Format TYPE Code Equal to Zero 1. Format TYPE Code ZERO (0) is labeled “no position information.” This is intended to be used when the lat/lon information is not available or invalid, and still permit the reporting of baro altitude loaded by the transponder. The principal use of this message case is to provide ACAS the ability to passively receive altitude. 2. Special handling is required for the airborne and Surface Position Messages because a CPR encoded value of ALL ZEROs in the Lat/Lon field is a valid value. C.2.5.3.2 Broadcast of Format TYPE Code Equal to Zero Format TYPE Code 0 shall only be set by the following events: a. Airborne Position or Surface Position (Register 0516, and 0616) has not been loaded by the GFM for 2 seconds. In this case the transponder clears the entire 56 bits of the register that timed out. (In the case of the Airborne Position register, the altitude subfield is only ZEROed if no altitude data is available). Transmission of the Airborne and Surface Position Extended Squitter that broadcasts the timed out register shall itself stop in 60 seconds except for the Airborne Position Message when Altitude is still available. Broadcast of this Extended Squitter shall resume when the GFM begins to insert data into the register. b. The GFM determines that all navigation sources that can be used for the Extended Squitter airborne or Surface Position Message are either missing or invalid. In this case the GFM can clear the Format TYPE Code and all other fields of the airborne position, surface position and insert this zeroed message in the appropriate register. This should only be done once so that the transponder can detect the loss of data insertion and suppress the broadcast of the related squitter. Note that in all of the above cases, a Format TYPE Code of ZERO contains a message of ALL ZEROs. The only exception is the airborne position format that may contain barometric altitude and surveillance status data as set by the transponder. There is no analogous case for the other Extended Squitter format types, since a ZERO value in any of the fields indicates no information. No other squitter types are broadcast with TYPE Code equal ZERO (0). Draft C.2.5.3.3 Reception of Format TYPE Code Equal to Zero If a squitter with format TYPE Code equal to ZERO (0) is received, it shall be checked to see if altitude is present. If altitude is not present, the message shall be discarded. If altitude is present, it may be used to update altitude. An Extended Squitter containing Format TYPE Code ZERO shall only be used to update the altitude of an aircraft already in track. Note.— For ACAS, this could be an aircraft that was being maintained via hybrid surveillance when the position data input failed. In this case, altitude only could be used for a short period of time. Interrogation would have to begin at the update rate for that track to ensure update of range and bearing information on the display. C.2.5.4 HANDLING OF EVENT-DRIVEN PROTOCOL The Event-Driven interface protocol shall provide a general-purpose interface into the transponder function for either those messages beyond those that are regularly transmitted all the time (provided input data is available), or those that are transmitted at a fixed periodic rate. This protocol shall operate by having the transponder broadcast a message once each time the Event-Driven register is loaded by the GFM. Note.— This gives the GFM complete freedom in setting the update rate (up to a maximum) and duration of broadcast for applications such as emergency status and intent reporting. 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: DRAFT - Working Paper ASP TSGWP11-0
Page 181 and 182: Appendix B B-45 MB FIELD DRAFT - Wo
Page 185 and 186: Appendix B B-49 MB FIELD DRAFT - Wo
Page 193 and 194: Appendix C C-5 Table C-2. “TYPE
Page 199 and 200: Appendix C C-11 C.2.3.2.2 Time Sync
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 227 and 228: Appendix C C-39 Notes.— DRAFT - W
Page 229: Appendix C C-41 Notes.— DRAFT - W
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 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Appendix CD CD-3 ACTIONS EVENTS DRA
Page 289 and 290:
Page 291 and 292:
Appendix CD CD-7 too many broadcast
Page 293 and 294:
Page 295 and 296:
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 303 and 304:
Page 305 and 306:
Page 307 and 308:
Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 309 and 310:
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?