Upload
ngotram
View
217
Download
0
Embed Size (px)
Citation preview
Asia/Pacific ATN Regional Planning
ATN Seminar Chiang Mai, 11th - 14th December 2001
Presented by Craig Head
ATN Transition Task Force
�The ATN Transition Task Force (ATNTTF) was established by APANPIRG/9 (1998) to address ATN Issues and to deal with residual AFS Issues.
�The ATNTTF reports are reviewed by CNS/MET Sub-Group before being submitted to APANPIRG
�The ATNTTF will schedule its fourth meeting in Mumbai in April 2002.
ATNTTF ATN Responsibilities
�The ATNTTF is Responsible for the Development of:
�ATN Transition Guidance Material�ATN Transition Plan�ATN Interface Control Documents�Technical Information on security, performance and
system management issues�Provide Planning and Implementation Information
in the Air Navigation Plan�Develop the ground ground part of the CNS
Facilities And Services Implementation Document (FASID)
ATNTTF Working Groups
�The ATNTTF Established Two Working Groups:
�Working Group A�Development of ATN technical plans
�Working Group B�Development of an ATN transition plan and other
ATN technical documents
ATNTTF Working Group A
�Established to develop the following Plans:�ATN Routing Architecture Plan�ATN NSAP Addressing Plan�AMHS Naming Plan�ATN NSAP Registration Plan
�WG A Includes Representatives from:�Australia�Japan�Thailand�United States
Status of Plans
�Plans submitted for review at the ATNTTF/3 in March 2001.
�Plans were reviewed at CNS/MET Sub Group/5 in July 2001.
�Plans were approved by APANPIRG/12 in August 2001.
�Plans to be circulated to States for comments.
ATNTTF Working Group B
�Established to develop the ATN Ground-Ground Transition Plan for the Asia/Pacific Region and other technical documents
�WG B Includes Representatives from:�Australia�Fiji�Hong Kong China�Japan�Singapore�Thailand�United States
ATN Technical Documents� ATN Transition Plan� AMHS Interface Control Documents� Router Interface Control Documents� Routing Policy for IDRP� Routing Policy for MTA� Directory Services� System Management� Security� Performance
Status of Documents
�ATN Transition Plan was submitted for review at the ATNTTF/3 in March 2001.
�Other Documents are currently in the development phase.
�ICDs and other critical documents to be presented at the ATNTTF/4 meeting.
ATN Routing Architecture Plan
�The establishment of Backbone Boundary Intermediate Systems (BBIS)
�Describes the role of a BBIS:�Must be very reliable�Capacity - capable of supporting significantly
more traffic�Alternative Routing - have access to multiple
links�Routing Policies - must support Regional
transit traffic and dynamic re-routing of traffic
APAC Region
Australia
China Japan
India
Thailand
Singapore
Hong Kong
Backbone BIS
Fiji
ATN NSAP Addressing Plan
�Development of a Network Service Access Point (NSAP) Address Scheme.
�Provides guidance in assigning values to the 20 byte address fields of the NSAP.
ATN NSAP Address StructureAFI
1 OctetIDI
2 OctetsADM3 Octets
RDF1 Octet
ARS3 Octets
LOC2 Octets
SYS6 Octets
SEL1 Octet
VER1 Octet
AFI - Authority and Format Identifier - defined by SARPS IDI - Initial Domain Identifier - defined by SARPSVER - Version - defined by SARPS and by PlanADM - Administration Identifier - defined by PlanRDF - Routing Domain Format - not used set to zeroARS - Administration Region Selector - defined by PlanLOC - Location - defined by PlanSYS - System Identifier - to be defined by StateSEL - NSAP Selector - defined by SARPS
AMHS Naming Plan
�Aligned with the Global AMHS Naming Convention to be adopted by ICAO
�ATN Panel Working Groups have recommended that the Global AMHS Naming Convention be included in Edition 3 of the ATN Manual
AMHS Name Assignments
�Proposed to use the following name attributes:�Country Name - XX�ADMD - ICAO�PRMD - States to register preferred name with
ICAO�Organisation Name�Unit Name�Common Name (includes the AFTN
Indicator)
AMHS Naming SummaryAttribute Assigned By Value CommentCountry-name(C)
ITU-T XX InternationalOrganization
ADMD (A) ICAO ICAO ICAO Responsibility toregister
PRMD (P) ATSO e.g.THAI
ATSO registered privatedomain with ICAO.
Organizationname (O)
ATSO e.g.AEROTHAI
Local/nationalgeographicalinformation, which canbe based on ICAOLocation Indictors (Doc7910)
Organizational-Unit name (OU1)
ATSO e.g.BB
ICAO LocationIndicator (Doc 7910)
Common Name(CN)
ATSO e.g. VTBBYFYX AFTN indicator address
ATN Transition Plan
�Recommends a Three Stage ATN Transition Phase:�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
Existing AFTN 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
Asia/Pacific AFTN Topology
MalaysiaKota K inabaluWBKK
Brunei
WBSB
Uzebekistan (UTTT)
Bahrain (OBBI)
INTERNATIONAL AFTN - ASIA PACIFIC
Tuvalu
PNGPort Moresby
American Samoa
NSTU
NGTA
French Polynesia
NTAA
Canada (C)
Sth America (S)
ChileSantiagoSC,SA
Europe (E,L)
-> Y,A,K,N,R,P,V,W,Z<- F
<-W(ex WA,WI,WP,WR)D,G,H,O,R,U,V,Z->Y,A,F,N
Tonga
NFTTF
Oman (OOMS)
Zimbabwe (FV)
Botswana (FB)South A frica (FA)M alawi (FW)M adagascar (FM)Seychelle s (FS)Ga bon (FO)Swaziland (FD)
CambodiaPnom PenhVDPP
Myanmar
VYYY VietnamHanoiVVVVLaos
VientianeVLVT
Japan
Ryukyu IsROAH
TaiwanTaibeiRCTP
New Caledonia
NWWW
Fortuna & Wallis IsNLWW
AYPY
Bangladesh
VGZRBhutan
VQPR
K uwait(OKBK)
ChinaGuangzhouZGGG
Hong KongVHHH
Sth KoreaSeoulRKSS
Russian FederationKhabarovskUHHH
Europe Rome (LIII)
Europe London (EGGG)
Kenya Nairobi (HK,D,F,G)
IndiaChennaiVOMM
VietnamHochiminhVVTS
MalaysiaKuala LumpurWMKK
ThailandBangkokVTBB
IndiaCa lcuttaVECC
PhillipinesManillaRPLL
Sri LankaColomboVCCC
Sri LankaColomboVCCC
Sri LankaColomboVCCCColombo
MaldivesMaleVRM M
IndonesiaBatamWIKB
VanuatuPor t VilaNVVV
IndonesiaJakartaWIII
SingaporeWSSS
MauritiusFIMM
Kirribati
NGTT
Samoa
NSFA
Niue IsNIUE
Cook IsRaratongaNCRG
New ZealandChristchurchNZCH
Iceland/Greenland (B)USASalt Lake CityKSLC
FijiNadiNFFN
ANAU
AustraliaBrisbane
Solomon IsHoniaraAGGG
YBBB
Nth K oreaPyongyangZKKK
IndiaMumbaiVABB
PakistanKarachiOPKC
Nauru
Papeete
Aug 2000
ChinaBeijingZBBB
TokyoJapan
RJAA
Nepa lKathmanduVNKT
Nepa lKathmanduVNKT
<-Y,AG,AN,AY,D,F,G,H,O,R,U,V,W,Z->NZ,NC,NT,NI
<-Y,A,FI,W->B,C,E,K,L,M,P,S,T
<-WI,WA,WP,WR-> Y,A,B,C,F,K,M,N,P
IndiaDelhiVIDD
<-Y,A,D,F,G,H,NV,O,R,U,V,W,Z->N(ex NZ,NC,NT,NI,NV
Russian FederationMoskva
Russian FederationIrkutskUIII
KwajalenPKMJ
PTYA
ChuukPTOK
PonapeiPTPN
KosraePTSA
UUUU
50bd
2400 X.25
.
2400 X.25
2400 X.25
600 COPB
2400 X.25
2X50 bd
2400 X.25
2400 bd
75bd
300bd
2400 X.25
1200 X.25
75bd
50bd
50bd
2400 X .25
2400 X.25
300 COPB
9600bd
4800 X.25
9600 X .25
9600 X .25
2400bd
1200 bd50bd
1200 bd200bd
Afghanistan (OA KB)
300bd
50bd
2400 X.25
1200bd X.25
50bd
Ulaan BaatarMongolia
ZMUB
1200bd
50bd
50bd
300 COPB
9600 X .25
75bd
300bd
2X75bd
2400bd
50bd2400bd
50bd
200 bd
Tashkent
50bd
Ka bul
50bd
50bd
300bd
300 bd
2400 bd
50 bd
2400 bd
50 bd
300 bd
300 bd
KunmingZPPP
Yangon
Paro
Darussalam
75bd300 bd
Naha
Apia
Funafuti
Noumea
Pago Pago
TarawaTongatapu
50 bd
MacauVMMC
Muscat Seeb
Dhaka
50 bd RTT
Marshall Is
2400 X.25
9600 X .25
9600 X.25
2X75 bd
200bd
IndonesiaUjungWAAA
Central America(M,T)
1200 X.25
9600 X.25China
9600 X.25300 bd
2400 bd
4800 X.25
2 X 75bd
1200 COPB
50 bd
1200 X.25
1200 X.25
1200 X.25
1200 X .25
1200 X.25Yap
50bd
5
50 bd
PalauKoror PTRO
1200 X.25
75bd2400 X.25
9600bd
Current Regional Circuit Speeds
75 Baud13%
200bps4%300bps
12%600bps
2%1200bps
13%
2400bps21%
50 Baud21%
4800bps2%
9600bps12%
50 baud to 1200bps = 65%50 baud to 4800bps = 88%
Current Regional Protocols
None59%
COPB6%
X.2535%
Non ATN Protocols = 65%
Stage 1 - Upgrade of Circuits
�ATN at present requires Subnetworks to interface at X.25
�Currently the majority of AFTN circuits (88%) will not be suitable for ATN
�This will require new circuits to be implemented or existing circuits to be upgraded
Stage 1 - Bandwidth Issues
�Bandwidth for circuits will need to be increased substantially.
�Speeds from 9.6kbps to 64kbps or higher will need to be considered.
�Overheads from each layer of the OSI stack will increase total message size as much as 94% (standard AFTN message size using AMHS)
ATC Site A
ATSMHS
AIDC
ADS
CPDLC
FIS
Airborne Site C
ADS
CPDLC
FIS
ATC Site B
ATSMHS
AIDC
ATN Applications
ATN
Stage 2 - ATN Backbone
�Selection of Locations based on Existing Inter-Regional Connections and Main Internal Connections
�Diversity for Backbone Connectivity within the Asia/Pacific Region and Neighbouring Regions
�Min of 56kbps to 64kbps for Backbone Trunk Speeds
ATN Regional Backbone
Inter-Regional Trunk ConnectionNew Inter-Regional Trunk ConnectionIntra-Regional Trunk ConnectionNew Intra-Regional Trunk Connection
NAM Region
EUR Region
MID Region
AFI RegionAPAC Region
AU
CN JP
IN
TH
SG
HK
FJ
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
Asia/Pacific ATN Routing
AU
CN JP
IN
TH
SG
TO TV WFPF
NZ
ID
KR
NR
CK KI NC WS
NP
MO
TW
VUPG SBBD
VN
BNPH
MM
MV
LKBT
KH
LA MY
KP MN
NU
US
MH FM PWAS
ATN Backbone Site
ATN Site
HK
FJ
ISO3166 Country CodesCountry ISO Code Country ISO Code
American Samoa AS Mongolia MNAustralia AU Myanmar MMBangladesh BD Nauru NRBhutan BT Nepal NPBrunei Darussalam BN New Caledonia NCCambodia KH New Zealand NZChina CN Niue NUCook Islands CK Pakistan PKFiji FJ Palau PWFrench Polynesia PF Papua New Guinea PGHong Kong China HK Philippines PHIndia IN Samoa WSIndonesia ID Singapore SGJapan JP Solomon Islands SBKiribati KI Sri Lanka LKKorea, Democratic People’sRepublic of
KP Taibei TW
Korea, Republic of KR Thailand THLao LA Tonga TOMacau China MO Tuvalu TVMalaysia MY United States USMaldive Islands MV Vanuatu VUMarshall Islands MH Viet Nam VNMicronesia, Federated States of FM Wallis and Futuna Islands WF
AMHS ICD - (1)� Development of an Interface Control Document
for interconnection of AMHS in the Asia Pacific Region.
� Document based on the AMHS work performed between Japan and USA.
� Outlines the Mandatory and Optional Requirements described in the AMHS PICS that are to be implemented within the Asia Pacific Region to maintain operability.
� Document will be presented at the Fourth ATNTTF meeting.
AMHS ICD - (2)
�The ICD does not include any additional features such as CIDIN/AMHS Gateway, Security and Directory Service which are in ICAO Doc 9705/AN-965, THIRD EDITION.
� The ICD can be enhanced to include such additional features in the future.
AFTN to AMHS Transition
�ATS Message Handling System will most likely be one of the first ATN Applications to be implemented by most States in the Region.
�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
Full Implementation of AMHS
Site BATNRouter
AMHSSystem
Site CATNRouter
AMHSSystem
Site DATNRouter
AMHSSystem
ATN
Site A
AMHSSystem
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
ATNRouter
Implementation of AFTN/AMHS Gateways
Site ASite DAFTN
System
Site CAFTNSystem
X.25X.25
Low Speed
Low Speed
Site BAFTNSystemX.25
AMHSGateway
ATNRouter
ATNRouter
AMHSGateway
AFTNSystem
Migration to AMHS - 1
Site A
AMHSSystem
ATNRouter
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
AMHSGateway Site DAFTN
System
X.25X.25
Site CAFTNSystem
ATNRouter
AMHSGateway
ATN
Site BATNRouter
AMHSSystem
Migration to AMHS - 2
Site A
AMHSSystem
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
ATNRouter
Site BAMHSSystem
ATNRouter
Site DAFTNSystem
ATNRouter
AMHSGateway
ATNSite CAMHS
SystemATN
Router
Full AMHS Implementation
Site BATNRouter
AMHSSystem
Site CATNRouter
AMHSSystem
Site DATNRouter
AMHSSystem
ATN
Site A
AMHSSystem
Domestic Network
DomesticAMHS
Systems
DomesticAMHS
Terminals
ATNRouter
AIDC Implementation
�ATS Inter-facility Data Communication� ATN AIDC is not Compatible with AIDC
over AFTN.�Implementation of ATN AIDC will need to
be implemented by agreement between States.
�Possible phased implementation could be AIDC over AFTN to AIDC/AFTN over AMHS.
AIDC/AFTN Over AMHS
Site A
AMHSSystem
Domestic Network
AIDC/AFTNEnd
System
ATNRouter
Site B
ATNRouter
AMHSSystem
Domestic Network
AIDC/AFTNEnd
System
ATN
Full AIDC Implementation
Site A
AMHSSystem
Domestic Network
AIDCEnd
System
ATNRouter
Site B
ATNRouter
AMHSSystem
Domestic Network
AIDCEnd
System
ATN
Summary
�Implementation of 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.
�Interim arrangements can be set up between States which have already started their implementation programs.