IR.21 Roaming Data Audits for Network Subsystem Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Signal coverage issues and inefficient roaming processes in wireless networks due to degraded Wi-Fi signals, AP configuration mismatches, and excessive probe requests lead to disconnections and performance delays, particularly in roaming scenarios.
Innovation Solution
An automated system for ingesting and executing roaming partner network updates using IR.21 information and OMD data to reconfigure network subsystems, performing event-driven audits, and applying configuration data to ensure seamless roaming across different networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automated system performs network reconfiguration, then productivity is improved, but device complexity increases
Solution Approach 1:
The system segments the network reconfiguration process into distinct phases: data collection from multiple sources, audit/verification, change generation, and execution. This segmentation allows the complex automated system to manage complexity through structured processing stages while maintaining high productivity in network reconfiguration operations.
Solution Approach 2:
The patent introduces an intermediary audit system that verifies and validates network configuration changes before execution. This intermediary layer mediates between the automated reconfiguration process and the actual network changes, enabling productivity improvement while managing system complexity through verification and validation mechanisms.
2Device complexity
If manual configuration updates are performed, then device complexity is reduced, but loss of time increases
Solution Approach 1:
The system implements self-service automation where the network configuration system automatically collects data from multiple sources, performs audits, generates change commands, and executes reconfiguration without requiring manual intervention. This eliminates time loss while the modular architecture keeps complexity manageable through automated routines and standardized processes.
Solution Approach 2:
The patent performs preliminary actions by collecting and validating all necessary configuration data and audit information before executing the actual network reconfiguration. This preliminary processing phase prepares everything needed for the change execution, reducing overall time loss while maintaining system complexity at acceptable levels through pre-computed and validated data structures.
3Reliability
If multiple data sources are integrated, then reliability is improved, but device complexity increases
Solution Approach 1:
The system implements a universal data collection framework that can ingest information from multiple diverse sources (OMD, IR.21, local network data) through a unified processing architecture. This multi-functional approach improves reliability by consolidating data from various sources while managing complexity through standardized data handling routines and a common audit mechanism.
Solution Approach 2:
The patent incorporates feedback mechanisms where the system continuously monitors network state, compares it against collected data from multiple sources, and adjusts configuration changes accordingly. This feedback loop improves data consistency and reliability by ensuring all sources are reconciled, while managing complexity through automated comparison and validation processes.
4Reliability
If automated audits are performed, then reliability is improved, but productivity decreases
Solution Approach 1:
The system performs preliminary audit actions by collecting, validating, and reconciling data from multiple sources before generating and executing configuration changes. This preliminary audit phase ensures high reliability and configuration accuracy, while the automated nature of the process maintains productivity by eliminating manual verification steps and using standardized audit routines.
Data Source
AI summary
A first mobile network operator (MNO) periodically retrieves roaming network updates for reconfiguring one or more network subsystems of a network operated by the first MNO. A portion of the roaming network update is retrieved from an operator master database (OMD). The roaming network update includes roam data associated with a second MNO and configuration data for the one or more network subsystems. The roam data is retrieved via IR.21 information from a cloud server associated with the second MNO. The roam data specifies one or more telecommunications carriers associated with the second MNO. The one or more network subsystems for reconfiguration are identified based on the roaming network update. The one or more network subsystems are reconfigured using the roaming network update to enable one or more user devices associated with the second MNO for roaming on the network.