The M2M device/gateway basically includes the device application, connectivity module, one or more sensors, and connection agent.
The connection agent plays the role of the connectivity client for the M2M service platform server and also provides the functionality of protocol adaptation layer required to translate the data format between the different protocols.
The algorithm is implemented in a grid-connected power converter that acts as an intelligent connection agent (ICA).
➢ This process configures the connection agent to start periodically polling the device.
For instance, the connection agent is responsible for interacting with the sensor module over an internal API and periodically polling it to retrieve measurements from the M2M device.
➢ If it is online, it simply routes the command to the right connection agent, which deploys the configuration changes to the device via the internal API.
As mentioned above, communication between the service platform and the device is made possible by the deployment of a connection agent and protocol mapper blocks on the device and MCM subsystem, respectively.
Using your mobile phone as identity carrier, connection agent and remote control you can gain access to your files in the cloud (videos and pictures on Youtube, Facebook, Flickr etc)., pay-TV channels, rented or purchased movies and any other content you have right to access.
Using your mobile phone as identity carrier, connection agent and remote control you can gain access to your files in the cloud (videos and pictures on Youtube, Facebook, Flickr etc.), pay-TV channels, rented or purchased movies and any other content you have right to access.
As to the integration of effort, the connection among agents within a DEE is important.
