M2M Device Provisioning via Non-Unique Identifier Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In machine-to-machine (M2M) platforms, devices often lack unique identifiers, making it difficult for servers to properly provision them, especially when developers do not have access to the devices during manufacturing or operation, leading to issues with tracking and authentication.
Innovation Solution
A method where client devices provide a non-unique provisioning identifier to a server, which generates a unique identifier for the device, allowing restricted communication until authentication, enabling authorized access to data and resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If devices use non-unique provisioning identifiers for communication, then device provisioning becomes possible without pre-programmed unique identifiers, but the server cannot properly track and re-identify individual devices
Solution Approach 1:
The patent introduces a provisioning identifier as an intermediary that bridges the gap between devices without unique identifiers and the server. This mediator allows devices to communicate and be provisioned while the server generates and manages unique identifiers internally, resolving the contradiction between ease of provisioning and proper device tracking
Solution Approach 2:
The server creates a copy or representation of the device identity through generated unique identifiers based on the non-unique provisioning identifiers. This copying mechanism allows the server to track and re-identify devices internally even though the original device identifiers are not unique
2Adaptability or versatility
If the server generates unique identifiers in real-time, then devices can be provisioned without factory programming, but the server must maintain complex mapping between devices and applications
Solution Approach 1:
The system enables self-service provisioning where devices can be automatically provisioned with unique identifiers generated by the server in real-time without requiring factory programming or complex manual mapping maintenance, reducing overall system complexity
3Ease of operation
If developers do not have access to devices during manufacturing or operation, then device distribution is simplified, but unique identifier programming and tracking become impossible
Solution Approach 1:
Devices automatically obtain unique identifiers through self-service provisioning when they first communicate with the server, eliminating the need for developer access during manufacturing or operation while ensuring proper tracking and identification of each device
Data Source
AI summary
Systems and methods for automatically provisioning devices that do not include or cannot provide a unique hardware identifier over a machine-to-machine network. A device or application may provide a server with a non-unique provisioning identifier during restricted communication between the server and the device. In response to receiving a provisioning identifier from a device, a server may generate a globally unique device identifier associated with the provisioning identifier for the individual device, and transmit the unique identifier to the device. The device may retain the unique identifier for future transactions. A request may be provided to a user, at the device, the server or any other interface, requesting that a newly identified device be authenticated. Upon authentication the device may communicate with the server with additional interactions that were not provided after provisioning and before authentication.