Arm Pelion Device Management Release

The secure management of IoT devices at scale is the hardest aspect of IoT deployments. In the latest release of Pelion Device Management, we are providing additional features to enable constrained IoT devices, that operate in more challenging network scenarios, with additional hardware and security support.

Key features of this release include:

  • Delta Update that significantly reduces the amount of data transmitted during software updates.
  • Secure Device Access bringing enterprise security to devices in the field.
  • Pelion Device Management Client support for constrained networks and new hardware.
  • Seamless integration with the latest Mbed OS version 5.14 helping customers and partners archive faster time to market and lower development costs.
  • Compressed software update images to support constrained devices – using Pelion delta update

    The ability to update a device’s software remotely is fundamental for managing IoT devices throughout their lifecycle. Traditional software updates require the device to download a complete image containing the OS (or its components) and the application, which consumes lots of device battery power. Additionally, when deploying at scale, a traditional update requires sending large update files to many devices, consuming lots of bandwidth.

    Pelion Delta Update compresses by removing redundant information. A delta update image only contains the differences between the old and new image.

    Extensive testing shows Pelion Delta Update is over 80% more efficient when compressing images in typical scenarios, resulting in a software update process consuming significantly less network bandwidth during the software update process. In addition, the smaller files used in delta software updates can now be extended to conserve energy in battery-constrained devices.

    Pelion Delta Update has now reached General Availability level and is available to all commercial customers.

    Click here for additional documentation.

    Managing permissions to access and control your deployed IoT devices - Secure Device Access – general availability

    IoT devices often require technicians to connect to the device to change configuration, diagnose problems, update software, and more. Traditionally, a password is the most common solution for protecting devices from unauthorized access, however, it’s virtually impossible to achieve high-level operational security when passwords are used to protect access to devices. The potential weakness of an IoT device password is a well-known security challenge and has been responsible for numerous high-profile security breaches and hacks where the same default password was used for every device.

    Pelion Secure Device Access makes it simple for enterprises, system integrators and device OEM to provide secure offline access to devices using an emerging IETF standard called OAuth-ACE.

    Pelion Secure Device Access has now reached General Availability level and is available to all commercial customers.

    Click here for additional documentation.

    Constrained networks and new hardware support ​- Pelion Device Management Client 4.0.0

    The Pelion Device Management Client delivers improvements for constrained networks, hardware boards, and other security features.

    Release of additional operating system support with the launch of UNISOC SXOS SDK v8p2.1 for UIS8908A NB-IoT board, enabling a cost-effective NB-IoT platform for product development.

    Improved user experience when deploying on congested, long latency networks (such as Wi-SUN), by providing configurable random delay when registering.

    Reduced bandwidth consumption for sleepy devices using TLS Resume. This dramatically reduces the bandwidth consumption from a typical TLS data handshake of 8.6 kilobytes, compared with a TLS Resume of only 853 bytes.

    Seamless integration with our IoT OS - Mbed OS 5.14

    Our free open-source IoT operating system, Mbed OS, is also now PSA Certified and helps developers build IoT devices without the cost and effort typically associated with architecting a secure foundation.

    Many of our customers are looking to deploy IoT devices at scale, and through our three years of collaboration; we’ve been able to refine and improve how features are used and how much memory they require. This is just one example of how last month’s Mbed OS 5.14 focused on optimizing features added over the past three years to address specific customer needs.

    Additional improvements to Platform Security Architecture (PSA) have also come to fruition, with the addition of the first Secure Element, the Atmel AT608a- A secure element that provides a device manufacturer with a simple way of adding a hardware enclave where device identity, cryptographic keys, certificates and other credentials can be stored in a hardware isolated form that protects them from malicious attacks.

    Mbed OS now provides support for all three platform configurations defined by PSA;

  • V8-M with TrustZone (such as the NXP LPC55S69 or the Nuvoton M2351).
  • Dual core v7-M (such as the Cypress PSoC6).
  • Single core v7-M platform with a secure element, such as the Atmel SE.
  • You can read the full Mbed OS 5.14 release blog here.

    Important Information for this Arm website

    This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.