LTE Cell Data Redirection via Local Core Equipment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions fail to maintain connectivity and service in PMR networks when an LTE cell disconnects from the remote core due to a failure in the connection between the cell site and the distant heart, leading to isolation from the rest of the network.
Innovation Solution
A method that redirects the data stream from a faulty cell site to a local core equipment via a second protocol X2, implementing dynamic load balancing of packet data gateways and utilizing a local application server to route the data stream back to the remote core, while also detecting base station load and quality, and allocating bandwidth for temporary redirection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a direct connection is maintained between the cell site and remote core equipment, then network performance and reliability are improved, but the system becomes vulnerable to isolation when the connection fails
Solution Approach 1:
The patent introduces a local core equipment as an intermediary between the cell site and remote core equipment. When the direct S5 connection fails, data flows through this intermediate local core equipment using X2 protocol, preventing isolation while maintaining the original direct connection architecture for normal operation.
Solution Approach 2:
The patent pre-configures alternative routing paths through local core equipment before connection failures occur. The system maintains readiness for failover by having the X2 interface and local core equipment prepared in advance, enabling immediate redirection when the primary S5 connection fails, thus improving reliability without requiring complex real-time decision-making.
2Duration of action of stationary object
If alternative routing paths are pre-configured for failover, then service continuity is improved during connection failures, but network complexity and resource requirements increase
Solution Approach 1:
The patent segments the core network into remote core equipment and local core equipment components. This segmentation allows the alternative routing path to use existing X2 interface infrastructure already present in the network, rather than requiring a completely new dedicated failover path, thus limiting the increase in infrastructure complexity.
Solution Approach 2:
The local core equipment serves multiple functions: it acts as a backup routing path during failures, provides load balancing capabilities, and maintains existing X2 interface functionality. This multi-functionality reduces the need for dedicated failover-only infrastructure, limiting the complexity increase while improving service continuity.
3Productivity
If dynamic load balancing is implemented during failover, then resource utilization is optimized, but the control and detection mechanisms become more complex
Solution Approach 1:
The patent implements feedback mechanisms where the local core equipment continuously monitors the status of the primary S5 connection and dynamically adjusts routing decisions. Load balancing information is exchanged between network elements, enabling optimized resource utilization during failover based on real-time network conditions rather than static pre-configured paths.
Solution Approach 2:
The patent makes the failover routing dynamic rather than static. The system can adaptively switch between direct S5 connection and indirect X2 routing through local core equipment based on real-time load conditions, connection status, and network performance metrics, optimizing resource utilization without requiring overly complex manual control mechanisms.
Data Source
Figure 1~2
Figure 3
AI summary
A method for maintaining a data flow from a cell site within a mobile communication network to a remote core equipment (EPC High) in the event of a failure of a connection planned between said cell site and said remote core equipment according to a first protocol (S5), characterized in that it includes a redirection, according to a second protocol (X2), of said data flow to said remote core equipment (EPC High) via a local core equipment (EPC Low) connected to said remote core equipment (EPC High).