340 likes | 682 Views
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
E N D
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/MEVA AFTN/VOICE Connections USA Bahamas Cuba Puerto Cayman Rico Jamaica Islands a Haïti Republica Dominican Belize 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 Suriname Trinidad Colombia Guyana Guyane Française & Tobago Ecuador Peru Brasil Bolivia Paraguay Chile Uruguay Argentina
Current US/CAMSAT AFTN/VOICE Connections USA Cuba Mexico Cayman Islands Belize Guatemala Honduras El Salvador Nicaragua Costa Rica Panama
2.4 Kbps 9.6 Kbps 50 Bauds 1.2 Kbps 600 Bauds 75 Bauds 300 Bauds 110 Bauds 150 Bauds Current CAR/SAM Region AFTN Data Speed CAR/SAM/3-WP/18 APPANDIX A
2% 83B3 2% 85A2 2% COPB X25 7% 10% None 77% Current Regional Protocols 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
AMHS AMHS AIDC ADS CPDLC FIS AIDC ATN ADS CPDLC FIS Site B Site A Site C ATN Applications
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 A 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
A B AB A1 A2 AC C I A3 CB DC A4 D D1 D3 I2 I3 I4 PI E D3 PG G FH F1 PH DF ID F H BN GJ GG H1 ATN Backbone Site G1 G2 GK J1 NC WS TO TV WF ATN Site Example CAR/SAM ATN Routing
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.
Site C Site D Site B Site A Current AFTN Environment AFTN System X.25 Low Speed Low Speed AFTN System AFTN System X.25 X.25 AFTN System
Site D Site C ATN Router AMHS Gateway X.25 AMHS Gateway ATN Router AFTN System AFTN System Site A Implementation of AFTN/AMHS Gateways AFTN System Site B Low Speed Low Speed AFTN System X.25 X.25
ATN Site D Site A Migration to AMHS - 1 Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B Domestic Network ATN Router AMHS Gateway AFTN System Site C AMHS System ATN Router X.25 AMHS Gateway X.25 AFTN System
ATN Site A Migration to AMHS - 2 Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B Domestic Network ATN Router AMHS System Site C AMHS System ATN Router ATN Router AMHS Gateway AFTN System Site D
ATN Site A Full AMHS Implementation Domestic AMHS Systems Domestic AMHS Terminals ATN Router AMHS System Site B Domestic Network ATN Router AMHS System Site C AMHS System ATN Router ATN Router AMHS System Site D
CN JP HK TH SG IN AU Inter-Regional Trunk Connection New Inter-Regional Trunk ConnectionIntra-Regional Trunk Connection New Intra-Regional Trunk Connection ATN Asia Regional Backbone Plan EUR Region NAM Region MID Region AFI Region Asia Region
CN JP KR KP MN MO HK US MM TW VN NP TH LA MY AS MH FM PW KH BT LK PH BN ID NR PG SB VU BD MV IN SG AU NZ FJ ATN Backbone Site NU PF CK KI NC WS TO TV WF ATN Site Asia/Pacific ATN Routing Plan
ATN G/G ApplicationsAIDC • 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
ATN Site A Site B AIDC Over AMHS AIDC End System AIDC End System Domestic Network Domestic Network 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