Difference between revisions of "DigitalTwin"
m |
|||
| Line 1: | Line 1: | ||
Digital Twin is emerging as an architedtural pattern for IoT systems | 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 [[ | + | A software compnent in the (Cloud) application platform like AWS or AZURE mimcs the physical deivce. Middelware and elements of an [[IoTPlatform| 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 | 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 connected . May be sleeping. Commands or queries may need to be buffered or queued | ||
Revision as of 02:12, 5 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)
