Arm Pelion Device Management Release

The flexibility, efficiency, and security of Pelion Device Management platform continues to be the focus of the Arm development team. In the latest release of Pelion Device Management, we are announcing features that provide greater flexibility for On-Premises deployments, ability to manage legacy and non-IP devices through Edge gateways, efficiency enhancements to our campaign service metrics and support of identity federation for even greater security and management of user access, together with numerous iterative improvements to existing capabilities.

Greater Deployment Flexibility – Providing On-Premises Support

Pelion Device Management On-Premises was introduced in our last release, enabling customers to deploy Pelion Device Management on their own physical hardware, datacenter, and infrastructure-as-a-service platform. On-Premises support has been extended with multiple deployment options of the system, providing identical features and capabilities that are available with Pelion Device Management operated and hosted by Arm in the Cloud.

Pelion On-Premises provides all necessary APIs and integration points for customer’s proprietary software and other third-party applications, including a feature-rich portal and admin console for efficient management of the system, including:

  • Streamlined billing for service users
  • Identity and access management to manage and federate users
  • System health diagnostics
  • Availability of Regional Pelion Access - China and Japan

    At Mobile World Congress in February, Arm announced a partnership with China Unicom to support their software as a service offering using Pelion. Pelion will enable China Unicom to reach local enterprises and global organizations operating in China with full IoT device management services.
    The collaboration will provide a flexible, high performance and secure solution by leveraging Pelion Device Management, Arm Mbed OS, China Unicom’s new IoT platform and a rich device and application ecosystem.

    Additionally, for Japanese customers, we are now able to offer Pelion Device Management access locally as a managed service. Customers and enterprises operating regionally will now be able to access all our device management services and features with greater performance and reduced latency using our local point of presence.

    Release of Pelion Edge for IoT Gateways

    We are excited to announce the release of our device management solution specifically for IoT gateways, that extends connection and management to non-IP devices by Pelion Device Management service and the capability to manage the gateway itself within the same platform.

    Supporting a wide range of features, Pelion Edge provides the same level of support provided to other endpoints: bring-on-board, first-to-claim, gateway firmware update, and resource management (read/write/observe).

    With the ability to support connection of up to 200 non-IP and legacy endpoints behind the gateway, Pelion Device Management extends its reach to support a wider range of IoT devices including Bluetooth Low Energy (BLE) endpoints.
    To support additional protocols, a framework for building your own Protocol Translators is delivered with an open source example of the BLE protocol translator.

    Pelion Edge Manager mobile application available on iOS and Android platforms provides users with local control of the gateway via a mobile device. The application includes the ability to connect and control devices including view status, resource management (read/write) and the option to communicate through the local Pelion Edge gateway directly or through the Cloud.

    The factory configuration utility facilitates the provisioning process, sets up your gateway for secure connection and communication with Pelion Device Management. Provisioning these credentials to your gateway in the factory enables them to trust Pelion Device Management and enables Device Management to authenticate your devices when they attempt to connect to your account.

    The Pelion Edge is provided as an open source reference code on RPB3+ with the potential to port on to additional hardware platforms with some customization.

    An update campaign defines which device or devices receive a firmware update and specifies which firmware image that is installed. A campaign is built around a manifest, that’s sent to the device and a filter that determines which devices receive the manifest. Devices that receive a manifest may reject the update if it does not match the compatibility fields or rules as defined in the manifest. This is to avoid firmware created for a specific model or for use by a particular vendor being updated on an incompatible or inappropriate device.

    In addition to the top-level visibility and overall campaign metrics that have been available since the launch of our device management service, additional device insights now include:

  • Number of devices in a campaign
  • Number of devices successfully updated
  • Number of devices pending an update
  • Number of devices failed to update
  • This additional functionality offers a detailed breakdown of device status within campaign metrics, along with information on devices that have failed to update per failure reasons.

    Simpler Enterprise User Access to Pelion Device Management Portal – Identity Federation

    Identity federation makes it simpler for enterprise users to work with the Pelion IoT platform. Allowing users to access the Pelion Device Management Portal using their work credentials, eradicating the need to create and remember additional user names and passwords.

    Identity Federation also provides greater level of system security, by allowing customers to centrally manage all users and their respective permissions to Pelion Device Management through their corporate directory service. For example; when an employee leaves the company or changes their role, enterprise IT can centrally update the identity databases to disable or change access rights of the user on both internal and external systems including the Pelion Device Management Portal.

    Pelion Device Management now supports the industry standard SAML 2.0 identity federation. To gain access to this capability, the account administrator needs to enable this feature using the Pelion Device Management Portal and configure the parameters of the SAML 2.0 identify server that will be used to authenticate Pelion Device Management users.

    Identity Federation is available to customers of commercial Pelion Device Management accounts without additional charge.

    Click here to find out more

    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.