International Civil Aviation Organization

ATN/AMHS IMPLEMENTATIONIN

ASIA/PACIFIC REGION

Sujan Kumar SaraswatiICAO Asia Pacific Office, Bangkok

SP/1

2AMHS/SWIM SEMINAR

STRUCTURE• Strategy• Structure• Status• Technical Specifications• Address Management• Handling OPMET & AIS/AIM messages• Directory Service• Voice over Internet Protocol (VoIP)• Conclusion

COMMUNICATIONGROUND-TO-GROUND

• Strategy adopted by APANPIRG/17 – August 2006– ATN to be implemented in compliance with ICAO requirements– Initially support ATS Message Handling System (AMHS) to replace

AFTN– Deploy Backbone ATN routers to provide reliable infrastructure to

eventually support air-ground applications– Reasonable timeframe be established to replace AFTN with AMHS– Message Transfer Agent sites to provide AFTN/AMHS gateways– States to cooperate with each other in the implementation– States to organize training – After successful deployment of ground-to-ground ATN, should

introduce air-to-ground– Deploy dual stack protocols (OSI/IPS)

ATN OVER OSI AND ATN OVER IPS

• Conclusion 19/20 – Adoption of ATN over IPS in addition to ATN over OSI

That, considering the inclusion of ATN over IPS SARPs in ICAO Annex 10, Volume 3 and to support global harmonization of ATN implementation, States hosting BBIS be urged to implement ATN over IPS in addition to ATN over OSI and complete this implementation of Dual Stack ATN (ATN/OSI and ATN/IPS) by 2011.

DUAL STACK

• Dual Stack at the MTA level• Dual Stack at the sub-net level• Dual stack at IP level: - Address allocation- IPv4 vs. IPv6

TP4

CLNP

AMHS MTA

ISO/OSI AMHS Message

IP Based AMHS Message

ATNRouter

MTA

MTA

MTA

ATNRouter

ATNRouter

IPRouter

IPRouterIP

RFC 1006TCP

ASIA/PAC REGIONAL ROUTER PLAN

JP

HK

TH

IN SG AU

US

FJ

KP

NP PK

MM

BT

KH

BD

MV

LK

MN

MO

LA

MY

PHVN

BN

TW

KR

AS

TL NRPG

ID

VU SB

MH

FM

PW

NU

NZ

TOWS PF CK

KI NC TV WF

ATN Backbone Site ATN Site

Plan ATN Backbone

Plan ATN Link

NewZealand

Operational ATN Backbone

Operational ATN Link

United State of AmericaJapan

Hong Kong,China

Palau

Micronesia, Federal State of

Marshall Island

American Samoa

FijiAustralia

Papua New Guinea

TimorLeste

Mongolia

DPR Korea

Cambodia

Wallis and Futuna Islands

Tuvalu NewCaledonia

CookIslands

Kiribati

French Polynesia

Niue

Nauru

Tonga

SolomonIslands

Samoa

Vanuatu

Sri Lanka

Indonesia

Singapore

Myanmar

PakistanNepal

Bhutan

India

China

Bangladesh

Thailand

Maldives Island

Malaysia Brunei Darussalam

Russian Federation

Lao

Vietnam

Macau China

Philippines Taiwan

CN

INTER-REGIONAL CONNECTIVITY

Inter-Regional Trunk ConnectionNew Inter-Regional Trunk ConnectionIntra-Regional Trunk ConnectionNew Intra-Regional Trunk Connection

NAM Region

EUR Region

MID Region

AFI Region

APAC Region

AU

CN JP

IN

TH

SG

HK

US is North America Backbone

FJ

JapanChina

Hong Kong,China

ThailandFiji

India

Singapore

Australia

North America

Europe

Middle East

Africa

8AMHS/SWIM SEMINAR

AMHS IMPLEMENTATION STATUSADMINISTRATION LOCATION TARGET DATE REMARKS

Australia Brisbane 2006 Implemented

China Beijing 2010 Implemented

Hong Kong China Hong Kong 2009 Implemented

Fiji Nadi 2010 Implemented

India Mumbai 2010 Implemented

Japan Fukuoka 2006 ISO/OSI

Singapore Singapore 2010 Implemented

Thailand Bangkok 2012

USA Salt Lake City 2006 Implemented

9AMHS/SWIM SEMINAR

TECHNICAL SPECFICATIONS• ATNICG/6 recognized that Asia/Pacific requirements for

ATN/AMHS developed at different times in several manuals based on different versions of Doc 9705 and EUROCONTROL AMHS Manual.

• Creates an Ad-hoc group to develop a baseline document. • APANPIRG adopts AMHS Technical Specifications– Draft Conclusion 22/18 – Asia/Pacific AMHS Technical

SpecificationsThat, the Asia/Pacific AMHS Technical Specifications provided in the Appendix E to the Report on Agenda Item 3.4 be adopted.

10Project title (Insert, Header & Footer)

AMHS REGISTER

• ICAO established AMHS Management Domains and Addressing Information Register available on web link http://legacy.icao.int/anb/panels/acp/amhs/AMHSRegisterList.cfm

• States urged to review information provided in respect of their administrations and get it corrected in case it is not correct.

11Project title (Insert, Header & Footer)

EUROCONTROL AMC

• ICAO in cooperation with EUROCONTROL establishes procedures for coordination and synchronization of AMHS addresses on short/medium term

• States invited to designate representatives to register as AMC users using procedures described

• For long term, true global method of AMHS address management required.

• States shall support CAAS addressing scheme and BBIS States shall support both CAAS and XF addressing scheme (Strategy)

12Project title (Insert, Header & Footer)

HANDLING OPMET MESSAGES

• ICAO supports XML for OPMET messages • Milestones reported to CNS/MET SG/14• AFTN limitations to handle XML messages

– Some States not implemented full IA-5 character set– Limitation line length 69 characters– Limitations message length 1800 characters.

• AFTN and AMHS expected to co-exist for considerable period of time.

• Regional OPMET Data Banks RODB to accept either AFTN or AMHS, so AFTN/AMHS Gateway required to be implemented.

13AMHS/SWIM SEMINAR

AMHS GATEWAY – OPMET MESSAGES

• Convert non-Annex 10 ITA2 characters to “?” before passing to AFTN

• Part messages of more than 1800 characters

• Convert IA5 IRV characters, if in lower case, into equivalent upper case characters

• Wrap lines if longer than 69 characters

14Project title (Insert, Header & Footer)

XML FOR AIM

• Elements of specifications for Digital NOTAM to be included in Amendment 38, Annex 15

• Amendment 38, Annex 15– Substantive chapter on digital services; and– Incorporation of requirement to enable digital data

exchange (AICM/AIXM)• Digital NOTAM encoded in AIXM 5.1 is 20 times larger

than equivalent Text NOTAM• Exchange of some static messaging requirement like

AIRAC cycle amendments may be challenging

15Project title (Insert, Header & Footer)

DIRECTORY SERVICEReference ATNICG WG/8 – WP/6 & WP/10 – 28/09/2010

In support of ATN Directory Servicea) can be used to distribute, update and synchronize address translation data between ATN

& AMHSb) allows lookup and browsing of ATC object entries by operational and administrative

staffc) can support Public Key Infrastructure (PKI) for digital signatures for AMHS and other

applicationsd) will provide more efficient & timely management of the data required to operate the

AMHS & AFTN gateways

Reasons for not using Directory Servicea) only a few ANSPs are using AMHSb) those that are using want to gain more experience before committing to deploy the

Directory Service – recognizing the associated difficulties

16Project title (Insert, Header & Footer)

DIRECTORY SERVICE

• X.500 based Directory Service specified in Doc 9880 Part IV Technical Specifications

• Distributed Global System• Commercial Off the Shelf (COTS) product • Main Directory Service Requirements– Resolve names between ATN & AMHS– Manage distribution list– Publish user attributes capabilities– Support AMHS security

17AMHS/SWIM SEMINAR

VOICE OVER INTERNET PROTOCOL

• VoIP to transmit audio data (especially voice) via IP packets.

• EUROCAE/67 created to examine use of VoIP in Air Traffic Management environment.

• Benefits for ground-ground communication– Technical benefits: single network – Cost reduction: single network for voice & data– Flexibility: IP solution

• Main issues to be addressed– Safety of operations– Continuity

• Release of documents in Feb 2009• Transition issues

18AMHS/SWIM SEMINAR

VOICE OVER INTERNET PROTOCOL

• Voice networks normally are Connection Oriented, whereas data networks are mainly Connection-less.

• Benefits– Network availability– Continuity/contingency

• Issues with IP– Data corruption– Sequence of receipt of datagrams– Loss or destruction of datagrams– Safety critical & administrative communication

19AMHS/SWIM SEMINAR

CONCLUSION

• Dual Stack BBIS in place to meet APANPIRG Conclusion 19/20 timeline

• AFTN and AMHS to coexist for considerable period of time

• Many options coexisting • For AMHS to be really acceptable, applications

need to developed • Transition to SWIM

AMHS/SWIM SEMINAR 20

THANK YOU