System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUb)Figure 2 – a) Overview of the functional architecture of TISPAN NGN release 2, b) layeredview of the TSPAN NGN architecture.The main scope of the above functional architecture is to identify a set of functional blocks, for example:Media Gateway Function (MGF); Border Gateway Function (BGF); Access Relay Function (ARF);Signaling Gateway Function (SGF); Media Resource Function Processor (MRFP); Layer 2 TerminationFunction (L2TF), etc. Each subsystem is specified as a set of functional entities and related interfaces. Asa result implementers may choose to combine functional entities where this makes sense in the context ofthe business models, services and capabilities being supported. Where functional entities are combinedthe interface between them is internal, hidden and un-testable.Example 2:The Web system architectures have a technical architecture that is divided in functional and informationarchitecture. For both the information architecture and the functional architecture, various abstractionlevels exist, which include the business architecture, logical architecture, physical architecture andimplementation architecture:• Business Architecture: The business architecture represents business processes, policies andprocedures, workflows and user interactions. This is used to guide the design of other moretechnical related architecture layers• Logical Architecture: The logical architecture defines at a high level the structure of the system tobe developed. The elements in this layer are logical concepts, instead of concrete or physicalsoftware componentsPUD2.3.2Issue 5 Page 16 of 122
pSHIELDSystem Architecture DesignPU• Physical Architecture: The physical architecture further defines the technical solution at a detailedlevel. Some design decisions, such as the selection of content storage product, can berepresented in this layer• Implementation Architecture: The implementation architecture specifies system composition andinterconnectionspSHILED Functional Architecture (pSFA) is composed by four functional layers: node, network,middleware and overlay, which represent a set of four functional sub-systems that are specified by its setof elements, functional entities and interfaces.Node Layer (NoL) of pSFA: node layer is composed of Intelligent ES HW/SW Platform and havedifferent kinds of Intelligent ES Nodes: nano node, micro/personal node, power node, and DependableSelf-X Crypto Technologies. This layer is composed of standalone and/or connected NoL elements likesensors and actuators, which perform smart transmission.The NoL is a layer composed by physical nodes (i.e. hardware). Each node is a generic EmbeddedSystem (for example a sensor, an actuator, a transmitter etc.).Network Layer (NeL) of pSFA is a heterogeneous layer composed by a common set of protocols,procedures, algorithms and communication technologies that allow the communication between two ormore nodes.Middleware Layer (ML) of pSFA is the software layer that provides the basic functionalities to use theunderlying networks of embedded systems (like service discovery and composition) as well as somesecurity functionalities (like accounting or access control). This layer, being software, is installed on thenodes.Overlay Layer (OL) of pSFA is a logical vertical layer that collects (directly or indirectly) semanticinformation coming from the Node, Network and Middleware layers and uses them to compute theadequate actions (if any) that ensure the desired level of SPD. It is a software routine running atmiddleware and/or application level.3.1 Cross-Layer / Cross-Overlay Architecture Definitions3.1.1 IntroductionThe purpose of this chapter is to give an overview on the cross-layer architectures (CLAs) proposedrecently by the research community and to address in details SPD issues for overall pSHIELD SystemArchitecture (pSSA).In wireless and mobile networking envisioned for pSHIELD System Architecture (pSSA), difficultenvironmental conditions are a permanent challenge, resulting in a demand for cross-layer optimizations.There is also a need to further increase flexibility of the network. Therefore, we believe cross-layerarchitectures should adapt themselves to these changing conditions, just as they adapt the network stack,devices, and applications.The network protocol stacks are logically organized in layers. These layers are strictly separated and thecross-layer functionality between them is restricted by determined interfaces, which in effect only allowpassing packets up and down the stack. In principle, all these layers have been designed to fulfil theirfunctionality without interaction across the layers. History shows that this works well in wired and staticPUD2.3.2Issue 5 Page 17 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: 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 67 and 68:
pSHIELDSystem Architecture DesignPU
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

Create successful ePaper yourself

Delete template?

Save as template?