ARINC 635-4-2003 HF Data Link Protocols《高频数据链接协议195包括附录1到4》.pdf

1、 HF DATA LINK PROTOCOLS ARINC SPECIFICATION 635-4 PUBLISHED: DECEMBER 22, 2003 AN DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401 This document is based on material submitted by various participants during

2、 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 regard. Any use of or reliance o

3、n this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer. 2003 by AERONAUTICAL RADIO, INC. 2551 Riva Road Annapolis, Maryland 21401-7465 USA ARINC SPECIFICATION 635-4 HF DATA LINK PROTOCOLS Published: December 22, 2003 Prepared by the Airlines Electronic Engin

4、eering Committee Specification 635 Adopted by the Airlines Electronic Engineering Committee: October 31, 1995 Specification 635 Adopted by the Industry: December 22, 1995 Summary of Document Supplements Supplement Adoption Date Published Specification 635-1 October 22, 1996 December 12, 1996 Specifi

5、cation 635-2 December 12, 1997 February 27, 1998 Specification 635-3 August 11, 2000 December 29, 2000 Specification 635-4 September 9, 2003 December 22, 2003 A description of the changes introduced by each Supplement is included on Goldenrod paper at the end of this document. ii FOREWORD Aeronautic

6、al Radio, Inc., the AEEC, and ARINC Standards Aeronautical 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

7、Companys principal shareholders. Other shareholders 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 freque

8、ncy management. These activities directly support 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 techn

9、ical standards for airborne electronic equipment-including 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 ARI

10、NC Standards. The use of ARINC Standards results in 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 i

11、nterfaces 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 physic

12、al 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

13、 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 airline or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an oper

14、ational 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: a) An Errata Repo

15、rt solicits any corrections to the text or diagrams in this ARINC Standard. b) 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 635 TABLE OF CON

16、TENTS ITEM SUJET PAGE iii1.0 INTRODUCTION 11.1 Purpose of this Document 1 1.2 Background 1 1.3 Relationship of this Document to ARINC Characteristics 1 1.3.1 ARINC Characteristic 758 1 1.3.2 ARINC Characteristic 724B 1 1.3.3 ARINC Characteristic 724 1 1.3.4 ARINC Characteristic 597 1 1.3.5 ARINC Cha

17、racteristic 753 1 1.4 Relationship to OSI Protocols 1 1.5 Conventions Used in This Document 1 2.0 INTEROPERABILITY 32.1 Subnetwork Interoperability 3 3.0 FUNCTIONAL ASPECTS 43.1 General Description 4 3.2 System Architecture 4 3.2.1 Architectural Guidelines 4 3.2.2 Layers of the OSI Model 5 3.2.2.1 L

18、ayer 1, The Physical Layer 5 3.2.2.2 Layer 2, The Link Layer 5 3.2.2.2.1 Layer 2, Higher Layer Entities 5 3.2.2.3 Layer 3, The Network Layer 5 3.2.2.4 Layer 4, Transport Layer 6 3.2.2.5 Layer 5, Session Layer 6 3.2.2.6 Layer 6, Presentation Layer 6 3.2.2.7 Layer 7, Application Layer 6 3.2.3 HFDL Fun

19、ctional Organization 6 3.3 Radio Frequency Management 6 3.4 Message Composition 6 3.5 Priorities 7 3.5.1 Safety 7 3.5.2 Priority, Precedence and Preemption 7 3.5.3 Intrasystem Coordination 7 3.5.4 ADS Support 7 4.0 AIR/GROUND INTERFACES AND PROTOCOLS FOR LAYER 1 - THE PHYSICAL LAYER 94.1 Introductio

20、n 9 4.2 Physical Layer Service Definition 9 4.2.1 Transceiver Control 9 4.2.2 Data Reception 9 4.2.2.1 Data Packet Detection 9 4.2.2.2 Equalization 9 4.2.2.3 Forward Error Correction 9 4.2.2.4 Average Error Rate Performance Goals 9 4.2.2.5 Signal Quality Analysis 9 4.2.2.6 TDMA Receive Slot Synchron

21、ization 9 4.2.3 HF Data Link Signal-In-Space Definition 10 4.2.3.1 Analog Waveform Definition 10 4.2.3.2 Data Packet Encoding 10 4.2.3.2.1 Prekey and Preamble Definition 11 4.2.3.2. Dat Symbol Formation 1 4.2.3.21 Forward Eror Corection Encoding 1 4.2.3.22 Interleaving 1 4.2.3.23 Coded Chip to M-PSK

22、 Symbol Maping 12 4.2.3.24 M-PSK Symbol Scrambling 12 4.2.3.3 TDMA Transmit Slot Time Synchronization 12 4.2.4 Service Primitives 12 4.2.4.1 Physical Layer Data Request 13 4.2.4.2 Physical Layer Data Indication 13 4.2.4.3 Physical Layer Frequency Request 13 4.2.4.4 Physical Layer Signal Quality Indi

23、cation 13 ARINC SPECIFICATION 635 TABLE OF CONTENTS ITEM SUJET PAGE iv4.2.4.5 Physical Layer Transmit Data Rate Request 13 4.2.4.6 Physical Layer Receive Data Rate Indication 13 4.2.4.7 Physical Layer Transmit Interleaver Setting Request 14 4.2.4.8 Physical Layer Receive Interleaver Setting Indicati

24、on 14 4.2.4.9 Physical Layer Transmit Time Request 14 4.2.4.10 Physical Layer Receive Time Indication 14 4.2.4.11 Physical Layer Antenna Tuning Request 14 4.2.4.12 Physical Layer Tuning in Progress Indication 14 4.2.4.13 Physical Layer Tuning Failure Indication 14 4.2.4.14 Physical Layer HFDL Enable

25、-Disable Request 14 4.2.4.15 Physical Layer BITE Request 14 4.2.4.16 Physical Layer BITE Indication 14 5.0 AIR/GROUND SERVICES AND PROTOCOLS OF LAYER 2 -LINK LAYER 15 5.1 Introduction 15 5.2 Link Layer Service Definition 15 5.2.1 Channel Access Protocol 15 5.2.1.1 Data Rate Negotiations 15 5.2.1.2 A

26、ssignment of Slots by the Ground Station 16 5.2.1.2.1 Transmision of MPDUs in Asigned Uplink Slots 16 5.2.1.3 Selection of Downlink Slot by Aircraft 16 5.2.1.3.1 Contention/Random Access Slot Selection 17 5.2.1.4 Downlink Slot Reservation Requests 17 5.2.1.5 Maximum MPDU Size Adjustment 18 5.2.1.6 D

27、ata Rate and Interleaver Selection 18 5.2.1.7 Squitter SPDU Format 18 5.2.1.7.1 Intra-Ground Staion Synchronization 21 5.2.1.7.2 Inter-Ground Staion Synchronization 21 5.2.1.7.3 Ground Staion Synchronization Staus 2 5.2.2 Data Link Layer Packet Encapsulation 22 5.2.2.1 LPDU Encapsulation 25 5.2.2.2

28、Log-On Request and Log-on Resume LPDUs 25 5.2.2.3 Log-On Confirm and Log-On Resume-Confirm LPDUs 25 5.2.2.4 Log-On Denied and Log-Off Request LPDU 25 5.2.2.5 Unnumbered Data LPDU 26 5.25.1 HFDL System Table 26 5.25.2 HFDL System Table Request 28 5.25.3 Performance Dat 28 5.25.4 Frequency Dat 30 5.2.

29、2.6 Numbered Data LPDU 30 5.2.2.7 Unnumbered Acknowledged Data LPDU 30 5.2.3 LPDU Prioritization and Preemption 31 5.2.4 Link Control Protocols 31 5.2.4.1 Direct Link Service Mode Protocol 31 5.2.4.2 Reliable Link Service Mode Protocol 33 5.2.4.2.1 Segmentaion of HFNPDUs Into BDUs and Flow Control 3

30、3 5.2.4.2. Reasembly of BDUs into HFNPDUs, Flow Control and Routing 34 5.2.4.2.3 Uplink Transmision of LPDUs and Flow Control 34 5.2.4.2.3.1 Uplink Acknowledgment Field 35 5.2.4.2.3.2 Uplink LPDU Sequence Number Asignment 35 5.2.4.2.3. Request Acknowledge 35 5.2.4.2.4 Downlink Transmision of LPDUs a

31、nd Flow Control 35 5.2.4.2.4.1 Downlink Acknowledgment Field 36 5.2.4.2.4.2 Downlink MPDU Sequence Number Asignment 37 5.2.5 Airborne Link Management Functions 38 5.2.5.1 HF Link Establishment and Management 38 5.2.5.1. Aircraft Log-On Procedure 38 5.2.5.1.2 Aircraft Log-On Resume Procedure 39 5.2.5

32、.1.3 Aircraft Log-Of Procedure 40 5.2.5.1.4 Table of Loged Aircraft 40 5.2.5.1.5 HF Voice/Dat Switching 40 5.2.5.2 Link Management in Slave Mode 40 ARINC SPECIFICATION 635 TABLE OF CONTENTS ITEM SUJET PAGE v5.2.5.3 HF Link Monitoring and Data Link Unavailable Indication 40 5.2.5.4 HFDL System Table

33、Management 41 5.2.5.5 HFDL Fault Monitoring and Fault Indication 41 5.3 Service Primitives 41 5.3.1 Data Link Layer Service Primitives 41 5.3.2 LME Service Primitives 42 6.0 SERVICES AND PROTOCOLS OF LAYER 3 - THE NETWORK LAYER 43 6.1 Introduction 43 6.1.1 General Operation 43 6.2 Packet-Mode Data S

34、ervice 43 6.2.1 Link Layer Functions 43 6.2.2 HFDL SubNetwork Layer Structure 43 6.2.3 HFSND Protocol Description 43 6.2.4 Mapping Process Description 44 6.2.5 Timing 44 6.2.6 Buffer Sizes 44 6.2.6.1 Overall Buffer Size 44 6.3 Enveloped Packet-Mode Data Services 44 6.3.1 Link Layer Functions 45 6.3.

35、2 Enveloped Message Structure 45 6.3.3 Internetworking Functions 45 6.3.3.1 Enveloped Packet-Data Transmit 45 6.3.3.2 Enveloped Packet-Data Receive 45 6.3.3.3 Logged On Status 45 ATTACHMENTS 1-1 Airborne Subsystem Block Diagram 46 1-2 HFDL Reference Model 47 2-1 Airborne Station Protocol Layer Inter

36、faces 48 2-2 HF Data Link Signal-In Space Definition 49 2-3 Data Modulator Encoding Functions 50 2-4 Rate 1/2 Convolutional Encoder 51 2-5 HF Signal-In-Space Minimum Packet Error Rate Performance With 1.8 Second Interleaver 52 2-6 Slotted Frame 53 2-7A Downlink MPDU Format 54 2-7B Uplink MPDU Format

37、 55 2-7C Aircraft ID Definition 56 2-8A Squitter SPDU Format 57 2-8B Slot Assignments and Acknowledgments in Squitter 58 2-8C HFDL Bit Map Representations 59 2-8D Intra-Station Synchronization 66 2-8E Inter-Station Synchronization 67 2-9A LPDU Types and Format Definition 68 2-10A Unnumbered Data LPD

38、U Format Definition 69 2-10B Numbered Data LPDU Format Definition 70 2-10C Unnumbered Data LPDU With Broadcast HFDL System Table 71 2-10D Log-On Request and Log-On Resume LPDU Format Definitions 72 2-10E Log-On Confirm and Log-On Resume-Confirm LPDU Format Definition 73 2-10F Log-Off Request and Log

39、-On Denied LPDU Format Definition 74 2-10G Unnumbered Acknowledged Data LPDU Format Definition 75 2-11 HFDL Log-On Procedures 76 2-12 Data Link Layer Table 1 Main State Transition Table - Aircraft 77 Table 2 Main State Transition Table - Ground Station 78 Table 3A Numbered Data Transfer State Transi

40、tion Table 79 Table 3B Unnumbered Acknowledge Data Transfer State Transition Table 79 Table 4 Timers, Counters and Other Parameters 80 2-13 Table 1 Link Management Layer State Transition Table - Aircraft 81 2-14 HF Data Link Contention Slot Selection Backoff Algorithm State Machine 82 ARINC SPECIFIC

41、ATION 635 TABLE OF CONTENTS ITEM SUJET PAGE vi2-15 Attachments-To-Sections Cross Reference 83 3-1 Packet -Mode Priorities Table 1 HF Data Link Subsystem Packet-Mode - Priority Structure 84 APPENDICES A Acronym List 85 B References 87 C Delayed Echo Application 88 ARINC Standard - Errata Report ARINC

42、 IA Project Initiation/Modification (APIM) Guidelines for Submittal ARINC SPECIFICATION 635 - 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 b

43、it-oriented data using an air-ground HF data link operating in an Open System Interconnection (OSI) environment. The protocols defined herein are consistent with the concepts of the Aeronautical Telecommunications Network (ATN). This document describes the functions to be performed by the airborne c

44、omponents of the HF Data Link System (HFDL) to successfully transfer messages between HF ground stations and avionics systems on aircraft where the data is encoded in a bit-oriented format. These functions are referred to as HFDL protocols. The compatibility with OSI is provided by defining a set of

45、 services and protocols in accordance with the OSI model. COMMENTARY HFDL, as used in this document, refers to the digital communication protocols to be exercised by the HF transceiver and supporting avionics to exchange messages with any appropriately equipped ground system. 1.2 Background Aeronaut

46、ical data link communications were initiated using the Aircraft Communications Addressing and Reporting System (ACARS). The ACARS air-ground system description was initially included in ARINC Characteristic 597. It was later transferred to ARINC Specification 618, “Air-Ground Character-Oriented Prot

47、ocol Specification”. The development of HF Data Link service builds on the experiences of ACARS and operators in the HF environment to offer a reliable data link to remote regions. HF Data Link offers another communications path for the ATN environment to use. The HF air-ground data communication fu

48、nctions described herein are compatible with the OSI Model. They were developed as the first step toward a fully OSI compliant protocol “stack”. 1.3 Relationship of this Document to ARINC Characteristics This Specification may be referenced by any appropriate equipment Characteristic: 753, 719 or 59

49、7. To obtain HFDL communications capability, the HFDL functions defined herein should be installed in an existing ARINC 597, 724 or 724B ACARS Management Unit (MU), 758 Communications Management Unit (CMU) Mark-2 or ARINC 753 HF Data Radio and HF Data Unit to produce a unit capable of exchanging information in a bit-oriented environment. The description of the Internetworking Protocol, which accomplishes the routing function, is defined in ARINC Specification 637, “Internetworking S