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 A-26 Technical Provisions for Mode S Services and Extended Squitter A.2.5.3.3 RECEPTION OF FORMAT TYPE CODE EQUAL TO ZERO An extended squitter containing format TYPE Code equal to zero shall not be used to initiate an ADS-B track. Note.— If a squitter with format TYPE Code equal to zero is received and if altitude is present it can be used to update altitude of an existing ADS-B track. A.2.5.4 TRANSPONDER CAPABILITY REPORTING The GFM shall be responsible for setting the transponder capability registers numbers 1016, and 1816 to 1C16. It shall also clear individual bits in register number 1716 in the event of a loss of a data source or an application. A particular bit shall remain set if at least one field in the corresponding register message is being updated. A.2.5.4.1 COMMON USAGE CAPABILITY REPORT (REGISTER NUMBER 1716) A bit in register number 1716 shall be cleared if there is a loss of corresponding input data (see §A.2.5.2), for all data fields of the register, and shall be set when data insertion into the register resumes. Bit 36 of register 1016 shall be toggled to indicate a change of capability. A.2.5.4.2 MODE S SPECIFIC SERVICES CAPABILITY REPORT A.2.5.4.2.1 Mode S specific services GICB capability report (registers numbers 1816 to 1C16) A bit set in one of these registers shall indicate that the service loading the register indicated by that bit has been installed on the aircraft. In this regard, these bits shall not be cleared to reflect a real-time loss of an application, as is done for register 1716. Draft A.2.5.4.2.2 Mode S specific services MSP capability report (registers numbers 1D16 to 1F16) Each bit shall indicate that the MSP it represents requires service when set to 1. A.2.5.4.3 TRANSPONDER MONITORING As indicated in §A.2.4, the transponder’s role in this process shall be to serve as a backup in the event of the loss of GFM functionality. For this reason, the transponder shall: 1) clear the extended squitter registers (0516, 0616, 0716 and 0916) if they have not been updated for a time no greater than twice the specified maximum update interval, or 2 seconds (whichever is the greater). 2) clear all of the registers loaded by the GFM if it detects a loss of GFM capability (e.g., a bus failure). In this case, it would also clear all of the bits in register number 1716 since a bit in this register means “application installed and operational”. The transponder shall not clear the other capability registers numbers (1816 to 1C16) since they are intended to mean only “application installed”. 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 A A-27 A.2.5.5 HANDLING OF EVENT-DRIVEN PROTOCOL The event-driven interface protocol provides a general purpose interface into the transponder function for messages beyond those that are regularly transmitted all the time (provided input data are available). 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. In addition to formatting, the GFM shall control the timing of message insertion so that it provides the necessary pseudorandom timing variation and does not exceed the maximum transponder broadcast rate for the event-driven protocol. A.2.5.5.1 TRANSPONDER SUPPORT FOR EVENT-DRIVEN MESSAGES A message shall only be transmitted once by the transponder each time that register number 0A16 is loaded. Transmission shall be delayed if the transponder is busy at the time of insertion. Note 1.— Delay times are short. They are usually a maximum of several milliseconds for the longest transponder transaction. The maximum transmission rate for the event-driven protocol shall be limited by the transponder to twice per second. If a message is inserted in the event-driven register and cannot be transmitted due to rate limiting, it shall be held and transmitted when the rate limiting condition has cleared. If a new message is received before transmission is permitted, it shall overwrite the earlier message. Note 2.— The squitter transmission rate and the duration of squitter transmissions are application dependent. A.2.5.5.1.1 Recommendation.— The minimum rate and duration consistent with the needs of the application should be chosen. A.2.5.5.2 GFM USE OF EVENT-DRIVEN PROTOCOL Draft An application that selects the event-driven protocol shall notify the GFM of the format type and required update rate. The GFM shall then locate the necessary input data for this format type and begin inserting data into register number 0A16 at the required rate. The GFM shall also insert this message into the register for this format type. This register image shall be maintained to allow read-out of this information by air-ground or air-air register read-out. When broadcast of a format type ceases, the GFM shall clear the corresponding register assigned to this message. The maximum rate that shall be supported by the event-driven protocol is twice per second from one or a collection of applications. For each event-driven format type being broadcast, the GFM shall retain the time of the last insertion into register number 0A16. The next insertion shall be scheduled at a random interval that shall be uniformly distributed over the range of the update interval ±0.1 second (using a time quantization no greater than 15 ms) relative to the previous insertion into register number 0A16 for this format type. The GFM shall monitor the number of insertions scheduled in any one second interval. If more than two would occur, it shall add a delay as necessary to ensure that the limit of two messages per second is observed. 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 31 and 32: Appendix A A-7 TYPE Code Format Hor
Page 37 and 38: Appendix A A-13 The supersonic vers
Page 39 and 40: Appendix A A-15 The transponder sha
Page 49: DRAFT - Working Paper ASP TSGWP11-0
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 71 and 72: Appendix A A-47 MB FIELD 1 2 3 4 5
Page 79 and 80: Appendix A A-55 MB FIELD 1 BDS A,8
Page 101 and 102:
Appendix A A-77 MB FIELD DRAFT - Wo
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:
DRAFT - Working Paper ASP TSGWP11-0
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:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Appendix C C-51 3. The decoded posi
Page 241 and 242:
Page 243 and 244:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix C C-65 Register 0A16 Figur
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Appendix C C-71 Table C-37. CF Fiel
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
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

Create successful ePaper yourself

Delete template?

Save as template?