Application Mobility Class Selection for Network Handover Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP EPC networks lack a flexible mobility management solution that can cater to diverse applications with varying requirements for session continuity and quality of service (QoS), leading to inefficiencies in handover delay and signaling costs.
Innovation Solution
A system and method for selecting the appropriate mobility support technique based on the mobility class of an application, which determines the subset of available techniques that meet and exceed its requirements, allowing for the selection and sharing of the optimal mobility support method among entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a tight tolerance application mobility solution is used for all applications, then session continuity requirements are met, but signaling cost increases and system complexity increases
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting mobility management parameters based on application-specific requirements. Different applications are assigned different mobility classes with varying handover delay tolerances (e.g., 10ms for stringent applications, 100ms for less stringent applications). The system changes the operational parameters of mobility management mechanisms to match the specific needs of each application, thereby achieving reliable session continuity only when necessary while reducing overall system complexity.
Solution Approach 2:
The patent segments the mobility management system into multiple mobility classes (e.g., first mobility class for stringent requirements, second mobility class for less stringent requirements). Each mobility class has its own set of parameters and management mechanisms. This segmentation allows the system to apply different levels of mobility management complexity to different applications, reducing the overall burden while maintaining reliability where needed.
2Reliability
If mobility support is provided for all applications, then session continuity is ensured, but signaling cost increases
Solution Approach 1:
The system changes the parameter of mobility support provision from a universal default to an application-specific basis. By evaluating the mobility requirements of each application and assigning appropriate mobility classes, the system ensures session continuity only for applications that require it, thereby reducing unnecessary signaling costs while maintaining reliability where needed.
Solution Approach 2:
The patent applies partial action by providing mobility support selectively rather than universally. The system determines the subset of applications that require mobility support based on their specific requirements, and applies mobility management mechanisms only to those applications. This partial application of mobility support reduces signaling costs while ensuring session continuity for applications that truly need it.
3Ease of manufacture
If a one-size-fits-all mobility solution is used, then implementation is simple, but diverse QoS requirements cannot be met
Solution Approach 1:
The patent resolves this contradiction by introducing parameter changes that allow the system to adapt to diverse QoS requirements. Different mobility classes are defined with different parameters (handover delay tolerances, signaling thresholds, etc.), enabling the system to meet diverse QoS requirements while maintaining a relatively simple implementation framework. The complexity is managed through parameter configuration rather than structural complexity.
Solution Approach 2:
The patent applies universality by creating a unified mobility management framework that can handle multiple types of applications with different requirements. The mobility class mechanism serves as a universal interface that accommodates various QoS needs through parameter differentiation, allowing a single system architecture to provide customized mobility support for different application types without requiring separate specialized systems.
Data Source
AI summary
A method for mobility support selection includes determining a mobility class of a first application executing on a device, and determining if a subset of a plurality of available mobility support techniques associated with the entity one of meets and exceeds requirements of the mobility class of the first application. When the subset of the plurality of available mobility support techniques associated with the entity one of meets and exceeds the requirements of the mobility class of the first application, the method comprises selecting a mobility support technique from the subset of the plurality of available mobility support techniques, and sharing information related to the selected mobility support technique with other entities.