VoIP Handover Timing via Silence Period Prediction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing mobility management in 3GPP networks, particularly during handover events in VoIP services, often results in quality of experience (QoE) degradation due to packet delays and losses during handover interruptions, which are not adequately addressed by current methods.

Innovation Solution

A method is introduced where the handover execution in 3GPP networks is coordinated based on VoIP traffic analysis and prediction, allowing handovers to occur during silence periods to minimize packet delays and losses, thereby improving the quality of experience by reducing handover-related disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If handover is executed immediately when radio quality degrades, then mobility responsiveness is improved, but VoIP quality of experience deteriorates due to packet delays and losses during handover interruptions

Engineering Contradiction:

Improvehandover execution speedVSAvoidVoIP quality of experience

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The system performs preliminary analysis of VoIP traffic patterns and predicts future traffic states to determine the optimal handover execution time. By analyzing historical traffic data and predicting silence periods ahead of time, the system can prepare and execute handovers during predicted low-traffic intervals, thus maintaining both fast handover response and high VoIP quality.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The handover execution timing is made dynamic rather than static. The system continuously monitors VoIP traffic patterns and adapts handover timing based on real-time traffic conditions. This dynamic approach allows the system to respond quickly to radio quality changes while simultaneously adapting to VoIP traffic patterns to minimize impact on call quality.

Inventive Principle:

Principle #15Dynamics

2Reliability

If handover execution is delayed to avoid VoIP traffic, then VoIP quality of experience is improved, but mobility responsiveness deteriorates

Engineering Contradiction:

ImproveVoIP quality of experienceVSAvoidhandover execution speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The system implements a feedback mechanism where VoIP traffic patterns are continuously monitored and fed back into the handover decision-making process. This feedback loop allows the system to learn from past handover outcomes and traffic patterns, progressively optimizing the timing of handovers to achieve the best balance between mobility responsiveness and VoIP quality.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If standard mobility mechanisms are used without VoIP awareness, then system complexity is minimized, but VoIP quality of experience deteriorates during handover interruptions

Engineering Contradiction:

Improvemobility management complexityVSAvoidVoIP quality of experience

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system enhances existing mobility management entities with multi-functionality, allowing them to perform both traditional mobility management and VoIP-aware handover optimization. By integrating traffic analysis and prediction capabilities into existing network elements, the system avoids creating entirely new complex systems while still achieving VoIP-optimized handover execution.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10531342B2VoIP service state aware hand over execution

Publication Date: 2020.01.07 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A Network Node, a Radio Access node and methods therein for handling and supporting Hand Over, HO, in a wireless communication network are disclosed. The method in a Radio Access node comprises receiving, from a Network Node, a VoIP session notification identifying a traffic flow associated with VoIP related to a UE. The method further comprises receiving, from the Network Node, a VoIP state report for the identified traffic flow, said VoIP state report comprising a determined VoIP state, and a prediction related to a time to a VoIP state change. Further, the method comprises, when the UE is a candidate for HO: deciding whether to delay or to trigger the HO based on the VoIP state and the prediction.