System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUWe can define the architecture of a pSHIELD Subsystem (pS-S) as a set of Embedded System Devicesincluding several L-ESD, connected to several pS-ESD and one and only one pS-SPD-ESD. Connectionsbetween two generic ESDs (L-ESD, pS-ESD or pS-SPD-ESD) can be performed, by means of legacyfunctionalities at Node, Network and/or Middleware layer, through the so-called NC, NS and MSfunctionalities, respectively. This means, for example, that the legacy Node layer capabilities (e.g. legacyphysical connectors) of an L-ESD can be used to connect it to a pS-SPD-ESD having a compatible Nodelayer capability (e.g. the same connector format factor). The connection of a pS-ESD with another pS-ESD or with a pS-SPD-ESD can also be performed by exploiting the additional pSHIELD Middlewarelayer functionalities exposed by the pS-MS interface. Each pSHIELD Subsystem (pS-S) must have oneand only one pS-SPD-ESD, so that a pS-SPD-ESD can be connected to another pS-SPD-ESD by meansof so called pS-OS functionalities. A pSHIELD Subsystem is depicted in the following figure.Figure 40 – pSHIELD Subsystem architecture decomposed into ESD componentsLet’s consider a pSHIELD system including several Embedded System Devices belonging to the threeabove defined types of ESD: L-ESD, pS-ESD and pS-SPD-ESD. The pSHIELD system architecture canbe represented as a set of pSHIELD subsystems each connected to the other by means of the overlayinterfaces provided by the Service Agent:Figure 41 – pSHIELD System Architecture decomposed into pSHIELD SubsystemPUD2.3.2Issue 5 Page 110 of 122
pSHIELDSystem Architecture DesignPUThe figure below shows the pSHIELD System Architecture highlighting the various ESD types.In particular, for the sake of clarity, only the pSHIELD Subsystem 1 has been exploded to explicit thevarious ESD types. Specifically, within the pSHIELD Subsystem 1, (i) the connections among the pS-ESDand the L-ESDs have been grouped in the “Legacy Middleware Network Node” cloud, (ii) the connectionsamong the pS-ESDs and the pS-SPD-ESD have been grouped in the “pSHIELD Middleware” cloud, (iii)the connections among different pSHIELD Subsystem (i.e. between different pS-SPD-ESDs) have beengrouped in the “Overlay” cloud.The Overlay consists of a set of SPD Security Agents located each in a different pS-SPD-ESD. Each SPDSecurity Agent controls a different pSHIELD subsystem. Subsystem identification has to be carefullyperformed scenario by scenario. Expandability is obtained by enabling communication between SPDSecurity Agents taking care of different pSHIELD sub-systems.pShield Subsystem 2pS‐SPD‐ESDpShield Subsystem NpS‐SPD‐ESDOVERLAYL‐ESDLEGACYMIDDLEWARENETWORKNODEL‐ESDpS‐ESDpSHIELDMIDDLEWAREL‐ESDpS‐SPD‐ESDpS‐ESDLEGACYMIDDLEWARENETWORKNODEL‐ESDL‐ESDpShield Subsystem 1pS‐ESDLEGACYMIDDLEWARENETWORKNODEL‐ESDL‐ESDFigure 42 – pSHIELD System Architecture highlighting the ESD types.In order to introduce the next sections, we should refine the ESD model. Exploding the model of a pS-SPD-ESD, it is possible to identify that its external functionalities are provided by the interaction of twocomponents: the L-ESD and the pSHIELD Proxy. While we have already defined the L-ESD component,the pSHIELD Proxy is a new component.PUD2.3.2Issue 5 Page 111 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: 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?