Rules of the Air and Air Traffic Services(124)

曝光台 注意防骗 网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

1.2.2 The pilot shall be provided with the capability to respond to messages, to request clearances and information, to report information, and to declare or cancel an emergency.
1.2.3 The pilot and the controller shall be provided with the capability to exchange “free text” messages which do not conform to defined formats.
1.2.4 Sending a message by CPDLC shall consist of selecting the recipient(s), selecting the appropriate message, and executing the transmission.
1.2.5 Wherever time is used in the application of CPDLC, it shall be accurate to within 1 second of UTC.
1.3 Where applicable, the communication procedures for the provision of CPDLC shall be in accordance with Annex 10, Volume III, Part I, Chapter 3. Message element intent and text and associated procedures are, in general, consistent with Part X — Phraseologies. It is, however, recognized that the CPDLC message set and the associated procedures differ somewhat from the voice equivalent used because of the differences between the two media; one being direct-speech and the other an exchange of data, the latter of which can be displayed and/or printed.
2. Communication procedures

2.1 The controller or pilot shall initiate data messages using either the defined message set, a free text message or a combination of both.
Note.— See Appendix 5 for the CPDLC message set including message intent/use and the respective message elements.
2.2 Ground and airborne systems shall allow for messages to be appropriately displayed, printed when required and stored in a manner that permits timely and convenient retrieval should such action be necessary. Whenever textual presentation is required, the English language shall be used as a minimum.
2.3 Message attributes

2.3.1 Message attributes dictate certain message handling requirements for the CPDLC user receiving a message. Each CPDLC message has three attributes: Urgency, Alert and Response.
2.3.2 Urgency
2.3.2.1 The urgency (URG) attribute delineates the queuing requirements for received messages that are displayed to the end-user. Urgency types are presented in Table XI-1.
2.3.3 Alert
2.3.3.1 The alert (ALRT) attribute delineates the type of alerting required upon message receipt. Alert types are presented in Table XI-2.
2.3.4 Response
2.3.4.1 The response (RESP) attribute mandates response requirements for a given message element. Response types are presented in Table XI-3 for uplink messages and Table XI-4 for downlink messages.
PANS-RAC (Doc 4444) 11-1
11-2  Rules of the Air and Air Traffic Services (PANS-RAC) 
Table XI-1.  Urgency attribute (uplink and downlink)  Table XI-2.  Alert attribute (uplink and downlink) 
Type  Description  Precedence  Type  Description  Precedence 
D U N L  Distress Urgent Normal Low  1 2 3 4  H M L N  High Medium Low No alerting required  1 2 3 4 

Table XI-3.  Response attribute (uplink)
Type  Response required  Valid responses  Precedence 
W/U  Yes  WILCO, UNABLE, STANDBY permitted, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR (if necessary)  1 
A/N  Yes  AFFIRM, NEGATIVE, STANDBY permitted, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR (if necessary)  2 
R  Yes  ROGER, UNABLE, STANDBY permitted, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR (if necessary)  3 
Y  Yes  Any CPDLC downlink message, LOGICAL ACKNOWLEDGEMENT (only if required)  4 
N  No, unless logical acknowledgement required  LOGICAL ACKNOWLEDGEMENT (only if required), ERROR (if necessary, only when logical acknowledgement is required)  5 

Table XI-4.  Response attribute (downlink)
Type  Response required  Valid responses  Precedence 
　
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：Rules of the Air and Air Traffic Services(124)