Voice Over 4G Call Retry Handling via Mapping Database

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing solutions for voice over 4G call failures often result in call dropping, which is unacceptable and lacks a seamless and quick reestablishment process within the voice over 4G domain.

Innovation Solution

A method is introduced that detects voice over 4G link failures and uses a mapping database to trigger specific actions, such as establishing a new CDMA call link or canceling existing voice over 4G call links, to reestablish communication efficiently without relying on timers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing solutions are used for voice over 4G call failures, then the system follows conventional call dropping procedures, but the call reliability deteriorates and user experience worsens due to unacceptable call drops

Engineering Contradiction:

Improvecall reliabilityVSAvoiduser experience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by detecting call failure indications and triggering predetermined actions before the call is completely dropped. The mapping database pre-configures retry actions and alternative communication paths, enabling proactive call preservation rather than reactive call restoration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring call failure indications and using this information to trigger appropriate retry actions. The mapping database receives event triggers containing failure information and responds with predetermined actions, creating a closed-loop control system that continuously adapts to call conditions.

Inventive Principle:

Principle #23Feedback

2Device complexity

If conventional call dropping procedures are followed, then the system simplifies error handling, but the call reestablishment time increases and seamless communication is lost

Engineering Contradiction:

Improveerror handling complexityVSAvoidcall reestablishment time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system pre-configures retry actions and alternative communication paths in the mapping database before failures occur. When a failure is detected, the predetermined actions are immediately executed without requiring complex real-time decision-making, thus reducing both complexity and reestablishment time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system changes operational parameters by switching between different communication protocols and paths based on failure conditions. The mapping database stores multiple action configurations that can be rapidly activated, allowing the system to adapt parameters such as communication protocol type and path selection without complex processing.

Inventive Principle:

Principle #35Parameter changes

3Speed

If the system implements rapid call reestablishment through mapping database and predetermined actions, then the call reestablishment speed improves, but the system complexity increases due to additional components and processes

Engineering Contradiction:

Improvecall reestablishment speedVSAvoidsystem complexity

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The mapping database pre-configures all necessary retry actions and alternative paths before failures occur. This preliminary configuration eliminates the need for complex real-time decision-making algorithms, achieving rapid reestablishment through pre-computed solutions that simply need to be executed when failures are detected.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automated failure detection and predetermined action execution. The mapping database automatically receives failure indications, determines appropriate actions, and executes retries without requiring manual intervention or complex control logic, thereby achieving fast reestablishment with manageable complexity.

Inventive Principle:

Principle #25Self-service

4Ease of manufacture

If the system uses timer-based retry mechanisms, then the implementation is straightforward, but the call reestablishment is delayed and not expedited

Engineering Contradiction:

Improveimplementation simplicityVSAvoidretry delay

Core Design Contradiction:

Ease of manufactureVSLoss of time

Solution Approach 1:

The system replaces timer-based mechanisms with feedback-driven triggers. The mapping database receives real-time failure indications and immediately executes predetermined actions based on the actual failure conditions, eliminating arbitrary waiting periods and achieving expedited call reestablishment responsive to actual system state.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system pre-configures retry actions in the mapping database to be executed immediately upon failure detection. This preliminary preparation of action plans eliminates the need for timer-based delays, as the system is already prepared with specific retry strategies that can be instantly activated when failures occur.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS8718636B1System and method for expedited call retry handling due to voice over 4G call failure

Publication Date: 2014.05.06 T MOBILE US INC

AI summary

A method for handling failure of a voice over 4G call connection within a wireless call connection includes the steps of detecting an indication of a failure of a voice over 4G link. An event trigger associated with the failure of the voice over 4G link is provided to a mapping database and the database maps the event trigger to at least one predetermined action responsive to indications within the mapping database. At least one predetermined action associated with the event trigger is then performed.