IP Library Granted Patent US 12,452,767
Granted Patent B2
US 12,452,767 · App. 17/886,582 · Granted Oct 21, 2025

Method and apparatus for route aggregation handling for control and user plane separation

Inventors: Abhishek Mishra (Karnataka, IN); Vipin Padlikar (Karnataka, IN); Rohit Gupta (Karnataka, IN); Tamanna Jindal (McKinney, TX)
Assignee: Mavenir Systems, Inc.
H04W40/30H04W40/06H04W40/248
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,452,767
App. No.
17/886,582
Granted
Oct 21, 2025
Kind
B2
Abstract

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.

Claims (28)

1. A method of route aggregation handling for 3rd Generation Partnership Project (3GPP) Control Plane and User Plane Separation (CUPS) architecture, comprising:

allocating, by a Control Plane (CP) node, an Internet Protocol (IP) Address from an IP pool to a selected User Equipment (UE) for a Packet Data Unit (PDU) session;

performing, by a User Plane (UP) node, data traffic routing between an internet service provider (ISP) and the UE;

sending, by the CP node to the UP node during one of a start or update of an association between the CP node and the UP node, one of: i) transmission routes to be used for the data traffic routing between the ISP and the UE; or ii) transmission routes to be deleted for the data traffic routing between the ISP and the UE; and

in the case of a UP path failure involving the UP node, sending by a standby UP node to the CP node an association update request for the transmission routes to be used for the data traffic routing between the ISP and the UE.

2. The method according to claim 1 , wherein the CP node sends the transmission routes to be used as part of one of an association setup request or an association update request to the UP node.

3. The method according to claim 2 , wherein the transmission routes to be used are provided by the CP node in a route aggregation information element within the one of the association setup request or the association update request sent to the UP node.

4. The method according to claim 3 , wherein the transmission routes to be used are contained in internet protocol (IP) pool route aggregation field within the route aggregation information element.

5. The method according to claim 4 , further comprising:

sending, by the UP node to a next hop router, a Border Gateway Protocol (BGP) Update message containing the IP pool route aggregation field.

6. The method according to claim 1 , wherein the CP node sends the transmission routes to be deleted as part of one of an association setup request or an association update request to the UP node.

7. The method according to claim 6 , wherein the transmission routes to be deleted are provided by the CP node in a route aggregation information element within the one of the association setup request or the association update request sent to the UP node.

8. The method according to claim 7 , wherein the transmission routes to be deleted are contained in internet protocol (IP) pool route aggregation field within the route aggregation information element.

9. The method according to claim 7 , further comprising:

sending, by the UP node to a next hop router, a Border Gateway Protocol (BGP) Update message containing the IP pool route aggregation field.

10. A system for route aggregation handling for 3rd Generation Partnership Project (3GPP) Control Plane and User Plane Separation (CUPS) architecture, comprising:

a Control Plane (CP) node configured to allocate an Internet Protocol (IP) Address from an IP pool to a selected User Equipment (UE) for a Packet Data Unit (PDU) session; and

a User Plane (UP) node configured to perform data traffic routing between an internet service provider (ISP) and the UE; and

a standby UP node configured to send to the CP node, in the case of a UP path failure involving the UP node, an association update request for the transmission routes to be used for the data traffic routing between the ISP and the UE;

wherein the CP node is configured to send to the UP node, during one of a start or update of an association between the CP node and the UP node, one of: i) transmission routes to be used for the data traffic routing between the ISP and the UE; ii) transmission routes to be deleted for the data traffic routing between the ISP and the UE; or iii) transmission routes to be withdrawn for the data traffic routing between the ISP and the UE.

11. The system according to claim 10 , wherein the CP node is configured to send the transmission routes to be used as part of one of an association setup request or an association update request to the UP node.

12. The system according to claim 11 , wherein the transmission routes to be used are provided by the CP node in a route aggregation information element within the one of the association setup request or the association update request sent to the UP node.

13. The system according to claim 12 , wherein the transmission routes to be used are contained in internet protocol (IP) pool route aggregation field within the route aggregation information element.

14. The system according to claim 13 , wherein the UP node is configured to send to a next hop router, a Border Gateway Protocol (BGP) Update message containing the IP pool route aggregation field.

15. The system according to claim 10 , wherein the CP node sends the transmission routes to be deleted as part of one of an association setup request or an association update request to the UP node.

16. The system according to claim 15 , wherein the transmission routes to be deleted are provided by the CP node in a route aggregation information element within the one of the association setup request or the association update request sent to the UP node.

17. The system according to claim 16 , wherein the transmission routes to be deleted are contained in internet protocol (IP) pool route aggregation field within the route aggregation information element.

18. The system according to claim 16 , wherein the UP node is configured to send to a next hop router, a Border Gateway Protocol (BGP) Update message containing the IP pool route aggregation field.

Assignments (13)
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069113 AND FRAME 0558 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072308/0172 →
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 067565 AND FRAME 0678 Recorded Jul 29, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0421 →
GRANT OF SECURITY INTEREST - PATENTS Recorded Jul 29, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: GLAS USA LLC
Reel/Frame 072245/0764 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0041 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0121 →
SECURITY INTEREST Recorded Jul 28, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: BLUE TORCH FINANCE LLC
Reel/Frame 072268/0439 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 4, 2024
From: MAVENIR SYSTEMS, INC.
To: GLAS USA LLC
Reel/Frame 069113/0558 →
RELEASE OF SECURITY INTEREST Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 069113/0596 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068822/0966 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0126 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0209 →
SECURITY INTEREST Recorded May 29, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 067565/0678 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 31, 2022
From: MISHRA, ABHISHEK; PADLIKAR, VIPIN; GUPTA, ROHIT; JINDAL, TAMANNA
To: MAVENIR SYSTEMS, INC
Reel/Frame 060951/0121 →
Priority Claims (1)
IN 202121037889 · Aug 20, 2021 · national
Continuity (1)
Related Publication 20230055358A1 · Feb 23, 2023
References Cited (14)
US 20150110095A1 · Tan · 2015 [cited by examiner]
US 20170118275A1 · Singh et al. · 2017 [cited by applicant]
US 20180295659A1 · Shan · 2018 [cited by examiner]
US 20220116305A1 · Niu · 2022 [cited by examiner]
3GPP TS 23.501 v. 16.2.0 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16); 3rd Generation Partnership Proje… [cited by applicant]
3GPP TS 23.502 v. 16.2.0 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16); 3rd Generation Partnership Project; Sep. … [cited by applicant]
Rekhter et al. “A Border Gateway Protocol 4 (BGP-4)” The Internet Society, Jan. 2006. [cited by applicant]
3GPP TS 29.244 v. 16.3.1 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface Between the Control Plane and User Plane Nodes; Stage 3 (Release 16); 3rd Generation Partn… [cited by applicant]
3GPP TS 29.571 v. 16.3.0 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Common Data Types for Service Based Interfaces; Stage 3 (Release 16); 3rd Generation Part… [cited by applicant]
Cisco Systems et al: “Considerations and solution for UE IP address management”, 3GPP Draft; S2-160082_PCR_CUPS_UE IP ADDRESS_R4, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucio… [cited by applicant]
Cisco Systems et al: “Considerations and solution for UE IP address management”, 3GPP DRAFT;S2-160082_PCR_CUPS_UE IP ADDRESS_R4, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Luciol… [cited by applicant]
Huawei: “Pseudo-CR on PGW-C and PGW-U restoration”, 3GPP Draft; C4-172267_REV_C4-172228_REV_C4-172183_CUPS_PGW_RESTORATION REV2, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Luciol… [cited by applicant]
Cisco Systems Inc: “Pseudo-CR on Solution for PGW-U Failure without Restart—Solution#1”, 3GPP Draft; C4-164274_PCR_PGW-U-FAILURE-WITHOUT-RESTART-SOL#1, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre… [cited by applicant]
Extended European Search Report for corresponding European application EP22190823.9, 9 pages, dated Oct. 27, 2022. [cited by applicant]