IP Library Granted Patent US 12,581,361
Granted Patent B2
US 12,581,361 · App. 18/627,615 · Granted Mar 17, 2026

Optimizing traffic redirection operations

Inventors: Abhishek Mishra (Bangalore, IN); Vipin Padlikar (Bangalore, IN); Tamanna Jindal (McKinney, TX); Rohit Gupta (Bangalore, IN)
Assignee: Mavenir Systems, Inc.
H04W28/082H04W28/0289H04W28/06
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,581,361
App. No.
18/627,615
Granted
Mar 17, 2026
Kind
B2
Abstract

Minimizing signaling traffic between a User Plane (UP) and a Control Plane (CP), where Policy and Charging Function/Policy and Charging Rule Function (PCF/PCRF) software transmits a first and a second Policy and Charging Control rule (PCCRule1 and PCCRule2) to CP equipment. The CP equipment installs both PCCRule1 and PCCRule2 on UP equipment as UPRule1 and UPRule2 respectively, where UPRule1 is set as active during a first time period and the UPRule2 set as active during a second time period. User Plane Function (UPF) software matching data traffic with a Packet Detection Rule (PDR) to generate identified traffic during the first and second time periods and automatically redirecting data traffic to a predetermined location at the expiration of the first and second time periods respectively. UPRule1 and UPRule2 are automatically enabled and disabled alternatively after expiration of their respective timers by the UPF software.

Claims (47)

1 . A method for optimizing traffic redirection operations between a Control Plane (CP) computer and a User Plane (UP) computer in a mobile phone network for mobile phones, the method comprising the steps of:

transmitting a first Policy and Charging Control rule1 (PCCRule1) from a Policy and Charging Function/Policy and Charging Rule Function (PCF/PCRF) from the CP computer to the UP computer;

transmitting a second Policy and Charging Control rule2 (PCCRule2) from the PCF/PCRF on from the CP computer to the UP computer;

installing both the PCCRule1 and PCCRule2 on the UP computer as UPRule1 and UPRule2 respectively, the UPRule1 set as an active rule and a timer associated with UPRule1 is started;

matching data traffic with a Packet Detection Rule (PDR) to generate identified traffic during the timer associated with UPRule1 to generate UPRule1 matched traffic with a User Plane Function (UPF) operating on the UP computer,

wherein the UPF performs the following steps:

disabling UPRule1 when the timer associated with UPRule1 expires; routing the UPRule1 matched traffic to a UPRule1 specified destination;

enabling UPRule2 and beginning a timer associated with a configuration of UPRule2;

matching data traffic with the PDR to generate identified traffic during the timer associated with UPRule2 to generate UPRule2 matched traffic;

disabling UPRule2 when the timer associated with UPRule2 expires; and

routing the UPRule2 matched traffic to a UPRule2 specified destination.

2 . The method according to claim 1 , wherein the matching of data traffic comprises: deep packet inspection, flow analysis of the traffic, Ethernet or layer 2 observation for non-IP traffic or is based on a location of the device.

3 . The method according to claim 1 , wherein the UPF comprises a gateway responsible for user plane traffic handling between User Equipment (UE) and external packet data networks.

4 . The method according to claim 1 , wherein the PCCRule1 and the PCCRule2 are contemporaneously resident on the CP equipment.

5 . The method according to claim 1 , wherein the UPRule1 causes the UP to be configured each time redirection is done by the UP.

6 . The method according to claim 1 , wherein when the timer associated with UPRule1 expires, the UPF only routes the UPRule1 matched traffic to the UPRule1 specified destination.

7 . The method according to claim 6 , wherein when the timer associated with UPRule2 expires, the UPF only routes the UPRule2 matched traffic to the UPRule2 specified destination.

8 . The method according to claim 1 , wherein UPRule1 and UPRule2 define if routing of UPRule1 and UPRule2 matched traffic is to be done only once for the PDR or after every time the UP is configured.

9 . The method according to claim 1 , wherein UPRule1 and UPRule2 are disabled on the UP equipment when the CP provides rules to the CP equipment for traffic handling.

10 . The method according to claim 1 , wherein UPRule1 and UPRule2 are disabled on the UP equipment based on a load on the UP equipment.

11 . The method according to claim 10 , wherein the load is determined based on:

a vCPU measurement of the UPF; or

a determination that an incoming or outgoing traffic is beyond a threshold of the UPF.

12 . A system for optimizing traffic redirection operations between a Control Plane (CP) and a User Plane (UP) in a mobile phone network for mobile phones comprising:

a Control Plane (CP) computer;

a User Plane (UP) computer;

wherein the CP computer performs the following Policy and Charging Function/Policy and Charging Rule Function (PCF/PCRF) functions:

transmitting a first Policy and Charging Control rule1 (PCCRule1) from the CP computer to the UP computer;

transmitting a second Policy and Charging Control rule2 (PCCRule2) from the CP computer to the UP computer;

installing both the PCCRule1 and PCCRule2 on the UP computer as UPRule1 and UPRule2 respectively, wherein the UPRule1 is set as an active rule and a timer associated with UPRule1 is started;

wherein the UP computer comprises a User Plane Function (UPF) adapted to matching data traffic with a Packet Detection Rule (PDR) to generate identified traffic during the timer associated with UPRule1 to generate UPRule1 matched traffic;

wherein the UPF performs the following functions:

disabling UPRule1 when the timer associated with UPRule1 expires;

routing the UPRule1 matched traffic to a UPRule1 specified destination;

enabling UPRule2 and beginning a timer associated with a configuration of UPRule2;

matching data traffic with the PDR to generate identified traffic during the timer associated with UPRule2 to generate UPRule2 matched traffic;

disabling UPRule2 when the timer associated with UPRule2 expires; and

routing the UPRule2 matched traffic to a UPRule2 specified destination.

13 . The system according to claim 12 , wherein said UPF comprises a gateway responsible for user plane traffic handling between User Equipment (UE) and external packet data networks.

14 . The system according to claim 12 , wherein the UPRule1 causes the UP to be configured each time redirection is done by the UP.

15 . The system according to claim 12 , wherein when the timer associated with UPRule1 expires, the UPF only routes the UPRule1 matched traffic to the UPRule1 specified destination, and when the timer associated with UPRule2 expires, the UPF only routes the UPRule2 matched traffic to the UPRule2 specified destination.

16 . The system according to claim 12 , wherein UPRule1 and UPRule2 define if routing of UPRule1 and UPRule2 matched traffic is to be done only once for the PDR or after every time the UP is configured.

17 . The system according to claim 12 , wherein UPRule1 and UPRule2 are disabled on the UP equipment when the CP provides rules to the CP equipment for traffic handling.

18 . The system according to claim 12 , wherein UPRule1 and UPRule2 are disabled on the UP equipment based on a load on the UP equipment.

19 . The system according to claim 18 , wherein the load is determined based on:

a vCPU measurement of the UPF; or

a determination that an incoming or outgoing traffic is beyond a threshold of the UPF.

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 May 15, 2024
From: MISHRA, ABHISHEK; PADLIKAR, VIPIN; JINDAL, TAMANNA; GUPTA, ROHIT
To: MAVENIR SYSTEMS, INC.
Reel/Frame 067425/0203 →
Priority Claims (1)
IN 202321027557 · Apr 14, 2023 · national
Continuity (1)
Related Publication 20240349117A1 · Oct 17, 2024
References Cited (14)
US 20200145876A1 · Dao · 2020 [cited by examiner]
US 20200351980A1 · Talebi Fard · 2020 [cited by examiner]
US 20200351984A1 · Talebi Fard · 2020 [cited by examiner]
US 20200404106A1 · Belling · 2020 [cited by examiner]
US 20220053603A1 · Talebi Fard · 2022 [cited by examiner]
US 20220239746A1 · Yan et al. · 2022 [cited by applicant]
US 20220321475A1 · Thiebaut · 2022 [cited by examiner]
US 20230362024A1 · Wikström · 2023 [cited by examiner]
US 20250274991A1 · Alvarez Dominguez · 2025 [cited by examiner]
WO 2021144041A1 · 2021 [cited by applicant]
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); Sep. 2019. [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 the User Plane Nodes Stage 3 (Release 16); Apr. 2020. [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); Sep. 2019. [cited by applicant]
Extended European Search Report for corresponding application EP24169741, 9 pages, dated Jun. 17, 2024. [cited by applicant]