RTCA DO-364A-2025 PDF

RTCA DO-364A-2025 PDF

Minimum Aviation System Performance Standards (MASPS) for Aeronautical Information/Meteorological Data Link Services

$587.50 $1,175.00 -50%
Publisher
Product Code: RTCA DO-364A
Stock In Stock
Edition: A
Published: 03/13/2025
Number of Pages: 908
File Size: 1 file, 10 Bytes

Available Options

Product Description

Scope of the Document This MASPS harmonizes AIS/MET Data Link Services minimum system requirements and for global Air Traffic Management (ATM) operations. AIS/MET information and associated attributes for the Services are assumed to be provided by approved AIS/MET service providers, and the information is assumed to be approved for aeronautical/operational use. This document builds on RTCA DO-364 with an update to the Eddy Dissipation Rate (EDR) Turbulence Service (ETS), adds a Collaborative Decision Making (CDM) Service titled Airborne Rerouting Information (ARI), and adds eight additional AIS/MET Services. These newly defined Services’ Service Descriptions used a different methodology to complete and harmonize the Operational Safety Assessments (OSAs) and Operational Performance Assessments (OPAs). The Special Activity Airspace (SAA) and the Weather Surveillance (WxS) Services were not updated and remain in the same form as in RTCA DO-364. The system description in the WxS Service Description is based on the Automatic Dependent Surveillance – Broadcast (ADS-B) data link. The differences between the Service Descriptions of the new Services and former Services include format, granularity of information exchange, terminology in sequence diagrams, system description, system operational characteristics, and system timing characteristics. Each Data Link Services System may specify a communication or data link specific for the scope of intended use for that AIS/MET Data Link Service System. This may include safety and non-safety links. A Service System has to consider the operational and performance requirements for that service, which could determine one or more links for operation of that Service System. As stated in the Introduction, Section 3.1, a Data Link Service System is not intended to infer any notional link as used today, rather it is meant to be agnostic to a link(s). The architectural design considerations of a Service System are also not meant to infer a physical location to perform a function of the Data Link Service System. One or more function(s) can be located on the ground, airborne, or even spatially located. This is a consideration for implementation. It should also be apparent that each Service System may have different functions physically located in different locations. This may happen to meet the operational performance requirements specific to that Service System. For example, the ODLPF, although the “O” relates to “onboard” may be physically located on the ground to perform that same function of an ODLPF. Effectively, it is the scope of this document to specify the minimum system standards for the intended use and not to specify or drive an implementation to meet the scope of a Service System. A key objective of the future ATM performance-based capabilities is to establish the aircraft and flight crew as an active primary participant. High-quality and reliable AIS/MET Data Link Services System information is necessary to support the implementation of this objective. Also needed for the future are improvements in aircraft performance predictability and operations efficiency, which are strongly dependent on AIS/MET Data Link Services System information. This MASPS builds on previously published standards by RTCA, EUROCAE, and other standards setting organizations (see Section 1.6) developed to support future ATM capabilities. It also draws on parallels with ARINC Specification 620-8, Data Link Ground System Standard and Interface Specification and ARINC Specification 622, ATS Data Link Applications over Aircraft Communications Addressing and Reporting System (ACARS) Air-Ground Network. These documents are intended to be used in conjunction with this MASPS to draw on similarities of the description of existing aeronautical information (AI)/MET applications and AIS/MET Data Link Services System. This document introduces processes and references protocols for air and ground communications, which may use satellite, very high frequency (VHF) links, high frequency (HF) links, or commercial links. It also considers various protocols like internet protocols (IPs) similar to the specifications detailed in ARINC 618, Air/Ground Character-Oriented Protocol Specification. Multiple links and protocols may be required to communicate the AIS and MET data and information. The Data Link Services described in this document are independent of Controller Pilot Data Link Communications (CPDLC) and the Services are not part of the message set of CPDLC. AIS/MET Data Link Services System may transmit over any air or ground data link unless limited by regulatory authority or performance limitations. The operational scenarios and use cases discussed in this document describe potential uses of AIS/MET Data Link Services System. Service Descriptions (Appendix A), OPAs (Appendix B), and OSAs (Appendix C) were developed to provide a basis on which minimum AIS/MET Data Link Services System performance standards could be derived. The requirements defined in Section 3 and Section 4 establish the baseline, minimum requirements that designers, manufacturers, installers, service providers, and users of AIS/MET Data Link Services System should evaluate to determine their appropriateness, when developing, deploying, and using such systems. Section 3.3 provides general requirements for AIS/MET Data Link Services System in response to results from the OPAs in Appendix B and the OSAs in Appendix C. A specific Service System may need to consider further requirements based on an OPA and an OSA, see the processes described in Section 3. The word “System” as used in this document includes all functions necessary for the system to properly perform its intended use and may be implemented in hardware and/or software. The Data Link Services System must provide service coverage, sufficient capacity, the number of connections, and consistency to support the intended Services. • Service coverage – Connectivity as the aircraft moves from one communication tower and/or one satellite to another. Describes geographical and temporal availability of the Service. • Network capacity – Ability to support multiple aircraft in a given area so the message traffic does not degrade in high-traffic areas. • Connection – Seamless communications when traveling at en route speeds/altitudes in extreme weather environments with fluctuating temperatures. • Consistency – Achieving all the above operating at 95% or greater of the time. AIS/MET Data Link Services will be delivered by systems that involve transmitting, receiving, and channel data link processing functions (cDLPFs). depicts a single path for inputs, outputs, and channels, there could be multiple inputs, outputs, and channels associated with a system. This basic system functionality can support a diverse set of intended uses, applications, and information implementing the Services in Appendix A. This document describes the AIS/MET Data Link Services System at two levels, the system and the services levels. 1. The System level is composed of all functions implemented between interfaces. 2. The Services level is defined by individual Service Descriptions in Appendix A and are implemented on this Services System. The channel function provides communication between aircraft and the ground or between aircraft. The transmitting and receiving functions could be duplicated in the same component within the System. The Services System starts at the external interface (I) to the transmitting Data Link Processing Function (tDLPF) and extends to include the cDLPF and the receiving Data Link Processing Function (rDLPF). The Services System ends at the external interface (O) from the rDLPF. The Services System also includes internal interfaces (2→3, A ↔B, and C↔D). The tDLPF includes the necessary capabilities to process AIS, ATM, and MET information for transmission, including managing the data link transactions. The rDLPF includes the necessary capabilities to process AIS, ATM, and MET information for reception, including the further routing of the information. The cDLPF includes communication systems employing a variety of signals-in-space that make use of aeronautical or non-aeronautical spectrum, e.g., terrestrial-based, aircraft-based, geosynchronous space-based, and low Earth orbit space-based. Note: These required conceptual and architectural elements have been described previously in RTCA DO-340, “Concept of Use (ConUse) for Aeronautical Information Services (AIS) and Meteorological (MET) Data Link Services”. RTCA DO-349, “Architecture Recommendations for Aeronautical Information (AI) and Meteorological (MET) Data Link Services”, used the terms Ground Data Link Processing Function (GDLPF), Data Link Services Provider Function (DLSPF), and Onboard Data Link Processing Function (ODLPF). While the scope, function, and architectural models from RTCA DO-349 provided a useful structure for classifying the system elements in the Service Descriptions in Appendix A of this MASPS, they are somewhat limiting for describing the flow of information for these Services because of their explicit inclusion of physical location references and implied send or receive functions associated with them. This is particularly true for the crosslink case where the Services System is comprised exclusively of onboard elements where the presentation of ODLPF-to-ODLPF communications is challenging given the GDLPF-to-ODLPF implied information flow in RTCA DO-349. The Appendix A Service Descriptions used the RTCA DO-349 functional terms because these systems had specific ground and/or air components. for example, the SAA Notification’s GDLPF transmits the message and receives the acknowledgment (ACK). Interface I→1 is the tDLPF interface from external entities that provide information. There may also be an interface to the tDLPF that provides other information needed to control the Services System, e.g., to maintain operational control, administrative control, and/or provide for remote configuration. Interface 2→3 is the tDLPF to rDLPF service-level interface. This interface is application layer specific, with respect to the Open Systems Interconnection model application layer and not to any other layer, e.g., transport or network. Only the cDLPF incorporates physical layer functions and provides signal-in-space communication. Interface 4→O is the rDLPF interface to external systems that provide end users with information (e.g., Flight Management Systems (FMS), User Interface (UI) of Electronic Flight Bag (EFB) application, Airline Operation Center (AOC)/Flight Operation Center (FOC), etc.). Interfaces A through D enable the Services System to exchange information through the cDLPF, e.g., terrestrial and/or satellite communication service providers. During a flight, a ground entity or the aircraft may transmit AIS, ATM, and/or MET information at varying intervals for multiple purposes and for multiple users. This document specifies different communication methods that can be used to exchange AIS, ATM, and/or MET information between information providers and air users and between aircraft. This document does not adopt any specific network, transport, or link layer models. Transmission and IPs should align with the International Civil Aviation Organization (ICAO) Doc 9896, Manual for the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocols. Three communications modes are envisioned for AIS, ATM, and MET Data Link Services System: (1) Broadcast, (2) Publish/Subscribe, and (3) Request/Reply. The Broadcast Mode is a communications method in which messages are sent without addressing them to specified recipients and without provisions for receipt confirmation. They are unidirectional transfers of information to any entity capable of receiving and interpreting the broadcast. The Publish/Subscribe Mode involves two-way interactions in which AIS, ATM, and/or MET information is initially sent to a subscriber and subsequent updates that meet subscription criteria are subsequently automatically or manually sent. The Request/Reply Mode involves a two-way interaction in which AIS, ATM and/or MET information is transmitted to the requestor in response to a specific request. Note: RTCA DO-308/EUROCAE ED-151, Operational Services and Environment Definition (OSED) for Aeronautical Information Services (AIS) and Meteorological (MET) Data Link Services, used the communications modes broadcast, contract, and demand. However, industry terminology, through initiatives such as Next Generation Air Transportation System and Single European Sky ATM Research, has migrated to the use of Publish/Subscribe for contract and Request/Reply for demand. In the Broadcast communications mode, messages are sent simultaneously to those users within the communications effective range (CER), without acknowledgement with delivery persistence. The delivery persistence is considered a quality-of-service discriminator for which requirements are not specified. In the Publish/Subscribe and Request/Reply communications modes, the possibility of sending messages with or without acknowledgement, error detection, and error correction exists. The error correction is considered a quality-of-service discriminator for which requirements are not specified. In this document, the terms data, message, and information are used extensively. Generally, they should be interpreted as follows: data are the binary 1s and 0s used to represent the base elements of information; messages are data formatted to facilitate transmittal; and information is data processed, organized, structured, and/or presented in a context that makes it useful. It may be necessary to transmit more than one message to deliver information. In addition to providing information from an external ground-based system to aircraft (uplink), aircraft may also collect and report information using external onboard sensors and avionics systems to external ground-based systems (downlink) and/or directly to other proximate aircraft (crosslink). Aircraft may be equipped with either a transmitting or a receiving capability but are not required to have both. The concepts of uplink, downlink, and crosslink were used in the development of the Service Descriptions in Appendix A. Purpose of the Document The purpose of this document is to provide Minimum Aviation System Performance Standards (MASPS) for Aeronautical Information Services (AIS) and Meteorological (MET) Data Link Services System. Eleven AIS/MET Data Link Services are fully defined in the Service Descriptions in Appendix A. This MASPS addresses system characteristics and allocation of requirements that support data link Services. This is intended to be useful to designers, manufacturers, installers, service providers, regulators, and users of the AIS/MET Data Link Services System. The requirements contained in this document are necessary to provide adequate assurance that AIS/MET Data Link Services System will function in an acceptable manner. Compliance with this standard is recommended as one means of assuring that AIS/MET Data Link Services System performs satisfactorily under all conditions normally encountered in aeronautical operations.

Be the first to write a review for this product.

Write a review

Note: HTML is not translated!
Bad           Good
RTCA DO-364A-2025 PDF

RTCA DO-364A-2025 PDF

$587.50 $1,175.00