RTH Moscow 1 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 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 (12.IX.2008) ENGLISH only
17
Embed
STATUS OF RTH MOSCOW (Submitted by Expert Russian Federation)
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) - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
RTH Moscow 1
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 (12.IX.2008)
ENGLISH only
RTH Moscow 2
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)
RTH Moscow 3
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)
RTH Moscow 4
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:
RTH Moscow 5
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
RTH Moscow 6
Current status of GTS circuits connected with RTH Moscow
Through Internet FTP WMO Messages: A/N, BIN IPSec VPN via Internet
22 Moscow –- Helsinki (NI)
RMTN
RTH Moscow 10
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.
There are three connections to Internet via three different Internet Service Providers for exchanging the operational data and collecting NCEP products from RTH Washington.
RTH Moscow 12
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.
RTH Moscow 13
The general technical decisions on development of the Russian GISC/DCPC prototype (1)
The architectural approach on the basis of client-server technology with use «mediators» is used: mediator is a software which, on the one hand, cooperates with the user of integrating system, and, on the other hand, with the removed data sources; the 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:Integration Server (mediator) – metadata management (accumulation, synchronization, etc.) and access to metadata and DCPC (NC) data via Data SupplierPortal – registration of the users, data/products research (then to data) using the system metadata catalogue Data Supplier (adapter) – support of data source – local data registration, metadata registration and provision of access to data
RTH Moscow 14
The general technical decisions on development of the Russian GISC/DCPC prototype (2)
And:1) it is provided the use of Integration Server as at GISC level GISC for interaction with DCPC (NС) and others GISC, and at DCPC level for interaction with NC and GISC;2) As the adapter are considered:Data Provider software of E2E technology, which is installed at DCPC(NC) centers; Own DCPC (NC) software tools which provides the metadata generation and their presentation for harvesting by GISC (DCPC).
Integration Server
Integration Server
Data Supplier
GISCGISC
DCPC
NC
Data Supplier
NC
Portal Russian_GISC
Data Supplier
NC
Metadata catalogue
NC
Other GISC (VGISC)
Metadata catalogue
DCPC
NCData Supplier
NC
Roles:GISC – RTH MoscowDCPC – Obninsk
Figure 2 - Scheme of GISC – DCPC interaction on the basis of the media even integration
RTH Moscow 15
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 responsibility of it DCPC. The portal realizes a single-enter in the integrated system, search and data presentation.
Functionality of the prototype, as a whole, meets 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); metadata updating (the Supplier of Data).