User Plane Redundancy for Control and User Plane Separation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In evolved packet core (EPC) architectures with control and user plane separation (CUPS), managing the independent scalability and resilience of user plane entities is challenging, particularly in ensuring continuous service without service impact in case of user plane entity failures.

Innovation Solution

Implementing 1:1 user plane redundancy, where each active user plane entity has a dedicated standby entity programmed with PDN information, which can immediately take over in case of failure, using a control plane entity to manage and activate the standby entity, and utilizing protocols like GTP and BGP for seamless session continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If control and user plane separation is implemented, then flexibility and independent scalability are improved, but reliability and service continuity deteriorate due to user plane entity failures

Engineering Contradiction:

Improveflexibility and independent scalabilityVSAvoidservice continuity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring standby user plane entities with all necessary packet data network (PDN) information before failures occur. The standby entities are prepared in advance with session contexts, IP addresses, and routing information, enabling immediate takeover without service disruption when active entities fail.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent applies beforehand cushioning by creating redundant standby user plane entities that serve as a buffer against failures. These standby entities are maintained in a ready state with synchronized PDN information, providing a protective cushion that absorbs the impact of active entity failures and ensures continuous service delivery.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If redundancy mechanisms are added to improve reliability, then service continuity is improved, but device complexity increases

Engineering Contradiction:

Improveservice continuityVSAvoidredundancy management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism in the form of a control plane entity that manages the redundancy system. This intermediary handles the complexity of coordinating between active and standby user plane entities, managing failover detection, and synchronizing PDN information, thereby simplifying the overall redundancy management architecture.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent merges the management of multiple user plane entities under a unified control plane framework. By combining the control functions for both active and standby entities into a single management structure, the system reduces operational complexity while maintaining reliability through coordinated redundancy management.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10855517B2Redundancy support for control and user plane separation

Publication Date: 2020.12.01 CISCO TECHNOLOGY INC

AI summary

In one embodiment, a method is performed. A first user plane entity may be associated with a user plane group comprising a plurality of user plane entities. The first user plane entity may be associated with a second user plane entity. A failure of the second user plane entity may be detected. In response to detecting the failure of the second user plane entity, the first user plane entity may be activated.