UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

RTCA - DO-351B VOLUME 1 & 2

Interoperability Requirements Standard for Baseline 2 ATS Data Communications (Baseline 2 Interop Standard)

active, Most Current
Organization: RTCA
Publication Date: 21 September 2023
Status: active
Page Count: 427
scope:

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) Clearance Request and Delivery (CRD);

2) ATC Microphone Check (AMC);

3) Departure Clearance (DCL);

4) Data Link Taxi (D-TAXI);

5) Pairwise Trajectory Management (PTM); and

6) In-Trail Procedures (ITP);

c) Automatic Dependent Surveillance - Contract Mode (ADS-C) service:

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

1) Air Traffic Control (ATC) Communication Management (ACM);

2) Information Exchange and Reporting (IER);

3) 4-Dimensional Trajectory Data Link (4DTRAD);

4) Interval Management (IM); and

5) Position Reporting (PR).

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 SPR, ED-228B/DO-350B [19], 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] 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 SPR document [19] and the ATN communication technologies.

Interoperability requirements needed to support B2 Rev A backward compatibility between Baseline 2 Revision B ground systems and Baseline 2 Revision A only aircraft are defined in this document. Backward compatibility between Baseline 2 Revision B aircraft and Baseline 2 Revision A only ground systems is not supported.

Note:

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 [16] and ED-231B/DO-353B document [21].

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

Document History

DO-351B VOLUME 1 & 2
September 21, 2023
Interoperability Requirements Standard for Baseline 2 ATS Data Communications (Baseline 2 Interop Standard)
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)...
March 17, 2016
Interoperability Requirements Standard for Baseline 2 ATS Data Communications (Baseline 2 Interop Standard)
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)...
March 18, 2014
Interoperability Requirements Standard for Baseline 2 ATS Data Communications (Baseline 2 Interop Standard)
This standard provides the interoperability requirements (INTEROP) standard for the implementation of the Air Traffic Service (ATS) applications supporting the Baseline 2 data link services as...

References

Advertisement