A device that has a unique identity and connected to a remote host.
A connected thing that has embedded intelligence and connected intelligence (from host) for a specific purpose.
A remote host that has the ability to control the thing, process the generated data.
The thing and the remote host can initiate and communicate to each other.
Things connected to each other via local area network (eg. wifi).
Thing use another thing as a gateway to communicate. Example – Wearable watch connected to smartphone via bluetooth and use smartphone internet connection to reach remote server.
Devices which do not support the IP stack will integrate using an IoT Gateway.
Field side registry (another thing) in the network which has details on all the connected devices which can serve things about the details and capabilities of others.
Leveraging containers such as Docker to provision a new thing with code and it’s software dependencies. It allows to push updates code updates to the thing.
Design devices to periodically send a heartbeat or a keep-alive signal to the IoT Cloud.
Remote processing host
Ability to manage endpoint devices remotely.
Use mechanism such as client certificates for device authorisation.
A device registry provides the capability to keep track of all the deployed devices and their co-ordinates.
Provide a state object which mirrors the state of the device.
Message processing host
Stream of data from things generate massive volume of data. Needs distributed message processing system at the host side.
Provide an ability to process data streams in real-time based on set business rules.
Ability to extract meaningful data, store them into data mart and deliver them to consumers via channels such as dashboard, alerts, etc.
- What are IOT design patterns