1、 ETHERNET SWITCH UNIT (ESU) ARINC CHARACTERISTIC 765 PUBLISHED: December 29, 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 dur
2、ing 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 relianc
3、e on 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 CHARACTERISTIC 765 ETHERNET SWITCH UNIT Published: December 29, 2003 Prepared by the Airlines Electronic Engin
4、eering Committee Characteristic 765 Adopted by the Airlines Electronic Engineering Committee: October 14, 2003 Characteristic 765 Industry Review Completed: December 26, 2003 A description of the changes introduced by each supplement is included on Goldenrod paper at the end of this document. ii FOR
5、EWORD Aeronautical 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. airl
6、ines remain the 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 gui
7、dance and frequency 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 deve
8、lopment of technical 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
9、are known as ARINC 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,
10、 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 sta
11、ndardized 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 Pr
12、ovide 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 airline or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the exis
13、tence 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: a
14、) An Errata Report 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 CHARACTERISTIC
15、 765 TABLE OF CONTENTS ITEM SUBJECT PAGE 1.0 INTRODUCTION 1 1.1 Purpose of this Document 1 1.2 Related Documents 2.0 ETHERNET SWITCH UNIT 3 2.1 General Description 3 2.2 Mechanical Interface 2.3 Electrical Interface 3 2.3.1 Connector and Pin Arrangement 3 2.3.2 Power Requirements2.3.3 Physical Inter
16、faces 3 2.4 Functional Requirements 4 2.4.1 Initialization 42.4.1.1 Internal BITE Process 4 2.4.1.2 Initialization and Configuration 4 2.4.1.3 Initialization Time 42.4.2 Ethernet Connectivity 4 2.4.2.1 Physical Layer Requirements 2.4.2.2 Ethernet Ports 4 2.4.3 Ethernet Switching 5 2.4.4 Port Grouped
17、 VLAN 5 2.4.5 Protocols 2.4.6 IP Routing 6 2.4.7 Traffic Control and Filtering 6 2.4.8 Network Monitoring and Management Services 6 2.4.9 Configuration 7 2.4.9.1 Data Base2.4.9.2 Protocol / Parallel Connection 7 2.4.9.3 Fault Isolation / Detection 7 2.4.9.4 ESU Configuration Management 7 ATTACHMENTS
18、 1 ESU Connector Definition 8 APPENDICES A List of Acronyms 12 ARINC Standard - Errata Report ARINC IA Project Initiation/Modification (APIM) Guidelines for Submittal ARINC CHARACTERISTIC 765 - Page 1 1.0 INTRODUCTION 1.1 Purpose of this Document This document defines an Ethernet Switch Unit which f
19、its in the general architectural philosophy and aircraft infrastructure for the proper use and interface of various information network related equipment. Equipment conforming to this document enables each respective equipment to operate in concert when integrated with other relevant equipment. This
20、 document is intended to be used in conjunction with ARINC Specification 628: Cabin Equipment Interfaces (CEI), Part 9, Cabin Management and Entertainment System, Cabin Information Network and other aircraft systems. ARINC Specification 628 Part 9 defines standards for the aircraft Cabin Information
21、 Network wiring, connectors, power, identification codes, space envelopes, and mounting principles. The equipment itself is not the subject of this specification because it may be unique to the system manufacturer or marketplace-driven. Design guidelines are included for informational purposes as th
22、ese guidelines impact the interfaces and installation of cabin equipment aboard the aircraft. A generic configuration of cabin subsystems interconnection is shown in the “Cabin Information Network Block Diagram“ (see Attachment 1 to ARINC Specification 628 Part 9). The block diagram also includes co
23、nnections with other systems that contribute to the operation of the aircraft network. 1.2 Related Documents The latest revisions of the following documents are pertinent to the design of equipment intended to meet this standard. ARINC Characteristic 763: Network Server System ARINC Report 604: Guid
24、ance for Design and Built-in Test Equipment (BITE) ARINC Report 606: Guidance for Electrostatic Sensitive Device Utilization and Protection ARINC Report 607: Design Guidance for Avionics Equipment ARINC Report 609: Design Guidance for Aircraft Electrical Power Systems ARINC Report 615A: Software Dat
25、a Loader Using Ethernet Interface ARINC Report 624: Design Guidance for Onboard Maintenance System (OMS) ARINC Specification 429: Mark 33 Digital Information Transfer System ARINC Specification 600: Air Transport Avionics Equipment Interfaces ARINC Specification 628: Cabin Equipment Interfaces (CEI)
26、 Part 1, Cabin Management and Entertainment System - Peripherals ARINC Specification 628: Cabin Equipment Interfaces (CEI) Part 3, Cabin Management and Entertainment System - In-Flight Entertainment ARINC Specification 628: Cabin Equipment Interfaces (CEI) Part 4A ARINC Specification 628: Cabin Equi
27、pment Interfaces (CEI) Part 9, Cabin Management and Entertainment System Cabin Information Network ARINC Specification 664: Aircraft Data Network ATA Specification 100, “Specification for Manufactures Technical Data” ARINC CHARACTERISTIC 765 - Page 2 1.0 INTRODUCTION 1.2 Related Documents (contd) EI
28、A-RS-232, “Interface Between Data Terminal Equipment and Data” Federal Aviation Regulation (FAR) Part 25 - Airworthiness Standards: Transport Category Airplanes IEEE 802.1D, “MAC bridges” IEEE802.1P, Traffic Class Expediting and Dynamic Multicast Filtering IEEE802.1Q, Virtual LAN (VLAN) Support IEEE
29、 802.3, “Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specification” IEEE 802.3ad, “Link Aggregation” IEEE 802.11, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications” IEEE 802.11b, “Wireless LAN Medium Access Control
30、 (MAC) and Physical Layer (PHY) Specifications: High Speed Physical Layer Extension” MIL-STD 883, Method 3025.2, “Microelectronics Test Methods and Procedures” RTCA DO-160 / EUROCAE ED 14, “Environmental Conditions and Test Procedures for Airborne Equipment” RTCA DO-178 / EUROCAE ED-12, “Software Co
31、nsiderations in Airborne Systems and Equipment Certification” RTCA DO-199, “Potential Interference to Aircraft Electronic Equipment from Devices Carried Aboard” RFCs referenced in ARINC 664 Part 3 ARINC CHARACTERISTIC 765 - Page 3 2.0 ETHERNET SWITCH UNIT 2.1 General Description Switched Ethernet ne
32、tworks consist of end-systems (devices), network components (e.g. switches, gateways or routers) as well as interconnecting wires. In this topology, the basic function of a switch as a network component is to link together segments of the networks to which various devices are being connected. The Et
33、hernet Switch Unit (ESU) provides a wired network connection between the connected devices. It is based on interfaces defined by ARINC Specification 664 and IEEE 802.3. The ESU should provide, as a minimum, a data link layer (OSI Layer 2) multi-port bridging mechanism, as defined in IEEE 802.1D and
34、Q/P, based on MAC destination address information supporting destination address switching for unicast, multicast, and broadcast Ethernet message transfer. In addition, the ESU should provide IP routing and filtering capabilities. Several ESUs may be installed in an aircraft for the connection of sy
35、stems or devices based on Ethernet interfaces. Therefore, the ESU should have the capability to connect end-systems as well as other network components. 2.2 Mechanical Interface The ESU should comply with the dimensional standards of ARINC Specification 600. The box size should be 4 MCU with a size
36、2 connector as shown in Attachment 1, Figure 1-1. 2.3 Electrical Interface 2.3.1 Connector and Pin Arrangement The connectors and the pin arrangement should be as shown in Attachment 1, Figures 1-2, 1-3, and 1-4. 2.3.2 Power Requirements The ESU should operate from 115 VAC/400 Hz or variable frequen
37、cy 115 VAC/360 to 800 Hz. The power consumption of the ESU should be kept to a minimum and should not exceed 100 VA. 2.3.3 Physical Interfaces The ESU should provide the following interfaces: A minimum of thirteen (13) Ethernet ports A minimum of two (2) Ethernet ports (insert C using #22 AWG pins)
38、One (1) Ethernet port on the front plate (RJ-45 jack with spring loaded cover) A minimum of two (2) ARINC 429 ports (optional) A minimum of five (5) input keylines according to ARINC 720 A minimum of one (1) EIA-RS 232 port (optional) A minimum of four (4) address identification pins Six (6) manufac
39、turer defined pins ARINC CHARACTERISTIC 765 - Page 4 2.0 ETHERNET SWITCH UNIT 2.4 Functional Requirements The ESU is a central network unit. It is responsible for significant portions of the airborne network security as specified in ARINC Specification 664. The minimum provisions delineated in the f
40、ollowing subsections are applicable. 2.4.1 Initialization The initialization sequence should be automatically activated after: Power on Manual reset Automatic reset (if implemented) The ESU should operate with the following power-on sequence: Internal BITE process Initialization and configuration 2.
41、4.1.1 Internal BITE Process The ESU should include a Power-On Self-Test. 2.4.1.2 Initialization and Configuration The ESU should initialize the connected equipment and components and be capable of setting up a customized aircraft configuration. 2.4.1.3 Initialization Time Full initialization and pow
42、er-on self-test should be completed within 60 seconds. COMMENTARY Initialization and Power-On Self-Test should be quicker than connected systems and units in order to not delay the full operation of the cabin systems after power on. For maintenance and troubleshooting, the waiting time for unit set
43、up should be limited and minimized. 2.4.2 Ethernet Connectivity The ESU should provide wired connectivity based on Ethernet according to ARINC Specification 664 and IEEE 802.3. 2.4.2.1 Physical Layer Requirements The ESU should conform to the basic physical layer characteristics of the network as de
44、scribed in ARINC Specification 664 and use connectors defined in ARINC Specification 600. 2.4.2.2 Ethernet Ports The ESU should provide at least 16 Ethernet ports. The ESU should be capable of filtering and transmitting frames with maximum speed on all Ethernet ports continuously according to ARINC
45、664. The ESU should provide the capability to enable/disable/configure each Ethernet port independently. ARINC CHARACTERISTIC 765 - Page 5 2.0 ETHERNET SWITCH UNIT Each Ethernet port should provide the following capabilities: Support the maximum bandwidth of the Ethernet modes 10BaseT and 100BaseTX
46、Operate as either a 10BaseT Ethernet interface or as a 100BaseTX Fast Ethernet interface Sense the speed of 10/100Mbps automatically Operate in either half-duplex of full duplex mode Detect and negotiate the operational modes automatically Be automatically compatible with IEEE 802.3 according to its
47、 specific configuration. 2.4.3 Ethernet Switching The ESU should provide OSI Layer 2 switching to separate the network into multiple domains as specified in ARINC Specification 664 and IEEE 802.1D. In general, the ESU should have the capability to determine whether a frame conforms to a set of crite
48、ria and to distribute uncorrupted frames to appropriate destinations. The policy-based frame forwarding as defined in ARINC Specification 664 (e.g., check of CRC, frame length, destination address) should be supported. For each frame the contents of the Destination Address field should be used to de
49、termine the appropriate Ethernet port(s) to which the frame has to be forwarded. For “plug and play” capabilities, the ESU should be capable of learning and building the forwarding address/port table dynamically according to IEEE 802.1D Transparent Bridging/Switching. The ESU should be capable of maintaining the address dynamically learned and disabling the port if the device is disconnected. The ESU should be capable of statically configuring or provisioning MAC addresses into the address/port table (port security function). 2.
