CUPS Route Aggregation with IP Pool Propagation for UP Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in 3GPP Control Plane and User Plane Separation (CUPS) architecture lies in efficient downlink traffic routing, particularly when the Control Plane (CP) allocates IP addresses, leading to bloating of routing information and inefficient routing by routers due to lack of awareness about UE addresses or IP Pool details, and issues during UP path failure and recovery where IP pools are not stored persistently, causing challenges in routing downlink packets to the correct User Plane (UP).
Innovation Solution
A method is provided where the CP sends IP pool blocks to the next hop router using vendor-specific information elements (IEs) during CP-UP association updates, and upon UP path failure or TCP connection resets, the standby UP retrieves and propagates these routes to ensure correct packet routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the CP allocates IP addresses from IP pools and sends them to UP nodes, then IP address allocation flexibility is improved, but routing information bloats and routing efficiency deteriorates
Solution Approach 1:
The patent extracts the routing information propagation function from the router and relocates it to the UP node. The UP node receives IP pool allocations from the CP and autonomously propagates the necessary routing information to the router, thereby separating the IP address allocation flexibility function from the routing efficiency function. This allows the CP to allocate IPs flexibly while the UP node handles routing information management, preventing routing information bloat at the router.
Solution Approach 2:
The UP node acts as an intermediary between the CP and the router. It receives IP pool allocations from the CP, processes the routing information, and propagates it to the router. This intermediary role allows the system to maintain IP allocation flexibility while improving routing efficiency, as the UP node can optimize routing information propagation based on current network state and can batch or aggregate routing updates to prevent router overload.
2Measurement precision
If the router routes downlink traffic based on UE IP addresses, then routing accuracy is improved, but the router requires detailed knowledge of IP pools which increases device complexity
Solution Approach 1:
The patent extracts the IP pool knowledge requirement from the router and relocates it to the UP node. The UP node maintains the IP pool allocations received from the CP and uses this information to generate appropriate routing entries for the router. The router only needs to receive and process the routing information propagated by the UP node, without requiring detailed knowledge of IP pools, thereby reducing router complexity while maintaining routing accuracy.
Solution Approach 2:
The UP node creates simplified copies of the IP pool allocation information in the form of routing entries and propagates these to the router. Instead of the router directly handling complex IP pool data, the UP node transforms it into router-friendly routing table entries, maintaining routing accuracy while reducing the informational burden on the router.
3Productivity
If IP pools are not stored persistently at the UP node to allow reallocation during failure recovery, then resource utilization is improved, but routing recovery time increases
Solution Approach 1:
The patent implements preliminary action by having the UP node proactively propagate routing information to the router before actual IP allocation occurs. When the CP allocates an IP pool to the UP node, the UP node immediately propagates the routing information to the router in advance. This preliminary propagation ensures that when failure recovery occurs, the routing information is already in place or can be quickly re-established, reducing recovery time while still allowing IP pools to be reallocated for resource utilization efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A Shared Cell (SC) Controller uses deployment information, radio resource utilization measurements, cell load measurements, signal quality measurement, operator's policies and radio capabilities to make decisions on system configuration, re-configuration, and channel allocation related to the Shared Cell groups. The SC Controller may also use artificial intelligence/machine learning to predict future system state when making decisions on system configuration and channel allocation. The SC Controller can be implemented in the context of using a CBRS system, the ORAN architecture, and the Shared Cell group of Radio Units (RUs). SC Controller can be implemented as part of the Non-Real Time Radio Intelligent Controller (Non-RT RIC). The SC Controller interfaces with the Citizens Broadband Radio Service Device (CBSD) Controller, and the SC Controller sends the Shared Cell group information to the O-RU Controller so that the O-RU Controller can configure the radio components.