Upload
phungliem
View
216
Download
1
Embed Size (px)
Citation preview
World Meteorological Organization RA-II/WG-IOS/WIS-1/Rep. 5.1 (7)
RA II WORKING GROUP ON WMO INTEGRATED OBSERVING SYSTEM AND WMO INFORMATION SYSTEM (RA-II/WG-IOS/WIS)
Submitted by: Coordinator
Date: 25.XI.2011
FIRST SESSIONSEOUL, REPUBLIC OF KOREA 30 NOVEMBER - 7 DECEMBER 2011
Original Language: English
Agenda Item: 5.1
Analysis and proposals for WIS progress in RA II by Coordinator
REFERENCE: RA-II/WG-IOS/WIS-1/Doc.5.1
CONTENT OF DOCUMENT: This report contains the results of analysis and practically-inclined proposals for Regional
progress in Regional Meteorological Telecommunication Network (RMTN) and the VPN Pilot Project in RAs II and V. The proposals are included in the Final Report of the RA-II/WG-IOS/WIS-1 if agreed.
APPENDICES:
A Regional Meteorological Telecommunication Network for Region II (Asia), Current status as of 25 November 2011
B Multipoint Telecommunication Systems in Region II
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 1
1. Regional Meteorological Telecommunication Network (RMTN)1.1 Point-to-point circuits (see Appendix A)(1) Implementation of circuits
As of 25 November 2011, the RMTN in RA II includes eighty operational circuits (i.e. 9 MTN, 46 regional, 13 inter-regional and 12 additional circuits). On the other hand, eleven circuits in the Regional configuration plan are not in operation. Especially NMCs Baghdad (ought to have 2 regional circuits), Kabul (3) and Thimpu (1) are still isolated from the GTS. SYNOP reports in Iraq are currently put into the GTS by special arrangement between WMO and USA. NMC Kabul started sending SYNOP reports through the Internet by e-mail but now it has again stopped. RTH New Delhi is trying to solve the problem. In spite of difficult situations, efforts to establish the circuits will be continued in cooperation with RTHs concerned. The configuration diagram of RMTN in RA II is shown in Appendix A
Table 1 Transition of the number of RMTN circuits in RA IIFeb 1997
Aug 1999
Sep 2000
Jan 2002
Aug 2003
Sep 2004
Sep 2006
Aug 2007
Oct 2008
Sep 2009
Aug 2010
Nov 2011
The number of the circuitsin operation
MTN circuits 8 8 8 8 8 8 8 8 8 9 9 9Regional circuits 42 42 42 42 42 42 46 47 45 46 46 46
Interregional circuits 11 10 10 12 12 12 12 12 12 13 13 13
Additional circuits 2 1 1 3 5 5 4 10 10 12 12 12Total 63 61 61 65 67 67 70 77 75 80 80 80
The number of the circuits
not in operation
MTN circuits 0 0 0 0 0 0 0 0 0 0 0 0Regional circuits 10 10 10 9 9 9 9 8 10 9 9 9
Interregional circuits 0 2 2 1 1 1 1 1 1 0 0 0
Additional circuits 1 1 1 0 1 1 2 2 2 2 2 2Total 11 13 13 10 11 11 12 11 13 11 11 11
The number of the circuits in Regional
configuration plan
MTN circuits 8 8 8 8 8 8 8 8 8 9 9 9Regional circuits 52 52 52 51 51 51 55 55 55 55 55 55
Interregional circuits 11 12 12 13 13 13 13 13 13 13 13 13
Additional circuits 3 2 2 3 6 6 6 12 12 14 14 14Total 74 74 74 75 78 78 82 88 88 91 91 91
All circuits between centres are not necessarily registered as RMTN circuits. Basically the sustainable operational circuits to exchange mainly WWW data on a real-time basis should be included in the RMTN from the operational view of the GTS role. The RMTN circuits are categorized into as follows;
A : MTN circuitsB : main regional circuitsC : regional and supplementary regional circuitsD : interregional and supplementary interregional circuitsX : additional circuits
The definition of additional circuits (symbol: X) is ambiguous, but an agreement by both side centres is indispensable to include a circuit in RMTN.
{Proposal}The necessary conditions for an RMTN circuit should be defined as:(a) a sustainable operational circuit to exchange mainly WWW data on a real-time basis; and(b) both end centres agree on registration as an RMTN circuit.
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 2
(2) Improvement of circuit speedA current regional requirement in speed is more than 9.6kbps at least in consideration of
dissemination of observation data within 15 minutes, distribution of processed information of a large volume and handling various data types (e.g. binary, charts and files).
Figure 1 shows that most of dedicated circuits in operation meet the requirement. The achievement rate is 95 percent. On the other hand, there are new requirements of an “All Hazards Network” of 2 minutes end-to-end within WIS, and timely exchange of satellite and NWP products. The current requirement in speed decided in 1997 should be reviewed.
{Proposal}Regional requirement of minimum GTS bandwidth required as a RMTN circuit should be raised
from 9600bps to 64kbps to meet the performance requirements of an “All Hazards Network” of 2 minutes end-to-end within WIS.
Appropriate target GTS bandwidths should be defined at the next step considering requirements on operational data exchange of NWP and satellite products.
(3) Migration to TCP/IPThe migration towards TCP/IP on GTS circuits has been progressing considerably since
beginning of the 21 century in the Region. All circuits in operation but four are running on pure TCP/IP. The achievement rate is 95 percent. Although the migration to TCP/IP has been the regional strategy with a highest priority for last 10 years, it is time to make an end of the strategy.
{Proposal}The migration to TCP/IP should be removed from high-prioritized Regional strategies.
38 33 32 32 2820 18 15
82 2 2
22
18 1813
9
8
23
3
2 2 1
310 11
1825
3341 45
4852 54 55
0%
25%
50%
75%
100%
Feb 1997
Aug 1999
Sep 2000
Jan 2002
Aug 2003
Sep 2004
Sep 2006
Aug 2007
Oct 2008
Sep 2009
Aug 2010
Nov2011
More than 9600bps
2400 to 9600 (inclusive)
less than 2400bps
Figure 1 Progress of improvement in circuit speed in RA II (except for Internet links)
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 3
(4) Use of cloud based services (Frame Relay to IP-VPN with MPLS)According to the Strategic Plan in RA II and IMTN implementation plan, migration from costly
leased circuits to cost-effective circuits by using cloud based services has been promoted by each RTH. As the result, there was steady progress in migration to Frame Relay circuits from 2000 to 2006. Since 2006 GTS links on Frame Relay have been migrating to more cost-effective links on IP-VPN (Virtual Private Network) with MPLS (Multi Protocol Label Switching), along change of technical and market trends in international telecom services.
IP-VPN with MPLS is a fully managed private network different from Internet VPN. It is secure, flexible, scalable and cost-effective and provides any-to-any connectivity within a VPN group. In addition the IMTN project was completed with consolidation of two clouds into one MPLS.
Figure 3 Transition of number of circuits on cloud-networks (FR to MPLS)
14
912
17
9 9
31 1
10 10
16 20 20
0
5
10
15
20
25
Feb 1997
Aug 1999
Sep 2000
Jan 2002
Aug 2003
Sep 2004
Sep 2006
Aug 2007
Oct 2008
Sep 2009
Aug 2010
Nov2011
MPLS
Frame Relay
0
10
20
30
40
50
60
70
80
Feb 1997
Aug 1999
Sep 2000
Jan 2002
Aug 2003
Sep 2004
Sep 2006
Aug 2007
Oct 2008
Sep 2009
Aug 2010
Nov2011
Additional circuits
Interregional circuits
Regional circuits
MTN circuits
Figure 2 Progress in migration to TCP/IP in RA II
number of circuits
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 4
(5) Internet linksExpansion of the Internet use brought a possibility of a GTS link through the Internet. Internet
links have specific characteristics of no guarantee in transfer speed, delay time and security, and no responsible body in connectivity. Especially security risks and hidden costs to mitigate them are seriously emerging year by year. In spite of those negative characteristics, there are various opportunities for cost-saving (no charge except for the connection to ISP), vast transport capacity, flexible connectivity and introducing modernized technologies.
Although use of the Internet for a GTS circuit should be the very end solution in RA II, the number of circuits is currently 22 and is expected to increase further.
Internet VPN constructs a virtual exclusive network protected by encryption technology on the
Closed
IP networkby a provider
PE
PE
CE
CE
IP IP Label IP Label
Core Router
Core RouterCore Router
PE
IP
VPNgroup
VPNgroup
InputLabelInputPortOutput
LabelOutputPort............
Destination IPVPNNo.Output LabelOutput port............
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
Figure 4 IP-VPN with MPLS
0
2
4
6
8
10
12
14
16
18
20
22
24
Feb 1997
Aug 1999
Sep 2000
Jan 2002
Aug 2003
Sep 2004
Sep 2006
Aug 2007
Oct 2008
Sep 2009
Aug 2010
Nov2011
Additional circuits
Interregional circuits
Regional circuits
MTN circuits
Figure 5 Growth in GTS circuits through the Internet in RA II
number of circuits
Figure 6 Internet VPN with IPsec
Internet
IPsec Product
ESP AH IP
VPN groupVPNgroup
IPsecVPN 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
IPsec Product
IP ESP AH IP IP
IPsec Product
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 5
Internet. It provides cost-effective connectivity with moderate security.Since most of the existing Internet circuits do not use any VPN techniques, insecurity factors
lurk in them even if filtering of IP addresses and port numbers is implemented. A risk of invasion attacks by address spoofing and pretense definitely exists. It is strongly recommended that VPN techniques, especially IPsec, should be introduced. As of November 2011, VPN with IPsec is implemented in only two Internet circuits, i.e. Bangkok-Phnom Penh and Jeddah-Sana'a.
{Proposal}All RTHs should restudy feasibility of migration from costly leased circuits to cost-effective
circuits by using cloud based services such as IP-VPN with MPLS before introducing a facile way of the Internet use. In case of use of the Internet for an RMTN circuit as the very end solution, VPN techniques such as IPsec should be implemented in the circuit.
1.2 Multipoint telecommunication systems (see Appendix B) (1) Satellite broadcasting systems
Satellite broadcasting systems are used for complements to the GTS, backup source and cost-effective alternatives to HF radio broadcasts.
A Ku-band satellite-based broadcasting system by China Meteorological Administration has been fully operating since January 1998. It totally has a 2Mbps broadcasting rate and supports 256 logical channels. The typical channel rate is 64Kbps. It covers China and some neighbouring countries and is integrated into the RMTN. CMA-PCVSAT receivers installed in Dhaka, Hanoi, Ulaanbaatar, Yangon and Pyongyang are used for obtaining GTS data, CMA’s NWP products and CMA’s FY satellite data as complements of the low speed GTS circuits.
CMA is developing a new Ku-band satellite-based broadcasting system, DVB-S system, for replacing the current CMA-PCVSAT system. It supports both data broadcasting and multimedia program broadcasting, has been put into running since April, 2006. Comparing with the current PCVSAT system, the new system gains the main advantages of higher data rates and lower costs for remote stations due to using standard DVB (Digital Video Broadcasting) technology. Currently, the DVB-S system has a hub station and over 400 receiving stations, and its total broadcasting speed is 8.5Mbps.
CMA also operates a C-band satellite-based broadcasting system – FENGYUNCast. It is CMA’s contribution to GEONETCast, and started operation since 2006. It covers Asia and Pacific Ocean with 2Mbps broadcasting rate, and has different kinds of satellites data distributed, including FY-2C, FY-2D, FY-1D, NOAA/AVHRR, MODIS (TERRA, AQUA), etc. Currently, FENGYUNCast receivers has been installed in Australia, Bangladesh, DPRK,
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 6
Indonesia, Iran, Kyrgyz, Lao P.D.R, Malaysia, Mongolia, Myanmar, Nepal, Pakistan, Philippines, Sri Lanka, Tajikistan, Thailand, Uzbekistan, and Viet Nam.
Russian satellite broadcasting system (TV-Inform-Meteo) had provided fax charts and AN bulletins since 1995. It was replaced by a new DVB satellite system named “Meteoinform”. The Meteoinform provides multicast functions for meteorological data based on MITRA (Multi-address Information Transmission) technology. The broadcasting at high-speed (up to 56 Mbps) is carried out in the C-band through 4 Russian satellites (Expres AM1, Expres AM3, Expres AM11 and Yamal-200) providing the coverage of the whole territory of the Russian Federation and a number of adjacent countries. In the majority of towns, the subscribers can receive 2 or 3 satellites simultaneously. More than 100 terminals including terminals in Kazakhstan, Kyrgyz and Tajikistan have already been connected to it. The rates in the channels of various satellites were chosen as required from 64 to 1024 kbps and can be used in the course of operation without changing the H/W and S/W. The programmes over various channels are also different and depend on the users’ requirements in the area of reception.
RTH New Delhi operates INSAT-DMDD. 37 DMDD receiving systems have been installed at various locations in India. DMDD receiving systems have been installed in NMCs Colombo, Dhaka, Kathmandu and Male used for complements to GTS.
RTH New Delhi switched their data serving for users including marine vessels from HF radio broadcasts to a satellite-based DAB (Digital Audio Broadcast) by World Space through Asia Star Satellite in August 2003. This is a very cost-effective solution. The approximate cost for distribution of 1 Mbytes through the satellite is US$ 12. A user receives required data using a commercial radio receiver with a small L band antenna and a PC card adapter, which is manufactured by several companies at an approximate cost of US$150.
METEOSAT-MDD service has been discontinued as from 14 June 2006. The MDD data stream itself is now embedded in the EUMETCast dissemination, and the same user-terminal can receive EUMETSAT images as well as MDD data and products. Oman (C and Ku bands) and Uzbekistan (Ku) already implemented EUMETCast receivers.
WAFS (ISCS, SADIS) broadcasting is regularly used for operation in most of RTHs/NMCs.
Many RTHs already discontinued HF radio broadcasts because of its high recurrent cost, its obsoleteness and emerging of standard satellite broadcast services. Although RTHs Bangkok, Tehran and Tokyo are still operating HF broadcast, the day is not far distant when HF broadcasts will disappear in Region II.
RTH Jeddah discontinued HF broadcast in 2007. DVB system via Arabsat (Ku band) is operational as from 1 January 2008 and replaces the former HF broadcast by RTH Jeddah. The broadcasting coverage covers national stations as well as neighbouring countries. The data will mainly be GTS and forecast charts.
(2) HF broadcasting systems Three RTHs (Bangkok, Teheran and Tokyo) still continue their HF radio broadcasts for mainly
ship users.
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 7
2. RMTN evolution towards AMDCNs{Proposal}
Along with Regional WIS implementation, RMTN will evolve into Area Meteorological Data Communication Networks (AMDCNs). RA II Members should consider appropriate evolution processes and procedures keeping the following principles and technical requirements in mind.
(a) Principles Individual improvement to resolve shortcomings in the current GTS must be continued
by centers concerned in cooperation with responsible RTHs. New techniques, procedures and equipments must be introduced in consideration of
operational sustainability without any interruption. Each GISC must lead strategic evolution towards AMDCNs in cooperation with DCPCs
and NCs in their responsible area. Each NC or DCPC should have a permanent connection with a principal GISC and a
connection mainly for backup with an associated GISC if possible.
(b) Technical requirements Acceptable delay-time for urgent information should be clarified in order to arrange
message routing and priority handling by Message Switching Systems at all GTS centers.
Appropriate target AMDCN bandwidths should be defined considering future-oriented data exchange of NWP, radar and satellite products and so on.
Cost-effective and secure network services should be principally used for AMDCN with supplementary use of the Internet VPN.
Future-oriented flexibility should be considered in evolutional implementation, e.g. migration from IPver4 to IPver6, and from uni-cast to multi-cast.
3. VPN Pilot Project in Regions II and VThe VPN Pilot Project in Regions II and V was launched in 2003 aiming to develop and evaluate
technologies required by WIS, particularly focusing on the Internet VPN (Virtual Private Network) technology. Australian Bureau of Meteorology, China Meteorological Administration (CMA), Hong Kong Observatory, Japan Meteorological Agency (JMA) and New Zealand MetService have led this project, and it has been run with participation of 17 NMHSs in the two Regions.
As the VPN technology itself was successfully confirmed by the project as one of promised technologies to be used in WIS, the project would now move to the next step. In March 2011, delegates from CMA and JMA met in Beijing, China and discussed the future plan of the project. Considering necessity of further development and more expertise in WIS technologies in these Regions, the both sides agreed to move the pilot project forward to the next stage by reforming it. The reformed project will focus on WIS applications in a more straightforward manner.
The new themes of the project are now under consideration. Some ideas are: Improve the web data ingest taking into account actual implementation Evaluate various methods to visualize meteorological data Review various ways to display availability of observational data based on results from WMO
monitoring software
CMA and JMA will further discuss details of the project and will proceed it in cooperation with other centres participating in the project.
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 8
{Proposal}Considering necessity of further development and more expertise in WIS technologies in the
Regions, the VPN Pilot Project in RAs II and V should be reformed focusing on WIS applications in a more straightforward manner. The Coordinator should facilitate development of the reforming plan in collaboration with the leading centres in RAs II and V.
Appendix A
Vientiane
Baghdad
Doha
Kuwait
Bahrain
Dhaka
Yangon
Kabul
Karachi
Colombo
Male
Phnom Penh
PyongYangAshgabad
Macao
256K
Dushanbe
Almaty
NI
NI
NI
Seoul
NI
NI
512K
14.4-28.8K (V.34)
4M64K
64K
1200
64K
64K
64k
Offenbach
Offenbach
CairoAlgiers
Kuala Lumpur
Tashkent
Novosibirsk
Khabarovsk
Bangkok
Washington
NI
24-19.2K (V.34)
19.2-24K (V.34)
Regional Meteorological Telecommunication Network for Region II (Asia)Current status as of 25 November 2011
Bishkek
64K
Singapore
RTH in Region II
NMC in Region II
Centre in other region
MTN circuitRegional circuitInterregional circuitAdditional circuit
Non-IP linkIP linkInternet E-mail transmission
NI No implementation
Tehran
Sanaa
Hong Kong
Moscow
NI
F/R CIR<32/32K>
Manila
Internet
Jeddah
Muscat
64K
64K
64K
Washington
ISDN 128K
64K
via Moscow
64K
64K
Thimpu
New Delhi
NI
64K
64K
64K
128K
9.6K
Ulaanbaatar
Abu-Dhabi
1200
64K
Melbourne
Melbourne
IMTNMPLS
10M64K512K
IMTNMPLS
IMTNMPLS
IMTNMPLS
IMTNMPLS
IMTNMPLS
MPLS
Internet
Internet
1M
10M
4M
10M
1M
512K
2M
1M
512K
4M
MPLS
2M
128K
MPLS
4M
Internet
Internet
Internet
Internet
Internet
Internet
Internet
Internet Internet
Internet
EUMETSAT
MPLS2M
Toulouse
Internet
64K
64K
64K
NI
Internet
Kathmandu
Internet
Internet
64K
Internet
Hanoi
128K2M
MPLS
2M
1M
MPLS
128K
2M
64KMPLS
1M
MPLS
64K64K
64K
64KMPLS MPLS
Internet8M
Toulouse
Beijing
Moscow
64K
64K
64K
InternetInternet
Internet
2M
4M
3M
IMTNMPLS
10M
1M
Tokyo
Exeter
IMTNMPLS
10M
2M
IMTNMPLS
4M
64K
4M
EUMETSAT
MPLS4M10M
RA-II/WG-IOS/WIS-1/Rep. 5.1(7), p. 2
Appendix B
Multipoint telecommunication systems in Region II
BangkokJ eddah
Tokyo
Khabarovsk
Beijing
New Delhi
Tehran
Tashkent
Novosibirsk
RTH
Fax,RTT
Fax
Fax GMS/MTSAT DCPs
multipoint systemvia satellite
radiobroadcast
CMA-FENGYUNCast(DVB, C-band)
EUMETCast(DVB,C and Ku-bands)
Members equipped with CMA-PCVSAT receivers: Bangladesh, Democratic People’s Republic of Korea,Mongolia, Myanmar and Vietnam.
Members equipped with CMA-FENGYUNCast receivers: Bangladesh, DPRK, Indonesia, Iran, “Hongkong, China”, Kyrghyz, Lao P.D.R, Malaysia, Mongolia, Myanmar, Nepal, Pakistan, Peru, Philippines, Sri Lanka, Tajikistan,Thailand, Uzbekistan, and Viet Nam.
Members equipped with Meteoinform-receivers: Kazakhstan, Kyrgyz, Tajikistan, Khabrovsk
Members equipped with INSAT-DMDD/VSAT receivers: Bangladesh, Maldives, Nepal and Sri Lanka areequipped.with INSAT DMDD receivers.
Members equipped with EUMETCast (incl. MDD) receivers: Oman (C and Ku bands), Uzbekistan
INSAT-DMDD(DVB)
Moscow
Meteoinform(DVB)
Asia Star broadcast (DAB)
Service stoppedARSAD-DVB(Ku-band) Not yet
operational
CMA-PCVSAT(Ku-band)