System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUThe L-ESD architecture is composed by three components: (i) the Legacy Middleware Services; (ii) theLegacy Network Services and (iii) the Legacy Node Capabilities.The Legacy Middleware Services includes all the legacy middleware services (i.e. messaging, remoteprocedure calls, objects/content requests, etc.) provided by the Legacy Embedded System Device whichare not pSHIELD-compliant. In order to be pSHIELD compliant, these services should be enriched withpSHIELD SPD functionalities. The pSHIELD Middleware Adapter is in charge of this task.The Legacy Network Services includes all the legacy network services (protocol stacks, routing,scheduling, Quality of Service, admission control, traffic shaping, etc.) provided by the Legacy EmbeddedSystem Device which are not pSHIELD-compliant. In order to be pSHIELD compliant, these servicesshould be enriched with pSHIELD SPD functionalities. The pSHIELD Network Adapter is in charge of thistask.The Legacy Node Capabilities component includes all the legacy node capabilities (i.e. battery, CPU,memory, I/O ports, IRQ, etc.) provided by the Legacy Embedded System Device which are not pSHIELDcompliant. In order to be pSHIELD-compliant, these capabilities should be enhanced and enriched withpSHIELD SPD functionalities. The pSHIELD Node Adapter is in charge of this task.Application ScenariopSHIELD Middleware LayerLegacy MiddlewareCapabilitiespSHIELD Middleware AdapterCore 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 50 – pSHIELD functional component architecture.The result of the above considerations is the pSHIELD functional architecture depicted in Figure 50. Thisfigure highlights some of the key pSHIELD enabling technologies mapped into the four functional layersintroduced in the previous section. More specifically:1. The pSHIELD NodePUD2.3.2Issue 5 Page 116 of 122
pSHIELDSystem Architecture DesignPU2. The Innovative SPD functionalities (e.g. smart SPD driven transmission and Cryptographicalgorithms)3. The semantic knowledge models4. The core SPD services5. The control algorithms based on Hybrid Automata theory6.6 InterfacesThis section attempts to register and to categorize the interfaces which occur in a pSHIELD system. Theterm is quite generic, but the importance is great, since the interfaces are used to determine theinterconnectivity internally, as well as the presentation and application capabilities of a platform.Consequently, the categories indicated hereafter may include overlapping elements, considering the factthat the definition is dependent on the different level of approach regarding “interface”.6.6.1 InternalThe interfaces between the four pSHIELD layers are registered below:Overlay interfacesInterfaces used for the interconnection with Middleware layer:1. Sensed Metadata (transferring information to Overlay)2. Elaborated Metadata (transferring information to Middleware)3. Rules for discovery and composition (transferring information to Middleware)Middleware interfacesApart from the interfaces with Overlay (mentioned just above), two interfaces handle the SPD related dataexchange with the underlying layers:1. Heterogeneous SPD relevant parameters and measurements (from Node and Network toMiddleware)2. Commands for composition and configuration of SPD modules (from Middleware to Node andNetwork)Network interfacesThe family of network interfaces is constituted from those registered in § 6.2.5 (NS, pS-NS), along with allthe devices or parts of equipment serving as demarcation points in telecommunication networks lying inevery pSHIELD implementation (Ethernet, Infiniband interface in Power Node etc.)Node interfacesA pSHIELD node exchanges data, measures parameters and receives commands through network,middleware and overlay interfaces, which ensure the communication with the respective incumbentlayers.PUD2.3.2Issue 5 Page 117 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:
Page 63 and 64:
Page 65 and 66: pSHIELDSystem Architecture DesignPU
Page 75: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?