EUROCAE ED 229
INTEROPERABILITY REQUIREMENTS STANDARD FOR BASELINE 2 ATS DATA COMMUNICATIONS (BASELINE 2 INTEROP STANDARD)
|Publication Date:||1 March 2016|
The scope of this document is the ATS applications that support the following air traffic services (ATS):
a) Context Management (CM) service:
1) Data Link Initiation Capability (DLIC);
b) Controller-Pilot Data Link Communication (CPDLC) services:
1) Air Traffic Control (ATC) Communication Management (ACM);
2) Clearance Request and Delivery (CRD);
3) ATC Microphone Check (AMC);
4) Departure Clearance (DCL);
5) Data Link Taxi (D-TAXI); 6) In-Trail Procedures (ITP); and
7) Oceanic Clearance Service (OCL);
c) Automatic Dependent Surveillance - Contract Mode (ADS-C) service:
1) Position Reporting (PR);
d) Combined services (CPDLC and ADS-C):
1) Information Exchange and Reporting (IER);
2) 4-Dimensional Trajectory Data Link (4DTRAD);
3) Dynamic Required Navigation Performance (DRNP); and
4) Interval Management (IM).
These ATS services supported by data communications are described in section 4 to the extent necessary to establish the INTEROP for the application functions needed to support them. The detailed specification of the ATS services can be found in the Baseline 2 SPR, ED-228A/DO-350A , Section 3, ATS Services.
NOTE: It is not intended to restrict the use of ATN applications for ATS or to restrict communication services from operating over other sub-networks. The INTEROP for such expanded implementations is outside the scope of the considered ATN profile. Parts of ICAO document 9880  that are identified as "out-of-scope" herein have not been considered for INTEROP. Therefore, INTEROP will need to be determined prior to supporting an out-of-scope part of these documents.
This INTEROP Standard documents the Interoperability Assessment (IA) performed for the functions defined in the Baseline 2 SPR document  and the ATN communication technologies.
1. Interoperability requirements needed to support B1 backward compatibility between Baseline 2 systems and Baseline 1 systems are defined in the ED-231A/DO-353A document .
2. Interoperability requirements between Baseline 2 systems and FANS1/A aircraft are defined in the ED-230A/DO-352A document .
The communication services addressed in this version of the INTEROP Standard are those used in ATN. These are the Upper Layer Communications Service (ULCS) and the Internet Communications Service (ICS) necessary to use any ATN mobile sub-network as defined in ICAO Annex 10.
NOTE: This INTEROP Standard does not consider the functional or interoperability aspects of the sub-networks or switching between multiple mobile subnetworks.
The ATS applications used by the Baseline 2 services are defined as a subset of Context Management (CM), Automatic Dependent Surveillance Contract (ADS-C) and Controller-Pilot Data Link Communication (CPDLC) of ICAO document 9880  as defined in this document.
1. This INTEROP Standard does not require implementing all ADS-C and CPDLC. However, CM is necessary to support either ADS-C or CPDLC.
2. This INTEROP Standard mentions the functional aspects of air traffic services ground-ground applications; however, the interoperability aspects are not considered.
3. This INTEROP Standard does not consider the functional or interoperability aspects of Aeronautical Operational Control (AOC) applications, relevant data links, or integration of ATN functionality with AOC functionality.
The purpose of this document is to define the set of requirements for the interoperability aspects of Baseline 2 data link systems. This document addresses ATN systems but would need to be amended to address other types of data link. This document is intended for use in conjunction with a consistent SPR standard, other INTEROP standards, and the guidelines described in ED-78A/DO-264  for each approval type associated with the elements of the CNS/ATM system.
Based on ED-78A/DO-264 , the INTEROP and SPR standards provide recommendations intended for government organizations, conference of governments, or agencies having statutory jurisdiction over the use and provision of air traffic services supported by data communications. These recommendations are for use by such government organizations to enunciate official policy, related to such matters, in aeronautical information publications (AIPs), notices to airmen (NOTAMs), airplane flight manuals (AFMs), and operator specifications.