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, SEPTEMBER 2008 ISS/ICM-MTN&ET-OI 2008/Doc (--.IX.2006) ENGLISH only

Message Switching System in RTH Moscow was replaced in 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. Messages can be received or transmitted via . 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 : - 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

Current status of GTS circuits connected with RTH Moscow № CircuitStatusTechnical infoProtocolData type Future ( ) 1 Moscow – Exeter 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 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:Gold LS/BW=512K/512K MCS, Dual access Prague: CoS:Gold LS/BW=2M/2M Enchanced, NAS=1M FTP WMOMessages: A/N, BIN, FAX IP/VPN MPLS (OBS): Moscow: LS/BW=1M/1M 3 Moscow – Sofia 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 FTP WMOMessages: A/N, BIN, FAX IP/VPN MPLS (OBS): Moscow: LS/BW=1M/1M Sofia: LS/BW = 1M/1M 4 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 WMOMessages: A/N, BIN IP/VPN MPLS (OBS): Moscow: LS/BW=1M/1M 5 Moscow – Cairo MTN Digital line Tx/ Rx – 64K BackUp:No FTP WMOMessages: A/N Cairo: 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:Gold LS/BW=512K/512K MCS, Dual access Norrkoping: CoS:Gold LS/BW=4M/3M Dual access, MCS FTP WMOMessages: A/N, BIN, FAX IP/VPN MPLS (OBS): Moscow: LS/BW=1M/1M 7 Moscow – Minsk RMTN Digital line Tx/Rx – 128K (Internet back-up) TCP/IP-Socket (Special) Messages: A/N, BIN, FAX, BIN-RADAR Minsk: IP/VPN MPLS (OBS) LS/BW=256K/256K Or Digital line Tx/ Rx – 256K 8 Moscow – Kiev RMTN Digital line Tx, Rx – 64 (Internet back-up) FTP WMO Messages: A/N, BIN, FAX, BIN-RADAR Kiev: IP/VPN MPLS (OBS) LS/BW=128K/128K Or Digital line Tx/ Rx – 128K 9 Moscow – Tbilisi RMTN Telephone leased line V.34 ITU Tx/Rx – 9,6 (Internet back-up) TCP/IP-Socket (Special), , Web-access Messages: A/N, FAX Tbilisi: IP/VPN MPLS (OBS) LS/BW=64K/64K Or Digital line Tx/ Rx – 64K 10 Moscow – Baku RMTNThrough Internet TCP/IP-Socket (Special), , Web-access Messages: A/N, FAX Baku: IP/VPN MPLS (OBS) LS/BW=64K/64K Or Digital line Tx/ Rx – 64K 11 Moscow – Erevan RMTN Telegraphic adapter 200 bod (via Rostov) + Through Internet Async , Web-access 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

12 Moscow – Kishinev 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 13 Moscow – Almaty 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 14 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 IP/VPN MPLS (OBS): Moscow: S/BW=1M/1M 15 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 16 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 17 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 18 Moscow – Hanoi Inter-regional Satellite Telegraphic adapter 100 bod AsyncMessages: A/N

19 Moscow – Tehran (NI) Inter- regiona l Telephone leased line TCP/IP FTP WMO (A/N, BIN) 20 Moscow – Bucharest bilatera l 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 WMOMessages: A/N, BIN IP/VPN MPLS (OBS): Moscow: LS/BW=1M/1M 21 Moscow – Melbourne bilatera l Through InternetFTP WMOMessages: A/N, BIN IPSec VPN via Internet 22 Moscow – - Helsinki (NI) RMTN

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.

Cover zone operating of system "Meteoinform" Satellit «Экспресс АМ1» (40Е) Satellit «Экспресс А2» (103Е)Satellit «Ямал 201» (90Е) Satellit «Экспресс АМ3» (140Е)

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.

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 NCNC NCNC NCNC NCNC 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 Data Provider GISC DCPC NC Data Provider NC Portal Russian_GISC Data Provider NC Metadata catalogue NC Other GISC (VGISC) Metadata catalogue DCPC NC Data Provider NC Roles under Russian GISC prototype: GISC – RTH Moscow DCPC – 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!