System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUdescribed in the previous section, these decisions consist in a set of rules for discovery, configuration andcomposition of SPD components.The decisions mentioned above are eventually actuated in the pSHIELD subsystem controlled by theconsidered SPD Security Agent, by exploiting the mediation of the middleware as detailed in the previoussection.Summarizing, each SPD Security Agent consists of two key elements:i. the Semantic Knowledge Repository (i.e. a database) storing the dynamic, semantic, enriched,ontological aggregated representation of the SPD functionalities of the pSHIELD subsystemcontrolled by the SPD Security Agentii. the Control Algorithms generating, on the grounds of the above representation, key SPD-relevantdecisions (consisting, as far as the Composability feature is concerned, in a set of discovery,configuration and composition rules)The formalized conceptual model of a pSHIELD Security Agent, described in the previous section, isreported in the below figure.Figure 34 – Formalized conceptual model for pSHIELD Security Agent.PUD2.3.2Issue 5 Page 106 of 122
pSHIELDSystem Architecture DesignPUThe figure also highlights the correspondence between the class diagram and a classical feedback controlscheme (including Process, Controller and Sensing/Actuation functionalities) where:• the Process to be controlled is represented by the three horizontal layers (Node, Network andMiddleware)• the Controller is the Security Agent supported by the Semantic Knowledge Repository• Sensors/Actuators are represented by the Core SPD Services lying at the pSHIELD MiddlewarelayerThe formalized conceptual model of the pSHIELD Overlay is shown in the following figure. Taking intoaccount that the pSHIELD Overlay can include several Security Agents each one controlling a pSHIELDsubsystem, the pSHIELD Overlay model is easily obtained by composing in parallel the feedback controlscheme relevant to each Security Agent presented in the previous figure. The coordination andinformation exchange between the different controllers (i.e. SPD Security Agents) is performed by meansof metadata (referred to as exchanged metadata). The advantages in terms of flexibility entailed by thismodular approach are evident.Figure 35 – Formalized conceptual model for the pSHIELD Overlay.6.5 System Overall ArchitectureIn order to formally describe the pSHIELD system overall architecture, we decided to use the UMLcomponent diagram formalism, where there could be identified the following formal elements:FUNCTIONALCOMPONENTPHYSICALCOMPONENTIMPORTINTERFACEEXPORTINTERFACEFigure 36 – pSHIELD functional architecture formalism.PUD2.3.2Issue 5 Page 107 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: pSHIELDSystem Architecture DesignPU
Page 75: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?