Architecting IoT Systems. Angelo Corsaro, PhD Chief Technology Officer

Transcription

1 Architecting IoT Systems Angelo Corsaro, PhD Chief Technology Officer

2 Internet of Things Flavours Internet of Things (IoT) is the term used to describe any kind of application that connected and made things interact through the internet It is now clear that there are at least two kinds of IoT, Consumer IoT (CIoT) and Industrial IoT (IIoT) The CIoT and IIoT follow the [Collect Store Analyse Share] architecture, yet they have some key differences that Wikipedia: Interconnection of uniquely identifiable embedded computing-like devices within the existing Internet infrastructure is important to understand

3 Consumer Internet of Things (CIoT) The Consumer Internet of Things (CIoT) represents the class of consumer-oriented applications where: Devices are consumer devices, such as smart appliances, e.g. refrigerator, washer, dryer, personal gadgets such as, fitness sensors, google glasses, etc. Data volumes and rates are relatively low Applications are not mission or safety critical, e.g., the failure of fitness gadget will make you, at worse, upset, but won t cause any harm CIoT applications tend to be consumer centric

4 Industrial Internet of Things (IIoT) The Industrial Internet of Things (IIoT) represents industry-oriented applications where: Devices are machines operating in industrial, transportation, energy or medical environment 1 Data volumes and rates tend to be from sustained to relatively high Applications are mission and or safety critical, e.g. the failure of a smart grid has severe impact on our life and economy, the misbehaving of a smart traffic system can threaten drivers IIoT applications tend to be system centric 1 The list of application domains is supposed to give examples and is not exhaustive

5 ] Copyright PrismTech, 2014 CIoT/IIoT Data Sharing Requirements Efficient and scalable High Individual Data Rates CIoT IIoT Data Sharing is a key High Aggregated Data Volumes requirement of practically any IoT system Low Latency Temporal Determinism The degree of Device-2-Device (D2D) Comms performance and faulttolerance required by the data sharing platform varies across Consumer Device-2-Cloud (D2C) Comms Cloud-2-Cloud (C2C) Comms Bandwidth Efficiency and Industrial Internet Fault-Tolerance on Things applications Transport-Level Security support is key for IIoT Data-Level Security 0,00 0,25 0,50 0,75 1,00 Relative Importance [Ref: A Comparative Study of Data-Sharing Standards for the Internet of Things, Cutter Journal, Dec 2014

6 Cloud Computing Limitations Connectivity to the Cloud is a pre-requisite of cloud computing. - Some IoT systems need to be able to work even when connection is temporarily unavailable or under degraded connection Cloud computing assumes that there is enough bandwidth to collect the data - That can become an overly strong assumptions for Industrial Internet of Things applications Cloud computing centralises the analytics thus defining the lower bound reaction time of the system - Some IoT applications won t be able to wait for the data to get to the cloud, be analysed and for insights to get back [source:

7 Cloud and Analytics, traditionally Device-to-Device Cloud-to-Cloud computed on a cloud, are Device-to-Cloud Collect Store Analyse Share increasingly moving on the Cloud Computing edge to improve scalability and responsiveness The Data Pipeline is Collect Store Analyse Share Fog-to-Cloud executed at different scales, Device-to-Device Collect Store Analyse Share Collect Store Analyse Share Collect Store Analyse Share

8 VORTEX The IoT Data Sharing Platform

9 Introducing Vortex VORTEX is a ubiquitous data sharing platform for the Internet of Things providing scalable end-to-end seamless, efficient, secure and timely data sharing for IoT supporting device, edge, gateways and cloud VORTEX platform coverage, performance and scalability make it the only viable choice from consumer to demanding business critical, industrial, real time, IoT applications Enterprise Systems Application Platform Edge Management/ Telemetry Connectivity/ Transport VORTEX simplifies IT/OT integration, and is the only platform that holistically addresses IT and OT requirements Sensors/ Things/ Devices Ubiquitous Data Sharing peer-to-peer, device-to-cloud, cloud-to-cloud

10 The VORTEX Platform Specialised device implementations optimally addressing requirements of OT and IT platforms VORTEX can readily deal with data ingestion seamlessly integrating with other protocols, e.g. MQTT, CoAP, etc. VORTEX leverages the DDS standard for interoperability and uniquely extends it with support for Internet Scale systems, mobility and Web 2.0 applications PaaS/MaaS

11 Cloud, Fog and Edge Computing VORTEX supports both the Cloud and the Fog Computing Paradigm Device-to-Cloud Device-to-Device Cloud-to-Cloud Cloud Computing VORTEX natively Collect Store Analyse Share supports: - Device-to-Device Device-to-Device Fog-to-Cloud - Device-to-Cloud Collect Store Analyse Share

12 Abstracting Connectivity Device-to-Device Cloud-to-Cloud Device-to-Cloud Cloud Computing Device-to-Device Fog-to-Cloud

13 High Level Abstraction Vortex provides a Distributed Data Space abstraction where applications can autonomously Data Writer Data Reader and asynchronously read and write data Its built-in dynamic discovery isolates applications from network topology and Data Writer Data Writer Topic A QoS Topic C QoS Topic D QoS Topic B QoS... Data Reader Data Reader connectivity details Data Writer Data Reader DDS Data Space is completely DDS Global Data Space decentralised

14 Data Centricity DDS supports the definition of Common Information Models. These data models allow to naturally represent physical and virtual entities characterising the application domain DDS types are extensible and evolvable, thus allowing incremental updates and upgrades

15 Topic A Topic defines a domain-wide information s class A Topic is defined by means of a (name, type, qos) tuple, where name: identifies the topic within the domain struct TemperatureSensor long sid; float temp; float hum; } type: is the programming language type associated with the topic. Types are extensible and evolvable qos: is a collection of policies that express the non-functional properties of this topic, e.g. reliability, persistence, etc. Type Name Topic QoS

16 Content Awareness Vortex knows about application data types and uses this struct TemperatureSensor long sid; float temp; float hum; } TempSensor Type information provide type-safety and content-based routing sid temp hum , temp > 25 OR hum >= 0.6 sid temp hum

17 Quality of Service For data to flow from a DataWriter (DW) Domain Participant joins Domain Id joins Domain Participant to one or many DataReader (DR) a few conditions have to apply: produces-in consumes-from Publisher PARTITION Subscriber The DR and DW domain participants have to be in the same domain RxO QoS Policies DURABILITY The partition expression of the DR s DEST. ORDER Subscriber and the DW s Publisher should match (in terms of regular expression match) DataWriter offered QoS RELIABILITY LATENCY BUDGET DEADLINE OWENERSHIP requested QoS DataReader The QoS Policies offered by the DW LIVELINESS should exceed or match those requested by the DR writes Topic reads

18 Your First Vortex App!

19 Writing Data in Scala import dds._ import dds.prelude._ import dds.config.defaultentities._ object SmartMeter { def main(args: Array[String]): Unit = { val topic = Topic[Meter]( SmartMeter ) val dw = DataWriter[Meter](topic) while (!done) { val meter = readmeter() dw.write(meter) Thread.sleep(SAMPLING_PERIOD) } } } enum UtilityKind { ELECTRICITY, GAS, WATER }; struct Meter { string sn; UtilityKind utility; float reading; float error; }; #pragma keylist Meter sn

20 Reading Data in Scala import dds._ import dds.prelude._ import dds.config.defaultentities._ object ChatLog { def main(args: Array[String]): Unit = { val topic = Topic[Meter]( SmartMeter ) val dr = DataReader[Meter](topic) dr listen { case DataAvailable(_) => dr.read.foreach(println) } } } enum UtilityKind { ELECTRICITY, GAS, WATER }; struct Meter { string sn; UtilityKind utility; float reading; float error; }; #pragma keylist Meter sn

21 Writing Data in C++ #include <dds.hpp> int main(int, char**) { DomainParticipant dp(0); Topic<Meter> topic( SmartMeter ); Publisher pub(dp); DataWriter<Meter> dw(pub, topic); while (!done) { auto value = readmeter() dw.write(value); std::this_thread::sleep_for(sampling_period); } enum UtilityKind { ELECTRICITY, GAS, WATER }; struct Meter { string sn; UtilityKind utility; float reading; float error; }; #pragma keylist Meter sn } return 0;

22 Reading Data in C++ #include <dds.hpp> int main(int, char**) { } DomainParticipant dp(0); Topic<Meter> topic( SmartMeter ); Subscriber sub(dp); DataReader<Meter> dr(dp, topic); enum UtilityKind { ELECTRICITY, GAS, WATER }; struct Meter { string sn; UtilityKind utility; float reading; float error; }; #pragma keylist Meter sn LambdaDataReaderListener<DataReader<Meter>> lst; lst.data_available = [](DataReader<Meter>& dr) { auto samples = data.read(); std::for_each(samples.begin(), samples.end(), [](Sample<Meter>& sample) { std::cout << sample.data() << std::endl; } } dr.listener(lst); // Print incoming data up to when the user does a Ctrl-C std::this_thread::join(); return 0;

23 Deployment Models

24 Fog + Cloud Device-to-Cloud Device communicate peer-to-peer within a fogdomain and through Cloud across fogdomains Peer-to-Peer (Brokerless) Device-to-Device Some device concurrently communicate with peers and the cloud

25 Fog + Cloud-Link + Cloud Device-to-Cloud Device communicate peer-to-peer within a fogdomain Peer-to-Peer (Brokerless) Device-to-Device Cloud-Link Cloud-Link A Cloud-Link controls which data is exchanged with the could

26 Federated Fog Cloud-Link Fog domain are Peer-to-Peer (Brokerless) Device-to-Device federated by Cloud-Link instances Cloud-Link A Cloud-Link controls which data is exchanged with the could

27 Architectures

28 device-to-device VORTEX Enables device-to-cloud device-to-device device-to-cloud Query Storage device-to-device device-to-cloud Compute device-to-cloud Analytics device-to-device

29 device-to-device VORTEX Enables device-to-cloud device-to-device device-to-cloud Query Storage device-to-device device-to-cloud Compute device-to-cloud Analytics device-to-device

30 VORTEX Enables device-to-cloud device-to-device device-to-cloud Query Storage device-to-device device-to-cloud Compute device-to-cloud Analytics device-to-device

31 device-to-device VORTEX Enables device-to-cloud device-to-device device-to-cloud Query Storage device-to-device device-to-cloud Compute device-to-cloud Analytics device-to-device

32 Performance

33 Industry leading performance and scalability VORTEX DEVICE VORTEX CLOUD Peer-to-Peer Intra-core latency as low as 8 µs Routing latency as low as 4 µs Linear scale out Peer-to-Peer latency as low as 30 µs Point-to-Point throughput well over 2.5M msg/sec 44K* msgs/sec with a single router, 4x times more the average Tweets per second in the world (~6000 tweets/sec)! *2048 bytes message payload

34 VORTEX Security

35 Boundary Security Device-to-Cloud TLS Boundary security support is enabled by TLS Cloud-Link Cloud-Link separates Peer-to-Peer (Brokerless) Device-to-Device Cloud-Link Cloud-Link security concerns at different scales and also allows to control what information to expose

36 DDS Security The DDS Security defines a framework for interoperable security with pluggable: - Authentication - Access Control - Crypto - Logging - Tagging

37 Vortex & DDS Security Device-to-Cloud S-DDSI DDS Security makes it possible for Vortex to: S-DDSI Securely interoperate with other DDS implementation Mutual Authentication Secure Multicast Encryption options: User Data User Data + Protocol Header Message Authentication Nothing Hash-based MAC Cloud-Link Cloud-Link Plug user preferred authentication, access, control, and crypto plugin Provide support for Symmetric and Asymmetric authentication as well as secure multicast Separate security domains through Vortex Cloud-Link

38 Demo

39 Cloud Deployed on Linode UK Device-to-Cloud Cloud Analytics Different Networks Different Partitions too. Peer-to-Peer (Brokerless) Device-to-Device Cloud-Link Cloud-Link Edge Analytics Edge Analytics Edge Analytics

40 The VORTEX Platform Specialised device implementations optimally addressing requirements of OT and IT platforms VORTEX can readily deal with data ingestion seamlessly integrating with other protocols, e.g. MQTT, CoAP, etc. VORTEX leverages the DDS standard for interoperability and uniquely extends it with support for Internet Scale systems, mobility and Web 2.0 applications PaaS/MaaS

41