ARINC-631-5-2008.pdf
AN DOCUMENT Prepared by AEEC Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 VHF DIGITAL LINK (VDL) MODE 2 IMPLEMENTATION PROVISIONS ARINC SPECIFICATION 631-5 PUBLISHED: December 3, 2008 This document is published information as defined by 15 CFR Section 734.7 of the Export Administration Regulations (EAR). As publicly available technology under 15 CFR 74.3(b)(3), it is not subject to the EAR and does not have an ECCN. It may be exported without an export license. DISCLAIMER THIS DOCUMENT IS BASED ON MATERIAL SUBMITTED BY VARIOUS PARTICIPANTS DURING THE DRAFTING PROCESS. NEITHER AEEC, AMC, FSEMC 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 REGARD. ARINC INDUSTRY ACTIVITIES USES REASONABLE EFFORTS TO DEVELOP AND MAINTAIN THESE DOCUMENTS. HOWEVER, NO CERTIFICATION OR WARRANTY IS MADE AS TO THE TECHNICAL ACCURACY OR SUFFICIENCY OF THE DOCUMENTS, THE ADEQUACY, MERCHANTABILITY, FITNESS FOR INTENDED PURPOSE OR SAFETY OF ANY PRODUCTS, COMPONENTS, OR SYSTEMS DESIGNED, TESTED, RATED, INSTALLED OR OPERATED IN ACCORDANCE WITH ANY ASPECT OF THIS DOCUMENT OR THE ABSENCE OF RISK OR HAZARD ASSOCIATED WITH SUCH PRODUCTS, COMPONENTS, OR SYSTEMS. THE USER OF THIS DOCUMENT ACKNOWLEDGES THAT IT SHALL BE SOLELY RESPONSIBLE FOR ANY LOSS, CLAIM OR DAMAGE THAT IT MAY INCUR IN CONNECTION WITH ITS USE OF OR RELIANCE ON THIS DOCUMENT, AND SHALL HOLD ARINC, AEEC, AMC, FSEMC AND ANY PARTY THAT PARTICIPATED IN THE DRAFTING OF THE DOCUMENT HARMLESS AGAINST ANY CLAIM ARISING FROM ITS USE OF THE STANDARD. THE USE IN THIS DOCUMENT OF ANY TERM, SUCH AS SHALL OR MUST, IS NOT INTENDED TO AFFECT THE STATUS OF THIS DOCUMENT AS A VOLUNTARY STANDARD OR IN ANY WAY TO MODIFY THE ABOVE DISCLAIMER. NOTHING HEREIN SHALL BE DEEMED TO REQUIRE ANY PROVIDER OF EQUIPMENT TO INCORPORATE ANY ELEMENT OF THIS STANDARD IN ITS PRODUCT. HOWEVER, VENDORS WHICH REPRESENT THAT THEIR PRODUCTS ARE COMPLIANT WITH THIS STANDARD SHALL BE DEEMED ALSO TO HAVE REPRESENTED THAT THEIR PRODUCTS CONTAIN OR CONFORM TO THE FEATURES THAT ARE DESCRIBED AS MUST OR SHALL IN THE STANDARD. ANY USE OF OR RELIANCE ON THIS DOCUMENT SHALL CONSTITUTE AN ACCEPTANCE THEREOF “AS IS” AND BE SUBJECT TO THIS DISCLAIMER. ©2008 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the AEEC Specification 631 Adopted by the AEEC Executive Committee January 31, 1991 Summary of Document Supplements Supplement Adoption Date Published Specification 631-1 November 3, 1992 January 22, 1993 Specification 631-2 October 31, 1995 December 1, 1995 Specification 631-3 June 26, 2000 October 16, 2000 Specification 631-4 July 11, 2005 August 31, 2005 Specification 631-5 October 9, 2008 December 3, 2008 A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document. ARINC SPECIFICATION 631-5 VHF DIGITAL LINK (VDL) MODE 2 IMPLEMENTATION PROVISIONS Published: December 3, 2008 -,-,- ii FOREWORD Aeronautical Radio, Inc., the AEEC, and ARINC Standards ARINC organizes aviation industry committees and participates in related industry activities that benefit aviation at large by providing technical leadership and guidance. These activities directly support aviation industry goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operations. ARINC Industry Activities organizes and provides the secretariat for international aviation organizations (AEEC, AMC, FSEMC) which coordinate the work of aviation industry technical professionals and lead the development of technical standards for airborne electronic equipment, aircraft maintenance equipment and practices and flight simulator equipment and used in commercial, military, and business aviation. The AEEC, AMC, and FSEMC develop consensus-based, voluntary standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results in substantial benefits to the aviation industry 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 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 interchangeability 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 be good practices, often related to avionics maintenance and support. The release of an ARINC Standard does not obligate any organization 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 it 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 in 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 631 TABLE OF CONTENTS iii 1.0 INTRODUCTION.1 1.1 Purpose of this Document .1 1.2 Background .1 1.3 Relationship of this Document to Other ARINC Standards .1 1.3.1 Characteristic 758.2 1.3.2 Characteristic 750.2 1.3.3 Specification 637.2 1.3.4 Specification 620.2 1.3.5 Specification 618.2 1.3.6 Specification 638.2 1.3.7 Specifications 622 and 623.2 1.4 Relationship to Other Standards3 1.4.1 Relationship to ICAO Documents .3 1.4.2 Relationship to RTCA Documents 4 1.5 Relationship to OSI Protocols4 2.0 INTEROPERABILITY 5 2.1 Subnetwork Interoperability.5 2.2 VDLM2/ACARS RF Coexistence.5 2.3 VDLM2/ACARS Protocol Coexistence 5 3.0 SYSTEM OVERVIEW6 3.1 General Description.6 3.2 System Architecture.6 3.2.1 Architectural Guidelines7 3.2.2 Layers of the OSI Model .9 3.2.2.1 Layer 1, The Physical Layer.10 3.2.2.2 Layer 2, The Link Layer10 3.2.2.3 Layer 3, The Network Layer10 4.0 CONCEPTS OF OPERATION.13 4.0 Introduction13 4.1 Radio Frequency Management .13 4.1.1 ACARS to VDL Mode 2 Transition15 4.1.2 Dedicated VDL Mode 2 Operation15 4.2 VHF and Link Management Entities (VME/LME).16 4.2.1 Link Establishment17 4.2.1.1 Expedited Subnetwork Establishment With One Data Service Provider18 4.2.1.2 Expedited Subnetwork Establishment With Two Data Service Providers20 -,-,- ARINC SPECIFICATION 631 TABLE OF CONTENTS iv 4.2.1.3 Explicit Subnetwork Establishment With One Data Service Provider 20 4.2.1.4 Explicit Subnetwork Establishment With Two Data Service Providers.21 4.3 Handoff Management21 4.3.1 Handoffs Using Expedited Subnetwork Network Establishment With the Same Ground System.23 4.3.1.1 Aircraft-Initiated Handoff (Expedited).23 4.3.1.2 Aircraft-Requested Ground-Initiated Handoff.24 4.3.1.3 Reserved.24 4.3.1.4 Ground-Requested Aircraft-Initiated Handoff24 4.3.2 Handoffs Using Explicit Connection Establishment With the Same Ground System.25 4.3.2.1 Aircraft-Initiated Handoff (Explicit) 25 4.3.2.2 Ground-Initiated Handoff.26 4.4 Provisions for Test DSP.27 4.4.1 Aircraft Considerations27 4.4.2 Ground Station Considerations.28 4.4.3 Typical Message Exchanges29 5.0 PHYSICAL LAYER SPECIFICATION31 5.1 Introduction31 5.2 VDR Design Specifications and Primitives31 5.3 Physical Layer Overview .31 5.3.1 Functions of the Physical Layer31 6.0 MEDIA ACCESS CONTROL SUB-LAYER SPECIFICATION.32 6.1 Introduction32 6.2 Functions of the MAC Sub-Layer.32 6.3 Procedures of the MAC Sub-Layer32 6.4 MAC Parameters.32 6.5 Multiple Link Operation32 7.0 DATA LINK LAYER SPECIFICATION.33 7.1 Introduction33 7.2 Data Link Layer Partitioning.33 7.3 Transmit Queue Management.33 7.3.1 Transmit Queue Management 33 7.3.2 Procedures for Transmission33 7.4 Addressing.34 -,-,- ARINC SPECIFICATION 631 TABLE OF CONTENTS v 7.4.1 Allocation of a Remote Ground Station Address 34 7.4.2 Erroneous use of Broadcast ICAO 24 bit Aircraft Address .34 7.5 Ground Station Information Frames 34 7.5.1 GSIF Parameters34 7.6 Timers36 7.6.1 Timer T136 7.6.2 Timer T337 7.6.3 Other Timers.37 7.7 System Mask Parameter .38 7.8 HDLC Public Parameter Set ID .38 7.9 AVLC Specific Option38 7.10 VDL Parameter Length40 7.11 Embedded Acknowledgment.40 7.12 PICS 40 7.13 Encoding of XID Public Parameters 40 7.14 Unrecognized XID Parameters40 8.0 SUBNETWORK LAYER SPECIFICATION41 8.1 Introduction41 8.2 Connection Establishment.41 8.2.1 Explicit Connection Establishment41 8.2.2 Expedited Connection Establishment.41 8.3 Fast Select.41 8.4 Call Maintenance.42 8.4.1 Call Redirection for X.121 Based Networks42 8.5 Call Switching Within Same Routing Domain42 8.6 Call Clearing43 8.7 Priority (QOS)43 8.8 DTE Addressing.43 8.9 PICS 43 8.10 Flow control Window Closure44 9.0 LINK MANAGEMENT ENTITY (LME) SPECIFICATION.45 9.1 Introduction45 9.2 Initial Frequency Acquisition45 9.3 Link Establishment 45 9.4 Link Maintenance 45 9.4.1 Hand-Off .45 9.4.1.1 New Call Per Hand-Off.46 ARINC SPECIFICATION 631 TABLE OF CONTENTS vi 9.5 Ground Station Selection.46 9.6 Parameter Negotiation.46 9.7 ATN Router NET Parameter47 9.8 Frequency Management/Auto-Tune47 9.8.1 Autotune48 9.8.2 Frequency Support List (FSL).49 9.8.2.1 Frequency Support List for Aircraft in the Air .50 9.8.2.2 Frequency Support List for Aircraft on the Ground.50 9.9 PECT Maintenance53 10.0 EXTERNAL INTERFACES54 10.1 Introduction54 10.2 VDLM2 to System Management Interface.54 10.2.1 Service Available Indication54 10.2.2 Service Unavailable Indication55 10.2.3 Ground Station Switch Indication55 10.2.4 Ground Station Switch Reject.55 10.2.5 VDL Service Startup Request.56 10.2.6 VDL Service Shutdown Request.56 10.3 SNAcP to SNDCF Interface56 10.4 VDLM2 CMU to VDR Interface56 ATTACHMENTS 1 Protocol Architecture Diagrams.57 2 Data Link Layer PICS58 3 Subnetwork Layer PICS 79 4 Encoding of XID Parameters.95 APPENDICES A Terms and Acronyms.100 B Definition of VDL Addresses, Ground System, System Mask and Use of These Parameters for VDL Link Handoff .106 C Message Sequence Charts .112 D VSDA Configuration Issue.122 E State Machines134 F Allocation of Ground Station Addresses141 -,-,- ARINC SPECIFICATION 631 TABLE OF CONTENTS vii G FIS-B and AOA Extended Protocol Identifier for VDL Mode 2 Link Layer.144 H Message Sequence Charts for Autotune and TGS .148 I Generic Data Link Interface.164 J Airborne ATN System Architecture169 ARINC Standard Errata Report ARINC IA Project Initiation/Modification (APIM) Guidelines for Submittal -,-,- -,-,- ARINC SPECIFICATION 631 - Page 1 1.0 INTRODUCTION 1.1 Purpose of this Document The intent of this document is to provide general and specific design guidance for the development and installation of the protocols needed to exchange bit-oriented data across an air-ground VHF Digital Link (VDL) in an Open System Interconnection (OSI) environment. Details of the VDL protocols defined herein are specified in the International Civil Aviation Organization (ICAO) VDL Mode 2 (VDLM2) Standards and Recommended Practices (SARPs) and in the ICAO Doc 9776 Manual on VHF Digital Link (VDL) Mode 2 Part II. VDLM2 is consistent with the concepts of the ICAO Aeronautical Telecommunication Network (ATN). This document describes the functions to be performed by airborne and ground components of the VDLM2 to successfully transfer messages from VHF ground networks to avionics systems on aircraft and vice versa where the data are encoded in a code and byte independent format. The compatibility of VDLM2 with OSI is established by defining a set of services and protocols that are in accordance with the OSI basic reference model. The compatibility with the ATN protocols is achieved by defining a set of interfaces between the VDLM2 subnetwork protocol specification and the Mobile Subnetwork Dependent Convergence Function (M-SNDCF). The SNDCF is defined in the ICAO ATN SARPs. COMMENTARY VDLM2, as used in this document refers to the digital communication protocols to be exercised by the VHF transceiver and supporting avionics to exchange messages with any appropriately equipped ground system. The VDLM2 definitions were introduced to enhance the effectiveness of Air Traffic Services (ATS) and Airline Operational Control (AOC) communications. 1.2 Background Communications across the air-ground VHF link were initiated using the Aircraft Communications Addressing and Reporting System (ACARS). The ACARS air- ground system description was initially included in ARINC Characteristic 597 but was later transferred to ARINC Specification 618: Air-Ground Character-Oriented Protocol Specification. ACARS uses a character-oriented protocol that is not suitable for future Communications, Navigation, and Surveillance (CNS) functions necessary for Air Traffic Management (ATM). The bit-oriented, OSI-compliant VDLM2 is designed by ICAO to overcome the limitations of ACARS in order to provide a high-bandwidth, reliable, VHF data link required by CNS/ATM services. 1.3 Relationship of this Document to Other ARINC Standards This Specification may be referenced by any appropriate equipment characteristic such as ARINC Characteristics 750 and 758. To obtain VDLM2 communications capability, the VDLM2 functions defined herein should be installed in an ARINC Characteristic 758: Communications Management Unit (CMU) and ARINC Characteristic 750: VHF Data Radio to produce a unit capable of exchanging information in a bit-oriented environment. ARINC SPECIFICATION 631 - Page 2 1.0 INTRODUCTION The VDLM2 function can support both bit-oriented ATN applications and character- oriented ACARS applications. ACARS character-oriented applications are defined in ARINC Specifications 620 and 623. 1.3.1 ARINC Characteristic 758 New aircraft will be designed with communications architectures designed to operate within the ATN. The Communications Management Unit (CMU) is described in ARINC Characteristic 758: Communications Manag
