Opportunistic QoS Management for Mobile Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile networks lack a means for applications to indicate strict service requirements and benefit from better services, leading to inefficient resource allocation and user experience, as they cannot differentiate and prioritize Quality of Service (QoS) settings effectively across multiple applications and connections.
Innovation Solution
A method that allows applications to request services based on their specific QoS requirements, including IP-address preservation and service continuity, enabling the network to provide connections that meet these needs while optimizing resource usage by offering better services to applications that benefit from them, even if initially requested by others.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the network provides basic QoS settings for all applications, then resource allocation is simplified, but applications with strict service requirements cannot receive optimal service
Solution Approach 1:
The system performs preliminary actions by storing additional QoS descriptions for all services during service establishment, even though these may not be immediately used. When a service request occurs, the pre-stored additional QoS descriptions are readily available for selection, enabling rapid QoS adaptation without complex real-time negotiations or calculations.
Solution Approach 2:
The QoS settings are made dynamic rather than static. The system can adaptively select between basic QoS settings and additional QoS descriptions based on actual service requirements and network conditions. This dynamic approach allows the same service to receive different QoS treatments at different times, optimizing reliability for applications that need it while maintaining simplicity for others.
2Reliability
If the network allocates resources for high QoS to all applications, then service quality is improved, but resource waste occurs for applications that do not require such service
Solution Approach 1:
Different QoS levels are applied locally to different applications based on their specific requirements rather than uniformly to all applications. The system identifies which applications have strict service requirements and applies enhanced QoS settings only to those specific cases, while standard QoS settings are used for applications that do not require special treatment, thereby avoiding resource waste.
Solution Approach 2:
The system changes QoS parameters dynamically based on application requirements. Instead of maintaining high QoS parameters for all services, the system adjusts parameters such as priority, bandwidth allocation, and service continuity settings according to the specific needs of each application, optimizing the balance between service quality and resource efficiency.
3Productivity
If applications cannot indicate their service requirements, then network configuration is simpler, but resource allocation and user experience are inefficient
Solution Approach 1:
Applications self-identify their service requirements by including appropriate QoS description parameters in their service requests. The application layer itself performs the task of indicating its needs rather than requiring complex external analysis or configuration, enabling the network to automatically allocate resources efficiently based on the application's own declarations.
Solution Approach 2:
The system implements a feedback mechanism where applications provide information about their service requirements through QoS descriptions, and the network responds by allocating appropriate resources. This feedback loop enables continuous optimization of resource allocation based on actual application needs, improving productivity while maintaining manageable complexity through standardized feedback formats.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention provides a method of providing a quality of service setting for a first application operating on a user equipment device, UE, the first application involving communication between the UE and a base station, the method comprising determining a first quality of service setting for the first application, the first quality of service setting comprising a minimum service requirement; determining if the first application could benefit from a higher quality of service setting and if so, storing that information; and following an initiation of a second application in the UE requiring a second quality of service setting higher than the first quality of service setting, changing, when it has been determined that the first application would benefit from a higher quality of service setting, the first quality of service setting for the first application to at least partially satisfy the higher quality of service setting.