Batch Update Wireless IoT Power Settings via Group Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing power consumption settings for IoT devices across thousands or tens of thousands of subscribers is burdensome due to varying carrier policies and the need for individual parameter settings for Low Power Wide Area (LPWA) technologies like LTE-M and NB-IoT, especially when Mobile Virtual Network Operators (MVNOs) lack control over parameter values stored in Mobile Network Operator (MNO) infrastructure.
Innovation Solution
A method and system that allow a server to collectively update parameter settings for multiple subscriber identifiers associated with a group identifier in a subscriber information database, enabling batch changes to low-power consumption states by transmitting update requests and detachment requests to IoT devices, facilitating reattachment and periodic updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If individual parameter settings are performed for each subscriber identifier, then power consumption settings can be customized according to subscriber needs, but the administrative burden and time required for managing thousands or tens of thousands of IoT devices becomes significant
Solution Approach 1:
The patent merges multiple individual parameter settings into a single group-based configuration. By associating multiple subscriber identifiers with a group identifier, the system allows simultaneous update of power consumption parameters for all devices in the group through a single update request, eliminating the need for individual configuration of each device.
Solution Approach 2:
The patent creates a universal configuration mechanism that serves multiple functions: it enables both individual device management and bulk group management. The group identifier acts as a universal key that can represent any number of subscriber identifiers, allowing the same configuration interface to handle both single-device and multi-device scenarios efficiently.
2Adaptability or versatility
If Mobile Virtual Network Operators (MVNOs) can control parameter values, then they can align settings with subscriber needs, but they currently lack control over parameter values stored in Mobile Network Operator (MNO) infrastructure
Solution Approach 1:
The patent introduces a group identifier as an intermediary layer between the MVNO and the MNO infrastructure. The MVNO can manage and update group-based configurations without directly accessing or controlling individual subscriber identifiers stored in the MNO's HSS. This intermediary mechanism enables MVNO control while maintaining the existing MNO infrastructure architecture.
3Productivity
If batch updates are implemented for multiple subscriber identifiers, then administrative efficiency improves, but it requires a new mechanism for grouping and managing multiple subscriber identifiers collectively
Solution Approach 1:
The patent segments the large set of subscriber identifiers into smaller manageable groups using group identifiers. This segmentation allows the system to process updates in manageable batches rather than handling all devices individually or requiring complex bulk processing mechanisms. Each group can be independently configured and updated.
Data Source
AI summary
In this method for managing configuration of a wireless communication service, a setting value of a parameter used in a low power consumption state is changed en masse for a plurality of subscriber identifiers. From a subscriber, an apparatus 200 receives an update request, in association with a group identifier corresponding to a plurality of subscriber identifiers, that includes a setting value of the parameter, identifies the plurality of subscriber identifiers corresponding with the received group identifier, and transmits an update request. An HSS 230 updates the value of the parameter and transmits a CLR to an MME 220. The MME 220 transmits a detach request to a subscriber terminal 210 and receives a re-attach request. After an interval from transmitting the first update request, the apparatus 200 transmits a second update request (S311).