System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPU6.1.1.1.12 Performance/Metrics SPD functionalities• Get performance/metrics – gets performance and metrics information from the whole systemFollowing, the list of the metrics provided by the node:1. System and components health status2. System and components configuration3. Power consumption4. Power supply status5. Number of detected errors per type and component6. Number of recoveries per types and component7. Failed components8. Number of intrusion attacks6.1.1.1.13 Discovery/Composability SPD functionalities• Discovery – provide to the pSHIELD Middleware Adapter the information, raw data, descriptionof available hardware resources and services in order to allow the system composability• Connect/Disconnect – connects or disconnects specific SPD functionalities for systemcomposability6.1.1.1.14 Miscellaneous SPD functionalitiesDepending on the application field, other services are provided, mainly related to the Special PurposeProcessor modules:• Compress/decompress – requests data compression or decompression for local storage orexchange over the network or with peripherals• Configure/calibrate – requests the configuration or calibration of a device attached to the node• Digital Signal Processing – digital signal acquisition and conversion (ADC/DAC)6.1.1.1.15 Node Status• Node Layer Status – provide to the pSHIELD Middleware Adapter the status information fromeach of the modules in Node Layer6.1.1.1.16 Legacy SPD functionalitiesLegacy devices provide SPD functionalities or capabilities through the pSHIELD specific components.Some examples are:• Compress/decompress – requests data compression or decompression for local storage orexchange over the network or with peripherals• Configure/calibrate – requests the configuration or calibration of a device attached to the nodeDigital Signal Processing – digital signal acquisition and conversion (ADC/DAC)6.1.1.2 Intrinsic SPD capabilitiesTo comply with SPD requirements, the pSHIELD Node has some Node Layer intrinsic, architecturalcharacteristics specially designed to provide dependability, security and privacy exclusively at Node layer.PUD2.3.2Issue 5 Page 72 of 122
pSHIELDSystem Architecture DesignPUThis intrinsic SPD capabilities can be configured by the pSHIELD Overlay and composed by the pSHIELDMiddleware Core SPD Services, however they apply autonomously and continuously in the pSHIELDNode.6.1.1.2.1 DependabilityDependability is mainly assured by the Dependability block, the SPD Node Status block and by all thefunctionalities embedded in the other blocks, such as those described in the Node pSHIELD SpecificComponent, providing the status of the module, checkpointing information, self-test and rollback-recovery.If any error is detected by any of the modules, the Dependability block triggers system recovery. TheDependability block itself must be able to detect a self-failure, by having a redundant component, such asa watchdog timer that starts system recovery.Other modules also provide other aspects of dependability, such as the Power Management (powerfailures).There are thus several levels of dependability:• Each module of the pSHIELD Node Adapter has an internal Health Status Module (HSM) thatmonitors its health and periodically sends health status information to the SPD Node Status. TheSPD Node Status sends a periodic Heartbeat containing the global layer status to theDependability module• On error, the HSM may inhibit the monitored module, performing a fail-fast operation. If the SPDNode Status stops receiving status information from one of the HSM or receives error informationor even the information itself is erroneous, it stops the Heartbit. On timeout, the Dependabilitymodule starts a recovery procedure• The SPD Node Status may also perform other health status monitoring operations, such asperforming a Power-On Self-Test• Dependability module itself sends a health status information to the SPD Node Status• If the Dependability module fails, the SPD Node Status halts the system• On permanent failure of one of the modules, the Dependability module may halt the system• The Power Management assures system availability by managing redundant power sources ortriggering a low-power mode if power level is low• The Dependability module contains a Stable Storage, assuring data survivability for rollbackrecoveryThe pSHIELD power node may exhibit advanced recovery and reconfigurability capabilities through partialFPGA reconfiguration 10 . Recent advances in FPGA technology offer the possibility of repairing a failedmodule by reloading the bit stream in the FPGA frames that contained this module 11 . Furthermore, thisFPGA reconfiguration may be used for changing the device functionality during runtime.10“In-Circuit Partial Reconfiguration of RocketIO Attributes”,http://www.xilinx.com/support/documentation/application_notes/xapp662.pdf“Two flows for Partial Reconfiguration: Module Based or Difference Based”,http://www.xilinx.com/support/documentation/application_notes/xapp290.pdf“Dynamic Reconfiguration of RocketIO MGT Attributes”,http://www.xilinx.com/support/documentation/application_notes/xapp660.pdf11Cheatham (portal.acm.org/citation.cfm?id=1142167)PUD2.3.2Issue 5 Page 73 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: 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 71: pSHIELDSystem Architecture DesignPU
show all

System Architecture Design

Create successful ePaper yourself

Delete template?

Save as template?