Post on 14-Jan-2016
transcript
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
________________________________________________________________
WORLD METEOROLOGICAL ORGANIZATION_________________________
COMMISSION FOR BASIC SYSTEMSOPAG 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
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 web-
interface.
Current status of RTH Moscow (1)
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
Current status of RTH Moscow (2)
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, Moscow-
Kishinev, 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
Future plans:
GTS infrastructure
DNS, MAIL, FTP, WWWServers
RTH CairoNMC KievNMC Minsk
RTH AlmatyNMC Kishinev
OBS MPLS
RTH ExeterRTH PrahaRTH SofiaRTH New DelhiRTH BeijingNMC NorrköpingNMC BucharestCisco 2800
Cisco 2600
NMC Hanoi
Cisco 2500
RTH KhabarovskRTH Novosibirsk
Cisco 2500
Dedicated circuits
Asynchronous circuit
FirewallNAT
Dedicated circuits
Dedicated circuits
Current status of GTS circuits connected with RTH Moscow
№Circuit Status Technical info Protocol Data type
Future(2009-20010)
1
Moscow –Exeter
MTN
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual accessExeter: CoS:GoldLS/BW=2M/2MMCS, Dual access
FTP WMO,Simple FTP
Messages: A/N, BIN, FAX,Files: NOAA satellite data
IP/VPN MPLS (OBS):Moscow: LS/BW=1M/1M
2
Moscow –Prague
MTN
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual accessPrague: CoS:GoldLS/BW=2M/2MEnchanced, NAS=1M
FTP WMO Messages: A/N, BIN, FAX
IP/VPN MPLS (OBS):Moscow: LS/BW=1M/1M
3
Moscow –Sofia
MTN
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KDual access, MCSSofia: CoS:GoldLS/BW=512K/512KEnchanced, NAS=128K
FTP WMO Messages: A/N, BIN, FAX
IP/VPN MPLS (OBS):Moscow: LS/BW=1M/1MSofia: LS/BW = 1M/1M
4
Moscow –New-Delhi
MTN
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual access New Delhi: CoS:GoldLS/BW=128K/128KEnchanced, NAS=128K
FTP WMO Messages: A/N, BIN
IP/VPN MPLS (OBS):Moscow: LS/BW=1M/1M
5Moscow –Cairo
MTNDigital lineTx/ Rx – 64KBackUp:No
FTP WMO Messages: A/NCairo: IP/VPN MPLS (OBS)LS/BW=64K/64K
LS – LinkSpeed BW – BandWidth CoS – Class of Service MCS – Mission Critical Site
6
Moscow –Norrkoping
RMTN
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual access Norrkoping: CoS:GoldLS/BW=4M/3MDual access, MCS
FTP WMO Messages: A/N, BIN, FAXIP/VPN MPLS (OBS):Moscow: LS/BW=1M/1M
7
Moscow –Minsk
RMTNDigital lineTx/Rx – 128K(Internet back-up)
TCP/IP-Socket(Special)
Messages: A/N, BIN, FAX,BIN-RADAR
Minsk:IP/VPN MPLS (OBS)LS/BW=256K/256KOr Digital lineTx/ Rx – 256K
8
Moscow –Kiev
RMTNDigital lineTx, Rx – 64(Internet back-up)
FTP WMOMessages: A/N, BIN, FAX,BIN-RADAR
Kiev:IP/VPN MPLS (OBS)LS/BW=128K/128KOr Digital lineTx/ Rx – 128K
9
Moscow –Tbilisi
RMTN
Telephone leased lineV.34 ITUTx/Rx – 9,6(Internet back-up)
TCP/IP-Socket(Special),Email,Web-access
Messages: A/N, FAX
Tbilisi:IP/VPN MPLS (OBS)LS/BW=64K/64KOr Digital lineTx/ Rx – 64K
10
Moscow –Baku
RMTN Through Internet
TCP/IP-Socket(Special),Email,Web-access
Messages: A/N, FAX
Baku:IP/VPN MPLS (OBS)LS/BW=64K/64KOr Digital lineTx/ Rx – 64K
11
Moscow –Erevan
RMTN
Telegraphic adapter200 bod (via Rostov)+Through Internet
AsyncEmail,Web-access
Messages: A/N, FAX
Erevan:IP/VPN MPLS (OBS)LS/BW=64K/64KOr Digital lineTx/ Rx – 64KTCP/IP-Socket orFTP WMO
12
Moscow –Kishinev
RMTN
Telephone leased lineV.34 ITUTx/ 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/64KOr Digital lineTx/ Rx – 64KTCP/IP-Socket or FTP WMO
13
Moscow –Almaty
RMTN
Telephone leased lineV.34 ITUTx, Rx –19,2K(Internet back-up)
TCP/IP-Socket(Special)
Messages: A/N, BIN, FAX,Digital lineTx/ Rx – 64K
14
Moscow –Beijing
Inter-regional
IP/VPN MPLS (OBS):Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual access Beijing: CoS:GoldLS/BW=2M/2MMCS, Dual access
FTP WMOMessages: A/N, BIN, FAX,Files: CMA and METOP Satellite
data
IP/VPN MPLS (OBS):Moscow: S/BW=1M/1M
15Moscow –Novosibirsk
Inter-regionalDigital lineTx/ Rx – 128K(Internet back-up)
TCP/IP-Socket (Special)
Messages: A/N, BIN,FAX,BIN-RADAR
Digital lineTx/ Rx – 512K
16
Moscow –Khabarovsk
Inter-regionalDigital lineTx/ Rx – 256K(Internet back-up)
TCP/IP-Socket(Special),Simple FTP
Messages: A/N, BIN, FAX,BIN-RADAR Files: Satellite images
Digital lineTx/ Rx – 512K
17
Moscow –Tashkent
Inter-regional
Telephone leased lineV.34 ITUTx/Rx –19,2K(Internet back-up)
TCP/IP-Socket(Special)
Messages: A/N, BIN, FAXDigital lineTx/ Rx – 64K
18Moscow –Hanoi
Inter-regionalSatelliteTelegraphic adapter100 bod
Async Messages: A/N
19Moscow –Tehran(NI)
Inter-regional
Telephone leased lineTCP/IP FTP WMO (A/N, BIN)
20
Moscow – Bucharest
bilateral IP/VPN MPLS (OBS):
Moscow: CoS:GoldLS/BW=512K/512KMCS, Dual access Bucharest: CoS:GoldLS/BW=2M/256KEnchanced, NAS=128K
FTP WMO Messages: A/N, BIN
IP/VPN MPLS (OBS):Moscow: LS/BW=1M/1M
21
Moscow –Melbourne
bilateral
Through Internet FTP WMO Messages: A/N, BIN IPSec VPN via Internet
22 Moscow –- Helsinki (NI)
RMTN
Cyprus
Larnaca
Sweden
Norrköping
Germany EUMETSAT
Ireland
Dublin
Serbia
Belgrade
Hungary
Budapest
Italy
Roma
Macedonia
Skopje
China
BeijingPortugal
Lisbon
Greece
Athens
Croatia
Zagreb
Austria
Vienna
Slovenia
Ljubljana
Slovakia
Bratislava
Romania
Bucharest
Czech Republic
Prague
Poland
Warszawa
Lebanon
Beirut
United Arab Emirates
Abu Dhabi
Turkey
Ankara
Saudi Arabia
J eddah
Jordan
Amman
India
New Delhi
Russia
Moscow
Spain
Madrid
France
Toulouse
Switzerland
Zurich
Belgium
Brussels
The Netherlands
De Bilt
DenmarkCopenhagen
United Kingdom
Exeter United Kingdom
ECMWFGermany
Offenbach
Iceland
Reykjavik
Norway
Oslo
Lithuania
Vilnius
Latvia
Riga
Estonia
Tallinn
Finland
Helsinki
RussiaK habarovsk
UzbekistanTashkent
RussiaNovosibirsk
Kazakhstan
Almaty
Egypt
Cairo
Iran
Tehran
Viet Nam
Hanoi
Georgia
Tbilisi
Azerbaijan
Baku
Australia
Melbourne
Armenia
Y erevan
Belarus
Minsk
Ukraine
K iev
Republic of MoldovaK ishinev
Albania
TiranaMontenegro
PodgoricaBosnia and Herzegovina
Sarajevo
Bulgaria
Sofia
Syria
Damascus
Algeria
AlgiersTunisiaTunis
Libia
Tripoli
Malta
Kenya
Nairobi
Senegal
Dakar
MoroccoCasablanca
USAWashington
Israel
Bet Dagan
Australia
Melbourne
NO
NO
NO
NI
NI
2M/2M
2M/768
NI
4M/3M
512/128
2M/2M
NO
9.6
Regional Meteorological Telecommunication Network for Region VI (Europe)Figure 1 - point-to-point circuits implementation (transmission speed in kilobit/s)
2M/2M
2M/2M
4M/3M
2M/2M
128/128
1M/1M
512/512
256/256
2M/1M
2M/2M
RTH in RA VI
NMC in RA VI
Centre in other regionMTN circuitRegional circuitInterregional circuitBilateral circuit
FR 256(CIR:64)
64
9.6
2.40.05
128
9.6
64
64
64
0.05
0.05
0.05
2.4
512/512
128/128
256/256
2M/768
2M/2M
128/128
64/64
2M/768
128/128
128/128
50M/50M
2M/768
128/128
128/128
RMDCN
64
256 128
64128
21.6
19.219.2
0.29.6
64
0.1
19.2
512/512
1M/1M
768/768
2M/2M
128/128
2M/2M
1M/768
NI
NO Not operational
Not implemented
2M/2M
768/768
NI
RTH in other region
INTERNET
NO21.6
Link speed/Band width to the RMDCN
1M/768
128/128
22 September 2008
2M/256
512/512
Greenland
Sondre Stormfjord
Luxembourg
Luxembourg
Russian broadcast system “Meteoinform” infrastructure
Internet
WAN
Cisco 2611
Cisco 2811 Helios Net
MITRA (Multi-address Information Transmission) Dispatcher
Expres AM1 Expres AM3 Expres AM11 Yamal-200
DVB-S standard channels(Digital Video Broadcasting)
MITRAUsers
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 «Ямал 201» (90Е)
Satellit «Экспресс АМ3» (140Е)
Internet infrastructure
RTH MelbourneNMC BakuNMC Tbilisi
Back-up for:RTH KhabarovskRTH NovosibirskRTH AlmatyNMC ErevanNMC MinskNMC KievNMC Kishinev
RTH Washington
2Mb Internet
10Mb
10Mb
Gloriad – Internet-2
Internet
Cisco 2611
Cisco 2811
DNS, MAIL, FTP, WWWServers
AS METEOTELECOMAS 30853DMZ
ISP3
ISP1
МSK-IX (Moscow Internet eXchange)
MMC data processing centre
FirewallNAT
10Mb
ISP2
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 interactionPicture 1 is presented the classical scheme of construction of interaction GISC - DCPC (in view of direct interaction GISC – NC).
GISCGISC
DCPC NC
NC
NC
NC
The general framework of the Russian segment of information system WMO (prototype GISC - Moscow – DCPC-Obninsk) 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 GISC-DCPC 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)
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.
Integration Server
Integration Server
Data Provider
GISCGISC
DCPC
NC
Data Provider
NC
Portal Russian_GISC
Data Provider
NC
Metadata catalogue
NC
Other GISC (VGISC)
Metadata catalogue
DCPC
NCData Provider
NC
Roles under Russian GISC prototype:GISC – RTH MoscowDCPC – Obninsk
Figure 2 - Scheme of GISC – DCPC – NC interaction on the Mediator/Wrapper model
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!