Dynamic Bootstrap Server Assignment for LW-M2M Carrier Porting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Lightweight-Machine-to-Machine (LW-M2M) devices face challenges in switching carriers due to hard-coded server URLs, which become unusable when devices are ported to new carriers, leading to issues with device registration and management.
Innovation Solution
Assigning LW-M2M devices to a local bootstrap server upon network attachment, using the Protocol Configuration Options (PCO) field in LTE signaling to dynamically provide the bootstrap server URL, eliminating the need for hard-coded server URLs and enabling seamless carrier porting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hard-coded server URLs are used in LW-M2M devices, then device registration and management work correctly on the original carrier, but the device cannot communicate with the correct server when ported to a new carrier
Solution Approach 1:
The patent applies dynamics by transitioning from static hard-coded server URLs to dynamic URL assignment. The device client changes from having fixed pre-configured server addresses to receiving server URLs dynamically from the network during attachment or registration processes. This allows the server address to adapt automatically when the device moves between carriers, resolving the contradiction between registration reliability and carrier porting adaptability.
Solution Approach 2:
The patent applies parameter changes by modifying the server URL parameter from a fixed value to a dynamically assigned value. Instead of using hard-coded server addresses, the system now assigns server URLs as configurable parameters that can change based on the carrier network. This parameter change enables the device to maintain reliable registration on any carrier while adapting to different network environments.
2Reliability
If manual reprogramming is performed to update server URLs when devices are ported to new carriers, then correct server communication is restored, but the process becomes complex and time-consuming
Solution Approach 1:
The patent applies self-service by enabling the device to automatically obtain and configure the correct server URL without human intervention. The device client autonomously requests and receives server address information from the network during attachment or registration, eliminating the need for manual reprogramming operations. This self-service mechanism maintains server communication reliability while dramatically simplifying the carrier porting process.
Solution Approach 2:
The patent applies preliminary action by pre-establishing the mechanism for dynamic server URL assignment during the initial device attachment or registration process. Instead of waiting for manual intervention after carrier porting, the system is pre-configured to automatically provide the correct server URL to the device client during these initial network interactions, ensuring seamless carrier transitions without operational complexity.
3Adaptability or versatility
If dynamic server URL assignment is implemented, then carrier porting becomes seamless and automatic, but the system requires additional network signaling and coordination mechanisms
Solution Approach 1:
The patent applies universality by designing the dynamic server URL assignment mechanism to work across multiple carriers and network types using standardized procedures. The same attachment or registration processes that devices already use for normal network access are extended to also convey server URL information. This multi-functional approach enables seamless carrier porting adaptability without requiring separate complex signaling paths, as the existing universal device-to-network interaction mechanisms are leveraged for both purposes.
Data Source
AI summary
A method assigns a bootstrap server for wireless devices in a machine-to-machine environment. The method includes receiving, by a network device in a wireless access network and from a wireless device, a first request for a bootstrap server identifier. The method also includes providing, to the wireless device, a response including an address for a carrier-specific bootstrap server device. The method also includes receiving, by the carrier-specific bootstrap server device, a request for management server connection information. The request is submitted by the wireless device using the bootstrap server identifier. The method further includes assigning, by the carrier-specific bootstrap server device, the wireless device to a management server of a group of management servers and sending connection information for the management server to the wireless device.


