ANNEX 10, VOLUME III, PART 1 AMDT 79
25 NOVEMBER 2004 / SWGN1/10 WP 1013
13 August 2006
/ International Civil Aviation Organization
WORKING PAPER /
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
SUB-WORKING GROUP N1
------
ANNEX 10, Volume III, CHAPTER 3
AERONAUTICAL TELECOMMUNICATION NETWORK
VERSION 1.0 (Rev.) (Sec)
1. Proposed updates to definitions.
1.1Definition for the ATN and the ATN/OSI and ATN/IPS
1.1Annex 10, Volume III, Part I, Chapter 1 contains the following definition for the Aeronautical Telecommunication Network: (ATN)
Aeronautical telecommunication network (ATN). An internetwork architecture that allows ground, air-ground and avionic data subnetworks to interoperate by adopting common interface services and protocols based on the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) reference model.
However, in Doc. 9705, paragraph 1.1.1 in note 1 the ATN is described as follows:
The aeronautical telecommunications network (ATN) comprises application entities and communication services which allow ground, air-to-ground and avionics data subnetworks to interoperate by adopting common interface services and protocols based on the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) reference model.
The same paragraph in Doc. 9705 describes, in the form of a definition, ATN as
ATN - The symbol used to designate the aeronautical telecommunication network.
1.1.2.Introduction of the internet protocol suite (IPS) in the ATN
1.1.2.1With the introduction of the IPS in the ATN, the ATN is not longer based on a common set of protocols (i.e. OSI standards), but incorporates also protocols and standards developed by the internet engineering task force (IETF). Although the end goal is that the ATN eventually is using IETF standards, amortizing current or planned investments in implementing OSI standards in the ATN (such as ground-ground implementations in the ASIA/PAC Region and air-ground implementations (VDL Mode 2) in the EUR Region) are expected to require for quite some time co-existence in the ATN of OSI and IPS protocols.
1.1.2.2The current provisions for the ATN (Annex 10, Volume III, Part I, paragraph 3.4.1 stipulates that:
3.4.1 The ATN shall use International Organization for Standardization (ISO) communication standards for open systems interconnection (OSI).
This provision links the ATN exclusively to the OSI standards and protocols and a proposal has been developed to complement this provision with the following:
3.4.1 bis The ATN shall use Internet Society (ISOC) communication standards for the internet protocol suite (IPS).
1.1.3.Through the introduction of IPS in the ATN, referencing common interface services and [common] protocols is not longer appropriate. Furthermore, the reference to the OSI reference model should also be removed as the IPS based ATN is not following all layers of the OSI reference model.
1.1.4.It should be noted that, although the ground-ground part as well as the avionics part of the ATN provide telecommunication services in the aeronautical fixed service (AFS), the air-ground part of the ATN does not qualify the ATN as a network in the aeronautical fixed service. (air-ground communications are two-way communications between aircraft and stations or locations on the surface of the Earth; air-to-ground and ground-to-air communications are one-way communications to stations on the surface of the Earth or to the aircraft respectively)
1.1.5.The AFTN is defined in Annex 10, Volume II, as follows:
Aeronautical fixed telecommunication network (AFTN). a worldwide system of aeronautical fixed circuits provided, as part of the aeronautical fixed service, for the exchange of messages and/or digital data between aeronautical fixed stations having the same or compatible characteristics.
1.1.5.1The relevant characteristics for the AFTN are contained in Annex 10, Volume II, Chapter 4, paragraph 4 and Volume III, Chapter 8
1.1.6. Considering the comments above, it is proposed to amend the definition for the ATN as follows which generalizes the definition and brings it more in line with the current definition for the AFTN and the aeronautical fixed service (AFS).
Aeronautical telecommunication network (ATN). Anglobal internetwork architecture that allows ground, air-ground and avionic data subnetworks to exchange messages primarily for the safety of air navigation and for the regular, efficient and economic operation of air services. interoperate by adopting common interface services and protocols based on the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) reference model.
1.1.6.1It should be noted that this definition enables the use of the ATN for ATS communications, aeronautical operational control and aeronautical administrative messages. The use of air-ground links is, through the ITU Radio Regulations, only reserved for communications related to the safety and regularity of flight (ATS communications and AOC). Specific definitions for an ATN based on OSI standards and an ATN based on IPS standards are not longer considered necessary. The proposed new definition for ATN should replace the current definition in Annex 10, Volume III, Part I, Chapter 1.
1.2Aeronautical administrative communication (AAC)
AAC is not defined in other Annexes. However, in Annex 10, Volume II, paragraphs 4.4.1.1 and 4.4.1.1.7 mention and specify aeronautical administrative messages as follows:
Aeronautical administrative messages shall comprise:
a)messages regarding the operation or maintenance of facilities provided for the safety or regularity of aircraft operations
b)messages concerning the functioning of aeronautical telecommunication services
cmessages exchanged between civil aviation authorities relating to aeronautical services
1.2.1This seems to be not in line with the current definition for AAC in Annex 10, Volume IIi, which is:
Aeronautical administrative communication (AAC). Communication used by aeronautical operating agencies relating to non-safety communications for the business aspects of operating their flights and transport services.
1.2.2In order to keep the definitions for Aeronautical Administrative Messages and aeronautical administrative communications in line with each other, the following new definition for AAC is proposed:
Aeronautical administrative communications (AAC). Communications necessary for the exchange of aeronautical administrative messages. (Re. Annex 10, Volume II, paragraph 4.4.1.6
1.2.3It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions).
1.3Aeronautical operational control (AOC)
1.3.1.The term “operational control” (also known as OPC) is used in various instances in the Annexes, and defined in Annex 6, Chapter 1 as “the exercise of authority over the initiation, continuation, diversion or termination of a flight in the interest of the safety of the aircraft and the regularity and efficiency of the flight”.
The definition for AOC rather defines AOC (as a communication service) as a communication for OPC. The following amendments to the definition for AOC are proposed, in order to align the definition for AOC with that for operational control
Aeronautical operational control communications (AOC). Communicationsnecessary required for the exercise of operational control ((Re. Annex 6 – Part I, Chapter 1 (Definitions)) authority over the initiation, continuation, diversion or termination of flight for safety, regularity and efficiency reasons
1.3.2It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions).
1.4Automatic Dependent Surveillance Contract (ADS-C)
1.4.1The following definition for ADS-C has been developed by the OPLINK Panel
Automatic dependent surveillance – contract (ADS-C) A means by which the terms of an ADS-C agreement will be exchanged between the ground system and the aircraft, via a data link, specifying under what conditions ADS-C reports would be initiated, and what data would be contained in the reports
Note: The abbreviated term ADS-contract is commonly used to refer to ADS event contract, ADS demand contract, ADS periodic contract or an emergency mode
1.4.2This new definition will be included in Annex 11. The current definition in Annex 11 for ADS, which is dentical to the same definition in Annex 10, Volume III, Part I, Chapter 3, will be removed from Annex 11. Current definition for ADS in Annex 10, Volume III, Part I Chapter 3 should be replaced with the new definition for ADS-C.
1.4.3 It is also proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions).
1.5Automatic terminal information service (ATIS)
1.5.1Annex 11, Chapter 1 already contains a definition for ATIS. It is proposed to add to the current definition for automatic terminal information service in Annex 10, volume III the following (Re. Annex 11, Chapter 1 – Definitions)
1.5.2It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions).
1.6Data link – automatic terminal information service (D-ATIS)
1.6.1Annex 11, Chapter 1 already contains a definition for D-ATIS. It is proposed to add to the current definition for data link-automatic terminal information service in Annex 10, volume III the following (Re. Annex 11, Chapter 1 – Definitions)
1.6.2It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions).
1.7Air traffic service ATS
1.7.1Annex 11, Chapter 1 already contains a definition for ATS. It is proposed to add to the current definition for air traffic service in Annex 10, volume III the following (Re. Annex 11, Chapter 1 – Definitions)
1.7.2It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions)
1.8Controller-pilot data link communication (CPDLC)
1.8.1.This definition is already contained in Annex 10, Volume II, Chapter 1 and Annex 11, Chapter 1. The definition used in these Annexes is as follows:
Controller-pilot data link communications (CPDLC). A means of communications between controller and pilot, using data link for ATC communications.
This is identical as the original definition for CPDLC in Annex 10, Volume III, Part I Chapter 3. It is proposed to keep the definition in line with the definitions as contained in Annex 10, Volume II and Annex 11. A reference to Annex 11, Chapter 1 – Definitions should be added to this definition.
1.8.2It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions)
1.9Flight information service (FIS)
1.9.1.The definition for FIS contained Annex 11 is identical to the definition for FIS contained in Annex 10 – Volume iii, Part I. A reference to the definition in Annex 11 should be added to the definition contained in Annex 10.
I1.9.2.n addition, a new definition for D-FIS should be added, along the same lines as for D-ATIS, as follows:
Data link-flight information service (D-FIS). The provision of FIS via data link
1.9.3.It is proposed to move this definition to Annex 10, Volume III, Part I, Chapter 1 (Definitions)
2.Suggested definition for ATN/OSI and ATN/IPS
In the light of the proposed amended definition for the ATN, where references to OSI have been removed, as well as the paragraphs 3.4.1 and 3.4.1 bis these suggested definition are no longer necessary.
3. Paragraph 3.2.
3.1The new text for paragraph 3.2 as discussed in WGN06 is as follows:
The ATN and the associated application processes have been designed in support of the communications, navigation, surveillance and air traffic management (CNS/ATM) systems. The ATN is specifically and exclusively intended to provide data communications services to air traffic service providers organizations and aircraft operating agencies supporting the following types of traffic:
1) air traffic services communications (ATSC)
2) aeronautical operational control (AOC)
3) aeronautical administrative communication (AAC)
3.2Since all of the material in Annex 10 is in support of CNS/ATM systems, reference to CNS/ATM can be deleted.
3.3It is proposed to amend this paragraph further as follows:
The ATN and the associated application processes have been designed in support of the communications, navigation, surveillance and air traffic management (CNS/ATM) systems. The ATN is specifically and exclusively intended to provide data communications services to air traffic service providers organizations and aircraft operating agencies supporting the following types of traffic:
1) air traffic services communications (ATSC);
2) aeronautical operational control commmunications (AOC); and
3) aeronautical administrative communications (AAC)
4.Paragraph 3.3.1
4.1This paragraph stipulates that the ATN shall provide communication services and application entities in support of …..
4.2The application entity is part of an application process concerned with communication within the ATN and as such an element in providing communication services. It is proposed to delete this reference. Furthermore, the list is not necessary limited and, if necessary, other communication services can be added in the future.
4.3It is proposed to amend paragraph 3.3.1 as follows:
The aeronautical telecommunication network (ATN) shall provide communication services and application entities in support of:
a) the delivery of air traffic services (ATS) to aircraft;
b) the exchange of ATS information between ATS units; and
c) other applications such as aeronautical operational control (AOC) and aeronautical administrative communincation (AAC).; and
d) aeronautical administrative messages (AAC).
5.Paragraph 3.3.3
5.1As is stipulated in paragraphs 3.4.1 and 3.4.1 bis, the ATN can use either OSI standards or IPS standards. It is therefore necessary that the regional agreement provided for in paragraph 3.3.3 shall identify the aereas in which the provisions of paragraph 3.4.1 and of paragraph 3.4.1. bis are applicable.
5.2It is therefore proposed to amend paragraph 3.3.3 as follows:
Requirements for implementation of the ATN shall be made on the basis of a regional air navigation agreement. This agreement shall specify the area in which the provisions of paragraph 3.4.1 or 3.4.1 bis below are applicable.
6.Paragraph 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
6.1WG N proposed to reword this paragraph into a standard.
In telecommunications, the term gateway has the following meanings:
- In a communications network, a network node equipped for interfacing with another network that uses different protocols.
- A gateway may contain devices such as protocol translators, impedance matching devices, rate converters, fault isolators, or signal translators as necessary to provide systeminteroperability. It also requires the establishment of mutually acceptable administrative procedures between the two networks.
- A protocol translation/mapping gateway interconnects networks with different network protocol technologies by performing the required protocol conversions.
Therefore, the use of gateways do not enable a transition of existing AFTN or CIDIN users into the ATN per se; they rather allow these users to interoperate with the ATN.
It is proposed to replace the current text of paragraph 3.4.3 into
AFTN/AMHS and CIDIN/AMHS gateways shall ensure the interoperability of AFTN or CIDIN stations or networks with the ATN
7.Paragraph 3.5.1.1
7.1The current text of paragraph 3.5.1.1 is as follows:
3.5.1.1 CONTEXT MANAGEMENT (CM) APPLICATION
3.5.1.1.1 The ATN shall be capable of supporting the following DL applications as contained in Doc. 9694 (Manual on Data link applications Part II)
7.2It seems that 3.5.1.1.1 does not relate to context management and can be deleted.
Changes proposed are as follows:
3.5.1.1 CONTEXT MANAGEMENT (CM) APPLICATION
3.5.1.1.1 The ATN shall be capable of supporting the following DL applications as contained in Doc. 9694 (Manual on Data link applications Part II)
83.5.1.2 ATN directory services (DIR)
8.1Paragraph 3.5.1.2.1 needs the following change since reference to Doc. 9705 is already included at the beginning of the ATN SARPs.
3.5.1.2.1 The ATN shall be capable of supporting following DIR applications as contained in Doc. 9705 functions:
b) directory information retrieval; and
c) directory information modification.
9.Section 3.5.2
9.1Section 3.5.2 This section addresses air-ground applications. As an editorial measure, the addition “application” can be removed from paragraphs 3.5.2.1 to 3.5.2.3.2.1
9.2In addition, METAR messages refer to aerodrome routine meteorological reports rather than aviation routine weather reports. It should here also noted that METAR is a sub-set of VOLMET (VOLMET also includes SPECI, TAF, SIGMET and AIRMET. It should be considered if, for the provision of meteorological information for aircraft in flight reference to VOLMET is more appropriate than reference to (only) METAR.
9.3The following amendments are proposed to section 3.5.2:
3.5.2 Air-ground applications
3.5.2.1 AUTOMATIC DEPENDENT SURVEILLANCE (ADS)-C APPLICATION
3.5.2.1.1 The ATN shall be capable of supporting ADS-C applications as contained in (include reference to the manual on data link applications from OPLINKP:
3.5.2.2CONTROLLER-PILOT DATA LINK COMMUNICATIONS (CPDLC) APPLICATION
3.5.2.2.1 The ATN shall be capable of supporting CPDLC applications as contained in (include reference to the manual on data link applications from OPLINKP)
3.5.2.3 FLIGHT INFORMATION SERVICE (FIS) APPLICATIONS
3.5.2.3.1 AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS) APPLICATION
3.5.2.3.1.1 The ATN shall be capable of supporting ATIS applications as contained in Doc. … functions:
3.5.2.3.2 AVIATION ROUTINE WEATHER REPORT SERVICE (METAR) APPLICATION VOLMET (meteorological information for aircraft in flight)
3.5.2.3.2.1 The ATN shall be capable of supporting Data link-VOLMET the METAR applications for aircraft-initiated FIS demand contracts.
9.4Alternatively, this section could read:
3.5.2 Air-ground applications
3.5.2.1 The ATN shall be capable of supporting
ADS-C (Re. Manual on data link applications)
CPDLC (Re. Manual on data link applications)
(FIS)
ATIS (Re. Manual on data link applications)
VOLMET (meteorological information for aircraft in flight)(Re. ANNEX 3)
3.5.2.3.2.1 The ATN shall be capable of supporting Data link-VOLMET for aircraft-initiated contracts.
10Section 3.5.3 Ground-ground applications
Similarly to the proposed changes to section 3.5.2 above, section 3.5.3 should be amended as below. Again, it is noted that under the heading “inter-centre communications, only AIDC is identified. In case not more ground-ground applications are to be incorporated here, this heading can be removed.
3.5.3 Ground-ground applications
3.5.3.1 INTER-CENTRE COMMUNICATIONS (ICC)
3.5.3.1.1 ATS INTERFACILITY DATA COMMUNICATION (AIDC)
3.5.3.1.1.1 The ATN shall be capable of supporting the AIDC applications as contained in Doc. [xxx] :
3.5.3.2 ATS MESSAGE HANDLING SERVICES (ATSMHS) APPLICATION
3.5.3.2.1 The ATN shall be capable of supporting the ATS message handling service application (ATSMHS). (MOD-ACP-WGW-01)
or alternatively:
3.5.3 Ground-ground applications
The ATN shall be capable of supporting the following applications: