AsiaPacific AMHS Implementation Workshop
AsiaPacific AMHS Implementation Workshop
AsiaPacific AMHS Implementation Workshop
Objective
Aeronautical Telecommunications Network (ATN)
Air Traffic Service Message Handling System (AMHS) Open System Interconnection(OSI)/ Internet Protocol Suite(IPS)/ Open System Interconnection(OSI) over TCP/IP
Implementation Documents
ICAO 9896 Flight plan/clearance
ICAO 9880
ATN SARP 9705
OSI
ATN
BBIS
UA AFTN Gateway TCP/IP
MTA
What do I need to do ?
Federal Aviation Administration
ATN is designed by Aeronautical Communication Panel (ACP) as a seamless network to distribute Air Traffic Control (ATC) message among ICAO members including Air to Ground (A/G) messages
ATN based on OSI (ATN/OSI) as specified in ICAO Doc. 9705 was completed in 2003 (ed. 3) by ATN Panel ATN based on Internet Protocol Suite (ATN/IPS) as specified in ICAO Doc. 9896 (expected publication January 2009) ATN/OSI that use TCP/IP network is developed by ACP
in 2008 for OSI based applications as specified in ICAO Doc. 9880
AMHS
AMHS component includes:
ATS message server ATS message user agent (UA) AFTN/AMHS Gateway
Extended Service is a superset of Basic Service, support more complex message structures (body parts), use of the directory service, and support security
AMHS
AFTN/AMHS Gateway
AFTN component ATN component
AFTN
MTA
MS
MTCU
MTA (Message Transfer Agent) UA Send out/Receive ATN Message MS (Message Store) AFTN (Aeronautical Fixed Telecommunication Network) MTCU (Message Transfer and Control Unit) provides interface between the ATN and AFTN components. UA (User Agent) provide interface for user sends or gets mail
AMHS Terminals
UA
MS MTA
MTCU MTA
MS
UA
UA
AFTN Switch
UA
MS
MTCU MTA
UA
MTA MS
UA
UA
UA
AMHS Terminals
UAw DUA
MTA w DUA
UAw DUA
UAw
MTA w DUA
DUA
UAw DUA
UAw DUA
X-500 DIRECTORY
DBA DBA
DBA
10
Routing Encoding Decoding Sending/Receiving Store and retrieve received messages Long-term logging of all messages passing through MTA and store at least 30 days
11
2. Priority
3. Content type 4. Originator name 5. Recipient name 6. Message content size
8. Arrival/submission time
9. Transfer destination and time 10. Recipient name 11. Delivery time 12. Delivery and non delivery reports
12
13
AFTN/AMHS Gateway
AFTN/AMHS gateway is to convert AFTN messages to AMHS messages or via versa, the gateway includes four logical components
AFTN component ATN component Message Transfer and Control Unit (MTCU) Control Position (PC)
14
AFTN/AMHS Gateway
AFTN Component
Provide interface with AFTN and MTCU Handle AFTN message format using ITA-2 (International Telegraph Alphabet No 2), the AFTN component shall convert message to/from IA-5 (International Alphabet 5) format
ATN Component
Provide interface with AMHS and MTCU Ensure all AMHS information passing MTCU complied with base standard of ATS Message Server
15
AFTN/AMHS Gateway
Message Transfer and Control Unit (MTCU)
Provide bi-directional conversion facility between the AFTN component and ATN component Using IA-5 character internally
16
The BBIS MTA can utilize TCP/IP network by using RFC 1006 for UA interface or other MTA (non BBIS)
17
ATN/OSI (AMHS)
These BBIS would implement AMHS with ATN Router
Intra Region
AMHS
AMHS
ATN
Router
ATN
Router
ATN
Router
BOUNDARY AMHS
ATN
Router
ATN
Router
AMHS
AMHS
19
Host
X.25 X.25 NADIN PSN X.25 NADIN MSN AFTN
MTA
AFTN Gateway
LAN TCP/IP/CLNP
Network Management
ES-IS
Duplex ATN Router
64 Kbps IDRP
ATN Network
20
IPv4
To IPS Regions
21
ATN REGION
AMHS
AMHS
AMHS
IP Router
IP Router
ATN Router
ATN
Router
ATN
Router
IP Router IP Router
IP Router
IP Router
BOUNDARY AMHS
BOUNDARY AMHS
ATN Router
ATN Router
AMHS
AMHS
AMHS
AMHS
22
AMHS MTA
TP4
IP Router
MTA
ATN Router
ATN Router
CLNP
SARP Compliance AMHS Message
ATN SARP compliant MTA and Router states can exchange traffic from their MTA to any MTA IP based MTA and Router will require its traffic to be forwarded by ATN SARP compliant MTA Discussion: - Address allocation - IPv4 vs. IPv6 - Documentation
23
AMHS/ATN Operation
AMHS will use AFTN/ATN Gateway to ensure the message will continue to be compatible with automation equipment
AFTN/AMHS Gateway will continue to process AFTN based messages direct from other AFTN switches UA will interface directly with MTA and AFTN/AMHS GW will convert to AFTN message format as required During transition period, all AMHS messages will be processed and routed by associated MTAs
24
UA Operation
UA is a PC based with COTS Web browser (Internet Explorer, Firefox, etc)
IPv4 is recommended for User Agent (UA) interfaces with MTA UA can connect to its MTA using IPv4 Addressing Scheme via dedicated circuit or Internet (VPN)
25
China
CN JP
Japan
Middle East
MID Region
TH Thailand
SG
Africa
AFI Region
Singapore
IN
India
APAC Region
Inter-Regional Trunk Connection New Inter-Regional Trunk Connection Intra-Regional Trunk Connection New Intra-Regional Trunk Connection
AU
26
Japan
Mongolia
Pakistan
Thailand
Cambodia Malaysia
Brunei Darussalam
American Samoa
Indonesia Bhutan
Bangladesh
India
Sri Lanka
Singapore
Australia
New Zealand Papua New Guinea Timor Leste Vanuatu Solomon Islands Nauru
Fiji
Maldives Island
27
Conclusion
The ATNICG has envisioned that States in the region with AFTN switches should replace them with AMHS The BBIS States should implement AMHS as soon as possible
The BBIS states with interface to other regions that adopt TCP/IP, should establish connection based on bilateral agreement States in the region that have only one connection or AFTN terminal should work with their associated BBIS States to implement UA
ATNICG has recommended that any upgrade to existing AMHS implementation will be considered at the next technical refresh cycle ATNICGs primary task is to ensure smooth transition to AMHS environment while sustaining the AFTN operation
28
29