Kerlink Light Weight Device management (LWDM) of LoRa connected endpoints

Forums IoTStack News (IoTStack) Kerlink Light Weight Device management (LWDM) of LoRa connected endpoints

Viewing 0 reply threads
  • Author
    Posts
    • #21515
      Curator 1 for Blogs
      Keymaster
      • Topic 369
      • Replies 5
      • posts 374
        @curator1

        Kerlink will demonstrate its new device-management service for simultaneously configuring and updating devices connected to the Internet of Things at the 8th LoRa Alliance All Members Meeting*.

        Device management (DM) of IoT-connected endpoints is a challenging and vital feature for companies that increasingly depend on the IoT to streamline their operations or generate new revenue streams for their business. With billions of sensors, accelerometers, actuators and other devices expected to be connected to the IoT in the future, remotely updating software and firmware, adding new functionality, installing applications, and configuring, monitoring or provisioning devices is key to maintaining their efficient, responsive performance.

        Although Low Power Wide Area (LPWA) networks offer lower data rates than traditional cellular technologies, or have to follow specific duty-cycle limitations inherent in the unlicensed spectrum (ISM band), device management is a vital part of the services that will shortly be proposed for public or private operators to update their fleets of IoT devices that are connected to those networks.

         

        The simulated device update at the LoRa Alliance™ meeting will combine Kerlink’s standalone Wanesy Small Private Network (SPN) server installed in the company’s latest-generation Wirnet iFemtoCell 915 MHz indoor base station, and connected Wirgrid Reference Designs for energy meters. It will illustrate with a concrete example the ability to master and execute the most challenging and key firmware-update operations:

        • Reading the device’s existing configuration and checking its current firmware version
        • Scheduling the firmware download to ensure that the endpoint will temporary be in a listening and data-reception mode (class C – downlink) on a specific shared schedule (RX Windows)
        • Executing the file broadcast and download, once devices wake up as planned
        • Verifying the complete download, and confirming that the device can switch to the new firmware without regression or incompatibility risk.
    Viewing 0 reply threads
    • You must be logged in to reply to this topic.