Call Setup Following Dedicated Bearer Failure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In telecommunications networks, dedicated bearers can fail to establish a user plane between the IMS core and user equipment (UE), leading to failed voice or video calls, especially in scenarios where fallback to 2G or 3G networks is not available.

Innovation Solution

Implementing call setup techniques that involve determining the failure of a dedicated bearer and configuring a default bearer using Real-Time Transport Protocol (RTP) and/or Real-Time Control Transport Protocol (RTCP) messages to establish a communication channel, ensuring that calls can be completed even when dedicated bearers fail.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dedicated bearer is used to establish a user plane between the IMS core and UE, then call quality and reliability are improved, but the system becomes vulnerable to bearer failures that drop calls

Engineering Contradiction:
Improvecall completion reliabilityVSAvoidbearer management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by establishing a default bearer before the dedicated bearer becomes necessary. When dedicated bearer failure is detected, the system has already prepared the default bearer as a fallback path, allowing immediate switch without call drop. This preliminary preparation resolves the contradiction by ensuring reliability through pre-configured backup paths while managing complexity through automated failure detection and switching mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes operational parameters by switching from dedicated bearer mode to default bearer mode upon failure detection. This parameter change involves modifying the active communication path, QoS parameters, and protocol behavior. By dynamically changing these parameters based on bearer status, the system maintains call reliability while managing complexity through adaptive parameter adjustment rather than static configuration.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If the system continues to attempt dedicated bearer establishment after failure, then bearer establishment precision is maintained, but call setup time increases and calls are dropped

Engineering Contradiction:
Improvebearer establishment precisionVSAvoidcall setup time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system implements feedback mechanisms that monitor dedicated bearer establishment status and provide real-time information about failure conditions. When failure is detected through feedback signals, the system immediately switches to the default bearer path. This feedback loop resolves the contradiction by maintaining precision through continuous monitoring while reducing time loss through automated response to failure feedback, preventing repeated unsuccessful attempts.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system applies the skipping principle by bypassing repeated dedicated bearer establishment attempts when failure is detected. Instead of continuing to rush through failed establishment procedures, the system skips directly to using the default bearer path. This resolves the contradiction by maintaining precision through intelligent decision-making about when to skip versus when to attempt establishment, thereby reducing overall call setup time while preserving successful connection quality.

Inventive Principle:
Principle #21Skipping (Rushing through)

3Reliability

If fallback to 2G or 3G networks is implemented when dedicated bearer fails, then call reliability is improved, but network switching complexity and time increase

Engineering Contradiction:
Improvecall completion reliabilityVSAvoidnetwork switching complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies segmentation by separating the bearer types into distinct functional segments: default bearer for basic connectivity and dedicated bearer for optimized voice/video calls. When dedicated bearer fails, the system segments the failure response from the main call flow by independently switching to the pre-configured default bearer path. This segmentation resolves the contradiction by maintaining reliability through functional separation while reducing switching complexity through modular bearer management rather than complete network fallback.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The default bearer acts as an intermediary between the dedicated bearer failure and complete network fallback. Instead of directly switching to 2G/3G networks which would increase complexity, the system uses the default bearer as an intermediate path that maintains LTE/5G connectivity. This intermediary resolves the contradiction by preserving call reliability while avoiding the complexity of inter-generation network switching through a simpler intra-generation bearer switch.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12284238B2Call setup following a dedicated bearer failure
Publication Date: 2025.04.22 T MOBILE US INC
  • US12284238B2 patent drawing
  • US12284238B2 patent drawing
  • US12284238B2 patent drawing

AI summary

Techniques for setting up a communication session responsive to a dedicated bearer failure are described herein. A telecommunications network can implement a server to determine that a user equipment (UE) is incapable of establishing a communication session using a dedicated bearer due to a bandwidth or technology used by the UE. The server can exchange a user plane message with the UE using a default bearer based on determining that the dedicated bearer failed to establish the communication session. The server can establish the communication session for the UE based at least in part on the user plane message associated with the default bearer.