Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 4222

c) other applications such as aeronautical operational control (AOC) and aeronautical administrative communication (AAC). Note 1.— Provisions have been made to accommodate the exchange of information such as weather, flight plans, notices to airmen and dynamic real time air traffic flow management between aircraft operating agencies’ ground-based systems and ATS units. Note 2.— Provisions have also been made to accommodate aeronautical passenger communication (APC). 3.3.2 When the ATN is used in support of air traffic services, it shall conform with the provisions of this chapter. 3.3.3 Requirements for use of the ATN shall be made on the basis of regional air navigation agreements. 3.3.4 Recommendation.— Civil aviation authorities should co-ordinate, with national authorities and aeronautical industry, those implementation aspects of the ATN which will permit its world-wide safety, interoperability and efficient use, as appropriate. 3.4 SYSTEM LEVEL REQUIREMENTS Note.— The system level requirements are high-level technical requirements that have been derived from operational requirements, technological constraints and regulatory constraints (administrative and institutional). These system level requirements are the basis for the functional requirements and lower-level requirements. 3.4.1 The ATN shall use International Organization for Standardization (ISO) communication standards for open systems interconnection (OSI). 3.4.2 The ATN shall provide a means to facilitate migration to future versions of application entities and/or the communication services. Note.— It is an objective that the evolution towards future versions facilitates the backward compatibility with previous versions. 3.4.3 The ATN shall enable the transition of existing AFTN/CIDIN users and systems into the ATN architecture. Note.— The transition from the AFTN or from the CIDIN to the ATN is handled by AFTN/AMHS and CIDIN/AMHS gateways respectively, which are defined in Doc 9705, Sub-volume III. 3.4.4 The ATN shall make provisions whereby only the controlling ATS unit may provide ATC instructions to aircraft operating in its airspace. Note.— This is achieved through the current and next data authority aspects of the controller-pilot data link communications (CPDLC) application entity. 3.4.5 The ATN shall accommodate routing based on a pre-defined routing policy. 3.4.6 The ATN shall provide means to define data communications that can be carried only over authorized paths for the traffic type and category specified by the user. 3.4.7 The ATN shall offer ATSC classes in accordance with the criteria in Table 3-1.* * All tables are located at the end of this chapter. 4C 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5/11/95 1/11/01 No. 76 Note 1.— When an ATSC class is specified by an ATN application, packets will be forwarded in the ATN internet communications service on a best effort basis. Best effort basis means that when a route is available of the requested ATSC class, the packet is forwarded on that route. When no such route is available, the packet will be forwarded on the first known route of the ATSC class higher than that requested, or if there is no such route, first known route of the ATSC class lower than that requested. Note 2.— The ATN communications service will not inform application entities if the requested ATSC class was not achieved. It is the responsibility of the application entity to determine the actual transit delay achieved by local means such as time stamping. 3.4.8 The ATN shall operate in accordance with the communication priorities defined in Table 3-2 and Table 3-3. 3.4.9 The ATN shall enable exchange of application information when one or more authorized paths exist. 3.4.10 The ATN shall notify the appropriate application processes when no authorized path exists. 3.4.11 The ATN shall provide means to unambiguously address all ATN end and intermediate systems. 3.4.12 The ATN shall enable the recipient of a message to identify the originator of that message. 3.4.13 The ATN addressing and naming plans shall allow States and organizations to assign addresses and names within their own administrative domains. 3.4.14 The ATN shall support data communications to fixed and mobile systems. 3.4.15 The ATN shall accommodate ATN mobile subnetworks as defined in this Annex. 3.4.16 The ATN shall make provisions for the efficient use of limited bandwidth subnetworks. 3.4.17 The ATN shall enable an aircraft intermediate system to be connected to a ground intermediate system via concurrent mobile subnetworks. 3.4.18 The ATN shall enable an aircraft intermediate system to be connected to multiple ground intermediate systems. 3.4.19 The ATN shall enable the exchange of address information between application entities. 3.4.20 The ATN shall support the context management (CM) application when any of the other air-ground applications are supported. 3.4.21 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the context management (CM) application. 3.4.22 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the automatic dependent surveillance (ADS) application. 3.4.23 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the controller-pilot data link communications (CPDLC) application. 3.4.24 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the automatic terminal information service (ATIS) application. 3.4.25 The ATN shall be capable of establishing, maintaining, releasing and aborting application associations for the ATS message handling services (ATSMHS) application. 3.4.26 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the ATS interfacility data communication (AIDC) application. 3.4.27 Where the absolute time of day is used within the ATN, it shall be accurate to within 1 second of coordinated universal time (UTC). Note.— A time accuracy value may result in synchronization errors of up to two times the stated accuracy value. 3.4.28 The end system shall make provisions to ensure that the probability of not detecting a 255-octet message being mis-delivered, non-delivered or corrupted by the internet communication service is less than or equal to 10–8 per message. Note.— It is assumed that ATN subnetworks will ensure data integrity consistent with this system level requirement. 3.4.29 ATN end systems supporting ATN security services shall be capable of authenticating the identity of peer end systems, authenticating the source of application messages and ensuring the data integrity of the application messages. Note.— Application messages in this context include messages related to ATS, systems management and directory services. 3.4.30 ATN ground and air-ground boundary intermediate systems supporting ATN security services shall be capable of authenticating the identity of peer boundary intermediate systems, authenticating the source of routing information and ensuring the data integrity of routing information. 4D 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5/11/95 1/11/01 No. 76 3.4.31 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the exchange of directory information. 3.4.32 ATN systems supporting ATN systems management shall facilitate enhanced continuity of ATN operations, including the monitoring and maintenance of the quality of the communications service. 3.4.33 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the systems management (SM) application. 3.4.34 The ATN shall be capable of establishing, maintaining, releasing and aborting peer-to-peer application associations for the aviation routine weather report service (METAR) application. 3.5 ATN APPLICATIONS REQUIREMENTS Note 1.— Implementation of ATN application(s) within a State or region does not imply implementation of all of the ATN applications defined below. Note 2.— The implementation of pre-defined subsets of the ATN application technical provisions are allowed as detailed in Doc 9705. 3.5.1 System applications Note.— System applications provide services that are necessary for operation of the ATN air-ground applications, ground-ground applications and/or ATN communication services. 3.5.1.1 CONTEXT MANAGEMENT (CM) APPLICATION Note.— The CM application provides the capability for an aircraft to log on with an ATS ground system; in some instances the ground system will request the aircraft to contact a specific ground system. Once an appropriate connection is established, CM provides for the exchange of information on each supported ATN application including the network address of each, as appropriate. For ATN systems supporting security services, CM also obtains and exchanges key and key usage information. CM also provides the capability to update log-on information and the capability for an ATS ground system to forward log-on information to another ATS ground system. The registration function of the CM allows the sharing of information with other applications on the ground or on the aircraft. 3.5.1.1.1 The ATN shall be capable of supporting the following CM application functions:

Source: https://magyarkozlony.hu/hivatalos-lapok/7e70cec03f34e3c2efd8610b865b65591eafd701/dokumentumok/a55dc160549d57fa4db0035e37c6a6a98dd1a0b9/letoltes