scope:

This document serves as an ARINC Standard to define the IPS avionics architecture, functions, and interfaces, and to describe implementation options and constraints as well as high level details regarding the accommodation of different applications. The Airborne IPS System described in this standard may be hosted in a Communications Management Unit (CMU) or other equivalent avionics that provides the IPS network stack and air-ground routing functionality. This includes, as necessary, other systems that interface and interoperate with the CMU or equivalent function.

This document also describes the end-to-end context of ATN/IPS, as it is recognized that some of the requirements that are levied on the aircraft also impose similar requirements on the peer ground entities. This considers the various aspects of the potential ground entities, including deployment options and architectures, IPS coexistence with other protocol stacks, security, and other aspects. Therefore, ground requirements and considerations are also captured in Part 2 of this document. Figure 1-1 illustrates the ATN/IPS near-term context showing the overlay of IPS Gateways in the current communications environment where IPS-enabled aircraft and existing aircraft co-exist with combinations of existing and IPS-enabled ground systems.

Note that this figure does not intend to illustrate the various ground administrative domains, but rather it is intended to show flexibility to accommodate various IPS Gateway deployment options, e.g., placement at an Air-Ground Communication Service Provider (ACSP) access network, at an ANSP, etc.

The intent of this document, in coordination with other related industry standards, is to provide implementers of the Airborne IPS System with the level of detail necessary to interface with other aircraft systems and to interoperate securely with Ground IPS Systems.