曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
TIS messages utilize the short-form MSP protocol and TIS is assigned MSP channel 2.
3.2.2.2.2 Message type
The 6-bit message type field shall be used to differentiate the different types of uplink messages:
Message type value TIS message uplink type
0 to 59 Traffic data, first segment (own-heading)
60 Traffic data, intermediate segment(s)
61 Traffic data, final segment
62 Goodbye
63 Keep-alive
In the case of "first segment" traffic data messages, the 6-bit message type field shall contain the Mode S interrogator-derived
tracked own-heading of the aircraft receiving the TIS message. This heading shall be quantized in 6 degree increments and shall
be expressed with reference to magnetic north at the interrogator. The own-heading value jn traffic data messages shall be provided
to permit display heading correction on board the TIS-equipped aircraft by using an airborne heading sensor.
Note.- Such a heading correction may be necessary when the aircraft is manoeuvring or crabbing due to wind
Since there may be several ITS traffic data messages to a given aircraft during a given scan, TIS processing shall be ablc to group
the TIS traffic data uplinks together correctly. The "first", "intermediate", and "linal" segment type values shall provide the
necessary information to perform this grouping process. The mechanism Ibr this shall be as specified below. Buffer space for at
least 4 TIS traffic data messages (eight aircraft) shall be provided.
3.2.2.2.2.1 Keep-alive message
The TIS keep-alive message shall contain the message header and the message Lype fields as described above. The message type
field shall be sel to 63 decimal. The remaining bits of the message shall be unused.
3.2.2.2.2.2 Goodbye message
The TIS goodbyc message shall contain the message header and the message type fields as described above. The message type tield
shall be set to 62 decimal. The remaining bits of the message shall be unused.
3.2.2.2.3 Trafic information block
Each TIS traffic data message shall contain two 21-bit traffic information blocks whose slruclure is shown below. The six fields in
a traffic information block shall describe one TIS alert aircraft. One TIS traffic data message shall be able to define onc or two
alerl: aircrafi.
Note.- A number 'n' of TIS trafic data messages may be uplin,ked in a given scan to convey information on up to 2n alert
aircraft.
Trafic bearing Trafic range Relative altitude Altitude rate TrafJic heading Traffic status
6 b~ls 4 bils 5 bits 2 bits 3 b~ts I bit
28111102
No. 77
Annex 10 - Aerorrnutical Telecommunications Volume 111
3.2.2.2.3.1 Traffic bearing
The &bit traffic bearing field shall concain the bearing angle from [he own-aircraft heading to the alert aircraft, quantized in 6 degree
increments. The valid range for the traffic hearing field shall be 0 to 59 (with the exception described below).
Note.- Since this hearing angle is defined by TIS with respect to its measured own-aircraft heading, corrections from an
airhome heading source can he applied.
If there is only one alert aircraft in a given TIS traffic data message, the traffic bearing field in the unused traffic information block
shall be sel lo the value 63 (a bearing angle greater than 360 degrees) and thc remainder of the bits in the traffic information block
shall be ignored. This shall be termed as a "null alert" block.
3.2.2.2.3.2 Trafic range
The 4-bit traffic range Bcld shall contain the distance between own-aircraft and the alert aircraft. A non-linear range encoding shall
he used to minimize the number of bits required for this field as follows:
Trafic range value (r) Range (in increments of 230 rn (0.125 NM))
3.2.2.2.3.3 Relative altitude
The 5-hit relative altitude field shall contain the difference in altitude between the own-aircraft and the alert aircraft. A non-linear
cncodlng shall be used to minimize thc number of bits required for this field. A special encoding value shall be used to indicate
that the alert aircraft has no reported altitude. By convention, a positive value in the relative altitude field shall indicate that the
alert aircraft is above the own-aircraft.
Relative altitude shall be given by:
Relative altitude = AltitudeAler,ti, c,ft - AltitudeOwn.aircraft
where altitudes are indicated in feet.
The TIS encoding for relative altitude shall be:
Relative altitude value (ah) Relative altitude Ifeet)
0 5 alt 5 +I00
+I00 < alt 5 +200
+200 < alt 5 +300
+300 < alt +400
+400 < alt 5 +500
2811 1/02
No. 77
Annex 10 - Aeronautical Xelecommunications
Relative altitude value (alt) Relative altitclde (feet)
+500 < alt +600
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_77(77)
