System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUThe composition engine tries to accomplish the pSHIELD Overlay configuration rules applying thefollowing procedure:1. Composition service triggers the Discovery service, sending a SPD component request, lookingfor those SPD components defined in the configuration rules provided by the Overlay2. The Discovery Engine sends the request to the Query Preprocessor3. The Query Preprocessor enriches the service request with contextual information and sends itback to the Discovery Engine4. The Discovery Engine applies a global service discovery using heterogeneous DiscoveryProtocols, in order to collect as much available SPD functionalities as possible over thenetworked Embedded System Devices5. Each Discovery Protocol interacts with the Service Registries reachable in the network andretrieves the SPD components’ descriptions and provides them back to the Discovery Engine6. The Discovery Engine collects the discovered descriptions and sends them to the Filter Engine7. The Filter Engine applies a semantic filtering, retrieving the semantic metadata from the semanticDB, accordingly with the references reported in each SPD component description. The filtered listof component is then sent back to the Discovery Engine8. The Discovery Engine sends the list of available, filtered SPD components to the Compositionservice9. If the Composition service, considering the available SPD components is able to provide a newconfiguration, these components are activated, otherwise the Composition service advise theOverlay that it is not possible to apply its decisionIt is important to note that the validity of this conceptual framework model is independent from the specificapplication scenario. On the basis of this conceptual framework it is possible to derive a number ofpossible alternative implementations, belonging to different pSHIELD compliant technology providers. Ifthe interfaces and the operation between the different elements are respected, it is possible to setupheterogeneous systems with the enhanced pSHIELD SPD functionalities.6.4 Overlay LayerThe following figure highlights in light red, some key functionalities and interfaces involving the Overlaylayer.PUD2.3.2Issue 5 Page 104 of 122
pSHIELDSystem Architecture DesignPUApplication ScenariopSHIELD Middleware LayerpSHIELD Middleware AdapterLegacy MiddlewareCapabilitiesCore SPD ServicesandInnovative SPD FunctionalitiesSensed MetadataElaborated MetadataRules for discoveryand compositionSemanticKnowledgeRepositoryControl algorithmsHeterogeneous SPD‐relevantparameters and measurementsSPD Security AgentCommands for composition andconfiguration of SPD modulesExchangedmetadatapSHIELD Node LayerpSHIELD Node AdapterInnovative SPDFunctionalitiespSHIELD Network LayerpSHIELD Network AdapterInnovative SPDFunctionalitiesOther SPD SecurityAgentsLegacy NodeCapabilitiesLegacy NetworkCapabilitiespSHIELD OverlayLayerFigure 33 – pSHIELD overlay: a functional viewThe Overlay consists of a set of SPD Security Agents, each one controlling a given pSHIELD subsystem.Subsystem identification has to be carefully performed scenario by scenario. Expandability of such aframework is obtained by enabling communication between SPD Security Agents controlling different subsystems.As a matter of fact, the presence of more than one SPD Security Agent is justified by the need ofsolving scalability issues in the scope of system-of-systems: exponential growth of complexity can beovercome only by adopting the policy of divide et impera (divide and rule).Each SPD Security Agent, in order to perform its work, exchange carefully selected information with theother SPD Security Agents, as well as with the three horizontal layers (node, network and middleware) ofthe controlled pSHIELD subsystem.Each SPD Security Agent collects properly selected heterogeneous SPD-relevant measurements andparameters coming from node, network and middleware layers of the controlled pSHIELD subsystem; thisinformation is used as valuable input for the Control Algorithms. Since the SPD Security Agent is mainly asoftware functionality and not a physical system itself, it needs the mediation of the pSHIELD MiddlewareCore SPD Services, as it has been explained in the previous section.The heterogeneous data collected from the three horizontal layers are abstracted, translated intotechnology-independent metadata, semantically enriched and aggregated. The resulting metadata(referred to as sensed metadata) are stored in the Semantic Knowledge Representation of the consideredSPD Security Agent. By so doing, this database stores a dynamic, semantic representation of thecontrolled pSHIELD subsystem.In the considered SPD Security Agent, the representation mentioned above is used as a valuable, richinput for a set of intelligent, technology-independent, closed-loop Control Algorithms. These last, by using(as input) the above-mentioned representation and by adopting appropriate advanced methodologies ableto profitably exploit such input, produce (as output) decisions aiming at guaranteeing, whenever it ispossible, target SPD levels over the controlled pSHIELD subsystem. In the Composability featurePUD2.3.2Issue 5 Page 105 of 122
Page 1 and 2:
Project no: 100204pSHIELDpilot embe
Page 3 and 4:
Contents1 Executive Summary .......
Page 5 and 6:
FiguresFigure 1 - A generic embedde
Page 7 and 8:
Figure 45 - pSHIELD Security Agent
Page 9 and 10:
MGFMIPSMLNeLNFMRFPNMPNMPSNoLNVMOLOS
Page 11 and 12:
Issue 5Page xi
Page 13 and 14:
pSHIELDSystem Architecture DesignPU
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
pSHIELDSystem Architecture Design3.
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
pSHIELDSystem Architecture Design
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
pSHIELDSystem Architecture Design
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
pSHIELDSystem Architecture Designen
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: pSHIELDSystem Architecture DesignPU
Page 75: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?