In order to ensure the device-level interoperability in IoT where two devices with different communication protocols can talk to each other, different solutions exist utilizing either server, broker, middleware, or gateways. Can someone highlight the difference between these when used in IoT?
You can define IoT as the Internet of Things, with several views of the same system.
First the IoT devices, building a system,for instance cameras and sensors at different places of a forest to detect a wildfire starting and raise alarms. This gives a map of devices and locations.
The devices connect to a network, and through the network those devices can be supervised and relevant data and alarms get uploaded to a forest fire supervision center.
In a second view, you have nodes and a network graph linking these nodes, abstracting the devices and the system comprising these devices. Each node has three functionalities in it: (1)network (access), (2)data (acquisition, handling), (3)compute (processing data locally, for instance extracting from measurements if the local temperature exceeds a threshold making the start of a fire likely).
This also assumes power supplied to the node (battery, solar panel or other energy harvesting,etc)
Let us now come to your question:
the fire supervision center may be a server, the nodes can act as mini-servers or just clients, and the software running on them as middleware for the data aspects.
Other software runs for system supervision,ensuring that every node runs adequately, and reports to the system supervision center where devices and software is managed.
If you want more details, please describe your use case.
I hope that the above helps you structure your approach.
You can define IoT as the Internet of Things, with several views of the same system.
First the IoT devices, building a system,for instance cameras and sensors at different places of a forest to detect a wildfire starting and raise alarms. This gives a map of devices and locations.
The devices connect to a network, and through the network those devices can be supervised and relevant data and alarms get uploaded to a forest fire supervision center.
In a second view, you have nodes and a network graph linking these nodes, abstracting the devices and the system comprising these devices. Each node has three functionalities in it: (1)network (access), (2)data (acquisition, handling), (3)compute (processing data locally, for instance extracting from measurements if the local temperature exceeds a threshold making the start of a fire likely).
This also assumes power supplied to the node (battery, solar panel or other energy harvesting,etc)
Let us now come to your question:
the fire supervision center may be a server, the nodes can act as mini-servers or just clients, and the software running on them as middleware for the data aspects.
Other software runs for system supervision,ensuring that every node runs adequately, and reports to the system supervision center where devices and software is managed.
If you want more details, please describe your use case.
I hope that the above helps you structure your approach.
A SERVER is a master in a situation where we have a master/slave relationship between IoT devices and legacy systems (SCADA). In such a situation, a server could be a legacy database running on a legacy system, which only say transmit data in pure serial format and uses protocols not compatible with IPv6. In such a situation, IoT devices may not directly transfer data (say the reading of temperature, which could be read by different sensors made by different vendors - this means the data format would be different) to the server. It may use IoT Data BROKER in order to ensure the transfer of data. An IoT data broker is a piece of middleware that standardizes sensor output into a common format that can then be retrieved by authorized applications.
- Badges
- Science topic