1 EMC2 - Arrowhead synergies Prof. Jerker Delsing Luleå University of Technology www.arrowhead.eu ■ Service interface architecture for multicritical applications executed on Multicore processors ■ Realtime ■ Security ■ Safety and Fault tolerant Page ‹#› IMC-AESOP: ArchitecturE for Service-Oriented Process - Monitoring and Control Seventh Framework Programme (FP7) Theme ICT - Information and Communication Technologies Grant agreement no: 258682 | Project Co-ordinator: Armando Walter Colombo | Schneider Electric Automation GmbH IMC-AESOP Architecture 3 EMC2 requirements ■ Service access control ■ Secure boot and update ■ Service discovery ■ Attest of boot and deployment ■ Service deployment ■ Power attacks ■ Service composition ■ Data encryption ■ Data aggregator (energy usage com. eff. ■ Encrypted service deployment ■ Resource monitoring ■ Interference detection ■ Disjoining processing units ■ Admission control ■ Security of reconfiguration ■ Process and resource synchronisation ■ Intra MPC communication ■ Deterministic communication ■ Monitoring service ■ Gateway service ■ Multiple security domains ■ Memory protection ■ Task/service identification ■ Resource identification ■ Error reporting ■ Service encapsulation ■ Service artefact id ■ Service configuration ■ HW and OS adaptability Page ‹#› EMC2 spec. mapping to Arrowhead Framework ■ Service access control Authorisation service, ■ Service discovery Service registry&discovery ■ Service deployment Service Deployment ■ Service composition Orchestration ■ Data aggregator Meta service registry ■ Resource monitoring ? ■ Disjoining processing units ? ■ Admission control Authentication service ■ Security of reconfiguration Authentication service ■ Process&resource synch ? ■ Intra MPC communication HW or Service ■ Deterministic com. ? ■ Monitoring service Monitoring service-proposed ■ Gateway service Arrowhead Framework Page ‹#› EMC2 spec. mapping to Arrowhead Framework ■ Secure boot and update ? ■ Attest of boot and deploy. ? ■ Power attacks ? ■ Data encryption Specified by SOA, CP ■ Encrypted service deploy Deployment authorisation ■ Multiple security domains Authorisation services ■ Interference detection ? ■ Memory protection ? ■ Task/service identification Service registry/discovery ■ Resource identification User system reposi./service ■ Error reporting Event handler system ■ Service encapsulation ? ■ Service artefact id Service registry/discovery ■ Service configuration Config, Orch, Depl System ■ HW and OS adaptability Arrowhead Framework Page ‹#› ■ SOA technology a brief introduction ■ Material from Arrowhead project Page ‹#› 8 SOA Services are produced Services are consumed Service producer Application service System B System A Exchange information www.arrowhead.eu Service Consumer 9 SOA Key properties • • Loosely coupled • Autonomy • Distributed • Owner is responsible and owns the information and decide whom to share to Late binding • • www.arrowhead.eu Possible to use information anytime by connect to the correct resource at a given time Lookup • Publish and register for notify others about endpoint (how to reach me) • Discover others that I comply to (expected/wanted Service Type) 10 Fundamental approaches in Arrowhead • • • • • www.arrowhead.eu Information centric Information assurance at service exchange level Publish subscribe approach Push approach - Pull possible Minimal set of mandatory services in a System of Systems Mandatory services to enable a service exchange 11 How to set presence (existence) of the Service in the Framework? How to discover Services? How to decide which consumer has access right in security level? Service producer How to control which service instances shall exchange information? Application service System B System A www.arrowhead.eu Service Consumer Exchange information 12 Core services IA II (core funct.) (core funct.) IA: (The Information Assurance )core system providing support for secure information exchange. The IA provides authorization, authentication, certificate distribution, security logging and service intrusion functionality Core Services II : (The Information Infrastructure) is the core system mainly in charge of providing support for service registry and service discovery. It also addresses orchestration, software distribution and application control Service producer Application service www.arrowhead.eu Exchange information (core funct.) SM : The System Management (SM) is the core system providing support for Late binding and solving system of system composition. The SM provides logging, monitoring and status functionality. It also addresses network QoS and performance, configuration and policy Service Consumer System B System A SM Core Arrowhead Framework Service IA, Information Assurance services Authorisation Control Authorisation Management User and System Registry Deployment Authentication SM, System Management services Orchestration Orchestration Store Orchestration Management Meta Service Registry II, Information Infrastructure service Service Registry User System Repository Service Discovery Event Handler www.arrowhead.eu Deployment System 14 Arrowhead Framework II SM Application system ARROWHEAD FRAMEWORK COMPLIANT LOCAL CLOUD Application system Application system Application system www.arrowhead.eu IA Application system Application system 15 Documentation structure SoSD: System-of-Systems Description SoSDD: System of Systems Design Descript SysD: System Description SysDD: System Design Description SD: Service Description IDD: Interface Design Description CP: Communication Profile SP: Semantic Profile www.arrowhead.eu 16 Application Pilot A Service def Pilot B Service def Pilot C Service def Pilot D Service def Pilot E Service def Pilot A XML def Pilot B JSON def Pilot C XML def Pilot D JSON def Pilot E XML def Semantics Compression/EXI CoAP UDP DDS XMPP DPWS uPnP HTTP 1.1 TCP IPv4/IPv6/IP multicast www.arrowhead.eu MQTT OPCUA EMC2 architectural aspects ■ Two possible principles ■ EMC2 service paradigm between any service executed on a single MCP, a cloud on a chip. ■ EMC2 services only as a shell to an MCP running multiple application Internal middleware/OS components to meet requirements Mission Mission critical tasks Mission critical tasks Mission critical tasks Mission critical tasks Mission critical tasks critical tasks EMC2 MCP Mission critical Mission critical Mission critical service Mission critical service Mission critical service service service Page ‹#› Conclusion ■ Arrowhead results exploited in the EMC2 project ■ Still a number of open questions on ■ Real time ■ Security ■ Safety and fault tolerant ■ EMC2 service interface architecture by 2017 Page ‹#›
© Copyright 2024