Concurrent Call Handover Using Dual Public Service Identity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing implementations of fixed mobile convergence (FMC) solutions do not support call handover between domains when a user has multiple standing calls, as the mobility application server cannot determine which call to handover first, leading to rejected handover requests due to multiple anchor points and unclear call status.
Innovation Solution
Implementing a two-handover public service identity (PSI) approach, where the handset uses the first HO PSI for the oldest call and the second HO PSI for the most recent call, allowing the mobility application server to track call duration and identify which call was established first, facilitating call handover between domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single handover PSI is used in existing FMC implementations, then the system structure remains simple, but the mobility application server cannot determine which call to handover first when multiple calls are active, leading to rejected handover requests
Solution Approach 1:
The patent segments the handover management by assigning a unique handover PSI to each active call. Instead of using a single handover PSI for all calls, the system divides the handover identification into call-specific segments, allowing the mobility application server to distinguish and manage multiple concurrent handover requests independently.
Solution Approach 2:
The patent adds a new dimension to handover identification by introducing call-specific handover PSIs. This transforms the handover management from a single-identifier system to a multi-identifier system, enabling the server to differentiate between multiple calls by selecting the appropriate handover PSI based on call priority or establishment order.
2Reliability
If multiple anchor points are maintained for multiple calls, then each call can be tracked independently, but the handover request is rejected due to the inability to identify which call is trying to handover first
Solution Approach 1:
The patent implements a feedback mechanism where the mobility application server receives handover requests containing specific handover PSIs, identifies the corresponding call based on that PSI, determines the call's priority or establishment order, and processes the handover accordingly. This feedback loop enables reliable tracking and resolution of handover requests for multiple calls.
Solution Approach 2:
The handover PSI acts as an intermediary that links the handover request to the specific call and its priority information. Instead of directly comparing multiple anchor points, the system uses the handover PSI as a mediator to identify which call should be handed over first, simplifying the decision-making process.
3Productivity
If the mobility application server cannot identify call establishment order, then handover decisions cannot be made for multiple calls, but implementing call order tracking increases system complexity
Solution Approach 1:
The patent applies preliminary action by establishing the call priority or establishment order at the time of call setup. The system pre-determines which call should be handed over first and associates this information with the call-specific handover PSI. When a handover request arrives, the server simply retrieves the pre-established priority information rather than performing complex real-time analysis.
Data Source
AI summary
Methods, systems, and apparatus can be used to provide concurrent call handover in converged networks. In various examples, a concurrent call handover can operate to transfer multiple calls between domains when a mobile device has two open call instances. In some implementations, multiple public service identifiers can be assigned for the call instances.