IP Library Granted Patent US 11,374,830
Granted Patent B2
US 11,374,830 · App. 16/722,795 · Granted Jun 28, 2022

Dynamic slice bandwidth multiplexing based on slice priority

Inventors: Robert Kidd (Champaign, IL); 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); Georgios Oikonomou (Patras, GR); Mingjie Zhao (Sunnyvale, CA)
Assignee: VMWARE, INC.
H04L41/5022H04L41/0896H04L41/5006H04L41/5025H04L45/507H04L47/805H04L49/101H04W28/20H04W28/24H04W76/12
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 11,374,830
App. No.
16/722,795
Granted
Jun 28, 2022
Kind
B2
Abstract

In a slice-based network, slice multiplexers can be used to anchor inter-cloud tunnels across different clouds in a slice path. The slice multiplexers can dynamically change a total allocated bandwidth of an outer tunnel and reconfigure relative slice bandwidths of inner tunnels. This can result in an optimized bandwidth allocation that enforces slice priorities, maintains required SLA performance levels, and minimizes total allocated bandwidth on the network connection. The dynamic changes can be based on slice priority levels, total number of slices, and historical slice throughput.

Claims (30)

1. A method for intercloud slice connectivity, comprising:

creating a slice multiplexer pair that connects traffic from a first cloud to a second cloud, the slice multiplexer pair including a corresponding slice multiplexer in each of the first and second clouds, each slice multiplexer of the pair comprising: multiple slice connections, each having a slice bandwidth allotment; and a total bandwidth allotment; and

setting the total bandwidth allotment at both slice multiplexers of the pair as a function of the slice bandwidth allotments multiplied by weighting factors, wherein the weighting factors correspond to slice priority levels.

2. The method of claim 1 , wherein packets are routed to different channels within the slice multiplexer pair based on a slice identifier.

3. The method of claim 1 , further comprising adjusting the total bandwidth allotment and at least one slice bandwidth allotment based on a first slice using less than its corresponding slice bandwidth allotment.

4. The method of claim 3 , wherein the total bandwidth allotment decreases and a slice bandwidth allotment for a second slice increases.

5. The method of claim 1 , wherein multiple tenants share the multiple slice connections between the first and second clouds.

6. The method of claim 1 , further comprising configuring connections between first and second service function chain steering nodes and the slice multiplexer pair.

7. The method of claim 6 , wherein a controller sends commands to configure the connections, including connecting the first and second service function chain steering nodes to a crossbar switch, and wherein the crossbar switch routes first packets for a first set of slices to a first slice multiplexer and second packets for a second set of slices to a second slice multiplexer, both the first and second slice multiplexers being in the first cloud.

8. A non-transitory, computer-readable medium comprising instructions that are executed by a processor to perform stages for intercloud slice connectivity, the stages comprising:

creating a slice multiplexer pair that connects traffic from a first cloud to a second cloud, the slice multiplexer pair including a corresponding slice multiplexer in each of the first and second clouds, the slice multiplexer pair comprising: multiple slice connections, each having a slice bandwidth allotment; and a total bandwidth allotment; and

setting the total bandwidth allotment at both multiplexers of the pair as a function of the slice bandwidth allotments multiplied by weighting factors, wherein the weighting factors correspond to slice priority levels.

9. The non-transitory, computer-readable medium of claim 8 , wherein packets are routed to different channels within the slice multiplexer pair based on a slice identifier.

10. The non-transitory, computer-readable medium of claim 8 , the stages further comprising adjusting the total bandwidth allotment and at least one slice bandwidth allotment based on a first slice using less than its corresponding slice bandwidth allotment.

11. The non-transitory, computer-readable medium of claim 10 , wherein the total bandwidth allotment decreases and a slice bandwidth allotment for a second slice increases.

12. The non-transitory, computer-readable medium of claim 8 , wherein multiple tenants share the multiple slice connections between the first and second clouds.

13. The non-transitory, computer-readable medium of claim 8 , the stages further comprising configuring connections between first and second service function chain steering nodes and the slice multiplexer pair.

14. The non-transitory, computer-readable medium of claim 13 , wherein the configuration includes connecting the first and second service function chain steering nodes to a crossbar switch, and wherein the crossbar switch routes first packets for a first set of slices to a first slice multiplexer and second packets for a second set of slices to a second slice multiplexer, both the first and the second slice multiplexers being in the first cloud.

15. A system for intercloud slice connectivity, comprising:

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

a processor that executes the instructions to perform stages comprising:

creating a slice multiplexer pair that connects traffic from a first cloud to a second cloud, the slice multiplexer pair including a corresponding slice multiplexer in each of the first and second clouds, the slice multiplexer pair comprising:

multiple slice connections, each having a slice bandwidth allotment; and

a total bandwidth allotment; and

setting the total bandwidth allotment at both multiplexers of the pair as a function of the slice bandwidth allotments multiplied by weighting factors, wherein the weighting factors correspond to slice priority levels.

16. The system of claim 15 , wherein packets are routed to different channels within the slice multiplexer pair based on a slice identifier.

17. The system of claim 15 , the stages further comprising adjusting the total bandwidth allotment and at least one slice bandwidth allotment based on a first slice using less than its corresponding slice bandwidth allotment.

18. The system of claim 17 , wherein the total bandwidth allotment decreases and a slice bandwidth allotment for a second slice increases.

19. The system of claim 15 , wherein multiple tenants share the multiple slice connections between the first and second clouds.

20. The system of claim 15 , the stages further comprising configuring connections between first and second service function chain steering nodes and the slice multiplexer pair, wherein a controller sends commands to configure the connections, including connecting the first and second service function chain steering nodes to a crossbar switch, and wherein the crossbar switch routes first packets for a first set of slices to a first slice multiplexer and second packets for a second set of slices to a second slice multiplexer, both the first and second slice multiplexers being in the first cloud.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2019
From: KIDD, ROBERT; KOMMULA, RAJA; TIDEMANN, JEREMY; POLYCHRONOPOULOS, CONSTANTINE; BORDELEAU, MARC ANDRE; CHOH, EDWARD; GUPTA, OJAS; OIKONOMOU, GEORGIOS; ZHAO, MINGJIE
To: VMWARE, INC.
Reel/Frame 051345/0478 →