IP Library Granted Patent US 12,137,401
Granted Patent B2
US 12,137,401 · App. 17/736,413 · Granted Nov 5, 2024

Method and apparatus for user plane resource optimization

Inventors: Abhishek Mishra (Bangalore, IN); Vipin Padlikar (Bangalore, IN); Rohit Gupta (Bangalore, IN); Tamanna Jindal (McKinney, TX)
Assignee: Mavenir Networks, Inc.
H04W40/02H04W40/246H04W40/26H04W80/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,137,401
App. No.
17/736,413
Filed
May 4, 2022
Granted
Nov 5, 2024
Kind
B2
Art Unit
2472
USPC
370/392
Abstract

A combined User Plane (UP) node optimizes the UP data stream handling for 4G/5G network operation as follows. The combined UP node, which includes an access data plane node, an intermediate data plane node, an anchor data plane node, and a session handling process module. If the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are different, then the downlink and uplink packet stream handling utilizes an intermediate interface path within the combined UP node. If the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are same, then the downlink and uplink packet stream handling does not utilize an intermediate interface path within the combined UP node, but TEID of the unutilized intermediate interface path is used in PFCP response message.

Claims (38)

1. A method of optimizing user plane data stream for at least one of a 4G and 5G network operation involving at least one combined User Plane (UP) node comprising an access data plane node, an intermediate data plane node, an anchor data plane node, and a session handling process module, the method comprising:

ascertaining, by the session handling process module, one of Internet Protocol (IP) addresses or namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node corresponding to Tunnel Endpoint Identifier (TEIDs) assigned for a Packet Forwarding Control Protocol (PFCP) session;

if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are different,

for a downlink connection between a service node and a Radio Access Network (RAN), packets transmitted by a first interface directly connecting the service node to the at least one combined UP node are routed to a second interface located internally within the at least one UP node, and the second interface maps the packets to at least one Tunnel Endpoint Identifier (TEID) associated with at least one third interface directly connecting the at least one combined UP node to the RAN, and

for an uplink connection between the RAN and the service node, packets transmitted by the at least one third interface directly connecting the RAN to the at least one combined UP node are routed to the second interface located internally within the at least one combined UP node, and the second interface maps the packets to the first interface directly connecting the at least one combined UP node to the service node;

if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same,

for a downlink connection between the service node and the RAN, packets transmitted by the first interface directly connecting the service node to the at least one combined UP node are routed directly to the at least one third interface directly connecting the at least one combined UP node to the RAN, and the at least one combined UP node stores at least one TEID of an intermediate path not utilized for the downlink connection, and

for an uplink connection between the RAN and the service node, packets transmitted by the at least one third interface directly connecting the RAN to the at least one combined UP node are routed directly to the first interface directly connecting the at least one combined UP node to the service node, and the at least one combined UP node stores at least one TEID of an intermediate path not utilized for the uplink connection.

2. The method of claim 1 , wherein for at least one of 4G network operation and handover from 5G network to 4G network operation, the access data plane node is Serving Gateway User Plane (SGW-U) node, the intermediate data plane node is Packet Gateway User Plane (PGW-U) node, and the anchor data plane node is Traffic Detection Function User Plane function (TDF-U) node.

3. The method of claim 2 , wherein the first interface directly connecting the service node to the at least one combined UP node is an SGi interface, the second interface located internally within the at least one combined UP node is at least one of S5-U interface and S8-U interface, and the at least one third interface directly connecting the at least one combined UP node to the RAN is at least one of S1-U interface and S12 interface.

4. The method of claim 3 , wherein at least one of S5-U interface and S8-U interface is the intermediate path not utilized for the downlink and the uplink connection in the case the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

5. The method of claim 4 , further comprising:

utilizing, by the at least one combined UP node, the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

6. The method of claim 1 , wherein for at least one of 5G network operation and handover from 4G network to 5G network operation, the access data plane node is at least one of Uplink Classifier (ULCL) node and a Branching Point (BP) node, the intermediate data plane node is an Intermediate User Plane Function (I-UPF) node, and the anchor data plane node is Packet Data Unit Session Anchor (PSA) node.

7. The method of claim 6 , wherein the first interface directly connecting the service node to the at least one combined UP node is an N6 interface, the second interface located internally within the at least one combined UP node is an N9 interface, and the at least one third interface directly connecting the at least one combined UP node to the RAN is an N3 interface.

8. The method of claim 7 , wherein an N9 interface is the intermediate path not utilized for the downlink and the uplink connection in the case the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

9. The method of claim 8 , further comprising:

utilizing, by the at least one combined UP node, the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

10. The method of claim 5 , wherein the session handling process module of the at least one combined UP node utilizes the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

11. A system comprising:

at least one combined User Plane (UP) node configured to optimize user plane data stream handling for at least one of a 4G and 5G network operation, the at least one combined UP node including an access data plane node, an intermediate data plane node, an anchor data plane node, and a session handling process module;

wherein the session handling process module is configured to:

ascertain one of Internet Protocol (IP) addresses or namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node corresponding to Tunnel Endpoint Identifier (TEIDs) assigned for a Packet Forwarding Control Protocol (PFCP) session;

if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are different,

for a downlink connection between a service node and a Radio Access Network (RAN), packets transmitted by a first interface directly connecting the service node to the at least one combined UP node are routed to a second interface located internally within the at least one combined UP node, and the second interface maps the packets to at least one Tunnel Endpoint Identifier (TEID) associated with at least one third interface directly connecting the at least one combined UP node to the RAN, and

for an uplink connection between the RAN and the service node, packets transmitted by the at least one third interface directly connecting the RAN to the at least one combined UP node are routed to the second interface located internally within the at least one combined UP node, and the second interface maps the packets to the first interface directly connecting the at least one combined UP node to the service node;

if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same,

for a downlink connection between the service node and the RAN, packets transmitted by the first interface directly connecting the service node to the at least one combined UP node are routed directly to the at least one third interface directly connecting the at least one combined UP node to the RAN, and the at least one combined UP node stores at least one TEID of an intermediate path not utilized for the downlink connection, and

for an uplink connection between the RAN and the service node, packets transmitted by the at least one third interface directly connecting the RAN to the at least one combined UP node are routed directly to the first interface directly connecting the at least one combined UP node to the service node, and the at least one combined UP node stores at least one TEID of an intermediate path not utilized for the uplink connection.

12. The system of claim 11 , wherein for at least one of 4G network operation and handover from 5G network to 4G network operation, the access data plane node is Serving Gateway User Plane (SGW-U) node, the intermediate data plane node is Packet Gateway User Plane (PGW-U) node, and the anchor data plane node is Traffic Detection Function User Plane function (TDF-U) node.

13. The system of claim 12 , wherein the first interface directly connecting the service node to the at least one combined UP node is an SGi interface, the second interface located internally within the at least one combined UP node is at least one of S5-U interface and S8-U interface, and the at least one third interface directly connecting the at least one combined UP node to the RAN is at least one of S1-U interface and S12 interface.

14. The system of claim 13 , wherein at least one of S5-U interface and S8-U interface is the intermediate path not utilized for the downlink and the uplink connection in the case the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

15. The system of claim 14 , wherein the at least one combined UP node utilizes the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

16. The system of claim 11 , wherein for at least one of 5G network operation and handover from 4G network to 5G network operation, the access data plane node is at least one of Uplink Classifier (ULCL) node and a Branching Point (BP) node, the intermediate data plane node is an Intermediate User Plane Function (I-UPF) node, and the anchor data plane node is Packet Data Unit Session Anchor (PSA) node.

17. The system of claim 16 , wherein the first interface directly connecting the service node to the at least one combined UP node is an N6 interface, the second interface located internally within the at least one combined UP node is an N9 interface, and the at least one third interface directly connecting the at least one combined UP node to the RAN is an N3 interface.

18. The system of claim 17 , wherein an N9 interface is the intermediate path not utilized for the downlink and the uplink connection in the case the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

19. The system of claim 18 , wherein the at least one combined UP node utilizes the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

20. The system of claim 15 , wherein the session handling process module of the at least one combined UP node utilizes the at least one TEID of the intermediate path not utilized for the downlink and uplink connection, in at least one Packet Forwarding Control Protocol (PFCP) response message, if the IP addresses or the namespaces of the access data plane node, the intermediate data plane node, and the anchor data plane node are the same.

Assignments (19)
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069115 AND FRAME 0815 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR NETWORKS, INC.
Reel/Frame 072307/0408 →
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 INTEREST IN ADDITIONAL COLLATERAL RECORDED AT REEL 068462 AND FRAME 0594 Recorded Jul 29, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR NETWORKS, INC.
Reel/Frame 072261/0043 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR NETWORKS, INC.
Reel/Frame 072262/0363 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR NETWORKS, INC.
Reel/Frame 072262/0409 →
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 →
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 →
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 NETWORKS, INC.
To: GLAS USA LLC
Reel/Frame 069115/0815 →
RELEASE OF SECURITY INTEREST RECORDED AT R/F 068453/0642 Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR NETWORKS, INC.
Reel/Frame 069117/0074 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR NETWORKS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068453/0642 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 19, 2024
From: MAVENIR NETWORKS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB, AS COLLATERAL AGENT
Reel/Frame 068462/0594 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0372 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0381 →
SECURITY INTEREST Recorded May 29, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 067565/0678 →
SECURITY AGREEMENT SUPPLEMENT Recorded Jul 13, 2022
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060640/0155 →
SECURITY AGREEMENT Recorded Jul 13, 2022
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060641/0242 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 4, 2022
From: MISHRA, ABHISHEK; PADLIKAR, VIPIN; GUPTA, ROHIT; JINDAL, TAMANNA
To: MAVENIR NETWORKS, INC
Reel/Frame 059812/0678 →