System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUFigure 43 – pS-SPD-ESD architecture.A pSHIELD Proxy (pS-P) is a technology dependent component of a pS-SPD-ESD that, interacting withthe available legacy Node, Network and Middleware capabilities and functionalities (through the NC, NSand MS interfaces, respectively), provides all the needed pSHIELD enhanced SPD functionalities. Fromthe above figure, it is clear that the pS-SPD-ESD functionalities belongs both to the L-ESD component(MS, NS and NC interfaces), as well as to the pSHIELD Proxy component (pS-MS and pS-OS interfaces).The pSHIELD Proxy component can be further decomposed in two components (see following figure),namely the pSHIELD Adapter and the Security Agent. The rationale behind these two components, aswell as their architecture, is hereinafter explained.The pSHIELD Adapter is a technology dependent component in charge of interfacing with the legacyNode, Network and Middleware functionalities (through the MS, NS and NC interfaces). The legacyfunctionalities can be enhanced by the pSHIELD Adapter in order to make them pSHIELD-compliant, i.e.they become SDP legacy device components, which can be composed by other SPD components,according to the SPD Composability approach. In addition, the pSHIELD Adapter includes Innovative SPDfunctionalities which are SPD pSHIELD-specific components, which can be composed by other SPDcomponents. The pSHIELD Adapter exposes the technology independent pSHIELD Middleware layerfunctionalities that are used by the Security Agent component.The Security Agent is a technology-independent component in charge of aggregating the informationcoming from the pSHIELD Middleware Services provided by the internal pSHIELD Adapter or by otherpSHIELD Proxies located in the same subsystem. The Security Agent is also in charge of gathering theinformation coming from other Security Agents connected on the same Overlay (through the pS-OSinterface). The Security Agent includes proper control algorithms working on the basis of the availableinformation; the decisions taken by these Control Algorithms are enforced through the pS-MS and the pS--OS interfaces.PUD2.3.2Issue 5 Page 112 of 122
pSHIELDSystem Architecture DesignPUFigure 44 – pSHIELD Proxy component architecture.The Security Agent component can be further decomposed in two components (see following figure),namely the Semantic Knowledge Representation and the Control Algorithms. The rationale behind thesetwo components, as well as their architecture, is hereinafter explained.Figure 45 – pSHIELD Security Agent component architectureThe Semantic Knowledge Representation is in charge of bi-directionally exchanging technologyindependent(and semantic enriched) information from the pS-MS and the pS-OS interfaces. It is also incharge to provide such information via the pS-SKR interface to the Control Algorithms component.The Control Algorithms retrieves the aggregated information on the current SPD status of thesubsystem, as well as of the other interconnected subsystems, by the pS-CA interface connected to theSemantic Knowledge Representation; such retrieved information is used as input for the ControlAlgorithms. The outputs of the Control Algorithms consist in decisions to be enforced in the various ESDsincluded in the pSHIELD subsystem controlled by the Security Agent in question; these decisions are sentback via the pS-MS interface, as well as communicated to the other Security Agents on the Overlay,through the pS-OS interface.The pSHIELD Adapter can be further decomposed as in three components (see following figure), namelythe pSHIELD Node Adapter, the pSHIELD Network Adapter and the pSHIELD Middleware Adapter. Therationale behind these three components, as well as their architecture, is hereinafter explained.PUD2.3.2Issue 5 Page 113 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:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62: pSHIELDSystem Architecture DesignPU
Page 75: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?