240 likes | 325 Views
An outline of the GTS & the Improved MTN project for FWIS. By Hiroyuki Ichijo Japan Meteorological Agency. ISS/ITT-FWIS 2003 (Kuala Lumpur , 20-24 October 2003). NMTN. NMTN. NMTN. NMTNs National Meteorological Telecommunication Networks. RMTNs Regional Meteorological
E N D
An outline of the GTS &the Improved MTN project for FWIS By Hiroyuki Ichijo Japan Meteorological Agency ISS/ITT-FWIS 2003 (Kuala Lumpur, 20-24 October 2003)
NMTN NMTN NMTN NMTNs National Meteorological Telecommunication Networks RMTNs Regional Meteorological Telecommunication Networks RMTN in RA II NMTN NMTN NMTN RMTN in RA VI NMTN RMTN in RA IV NMTN RMTN in RA I RMTN in RA III NMTN RMTN in RA V NMTN NMTN NMTN NMTN NMTN NMTN NMTN 1. Structure of the GTS (Global Telecommunication System) MTN = Core of the GTS managed by MTN centres in cooperation with WMO RMTN managed by each Regional Association National level network managed by each Member MTN Main Telecommunication Network Centre classification MTN Centres (RTHs on the MTN) RTH RTHs (Regional Telecommunication Hubs) NMC NMCs (National Meteorological Centres)
2. MTN configuration Region VI Region II Region IV Region I Region V Region III MTN (Main Telecommunication Network) consists of 18 MTN Centres and 24 connections.
Regional plan : 78 circuits Implemented : 67 circuits Implementation rate : 86 % RTH in Region II NMC in Region II Moscow Washington 64K Centre in other region 3. Regional aspect : Region II case 64K MTN circuit Regional circuit Interregional circuit Additional circuit IMTN-MDCN CIR<32/768K> 19.2-33.6K (V.34) Novosibirsk Khabarovsk 19.2-33.6K (V.34) 19.2-33.6K (V.34) via Moscow 9.6K 19.2-33.6K (V.34) Almaty NI No implementation 19.2-33.6K (V.34) 14.4K Non-IP link IP link NI NI Bishkek 19.2-33.6K (V.34) 19.2-33.6K V.34 19.2-33.6K (V.34) PyongYang Tokyo Ulaanbaatar Id V.34 Ashgabad Tashkent Offenbach Id V.34 75 Frame Relay CIR<32/32K> 4.8K NI 75 Baghdad Tehran IMTN-MDCN Frame Relay CIR<48/48K> NI Dushanbe Beijing NI NI NI Frame Relay CIR<32/32K> 7.2K 2.4K NI Offenbach Frame Relay CIR<16/16K> Kabul 50 Kuwait 9.6K 100 64K NI Seoul Karachi 64K 64K Bahrain New Delhi 64K 64K Jeddah Frame Relay CIR<16/16K> 128K 200 50 75 Doha 64K 75 1200 Kathmandu Moscow NI Hong Kong Internet Internet Emirates 50 ISDN 64K 2.4K 100 Internet 100 50 200 Hanoi 9.6K Macao Algiers 75 Dhaka Cairo Muscat Internet Internet Vientiane 9.6K Frame Relay CIR<16/16K> Internet 50 IMTN-MDCN CIR<16/32K> Cairo Yangon Sanaa Colombo 1200 50 Male 64K Melbourne 200 200 Manila Washington Bangkok Phnom Penh 75 NI Melbourne Current Status of RMTN in RA II (As of 10 September 2003) 2.4K Frame Relay CIR<16/16K> Kuala Lumpur Singapore
RTH in Region II NMC in Region II Moscow Washington 64K Centre in other region 64K MTN circuit Regional circuit Interregional circuit Additional circuit 19 Upgrade Plans of RMTN in RA II within 2 years IMTN-MDCN CIR<32/768K> Novosibirsk Khabarovsk 64K 19.2-33.6K (V.34) (V.34) via Moscow (V.34) V.34 NI No implementation Almaty 64K 9.6K Non-IP link IP link Bishkek 64K V.34 Internet V.34 PyongYang Tokyo Ulaanbaatar V.34 Ashgabad Tashkent Offenbach V.34 75 IMTN-MDCN CIR<48/48K> 7.2-9.6K 75 IMTN-MDCN CIR<8/8K> Baghdad Tehran NI Dushanbe Beijing IMTN-MDCN CIR<48/48K> NI IMTN-MDCN NI NI Frame Relay CIR<32/32K> Internet 64K Offenbach Frame Relay CIR<16/16K> Kabul 50 Kuwait 9.6K NI 64K 100 Seoul IMTN-MDCN CIR<16/16K> Karachi 64K 64K Bahrain New Delhi 64K Jeddah Frame Relay CIR<16/16K> Internet 128K 200 64K 64K Doha 75 Internet Kathmandu Moscow 1200 Hong Kong Internet Internet Emirates 50 64K 2.4K ISDN 100 64K Dhaka Internet 200 Hanoi 64K Macao Cairo Algiers Internet Internet Muscat Vientiane 9.6K Internet Internet 75 Frame Relay CIR<16/16K> Yangon Cairo Internet Sanaa 1200 Colombo 50 Male 64K Melbourne 64K 64K Manila Washington Bangkok 9.6K 64K Melbourne Frame Relay CIR<16/16K> Phnom Penh Frame Relay CIR<16/16K> Plans of RMTN in RA II for 2003-2005 Singapore Kuala Lumpur
The number of circuits Progress of improvement in circuit speed in RA II Low speed circuits are still more than half. It is a problem.
number of circuits Progress in migration to TCP/IP in RA II Achievement rate : about 35% ( as of August 2003) Estimation rate : about 55% by the end of 2005
Internet like applications • Saving implementation costs • and human resources • allowing latitude in selecting • a network service • Expanding bandwidth • Flexible connectivity • Saving recurrent cost Use of cost-effective networks Improved GTS Migration to TCP/IP Strategies Leased circuits Legacy protocols Traditional GTS 4. Strategies to improve the GTS Strengthen the overall GTS capabilities with cost-effectiveness and technical trends
File transfer File transfer Server/client Server/client Legacy protocol Legacy protocol Frame Relay IP-VPN TCP/IP TCP/IP Layer separation concepts Application level Adding applications Message Switching Message Switching Transmission protocol level Migration to TCP/IP Use of cost-effective networks Transport level
Office B Office C Network user Logical connectivity of managed data-communication network Office A Network cloud Expand the capacity between A and B Establish a new connection between B and C Yes sir! We do everything in network management! Network supplier
Tokyo Tokyo Asynchronous 200bps Hong Kong X.25 64kbps Frame Relay Network Hong Kong X.25 64kbps Seoul X.25 Seoul 9600bps X.25 9600bps Beijing Beijing Example of the Improved GTS : East Asian triangles Upgrade items: 1) Migration to TCP/IP 2) Use of Frame Relay Network
Hong Kong Tokyo Before the After the upgrade Before the upgrade After the upgrade upgrade HK $ 1 2 , 743 HK $ 7,470 212,560 yen 165,020 yen Monthly running C ost saving of HK$ 5,273 (about C ost saving of 47,540 yen (about costs US$ 677) a month US$ 450 ) a month 16 kbps (CIR) 16 kbps (CIR) Transmission 200 bps 200 bps nearly 64 kbps nearly 64 kbps speed (at a burst) (at a burst) Holding transmission Sometimes Rarely Always Rarely queues Transmission 50 sec. (average) 1 sec. (average) 880 sec. (average) 6 sec. (average) Performance delay 72 min. (maximum) 20 sec. (maximum) 130 min. (maximum) 69 sec. (maximum) Good but Mostly good but sometimes occasionally Receiving receiving garbled Excellent receiving garbled Excellent condition messages by bit- messages by bit- error error Benefit of the Hong Kong-Tokyo upgrade
Cloud I Frame Relay by BT Ignite Beijing Tokyo New Delhi Sofia Prague Washington Moscow Melbourne Brasilia Bracknell Jeddah Buenos Aires Cloud II Offenbach Frame Relay by Equant Nairobi Dakar Cairo Algiers Toulouse The IMTN project is making satisfactory progress. The planned configuration will be achieved in 2004 except for a few MTN centres in Regions I and III. 5. Status on the Improved MTN (IMTN)
PVC Access circuit 1.5Mbps CIR= 768kbps 1.5Mbps 32kbps Tokyo Washington 16kbps 32kbps 32kbps 32kbps 16kbps 16kbps Bracknell Melbourne 256kbps 64kbps 32kbps 256kbps Cloud I Frame Relay • Flexibility of establishing logical connections (PVC) on an access circuit • Asymmetric bandwidths (CIR: Committed Information Rate) • Better performance than CIR with minimum delay (Turnaround time by SLA) Specific characteristics of IMTN clouds
with Asymmetric CIRs Unbalanced traffic 384kbps line (Half of CIR)
Data FromWashington (CIR=768kbps) From Melbourne (CIR=32kbps) From other GTS circuits WWW data and products in message type AN 43Mbytes 3Mbytes 4Mbytes Binary 84Mbytes 6Mbytes 2Mbytes T4 fax 2Mbytes 1Mbytes 1Mbytes Large satellite data File 1063Mbytes 15Mbytes --- Total 1192Mbytes 25Mbytes 7Mbytes Utilisation rate on the CIR basis [on practical basis] 14.4% [11%] 7.2% [3%] Traffic status on the GTS (Example of daily volume received at RTH Tokyo)
Transition environment for pilot tests and parallel operations 6. Prospect of IMTN evolution for FWIS Option 1) coexistence of test connections with GTS operational connections on a PVC Easy way but sharing CIR bandwidth of a PVC
Option 2) Separation of PVCs for GTS operational and test Minimum impact to GTS operation but additional PVC cost
VPN group IP Label IP Label Core Router CE Closed IP network by a provider PE CE PE VPN group CE Core Router Core Router PE CE IP IP Provider’s PEs and Core Routers based on MPLS have Label Tables and switch IP packets forward according to the Tables. CE : Customer Edge Router VPN : Virtual Private Network PE : Provider Edge Router MPLS : Multi Protocol Label Switching IP-VPN with MPLS One of VPN services is IP-VPN which is different in backbone management from Internet VPN. Possible evolution into IP-VPN
ESP AH IP ESP AH IP IPsec Product IPsec Product VPN group VPN group IPsec Product IP IP IPsec VPN products add/remove the ESP for encryption and encapsulation and the AH for authentication to/from an IP packet. ESP : Encapsulation Secure Payload AH : Authentication Header Internet Internet VPN with IPsec
Frame Relay Network X Frame Relay Network Y NNI Traditional method : bilateral contract/billing 7. Administrative aspect of the improved MTN
The IMTN can become a core transport network linking GISCs together. • In 2006, if a GISC will have connections of 1 – 1.5Mbps with other GISCs, expected recurrent monthly cost for the GISC could be US$ 5000 x ((a number of GISCs) - 1). • The IMTN can provide the environment for a test-bed and parallel operations In transition periods. • The IMTN seems to be available for connections among GISCs, DCPCs and NCs as long as the administrative hurdles could be cleared. Tentative conclusions