100 likes | 105 Views
Learn about data communication requirements and services of WIS/GTS, IGDDS, DAR, and more presented by Jean-François Gagnon from Environment Canada. Get details on implementation methods and future milestones. Understand key technical specifications, organization principles, and design considerations for the WIS data communication structure.
E N D
Debriefing on WIS Aspects Discussionsfrom the ICM IMTN Cloud 1 (Washington Nov 2007) Jean-François Gagnon Telecommunications and Security Division Information Technology Infrastructure Chief Information Officer Branch Environment Canada jean-francois.gagnon@ec.gc.ca ET-CTS Toulouse
WIS-GTS data communication structure and requirements on MTN • Presented by Jean-Michel Rainer • Presentation available in documents • Following 5 slides are reproduced from the presentation ET-CTS Toulouse
WIS Vision ET-CTS Toulouse
Data pull Data push WIS DATA-COMMUNICATIONS FUNCTIONS AND SERVICES(for weather, water, climate and related data and products) DAR WIS IGDDS GTS WIS/GTS: for time and operation-critical data & products WIS/IGDDS: for space-based data & products WIS/DAR: data discovery, access and retrieval Data push: routine distribution of data & products Data pull: access to and retrieval of data & products ET-CTS Toulouse
Data pull Data push WIS DATA-COMMUNICATIONS IMPLEMENTATION(for weather, water, climate and related data and products) DAR Essentially through the Internet(HTTP, FTP, VPN…) Essentially through telecom. with guaranteed quality of service, e.g. leased circuits, dedicated data com network services, sat.-based systems, .. WIS Essentially through satellite based data distribution systems, e.g. DVB-S IGDDS GTS WIS/GTS: for time and operation-critical data & products WIS/IGDDS: for space-based data & products WIS/DAR: data discovery, access and retrieval Data push: routine distribution of data & products Data pull: access to and retrieval of data & products ET-CTS Toulouse
IGDDS within the WIS LEO satellites Global data (recorded/dumped) GEO satellites in the region R&D satellites Polar orbiting satellites Network of HRPT stations RARS Satellite products Local processing Local processing Local processing Central processing Central processing Regional processing GISC (Data, metadata and user management) Interoperability DCPC Data, metadata & user management Data exchange with other DCPCs Routine Dissemination Request/ reply (Internet) Request/ reply (Internet) ADM Other media National centres and other users ET-CTS Toulouse
WIS Data Policies • Complies with WMO data policies • Res. 40 (Cg-XII) and Res. 25 (Cg-XIII) • Will follow evolution of WMO data policy • Procedures for managing of access rights, control of data retrieval, registration and identification of users, etc can be defined, as and when required • Anonymous downloading is technically possible, but depends on whether a NC permits that feature • Has no system-inherent features that would violate international legal frameworks ET-CTS Toulouse
Key Future Milestones • Consolidate plans on development, governance and implementation of WIS: 2007-2008 • Develop WIS regulatory documentation and guidance material for implementation, including specifications for the GISC interfaces and a unified user interface: 2007-2008 • Develop scheme and practices for security, authentication and authorization procedures for WIS services : 2007-2008 • Implementation of first operational GISC: 2008 • Implementation of other operational GISCs: 2009 - 2011 • Implementation of DCPCs, i.e. WIS interfaces at WMO programmes’ centres: 2008-2011 ET-CTS Toulouse
WIS Technical Specifications • Chris Eliott • Specifications will be used for GISC, DCPC & NC certification • Focus moves from “communications centric” to “data management” • ICG-WIS is accountable for technical specifications • SIMDAT is included, but is not the only solution ET-CTS Toulouse
Organization and Design Principles for the WIS Data Communication Structure • Presented by jfg for Hiroyuki Ichijo • Revised version of this paper to be discussed in Toulouse • Comments gathered in Washington: • 1 or 2 (or many) clouds: • Need to better describe the need and the interaction of 1 or 2 clouds • Propose one specific solution as the design, or • use generic terms to describe an architecture. • Backup (redundancy): • Finalize decision on • Using separate dedicated network, or • Using Internet • Design of connectivity in backup network should match connectivity in main network • For example full mesh versus not full mesh • Is integrity requirement same for all datasets? • In general: • streamline and simplify document as much as possible • Ensure design principles are in coherent with the decisions surrounding the future of IMTN Cloud 1 (as currently under discussion) ET-CTS Toulouse