Designing WIS Data Communication Structure: Approach Models, Solutions, and Smooth Evolution

1. WIS data-communications functions and services, and implementationProgress report on Expert Team on WIS-GTS Communication Techniques and Structure (ET-CTS) ICG-WIS-4 (Reading, 4-7 September 2007) Hiroyuki ICHIJO (Japan)

2. Progress Report Interim Report Final Report Recommendation Position of this report Outcome Follow-up discussion ET-CTS-1 (Tokyo, 25-28 April 2006) ICG-WIS-3 (Beijing, 5-8 September 2006) Compiling further study items ICG-WIS-4 (Reading, 4-7 September 2007) ICM-IMTN (cloud I)(October 2007) Discussion and finding solutions Contribution ICM-IMTN (cloud II, Africa)(1Q 2008) ET-WISC(4Q 2007, 1Q 2008) ICG-WIS-5 (3Q 2006) ET-CTS-2 (2Q 2008) ICT-ISS (3Q 2008) CBS-XIV (4Q 2008)

3. Design requirements Further study items I. Approach models to design for WIS data communication structure Assembling approach model Totality approach model Design principles Solutions Design principles Solutions Most feasible design

4. Site A acts as a gateway for Site G Site D acts as a gateway for Site F • Study steps are: • create a global any to any network (e.g. Global MPLS Cloud); • provide an IPVPN backup solution keeping any to any connectivity; • on top of the any to any network connection map the needed • application connection. 1. Totality approach model • Consideration points are: • how to connect with WIS participants other than NMHSs; • administrative aspects such as coordinated contract, management and governance; • iii) gateway issues such as responsibility, the expected number and technical requirement.

5. The team has been discussing design principles of individual components • based on this model so far. The reasons are: • differences between components in migration target period, feasibility and accuracy of implementation plans, the number of related centers, required specifications, design flexibility and coordination difficulties in administrative aspects; • importance and requirements of initial establishment of a WIS core network; • understandability and easiness of practical study and smooth evolution. 2. Assembling approach model • Consideration points are: • how to harmonize all components as a WIS data communication structure; • administrative aspects in each component; • iii)how to shorten long term evolution period.

6. WIS core network WIS core network #1 GISC GISC GISC GISC GISC GISC GISC GISC Internet WIS core network #2 1. Concepts for the WIS core network1.1 Backup for a WIS core network Further study Items with a high priority (1) Internet backup (2) Dual network configuration • Consideration points: • Backup control, automatic • or manual • Security requirements and sustainable level • Limitaion of backup traffic • Consideration points: • Risk avoidance by two suppliers • Cost tolerable condition • Usual traffic load balancing • Administrative and technical aspects in implementation

7. GISC NC GISC#1 Alternate GISC#2 GISC-NC connection components GTS for time-critical operational data Backup case Internet VPN Internet VPN link for near real-time products VPN VPN GTS Internet Internet access to a portal for ad hoc request/reply Internet Portal NC Team’s goal is to recommend necessary backup cases with appropriate options by alternate GISCs. Consideration points are: i) Coordination issue between GISCs but consideration from the NC view ii) Backup traffic scenarios for time-critical operational data, near real- time products and ad hoc 1.2 Backup connections with alternate GISCs Example configuration and backup case

8. Multicast-oriented network Unicast-oriented network Duplicated transmission GISC GISC GISC GISC GISC GISC GISC GISC Multicast group Responsibility Area Responsibility Area • Consideration points for contribution to ICM-IMTN meetings • i) Reviewing outcome of the ET-CTS-1 • Use of closed network cloud(s) by SLA based service • Limitation of the number of GISCs for practical reasons • Benefit of full-mesh topology in case of a small number of GISCs • ii) Data synchronization on application connections • Full-mesh or non-full-mesh with sophisticated Data GRID (e.g. SIMDAT) • Unicast or multicast-oriented architecture • Future possibility to use IPv6 multicast • iii) Current IMTN configuration of two clouds 2. Smooth evolution and migration scenario2.1 Evolution process from the Improved MTN to the WIS core network

9. Cloud I Tokyo Beijing Washington Melbourne Sofia Moscow New Delhi Prague Brasilia Exeter Buenos Aires Jeddah Offenbach Cloud II Nairobi Toulouse Cairo Dakar Algiers Current IMTN configuration

10. The team will study necessary adjustment considering the following points: i) Mapping and hierarchical design: RTH(MTN) – RTH(non-MTN) - NMC … GISC – DCPC – NC ii) Analysis of shortcomings of the current GTS 2.2 Adjustment of the current GTS configuration to WIS topology • Standardization of protocols and procedures • The team will contribute technical recommendations to regulatory • documentation. Possible contribution items are: • i) Comparison of VPN techniques • Differences between WMO standards and industrial standards • Standard VSAT Furthermore, an important aspect is the definition of the governance structures to control data flows and growth of traffic. In a new WIS core network, telecommunication becomes ubiquitous and general purpose. The telecommunication managers may not be able to see and control data flows and growth. Governance of data exchange needs to be redefined.

11. Collaboration Framework GISC Contract with SLA MoU DCPC DCPC NC Managed Network by a single provider NC NC NC NC NC NC In spite of their difficulty and sensitiveness, the following administrative items should be studied in cooperation with other teams and/or groups such as ICM-IMTN groups and the IGDDS implementation group. 4. Administrative aspects • i) Hurdles in administrative aspect of the collaboration framework by multi-nations • Adaptability to contracts on SLA and agreement on MoU • Appropriate collaboration schemes for satellite-based communication systems Example of a collaboration framework to join a common managed network service

12. Internet Closed network DCPC GISC In spite of their difficulty and sensitiveness, the following administrative items should be studied in cooperation with other teams and/or groups such as ICM-IMTN groups and the IGDDS implementation group. 5. Technical solutions of key issues5.1 Complementary Internet VPN links for overflow traffic • i) Hurdles in administrative aspect of the collaboration framework by multi-nations • Adaptability to contracts on SLA and agreement on MoU • Appropriate collaboration schemes for satellite-based communication systems 5.2 Effective load balancing on dual network configuration From a network point of view, the team has not found a firm solution on load balancinganother network. 5.3 Possible services for mobile terminal users

13. Thank you for your attention and valuable comments On behalf of ET-CTS, one of the most powerful teams