System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPUAlso depending on application criticality, other forms of fault-tolerance may be used, such as staticredundancy (e.g. Triple Modular Redundancy - TMR) 12 or dynamic redundancy, such as stand-by spare.This redundancy may be applied for each one of the modules that constitute the pSHIELD Node, evenNano Node.6.1.1.2.2 Security and PrivacySecurity and privacy are assured by the Security/Privacy module. The level of security and privacydepends on the modules that are implemented, which may assure, for example, Data Encryption, DataDecryption, Generation of Cryptographic Keys, etc.6.1.1.3 Requirements for pSHIELD Power Node, Micro/Personal Node and Nano node6.1.1.3.1 HW/SW ImplementationA pSHIELD Node is deployed as a hardware/software platform, encompassing intrinsic, innovative SPDfunctionalities, providing proper services to the other pSHIELD Network and Middleware Adapters toenable the pSHIELD Composability and consequently the desired system SPD 13 .The three kinds of pSHIELD SPD Node each deploy a different configuration of Node Layer SPDfunctionalities of the pSHIELD framework and comprise a different type of complexity: Nano nodes,Micro/Personal nodes and Power nodes. Nano nodes are typically small ESD with limited hardware andsoftware resources, such as wireless sensors. Micro/Personal nodes are richer in terms of hardware andsoftware resources, network access capabilities, mobility, interfaces, sensing capabilities, etc. Powernodes offer high performance computing in one self-contained board offering data storage, networking,memory and (multi-)processing.The table below presents typical hardware deployed in each node type for every module of the pSHIELDSPD Node conceptual model.12“On the Reliability of Cascaded TMR Systems”, Masashi Hamamatsu, Nomura Research Institute, Ltd., Yokohama-City, Japan,Tatsuhiro Tsuchiya Tohru Kikuno, Osaka University, Suita-City, Japan, 2010 Pacific Rim International Symposium on DependableComputing13 “Security and Dependability of Embedded Systems: A Computer Architects’ Perspective” Jörg Henkel, University of Karlsruhe,Karlsruhe, Germany; Vijaykrishnan Narayanan, Pennsylvania State University, USA; Sri Parameswaran, University of New SouthWales, Australia; Roshan Ragel, University of Peradeniya, Sri Lanka VLSID '09 Proceedings of the 2009 22nd InternationalConference on VLSI Design EEE Computer Society Washington, DC, USA ©2009PUD2.3.2Issue 5 Page 74 of 122
pSHIELDSystem Architecture DesignPUpSHIELD SPD node blockApplication Processor (Legacy DeviceComponent)Non-volatile memory (Legacy DeviceComponent)Volatile memory (Legacy DeviceComponent)Special-Purpose Processor (LegacyDevice Component)Node pSHIELD Specific ComponentStable Storage (Dependability Block)Reconfiguration and RecoveryController (Dependability Block)I/O InterfacePower ManagementSecurity and PrivacyPower nodeMulti-core processor(HW and/or SWcore)ROM, EEPROM,FLASH, Hard Disk orother forms of nonvolatilememoryMicro/PersonalnodeMicrocontroller (HWand/or SW core)ROM, EEPROM,FLASHNano nodeMicrocontrollerROM, EEPROM,FLASHRAM, SRAM, DRAM RAM, SRAM, DRAM RAMHardware digitalsignal processing(DSP) and/or gluelogic blocksHardware orSoftwareFlash-based, 2memory banks, HWor SW controlIP CoreUSB, ETHERNET,UART, CAN, RS232,RS485, GPIOUPS, PowerMonitoring DeviceAES EncryptionTPM ModuleADCHardware orSoftwareFlash-based, singlememory bankIP Core, ASIC orVLSIGPIO,ETHERNET,RS232, CANPower MonitoringDeviceTPM moduleOTP (one time)PasswordADCHardware orSoftwareN.A.N.A.SERIAL; Wi-fi; RF-ID;BT; Zigbee;N.A.N.A.6.1.1.3.2 Capabilities and FunctionalitiesTable 1 - pSHIELD enabling technologies by node types.As previously stated, different pSHIELD node types are enabled by different technologies and providedifferent functionalities.Depending on the Node Type, different capabilities and functionalities, such as those described in Section6.1.2, may be Available [A], Not Available [N.A.] or Optional [O.], such as presented, as example, in thefollowing table:PUD2.3.2Issue 5 Page 75 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: pSHIELDSystem Architecture DesignPU
Page 31 and 32: pSHIELDSystem Architecture Design
Page 39 and 40: pSHIELDSystem Architecture Design
Page 47 and 48: pSHIELDSystem Architecture Designen
Page 73: pSHIELDSystem Architecture DesignPU
Page 82: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

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

Delete template?

Save as template?