System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPU6.6.2 ExternalThe interfaces between the systems and the applications, along with those for (remote) administration of apSHIELD system are two cases of external interfaces:Remote commandsThe interface through which a node receives configuration commands, data and equipment status form anexternal operator.SNMP interfaceAn external maintenance system can perform node monitoring and control through an SNMP interface.User interfacesThe interfaces used in specific applications for the intercommunication between components or betweenthe user and the system. For example, Shepherd (provided by Telenor Objects) is an M2Mcommunication platform, on which pSHIELD nodes can be connected through APIs and transmit theirsensor information securely. More detailed information about application information is being developedand presented in the framework of WP6.6.6.3 NodeThe interfaces that the nodes of the systems are using and providing are mentioned below:I/O interfacesInterfaces used to connect to peripherals and pSHIELD functionalities. Depending on the node type andfunctionality they can be RS232, Serial, GPIO etc.Dedicated functions/modules interfacesInterfaces (usually in master-slave form) which transmit the output of a dedicated function:1. Health monitoring2. Security3. Application processor4. Power management5. Memory6. Reconfiguration controllerCommunication interfacesInterfaces used for the networking or radio function of the node (Ethernet, USB, Wi-Fi, ZigBee, TPM andInfiniband).PUD2.3.2Issue 5 Page 118 of 122
pSHIELDSystem Architecture DesignPU6.6.4 ComponentsThe interfaces between the components of the architecture are indicated below:L-ESD interfacesThree interfaces are exported by legacy embedded devices, representing the inter-layer communication ofdifferent components:1. Middleware services interface, MS2. Network services interface, NS3. Node capabilities interface, NCpS-ESD interfaceThe transition from legacy devices to the so called pSHIELD embedded device comes with the addition ofinterface pS-MS, providing pSHIELD functionalities at Middleware layer. Moreover, pS-NC and pS-NS arethe expansion of NC and NS (above) to include pSHIELD compliant functionalities.These interfaces include the following features:1. Function (operation of the component, further discriminated in name, input and outputparameters)2. Contract (used by the Core SPD services to synthesize the available services beam)3. Description (semantics)4. SPD status (current SPD level)5. Connector (connecting two functionalities)pS-SPD-ESD interfacepSHIELD SPD Embedded System Device is outfitted with a minimal set of Overlay functionalities. Thisextra feature corresponds to the extra overlay interface pS-OS. The Overlay services are provided bySecurity Agent, the pSHIELD module responsible for the composability of the platform.Security Agent interfacesTwo internal interfaces (inside every Security Agent) are used to exchange information between the twomodules of SA. They are pS-SKR and pS-CA, arranging the communication between SemanticKnowledge Representation and Control Algorithms modules.Semantic modelsThe Semantic models are responsible for the efficient interpretation of syntax of data structures andknowledge in the application domains. Two interfaces are realized in these components, namely interfaceDB, between the Semantic Reasoner and the Database and interface KR (Knowledge Repository),between semantic aware components.PUD2.3.2Issue 5 Page 119 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:
Page 67 and 68: pSHIELDSystem Architecture DesignPU
Page 75: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?