About Acklio FullSDK
Read the Acklio FullSDK section for prior information on the role and functioning of the SDK, including diagrams of the layer organization and the communication sequences.
Acklio FullSDK Role​
The role of Acklio FullSDK is to enable the SCHC compression and fragmentation mechanisms on device side, either by being fully embedded into an AT modem application that receives messages from an UDP client, or by being deployed on the device directly.
See our Demo Examples:
- AT Modem UDP Client and AT Modem DLMS using Gurux for a deployment on an AT Modem application;
- FreeRTOS UDP Client Server for a deployment on a stand-alone device.
Acklio FullSDK Layer Integration​
Acklio FullSDK integrates with both the underlying LPWAN technology and the upper application layer.
The configuration of Acklio FullSDK at runtime, the exchange of packets or the adaptation with the Level2 layer are tasks assumed by interfaces, each provided in a dedicated header file.
See Layers and interfaces for diagrams and detailed information.
Acklio FullSDK Paradigm​
One major structuring requirement for the Acklio FullSDK is the ability to support low power modes. Consequently, its implementation allows it to be fully integrated in an event-driven environment.
- When an event concerning the Acklio FullSDK occurs (e.g., reception of data, timeout, etc.), the application layer is informed by a callback.
- Then, the application decides whether to let the Acklio FullSDK process the event or not. If yes, it calls a dedicated function.
- Once an event has been processed (the function has returned), the Acklio FullSDK does nothing more.