1、 AN DOCUMENT Prepared by AEEC Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 AIRCRAFT DATA NETWORK PART 7 AVIONICS FULL-DUPLEX SWITCHED ETHERNET NETWORK ARINC SPECIFICATION 664 P7-1 PUBLISHED: September 23, 2009 This document is published information as defined
2、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 P
3、ARTICIPANTS 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 RE
4、GARD. 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, COMPONEN
5、TS, 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 DAMAG
6、E 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
7、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 T
8、HEIR 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
9、 THIS DISCLAIMER. 2009 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the AEEC Specification 664P7 Adopted by the Airlines Electronic Engineering Committee April 26, 2005 Summary of Document Supplements Supplement Adoption Date Published Specification 664P7
10、-1 April 15, 2008 September 23, 2009 A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document. ARINC SPECIFICATION 664P7-1 AIRCRAFT DATA NETWORK PART 7 AVIONICS FULL-DUPLEX SWITCHED ETHERNET NETWORK Published: September 23, 2009ii FOREWORD
11、 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 safe
12、ty, 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 t
13、echnical 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 a
14、s 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, fi
15、t, 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 s
16、tandardized 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
17、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 t
18、he 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 vo
19、lume: 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
20、 664 PART 7 TABLE OF CONTENTS iii 1.1 Purpose of Document 1 1.2 Scope.1 1.3 Document Organization .1 1.3.1 ARINC Specification 64, Aircraft Data Network.1 1.4 Related Documents .2 1.4.1 Relationship of this Document to Other ARINC Standards .2 1.4.2 Relationship to Industry Standards .2 1.4.3 RTCA a
21、nd EUROCAE Documents2 1.5 Document Precedence 3 1.6 Regulatory Approval 3 2.0 OVERVIEW4 2.1 Comparative Model4 2.2 Switched Ethernet Networks5 2.3 Scalability.7 2.4 Ordinal Integrity7 2.5 Fault Performance .8 2.6 Switching8 2.7 System Performance .8 3.0 END SYSTEM SPECIFICATION .9 3.1 Introduction 9
22、 3.1.1 ES Identification 10 3.2 Interoperability and Determinism at the Media Access Control (MAC) Layer10 3.2.1 Virtual Link.10 3.2.2 Flow/Traffic Control .11 3.2.3 Scheduling.12 3.2.4 End System Performance .13 3.2.4.1 Latency .13 3.2.4.2 MAC Constraints 15 3.2.4.3 Jitter16 3.2.5 MAC Addressing .1
23、7 3.2.5.1 MAC Destination Address 17 3.2.5.2 MAC Source Address .18 3.2.6 Redundancy Concept19 3.2.6.1 Sequence Numbers and the Sending End System 22 3.2.6.2 Sequence Numbers and the Receiving End System23 3.2.6.2.1 Integrity Checking 23 3.2.6.2.2 Redundancy Management.24 ARINC SPECIFICATION 664 PAR
24、T 7 TABLE OF CONTENTS iv 3.3 Interoperability at the IP Layer and Above.26 3.3.1 Avionics Services 27 3.3.1.1 Communication Ports .28 3.3.1.1.1 Avionics Sampling Services.28 3.3.1.1.1.1 In Transmission.28 3.3.1.1.1.2 In Reception 29 3.3.1.1.2 Avionics Queuing Service29 3.3.1.1.2.1 In Transmission.29
25、 3.3.1.1.2.2 In Reception 30 3.3.1.2 SAP Port.30 3.3.1.2.1 Services to Compliant Network30 3.3.1.2.2 SAP Port Error Management .30 3.3.1.2.3 File Transfer Services30 3.3.1.3 The Sub-VL 31 3.3.2 Trivial File Transfer Protocol Example 33 3.3.3 ES Communication Stack34 3.3.3.1 ES MAC Profile.34 3.3.3.2
26、 ES IP Profile .35 3.3.3.2.1 IP Packet Structure35 3.3.3.2.2 IP Fragmentation/ Reassembly35 3.4 Network Level Interoperability36 3.4.1 Addressing 36 3.4.1.1 Introduction .36 3.4.1.2 Structure of an AFDX Frame Without Fragmentation.36 3.4.1.3 Identification for End-to-End Communication .39 3.4.1.3.1
27、Intra-AFDX Communication.40 3.4.1.3.2 Extra-AFDX Communication41 3.4.1.4 IP Addressing Format.41 3.4.1.4.1 IP Source Address.41 3.4.1.4.2 IP Destination Address 42 3.4.1.5 AFDX Communication Port, SAP and UDP/TCP Addressing Format 43 3.4.1.5.1 AFDX Communication Ports44 3.4.1.4.2 SAP Ports 44 3.4.1.
28、5.3 Allocation of the SAP and AFDX Communication Port Numbers 44 4.0 SWITCH SPECIFICATION 48 4.1 Basic Concepts 48 4.1.1 Filtering and Policing Function Introduction 49 4.1.1.1 Policing and Filtering Parameters.49 ARINC SPECIFICATION 664 PART 7 TABLE OF CONTENTS v 4.1.1.2 Frame Filtering .49 4.1.1.3
29、 Traffic Policing 50 4.2 Filtering and Policing Function.52 4.2.1 Frame Filtering 52 4.2.2 Traffic Policing.53 4.4 Switching Function.55 4.5 Switch End System Function .56 4.5.1 Overview .56 4.5.2 Addressing Policy56 4.6 Monitoring Function .56 4.7 Configuration Files .58 4.7.1 Introduction 58 4.7.2
30、 Default_Configuration_Table.59 4.7.2.1 Default Physical Port 59 4.7.2.2 Default Reception Configuration.59 4.7.2.3 Default Transmission Configuration .59 4.7.3 Field Loadable Configuration Tables: OPS_Configuration_File60 4.7.3.1 EndSystem_Configuration_Table.61 4.7.3.2 Filtering_Policing and_Forwa
31、rdingConfiguration_Table.61 4.8 Operating Modes .62 4.8.1 Overview .62 4.8.2 INIT63 4.8.2.1 Initialization Sequence64 4.8.2.2 Ground_Condition 65 4.8.3 OPS: Operational Mode 65 4.8.4 DL: Dataloading Mode.65 4.8.5 SHOP (Optional) .66 4.8.6 PASSIVE.66 4.8.7 QUIET .67 4.9 Dataloading68 4.9.1 General Da
32、taloading Requirements68 4.9.2 Configuration Identification68 4.9.2.1 Definition of Switch Configuration.68 4.9.2.2 Switch-On Configuration Identification .68 4.9.3 Dataloader IP Address 68 4.10 Pin Programming .69 4.10.1 Pin Programming Processing69 4.10.1.1 When Pins Programming Should be Read.69
33、4.10.1.2 Parity Check and Processing .69 ARINC SPECIFICATION 664 PART 7 TABLE OF CONTENTS vi 4.10.2 List of Pin Programming69 4.10.2.1 Position Coding 69 4.11 Performance Characteristics69 4.11.1 General Characteristics.69 4.11.2 Physical Layer Characteristics 70 4.11.3 Processing Capabilities.70 5.
34、0 SYSTEM ISSUES 72 5.1 Performances.72 ATTACHMENTS 1 Data Format .74 2 IP/ICMP, UDP, and TCP Profile Provisions .94 APPENDICES A An Example of ES Identification.125 B Guidelines for ARINC 429 to AFDX Formatting.126 C Network Terminology .130 D Services to Protocol Mapping 132 ARINC Standard Errata R
35、eport ARINC IA Project Initiation/Modification (APIM) ARINC SPECIFICATION 664 PART 7 Page 1 1.0 INTRODUCTION 1.1 Purpose of Document The purpose of this document is to define a deterministic network: Avionics Full Duplex Switched Ethernet (AFDX). AFDX is a trademark of Airbus and is used with permis
36、sion. This document also highlights the additional performance requirements of avionics systems, within the context of AFDX. This specification allows: System integrators to design flight critical systems using AFDX Equipment designers to specify equipment interoperable with AFDX 1.2 Scope The requi
37、rements listed in this document aim at specifying interoperable functional elements: Data link: MAC, VL addressing concept Network: IP, ICMP Transport: UDP, TCP (optional) Network application layers: Sampling, Queuing, SAP, TFTP, and SNMP This document will be limited to the description of the norma
38、tive protocols listed above. COMMENTARY System designers may add other protocols on a case-by-case basis (example FTP at network application layer), but there is no requirement for an AFDX compliant LRU to implement this additional protocol. Physical layer is not specified here, but should be any of
39、 the ARINC Specification 664, Part 2, defined solutions. This means that any AFDX compliant LRU (including switch) can be connected to any AFDX network, as far as the Form and Fit requirements (specific to the System and not specified in this document) are respected. 1.3 Document Organization 1.3.1
40、ARINC Specification 664, Aircraft Data Network ARINC Specification 664 defines an Ethernet data network for aircraft installation. It is developed in multiple parts, listed as follows: Part 1 - Systems Concepts and Overview Part 2 - Ethernet Physical and Data Link Layer Specifications Part 3 - Inter
41、net-based Protocols and Services Part 4 - Internet-based Address Structures and Assigned Numbers Part 5 - Network Interconnection Services and Functional Elements Part 6 - Reserved Part 7 - Avionics Full Duplex Switched Ethernet (AFDX) Network Part 8 - Upper Layer Services ARINC SPECIFICATION 664 PA
42、RT 7 Page 2 1.0 INTRODUCTION 1.4 Related Documents 1.4.1 Relationship of this Document to Other ARINC Standards When standards for avionics systems and subsystems that use the capabilities provided by this specification are developed, they should incorporate the provisions of this specification by r
43、eference. References to this specification should assume the application of the most recent version of this Specification. A list of other ARINC documents that are related to this specification are listed below. ARINC Specification 653: Avionics Application Software Standard Interface ARINC Report 6
44、15A: Software Data Loader using Ethernet Interfaces ARINC Report 665: Loadable Software Standards 1.4.2 Relationship to Industry Standards IEEE Standard 802.3, 2000 Edition, is considered an integral part of this specification and is considered required reading. In this document, when referencing th
45、is standard, the title is shortened to simply “IEEE 802.3.” 1.4.3 RTCA and EUROCAE Documents RTCA and EUROCAE develop Minimum Operational Performance Standards (MOPS) that are applicable to avionics equipment, systems and processes. The latest revision of the following RTCA and EUROCAE documents per
46、tain to this Specification: RTCA DO-160/EUROCAE ED-14: Environmental Conditions and Test Procedures for Airborne Equipment. In this document, when referencing this standard, the title is shortened to simply “DO-160.” RTCA DO-254: Design Assurance Guidance for Airborne Electronic Hardware. RTCA DO-17
47、8B: Software Considerations in Airborne Systems and Equipment Certification. COMMENTARY Specific performance levels defined in the RTCA/EUROCAE documents are specified by the aircraft systems integrator according to application. 1.5 Document Precedence This Specification is based on IEEE Std 802.3.
48、The philosophy of this Specification is to define changes to the provisions of IEEE 802.3 only when the aeronautical environment or user desires conflict with the provisions of IEEE 802.3, or when it is necessary to remove ambiguity by restricting the options available to implementers. The contents
49、of this Specification are limited to describing these changes and option restrictions. In case of a conflict between this Specification and the applicable ISO and IEEE standards, this Specification should have precedence. ARINC SPECIFICATION 664 PART 7 Page 3 1.0 INTRODUCTION 1.6 Regulatory Approval Implementation of this standard should meet all applicable regulatory requirements. Manufacturers are urged to obtain all necessary information for such regulatory approval. This information is not contained in th
