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.

An outline of the GTS &the Improved MTN project for FWIS

By Hiroyuki IchijoJapan Meteorological AgencyISS/ITT-FWIS 2003 (Kuala Lumpur, 20-24 October 2003)

1. Structure of the GTS (Global Telecommunication System)

MTN = Core of the GTSmanaged by MTN centres in cooperation with WMO

RMTNmanaged by each

Regional Association

National level network

managed by each Member

RTHs (Regional Telecommunication Hubs)

NMTNsNational Meteorological Telecommunication Networks

NMTN

NMTN

NMTN

NMTN

NMTN

NMTN

NMTN

NMTN

NMTNNMTN

NMTNNMTN

NMTN

NMTN

NMTN NMTN

RMTNsRegional Meteorological

Telecommunication Networks

RMTN in RA I

RMTN in RA II

RMTN in RA III

RMTN in RA IV

RMTN in RA V

RMTN in RA VI

MTNMain Telecommunication

Network

NMCs(National Meteorological Centres)

　 Centre　classification　　

MTN Centres(RTHs on the MTN)

NMC

RTH

2. MTN configuration

MTN　(Main　Telecommunication　Network)　consists　of　18　MTN　Centres　and　24　connections.　　

Melbourne

Washington

Bracknell

New Delhi

Beijing

Jeddah

NairobiDelhi

Dakar

Algiers

Buenos Aires

Brasilia

Moscow

Cairo Tokyo

SofiaPragueToulouse

Offenbach

Region VI Region II Region IV

Region I Region V Region III

3. Regional aspect : Region II case

Current Status of RMTN in RA II (As of 10 September 2003)

Regional plan : 78 circuits Implemented : 67 circuits Implementation rate : 86 %

Vientiane

Ulaanbaatar

Baghdad

Doha

Kuwait

Bahrain

Dhaka

Yangon

Kathmandu

Kabul

Karachi

ColomboMale

Hanoi

Phnom Penh

PyongYang

Ashgabad

Macao

64K

14.4K

Dushanbe

Almaty

NI

NI

NI

NI

Seoul

NI

NI

19.2-33.6K (V.34)

64K

19.2-33.6K V.34

2.4K

9.6K

4.8K

64K

128K

7.2K

9.6K

50

50

50

50

50

64K

100

200

1200

2.4K

64K

100

200

75

75

75

1200

75

50

100

7575

9.6K

Melbourne

Offenbach

Offenbach

Cairo

Cairo

Algiers

Moscow

Kuala Lumpur

Tashkent

Novosibirsk Khabarovsk

Bangkok

Frame RelayCIR<16/16K>

Frame RelayCIR<16/16K>

Melbourne

Washington

Frame RelayCIR<16/16K>

NI

NI 19.2-33.6K (V.34)

19.2-33.6K (V.34)

19.2-33.6K (V.34)

Bishkek

64K

2.4K

Singapore

9.6K

19.2-33.6K (V.34)

Tehran

Sanaa

200

Hong Kong

Moscow

NIFrame Relay

CIR<32/32K>

64K

Frame RelayCIR<32/32K>

Tokyo

Beijing

Frame RelayCIR<16/16K>

200

New Delhi

IMTN-MDCN CIR<32/768K>

IMTN-MDCNCIR<16/32K>

Manila

IMTN-MDCNFrame Relay

CIR<48/48K>

19.2-33.6K (V.34)via Moscow

Internet

19.2-33.6K (V.34)

Jeddah

Internet Internet

Internet

Muscat

Emirates

NI

Id V.34

Id V.34

64K

64K

64K

Internet

Washington

Internet

ISDN

NI

RTH in Region II

NMC in Region II

Centre in other region

MTN circuitRegional circuitInterregional circuitAdditional circuit

Non-IP linkIP link

NI No implementation

19 Upgrade Plans of RMTN in RA II within 2 years

Vientiane

Ulaanbaatar

Baghdad

Doha

Kuwait

Bahrain

Dhaka

Yangon

Kathmandu

Kabul

Karachi

ColomboMale

Hanoi

Phnom Penh

PyongYang

Ashgabad

Macao

64K

Dushanbe

Almaty

NI

NI

Seoul

NI

64K

V.34

64K

9.6K

64K

128K

64K

50

50

64K

100

200

1200

2.4K

75

1200

75

50

100

7.2-9.6K 7575

9.6K

Melbourne

Offenbach

Offenbach

Cairo

Cairo

Algiers

Moscow

Kuala Lumpur

Tashkent

Novosibirsk Khabarovsk

Bangkok

Frame RelayCIR<16/16K>

Frame RelayCIR<16/16K>

Melbourne

Washington

Frame RelayCIR<16/16K>

NI

19.2-33.6K (V.34)

Plans of RMTN in RA II for 2003-2005

Bishkek

64K

Singapore

9.6K

RTH in Region II

NMC in Region II

Centre in other region

MTN circuitRegional circuitInterregional circuitAdditional circuit

Non-IP linkIP link

NI No implementation

Tehran

Sanaa

Hong Kong

Moscow

NIFrame Relay

CIR<32/32K>

IMTN-MDCNCIR<48/48K>

Tokyo

Beijing

Frame RelayCIR<16/16K>

200

New Delhi

IMTN-MDCNCIR<32/768K>

Manila

IMTN-MDCNCIR<48/48K>

(V.34)via Moscow

IMTN-MDCNCIR<8/8K>

IMTN-MDCNCIR<16/16K>

64K

64K

64K

Frame RelayCIR<16/16K>

64K

(V.34)

Internet

Internet InternetInternet

Internet Internet

Internet

Jeddah

Muscat

Emirates

Internet

V.34V.34

9.6K

64K

64K

64K

64K

64K

V.34

Internet

64K

64K

V.34

Internet

64K

Internet

Washington

Internet

ISDN

IMTN-MDCN

Progress of improvement in circuit speed in RA II

3833 32 28 28

21

22

18 18

159

5

310 11

1825

33

0%

25%

50%

75%

100%

Feb 1997 Aug 1999 Sep 2000 Jan 2002 Aug 2003 2005 (plan)

More than9600bps

2400 to 9600(inclusive)

less than2400bps

The numberof circuits

Low speed circuits are still more than half. It is a problem.

Achievement rate : about 35% ( as of August 2003)

Estimation rate : about 55% by the end of 2005

Progress in migration to TCP/IP in RA II

0

10

20

30

40

50

Feb 1997 Aug 1999 Sep 2000 Jan 2002 Aug 2003 2005 (plan)

Additional circuits

Interregional circuits

Regional circuits

MTN circuits

number of circuits

4. Strategies to improve the GTS

Strengthen the overall GTS capabilitieswith cost-effectiveness and technical trends

Migration to TCP/IP

Use ofcost-effective

networks Strategies

Leased circuits Legacy protocols Traditional GTS

Improved GTS

• Internet like applications• Saving implementation costs and human resources• allowing latitude in selecting a network service

• Expanding bandwidth• Flexible connectivity• Saving recurrent cost

Layer separation concepts

Message Switching

Message Switching

Server/client Server/client

File transfer File transferApplication level

Transport level

Frame Relay

IP-VPN

Transmissionprotocol level

Use of cost-effective networks

Migration to TCP/IP

Adding applications

Legacy protocol Legacy protocolTCP/IP TCP/IP

Office AOffice B

Network cloud

Office C

Network user Network supplier

Establish a new connection between B and C Yes sir!

We do everything in network

management!

Logical connectivity of managed data-communication network

Expand the capacity between A and B

Example of the Improved GTS : East Asian triangles

Beijing

Tokyo

Hong　Kong

Seoul

64kbps

64kbps

9600bps

9600bps

200bpsAsynchronous

X.25

X.25

X.25

X.25

Beijing

Tokyo

Hong　Kong

Seoul Frame Relay NetworkFrame Relay Network

Upgrade　items:1)　Migration　to　TCP/IP2)　Use　of　Frame　Relay　Network

Benefit of the Hong Kong-Tokyo upgrade

Hong KongHong Kong TokyoTokyo

Before theupgrade

After the upgrade Before the upgrade After the upgrade

HK$ 12,743 HK$ 7,470 212,560 yen 165,020 yenMonthly runningcosts Cost saving of HK$ 5,273 (about

US$ 677) a monthCost saving of 47,540 yen (aboutUS$ 450 ) a month

Transmissionspeed

200 bps16 kbps (CIR)nearly 64 kbps

(at a burst)200 bps

16 kbps (CIR)nearly 64 kbps

(at a burst)

Holdingtransmissionqueues

Sometimes Rarely Always Rarely

Transmissiondelay

50 sec. (average)72 min. (maximum)

1 sec. (average)20 sec. (maximum)

880 sec. (average)130 min. (maximum)

6 sec. (average)69 sec. (maximum)

Per

form

ance

Receivingcondition

Good butoccasionallyreceiving garbledmessages by bit-error

Excellent

Mostly good butsometimesreceiving garbledmessages by bit-error

Excellent

5. Status on the Improved MTN (IMTN)

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.

Bracknell

Sofia

Cloud IICloud II

Melbourne

Buenos Aires

TokyoBeijing

New Delhi

Nairobi

Cairo

Toulouse

Dakar

Algiers

MoscowWashington

Brasilia

Offenbach

Jeddah

Prague

Frame　RelayFrame　Relay　　by　BT　Igniteby　BT　Ignite

Frame　RelayFrame　Relay　　　　　　　　by　Equantby　Equant

Cloud ICloud I

Specific characteristics of IMTN clouds

Cloud I Frame Relay

Melbourne

Tokyo

1.5Mbps

Washington

256kbps

Bracknell

256kbps

Access circuit 1.5Mbps

32kbps

16kbps 16kbps

16kbps

CIR= 768kbps 32kbps

64kbps32kbps

32kbps

32kbps

PVC

a) Flexibility of establishing logical connections (PVC) on an access circuitb) Asymmetric bandwidths (CIR: Committed Information Rate)c) Better performance than CIR with minimum delay (Turnaround time by SLA)

Unbalanced traffic

0

10

20

30

40

50

60

00 03 06 09 12 15 18 21 [UTC]

File

FAX

BIN

AN

[Mbytes/20 min] Washington to Tokyo (CIR=768kbps) (3 October 2003)

withAsymmetric CIRs

384kbps line(Half of CIR)

Traffic status on the GTS (Example of daily volume received at RTH Tokyo)

DataFrom

Washington(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 on the CIR basisbasis [on practical basis]

14.4%[11%]

7.2%[3%]

6. Prospect of IMTN evolution for FWIS

PVC Socket and FTP connections

for GTS operation

Access circuit

Any test connections for Pilot Tests

Transition environment for pilot tests and parallel operations

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

PVC for GTS operation

PVC for Pilot Tests

Socket and FTP connections

Access circuit

Any test connections

Possible evolution into IP-VPN

One of VPN services is IP-VPN which is different in backbone management from Internet VPN.

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

Closed

IP　networkby　a　provider

CE PE

CE PE

CE

CE

IP IP Label IP Label

Core Router

Core RouterCore Router

PE

IP

VPN group

VPN group

IP-VPN with MPLS

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

InternetIPsec Product

ESP AH IP

VPN group

VPN group

IPsec Product

IP ESP AH IP

IP

IPsec Product

Internet VPN with IPsec

7. Administrative aspect of the improved MTN

InternationalTelecom.Carrier

X

NMHSA

InternationalTelecom.Carrier

Y

NMHSB

contractual boundarybetween X and Y

• Contract between A and X• Payment for the X portion to the

boundary

• Contract between B and Y• Payment for the Y portion to the

boundary

Bill

Payment

Bill

Payment

Tariff of Xin the localcurrency

Tariff of Yin the localcurrency

Traditional method : bilateral contract/billing

Frame RelayNetwork

X

Frame RelayNetwork

YNNI

Collaborative method : one-stop concept & multi-end billing

• Contract between A and X• Individual bill and payment

based on charge rules agreed by customers

Provider X

Bill

Payment

Tariff of Xin a majorcurrency

• MoU includes charge rules

MoUamongcustomers

NMHS A(Primary customer)

NMHS B(Secondary customer)

Bill

Bill Payment

Payment

NMHS C(Secondary customer)

Network

supplied by

a single provider X

Tentative conclusions

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