ACSICG/3 IP/16 Agenda Item 6 12/05/16. MG II Technical Messaging Overview

Size: px

Start display at page:

Download "ACSICG/3 IP/16 Agenda Item 6 12/05/16. MG II Technical Messaging Overview"

Melvin Jenkins
5 years ago
Views:

1 ACSICG/3 IP/16 Agenda Item 6 12/05/16 MG II Technical Messaging Overview

2 GEMS Agenda Global Concept Review Mini Global GEMS Architecture Lessons Learned 2

3 Global Coordination Seamless information exchange across Flight Information Regions (FIRs) is essential for operators and Air Navigation Service Providers (ANSPs) Global Interoperability is a major component of ICAO's future roadmap

4 Mini Global ASBU Connection Mini Global supports Global Air Navigation Plan (GANP) and Aviation System Block Upgrades (ASBUs) goals

5 Mini Global Enterprise Messaging Harris GEMS Mosaic GEMS Global Enterprise Messaging Services Indra GEMS NEC GEMS 5

6 Current Architecture

7 ICAO Concept Architecture 7

8 GEMS MG II Architecture Common GEMS Standard Service by Harris A P A P Service by Indra FAA User 2 User 3 FAA (NEMS) User 4 User 5 User 6 Region A Service by Mosaic ATM A P Local Standard Flight Weather Aeronautical A P Region B Service by NEC User 7 User 8 User 9 User 10 User 11 User 12 Region C Region D

9 Policy Enforcement Service by Harris Service by Indra User 1 User 2 User 3 GEMS User 4 User 5 User 6 Local Common Service by Mosaic ATM Regional Service by NEC User 7 User 8 User 9 User 10 User 11 User 12 9

10 Lessons Learned Open standards provide flexibility for GEMS Service Providers Governance must be handled by GEMS Providers in unison and in a flexible manner A common security model must be implemented by GEMS Providers Mediation is core to the success of Global

11 GEMS Working Group Charter Include technical experts from each GEMS Service Provider Ensure seamless end-to-end connectivity for Mini Global participants Use common, open standard messaging protocol(s) Develop data sharing agreements amongst the data providers Enforcing governance policies across multiple EMS

12 GEMS Working Group Topics General Agree on definition of EMS What are the minimum requirements for a GEMS provider? How will participant become aware of existing data sources / services connected to the GEMS? Governance What is the process for generating governance rules and policies? How will governance rules and policies be communicated, enforced and monitored over a distributed EMS to EMS architecture? Validation Where should validation of standards take place? What is the process for non-valid messages / data elements? Routing What metadata requirements are required to ensure proper message routing? What is the process for defining and maintaining a common message definition (ICAO Doc 4444 ATS messages) Security What are the components of security which will be enforced by EMS (integrity, authentication, authorization, nonrepudiation, etc.)?

13 Data Sharing Agreements Participants define sensitive data elements in System Description Document Users request access to sensitive data elements through GEMS Service Provider Primary GEMS service provider converts the declaration of sensitive data elements / approved user needs into GEMS system configuration Primary GEMS notify other GEMS service providers of configuration 13

Global Enterprise Message Service (Governance, Validation, Security, and Routing) A P Common

14 GEMS Mediation Example GEMS Adaptor GEMS Adaptor JMS (Metadata) AMQP (Metadata) AMQP (Metadata) STOMP (Metadata) JMS (Body) AMQP (Body) AMQP (Body) STOMP (Body) GEMS Provider A GEMS Provider B Global Enterprise Message Service (Governance, Validation, Security, and Routing) A P Common Messaging A P Global Enterprise Message Service (Governance, Validation, Security, and Routing) Source Consumer 14

15 Validation GEMS Validation GEMS Service Providers ensure messages published by data sources adhere to messaging and metadata standards Non-valid message are not routed to their destination Data Governance Module (DGM) Validation All messages published over the GEMS Service Providers are sent to the DGM DGM ensures message content adheres to international data standards (AIXM, WXXM, FIXM)

16 Routing GEMS Service Providers are responsible for: Ensuring information routes from each data source to the correct destination Enforcing data sharing agreements Adhering to standard for GEMS Message Metadata

17 GEMS Metadata Standard Example Header Name Values Descriptions SBI Service by Indra GEMS_EMS SBM Service by Mosaic SBH Service by Harris SBC Service by Canada FAA Federal Aviation Administration SBM_FO Mosaic_FO SBM_AW AIXM, iwxxm, WXXM SBM_OTHER Conflict reporting and other legacy messages SBH_OTHER Other legacy messages NAVP NAV Portugal AGENCY US Government other than FAA AEROTHAI Aero Thai GEMS_SOURCE ASA Air services Australia CAAS Singapore JCAB Japan NAVCANADA NAVCanada ROK Republic of Korea BRAZIL National Civil Aviation Agency (ANAC) TRINIDAD_TOBAGO Trinidad and Tobago HARRIS Harris Test System NCB FAA Network Communications Branch 17

18 Security Example GEMS Req/Reply Pub/Sub System Organization User Pub/Sub access to User User access to Messages Web Service filter name/pass network based Endpoint on user authenticated authorized authorized access

19 Future Topics Governance development Advanced governance synchronization Data Sharing Agreements FF-ICE Governance Rules Messaging development Flight Object Messaging Global Security Model

European Sky ATM Research (SESAR) [5][6] in Europe both consider the implementation of SWIM as a fundamental element for future ATM systems.

European Sky ATM Research (SESAR) [5][6] in Europe both consider the implementation of SWIM as a fundamental element for future ATM systems. (FIXM) and the weather information exchange model 1. INTRODUCTION With the rapid increase in local and global air traffic, the system-wide operational information exchange and life-cycle management technologies