曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
2.5.4. I COMMOUNS AGE CAPABILITY REPORT (REGISTER NUMBER 1716)
A bit in register number 171G shall be cleared if there is a loss of corresponding input data (2.5.2) and shall be set when data
insertion into the register resumes. Bit 36 of register lolG shall be toggled to indicate a change of capability.
2.5.4.2 MODES SPECrFIC SERVICES CAPABILITY REPORT (REG~STERN UMBERS to 1C16)
A bit sct in one of these registers shall indicate that the service loading the register indicated by that bit has been installed on the
aircraft. In this regard, these bits shall not be cleared to reflect a real limc loss of an application, as is done for register 171b.
2.5.4.3 mNSPONDER MONITORING
As indicated in 2.4, the transponder's role in this process shall be to serve as a backup in the event of the loss of GFM functionality.
For this reason, the transponder shall:
1) clear the extended squitter registers (usl6, 06,6, 0716 and 0916) if they have not been updatcd in 2 seconds.
2) clear all of the registers loaded by the GFM if it dcrects a loss of GFM capability (e.g. a bus failure). In this case, it would
also clear all of the bits in register number since a bit in this register means "application installed and operational".
The transponder shall not clear the other capability register numbers (1XI6 to 1CI6) since they are intended to mean only
"application installed".
2.5.5 HANDLING OF EVENT-DRIVEN PROTOCOL
The event-driven interface protocol provides a general purpose interface into the transponder function for messages beyond those
that are regularly transmitted all the timc (provided input data are available). This protocol shall operate by having the transponder
broadcast a message once each time the event-driven register is loaded by the GFM.
Note.- Tlzis gives the GFM complete freedom in setting the update rate (up to a maximum) arzd duration of broadcast for
applications si~ch as emergency status and intent reporting.
Purl 1 Annex 10 - Aero~zautical Tclecornmunications
In addition to formalting, the GFM shall control the liming of message insertion so that it provides the necessary pseudo-random
timing variation and does not exceed the maximum transponder broadcasl rate for the event-driven protocol.
2.5.5.1 TRANSPONDER SUPPORT FOR EVENf-DRIVEN MESSAGES
A messagc shall only be transmiited oncc by the transponder each limc that register number OA16 is loaded. Transmission shall be
delayed if the transponder is busy at the time of inscrtion.
Note I.- Delay times are short. They are us~~alal ym aximum of several milliseconds for the longest transponder transaction
The maximum transmission rale for the event-driven protocol shall be limited by the transponder to twice per second. If a messagc
is inserted in the event-driven rcgister and cannot be transmitted due to rate limiting, it shall be held and transmitted when the rate
limiting condition has cleared. If a new message is received before transmission is permitted, it shall overwrite the earlier message.
Note 2.- The squitter transmission rate and the duration of squitter transmissions are application dependent. The ~ninirn~irrna te
and duration consistent with the needs of the applicution should be chosen.
2.5.5.2 GFM USE OF EVEN'f-DRIVEN PROTOCOL
An application that selects thc event-driven protocol shall notify khe GFM of the format type and rcquired update rate. The CFM
shall then locate the necessary input data for this format type and begin inserting data into register number ()Al6 at the required
rate. The GFM shall also insert this message into the register for this format type. This register image shall be maintained to allow
read-out of this information by air-ground or air-air register read-out. When broadcast of a ibnnat type ceases, the CFM shall clear
the corresponding regisler assigned to this message.
The maximum rate that shall be supported by the evenl-driven protocol is twice per second from one or a collection of applications.
For each event-driven format type being broadcast, the GFM shall retain the time of the last insertion into register numbcr OA16.
The next insertion shall be scheduled at a random interval that shall be uniformly distributed over the range of the update interval
0.1 second (using a time quantization no greater than 15 ms) relative to the previous insertion into register number OA16 for this
format type.
The GFM shall monitor the number of insertions scheduled in any one second interval. If more than two would occur, it shall add
a delay as necessary to ensure that the limit of two messages per second is observed.
2.5.5.3 EVENT-DR~VEN PRIORITY
If the event-driven messagc transmission rate musi bc reduced in order not to exceed the maximum rate specified in 2.5.5.2,
transmission priority shall be assigned as follows:
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_77(59)
