M2M Device Bootstrapping via DHCPv6 Gateway
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
M2M devices face challenges in reconfiguring their bootstrapping service addresses, especially when the original server malfunctions or changes in ownership occur, due to the lack of a user interface and cumbersome update processes.
Innovation Solution
A gateway system utilizing the Dynamic Host Configuration Protocol for Internet Protocol Version 6 (DHCPv6) to dynamically assign and manage bootstrapping service addresses to M2M devices, allowing for easy reconfiguration and adaptation to new servers through the Identity Association for Prefix Delegation (IA_PD) mechanism.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the bootstrapping service address is configured in the M2M device at manufacturing stage, then the device can initially contact the server, but the device cannot be easily reconfigured when the server malfunctions or ownership changes
Solution Approach 1:
The patent introduces a gateway as an intermediary component between the M2M device and the bootstrapping service. The gateway stores the bootstrapping service address and provides it to M2M devices upon request, eliminating the need for direct hardcoding in devices. This intermediary allows centralized management and easy reconfiguration of service addresses without requiring device updates or user intervention.
Solution Approach 2:
The M2M device is designed to automatically request and obtain the bootstrapping service address from the gateway during its operation. The device can self-reconfigure by fetching updated addresses from the gateway without requiring manual intervention, user interface interactions, or reprogramming, thereby achieving easy adaptability to server changes.
2Adaptability or versatility
If the bootstrapping service address is hard-coded in the M2M device, then the device configuration is stable, but the device lacks flexibility to adapt to network changes or server failures
Solution Approach 1:
The gateway serves as a centralized configuration management intermediary that handles all bootstrapping service address distribution. This externalizes the complexity of configuration management from individual M2M devices to the gateway, allowing devices to remain simple while the system as a whole gains flexibility and adaptability to network changes.
Solution Approach 2:
The gateway provides universal configuration management services to multiple M2M devices simultaneously. It can serve as a single point of control for the entire M2M network, providing bootstrapping service addresses to numerous devices and enabling centralized management of network-wide configuration changes.
3Reliability
If manual reconfiguration of the bootstrapping service address is required, then the device can be updated, but the process is cumbersome and time-consuming
Solution Approach 1:
The M2M device automatically performs reconfiguration by requesting updated bootstrapping service addresses from the gateway when needed. This self-service mechanism eliminates the time-consuming manual reconfiguration process, allowing devices to quickly adapt to server failures or changes without user intervention, thereby improving reliability while minimizing time loss.
Solution Approach 2:
The gateway pre-stores multiple bootstrapping service addresses and makes them available to M2M devices in advance. When a server fails or changes occur, devices can immediately retrieve alternative addresses from the gateway without waiting for manual configuration, enabling rapid recovery and reducing downtime.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A gateway is provided for configuring a device management bootstrapping service address in a machine-to-machine, M2M, device. The gateway is configured to send a request to a dynamic host configuration protocol for internet protocol version six, DHCPv6, server for identity association for prefix delegation, IA_PD. The gateway is further configured to receive a response from the DHCPv6 server comprising at least one prefix of an Internet Protocol for version 6, IPv6, address assigned to the gateway. Additionally, the gateway is configured to receive a device management bootstrapping service address from a node. This node may be the DHCPv6 server.