The Copperchase AMHSGATE is a high performance multi-protocol message gateway that conforms to the ICAO ATN SARPs for ATSMHS applications, and more specifically on the AFTN/AMHS Gateway specified in these SARPs. Based on the industry standard Microsoft Exchange 2000 Server and X.400 MTA, the AMHSGATE combines the AFTN expertise of Copperchase with the OSI communications services of industry leaders Bolden James. The total AMHSGATE solution paves a way for a seamless transition from today’s ATC Messaging Service of the AFTN to the exciting world of the Air Traffic Services Message Handling Service (AMHS - X.400).

Key Features:

• High reliability for mission critical operation
• Highly scaleable architecture and performance
• Convert AFTN message formats to AMHS message formats and vice versa
• API allows the submission and reception of AFTN messages for 3rd party applications
• Supports X.400 (92,88,84) messaging for maximum interoperability
• Available on Windows Exchange 2000 Server

Comprehensive Management Tools
The AMHSGATE provides comprehensive tools to support the system administrator. Management features include the ability to re-route messages, time schedule message channels for cost and message flow control. Comprehensive logging is provided for audit and message tracking.

Integration
The power and flexibility in the Copperchase AMHSGATE is provided by the Microsoft Exchange 2000 Server combined with the X.400 MTA. By utilising the Microsoft Exchange Server as the basis for the AMHSGATE solution, Copperchase has created a generic and total COTS messaging solution that even surpasses the initial requirement for the EUROCONTROL EATCHIP Enhanced Communications Gateway (ECG). The AMHSGATE has been designed to facilitate the smooth transition from existing communications and networks towards the ATN.

This is an Industry product that allows States to purchase an ATN-compliant communication system as an off-the-shelf commercial product.

Allows a phased evolution from a variety of initial situations towards enhanced harmonised ATM Communications using the ATN. This is achieved using the Microsoft Exchange Servers ability to integrate various formats/protocols via gateway facilities to communicate with a common message switch interfacing with the relevant ATN applications.

Scalability and modularity for ease of implementation and suitability.

A proprietary file-based API for 3rd party applications.

Uses Directory Services for dynamic distribution lists, and routing.


The AMHSGATE comprises of 5 major components:

• MS Exchange 2000 server – COTS MS product
•  MS Exchange x.400 MTA server - COTS MS product
• OSI TP4/CLNS transport stack – COTS Bolden James product
• Exchange ATN Gateway module

Copperchase (or other) AFTN gateway module

The AFTN system produces output and accepts input in the form of [disk] files (via ATN ‘input/output’ folders). The format of the data in these files is presented in XML format. The Schema for the AFTN XML data is available to 3rd Parties. 

The AFTN gateway module has two inputs: 

•  Outbound (from the ATN) - the AFTN gateway system monitors the ‘ATN Output’ folder so that it can process new messages [files] as they arrive.
• Inbound (to the ATN) where it needs to monitor the AFTN network interface.
  

Exchange ATN Gateway module
The Exchange ATN Gateway monitors the ATN ‘Input folder’ and gateway ‘inbox’ for new message input. 

On inbound (to the ATN) the AFTN system receives AFTN messages and translates them into XML data files, which are queued in the ’Input Folder’, the Exchange Gateway opens these files and converts the data into an Exchange Gateway message format which it places in its ‘outbox’. This ‘message’ is a set of MAPI properties which the Exchange 2000 Server will encode into an X.400 message and route to the X.400 ATN network.

On outbound (from the ATN), the Exchange Gateway converts the received message (which will be in MAPI format) into XML data and writes it to a file in the ATN Output folder. The AFTN system will be monitoring this folder and will pickup the new file and process it.

MS Exchange 2000 (x.400) server 
Messages received by the Exchange MTA destined for the AFTN network are routed to the ATN Gateway’s Inbox. This routing ability is intrinsic to the Exchange 2000 Server. Vice versa messages to the ATN are routed using the standard Exchange server routing features. P1 Exchange x.400 connectors are configured for all the bi-lateral agreements held by the particular messaging domain.

Address mapping - The ATN Gateway will translate the AFTN addresses to X.400 addresses and vice-versa, as defined by the XF, MF-address formats. This is done by reference to a Directory (LDAP) Service (not shown).