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-6 Technical Provisions for Mode S Services and Extended Squitter The setting of this bit is preferably dynamic. In case it is statically handled it should be forced to 1. When this bit is dynamic, it is always equal to bit 7 of register 1716. It might be different from bit 25 of register 1816 since the bits of registers 1816 to 1C16 are not reset once they are set. If the interface availability changes during the flight, bit 33 of register 1016 and bit 7 of register 1716 will be updated accordingly whereas bit 25 of register 1816 will remain unchanged. This is explained in notes 1 and 2 of §A.2.2.1. Note 1.— The intent of the capability bits in register number 1716 is to indicate that useful data are contained in the corresponding transponder register. For this reason, each bit for a register is cleared if data becomes unavailable (see §A.2.5.4.1) and set again when data insertion into the register resumes. Note 2.— A bit set in register numbers 1816 to 1C16 indicates that the application using this register has been installed on the aircraft. These bits are not cleared to reflect the real-time loss of an application, as is done for register number 1716 (see §A.2.5.4.2). It is also to be noted that register 1016 will be broadcast twice following the interface availability change. The first time because bit 33 will change, then because bit 36 will also toggle approximately one minute later to indicate that the content of register 1716 has changed. CD.2.4.1.8 BIT 34 (SQUITTER CAPABILITY SUBFIELD) This bit should be set as specified in Table A-2-16 of Appendix A. The squitter capability subfield (SCS) is interpreted as follows: 0 = squitter registers are not updated 1 = squitter registers are being updated SCS: This 1-bit squitter capability subfield reports the capability of the transponder to transmit extended squitter position reports. It shall be set to 1 if BDS registers 05 and 06 {HEX} have been updated within the last ten plus or minus one seconds. Otherwise, it shall be set to 0. Bit 34 is therefore an AND of bits 1 and 2 of transponder register 1716 and the setting of this bit is dynamic. Note that register 1016 will be broadcast twice in case bit 34 changes. The first time because bit 34 will change, then because bit 36 will also toggle one minute later to indicate that the content of register 1716 has changed. CD.2.4.1.9 BIT 35 (SI CODE CAPABILITY) This bit should be set as specified in Table A-2-16 of Appendix A, item 6. The surveillance identifier code (SIC) bit is interpreted as follows: 0 = no surveillance identifier code capability 1 = surveillance identifier code capability Draft SIC: This 1-bit surveillance identifier capability subfield reports the capability of the transponder to support the surveillance identifier (SI) codes. The setting of this bit is static. If the transponder software version handles SI codes then this bit should be set to 1. CD.2.4.1.10 BIT 36 (COMMON USAGE GICB CAPABILITY REPORT) This bit should be set as specified in Table A-2-16 of Appendix A, item 7. Bit 36 toggles each time the common usage GlCB capability report (BDS code 1,7) changes. To avoid the generation of DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix CD CD-7 too many broadcast capability report changes, BDS code 1,7 is sampled at approximately one minute intervals to check for changes. The setting of this bit is therefore dynamic. CD.2.4.2 TRANSPONDER REGISTER 1816 TO 1c16 The bits contained in Registers 1816 to 1C16 indicate the capability of the installation and are therefore specific to the platform on which the transponder is installed. It is accepted that these bits can be set once the corresponding data has been received by the transponder over a period of time. This can happen at any time and not only during the power-on cycle of the transponder as equipment providing expected information could be powered-on later. Once a bit is set, it remains set until the power-off of the transponder. CD.2.4.3.1 AIRBORNE FUNCTION CD.2.4.3 TRANSPONDER REGISTER 2016 Annex 10, Volume IV requirements (Annex 10, Volume IV, §3.1.2.9.1.1) state the following for data in transponder register 2016: DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris “AIS, aircraft identification subfield in MB. The transponder shall report the aircraft identification in the 48-bit (41-88) AIS subfield of MB. The aircraft identification transmitted shall be that employed in the flight plan. When no flight plan is available, the registration marking of the aircraft shall be inserted in this subfield. Note.— When the registration marking of the aircraft is used, it is classified as ‘fixed direct data’ (3.1.2.10.5.1.1). When another type of aircraft identification is used, it is classified as ‘variable direct data’ (3.1.2.10.5.1.3).” When the aircraft installation does not use an external source to provide the aircraft identification (most of the time it will be the call sign used for communications between pilot and controllers), the text above means that the aircraft identification is considered as variable direct data. It also means that such data characterize the flight condition of the aircraft (not the aircraft itself) and are therefore subject to dynamic changes. It further means that variable direct data are also subject to the following requirement when data become unavailable. Paragraph §A.2.1.1 states: Draft “If data are not available for a time no greater than twice the specified maximum update interval or 2 seconds (whichever is the greater), the status bit (if specified for that field) shall indicate that the data in that field are invalid and the field shall be zeroed.” Therefore, if the external source providing the aircraft identification fails or delivers corrupted data, transponder register 2016 should be zeroed. It should not include the registration marking of the aircraft since the airborne installation has initially been declared as providing variable direct data for the aircraft identification. The loss of the aircraft identification data will be indicated to the ground since transponder register 2016 will be broadcast following its change. If the registration marking of the aircraft was inserted in lieu of the call sign following a failure of the external source, it would not help the ground systems since the registration marking of the aircraft is not the information that was inserted in the aircraft flight plan being used by the ground ATC systems. In conclusion, the aircraft identification is either fixed (aircraft registration) or variable direct data (call sign). It depends whether the aircraft installation uses a data source providing the call sign; if so, data contained in transponder register 2016 should meet the requirement of the SARPs. When data become unavailable because of a data source failure, transponder register 2016 should contain all zeros. CD.2.4.3.2 GROUND CONSIDERATIONS Aircraft identification data can be used to correlate surveillance information with flight plan information. If the data source 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: DRAFT - Working Paper ASP TSGWP11-0
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 287 and 288: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 289: DRAFT - Working Paper ASP TSGWP11-0
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?