System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPU1 Executive SummaryD2.3 is a deliverable of pSHIELD WP2, “Scenarios, requirements and system design,” separated intointernal intermediate deliverable D2.3.1, “Preliminary system architecture design” and public finaldeliverable D2.3.2, “System architecture design”. As denoted by its title, the main objective is to describea formal and conceptual overall system architecture, to address Security, Privacy and Dependability(SPD) in the context of Embedded Systems (ESs) as “built in” rather than as “add-on” functionalities,proposing and perceiving with this strategy the first step towards SPD certification for future ESs. Themethodology adopted concerns the gradual process and interaction with the major project topics, whichform the framework for the architecture design, such as requirements, application scenario, metrics andtechnology development in the four layers described in the project. The latter, hierarchically ascending,Node, Network, Middleware and Overlay layers comprise the pSHIELD proposal, an alternative butintegrative to classical layered OSI model structure. Therefore, the concluding complete architecture ispresented through the definition of the four layers, the interfaces between them and the overall frameworksynthesized.PUD2.3.2Issue 5 Page 12 of 122
pSHIELDSystem Architecture DesignPU2 IntroductionThe main goal of pSHIELD is to ensure that security, privacy and dependability (SPD) in the context ofintegrated and interoperating heterogeneous services, applications, systems and devices. Systems andservices must be robust in the sense that an acceptable level of services is available despite theoccurrence of transient and permanent perturbations such as hardware faults, design faults, imprecisespecifications and accidental operational faults.The pSHIELD architecture composability relies on the so called SPD modules. Indeed the pSHIELDarchitecture is composed by a ‘mosaic’ of innovative SPD functionalities, each one of the consideredlayers. The pSHIELD architecture is able to derive application instantiations of the general framework,selecting statically (at design time) and dynamically (at runtime) the best SPD functionalities for achievingthe required SPD levels. In particular, referring to the abovementioned layers, the SPD modules willimplement the following functionalities:• At node layer, intelligent hardware and firmware SPD• At network layer, secure, trusted, dependable and efficient data transfer based on selfconfiguration,self-management, self-supervision and self-recovery• At middleware layer, secure and efficient resource management, inter-operation amongheterogeneous networks• At overlay layer, composabilityR&D for embedded security, intended as a system issue that must be solved at all abstraction levels(protocols, algorithms, architecture), will lead, in the framework of this task, to a coherent, composableand modular architecture for a flexible distribution of SPD information and functionalities between differentESs while supporting security and dependability characteristics.This framework in D2.3.2 aims, at the one hand, to explore the minimum set of interdependenciesbetween applications and architectures in an efficient way and to systematically classify those withrespect to SPD. On the other hand, it aims to produce a composable architecture which will include mostcritical elements, thus covering most of the SPD requirements for all the applications. This approach isexpected to produce a multi-layered architecture, where each layer consists of several hardware andsoftware SPD modules (components), since it is imperative to take into account the need for composablesecurity, privacy and dependability.The resulting architecture has to be reconfigurable, offline, meaning that mechanisms should be providedto the designer for enabling/disabling nodes in order to tailor the overall system to his needs. Furthermore,fault diagnosis and fault recovery have to be addressed both in hardware and software layers.Intra-layer and inter-layer interfaces should be defined in the system architecture to ensure the correctcommunication among the different SPD modules.PUD2.3.2Issue 5 Page 13 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: Issue 5Page xi
Page 15 and 16: pSHIELDSystem Architecture DesignPU
Page 19 and 20: pSHIELDSystem Architecture Design3.
Page 31 and 32: pSHIELDSystem Architecture Design
Page 39 and 40: pSHIELDSystem Architecture Design
Page 47 and 48: pSHIELDSystem Architecture Designen
Page 63 and 64:
pSHIELDSystem Architecture DesignPU
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75:
Page 80 and 81:
Page 82:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
show all

System Architecture Design

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

Delete template?

Save as template?