Technical Provisions for Mode S Services and Extended Squitter
Technical Provisions for Mode S Services and Extended Squitter
Technical Provisions for Mode S Services and Extended Squitter
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DRAFT - Working Paper ASP TSGWP11-01 <strong>for</strong> review by the TSG during the meeting in June 2011 in Paris<br />
Appendix C C-85<br />
Message<br />
Format TYPE<br />
Code(s)<br />
1 through 4<br />
Table C-39. Version Zero (0) ADS-B Message Types<br />
Assignment Nominal Broadcast Rate<br />
<strong>Extended</strong> <strong>Squitter</strong> Identification <strong>and</strong><br />
Category<br />
5.0 s airborne/10.0 s surface<br />
5 through 8 <strong>Extended</strong> <strong>Squitter</strong> Surface Position 0.5 s in motion/5.0 s stationary<br />
9 through 18<br />
<strong>and</strong><br />
20 through 22<br />
<strong>Extended</strong> <strong>Squitter</strong> Airborne Position 0.5 s<br />
19 <strong>Extended</strong> <strong>Squitter</strong> Airborne Velocity 0.5 s<br />
28<br />
<strong>Extended</strong> <strong>Squitter</strong> Aircraft Status<br />
(e.g., emergency/priority)<br />
1.0 s<br />
31 Aircraft Operational Status 1.7 s<br />
C.5.2.1.1 Message TYPE Codes<br />
The first 5-bit field in every 1090 MHz ADS-B Message shall contains the message <strong>for</strong>mat TYPE. As shown<br />
in Table C-40, the TYPE Code (i.e., <strong>for</strong>mat type) is shall be used to differentiate the ADS-B Messages into<br />
several classes: airborne position, airborne velocity, surface position, identification, aircraft status, etc.<br />
Notes.—<br />
1. The general definition <strong>for</strong> all ADS-B Messages Types used <strong>for</strong> ADS-B Version Zero (0) ADS-B<br />
Messages has been retained <strong>for</strong> ADS-B Version One (1) <strong>and</strong> ADS-B Version Two (2) Messages. It must be<br />
noted <strong>for</strong> ADS-B Version Zero (0) ADS-B Messages, <strong>for</strong>mat TYPE Code 29 was defined but the<br />
corresponding messages are not to be transmitted. For ADS-B Version Zero (0) ADS-B Subsystems, TYPE<br />
Code 29 was associated with intent messages conveying Trajectory Change Point (TCP) in<strong>for</strong>mation.<br />
Although the message <strong>for</strong>mats <strong>for</strong> TCP related messages were defined within Appendix A, the requirements<br />
<strong>and</strong> the associated test procedures prohibited the broadcast of such messages.<br />
2. Appendix A defined TYPE Code 30 <strong>for</strong> Aircraft Operational Coordination Messages. The<br />
requirements <strong>and</strong> associated provisions <strong>for</strong> Aircraft Operational Coordination Messages have now been<br />
withdrawn by this Edition of this Manual. Although Appendix A (i.e., Version Zero) con<strong>for</strong>mant<br />
implementations are not prohibited from transmitting Aircraft Operational Coordination Messages (i.e., using<br />
TYPE Code 30), ADS-B Version Two (2) con<strong>for</strong>mant ADS-B Receiving Subsystems have no requirement <strong>for</strong><br />
the reception <strong>and</strong> processing of these broadcasts.<br />
Draft<br />
ADS-B Version Two (2) ADS-B Receiving Subsystems will shall process ADS-B Messages based only on<br />
the reception of ADS-B Version Zero (0) ADS-B Messages with ADS-B Message TYPE Code values of 0<br />
through 22, 28 <strong>and</strong> 31.<br />
DRAFT - Working Paper ASP TSGWP11-01 <strong>for</strong> review by the TSG during the meeting in June 2011 in Paris
Change language