Transcript WORLD METEOROLOGICAL ORGANIZATION _________________________ COMMISSION FOR BASIC SYSTEMS OPAG ON INFORMATION SYSTEMS & SERVICES JOINT IMPLEMENTATION-COORDINATION MEETING ON THE GTS-WIS MTN AND MEETING OF THE.

WORLD METEOROLOGICAL ORGANIZATION
_________________________
COMMISSION FOR BASIC SYSTEMS
OPAG ON INFORMATION SYSTEMS & SERVICES
JOINT IMPLEMENTATION-COORDINATION MEETING
ON THE GTS-WIS MTN AND MEETING OF THE CBS
EXPERT TEAM ON GTS_WIS OPERATIONS AND
IMPLEMENTATION (ET-OI)
GENEVA, 23 - 26 SEPTEMBER 2008
ISS/ICM-MTN&ET-OI 2008/Doc. 2.11
(--.IX.2006)
ENGLISH only
STATUS OF RTH MOSCOW
(Submitted by Expert (Russian Federation))
________________________________________________________________
Summary and Purpose of Document
This document includes the report on the status of implementation of
telecommunication centre and circuits at RTH Moscow
________________________________________________________________
Current status of RTH Moscow (1)







Message Switching System in RTH Moscow was replaced in
2000. It consists of two sub-systems: operational and standby.
MSS network software is based on TCP/IP procedures.
In addition, there are a limited number of asynchronous connections.
Russian broadcast system “Meteoinform” is also integrated to
the system.
TCP/IP Socket (Special) and FTP/WMO: are the basic data
exchange protocol used.
E-Mail: Messages can be received or transmitted via e-mail.
WWW: A/N messages and FAX charts can be received via webinterface.
Current status of RTH Moscow (2)
Links of RMDCN OBS/Equant (Exeter, Prague, Sofia, Norrkoping,
Beijing, New-Delhi, Bucharest) were migrated from F/R to IPVPN
MPLS network in June 2007 with success.
 Bandwidth of some links were extended during 2007-2008:
- RTH Novosibirsk up to 128 Kbps
- RTH Khabarovsk up to 256 Kbps
- NMC Minsk up to 128 Kbps

Future plans:




•
•
•
•
Establish backup connection to RTH Melbourn and RTH Sofia
through Internet VPN
Upgrade the B/W of RMDCN access circuit up to 1 Mbps
Migrate Moscow-Tbilisi, Moscow-Baku, Moscow-Erevan, MoscowKishinev, Moscow-Almaty links to RMDCN or establish digital lines
with these NMCs.
Upgrade next circuits:
Moscow-Khabarovsk up to 512 Kbps
Moscow-Novosibirsk up to 512 Kbps
Moscow-Minsk up to 256 Kbps
Moscow-Kiev up to 128 Kbps
GTS infrastructure
OBS MPLS
DNS, MAIL, FTP, WWW
Servers
Cisco 2800
Firewall
NAT
Dedicated circuits
RTH Exeter
RTH Praha
RTH Sofia
RTH New Delhi
RTH Beijing
NMC Norrköping
NMC Bucharest
RTH Cairo
NMC Kiev
NMC Minsk
Cisco 2600
RTH Khabarovsk
RTH Novosibirsk
Dedicated circuits
Cisco 2500
RTH Almaty
NMC Kishinev
Cisco 2500
Dedicated circuits
NMC Hanoi
Asynchronous circuit
Current status of GTS circuits connected with RTH Moscow
LS – LinkSpeed
№
Circuit
BW – BandWidth
MCS – Mission Critical Site
Status
Technical info
MTN
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
Exeter: CoS:Gold
LS/BW=2M/2M
MCS, Dual access
MTN
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
Prague: CoS:Gold
LS/BW=2M/2M
Enchanced, NAS=1M
MTN
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
Dual access, MCS
Sofia: CoS:Gold
LS/BW=512K/512K
Enchanced, NAS=128K
Moscow –
New-Delhi
MTN
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
New Delhi: CoS:Gold
LS/BW=128K/128K
Enchanced, NAS=128K
FTP WMO
Messages: A/N, BIN
Moscow –
Cairo
MTN
Digital line
Tx/ Rx – 64K
BackUp:No
FTP WMO
Messages: A/N
1
Moscow –
Exeter
2
Moscow –
Prague
3
Moscow –
Sofia
4
5
CoS – Class of Service
Protocol
FTP WMO,
Simple FTP
Data type
Messages: A/N, BIN, FAX,
Files: NOAA satellite data
Future
(2009-20010)
IP/VPN MPLS (OBS):
Moscow:
LS/BW=1M/1M
IP/VPN MPLS (OBS):
Moscow:
LS/BW=1M/1M
FTP WMO
FTP WMO
Messages: A/N, BIN, FAX
Messages: A/N, BIN, FAX
IP/VPN MPLS (OBS):
Moscow:
LS/BW=1M/1M
Sofia: LS/BW = 1M/1M
IP/VPN MPLS (OBS):
Moscow:
LS/BW=1M/1M
Cairo:
IP/VPN MPLS (OBS)
LS/BW=64K/64K
6
Moscow –
Norrkoping
RMTN
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
Norrkoping: CoS:Gold
LS/BW=4M/3M
Dual access, MCS
RMTN
Digital line
Tx/Rx – 128K
(Internet back-up)
RMTN
Digital line
Tx, Rx – 64
(Internet back-up)
FTP WMO
RMTN
Telephone leased line
V.34 ITU
Tx/Rx – 9,6
(Internet back-up)
TCP/IP-Socket
(Special),
Email,
Web-access
Through Internet
TCP/IP-Socket
(Special),
Email,
Web-access
FTP WMO
Messages: A/N, BIN, FAX
IP/VPN MPLS (OBS):
Moscow:
LS/BW=1M/1M
Messages: A/N, BIN, FAX,
BIN-RADAR
Minsk:
IP/VPN MPLS (OBS)
LS/BW=256K/256K
Or Digital line
Tx/ Rx – 256K
Messages: A/N, BIN, FAX,
BIN-RADAR
Kiev:
IP/VPN MPLS (OBS)
LS/BW=128K/128K
Or Digital line
Tx/ Rx – 128K
Messages: A/N, FAX
Tbilisi:
IP/VPN MPLS (OBS)
LS/BW=64K/64K
Or Digital line
Tx/ Rx – 64K
Messages: A/N, FAX
Baku:
IP/VPN MPLS (OBS)
LS/BW=64K/64K
Or Digital line
Tx/ Rx – 64K
Messages: A/N, FAX
Erevan:
IP/VPN MPLS (OBS)
LS/BW=64K/64K
Or Digital line
Tx/ Rx – 64K
TCP/IP-Socket or
FTP WMO
7
Moscow –
Minsk
TCP/IP-Socket
(Special)
8
Moscow –
Kiev
9
Moscow –
Tbilisi
10
Moscow –
Baku
RMTN
11
Moscow –
Erevan
RMTN
Telegraphic adapter
200 bod (via Rostov)
+
Through Internet
Async
Email,
Web-access
12
RMTN
Telephone leased line
V.34 ITU
Tx/ Rx – 21.6K
(Internet back-up)
TCP/IP-Socket
(Special)
Web-access
Messages: A/N, FAX,
BIN-RADAR
Kishinev:
IP/VPN MPLS (OBS)
LS/BW=64K/64K
Or Digital line
Tx/ Rx – 64K
TCP/IP-Socket or
FTP WMO
RMTN
Telephone leased line
V.34 ITU
Tx, Rx –19,2K
(Internet back-up)
TCP/IP-Socket
(Special)
Messages: A/N, BIN, FAX,
Digital line
Tx/ Rx – 64K
Moscow –
Beijing
Inter-regional
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
Beijing: CoS:Gold
LS/BW=2M/2M
MCS, Dual access
FTP WMO
Messages: A/N, BIN, FAX,
Files: CMA and METOP Satellite
data
Moscow –
Novosibirsk
Inter-regional
Digital line
Tx/ Rx – 128K
(Internet back-up)
TCP/IP-Socket
(Special)
Messages: A/N, BIN,FAX,
BIN-RADAR
Digital line
Tx/ Rx – 512K
Moscow –
Khabarovsk
Inter-regional
Digital line
Tx/ Rx – 256K
(Internet back-up)
TCP/IP-Socket
(Special),
Simple FTP
Messages: A/N, BIN, FAX,
BIN-RADAR
Files: Satellite images
Digital line
Tx/ Rx – 512K
Moscow –
Tashkent
Inter-regional
Telephone leased line
V.34 ITU
Tx/Rx –19,2K
(Internet back-up)
TCP/IP-Socket
(Special)
Messages: A/N, BIN, FAX
Digital line
Tx/ Rx – 64K
Moscow –
Hanoi
Inter-regional
Satellite
Telegraphic adapter
100 bod
Async
Messages: A/N
Moscow –
Kishinev
13
Moscow –
Almaty
14
15
IP/VPN MPLS (OBS):
Moscow: S/BW=1M/1M
16
17
18
19
Moscow –
Tehran
(NI)
20
bilatera
l
Moscow –
Bucharest
21
Moscow –
Melbourne
22
Moscow –
- Helsinki
(NI)
Telephone leased
line
TCP/IP FTP WMO
(A/N, BIN)
Interregiona
l
bilatera
l
RMTN
IP/VPN MPLS
(OBS):
Moscow:
LS/BW=1M/1M
IP/VPN MPLS (OBS):
Moscow: CoS:Gold
LS/BW=512K/512K
MCS, Dual access
Bucharest: CoS:Gold
LS/BW=2M/256K
Enchanced, NAS=128K
FTP WMO
Messages: A/N, BIN
Through Internet
FTP WMO
Messages: A/N, BIN
IPSec VPN via
Internet
NI
RTH in RA VI
Finland
RTH in other region
NI
Estonia
Latvia
Riga
Oslo
Sondre
Stormfjord
FR 256
(CIR:64)
Bet Dagan
9.6
ECMWF
2.4
Spain
Dakar
Kenya
0.05
128
9.6
Nairobi
64
Algeria
64
Algiers
Tunisia
Tunis
Libia
2M/1M
128/128
Madrid
1M/768
2M/2M
2M/768
128/128
128/128
Zurich
4M/3M
128/128
0.05
Tripoli
0.05
Malta
2.4
The Netherlands
2M/768
128/128
Portugal
768/768
2M/2M
Lisbon
Italy
Roma
2M/2M
Slovenia
RMDCN
Kishinev
Uzbekistan
0.2
Almaty
Armenia
Yerevan
Georgia
Tbilisi
64
Egypt
Cairo
9.6
Viet Nam
Hanoi
NI
Iran
Serbia
Tehran
Macedonia
Melbourne
Belgrade
Australia
Skopje
NO
Azerbaijan
Baku
Turkey
Ankara
INTERNET
Bulgaria
Sofia
Tirana
Podgorica
Athens
Beirut
Albania
Montenegro
Greece
Lebanon
NO
Kazakhstan
0.1
Bosnia and Herzegovina
Sarajevo
21.6
NO
NO
India
New Delhi
United Arab Emirates
NI
Abu Dhabi
Cyprus
Larnaca
Jordan
Amman
512/128
Minsk
Tashkent
Prague
Ljubljana
512/512
2M/2M
Toulouse
0.05
19.2
9.6
Vienna
Belarus
Republic of Moldova
19.2
Budapest
256/256
768/768
50M/50M
Switzerland
De Bilt
21.6
Moscow
Zagreb
128/128
2M/2M
2M/2M
France
Bucharest
512/512
512/512
2M/2M
Belgium
Brussels
Kiev
128
Croatia
Germany
Offenbach
Casablanca
64
Exeter
Romania
Austria
2M/2M
64
Senegal
2M/2M
2M/2M
Russia
Khabarovsk
Russia
Novosibirsk
Ukraine
64
Czech Republic
Dublin
United Kingdom
128
Hungary
1M/1M
United Kingdom
Israel
Morocco
512/512
128/128
Denmark
Copenhagen
EUMETSAT
Warszawa
Russia
128/128
1M/1M
Germany
Australia
64
64/64
Iceland
Reykjavik
Greenland
USA
2M/256
Norway
Ireland
Washington
2M/768
Lithuania
Vilnius
256
Poland
128/128
Tallinn
Link speed/Band width
to the RMDCN
Not implemented
Not operational
Melbourne
256/256
4M/3M
Helsinki
Centre in other region
MTN circuit
Regional circuit
Interregional circuit
Bilateral circuit
NO
Bratislava
Norrköping
NMC in RA VI
1M/768
19.2
Slovakia
Sweden
China
NI
Syria
Damascus
Beijing
Saudi Arabia
Jeddah
2M/768
Luxembourg
Luxembourg
Regional Meteorological Telecommunication Network for Region VI (Europe)
Figure 1 - point-to-point circuits implementation (transmission speed in kilobit/s)
22 September 2008
NO
Russian broadcast system “Meteoinform” infrastructure
Expres AM1
Expres AM3
Expres AM11
Yamal-200
DVB-S standard channels
(Digital Video Broadcasting)
MITRA
Users
MITRA
(Multi-address Information
Transmission) Dispatcher
Internet
Cisco 2811
Helios Net
WAN
Cisco 2611
The broadcasting 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.
Cover zone operating of system "Meteoinform"
Satellit «Экспресс АМ1» (40Е)
Satellit «Экспресс А2» (103Е)
Satellit «Экспресс АМ3» (140Е)
Satellit «Ямал 201» (90Е)
Internet infrastructure
RTH Washington
AS METEOTELECOM
AS 30853
DMZ
10Mb
10Mb
ISP1
DNS, MAIL, FTP, WWW
Servers
Cisco 2611
ISP2
10Mb
Gloriad –
Internet-2
Internet
МSK-IX (Moscow
Internet eXchange)
RTH Melbourne
NMC Baku
NMC Tbilisi
MMC data processing centre
ISP3
Firewall
NAT
2Mb
Cisco 2811
Internet
Back-up for:
RTH Khabarovsk
RTH Novosibirsk
RTH Almaty
NMC Erevan
NMC Minsk
NMC Kiev
NMC Kishinev
There are three connections to Internet via three different Internet Service
Providers for exchanging the operational data and collecting NCEP products
from RTH Washington.
The general technical decisions on development of the Russian
GISC/DCPC prototype
In 2008 the tender for the research work including as one a problem, construction
of the prototype Russian GISC is declared.
The general architecture and interaction
Picture 1 is presented the classical scheme of construction of interaction GISC DCPC (in view of direct interaction GISC – NC).
GISC
DCPC
N
C
N
C
N
C
N
C
The general framework of the Russian
segment of information system WMO
(prototype GISC - Moscow – DCPCObninsk) is supposed to build on the
basis of solutions of (End-to-end, E2E)
technology and providing E2E
development for maintenance of full
standards and functionality according
to WIS Technical specifications.
The general technical decisions on development of the Russian
GISC/DCPC prototype (1)
The architectural approach on the basis of client-server technology with
«mediator/wrapper» mechanism is used:
 mediator is a software which, on the one hand, cooperates with the users of
integrating system, and, on the other hand, with the removed data sources;
 wrapper (or the adapter) is the intermediary between mediator and local system
of data. The wrapper carries out functions of a data source.
With regard for the approach indicated the main components of the Russian GISCDCPC prototype are the follows:
 Portal – registration of the users, data/products search using the system
metadata catalogue, data visualization or saving on user computer
 Integration Server (mediator) – metadata management (accumulation,
harvesting, synchronization, etc.), access/upload the DCPC (NC) metadata and
data via Data Provider software
 Data Provider (adapter) – local data registration, metadata generation, provision
of access to data
The general technical decisions on development of the Russian
GISC/DCPC prototype (2)
Portal Russian_GISC
Other GISC (VGISC)
Integration Server
GISC
Metadata catalogue
DCPC
Metadata
catalogue
NC
Data Provider
Integration Server
NC
DCPC
NC
Data Provider
NC
Data Provider
Data Provider
NC
NC
Roles under Russian GISC
prototype:
GISC – RTH Moscow
DCPC – Obninsk
Figure 2 - Scheme of GISC – DCPC – NC
interaction on the Mediator/Wrapper model
And:
It is planned to use:
1) Integration Server at GISC
level for interaction with DCPC
(NС) and others GISC, and at
DCPC level for interaction with NC
and GISC;
2) Data Provider at DCPC(NC)
centers;
Data Provider will have two
version:
1)“full” – connection with local data
and generation of metadata
automatically;
2)“light” – remote registration data
source and interaction with
Integration Server. Under this
version the DCPC(NC) generates
the metadata by own software as
proposed canonical WIS
framework.
The general technical decisions on development of the Russian
GISC/DCPC prototype (3)
The Data Provider (NC level) is intended for interaction with local data
systems of NC, placed in the organizations – participants of Russian GISC.
The Integration Server at GISC level is responsible for DCPC/NC metadata
management and data acquisition from DCPC/NC and transfer to their
external users (GISC Portal). The Integration Server at DCPC level carries
out similar functions concerning NC’s of zone of the DCPC responsibility. The
GISC Portal realizes a single-enter in the integrated system, search and data
presentation.
Functionality of the prototype, as a whole, will meet the Technical
Specifications of WIS (special actions for check are planned):
 registration of users (the Portal + the Integration Server);
 search of data through metadata base (the Portal + the Integration Serve);
 accumulation and synchronization of metadata, realization of
request/response, sample and delivery of data (the Integration Server + the
Data Provider);
 local metadata updating (the Data Provider).
Questions?
Thanks for attention!