Regional ATN Transition Planning Presentation ATN 4.2 by H. Tran Varadero, Cuba May 2002

Regional ATN Planning Establish an ATN Regional Task Force The Regional Task Force should develop an ATN Transition Plan for the CAR/SAM Region The Regional Task Force should be tasked to develop various regional ATN implementation related documents

ATN Implementation Related Documents The following ATN Implementation issues need to be addressed by the regional ATN task force: Regional ATN Routing Architecture Plan Regional ATN Addressing Plan Regional ATN AMHS Naming Plan Regional ATN NSAP Addressing Registration Regional AMHS ICD Regional BIS Router ICD Regional CNS FASID Regional ATN Transition Plan Regional ATN Routing Policy (IDRP) Regional Routing Policy (MTA) Regional Directory Services Regional System Management System Performance Security

ATN Transition Plan Recommendation for a Three Stage ATN Transition: Stage 1 - Upgrade Current/Existing Infrastructure Stage 2 - Establishment of a Ground ATN Backbone Router Network Stage 3 - Connectivity of User ATN Routers to the Backbone

Stage 1 - Existing Infrastructure AFTN Infrastructure Based on point to point circuits Majority of Circuits are low speed: 50 baud through to 9600bps Circuit Protocols range from no protocols through to COPB and X.25

Current US/CAR/SAM/Mexico AFTN/VOICE Connections

Current US/MEVA AFTN/VOICE Connections USA Bahamas Cuba Puerto Cayman Rico Islands Jamaica a Haïti Republica Belize Dominican Guatemala Honduras El Salvador Nicaragua Aruba Curaçao Costa Rica Panama Peru

Current US/E-CAR AFTN/VOICE Connections USA Puerto Rico Anguilla St Marteen St Kitts Antigua & Nevis Montserrat Guadeloupe Dominica Martinique St Lucia St Vincent Barbados Grenada Venezuela Trinidad & Guyana Tobago

Current US/REDDIG AFTN/VOICE Connections USA USA Puerto Rico Venezuela Colombia Suriname Trinidad Guyana Guyane Française & Tobago Ecuador Peru Brasil Bolivia Paraguay Chile Argentina Uruguay

Current US/CAMSAT AFTN/VOICE Connections USA Cuba Mexico Cayman Islands Belize Guatemala Honduras El Salvador Nicaragua Costa Rica Panama

Current CAR/SAM Region AFTN Data Speed 75 Bauds 300 Bauds 9.6 Kbps 50 Bauds 2.4 Kbps 150 Bauds 110 Bauds 600 Bauds 1.2 Kbps CAR/SAM/3-WP/18 APPANDIX A

Current Regional Protocols 2% 83B3 85A2 X25 10% None 77% COPB 7% CAR/SAM/3-WP/18 APPANDIX A About 90% None ATN supports protocols

Stage 1 - Upgrade of Circuits ATN at present recommend to use Subnetworks to interface at X.25, Which require existing non-compatible AFTN circuits will need to be upgraded

Stage 1 - Bandwidth Issues Overheads from each layer of the OSI stack will increase total message size as much as 94% (standard AFTN message size using AMHS) Bandwidth for circuits will need to be increased substantially Minimum speed 9.6kbps is required for ATN AMHS application Recommend 64kbps or higher will need to be considered for the regional ATN backbone

ATN Applications AMHS AMHS AIDC AIDC ADS CPDLC Site B ATN FIS ADS Site A AMHS AIDC ADS CPDLC FIS ATN Site C ADS CPDLC FIS

Stage 2 - ATN Backbone Selection of Locations based on Existing Inter-Regional Connections and Main Internal Connections Diversity for Backbone Connectivity within the CAR/SAM Region and Neighbouring Regions Minimum of 64kbps for Backbone Trunk Speeds

Example ATN Regional Backbone ASIA Region EUR Region B C D E F G H AFI Region I CAR/SAM Region Inter-Regional Trunk Connection Intra-Regional Trunk Connection

Example CAR/SAM ATN Routing B F D H TO TV WF G2 GJ GG ID AB GK J1 NC WS A4 AC CB PG DF DC BN PH A3 H1 FH F1 D3 D1 A1 A2 G1 I I3 I4 PI I2 ATN Backbone Site ATN Site C E

Stage 3 - ATN Connectivity Generally ATN Routers will connect to the ATN Backbone In some cases ATN Routers will connect to other ATN Routers to get to the ATN Backbone

AFTN to AMHS Transition For the very first time there is now an alternative to the replacement of an AFTN system - AMHS Transition to AMHS can involve a number of steps Introduction of AFTN/AMHS Gateways. To full AMHS Interconnection between States.

Current AFTN Environment Site A Site B AFTN System X.25 Low Speed Site C Low Speed AFTN System AFTN System X.25 X.25 Site D AFTN System

Implementation of AFTN/AMHS Gateways Site A AMHS Gateway ATN Router ATN Router AMHS Gateway AFTN System X.25 Site B Low Speed Site C AFTN System Low Speed AFTN System X.25 X.25 Site D AFTN System

Migration to AMHS - 1 Site B ATN Site C X.25 X.25 Site D Site A Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B ATN Domestic Network ATN Router AMHS Gateway AFTN System Site C AMHS System ATN Router X.25 AMHS Gateway X.25 Site D AFTN System

Migration to AMHS - 2 Site B ATN Site C Site D Site A Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B Domestic Network ATN ATN Router AMHS System Site C AMHS System ATN Router ATN Router AMHS Gateway AFTN System Site D

Full AMHS Implementation Site A Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B Domestic Network ATN ATN Router AMHS System Site C AMHS System ATN Router ATN Router AMHS System Site D

Current ATN Trials Infrastructure In Europe The development of the early ATN Infrastructure (ATIF) in Europe has come to a point where experimental ICAO SARPS (as published in ICAO document 9705) compliant ATN system elements are available and widely deployed. Complementary ATN components like the Trials End System (TES), the Trials ATN Router and Transport Server (TAR-TTS), and the Mode S and AMSS ATN subnetworks have been integrated into a distributed European ATN Trials Infrastructure which is being extended to other regions (e.g. the U.S., Japan and Australia)

ATN Asia Regional Backbone Plan AU CN JP IN TH SG HK EUR Region NAM Region MID Region AFI Region Inter-Regional Trunk Connection New Inter-Regional Trunk Connection Intra-Regional Trunk Connection New Intra-Regional Trunk Connection Asia Region

Asia/Pacific ATN Routing Plan AU CN JP IN TH SG TO TV WF PF FJ NZ ID KR NR CK KI NC WS NP MO TW VU PG SB BD VN BN PH MM MV LK BT KH LA MY KP MN NU US MH FM PW AS ATN Backbone Site ATN Site HK

ATN G/G Applications AIDC The AIDC will automatically exchange ATC information between ATSU, in support of the ATC functions : NOTIFICATION of flights approaching an FIR boundary, CO-ORDINATION of boundary crossing conditions, TRANSFER of control at the FIR boundary.

AIDC Overview Aircraft Flight ATN AIDC BIS ES ES Legend AIDC ATS Inter-facility Data Communication BIS Boundary Router ES End System FIR Flight Information Region AIDC AIDC ES BIS BIS ES AIDC Flight notification, coordination, and transfer between FIRs

AIDC Implementation ATN AIDC is not Compatible with AIDC over AFTN Implementation of ATN AIDC will need to be implemented by arrangement between both parties Possible phased implementation can be AIDC over AFTN to AIDC over AMHS

AIDC Over AMHS Site A Site B ATN AIDC End System AIDC End System Domestic Network Domestic Network ATN AMHS System ATN Router ATN Router AMHS System

Conclusions ATN is a policy agreed among ICAO member states Implement new links or Upgrade existing AFTN links where appropriate to be compatible with ATN protocols Plan for adequate bandwidth which can be increased without restriction Each Region needs to developed its own implementation plan and related documents to address its own regional environment Interim arrangements can be set up between States/Organizations which can provide ATN service or gateway