Asia/Pacific ATN Regional Planning. ATN Seminar Chiang Mai, 11 th -14 th December 2001 Presented by Craig Head

Transcription

1 Asia/Pacific Regional Planning Seminar Chiang Mai, 11 th -14 th December 2001 Presented by Craig Head

2 Transition Task Force The Transition Task Force (TTF) was established by APANPIRG/9 (1998) to address Issues and to deal with residual AFS Issues. The TTF reports are reviewed by CNS/MET Sub-Group before being submitted to APANPIRG The TTF will schedule its fourth meeting in Mumbai in April 2002.

3 TTF Responsibilities The TTF is Responsible for the Development of: Transition Guidance Material Transition Plan 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)

4 TTF Working Groups The TTF Established Two Working Groups: Working Group A Development of technical plans Working Group B Development of an transition plan and other technical documents

5 TTF Working Group A Established to develop the following Plans: Routing Architecture Plan NSAP Addressing Plan Naming Plan NSAP Registration Plan WG A Includes Representatives from: Australia Japan Thailand United States

6 Status of Plans Plans submitted for review at the TTF/3 in March Plans were reviewed at CNS/MET Sub Group/5 in July Plans were approved by APANPIRG/12 in August Plans to be circulated to States for comments.

7 TTF Working Group B Established to develop the 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

8 Technical Documents Transition Plan Interface Control Documents Router Interface Control Documents Routing Policy for IDRP Routing Policy for MTA Directory Services Management Security Performance

9 Status of Documents Transition Plan was submitted for review at the TTF/3 in March Other Documents are currently in the development phase. ICDs and other critical documents to be presented at the TTF/4 meeting.

10 Routing Architecture Plan The establishment of Backbone Boundary Intermediate s (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

11 Backbone BIS China Japan Thailand Hong Kong Fiji Singapore India Australia APAC Region

12 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.

13 NSAP Address Structure AFI 1 Octet IDI 2 Octets VER 1 Octet ADM 3 Octets RDF 1 Octet ARS 3 Octets LOC 2 Octets SYS 6 Octets SEL 1 Octet AFI - Authority and Format Identifier - defined by SARPS IDI - Initial Domain Identifier - defined by SARPS VER - Version - defined by SARPS and by Plan ADM - Administration Identifier - defined by Plan RDF - Routing Domain Format - not used set to zero ARS - Administration Region Selector - defined by Plan LOC - Location - defined by Plan SYS - Identifier - to be defined by State SEL - NSAP Selector - defined by SARPS

14 Naming Plan Aligned with the Global Naming Convention to be adopted by ICAO Panel Working Groups have recommended that the Global Naming Convention be included in Edition 3 of the Manual

15 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)

16 Naming Summary Attribute Assigned By Value Comment Country-name (C) ITU-T XX International Organization ADMD (A) ICAO ICAO ICAO Responsibility to register PRMD (P) ATSO e.g. THAI Organization name (O) Organizational- Unit name (OU1) Common Name (CN) ATSO ATSO e.g. AEROTHAI e.g. BB ATSO registered private domain with ICAO. Local/national geographical information, which can be based on ICAO Location Indictors (Doc 7910) ICAO Location Indicator (Doc 7910) ATSO e.g. VTBBYFYX AFTN indicator address

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

18 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

19 Zimbabwe (FV) Botswana (FB) South Africa (FA) Malawi (FW) M adagascar (FM) Seychelles (FS) Gabon (FO) Swaziland (FD) Asia/Pacific AFTN Topology 200 bd Russian Federation Russian Federation Irkutsk Moskva Mongolia UIII 50bd UUUU Japan Ulaan Baatar Russian Federation Khabarovsk 24 00bd Tokyo ZMUB 50bd RJAA UHHH Iceland/Greenland (B) 1200bd K uwait(okbk) 50bd 1200 bd USA 9600 X X.25 Salt Lake City 50 bd 300 bd KSLC Canada (C) Nth Korea Sth Korea 9600 X.25 Pyon gyang Seoul Japan 1200 COPB Ponapei Kosrae ZKKK RKSS Na ha PTPN Pakistan Ryukyu Is PTSA 1200 X.25 China Europe (E,L) Karachi Beijing 9600 X.25 ROAH Chuuk OPKC Nepa l ZBBB 9600 X.25 PTOK Kathmandu 300 bd 4800 X.25 Phillipines 1200 X.25 Ka bul VNKT 9600 X X.25 Taiwan Yap 1200 bd 75bd Manilla 1200 X.25 Afghanistan (OAKB) China Kunming China Taibei RPLL PTYA Central America 4800 X bd ZPPP RCTP (M,T) Guangzhou Uzebekistan (UTTT) 50 bd RT T Palau 1200 X.25 ZGGG 2X75bd India Koror Tashkent India 50bd Ca lc utta Myanmar Hong Kong PTRO Sth America (S) Delhi VECC Yangon 300bd Bangladesh VHHH 50bd VIDD VYYY Vietnam 1200 X.25 Vietnam 50bd Dha ka 2400 X bd Hanoi Bhutan VGZR Macau Hochiminh Laos VVVV 1200 X COPB Marshall Is Paro VMMC VVTS Kwajalen VQPR 300 bd Vientiane 9600bd PKMJ VLVT 9600bd Brunei 50bd 2 X 75bd Thailand Darussalam 2400 X.25 Bangkok 75bd WBSB Oman (OOMS) VTBB 300 COPB 2400bd Malaysia Musc at Seeb 50 bd 30 0bd 2400 X.25 Kota Kinabalu Malaysia WBKK 2X75 bd 2400bd American Samoa Kuala Lumpur India Samoa India. WMKK 2400 X.25 Pago Pago 50bd Mumbai Chennai Apia NSTU VOMM NSFA Kenya Nairobi (HK,D,F,G) VABB 300 bd 50 bd 75bd <-Y,A,FI,W 2400 X X.25 ->B,C,E,K,L,M,P,S,T Cambodia 50 bd Ne w Caledonia Europe Rome (LIII) Pnom Penh Nauru Singapore 1200 X.25 Noumea 2400 X.25 VDPP NWWW WSSS ANAU Fiji Nadi 2400 bd 50bd NFFN Bahrain (OBBI) 200bd 2400 bd Indonesia PNG NLWW 2X50 bd Jakarta Port Moresby Solomon Is Fortuna & Wallis Is WIII Indonesia AYPY Honiara Europe London (EGGG) 1200bd X.25 50bd Ujung AGGG Van uatu 50 bd Port Vila Tuvalu Indonesia 600 COPB WAAA 2400 X.25 75bd NVVV Funafuti 50 bd Batam NGTA 50bd WI KB Tonga 2400 X bd 2400 X.25 Tongatapu Kirribati 75bd <- WI,WA,WP,WR NFTTF Tara wa NGTT Sri Lanka -> Y,A,B,C,F,K,M,N,P Colombo X.25 50bd VCCC Maldives Male VRM M Mauritius FIMM -> 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 50bd Australia Brisbane YBBB INTERNATIONAL AFTN - ASIA PACIFIC Aug 2000 <-Y,A,D,F,G,H,NV,O,R,U,V,W,Z ->N(ex NZ,NC,NT,NI,NV 2400 X bd French Polynesia Papeete 300 bd NTAA <-Y,AG,AN,AY,D,F,G,H,O,R,U,V,W,Z ->NZ,NC,NT,NI New Zealand Christchurch NZCH Niue Is NIUE Cook Is Rar atonga NCRG 2400 bd Chile Santiago SC,SA

20 Current Regional Circuit Speeds 2400bps 21% 4800bps 2% 9600bps 12% 50 Baud 21% 75 Baud 13% 1200bps 13% 600bps 2% 300bps 12% 200bps 4% 50 baud to 1200bps = 65% 50 baud to 4800bps = 88%

21 Current Regional Protocols X.25 35% COPB 6% None 59% Non Protocols = 65%

22 Stage 1 - Upgrade of Circuits at present requires Subnetworks to interface at X.25 Currently the majority of AFTN circuits (88%) will not be suitable for This will require new circuits to be implemented or existing circuits to be upgraded

23 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 )

24 Applications ATSMHS AIDC ADS CPDLC FIS ATC Site A ATSMHS AIDC ATC Site B ADS CPDLC FIS Airborne Site C

25 Stage 2 - 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

26 Regional Backbone CN JP EUR Region HK TH MID Region FJ NAM Region SG IN AFI Region APAC Region AU Inter-Regional Trunk Connection New Inter-Regional Trunk Connection Intra-Regional Trunk Connection New Intra-Regional Trunk Connection

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

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

29 ISO3166 Country Codes Country ISO Code Country ISO Code American Samoa AS Mongolia MN Australia AU Myanmar MM Bangladesh BD Nauru NR Bhutan BT Nepal NP Brunei Darussalam BN New Caledonia NC Cambodia KH New Zealand NZ China CN Niue NU Cook Islands CK Pakistan PK Fiji FJ Palau PW French Polynesia PF Papua New Guinea PG Hong Kong China HK Philippines PH India IN Samoa WS Indonesia ID Singapore SG Japan JP Solomon Islands SB Kiribati KI Sri Lanka LK Korea, Democratic People s Republic of KP Taibei TW Korea, Republic of KR Thailand TH Lao LA Tonga TO Macau China MO Tuvalu TV Malaysia MY United States US Maldive Islands MV Vanuatu VU Marshall Islands MH Viet Nam VN Micronesia, Federated States of FM Wallis and Futuna Islands WF

30 ICD - (1) Development of an Interface Control Document for interconnection of in the Asia Pacific Region. Document based on the work performed between Japan and USA. Outlines the Mandatory and Optional Requirements described in the PICS that are to be implemented within the Asia Pacific Region to maintain operability. Document will be presented at the Fourth TTF meeting.

31 ICD - (2) The ICD does not include any additional features such as CIDIN/ 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.

32 AFTN to Transition ATS Message Handling will most likely be one of the first Applications to be implemented by most States in the Region. Transition to can involve a number of steps Introduction of AFTN/ Gateways. To full Interconnection between States.

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

34 Full Implementation of Domestic s Domestic Terminals Router Site B Domestic Network Router Router Site C Site A Router Site D

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

36 Migration to - 1 Domestic s Domestic Terminals Router Site B Domestic Network Router Router Gateway AFTN X.25 Site C Gateway Site A X.25 AFTN Site D

37 Migration to - 2 Domestic s Domestic Terminals Router Site B Domestic Network Router Router Site C Site A Router Gateway AFTN Site D

38 Full Implementation Domestic s Domestic Terminals Router Site B Domestic Network Router Router Site C Site A Router Site D

39 AIDC Implementation ATS Inter-facility Data Communication AIDC is not Compatible with AIDC over AFTN. Implementation of AIDC will need to be implemented by agreement between States. Possible phased implementation could be AIDC over AFTN to AIDC/AFTN over.

40 AIDC/AFTN Over AIDC/AFTN End AIDC/AFTN End Domestic Network Domestic Network Router Router Site A Site B

41 Full AIDC Implementation AIDC End AIDC End Domestic Network Domestic Network Router Router Site A Site B

42 Summary Implementation of new links or Upgrade existing AFTN links where appropriate to be compatible with 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.