ARINC - 858P2
INTERNET PROTOCOL SUITE (IPS) FOR AERONAUTICAL SAFETY SERVICES PART 2 IPS GATEWAY AIR-GROUND INTEROPERABILITY
|Publication Date:||21 June 2021|
Since the end-state goal for ICAO and the aviation industry is an aviation network communication infrastructure based on IPS, the transition strategy for achieving that end state is critical to the success of IPS adoption. For FANS-1/A users, which include oceanic and remote airspace as well as an increasing number of domestic enroute programs, the challenge is transitioning from ACARS network protocols to IPS. For domestic Europe, which uses the B1 application set (with a planned upgrade to the B2 application set) over OSI protocols, the challenge is transitioning from OSI to IPS.
"Big bang" approaches do not tend to work in aviation given the large numbers of aircraft equipped with legacy systems, the numbers of ground systems that need to change in short order, and the international operation of many aircraft. Changing aircraft equipment is expensive and time consuming. And ideally, the ANSPs should not be required to continually upgrade ground systems or implement duplicate networks to deal with different aircraft configurations.
For network protocol compatibility, the desired outcome is the ability of the protocol to meet the performance and delivery requirements for the provided services. Since the network protocol should largely be invisible to the end user, as long as application compatibility is maintained, the main concern then becomes how to make different network technologies interoperate with minimal impact to systems on the aircraft and on the ground. Since the introduction of IPS-enabled avionics and ground systems is expected to happen over an extended time period, the IPS-based systems will need to be interoperable with existing ACARS and ATN/OSI aircraft and ground systems. Accommodation of IPS during the transition period will be accomplished via ground-based IPS Gateways, and the gateway architecture and functional requirements are described in this document.
Figure 1-1 illustrates the ATN/IPS near-term context showing the overlay of IPS Gateways in the current (at the time of this writing) 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 IPS Gateway with the level of detail necessary to interoperate securely with Airborne IPS Systems and with other ground systems.