IP Library Granted Patent US 10,897,423
Granted Patent B2
US 10,897,423 · App. 16/411,888 · Granted Jan 19, 2021

Congestion avoidance in a slice-based network

Inventors: Raja Kommula (Cupertino, CA); Jeremy Tidemann (Urbana, IL); Constantine Polychronopoulos (Palo Alto, CA); Marc Andre Bordeleau (Shawinigan, CA); Edward Choh (Richmond, CA); Ojas Gupta (Mountain View, CA); Robert Kidd (Champaign, IL); Georgios Oikonomou (Patras, GR)
Assignee: VMWARE, INC.
H04L47/122G06F9/45558H04L41/046H04L41/0896H04L41/5009H04L41/5019H04L43/0852H04L47/2425G06F2009/4557G06F2009/45595
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,897,423
App. No.
16/411,888
Granted
Jan 19, 2021
Kind
B2
Abstract

A system can reduce congestion in slice-based networks, such as a virtual service network (“VSN”). The system can include a monitoring module that communicates with agents on switches, such as routers or servers. The switches report telematics data to the monitoring module, which determines slice-specific performance attributes such as slice latency and slice throughput. These slice-specific performance attributes are compared against software license agreement (“SLA”) requirements. When the SLA is not met, the monitoring module can implement a new slice path for the slice to reduce the congestion.

Claims (43)

1. A method for avoiding congestion in a slice-based network, comprising:

receiving data from multiple switches for a plurality of slices;

determining, based on the data from at least first and second switches, that a service level agreement (“SLA”) is not met for a slice that uses the first and second switches;

selecting an alternate slice path for the slice, the alternate path including a third switch that is not in the existing path for the slice; and

dynamically implementing the alternate slice path, including:

after selecting the alternate slice path, instantiating a virtual network function on the third switch for use with the slice; and

causing the first switch to send traffic for the slice to the third switch instead of the second switch.

2. The method of claim 1 , wherein the data is sent from agents installed at the switches to a remote monitoring module that selects the alternate slice path.

3. The method of claim 1 , wherein the data includes latency, and wherein the alternate slice path is selected based on a monitoring module determining a latency requirement of the SLA is not met.

4. The method of claim 1 , wherein the data includes throughput, and wherein the alternate slice path is selected based on a monitoring module determining a throughput requirement of the SLA is not met.

5. The method of claim 1 , further comprising:

sending the agent to the multiple switches for execution, the agent determining the data by analyzing packets in the physical layer of the switch.

6. The method of claim 1 , further comprising utilizing throughput information from fewer that all of the switches in the original slice path to determine slice throughput.

7. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for avoiding congestion in a slice-based network, the stages comprising:

receiving data from multiple switches for a plurality of slices;

determining, based on the data from at least first and second switches, that a service level agreement (“SLA”) is not met for a slice that uses the first and second switches;

selecting an alternate slice path for the slice, the alternate path including a third switch that is not in the existing path for the slice; and

dynamically implementing the alternate slice path, including:

after selecting the alternate slice path, instantiating a virtual network function on the third switch for use with the slice; and

causing the first switch to send traffic for the slice to the third switch instead of the second switch.

8. The non-transitory, computer-readable medium of claim 7 , wherein the data is sent from agents installed at the switches to a remote monitoring module that selects the alternate slice path.

9. The non-transitory, computer-readable medium of claim 7 , wherein the data includes latency, and wherein the alternate slice path is selected based on a monitoring module determining a latency requirement of the SLA is not met.

10. The non-transitory, computer-readable medium of claim 7 , wherein the data includes throughput, and wherein the alternate slice path is selected based on a monitoring module determining a throughput requirement of the SLA is not met.

11. The non-transitory, computer-readable medium of claim 7 , the stages further comprising:

sending the agent to the multiple switches for execution, the agent determining the data by analyzing packets in the physical layer of the switch.

12. The non-transitory, computer-readable medium of claim 7 , the stages further comprising utilizing throughput information from fewer that all of the switches in the original slice path to determine slice throughput.

13. A system for avoiding congestion in a slice-based network, comprising:

a non-transitory, computer-readable medium containing instructions for a monitoring module; and

a processor that executes the monitoring module to perform stages comprising:

receiving data from multiple switches for a plurality of slices;

determining, based on the data from at least first and second switches, that a service level agreement (“SLA”) is not met for a slice that uses the first and second switches;

selecting an alternate slice path for the slice, the alternate path including a third switch that is not in the existing path for the slice; and

dynamically implementing the alternate slice path, including;

after selecting the alternate slice path, instantiating a virtual network function on the third switch for use with the slice; and

causing the first switch to send traffic for the slice to the third switch instead of the second switch.

14. The system of claim 13 , wherein the data is sent from agents installed at the switches to a remote monitoring module that selects the alternate slice path.

15. The system of claim 13 , wherein the data includes latency, and wherein the alternate slice path is selected based on a monitoring module determining a latency requirement of the SLA is not met.

16. The system of claim 13 , wherein the data includes throughput, and wherein the alternate slice path is selected based on a monitoring module determining a throughput requirement of the SLA is not met.

17. The system of claim 13 , the stages further comprising:

sending the agent to the multiple switches for execution, the agent determining the data by analyzing packets in the physical layer of the switch.

18. The method of claim 1 , wherein the data comprises telematics data.

19. The non-transitory, computer-readable medium of claim 7 , wherein the data comprises telematics data.

20. The system of claim 13 , wherein the data comprises telematics data.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067103/0030 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2019
From: KOMMULA, RAJA; GUPTA, OJAS; BORDELEAU, MARC ANDRE; OIKONOMOU, GEORGIOS; CHOH, EDWARD; TIDEMANN, JEREMY; KIDD, ROBERT; POLYCHRONOPOULOS, CONSTANTINE
To: VMWARE, INC.
Reel/Frame 049175/0934 →
Continuity (1)
Related Publication 20200366611A1 · Nov 19, 2020