In centralized IoT architecture, all the sensor data is processed at the cloud and requires each embedded smart devices to adopt various Message Transfer Protocols like HTTP, MQTT, LWM2M, CoAP, TR-069/TR-369.
Each of embedded low power devices mostly has low processing MCUs that operates at low frequency and low memory footprint and may not support all Message Transfer Protocols.
Majority of these embedded devices support at least TCP Socket communication layers provided natively by embedded RTOSs.
With TCP Socket communication, these embedded devices can very well send sensor data inTCP packets in Raw or TLS secured data format to TCP middleware servers.
If we can offload these embedded device’s Message Transfer Protocol engines in single TCP middleware server for all of deployed embedded devices, the customers can very well manage their deployed devices and move between different Message Transfer Protocols as per their end Application requirements without changing the embedded device’s firmware.
The current version of TUNE, supports HTTP message transfer protocol with End Application Servers.
The TUNE – TCP Middleware Server can be deployed on-premises, private cloud or public cloud.
The TUNE server can also be used as TCP Server Simulator for embedded devices firmware development and testing.
With TUNE deployed at on-premises/private cloud of customers, thousands of IoT devices of customers can be managed well and inventory of devices can be known well.
The external security attack can be restricted to this middleware server instead of each embedded device.