曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專營(yíng)店坑蒙拐騙欺詐消費(fèi)者

he identified. If there was no available AI, no PI is now available and the airborne TIS processor shall be in the "no TIS supported"
state. This state shall continue until a TIS mcssage (either traffic or keep-alive) is received from a Mode S ground interrogator.
When such an uplink message is received, the IT code contained in the message shall become the PI and the airborne processing
shall resume the display of TIS. The PI definition shall be initialized to the "none" state when TIS is enabled (TSCR) or disabled
(TSDR) by the pilot.
3.2.3 UPLINKM SP CHANNEL 3
(Reserved for ground-to-air alert)
The description of this channel has not yet been developed.
3.2.4 UPLINK MSP CHANNEL 4
(Reserved for ground-derived position)
The description of this channel has not yet been developed.
3.2.5 UPLINK MSP CHANNEL 5
(ACAS sensitivity level control)
The description of this channel has not yet been developed.
3.2.6 UPLINK MSP CHANNEL 6
(Ground-to-air request)
This service shall provide a means of requesting access to services supported by the aircraft. When implemented, bit 6 of the register
accessed by BDS code I,D shall be set to a 1.
The request shall be transferred in an uplink MSP packet with the channel number set to 6 and, in the case of a long form MSP
packet, with SP set to "ZERO. The first byte of the user data field shall contain a service request (SR) header. The contents and
format of the service request are specified by the application.
3.2.6.3 SR HEADER ASSIGNMENTS
Decimal value of SR
0 Unassigned
1 Dataflash
2 Local system management
3 to 255 Unassigned
28/11/02
No. 77
Annex I0 - Aeronautical hlecommunications
3.2.6.3.1.1 Dataflash request fonnat
The format of the user data field shall be as specified in Table 3-1. The user data field of h e requesting MSP packet shall contain
the decimal value of "ONE" in [he first byte (SR header), followed by one or more requests for dataflash services. Each request
shall contain a 2-byte dataflash request header (DH), followed by a 1-byte field to define the minimum time interval permitted
between reports (MT field), a 4-bit field to determine the event criterion (EC field), a Chit field to determine stable time (ST field),
and if indicated in EC, a change quanta field (CQ) and a change threshold (CT) field. The 4-bit ST field shall indicate the decimal
value in seconds and how long the changed data has been stable before a message shall be initiated. All zeros in the dataflash header
(DH) shall indicate that there are no more dataflash requests in the packet. When an MSP packet is completely filled with dataflash
requests, or when there is not sufficient room in the packet for another dacaflash request header, it shall be assumed that the
dataflash request sequence is complete.
3.2.6.3.1.1.1 All aircraft dataflash equipment and installations shall support 16 dataflash contracts. Aircraft equipment and
installalions originally certified after 1 January 2001 shall support 64 dataflash contracts.
Note 1.- A single dataflash contract relates to a single contract number (see 3.2.6.3.1.2.1) for n sin,gle register for a particular
I1 code. Therefore, dataflash services, with dzfJerent DH values for each 11 code, can be established simultaneously with the same
aircraft. These may be modified or discontinued independently of each other
3.2.6.3.1.1.2 Recommendation.- When a request has been accepted by the aircraft system, a dataflash response should be
triggered immediately regardless of thresholds or event criteria. If no response is received in 30 seconds then a check should be
made that the aircrafr is still available on roll call, and if so a new request should he generated. In order to avoid repeated dataJash
requests that produce no rcsporzse, the number of such requests (N) should be limited (N = 3).
3.2.6.3.1.1.3 When a new contract request is received for a contract already in existence, the old contract shall be discontinued
and replaced immediately by the latest one.
3.2.6.3.1.2 Dataflash header (DH) 16 bits
The 16-hit DH field is divided into four subfields separated by 3 reserved bits (14 through 16) see Table 3-1
3.2.6.3.1.2.1 Contract number subfield (CNS) 4 bits
(Bits 9 to 12 of the uplink MSP 6
user data field when SR = I )
This subfield shall be interpreted as a contract number permitting 16 different contracts to be associated with the register specified
by the BDS1 and BDS2 codes of this contract request. Contract numbers available are 0 to I5 and shall be associated with the I1
code of the contract request.
3.2.6.3.1.2.2 Request data subfield (RDS) 1 bit
(Bit 13 of the uplink MSP 6
user data field when SR = 1
This subheld shall indicate whether or not the contents of the register being monitored by the requested contract must be sent in
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：附件10--航空電信an10_v3_1ed_amend_77(80)