IP Library › Granted Patent US 12,068,888
Granted Patent B2
US 12,068,888 · App. 18/231,580 · Granted Aug 20, 2024

System and method for a multi-tenant datacenter with layer 2 interconnection and cloud storage

Inventors: Luke Matthew Norris (Silverthorn, CO); Matthew Alan Wallace (Highlands Ranch, CO); Bryan James Gallant (Thornton, CO); Hooker Ashley Heggestad (Lafyette, CO)
Assignee: THE FACTION GROUP LLC
H04L12/4666G06F9/5077H04L12/4633H04L12/4641H04L12/465H04L67/10H04L45/66H04L67/1097H04L69/324H04L2212/00
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,068,888
App. No.
18/231,580
Granted
Aug 20, 2024
Kind
B2
Abstract

Provided is a system and method for a multi-tenant datacenter with layer 2 cloud interconnection and cloud storage. More specifically, the datacenter providing cloud storage, includes a plurality of Client Systems coupled to a first datacenter each Client System having a set of infrastructure resources and an initial networking configuration; and a first cloud computing environment established in the first datacenter, and coupled to the Client Systems by OSI Layer 2 as a data link layer for the transfer of data frames, each frame having a plurality of OSI Layer 2 tags, the first cloud computing environment providing storage resources for allocation to at least two Client Systems, the plurality of OSI Layer 2 tags permitting the at least two Client Systems to have overlapping network configurations. An associated method of providing a multi-tenant datacenter with layer 2 cloud interconnection and cloud storage is also provided.

Claims (35)

1. A datacenter, utilizing Open System Interconnection (OSI) frame header tags to isolate transmission data in Layer 2 Frames apart from Layer 3 packets, comprising:

a plurality of client systems coupled to a first datacenter each client system having a set of infrastructure resources and a client defined networking configuration; and

a first cloud computing environment established in the first datacenter, and coupled to the client systems at a protocol level for the transfer of frames at a protocol other than an Internet Protocol (IP), with a plurality of different OSI frame header tags uniquely identifying each of the plurality of client systems, wherein each client system self-direct software defined networking.

2. The datacenter of claim 1 , wherein client data traffic at an internet protocol is transparently tagged and isolated at OSI Layer 2.

3. The datacenter of claim 1 , wherein coupling between the client systems and the datacenter is facilitated at least in part by at least one switch having a routing map, the routing map indicating different OSI frame header tags for each client system.

4. The datacenter of claim 1 , wherein the map permits isolation of each client defined network configuration as a distinct virtual local area network (VLAN) based on header tags.

5. The datacenter of claim 4 , wherein the map permits at least two client systems to have overlapping virtual local area networks (VLANs) and or overlapping IP address ranges.

6. The datacenter of claim 1 , wherein a first set of header tags are associated with a first virtual local area network (VLAN) of a first client system and a second set of header tags are associated with a second virtual local area network (VLAN) of a second client system.

7. The datacenter of claim 1 , wherein the first cloud computing environment virtually extends the infrastructure resources of at least one client system.

8. A datacenter, utilizing Open System Interconnection (OSI) frame header tags to uniquely identify transmission data in Layer 2 Frames apart from Layer 3 packets, comprising:

a plurality of client systems coupled to a first datacenter each client system having a set of infrastructure resources and a client defined networking configuration; and

a first cloud computing environment established in the first datacenter, and coupled to the client systems at a protocol level for the transfer of frames at a protocol other than an Internet Protocol (IP), with a plurality of different OSI frame header tags uniquely identifying each of the plurality of client systems, such that at least two client systems are permitted to have overlapping network configurations.

9. The datacenter of claim 8 , wherein client data traffic at an internet protocol is transparently tagged and isolated at OSI Layer 2.

10. The datacenter of claim 8 , wherein coupling between the client systems and the datacenter is facilitated at least in part by at least one switch having a routing map, the routing map indicating different OSI frame header tags for each client system.

11. The datacenter of claim 10 , wherein the map permits isolation of each client defined network configuration as a distinct virtual local area network (VLAN) based on header tags.

12. The datacenter of claim 10 , wherein the map permits at least two client systems to have overlapping virtual local area networks (VLANs) and or overlapping IP address ranges.

13. The datacenter of claim 8 , wherein a first set of header tags are associated with a first virtual local area network (VLAN) of a first client system and a second set of header tags are associated with a second virtual local area network (VLAN) of a second client system.

14. A cloud system for client systems utilizing Open System Interconnection (OSI) frame header tags to isolate transmission data in Layer 2 Frames apart from Layer 3 packets, comprising:

A plurality of datacenters interconnected at OSI Layer 2, each datacenter having a plurality of client systems connected thereto, each client system having a set of infrastructure resources and a client defined networking configuration; and

a cloud computing environment established in the first datacenter, and coupled to the client systems at a protocol level for the transfer of frames at a protocol other than an Internet Protocol (IP), with a plurality of different OSI frame header tags uniquely identifying each of the plurality of client systems, such that at least two client systems are permitted to have overlapping network configurations.

15. The cloud system of claim 14 , further including at least one OSI Layer 2 tag for identification of a datacenter.

16. The cloud system of claim 14 , further including at least one OSI Layer 2 tag for identification of a network IP address for a remote datacenter.

17. The cloud system of claim 14 , wherein coupling between the client systems and the datacenters is facilitated at least in part by at least one switch having a routing map, the routing map indicating different OSI frame header tags for each client system.

18. The cloud system of claim 17 , wherein the map permits isolation of each client defined network configuration as a distinct virtual local area network (VLAN) based on header tags.

19. The cloud system of claim 17 , wherein the map permits at least two client systems to have overlapping virtual local area networks (VLANs) and or overlapping IP address ranges.

20. The cloud system of claim 14 , wherein a first set of header tags are associated with a first virtual local area network (VLAN) of a first client system and a second set of header tags are associated with a second virtual local area network (VLAN) of a second client system.

21. A method for providing a datacenter utilizing Open System Interconnection (OSI) frame header tags to isolate transmission data in Layer 2 Frames apart from Layer 3 packets, comprising:

establishing within at a first data center a first cloud computing environment;

connecting a plurality of client systems to the first datacenter, each client system having a set of infrastructure resources and a client defined networking configuration, the client systems connected to the first datacenter at a protocol level for the transfer of frames at a protocol other than an Internet Protocol (IP), with a plurality of different OSI frame header tags uniquely identifying each of the plurality of client systems, wherein each client system self-direct software defined networking.

22. The method of claim 21 , wherein client data traffic at an internet protocol is transparently tagged and isolated at OSI Layer 2.

23. The method of claim 21 , wherein coupling between the client systems and the datacenter is facilitated at least in part by at least one switch having a routing map, the routing map indicating different OSI frame header tags for each client system.

24. The method of claim 23 , wherein the map permits isolation of each client defined network configuration as a distinct virtual local area network (VLAN) based on header tags.

25. The method of claim 23 , wherein the map permits at least two client systems to have overlapping virtual local area networks (VLANs) and or overlapping IP address ranges.

26. The method of claim 21 , wherein a first set of header tags are associated with a first virtual local area network (VLAN) of a first client system and a second set of header tags are associated with a second virtual local area network (VLAN) of a second client system.

27. The method of claim 21 , wherein the first cloud computing environment virtually extends the infrastructure resources of at least one client system.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2024
From: THE FACTION GROUP LLC
To: FACTION ABC, LLC
Reel/Frame 069041/0833 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 11, 2023
From: NORRIS, LUKE MATTHEW; WALACE, MATTHEW ALAN; GEGGESTAD, HOOKER ASHLEY; GALLANT, BRYAN JAMES
To: THE FACTION GROUP LLC
Reel/Frame 064560/0947 →
Continuity (7)
Continuation 17141747 · Jan 5, 2021
Continuation 16711315 · Dec 11, 2019
Continuation In Part 16104834 · Aug 17, 2018
Continuation 15424651 · Feb 3, 2017
Continuation 14621320 · Feb 12, 2015
Continuation 13356555 · Jan 23, 2012
Related Publication 20230388152A1 · Nov 30, 2023