Question: What is the underlining design behind an “Embedded Agent” in relationship to low powered Internet of Things (IoT) edge devices?
Some of the IoT cloud service vendors keep referring to installing an embedded agent on the sensor based edge devices. It appears to be a proprietary piece of software which vendors install on each device connecting to the cloud. Below are two images of software stacks with references to Agent. A portion of the of software stack reside in the microcontroller.
Also here is very broad explanation Thingworx blog
An agent is an embedded program that runs on or near an IoT device and reports the status of some asset or environment. There is always some agent present in an IoT application. Typically the agent reads the status from sensors or local connectivity to an asset, applies some rules or logic about how often the sender has to aggregate the information, and then sends the information over a long-haul communications network to the server. This process can operate in reverse as well.
It is my assumption this agent consist of connectivity information such as IP address, server name, SSID type information to aid connectivity. Does these Embedded Agents have other functionality beyond providing connectivity?