1 / 17

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)

petra
Download Presentation

STATUS OF RTH MOSCOW (Submitted by Expert Russian Federation)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 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 ________________________________________________________________ RTH Moscow

  2. 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 web-interface. RTH Moscow

  3. 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 RTH Moscow

  4. 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, 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 RTH Moscow

  5. GTS infrastructure RTH Moscow

  6. Current status of GTS circuits connected with RTH Moscow LS – LinkSpeed BW – BandWidth CoS – Class of Service MCS – Mission Critical Site RTH Moscow

  7. RTH Moscow

  8. RTH Moscow

  9. RTH Moscow

  10. Russian broadcast system “Meteoinform” infrastructure 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. RTH Moscow

  11. Internet infrastructure 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. GISC DCPC NC NC NC NC 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). 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 Supplier • Portal – 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. Portal Russian_GISC Other GISC (VGISC) Integration Server GISC Metadata catalogue DCPC Metadata catalogue NC Data Supplier Integration Server NC DCPC NC Data Supplier NC Data Supplier Roles: GISC – RTH Moscow DCPC – Obninsk NC Data Supplier NC 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). 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). RTH Moscow

  16. Questions? RTH Moscow

  17. Thanks for attention! RTH Moscow

More Related