Editing Architecture
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
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. | ||
− | == | + | == IoT System Components == |
− | IoT | + | IoT systems 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 63: | 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 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 80: | Line 75: | ||
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 | ||
− | |||
− | |||
− | |||
=== DataIntegration === | === DataIntegration === | ||
Line 129: | Line 121: | ||
*[http://34.205.35.2/fog-iot/ Do not let the fog hide the clouds in the Internet of Things] | *[http://34.205.35.2/fog-iot/ Do not let the fog hide the clouds in the Internet of Things] | ||
*[[Fog Computing]] | *[[Fog Computing]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
*https://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/ | *https://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/ | ||
Line 140: | Line 127: | ||
*[[UsersWiki!:DigitalTwin|Digital Twin]] | *[[UsersWiki!:DigitalTwin|Digital Twin]] | ||
*https://www.slideshare.net/IanSkerrett/3-software-stacks-for-iot-solutions | *https://www.slideshare.net/IanSkerrett/3-software-stacks-for-iot-solutions | ||
− | |||
[[Category:IoTStack]] | [[Category:IoTStack]] |