WORLD METEOROLOGICAL ORGANIZATION COMMISSION FOR BASIC SYSTEMS OPAG

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) n n n n 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 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. n 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 n

Future plans: n n • • 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

GTS infrastructure

Current status of GTS circuits connected with RTH Moscow LS – Link. Speed № Circuit BW – Band. Width MCS – Mission Critical Site Status Technical info MTN IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access Exeter: Co. S: Gold LS/BW=2 M/2 M MCS, Dual access MTN IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access Prague: Co. S: Gold LS/BW=2 M/2 M Enchanced, NAS=1 M MTN IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K Dual access, MCS Sofia: Co. S: Gold LS/BW=512 K/512 K Enchanced, NAS=128 K Moscow – New-Delhi MTN IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access New Delhi: Co. S: Gold LS/BW=128 K/128 K Enchanced, NAS=128 K FTP WMO Messages: A/N, BIN Moscow – Cairo MTN Digital line Tx/ Rx – 64 K Back. Up: No FTP WMO Messages: A/N 1 Moscow – Exeter 2 Moscow – Prague 3 Moscow – Sofia 4 5 Co. S – 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=1 M/1 M FTP WMO Messages: A/N, BIN, FAX IP/VPN MPLS (OBS): Moscow: LS/BW=1 M/1 M Sofia: LS/BW = 1 M/1 M IP/VPN MPLS (OBS): Moscow: LS/BW=1 M/1 M Cairo: IP/VPN MPLS (OBS) LS/BW=64 K/64 K

6 Moscow – Norrkoping RMTN IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access Norrkoping: Co. S: Gold LS/BW=4 M/3 M Dual access, MCS RMTN Digital line Tx/Rx – 128 K (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=1 M/1 M Messages: A/N, BIN, FAX, BIN-RADAR Minsk: IP/VPN MPLS (OBS) LS/BW=256 K/256 K Or Digital line Tx/ Rx – 256 K Messages: A/N, BIN, FAX, BIN-RADAR Kiev: IP/VPN MPLS (OBS) LS/BW=128 K/128 K Or Digital line Tx/ Rx – 128 K Messages: A/N, FAX Tbilisi: IP/VPN MPLS (OBS) LS/BW=64 K/64 K Or Digital line Tx/ Rx – 64 K Messages: A/N, FAX Baku: IP/VPN MPLS (OBS) LS/BW=64 K/64 K Or Digital line Tx/ Rx – 64 K Messages: A/N, FAX Erevan: IP/VPN MPLS (OBS) LS/BW=64 K/64 K Or Digital line Tx/ Rx – 64 K 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. 6 K (Internet back-up) TCP/IP-Socket (Special) Web-access Messages: A/N, FAX, BIN-RADAR Kishinev: IP/VPN MPLS (OBS) LS/BW=64 K/64 K Or Digital line Tx/ Rx – 64 K TCP/IP-Socket or FTP WMO RMTN Telephone leased line V. 34 ITU Tx, Rx – 19, 2 K (Internet back-up) TCP/IP-Socket (Special) Messages: A/N, BIN, FAX, Digital line Tx/ Rx – 64 K Moscow – Beijing Inter-regional IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access Beijing: Co. S: Gold LS/BW=2 M/2 M MCS, Dual access FTP WMO Messages: A/N, BIN, FAX, Files: CMA and METOP Satellite data Moscow – Novosibirsk Inter-regional Digital line Tx/ Rx – 128 K (Internet back-up) TCP/IP-Socket (Special) Messages: A/N, BIN, FAX, BIN-RADAR Digital line Tx/ Rx – 512 K Moscow – Khabarovsk Inter-regional Digital line Tx/ Rx – 256 K (Internet back-up) TCP/IP-Socket (Special), Simple FTP Messages: A/N, BIN, FAX, BIN-RADAR Files: Satellite images Digital line Tx/ Rx – 512 K Moscow – Tashkent Inter-regional Telephone leased line V. 34 ITU Tx/Rx – 19, 2 K (Internet back-up) TCP/IP-Socket (Special) Messages: A/N, BIN, FAX Digital line Tx/ Rx – 64 K Moscow – Hanoi Inter-regional Satellite Telegraphic adapter 100 bod Async Messages: A/N Moscow – Kishinev 13 Moscow – Almaty 14 15 16 17 18 IP/VPN MPLS (OBS): Moscow: S/BW=1 M/1 M

19 Moscow – Tehran (NI) 20 bilateral Moscow – Bucharest 21 IP/VPN MPLS (OBS): Moscow: LS/BW=1 M/1 M IP/VPN MPLS (OBS): Moscow: Co. S: Gold LS/BW=512 K/512 K MCS, Dual access Bucharest: Co. S: Gold LS/BW=2 M/256 K Enchanced, NAS=128 K FTP WMO Messages: A/N, BIN Through Internet FTP WMO Messages: A/N, BIN bilateral Moscow – Melbourne 22 Telephone leased line TCP/IP FTP WMO (A/N, BIN) Interregiona l Moscow – - Helsinki (NI) RMTN IPSec VPN via Internet

Russian broadcast system “Meteoinform” infrastructure The broadcasting is carried out in the C-band through 4 Russian satellites (Expres AM 1, Expres AM 3, Expres AM 11 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 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 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, E 2 E) technology and providing E 2 E 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 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!