Flex4Apps WP5 D5.1: Platform Architecture & Integration COVER PAGE SUBTITLE PLACEHOLDER COMPANY CONFIDENTIAL
Flex4Apps – Introduction Situation : Many sensors produce large data amounts Challanges for future systems : – Extract the important information fast – React quickly to anomalies – Reveal hidden correlations – Keep data secure Solution : Flex4Apps - Smart system connecting multiple sensors to the cloud – The Flex4Apps platform architecture shall monitor, analyze and hence utilize Big Data (technologies). NXP target : – The project requires an efficient and flexible end-to-end security concept. – For instance, common Plug & Play concepts could be upgraded to industrial Plug & Trust systems by introducing automatic authentication and secure data transmission methods. 2
Application Scenarios for Flex4Apps Use Case Domain Sensors Real-time adapted Security consideration sensor usage Elderly house healthcare Heart rate, Priority sensor reading Personal privacy glucose for sensors on critical monitoring, persons breath rate, oxygen level, … Building Automation Personal, Temperature, Priority transmission on External interference on enterprise humidity, gas suspect sensor data Sensor network must not be the composition, allows for targeted ‘open window’ to vital networks in noise, … setting of building the building controls Factory Monitoring Industry Temperature, Early warning for shift in Competition insight in factory pressure, machinery settings. status chemical Machinery data must be composition… guaranteed to be correct for proper feedback. Network Monitoring Industry Network Use network optimally Information on functioning of elements by knowledge of status network elements must not be providing log on network elements open. data, status info 3
Architecture Considerations Observations: – Solutions nowadays are heterogeneous Processing, analysis Commissioning, dev. authentication, connectivity Presentation – With different deployment of applied security IP – With variety of sensors/actors used Device Cloud Services Presentation & (basic On/Off up to smart with business connectivity identification, en/decryption, etc.) API – Neither simple nor standalone - turning Start a task process one gear may trigger unexpected behavior in one or many unexpected extract areas and unexpected locations. information from data logs – Companies want quick return on invest IP security follows functionality. Cloud F Device Gateway do complex computations System topologies: Non-IP check events for Field – Generally follow the architecture Device priority Gateway shown on the right site build final data 6LoWPAN storage IP Device Next generation solutions need to be architecture conscious – key hole surgery is envisaged. A minimal invasive change shall lead to a Field Cloud maximum result. 4
Flex4Apps Use Cases Telecommunication Architecture NXP challenge in the Flex4apps NE Cloud Cloud Cloud Store Processing Presentatio n Trace project: To add security to a Cloud Gateway Push Trace Pull Pull S S Flex4Apps framework: Log Trace Entries ... – With minimum invasive changes in Trace existing systems? Home-Automation Architecture – With user determined protection Flat Cloud Cloud Cloud mechanisms to prevent data loss / Sensor Microserver Store Processing Presentatio Gateway ... Flat n S theft? Cloud Gateway Sensor Pull Pull Pull S – To adjust security levels of data Push Push Flat transfers with respect to priority Sensor Microserver Gateway ... S Flat and content Sensor Field Cloud - Interface examples for secured data communication S 5
Architectures 6.
Architecture overview Cyber physical system Cloud Device (sensor, actor) Aggregator Communicator staging storage processing presentation build final data Get item from Start a task storage storage process extract Visualize items Microserver Evermind FlatGateway information from data logs communication do complex computations check events for Adapter Adapter priority Receives information for futher processing Nokia NE Collects data / acts uppon commands Manages devices, Can aggregate data Receives data in any form Logic which transforms information database Visualizes information to little to no dedicated intelligence gathers information Sets priorities on communication or shape and holds it for data into information become knowledge Must ensure confidentially / integrity further processing communication communication communication communication comm comm communication communication 7.
Structure of the architecture document 2. Architecture 1. Introduction – Short description of FLex4Apps – Overview – Overview of the document – Cloud – Glossary and abbreviations • Staging – References – Conventions • Storage 3. Dynamic behavior of the • Processing architecture • Presentation – Workflows – Cyber Physical devices – Sequences • Devices 4. Reasons for the architecture • Aggregator – System architecture capabilities • Communicator – Network architecture capabilities – Risk analysis • Customer business logic – Security 5. Requirements traceability – Software COTS 8.
Recommend
More recommend
