《ARINC-623-3-2005.pdf》由会员分享，可在线阅读，更多相关《ARINC-623-3-2005.pdf（119页珍藏版）》请在三一文库上搜索。
1、 AN DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401 CHARACTER-ORIENTED AIR TRAFFIC SERVICE (ATS) APPLICATIONS ARINC SPECIFICATION 623-3 PUBLISHED: April 25, 2005 This document is based on material submitte
2、d by various participants during the drafting process. Neither AEEC nor ARINC has made any determination whether these materials could be subject to valid claims of patent, copyright or other proprietary rights by third parties, and no representation or warranty, express or implied, is made in this
3、regard. Any use of or reliance on this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer. 2005 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the Airlines Electronic Engineering Committee Specification 623 Adopted by
4、the Airlines Electronic Engineering Committee October 19, 1994 Summary of Document Supplements Supplement Adoption Date Published Specification 623-1 October 14, 1997 December 12, 1997 Specification 623-2 September 20, 1999 October 15, 1999 Specification 623-3 October 26, 2004 April 25, 2005 A descr
5、iption of the changes introduced by each supplement is included on Goldenrod paper at the end of this document. ARINC SPECIFICATION 623-3 CHARACTER-ORIENTED AIR TRAFFIC SERVICE (ATS) APPLICATIONS Published: April 25, 2005 -,-,- ii FOREWORD Aeronautical Radio, Inc., the AEEC, and ARINC Standards Aero
6、nautical Radio, Inc. (ARINC) was incorporated in 1929 by four fledgling airlines in the United States as a privately-owned company dedicated to serving the communications needs of the air transport industry. Today, the major U.S. airlines remain the Companys principal shareholders. Other shareholder
7、s include a number of non-U.S. airlines and other aircraft operators. ARINC sponsors aviation industry committees and participates in related industry activities that benefit aviation at large by providing technical leadership and guidance and frequency management. These activities directly support
8、airline goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operations. The Airlines Electronic Engineering Committee (AEEC) is an international body of airline technical professionals that leads the development of technical standards for airborne electronic equipment-i
9、ncluding avionics and in-flight entertainment equipment-used in commercial, military, and business aviation. The AEEC establishes consensus-based, voluntary form, fit, function, and interface standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results i
10、n substantial benefits to airlines by allowing avionics interchangeability and commonality and reducing avionics cost by promoting competition. There are three classes of ARINC Standards: a) ARINC Characteristics Define the form, fit, function, and interfaces of avionics and other airline electronic
11、 equipment. ARINC Characteristics indicate to prospective manufacturers of airline electronic equipment the considered and coordinated opinion of the airline technical community concerning the requisites of new equipment including standardized physical and electrical characteristics to foster interc
12、hangeability and competition. b) ARINC Specifications Are principally used to define either the physical packaging or mounting of avionics equipment, data communication standards, or a high-level computer language. c) ARINC Reports Provide guidelines or general information found by the airlines to b
13、e good practices, often related to avionics maintenance and support. The release of an ARINC Standard does not obligate any airline or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does i
14、t constitute endorsement of any manufacturers product designed or built to meet the ARINC Standard. In order to facilitate the continuous product improvement of this ARINC Standard, two items are included in the back of this volume: An Errata Report solicits any corrections to the text or diagrams i
15、n this ARINC Standard. An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for addition of substantive material to this volume which would be the subject of a new Supplement. -,-,- ARINC SPECIFICATION 623 TABLE OF CONTENTS iii 1.0 CHARACTER-ORIENTED ATS APPLICATIONS
16、.1 1.1 Introduction1 1.2 Relationship to Other Documents1 1.3 Annunciations2 1.4 Documents Referenced.2 2.0 RESERVED.3 3.0 RESERVED.4 4.0 RESERVED.5 5.0 FLIGHT SYSTEM APPLICATION .6 5.1 Flight System Message .6 5.2 Flight System Uplink 6 5.2.1 Flight System Uplink, Version 16 5.2.1.1 Message Text.7
17、5.2.1.1.1 Message Type Identifier7 5.2.1.1.2 Base Message.7 5.2.1.3 Supplemental Message7 6.0 TERMINAL WEATHER INFORMATION FOR PILOTS.8 6.1 Terminal Weather Information for Pilots8 6.2 Requesting TWIP Information8 6.2.1 Request for TWIP Downlink, Version 1.8 6.2.1.1 Message Text.8 6.2.1.1.1 Message
18、Type Identifier8 6.2.1.1.2 Avionics Indicator.8 6.2.1.1.3 Airport ID9 6.2.1.1.4 Request Mode9 6.2.1.1.5 Text/Graphics Indicator9 6.3 Delivery of the TWIP Report9 6.3.1 TWIP Report Uplink, Version 1.9 6.3.1.1 Message Text .9 6.3.1.1.1 Message Type Identifier.9 6.3.1.1.2 Airport ID9 6.3.1.1.3 TWIP Ide
19、ntifier .10 6.3.1.1.4 TWIP Time .10 ARINC SPECIFICATION 623 TABLE OF CONTENTS iv 6.3.1.1.5 TWIP Information .10 7.0 RESERVED.11 8.0 DATA LINK DELIVERY OF TAXI CLEARANCE .12 8.1 Data Link Delivery of Taxi Clearance 12 8.2 Requesting Pushback Clearance 12 8.2.1 Message Text, Version 112 8.2.1.1 Messag
20、e Type Identifier.12 8.2.1.2 Avionics Indicator.12 8.3 Delivering a Pushback Clearance Request Acknowledgment.13 8.4 Delivering a Pushback Clearance Response 13 8.5 Requesting Expected Taxi Clearance .13 8.6 Delivering Expected Taxi Clearance13 9.0 CONTROLLER TO PILOT COMMUNICATION (CPC) APPLICATION
21、S 14 9.1 CPC Applications.14 9.2 CPC Aircraft Log-On/Log-Off Request 14 9.2.1 Message Text .15 9.2.2 Message Type Identifier15 9.2.3 Avionics Indicator15 9.2.4 Message Identification Number 15 9.2.5 Message Reference Number16 9.2.6 Departure and Destination Airport IDs16 9.2.7 Optional Free Talk 16
22、9.3 CPC WILCO/UNABLE Response116 9.3.1 Message Text .17 9.3.2 Message Identification Number 17 9.3.3 Message Reference Number17 9.3.4 Supplemental CPC Data.18 9.3.4.1 Supplemental Data: Assigned Altitude18 9.4 CPC Command/Response Uplink .18 9.4.1 Message Text .19 9.4.2 Message Type Identifier20 9.4
23、.3 Message Identification Number 20 9.4.4 Message Reference Number20 9.4.5 Summary Information21 9.4.6 CPC Application Text21 ARINC SPECIFICATION 623 TABLE OF CONTENTS v ATTACHMENTS 1 Encoding Symbology and Use22 2 Reserved .27 3 Reserved .28 4 Reserved .29 5 Reserved .30 6 Reserved .31 7 Reserved .
24、32 8 Reserved .33 9 Flight System Message (FSM) Uplink Format.34 10 Terminal Weather Information for Pilots38 11 Reserved .41 12 Data Link Pushback Request and Clearance Formats42 13 Data Link Expected Taxi Clearance Request and Expected Taxi Clearance Format .46 14 Aircraft Log-On/Log-Off Message51
25、 15 Aircrew Response Downlink Message 53 16 CPC Uplink Message.55 APPENDICES A List of Acronyms59 B ATIS Report Request (Downlink) and ATIS Report (Uplink) Formats.61 C Oceanic Clearance Formats70 D Departure Clearance Formats.81 ARINC Standard - Errata Report ARINC IA Project Initiation/Modificatio
26、n (APIM) -,-,- ARINC SPECIFICATION 623 - Page 1 1.0 CHARACTER-ORIENTED ATS APPLICATIONS 1.1 Introduction This document defines the application text formats for character-oriented Air Traffic Services (ATS) messages that can be transmitted over the Aircraft Communications Addressing and Reporting Sys
27、tem (ACARS) data link. Several ACARS data links are available, including but not limited to, VHF, HF and satellite. The messages defined in this document are not specific to any data link. This document is limited in scope to character-oriented applications. Bit-oriented applications are defined in
28、a number of documents. See ARINC Specification 622 for references to these applications. The format/content of character-oriented messages is not consistent with bit-oriented messages. COMMENTARY Equivalent bit-oriented applications have been defined by the RTCA and acknowledged by the International
29、 Civil Aviation Organization (ICAO). ATS applications involve a single ground agency such as a the Civil Aviation Authority (CAA) communicating with aircraft belonging to multiple users. Therefore, uniform worldwide message formats are necessary. COMMENTARY The ACARS data link was originally conceiv
30、ed to provide a user, typically an airline, with a link between the users ground-based computer systems and those on-board the users aircraft. Although the air-ground protocol is common to all users, the message content for a given application was not standardized since the user controlled the appli
31、cation at each end. The airlines have expressed a strong desire for a single implementation in the avionics to support Air Traffic Services (ATS) via the ACARS data link. To enable a single software application to be appropriate for airspace worldwide, the users have recommended that all CAAs implem
32、ent the provisions of Chapter 5 of ARINC Specification 622 when installing ATS applications. Specifically, ARINC Specification 622 calls for the addition of an Imbedded Message Identifier and an end-to-end Cyclical Redundancy Check (CRC) with the message. Other data link media may become available i
33、n the future, including an IEEE 802.11based wireless LAN that is referred to as Gatelink. 1.2 Relationship to Other Documents Character-oriented messages may be transmitted directly over the ACARS network. However, where the additional functionality described in ARINC Specification 622 is required,
34、then the messages generated by these applications can be processed using the techniques described in ARINC Specification 622. -,-,- ARINC SPECIFICATION 623 - Page 2 1.0 CHARACTER-ORIENTED ATS APPLICATIONS COMMENTARY ARINC Specification 622 provides a number of functions which may be needed by the AT
35、S applications, i.e., a CRC integrity check and a means of addressing downlink messages to the relevant ATS ground agency. For transmission over the ACARS network, the message formats given in this document must be enveloped according to the processes described in ARINC Specification 620. ARINC Spec
36、ification 620 does not duplicate any of the text formats specified in this document as it only describes the envelope. COMMENTARY ARINC Specifications 620 and 622 also provide necessary information on the use of Labels/sub-Labels/Message Function Identifier (MFIs) and Imbedded Message Identifier (IM
37、Is). 1.3 Annunciations The avionics may be required to activate various alerts in response to specific ATS uplinks depending upon such things as aircraft configuration, airline policy and certifying authority mandates. The alert may be aural, visual, or both. The annunciation may differ depending up
38、on the type of ATS uplink (e.g., Automatic Terminal Information Service (ATIS) compared to Departure Clearance). 1.4 Documents Referenced This Specification refers to a number of other documents. Reference to such documents should be interpreted as the most recent version unless a specific issue is
39、cited. ARINC Specification 620: Data Link Ground System Standard and Interface Specification ARINC Specification 622: Data Link Applications Over ACARS Air/Ground Network EUROCAE ED-85A: Data Link Application System Document (DLASD) for the “Departure Clearance” Data Link-Service EUROCAE ED-89A: Dat
40、a Link Application System Document (DLASD) for the “ATIS” Data-Link Service EUROCAE ED-106A: Data Link Application System Document (DLASD) for the “Oceanic Clearance” Data-Link Service ARINC SPECIFICATION 623 - Page 3 2.0 RESERVED Information for ATIS Version 1 and 2 uplink and downlink messages, fo
41、rmerly Section 2.0, AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS), has been integrated with Attachment 2, and moved to Appendix B. -,-,- ARINC SPECIFICATION 623 - Page 4 3.0 RESERVED Information for Oceanic Clearance, formerly in Section 3.0, OCEANIC CLEARANCE, has been integrated with Attachments 3
42、, 4, and 5 and moved to Appendix C. -,-,- ARINC SPECIFICATION 623 - Page 5 4.0 RESERVED Information for Departure Clearance, formerly in Section 4.0, DEPARTURE CLEARANCE, has been integrated with Attachments 6, 7, and 8 and moved to Appendix D. -,-,- ARINC SPECIFICATION 623 - Page 6 5.0 FLIGHT SYSTE
43、M APPLICATION 5.1 Flight System Message The Flight System Message (FSM) application is used in conjunction with the ATS messages defined in this document. The FSM message provides a means to extend the range of information transfer between controller and pilot. The FSM message set, illustrated in Ta
44、ble 5.1-1, defines a number of possible response messages that augment the ATC Clearance applications defined in other sections of this document. COMMENTARY The FSM application was established to extend the options for providing information concerning clearances to the aircraft. Since this function,
45、 the FSM, is generic, its utility may be expanded to other message types as they evolve and are defined in this document. Table 5.1-1 FSM Set Definition Message Up/Down IMI Message Type Identifier MFI/ Label Flight System Message Up FSx FSM A4 In Table 5.1-1, the IMI of FSx, the value of the third c
46、haracter, x, should be filled with the version number of the message. 5.2 Flight System Uplink The Flight System Message is prepared by the Flight System application on the ground and sent to appropriate ATC application the aircraft. COMMENTARY The location of the destination on-board the aircraft i
47、s dependent upon the application to which the Flight System application communicates. Candidate applications are the interactive applications identified in this Specification, i.e., Departure and Oceanic Clearances. 5.2.1 Flight System Uplink, Version 1 The FSM message set includes information conce
48、rning the status of a clearance request and instructions to the pilot concerning what action to take. COMMENTARY For example, if the received downlink Oceanic Clearance Readback message fails the verification checks performed in the ground ATC system, the FSM application provides a mechanism to inform the pilot that an error has occurred. The clearance is canceled and reversion to Voice Procedures is necessary. -,-,- ARINC SPECIFICATION 623 Page 7 5.0 FLIGHT SYSTEM APPLICATION 5.2.1.1 Messag