This item is not available for sale.

Customers Who Bought This Also Bought

 

About This Item

 

Full Description

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),

7) Interval Management (IM), and 8) Oceanic Clearance Service (OCL);

c) CPDLC or Automatic Dependent Suveillance – Contract Mode (ADS-C) services:

1) Information Exchange and Reporting (IER), and

2) Position Reporting (PR);

d) Combined services (CPDLC and ADS-C):

1) 4-Dimensional Trajectory Data Link (4DTRAD).

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-228/DO-350 [10], 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 [5] and PU- 40 [12] 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 [10] and the ATN communication technologies.

NOTE:

1. Interoperability requirements needed to support B1 backward compatibility between Baseline 2 systems and Baseline 1 systems are defined in the ED-231/DO-353 document [13].

2. Interoperability requirements between Baseline 2 systems and FANS1/A aircraft are defined in the ED-230/DO-352 document [11].

PURPOSE

The purpose of this document is to define the set of requirements for the interoperability aspects of Baseline 2 datalink 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 [7] for each approval type associated with the elements of the CNS/ATM system.

NOTE: Based on ED-78A/DO-264 [7], 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.

 

Document History

  1. EUROCAE ED-229B


    INTEROPERABILITY REQUIREMENTS STANDARD FOR BASELINE 2 ATS DATA COMMUNICATION (BASELINE 2 INTEROP STANDARD)

    • Most Recent
  2. EUROCAE ED-229B


    INTEROPERABILITY REQUIREMENTS STANDARD FOR BASELINE 2 ATS DATA COMMUNICATION (BASELINE 2 INTEROP STANDARD)

    • Historical Version
  3. EUROCAE ED-229A


    INTEROPERABILITY REQUIREMENTS STANDARD FOR BASELINE 2 ATS DATA COMMUNICATIONS (BASELINE 2 INTEROP STANDARD)

    • Historical Version
  4. EUROCAE ED-229

    👀 currently
    viewing


    INTEROPERABILITY REQUIREMENTS STANDARD FOR BASELINE 2 ATS DATA COMMUNICATIONS (BASELINE 2 INTEROP STANDARD)

    • Historical Version