Default Bearer Failover for Dedicated Cellular Call Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Dedicated bearers in cellular networks often fail during setup or mid-call, leading to call drops and interruptions, due to issues like network congestion, radio interference, handover problems, and quality of service violations.

Innovation Solution

Implementing mechanisms to transition calls from failed dedicated bearers to default bearers in both evolved packet core (EPC) and fifth generation core (5GC) networks, using message-based protocols to ensure call continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated bearers are used for specific applications requiring guaranteed data rates, then quality of service is improved, but reliability deteriorates due to bearer failures during setup or mid-call

Engineering Contradiction:
Improvecall continuityVSAvoidbearer failure resilience
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system establishes a default bearer in advance that can serve as a backup communication path. When a dedicated bearer fails, the call automatically transitions to the pre-established default bearer, preventing call drops and maintaining service continuity without requiring prior manual intervention.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The default bearer acts as an intermediary communication path between the mobile device and the network. When the dedicated bearer becomes unavailable, the default bearer mediates the data transmission, allowing the call to continue uninterrupted through an alternative route.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If dedicated bearers allocate dedicated network resources for specific applications, then quality of service metrics are met, but device complexity increases due to bearer management overhead

Engineering Contradiction:
Improvequality of service guaranteeVSAvoidbearer management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically detects bearer failures and performs seamless transitions from dedicated to default bearers without requiring user intervention or complex manual configuration. The bearer management process operates autonomously, reducing the perceived complexity for end users while maintaining QoS guarantees.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The default bearer is designed to serve multiple functions: it acts as a primary communication path for general traffic and simultaneously serves as a backup path when dedicated bearers fail. This multi-functionality reduces the need for separate specialized mechanisms, simplifying the overall system architecture.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If multiple types of bearers are used for different network activities, then adaptability is improved, but loss of information increases due to call drops during bearer failures

Engineering Contradiction:
Improvebearer type diversityVSAvoidcall continuity
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

A default bearer is established in advance as a safety net before dedicated bearers are deployed. This preparatory measure ensures that if dedicated bearers fail during critical operations, the call can immediately switch to the default bearer, preventing information loss and maintaining call continuity.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The system continuously monitors the status of dedicated bearers and automatically triggers a switch to the default bearer when failures are detected. This feedback mechanism ensures that call information is preserved by dynamically adapting the communication path based on real-time bearer health status.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250331049A1Bearer failure resiliency
Publication Date: 2025.10.23 T MOBILE US INC
  • US20250331049A1 patent drawing
  • US20250331049A1 patent drawing
  • US20250331049A1 patent drawing

AI summary

A device may receive, by a policy function from a call session control function, a request for a dedicated bearer. A device may provide, by the policy function to the call session control function, a response to the request. A device may forward, by the policy function to a bearer management system, the request for the dedicated bearer. A device may determine, by the policy function, an indication of a failure to set up the dedicated bearer. A device may determine, by the policy function, that the call can continue on a default bearer. A device may in response to the determining, taking no action such that the call continues on the default bearer.