Difference between revisions of "Architecture"
ArvindIOTF (talk | contribs) m (→Scenarios) |
(→See Also) |
||
| (29 intermediate revisions by 4 users not shown) | |||
| Line 6: | Line 6: | ||
The [https://en.wikipedia.org/wiki/Unified_Modeling_Language| UML] specifies component, package, deployment and interaction views among others. | The [https://en.wikipedia.org/wiki/Unified_Modeling_Language| UML] specifies component, package, deployment and interaction views among others. | ||
| − | == | + | == IoTStack == |
| − | IoT | + | IoT system components use ''constrained devices'' with much less functionality then computers. IEEE and other standards use many terms and this is a quick layman's intro to some of them. IoT Devices fall into ''Full Function Device'' (FFD) like a Linux based TV Set top box or CCTV device, ''Reduced Function Device'' (RFD) like a pollution sensor which does not do ISO layer 2 routing and Limited Function device(LFD) which are motes or smart dust of the wireless sensor network (WSN). IoT Lite-OS like Contiki run on micrcontrollers with full UDP stack under 32Kb of memory. |
;Motes | ;Motes | ||
:Motes<ref>https://computer.howstuffworks.com/mote.htm</ref> are limited function devices (LFD) with sensors and/or actuators and very small memory (32 Kb ) and small compute capacity ( 8 or 16 bit micro controller) and may use energy harvesting techniques( Solar etc) or be passive (RFID) or be battery powered typically for a year or more. | :Motes<ref>https://computer.howstuffworks.com/mote.htm</ref> are limited function devices (LFD) with sensors and/or actuators and very small memory (32 Kb ) and small compute capacity ( 8 or 16 bit micro controller) and may use energy harvesting techniques( Solar etc) or be passive (RFID) or be battery powered typically for a year or more. | ||
| Line 29: | Line 29: | ||
The data formats range from fixed field records (Modbus) to XML style ( HTML, XMPP) over Rest API calls and binary JSON over MQTT. | The data formats range from fixed field records (Modbus) to XML style ( HTML, XMPP) over Rest API calls and binary JSON over MQTT. | ||
;IoTPlatfrom | ;IoTPlatfrom | ||
| − | A component tightly coupled with the gateway and managing south side IoTNetworks and devices and interfacing with north side Internet and cloud See [[ | + | A component tightly coupled with the gateway and managing south side IoTNetworks and devices and interfacing with north side Internet and cloud See [[IoTPlatform]] |
;Touch-points | ;Touch-points | ||
IoT assume machine to machine communication (M2M). A variety of touchpoints from HTML pages, voice (Amazon Alexa), SMS , email, twitter and whatsApp based interaction, chatbots and API based machine interaction are expected. | IoT assume machine to machine communication (M2M). A variety of touchpoints from HTML pages, voice (Amazon Alexa), SMS , email, twitter and whatsApp based interaction, chatbots and API based machine interaction are expected. | ||
| Line 35: | Line 35: | ||
Typically in modern system the application provides a user interface (UI) over HTML or a front end Smartphone App. | Typically in modern system the application provides a user interface (UI) over HTML or a front end Smartphone App. | ||
These require a micro-service based server side or user interface less applications. There are new concerns of authentication and authorization and security in this scenario and bots and devices must have thier own identity in the software. The concept of [[UsersWiki!:DigitalTwin|''Digital Twin'']] is emerging as a paradigm. | These require a micro-service based server side or user interface less applications. There are new concerns of authentication and authorization and security in this scenario and bots and devices must have thier own identity in the software. The concept of [[UsersWiki!:DigitalTwin|''Digital Twin'']] is emerging as a paradigm. | ||
| + | |||
| + | ==Historical Transition== | ||
| + | In the old non IoT world we have over 2 decades seen some experimentation from local single user or host based computing to client server , flirted with thin computing and the current dominance of web based. The web approach seems to be a good partioning between roles and capability with presentation being delgated to endpoint devices and server managing data and logic. | ||
| + | |||
| + | [[File:TraditionalComputing ioTStack Arvind.png| Traditional Computing]] | ||
| + | |||
| + | The IoT paradigm intially built on the web application concept ( Traditional IoT) but has splintered into variations.Terms are not standerdized but here is one representation. | ||
| + | |||
| + | |||
| + | [[File:IoTComputing IoTStack Arvind.PNG| Edge, Fog and IoT]] | ||
| + | |||
| + | :Autonomus drones inspecting the chimmeny of a steel plant or a robot checking a nuclear plant operate in hostile environment. They may work semi autonomously with no connectivty and a pre planned mission. This is ''"EndPoint Computing"''. When the gateway can host the application and complete the transaction we have an example of [https://en.wikipedia.org/wiki/Edge_computing ''Edge computing''].In these cases the local gateway and /or device can complete the application processing. [https://www.webopedia.com/TERM/F/fog-computing.html ''Fog computing''] implies multiple places where computing happens and may be on gateway, on premise servers as well as cloud servers. | ||
| + | |||
| + | Broadly significant work is being taken away from cloud or back-end server application to IoTPlatforms or to gateways. Fog computing is being seen in many scenarios. | ||
| + | |||
==Examples== | ==Examples== | ||
The telco world has long broken functionality and features as | The telco world has long broken functionality and features as | ||
| Line 42: | Line 57: | ||
:Business System Support covering billing etc | :Business System Support covering billing etc | ||
| − | in IoT systems a | + | in IoT systems a similar differentiation has not yet become common and depending on purpose we see fluid intermixing of physical components, software functionality (Modules or sub systems) and horizontal concerns like security and trust. |
=== Context in IoT === | === Context in IoT === | ||
| Line 48: | Line 63: | ||
[http://www.infoq.com/articles/internet-of-things-reference-architecture Infoq ] has a deep apporach to building context for intelligent devices | [http://www.infoq.com/articles/internet-of-things-reference-architecture Infoq ] has a deep apporach to building context for intelligent devices | ||
https://cdn.infoq.com/statics_s2_20171017-0336-1/resource/articles/internet-of-things-reference-architecture/en/resources/32.jpg | https://cdn.infoq.com/statics_s2_20171017-0336-1/resource/articles/internet-of-things-reference-architecture/en/resources/32.jpg | ||
| + | |||
| + | ===Anatomy of IoT=== | ||
| + | [https://dzone.com/articles/the-anatomy-of-an-iot-solution Hans Vissar overview] | ||
| + | |||
| + | https://www.mendix.com/wp-content/uploads/Artboard-1SAP.png | ||
| Line 60: | Line 80: | ||
Naveen Balani at Accenture has proposed an [http://naveenbalani.com/index.php/articles/enterprise-internet-of-things-stack-and-architecture/ Enterprise IoT Architecture] | Naveen Balani at Accenture has proposed an [http://naveenbalani.com/index.php/articles/enterprise-internet-of-things-stack-and-architecture/ Enterprise IoT Architecture] | ||
http://naveenbalani.com/wp-content/uploads/2016/09/Nbx1-1024x792.png | http://naveenbalani.com/wp-content/uploads/2016/09/Nbx1-1024x792.png | ||
| + | |||
| + | === [https://www.linkedin.com/pulse/iot-technology-tree-aleksander-poniewierski/ EY IoT Tree]=== | ||
| + | https://media.licdn.com/mpr/mpr/AAEAAQAAAAAAAAqZAAAAJDUzZDQ0ZGM1LWYxYTctNDViNS04YjJhLTQ4MTY2MTRkZDYwOQ.jpg | ||
=== DataIntegration === | === DataIntegration === | ||
| Line 75: | Line 98: | ||
http://www.ibmbigdatahub.com/sites/default/files/public_images/Screen%20Shot%202017-01-24%20at%209.19.32%20AM.png | http://www.ibmbigdatahub.com/sites/default/files/public_images/Screen%20Shot%202017-01-24%20at%209.19.32%20AM.png | ||
| − | <pre>IBM distinguishes by IoTNetwork ( proximity network) , Public Internet and Provider on premise network.</pre> | + | <pre>IBM distinguishes by IoTNetwork ( proximity network) , Public Internet and Provider on premise network.</pre> |
| + | |||
| + | The Cosultancy Zinnov has a CXO level view of IoT Architecture | ||
| + | |||
| + | https://image.slidesharecdn.com/zinnovzonesiotservicesmediareport-160824060809/95/zinnov-zones-for-iot-services-2017-3-1024.jpg | ||
=== Eclipse 3 layer === | === Eclipse 3 layer === | ||
| Line 85: | Line 112: | ||
http://15809-presscdn-0-93.pagely.netdna-cdn.com/wp-content/uploads/EXF_Platform-Architecture-2-1024x603.png | http://15809-presscdn-0-93.pagely.netdna-cdn.com/wp-content/uploads/EXF_Platform-Architecture-2-1024x603.png | ||
| − | The proposed edJe for constrained devices ( 32bit,32KB RAM,128KB Flash device) uses light weight virtual container approach. The [https://jaxenter.com/a-simple-way-to-look-at-eclipse-iot-125477.html Eclipse Jaxenter project] is among a number of Open Source projects underway. They explcitly support WeMo Lifx, HomeKIt at Router, south | + | The proposed edJe for constrained devices ( 32bit,32KB RAM,128KB Flash device) uses light weight virtual container approach. The [https://jaxenter.com/a-simple-way-to-look-at-eclipse-iot-125477.html Eclipse Jaxenter project] is among a number of Open Source projects underway. They explcitly support WeMo Lifx, HomeKIt at Router, south bound field Protocol for devices, northbound Internet MQTT etc. |
<pre>This trend sees IoTPlatform functionality of bridging several different networks migrating to the gateway and the cloud IoT platform like Amazon AWS and Microsft Azure can concentrate on Digital Twin based functionality.</pre> | <pre>This trend sees IoTPlatform functionality of bridging several different networks migrating to the gateway and the cloud IoT platform like Amazon AWS and Microsft Azure can concentrate on Digital Twin based functionality.</pre> | ||
| Line 91: | Line 118: | ||
A deployment oriented architecture from a multi vendor mix and match approach for SmartCity etc. Distinguishes application from touch-points and gateway less use cases where device connects directly to (cloud) application. | A deployment oriented architecture from a multi vendor mix and match approach for SmartCity etc. Distinguishes application from touch-points and gateway less use cases where device connects directly to (cloud) application. | ||
| − | [[File:IoT_Roles_and_Stack_ioTStack_Arvind.png]] | + | [[File:IoT_Roles_and_Stack_ioTStack_Arvind.png|link=https://www.linkedin.com/pulse/iot-interoperability-using-simple-architecture-arvind-tiwary/]] |
== Scenarios == | == Scenarios == | ||
The many different use-cases with different requirements and constraints lead to many different way to slice and dice the system A nice visualization of options is provided by [https://exosite.com/ ExoSite] | The many different use-cases with different requirements and constraints lead to many different way to slice and dice the system A nice visualization of options is provided by [https://exosite.com/ ExoSite] | ||
| − | + | [[File:Deployment options IoTStack Arvind.jpg|850px| Deployment Options]] | |
| − | |||
==See Also== | ==See Also== | ||
| − | https://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/ | + | *[[UsersWiki!IoTPlatform|IoTPlatform]] |
| − | http://internetofthingsagenda.techtarget.com/feature/Using-an-IoT-gateway-to-connect-the-Things-to-the-cloud | + | *[http://34.205.35.2/fog-iot/ Do not let the fog hide the clouds in the Internet of Things] |
| − | https://www.slideshare.net/IanSkerrett/3-software-stacks-for-iot-solutions | + | *[[Fog Computing]] |
| + | *[https://standards.ieee.org/content/ieee-standards/en/standard/2413-2019.html 2413-2019 - IEEE Approved Draft Standard for an Architectural Framework for the Internet of Things (IoT)] | ||
| + | *[https://www.iiconsortium.org/IIC_PUB_G1_V1.80_2017-01-31.pdf Reference Architecture - Industrial Internet Consortium] | ||
| + | *[https://www.etsi.org/technologies/internet-of-things ETSI IoT M2M Standards | ||
| + | *[https://www.postscapes.com/internet-of-things-protocols/ IoT Standards and Protocols] | ||
| + | *[https://negd.gov.in/india-enterprise-architecture India Enterprise Architecure IndEA] | ||
| + | |||
| + | *https://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/ | ||
| + | *http://internetofthingsagenda.techtarget.com/feature/Using-an-IoT-gateway-to-connect-the-Things-to-the-cloud | ||
| + | *https://www.linkedin.com/pulse/iot-interoperability-using-simple-architecture-arvind-tiwary/ | ||
| + | *[[UsersWiki!:DigitalTwin|Digital Twin]] | ||
| + | *https://www.slideshare.net/IanSkerrett/3-software-stacks-for-iot-solutions | ||
| + | *[https://medium.com/@costastselios/iot-patterns-managed-iot-data-services-350c17df2d8b IoT Patterns — Managed IoT Data Services ] | ||
| + | |||
| + | |||
| + | [[Category:IoTStack]] | ||
Latest revision as of 15:56, 2 November 2020
System Architecture or Software Architecture for IoT is an evolving story as it covers heterogeneous devices and use cases from closed loop near real time process control, automotive to sporadic SmartCity pollution measurements and very dense urban deployment of Smartdevices for electric grid and street lighting etc.There are many proposed reference architecture for IoT. They vary by purpose ( Analytics Dash-boarding, Device management,M2M Standard bodies) and scope (Cloud or SmartCity).
Architecture is broadly about two ideas
- The components of a system that provide the function being delivered. This is a structural view and may involve many layers with each component have a similar blowup
- The interaction, protocols and evolution of the individual components in the usage of the system. This may also be a normative or presciptive specification using standards
The UML specifies component, package, deployment and interaction views among others.
Contents
IoTStack[edit]
IoT system components use constrained devices with much less functionality then computers. IEEE and other standards use many terms and this is a quick layman's intro to some of them. IoT Devices fall into Full Function Device (FFD) like a Linux based TV Set top box or CCTV device, Reduced Function Device (RFD) like a pollution sensor which does not do ISO layer 2 routing and Limited Function device(LFD) which are motes or smart dust of the wireless sensor network (WSN). IoT Lite-OS like Contiki run on micrcontrollers with full UDP stack under 32Kb of memory.
- Motes
- Motes<ref>https://computer.howstuffworks.com/mote.htm</ref> are limited function devices (LFD) with sensors and/or actuators and very small memory (32 Kb ) and small compute capacity ( 8 or 16 bit micro controller) and may use energy harvesting techniques( Solar etc) or be passive (RFID) or be battery powered typically for a year or more.
- Gateway or Hubs
- These take part in packet routing and typically are Linux based devices. Android based smartphones are also emerging as a option. Hubs are used in mesh networks and route packets using same radio and protocols as they receive . 802.15.4based Zigbee and new Bluetooth 5 use mesh approach. Gateway typically connect to the Internet on one side(north side) and may connect to non internet based networks on the other (south ) side.
- IoTNetworks
A vast range of methods and protocols are used to connect endpoints. The academic literature call them capillary networks and other terms like proximity networks or field networks and south side networks are also used. In this note we use the newer term IoTNetwork. Some examples of the over 200
- wired
- RS 232 / RS485 based Modbus
- Fieldbus using industrial Ethernet
- OPC now migrating to wireless
- wireless
- WiFi and extensions like HaLow
- IEEE 802.15.4 based Zigbee, 6LowPAN based Thread
- (Wireless HART)
- ISA100
- Cellular (M2M) covering 1G, 2G ,3G
- LPWAN
- BLE
- Middelware & Data Formats
The data formats range from fixed field records (Modbus) to XML style ( HTML, XMPP) over Rest API calls and binary JSON over MQTT.
- IoTPlatfrom
A component tightly coupled with the gateway and managing south side IoTNetworks and devices and interfacing with north side Internet and cloud See IoTPlatform
- Touch-points
IoT assume machine to machine communication (M2M). A variety of touchpoints from HTML pages, voice (Amazon Alexa), SMS , email, twitter and whatsApp based interaction, chatbots and API based machine interaction are expected.
- Server Applications
Typically in modern system the application provides a user interface (UI) over HTML or a front end Smartphone App. These require a micro-service based server side or user interface less applications. There are new concerns of authentication and authorization and security in this scenario and bots and devices must have thier own identity in the software. The concept of Digital Twin is emerging as a paradigm.
Historical Transition[edit]
In the old non IoT world we have over 2 decades seen some experimentation from local single user or host based computing to client server , flirted with thin computing and the current dominance of web based. The web approach seems to be a good partioning between roles and capability with presentation being delgated to endpoint devices and server managing data and logic.
The IoT paradigm intially built on the web application concept ( Traditional IoT) but has splintered into variations.Terms are not standerdized but here is one representation.
- Autonomus drones inspecting the chimmeny of a steel plant or a robot checking a nuclear plant operate in hostile environment. They may work semi autonomously with no connectivty and a pre planned mission. This is "EndPoint Computing". When the gateway can host the application and complete the transaction we have an example of Edge computing.In these cases the local gateway and /or device can complete the application processing. Fog computing implies multiple places where computing happens and may be on gateway, on premise servers as well as cloud servers.
Broadly significant work is being taken away from cloud or back-end server application to IoTPlatforms or to gateways. Fog computing is being seen in many scenarios.
Examples[edit]
The telco world has long broken functionality and features as
- OSS
Operations System Support covering the network provisioning and management and uptime support
- BSS
- Business System Support covering billing etc
in IoT systems a similar differentiation has not yet become common and depending on purpose we see fluid intermixing of physical components, software functionality (Modules or sub systems) and horizontal concerns like security and trust.
Context in IoT[edit]
Infoq has a deep apporach to building context for intelligent devices
Anatomy of IoT[edit]
IIOT Architecture[edit]
Jonas Berge focuses on Industrial IoT and interoperability and talks about a data diode controlling control plane and providing security.
Enterprise IoT Architecture[edit]
Naveen Balani at Accenture has proposed an Enterprise IoT Architecture
EY IoT Tree[edit]
DataIntegration[edit]
Eurotech Everywhere device cloud uses data aggregation layer
Functional IoT Architecture[edit]
Machnation Functional Architecture
- IBM Data Analytics has a niche architecture for IoT based analytics
IBM distinguishes by IoTNetwork ( proximity network) , Public Internet and Provider on premise network.
The Cosultancy Zinnov has a CXO level view of IoT Architecture
Eclipse 3 layer[edit]
Gateway[edit]
Linux EdegeX Foundry for gateways .
The proposed edJe for constrained devices ( 32bit,32KB RAM,128KB Flash device) uses light weight virtual container approach. The Eclipse Jaxenter project is among a number of Open Source projects underway. They explcitly support WeMo Lifx, HomeKIt at Router, south bound field Protocol for devices, northbound Internet MQTT etc.
This trend sees IoTPlatform functionality of bridging several different networks migrating to the gateway and the cloud IoT platform like Amazon AWS and Microsft Azure can concentrate on Digital Twin based functionality.
IoTForum[edit]
A deployment oriented architecture from a multi vendor mix and match approach for SmartCity etc. Distinguishes application from touch-points and gateway less use cases where device connects directly to (cloud) application.
Scenarios[edit]
The many different use-cases with different requirements and constraints lead to many different way to slice and dice the system A nice visualization of options is provided by ExoSite
See Also[edit]
- IoTPlatform
- Do not let the fog hide the clouds in the Internet of Things
- Fog Computing
- 2413-2019 - IEEE Approved Draft Standard for an Architectural Framework for the Internet of Things (IoT)
- Reference Architecture - Industrial Internet Consortium
- [https://www.etsi.org/technologies/internet-of-things ETSI IoT M2M Standards
- IoT Standards and Protocols
- India Enterprise Architecure IndEA
- https://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/
- http://internetofthingsagenda.techtarget.com/feature/Using-an-IoT-gateway-to-connect-the-Things-to-the-cloud
- https://www.linkedin.com/pulse/iot-interoperability-using-simple-architecture-arvind-tiwary/
- Digital Twin
- https://www.slideshare.net/IanSkerrett/3-software-stacks-for-iot-solutions
- IoT Patterns — Managed IoT Data Services
