IP Library Granted Patent US 10,827,544
Granted Patent B1
US 10,827,544 · App. 16/847,079 · Granted Nov 3, 2020

Methods and systems for 5G traffic routing in IPX with network slicing

Inventors: Edward Yau (Tseung Kwan O, HK); Huiyue Xu (Tampa, FL); Prashant Datar (Tampa, FL); Ravi Tandon (Sandweiler, LU); Rakesh Mehta (Tampa, FL)
Assignee: Syniverse Technologies, LLC
H04W76/12H04W8/02H04W40/12H04W40/20
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 10,827,544
App. No.
16/847,079
Granted
Nov 3, 2020
Kind
B1
Abstract

A system and method for routing of 5G mobile data traffic along a routing path in an Internetwork Packet Exchange (IPX) network having requisite Quality of Service (QoS). A proxy is deployed in the IPX network to intercept Session Create request and response messages exchanges between the home network and the visited network. The routing platform extracts Single-Network Slice Selection Assistance Information (S-NSSAI) attribute and uses this attribute and the geographic locations of the visited network and the home network to select a routing path in the IPX network having requisite QoS for the network slice use case. The routing platform uses layer-3 routing technique to anchor User Plane Function (UPF) Proxies deployed at different routing paths in the IPX network. Alternately, the routing platform uses layer-2 routing technique, with Software-Defined Networking (SDN) controller and SDN-switches to route traffic via the selected routing path in the IPX network.

Claims (18)

1. A method of routing 5G roaming mobile data traffic between a visited public land mobile network (VPLMN) and a home public land mobile network (HPLMN) interconnected via an Internetwork Packet Exchange (IPX) network having a plurality of predefined routing paths, comprising:

capturing, within the IPX network, a Protocol Data Unit (PDU) Session Create request message from the VPLMN, wherein the PDU Session Create request message carries a Single-Network Slice Selection Assistance Information (S-NS SAI) value and an Internet Protocol (IP) address of a visited User Plane Function (v-UPF);

identifying the S-NSSAI value within the PDU Session Create request message;

selecting a first routing path from the plurality of predefined routing paths in the IPX network based on the S-NSSAI value identified from the PDU Session Create Request message, wherein the first routing path is associated with a first UPF-Proxy deployed in the IPX network, the first routing path configured to provide a predefined Quality of Service (QoS) for data traffic associated with the S-NSSAI value;

modifying the PDU Session Create Request message by replacing the IP address of the v-UPF with an IP address of the first UPF-Proxy, thereby creating a modified PDU Session Create request message;

sending the modified PDU Session Create request message to the HPLMN;

capturing, within the IPX network, a PDU Session Create response message from the HPLMN, wherein the PDU Session Create response message carries an IP address of the home User Plane Function (h-UPF);

modifying the PDU Session Create response message by replacing the IP address of the h-UPF with an IP address of a second UPF-Proxy associated with a second routing path in the IPX network, thereby creating a modified PDU Session Create response message; and

sending the modified PDU Session Create response message to the VPLMN;

wherein subsequent uplink data packets from the VPLMN to the HPLMN are delivered to the first UPF-Proxy via the first routing path in the IPX network, and wherein subsequent downlink data packets from the HPLMN to the VPLMN are delivered to the second UPF-Proxy via the second routing path in the IPX network.

2. The method of claim 1 , wherein the second routing path is the same as the first routing path and the second UPF-Proxy is the same as the first UPF-Proxy.

3. The method of claim 1 , wherein the second routing path is different than the first routing path and the second UPF-Proxy is different than the first UPF-Proxy.

4. The method of claim 1 , wherein a geographic location of the VPLMN or the HPLMN is used as a factor in selecting the first routing path, the second routing path, or both.

5. The method of claim 1 , wherein the an ‘ipv4Addr’ value or an ‘ipv6Addr’ value in a ‘vcnTunnelInfo’ attribute of the PDU Session Create Request message is replaced with the IP address of the first UPF-Proxy.

6. The method of claim 1 , wherein the an ‘ipv4Addr’ value or an ‘ipv6Addr’ value in a ‘hcnTunnelInfo’ attribute of the PDU Session Create Response message is replaced with the IP address of the second UPF-Proxy.

7. The method of claim 1 , wherein each of the plurality of the predefined routing paths in the IPX network has one or more attributes associated with a 5G use case.

8. The method of claim 7 , wherein the 5G use case is selected from the group consisting of an Enhanced Mobile Broadband (eMBB), Massive Internet Of Things (mIoT), and Ultra-Reliable and Low Latency Communications (uRLLC).

9. The method of claim 7 , wherein the one or more attributes associated with the 5G use case is selected from the group consisting of bandwidth, latency, cost, capacity, and reliability.

Assignments (2)
NOTICE AND CONFIRMATION OF GRANT OF SECURITY INTEREST IN PATENTS Recorded May 16, 2022
From: SYNIVERSE TECHNOLOGIES, LLC
To: BARCLAYS BANK PLC, AS COLLATERAL AGENT
Reel/Frame 060072/0598 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 24, 2020
From: YAU, EDWARD; XU, HUIYUE; DATAR, PRASHANT; TANDON, RAVI; MEHTA, RAKESH
To: SYNIVERSE TECHNOLOGIES, LLC
Reel/Frame 052484/0371 →