AMC
|
EUROCONTROL was requested by ICAO EUR/NAT Air Navigation Planning Group (EANPG) to develop and operate centralised off-line management functions to support the Common ICAO Data Interchange Network. For that purpose, Pulsar has developed in 2001 the CIDIN application, allowing operators to design and plan their communication network. Such a network was using CIDIN or AFTN protocols. After several years of successful operation, CIDIN needed to be extended in order to support the new ATS Message Handling System (AMHS) protocol. This need for AMHS off-line management functions gave birth to the AMC (ATS Messaging Management Centre) application. Project ScopeAMC is a Web application designed for managing an aeronautical off-line communication network in a collaborative way. It allows describing COM centres’ characteristics and planning changes. Operators can define connections and routings between COM centres using 3 distinct protocols. The application helps checking the consistency of the network and finding other paths in case of failure. An interactive map is used to represent the so-defined network. Different kinds of reports are also available. |
The AMC application was built using Pulsar’s framework called GidPro (J2EE, JSP, Struts, XML/XSL, Web Services, HTML, CSS, Javascript) and the following technologies:
|
|
Main ConceptsNetwork Protocols
|
|
Organizations
|
|
|
Functions |
AMF-I: AMHS off-line Management Functions - Implementation support
The main purpose of AMF-I functions is to provide support to states that are in the process of implementing AMHS, and do not yet have AMHS in operational use. However, they may also be used by States that have already started operational use of AMHS, e.g. to plan future evolution of their AMHS systems.
|
AMF-O: AMHS off-line Management Functions – Operations
|
|
AMC Network
Network inventory: describes all the physical elements allowing to route a message. Routing Directory: indicates only 1 communication route at once, step by step (hop after hop).
|
| Matrix There is only 1 network inventory but routing requires simulation. So, matrices are kinds of scenario for the whole routing. We can copy matrices. We can roll-back to previous matrix. For transfer to pre-operational, the matrix is locked and copied. There is no algorithm of partial transfer, so all matrices contain the whole routing, for consitency purposes. |
Connections
|
| VCG’s Physical connections take place inside channels of virtual circuits. When creating a connection, the required VCG is created if not yet existing.
A maximum of 6 VCG can be created between 2 COM centres, one for each combination of:
But the screen allows managing only CIDIN VCG’s, the VCGs for AFTN & AMHS are managed automatically by the application for technical reasons.
|
| Main vs. Alternate Routing Routing can define several paths for each hop:
|
Existing vs. Planned Routing Routing can define several paths for each hop:
|
|
|
|
COM Chart
Fully meshed island The fully-meshed topology of the target AMHS network will lead to a very high number of AMHS connections. The individual representation of all these connections would lead to an extremely unclear, not legible, diagram. Hence the need for a specific representation of a fully-meshed AMHS island. |
AMHS connections are different because a variety of underlying networks can be used, including shared accesses connectionless IP networks. In this technical environment, there is not a constant binary capacity or throughput identified for each AMHS connection. The representation of AMHS connections in the COM Chart is therefore limited to logical aspects, i.e. to the existence of an AMHS association between two COM Centres. Each COM Centre must be associated to one or several COM Charts in the Network Inventory screen in order to be displayed in these charts.
|
|
Areas An area is a logical unity for manipulation of data. The use of different areas allows people to work in a secure way on his/her data by acknowledging their correctness. There are 3 areas: the background area, the pre-operational area and the operational area.
Edition is done by Com Center Operators (CCC) only in background area. The general purpose of the Pre-Operational Data Area is to display to Network Managers (CMC) data regarding all COM Centres, before these data become live at the end of the cycle when they are transferred to the Operational area. In order to show changes, information is shown in red colour in the Pre-operational Area if the information is different from the corresponding information currently in the Operational Area. The general purpose of the Operational Data Area is to display operational data for the current cycle. to everybody involved in Network Management accross Europe. AMHS MD Register (Management Domain)
Path Function
It also allows searching for another path by simulating a situation where a COM center is out of service or where a routing between 2 intermediary COM centers fails.
ANP Location
Unofficial Territories are added to the ICAO database by Eurocontrol. In AMC when there exists an official and an unofficial ANP location with the same code the unofficial take the precedence. A special procedure was developed to compare the locations in use in AMC with the updated data of ICAO and to manage the synchronization within AMC.
AMC Regions Persons Routing Inconsistencies Network Planning AIRAC Cycle
Collaboration
Reference Tables These functions enable the AMC Operator to manage:
User Rights
|



















