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 CD-28 Technical Provisions for Mode S Services and Extended Squitter When a transponder register (which was previously supported) becomes unavailable and is currently monitored by a dataflash contract, a downlink dataflash message containing bits 1 to 40 will be sent with a CI field value of 7. This will indicate to the ground that the transponder register is not serviced anymore. The related contract is terminated by the airborne application, and the ground system should notify the user which has initiated the request that the service request has been terminated by the airborne installation. An alternative means for the ground system to detect that the transponder register is not serviced any longer is to analyze the resulting transponder register 1016 which will be broadcast by the transponder to indicate to the ground system that transponder register 1716 has changed. The Mode S sensor should then extract transponder register 1716 and send it to the ground application. The ground application should then analyze the content of this transponder register and should notice that the transponder register monitored by a dataflash contract is no longer supported by the airborne installation. CD.3.1.4 SERVICE CONTINUITY IN OVERLAPPING COVERAGE WITH RADARS USING THE SAME II CODE Depending on the system configuration the following guidance should be taken into account to ensure service continuity in overlapping coverage of radars working with the same II code. CD.3.1.4.1 RADAR WITH THE DATAFLASH APPLICATION EMBEDDED IN THE RADAR SOFTWARE For this configuration it is necessary to manage the contract numbers which will be used by each station and to ensure that the same contract number for the same transponder register is not used by another sensor having overlapping coverage and working with the same II code. The reason for this is that a sensor has no means of detecting if a contract it has initialized has been overwritten by another sensor using an identical dataflash header. Also one sensor could terminate a contract because an aircraft is leaving its coverage and no other sensor would know that this contract had been closed. For this reason, no dataflash contract termination should be attempted by either sensor in order to ensure a service continuity. When two ground stations with overlapping coverage and having the same II code each set up dataflash contracts with the same transponder register for the same aircraft, it is essential to ensure that the contract number is checked by each ground station prior to the closeout of any AICB which is announcing a dataflash message. CD.3.1.4.2 USE OF AN ATC CENTRE-BASED DATAFLASH APPLICATION The ATC system hosting the dataflash application should manage the distribution of contract numbers for sensors operating with the same II code. This ATC system will also have the global view of the aircraft path within the ATC coverage to either initiate or close dataflash contracts when appropriate. This is the preferred configuration since a central management of the contract numbers is possible which also allows a clean termination of the contracts. Draft C.3.1.5 GROUND MANAGEMENT OF MULTIPLE CONTRACTS FOR THE SAME TRANSPONDER REGISTER The ground system managing the dataflash application must ensure that when it receives a request from ground applications for several contracts to monitor different parameters, or different threshold criteria, related to the same transponder register for a particular aircraft/II code pair, it assigns a unique contract number for each contract sent to the aircraft. CD.3.1.6 SERVICE TERMINATION There are three ways to terminate a dataflash service (one from the ground initiative, two from the airborne installation): 1. The ground can send an MSP with the ECS field set to 0 which means that the service is to be discontinued by the airborne installation. 2. The airborne installation will terminate the service with no indication to the ground system if any message is not extracted from the transponder by a ground interrogator within 30 seconds following the event specified in the dataflash contract (TZ timer). 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 CD CD-29 3. When the transponder has not been selectively interrogated by a Mode S interrogator with a particular II code for 60 seconds (this is determined by monitoring the IIS subfield in all accepted Mode S interrogations), all dataflash contracts related to that II code will be cancelled with no indication to the ground system. The termination from the ground initiative is the preferable way to terminate the service since both the ground and the airborne systems terminate the service thanks to a mutually understood data link exchange. This termination should nevertheless not be allowed in certain configurations especially with adjacent sensors (with the dataflash application embedded in the sensor software) working with the same II code as explained in §CD.2.1. If the termination of the contract by a ground system is to be exercised, it should also be noticed that the ground system should anticipate the exit of the aircraft from its coverage to send the close-out message. CD.3.1.7 DATAFLASH REQUEST CONTAINING MULTIPLE CONTRACTS It is possible to merge several contracts into one single dataflash request. If multiple events occur which are related to several contracts of the initial dataflash request, one downlink message for each individual event should be triggered containing the associated transponder register. Each of these downlink messages should use the air initiated protocol. CD.3.1.8 TRANSPONDER REGISTER DATA CONTAINED IN THE DOWNLINK MESSAGE The transponder register data received by the ground system following the extraction of a downlink dataflash message consisting of two segments are the transponder register data at the time of the event. The transponder register data may be up to 1 aerial scan old since the event may occur just after the illumination of the aircraft. Should the end-user need more up-to-date data, the user should use the event announcement to trigger extraction via GICB protocol to get the latest transponder register data. CD.3.2 TRAFFIC INFORMATION SERVICE (TIS) TBD CD.3.3 EXTENDED SQUITTER TBD Draft 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:
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: 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: 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?