Difference between revisions of "DigitalTwin"
ArvindIOTF (talk | contribs) m (→ToDo) |
ArvindIOTF (talk | contribs) m (→ToDo) |
||
| Line 7: | Line 7: | ||
| − | == | + | ==Also see== |
*[https://www.forbes.com/sites/janakirammsv/2017/10/30/the-role-of-device-twins-in-designing-industrial-iot-solutions/#6b86c26320ac The Role Of Device Twins In Industrial IoT Solutions] | *[https://www.forbes.com/sites/janakirammsv/2017/10/30/the-role-of-device-twins-in-designing-industrial-iot-solutions/#6b86c26320ac The Role Of Device Twins In Industrial IoT Solutions] | ||
*[https://www.ge.com/digital/industrial-internet/digital-twin GE] | *[https://www.ge.com/digital/industrial-internet/digital-twin GE] | ||
Revision as of 14:12, 13 November 2017
Digital Twin is emerging as an architedtural pattern for IoT systems A software compnent in the (Cloud) application platform like AWS or AZURE mimcs the physical deivce. Middelware and elements of an IoT Platform synchronize the state of the physical device and the representation in the cloud platform. This synchronization is not a trivial issue and needs to consider
- The device may not be connected . May be sleeping. Commands or queries may need to be buffered or queued
- The device may not be directly addresable ( non static IP address )
- The device may not be on a IP network (BLE)
