Search Results

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Part 0 has been adjusted to reflect technical changes made in Supplements to Parts 1 through 5 in conjunction with the technical changes made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 – Overview of ARINC 653 Part 1 – Required Services Part 2 – Extended Services Part 3A – Conformity Test Specification for ARINC 653 Required Services Part 3B – Conformity Test Specification for ARINC 653 Extended Services Part 4 – Subset Services Part 5 – Core Software Recommended Capabilities The term “this document” refers to Part 0 only, while the term “ARINC 653” or “the Specification” refers to the whole set of ARINC 653 documents, currently Parts 0 to 5.

The purpose of this document is to provide guidelines for integrating previously standalone cabin systems such as cabin management systems, In-Flight Entertainment (IFE) systems, In-Flight Connectivity (IFC) systems, galley systems, surveillance systems, etc. Resource sharing between systems can reduce airline costs and/or increase functionality. But, as systems expose their internal resources to external systems, the risk of an intrusion that could degrade function and/or negatively expose the supplier’s or airline’s brand increases. This document provides a recommended IP networking design framework between aircraft systems to reduce the operational security threats while still supporting the necessary intersystem routing.

ARINC 858 Part 1 defines the airborne data communication network infrastructure for aviation safety services using the Internet Protocol Suite (IPS). ARINC 858 builds upon ICAO Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. IPS will extend the useful life of data comm services presently used by operators, e.g., VDL, Inmarsat SBB, Iridium NEXT, and others. It represents the evolutionary path from ACARS and ATN/OSI to the end state: ATN/IPS. ARINC 858 includes advanced capabilities such as aviation security and mobility. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

ARINC Report 686 represents the consensus of industry to prepare a roadmap migration from IPv4 to IPv6. This document describes airline objectives (air and ground side when possible) towards the development and introduction of IPv6. There are three distinct elements considered: 1) the applications for addressing aspects 2) the communication network(s) over which the applications are running for the IP protocol level itself and associated features, and 3) the physical link(s) the network(s) interface.

This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Part 0 will be made more consistent with Parts 1 through 5 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.

This specification provides Ethernet physical parameters and data link layer specifications for use in a commercial aircraft environment. This specification provides general and specific guidelines for the use of IEEE 802.3 compliant Ethernet, 2000 edition. Physical layer and Medium Access Control (MAC) sub-layers are expected to comply with the Open System Interconnection (OSI) Reference Model to enable maximal utilization of off-the-shelf components, both hardware and software, for aviation use. The Ethernet Physical layer specification defines the electrical and optical parameters for the 10BASE-T, 100BASE-TX, and 100BASE-FX Ethernet implementations. This specification references ARINC Specification 600: Air Transport Avionics Equipment Interfaces for definition of copper-based implementations of the Ethernet Physical layer.

ARINC 628, Part 9 defines general architectural philosophy and aircraft infrastructure for the proper use and interface of various cabin information network related equipment. It specifies a generic on-board infrastructure with commercial server technology, high-speed data communication and exchange via wired and wireless LAN for a wide range of applications. Supplement 5 significantly modifies the standard to remove references to obsolete cabin information network definition. It adds references to current cabin network definitions, ARINC 664: Aircraft Data Network and ARINC 808: Third Generation Network (3GCN).

This report sets forth guidance for IP-based onboard networks and systems residing in the Airline Information Services (AIS) and Passenger Information and Entertainment Services (PIES) Domains by establishing a common set of security related data elements and format(s) that are produced by aircraft systems, suitable for use by airline IT and/or avionic supplier analytical ground tools.

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

The purpose of this specification is to define test procedures to verify the implementation of the Controller Area Network (CAN) interface for Galley Systems, as defined in ARINC Specification 812A, Part 1.

This document is the first of a multi-part specification that will provide a catalog of cabin connector and cables that may be used in ARINC Standard cabin systems, including In-Flight Entertainment. Part 1 describes connector and cable requirements and evaluation criteria for the interface components used in the integration of cabin systems. Future releases will define connectors, contacts, and termination methods in Part 2. Cables will be specified in Part 3.

This Specification defines general architectural philosophy and aircraft infrastructure for the proper use and interface of various cabin related IFE equipment. Compliance with ARINC Specification 808 allows each respective system to operate in concert when integrated with other relevant cabin equipment. ARINC Specification 808 defines standards for the aircraft 3rd Generation Cabin Network (3GCN), IFE Cabin Distribution System (CDS), wiring, connectors, power, identification codes, space envelopes, and mounting principles. Although some of these standards also apply to 3GCN wireless IFE systems, the overall 3GCN wireless IFE network specification is covered in ARINC Specification 820. The equipment itself is not a subject of this specification because it may be unique to the system manufacturer or marketplace-driven. Design guidelines are included for informational purposes as these guidelines impact the interfaces and installation of cabin equipment aboard the aircraft.

This Specification was written to support future aeronautical applications and services beyond those using Transmission Control Protocol/Internet Protocol (TCP/IP). The initial focus is to support air/ground applications using the Aeronautical Telecommunications Network (ATN). These include Controller-Pilot Data Link Communication (CPDLC), Flight Information System (FIS), and Context Management Application (CMA). Supplement 1 was written to allow interoperation with non-IP protocols and services and upper layer services with respect to the OSI reference model. Supplement 1 reflects ICAO Aeronautical Communication Panel recommendations.

This standard consolidates and defines various interface parameters, except for power, that may be required to support the operation of an IFES on any airplane model. Supplement 2 adds an Ethernet interface between the aircraft Cabin Services System (CSS) and In-Flight Entertainment System. This interface may be used to exchange information between the CSS and The Passenger Service System (PSS), passenger address/entertainment, airplane mode, navigation, and operational data.

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 permission. This document also highlights the additional performance requirements of avionics systems within the context of AFDX.

This document provides standards necessary to achieve interchangeability between equipment providers. Attachment 1 specifies an interconnection scheme by which aircraft can be wired to enable full interchangeability between OMTS products from different suppliers. Attachment 1 also specifies a minimum interface configuration which can be viewed as a desirable future implementation on new aircraft because of its potential for significant weight and space savings along with the possibility for less complex integration into the OEM production environment. The OMTS standard includes the physical interfaces, wiring, connectors, space envelopes, equipment chassis, unit co-location requirements, and power requirements. The basic functionality within each component of the OMTS is covered. Detailed functionality, protocols, and design parameters unique to each system supplier are not covered in this document.

This specification defines Network and Transport layer provisions for data networks that are installed on commercial aircraft. The definitions are based on Internet Engineering Task Force (IETF) Internet protocol and service standards that have been published as Request for Comments (RFC). In some cases the protocols and services are tailored for use on board aircraft. The specification identifies two types of networks: First, Compliant Aircraft Data Network, which operates fully within the applicable Internet specifications. Second, Profiled Aircraft Data Network, in which one or more industry standard protocols have been extended to address the unique environment of aircraft installations. Within the specification, the functionality of Internet protocols and services are defined with the intent that interoperability of components connected to onboard data networks can be achieved without undue restrictions on the component designer.