Regional ATN Transition Planning
Varadero, Cuba
May 2002
Presentation ATN 4.2 by H. Tran
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 InfrastructureBased on point to point circuitsMajority of Circuits are low speed: 50 baud
through to 9600bpsCircuit Protocols range from no protocols
through to COPB and X.25
Current US/CAR/SAM/Mexico AFTN/VOICE Connections
In order to easily grasp the network inits entirety part of the map have been
distorded. Countries are notrepresented to scale.
Aruba
VenezuelaColombia
Ecuador
Peru
Bolivia
Chile
Paraguay
UruguayArgentina
Brasil
GuyaneFrançaise
SurinameGuyana
Belize
Guatemala
El Salvador
Honduras
Costa Rica
Panama
Nicaragua
USA
Bahamas
Cuba
CaymanIslands
Jamaica
HaïtiRepublicaDominican
aPuertoRico
Trinidad&
Tobago
Curaçao
REDDIG
Connection between Networks
CAMSAT
E-CAR
MEVA
IS Router
BIS Router
St Marteen
St Vincent
Guadeloupe
St Lucia
St Kitts& Nevis
Dominica
Martinique
Antigua
Anguilla
Montserrat
Grenada
Barbados
US
Aruba
Belize
Guatemala
El Salvador
Honduras
Costa Rica
Panama
Nicaragua
USA
Bahamas
Cuba
CaymanIslands Jamaica
Haïti Republica
Dominican
a
Puerto
Rico
Curaçao
Peru
Current US/MEVA AFTN/VOICE Connections
Current US/MEVA AFTN/VOICE Connections
Venezuela
Guyana
PuertoRico
Trinidad&
Tobago
St Marteen
St Vincent
Guadeloupe
St Lucia
St Kitts& Nevis
Dominica
Martinique
Antigua
Anguilla
Montserrat
Grenada
Barbados
USA
Current US/E-CAR AFTN/VOICE Connections
Current US/E-CAR AFTN/VOICE Connections
VenezuelaColombia
Ecuador
Peru
Bolivia
Chile
Paraguay
UruguayArgentina
Brasil
Guyane
Française
SurinameGuyana
Trinidad
&Tobago
USAPuertoRico
USA
Current US/REDDIG AFTN/VOICE Connections
Current US/REDDIG AFTN/VOICE Connections
Belize
Guatemala
El Salvador
Honduras
Costa Rica
Panama
Nicaragua
USA
Cuba
Cayman
Islands
Mexico
Current US/CAMSAT AFTN/VOICE Connections
Current US/CAMSAT AFTN/VOICE Connections
Current CAR/SAM Region AFTN Data Speed
13%
35%
2%5%
20%
2%
1%
8%14%
75 Bauds300 Bauds
9.6 Kbps 50 Bauds2.4 Kbps
150 Bauds 110 Bauds
600 Bauds
1.2 Kbps
CAR/SAM/3-WP/18APPANDIX A
2%
83B32%
85A22%
X2510%
None77%
COPB7%
Current Regional ProtocolsCurrent Regional Protocols
About 90% None ATN supports protocolsCAR/SAM/3-WP/18APPANDIX A
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
Site A
AMHS
AIDC
ADS
CPDLC
FIS
Site C
ADS
CPDLC
FIS
Site B
AMHS
AIDC
ATN Applications
ATN
Stage 2 - ATN Backbone
Selection of Locations based on Existing Inter-Regional Connections and Main Internal ConnectionsDiversity for Backbone Connectivity within the CAR/SAM Region and Neighbouring RegionsMinimum of 64kbps for Backbone Trunk Speeds
Inter-Regional Trunk ConnectionIntra-Regional Trunk Connection
EUR RegionASIA Region
AFI Region
CAR/SAM Region
Example ATN Regional Backbone
I
A
C
G
D
F
B
H
E
Example CAR/SAM ATN Routing
G
A B
F
D
H
TO TV WFG2
GJGG
ID
AB
GK J1 NC WS
A4
AC
CB
PG
DF
DC
BN
PH
A3
H1
FHF1
D3
D1
D3
A1 A2
G1
I
I3 I4 PII2
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 C
Site D
Site B
Site A
AFTNSystem
X.25X.25
X.25
Low Speed
Low Speed
AFTNSystem
AFTNSystem
AFTNSystem
Site A
AMHSGateway
ATNRouter
ATNRouter
AMHSGateway
Implementation of AFTN/AMHS Gateways
Site BAFTN
System
AFTNSystem
X.25
Site DAFTN
System
Site CAFTN
System
X.25X.25
Low Speed
Low Speed
Site A
AMHSSystem
ATNRouter
AMHSGateway
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
Migration to AMHS - 1
Site CAFTN
System
Site DAFTN
System
X.25
X.25
ATNRouter
AMHSGateway
ATN
Site BATN
RouterAMHS
System
Migration to AMHS - 2
Site CATN
RouterAMHS
System
Site BATN
RouterAMHS
System
Site A
AMHSSystem
ATNRouter
ATN
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
Site DAFTN
SystemATN
RouterAMHS
Gateway
Full AMHS Implementation
Site DATN
RouterAMHS
System
Site CATN
RouterAMHS
System
Site BATN
RouterAMHS
System
Site A
AMHSSystem
ATNRouter
ATN
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
Current ATN Trials Infrastructure In Europe
Inter-Regional Trunk ConnectionNew Inter-Regional Trunk ConnectionIntra-Regional Trunk ConnectionNew Intra-Regional Trunk Connection
ATN Asia Regional Backbone Plan
NAM Region
EUR Region
MID Region
AFI Region
Asia Region
AU
CN JP
IN
TH
SG
HK
Asia/Pacific ATN Routing PlanAsia/Pacific ATN Routing Plan
AU
CN JP
IN
TH
SG
TO TV WFPF
FJNZ
ID
KR
NR
CK KI NC WS
NP
MO
TW
VUPG SBBD
VN
BNPH
MM
MV
LKBT
KH
LAMY
KP MN
NU
US
MH FM PWAS
ATN Backbone Site
ATN Site
HK
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 OverviewAIDC Overview
BISAIDC
BISES ES
Aircraft Flight
AIDC Flight notification, coordination, and transfer between FIRs
LegendAIDC ATS Inter-facility Data CommunicationBIS Boundary RouterES End SystemFIR Flight Information Region
ATN
BIS AIDCES
ES
AIDC
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
ATN
Site A
AMHSSystem
ATNRouter
Domestic Network
AIDCEnd
System
Site B
ATNRouter
AMHSSystem
Domestic Network
AIDCEnd
System
Conclusions
ATN is a policy agreed among ICAO member statesImplement new links or Upgrade existing AFTN links where appropriate to be compatible with ATN protocolsPlan for adequate bandwidth which can be increased without restrictionEach Region needs to developed its own implementation plan and related documents to address its own regional environmentInterim arrangements can be set up between States/Organizations which can provide ATN service or gateway