Enabling virtual workloads using overlay technologies to interoperate with physical network services
A solution is provided to enable cloud service provider customers/users to offer physical network services to virtualized workloads that use overlay technologies, such as a Virtual Extensible Local Area Network (VXLAN). For a virtual workload that uses an overlay technology, an identifier is received of a logical network to which the virtual workload connects and a policy for the logical network. Based on the identifier of the logical network and the policy, a gateway is configured to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of the physical network service equipment on which the policy is configured.
Latest CISCO TECHNOLOGY, INC. Patents:
This application is a continuation of U.S. patent application Ser. No. 13/789,721, filed Mar. 8, 2013, which claims priority to U.S. Provisional Application No. 61/736,577, filed Dec. 13, 2012. The entirety of these applications is incorporated herein by reference.
TECHNICAL FIELDThe present disclosure relates to virtual switches that use overlay technologies.
BACKGROUNDVirtualization of workloads has become pervasive and there is a need for customers to be able to use the existing installed base of physical network services (such as firewalls, load balancers etc.) to offer network service capability to the virtualized workloads in the same way as in the physical environment, in an on-demand, dynamic fashion, particularly in cloud service provider environments.
In the physical (baremetal) environment, application traffic is assigned to a specific virtual local area network (VLAN) to be sent to the firewall and the traffic from the firewall is sent on another VLAN for ultimate transmission to the network service. To satisfy the needs of large scale multi-tenancy requirements, overlay technologies such as Virtual Extensible LANs (VXLANs) are becoming popular. However, there is no easy way to offer physical network services (such as firewall services) for virtualized workloads using an overlay technology.
A solution is provided to enable cloud service provider customers/users to offer physical network services to virtualized workloads that use overlay technologies, such as a Virtual Extensible Local Area Network (VXLAN). For a virtual workload that uses an overlay technology, an identifier is received of a logical network to which the virtual workload connects and a policy for the logical network. Based on the identifier of the logical network and the policy, a gateway is configured to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of the physical network service equipment on which the policy is configured.
Example EmbodimentsA solution is presented herein that configures a gateway entity and one or more physical networking services so as to extend the physical networking services to virtualized network endpoints.
Reference is first made to
On the left side of the diagram, there is a virtual switch 30 running in a hypervisor 40 in a data center. The data center and its supporting equipment are not shown in
VXLAN is a technology to allow for “floating” virtual domains on top of a common networking and virtualization infrastructure. By leveraging industry-standard Ethernet technology, large numbers of virtual domains can be created, which can be isolated from each other and the underlying network. VXLAN provides the capability to create isolated, multi-tenant broadcast domains across data center fabrics, allowing for the creation of logical networks that span physical network boundaries.
VXLAN can be used to abstract a network into a generalized pool of network capacity. The use of these services can be separated from the underlying physical infrastructure. This pool can span physical boundaries, optimizing compute resource utilization across clusters, pods and even geographically separated datacenters. The pool of network capacity can be segmented into logical networks directly associated with specific applications.
VXLAN operates by creating Layer 2 logical networks that are encapsulated in standard Layer 3 IP packets. A “Segment ID” in every frame differentiates the individual logical networks (VXLANs) from each other. Numerous isolated Layer 2 VXLAN networks can therefore co-exist on a common Layer 3 infrastructure.
An example of another overlay technology that may be used, as an alternative to VXLAN, is Network Virtualization using Generic Routing Encapsulation (NVGRE).
A virtual service 70 is in communication with the virtual switch 30. Examples of a virtual service 70 include a Virtual Security Gateway (VSG) that serves as a virtual firewall appliance providing trusted access to virtual data center and cloud environments, a Virtual Wide Area Application Services (vWAAS) for application acceleration in private and public cloud environments, and a cloud router. There are virtual workloads, e.g., virtual machines, shown at reference numeral 80 in
The arrangement shown in
Reference is now made to
A tie-in is built between the VXLAN segment_id that a virtual machine (VM) is using with the VLAN that is needed to transport the traffic to the appropriate context that is configured in the physical network service equipment, e.g., a firewall context in the case where the physical network service equipment is a firewall.
Turning now to
Each VM is created within a tenant container. At step 120, through the physical services manager 94, a customer provisions the physical network service equipment 20 with a context for each tenant. Tenant VM policies are configured within each context. One or more VLANs may be associated with each context. Thus, each context contains multiple VLAN interfaces, each with its own policy configuration.
At 130, using the CMP 90, a user/customer acting on behalf of a tenant, defines a policy for each logical network (e.g., VXLAN) to which VMs connect. This policy is to be enforced by the physical network service equipment 20.
At 140, the CMP 90 sends the logical network identifier, tenant_id and policy information (VXLAN segment_id, tenant_id, policy) to the physical services manager 94. At 150, the physical services manager 94 configures the VXLAN/VLAN gateway 50 to connect the VXLAN segment to the VLAN_id on which the policy will be applied. At 160, the physical services manager 94 defines the policy on the physical network service equipment 20 within the given tenant's service context and instructs it to apply it on the VLAN_id to which the VXLAN segment is connected. The VXLAN/VLAN gateway 50 bridges traffic between a particular VXLAN segment_id (e.g. VXLAN 5500) and a VLAN_id (e.g. VLAN-55). In this example, VLAN 55 belongs to a particular context. The contexts and the associated security policies may be pre-provisioned in the physical network service equipment 20.
The CMP 90 will send this information (VXLAN segment_id, VLAN_id, context_name) to the physical services manager 94 which in turn configures the VXLAN/VLAN gateway 50 (for the VXLAN to VLAN mapping) and the physical services network equipment 20 for the VLAN to the context-name mapping.
Once this is setup, the VMs that connect to the network will send their traffic on that specific VXLAN segment-id through the virtual switch and to the VXLAN/VLAN gateway 50. The VXLAN/VLAN gateway 50 will bridge that traffic to the correct VLAN as defined in the mapping. The physical network service equipment 20 will apply the appropriate policy to the traffic as defined in the VLAN-context mapping. This process does not require any changes to the existing physical network service equipment 20.
Reference is now made to
Turning now to
The memory 420 may comprise read only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory 420 may comprise one or more tangible (non-transitory) computer readable storage media (e.g., a memory device) encoded with software comprising computer executable instructions and when the software is executed (by the processor 410) it is operable to perform the operations described herein. More specifically, stored/encoded in memory 420 are instructions for physical services manager process logic 500, that when executed by processor 410, cause the processor 410 to perform the operations described herein for the CMP 90, virtual services manager 92 and physical services manager 94 in connection with
In summary, the foregoing solution provides for automated on-demand provisioning to leverage the installed base of physical network services. From a method perspective, a method is providing in which, for a virtual workload that uses an overlay technology, receiving an identifier of a logical network to which the virtual workload connects and a policy for the logical network; and based on the identifier of the logical network and the policy, configuring a gateway to connect traffic for the virtual workload on the logical network to a particular VLAN interface of the physical network service equipment on which the policy is configured.
This method may be embodied or implemented by computer executable instructions stored or encoded in a computer readable storage media, wherein the instructions are operable to: for a virtual workload that uses an overlay technology, receive an identifier of a logical network to which the virtual workload connects and a policy for the logical network; and based on the identifier of the logical network and the policy, configure a gateway to connect traffic for the virtual workload on the logical network to a particular VLAN interface of the physical network service equipment on which the policy is configured.
Further still, an apparatus, such as a computing apparatus, may be configured to perform these techniques. The apparatus comprises a network interface unit configured to enable network communications; a memory; and a processor coupled to the network interface unit and the memory, wherein the processor is configured to: for a virtual workload that uses an overlay technology, receive an identifier of a logical network to which the virtual workload connects and a policy for the logical network; and based on the identifier of the logical network and the policy, configure a gateway to connect traffic for the virtual workload on the logical network to a particular VLAN interface of the physical network service equipment on which the policy is configured.
The above description is intended by way of example only.
Claims
1. A method comprising:
- receiving an identifier of a logical network to which a virtual workload connects and a policy for the logical network, wherein the virtual workload is associated with an overlay technology; and
- configuring, based on the identifier of the logical network and the policy, a gateway to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of physical network service equipment on which the policy is configured, wherein the physical network service equipment is provisioned with a service context for each of a plurality of tenants.
2. The method of claim 1, wherein receiving comprises receiving an identifier for a Virtual Extensible Local Area Network (VXLAN) segment associated with the virtual workload, and wherein configuring comprises configuring a VXLAN/VLAN gateway to connect traffic for the VXLAN segment to the particular VLAN.
3. The method of claim 2, wherein the physical network service equipment is preconfigured with one or more policies, each with a corresponding context and VLAN identifier, and further comprising:
- publishing information pertaining to the policies preconfigured on the physical network service equipment and corresponding VLAN identifiers to a cloud management platform;
- configuring a pool of VXLAN-based networks for each tenant in the cloud management platform; and
- selecting a policy when a network is allocated from a particular tenant's pool of networks and generating information comprising a VXLAN segment identifier and a policy identifier;
- wherein configuring the gateway is based on the VXLAN segment identifier and the policy identifier.
4. The method of claim 2, further comprising:
- creating a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configuring a pool of VXLAN-based networks for each tenant in the cloud management platform;
- generating information comprising a policy, VXLAN segment identifier and tenant identifier based on the pool of VXLAN-based networks configured;
- allocating a VLAN for a newly instantiated tenant network and creating a VLAN interface on the physical network service equipment;
- configuring the policy obtained from the cloud management platform on the VLAN interface in the physical network service equipment within a tenant context based on the tenant identifier; and
- wherein configuring the gateway comprises configuring a VXLAN/VLAN gateway to connect the VXLAN-based tenant network to the VLAN interface on the physical network service equipment based on the VXLAN segment identifier.
5. The method of claim 1, further comprising:
- provisioning the physical network service equipment with the service context for each tenant; and
- configuring the physical network service equipment with multiple policies, each policy within a service context for a particular tenant and having a policy identifier, and one VLAN being associated with each policy.
6. The method of claim 5, further comprising, through a cloud management platform, defining a policy for each logical network to which virtual machines within a service context connect.
7. The method of claim 6, wherein configuring the gateway is based on a logical network identifier, tenant identifier and policy information received from the cloud management platform.
8. One or more non-transitory computer readable storage media encoded with computer executable instructions that, when executed by a processor, cause the processor to:
- receive an identifier of a logical network to which a virtual workload connects and a policy for the logical network, wherein the virtual workload is associated with an overlay technology; and
- configure, based on the identifier of the logical network and the policy, a gateway to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of physical network service equipment on which the policy is configured, wherein the physical network service equipment is provisioned with a service context for each of a plurality of tenants.
9. The non-transitory computer readable storage media of claim 8, wherein the instructions that cause the processor to receive an identifier of a logical network comprise instructions that cause the processor to receive an identifier for a Virtual Extensible Local Area Network (VXLAN) segment associated with the virtual workload, and wherein configuring comprises configuring a VXLAN/VLAN gateway to connect traffic for the VXLAN segment to the particular VLAN.
10. The non-transitory computer readable storage media of claim 9, wherein the physical network service equipment is preconfigured with one or more policies, each with a corresponding context and VLAN identifier, and further comprising instructions that cause the processor to:
- publish information pertaining to the policies preconfigured on the physical network service equipment and corresponding VLAN identifiers to a cloud management platform;
- configure a pool of VXLAN-based networks for each tenant in the cloud management platform; and
- select a policy when a network is allocated from a particular tenant's pool of networks and generating information comprising a VXLAN segment identifier and a policy identifier;
- wherein the instructions that cause the processor to configure comprise instructions that cause the processor to configure the gateway based on the VXLAN segment identifier and the policy identifier.
11. The non-transitory computer readable storage media of claim 9, further comprising instructions that cause the processor to:
- create a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configure a pool of VXLAN-based networks for each tenant in the cloud management platform;
- generate information comprising a policy, VXLAN segment identifier and tenant identifier based on the pool of VXLAN-based networks configured;
- allocate a VLAN for a newly instantiated tenant network and creating a VLAN interface on the physical network service equipment; and
- configure the policy obtained from the cloud management platform on the VLAN interface in the physical network service equipment within a tenant context based on the tenant identifier; and
- wherein the instructions operable to configure the gateway comprises instructions operable to configure a VXLAN/VLAN gateway to connect the VXLAN-based tenant network to the VLAN interface on the physical network service equipment based on the VXLAN segment identifier.
12. The non-transitory computer readable storage media of claim 8, further comprising instructions that cause the processor to:
- provision the physical network service equipment with the service context for each tenant; and
- configure the physical network service equipment with multiple policies, each policy within a service context for a particular tenant and having a policy identifier, and one VLAN being associated with each policy.
13. The non-transitory computer readable storage media of claim 12, further comprising instructions that cause the processor to define a policy for each logical network to which virtual machines within a service context connect.
14. The non-transitory computer readable storage media of claim 13, wherein the instructions that cause the processor to configure the gateway comprise instructions that cause the processor to configure the gateway based on a logical network identifier, tenant identifier and policy information received from the cloud management platform.
15. An apparatus comprising:
- a network interface unit configured to enable network communications; and
- a memory;
- a processor coupled to the network interface unit and the memory, wherein the processor is configured to: process a received identifier of a logical network to which a virtual workload connects and a policy for the logical network, wherein the virtual workload is associated with an overlay technology; and configure, based on the identifier of the logical network and the policy, a gateway to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of physical network service equipment on which the policy is configured, wherein the physical network service equipment is provisioned with a service context for each of a plurality of tenants.
16. The apparatus of claim 15, wherein the processor is configured to receive an identifier for a Virtual Extensible Local Area Network (VXLAN) segment associated with the virtual workload, and to configuring a VXLAN/VLAN gateway to connect traffic for the VXLAN segment to the particular VLAN.
17. The apparatus of claim 16, wherein the physical network service equipment is preconfigured with one or more policies, each with a corresponding context and VLAN identifier, and wherein the processor is further configured to:
- publish information pertaining to the policies preconfigured on the physical network service equipment and corresponding VLAN identifiers to a cloud management platform; configure a pool of VXLAN-based networks for each tenant in the cloud management platform;
- select a policy when a network is allocated from a particular tenant's pool of networks and generating information comprising a VXLAN segment identifier and a policy identifier; and
- configure the gateway based on the VXLAN segment identifier and the policy identifier.
18. The apparatus of claim 16, wherein the processor is further configured to:
- create a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configure a pool of VXLAN-based networks for each tenant in the cloud management platform;
- generate information comprising a policy, VXLAN segment identifier and tenant identifier based on the pool of VXLAN-based networks configured;
- allocate a VLAN for a newly instantiated tenant network and creating a VLAN interface on the physical network service equipment;
- configure the policy obtained from the cloud management platform on the VLAN interface in the physical network service equipment within a tenant context based on the tenant identifier; and
- configure a VXLAN/VLAN gateway to connect the VXLAN-based tenant network to the VLAN interface on the physical network service equipment based on the VXLAN segment identifier.
19. The apparatus of claim 16, wherein the processor is further configured to:
- provision the physical network service equipment with the service context for each tenant; and
- configure the physical network service equipment with multiple policies, each policy within a service context for a particular tenant and having a policy identifier, and one VLAN being associated with each policy.
20. The apparatus of claim 19, wherein the processor is further configured to define a policy for each logical network to which virtual machines within a service context connect, and to configure the gateway based on a logical network identifier, tenant identifier and policy information received from the cloud management platform.
21. The method of claim 1, wherein receiving an identifier of a logical network includes receiving an overlay segment identifier;
- wherein the gateway is a logical network to virtual network gateway and configuring includes configuring the gateway to connect traffic for the identified overlay segment of the logical network to a particular VLAN, identified by a VLAN identifier; and
- using the gateway to connect traffic between the logical network and a physical network connected to the physical network service equipment in accord with the policy, wherein the traffic in the logical network is isolated in part using the overlay segment identifier, and the traffic in the physical network is isolated in part using the VLAN identifier.
22. The method of claim 21, wherein the policy is applied to the physical network service equipment, and wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch.
23. The method of claim 22, wherein the policy applied for a first tenant in the plurality of tenants differs from the policy applied for a second tenant in the plurality of tenants.
24. The method of claim 22, wherein a single VLAN is associated with a tenant.
25. The method of claim 22, wherein multiple VLANs are associated with a tenant.
26. The method of claim 22, wherein multiple virtual network segments are associated with a tenant.
27. The method of claim 21, further comprising:
- creating a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configuring at least one overlay-based virtual network for the tenant in the cloud management platform;
- generating the policy as a generated policy to be applied to the physical network service equipment, wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch;
- creating a VLAN interface on the physical network service equipment;
- connecting the VLAN interface to the overlay-based virtual network identified by the overlay segment identifier; and
- configuring the physical network service equipment to act according to the generated policy when connecting traffic between the virtual and the physical network.
28. The method of claim 21, further comprising:
- provisioning the physical network service equipment with the service context for each tenant; and
- configuring the physical network service equipment with multiple policies, each policy within a service context for a particular tenant.
29. The method of claim 28, further comprising, through a cloud management platform, defining a policy for each logical network to which virtual machines within a service context connect.
30. The non-transitory computer readable storage media of claim 8, wherein the instructions that cause the processor to receive an identifier of a logical network include instructions that cause the processor to receive an overlay segment identifier;
- wherein the gateway is a logical network to virtual network gateway and the instructions that cause the processor to configure include instructions that cause the processor to configure the gateway to connect traffic for the identified overlay segment of the logical network to a particular VLAN, identified by a VLAN identifier; and
- wherein the instructions are configured to cause the processor to use the gateway to connect traffic between the logical network and a physical network connected to the physical network service equipment in accord with the policy, wherein the traffic in the logical network is isolated in part using the overlay segment identifier, and the traffic in the physical network is isolated in part using the VLAN identifier.
31. The non-transitory computer readable storage media of claim 30, wherein the policy is applied to the physical network service equipment, and wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch.
32. The non-transitory computer readable storage media of claim 31, wherein the policy applied for a first tenant in the plurality of tenants differs from the policy applied for a second tenant in the plurality of tenants.
33. The non-transitory computer readable storage media of claim 31, wherein a single VLAN is associated with a tenant.
34. The non-transitory computer readable storage media of claim 31, wherein multiple VLANs are associated with a tenant.
35. The non-transitory computer readable storage media of claim 31, wherein multiple virtual network segments are associated with a tenant.
36. The non-transitory computer readable storage media of claim 30, wherein the instructions further cause the processor to:
- create a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configure at least one overlay-based virtual network for the tenant in the cloud management platform;
- generating the policy as a generated policy to be applied to the physical network service equipment, wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch;
- create a VLAN interface on the physical network service equipment;
- connect the VLAN interface to the overlay-based virtual network identified by the overlay segment identifier; and
- configure the physical network service equipment to act according to the generated policy when connecting traffic between the virtual and the physical network.
37. The non-transitory computer readable storage media of claim 30, wherein the instructions further cause the processor to:
- provision the physical network service equipment with the service context for each tenant; and
- configure the physical network service equipment with multiple policies, each policy within a service context for a particular tenant.
38. The non-transitory computer readable storage media of claim 37, wherein the instructions further cause the processor to, through a cloud management platform, define a policy for each logical network to which virtual machines within a service context connect.
39. An apparatus comprising:
- a network interface unit configured to enable network communications; and
- a memory;
- a processor coupled to the network interface unit and the memory, wherein the processor is configured to: process a received identifier of a logical network to which a virtual workload connects and a policy for the logical network, wherein the virtual workload is associated with an overlay technology; and
- configure, based on the identifier of the logical network and the policy, a gateway to connect traffic for the virtual workload on the logical network to a particular virtual local area network (VLAN) interface of physical network service equipment on which the policy is configured, wherein the physical network service equipment is provisioned with a service context for each of a plurality of tenants,
- wherein the gateway is a logical network to virtual network gateway, and the apparatus is configured to:
- receive an overlay segment identifier;
- configure the gateway to connect traffic for the identified overlay segment of the logical network to a particular VLAN, identified by a VLAN identifier; and
- use the gateway to connect traffic between the logical network and a physical network connected to the physical network service equipment in accord with the policy, wherein the traffic in the logical network is isolated in part using the overlay segment identifier, and the traffic in the physical network is isolated in part using the VLAN identifier.
40. The apparatus of claim 39, wherein the policy is applied to the physical network service equipment, and wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch.
41. The apparatus of claim 40, wherein the policy applied for a first tenant in the plurality of tenants differs from the policy applied for a second tenant in the plurality of tenants.
42. The apparatus of claim 40, wherein a single VLAN is associated with a tenant.
43. The apparatus of claim 40, wherein multiple VLANs are associated with a tenant.
44. The apparatus of claim 40, wherein multiple virtual network segments are associated with a tenant.
45. The apparatus of claim 39, wherein the processor is further configured to:
- create a tenant context on the physical network service equipment when a tenant is provisioned in a cloud management platform;
- configure at least one overlay-based virtual network for the tenant in the cloud management platform;
- generate the policy as a generated policy to be applied to the physical network service equipment, wherein the physical network service equipment includes at least one of firewall equipment, load balancer equipment, or a switch;
- create a VLAN interface on the physical network service equipment;
- connect the VLAN interface to the overlay-based virtual network identified by the overlay segment identifier; and
- configure the physical network service equipment to act according to the generated policy when connecting traffic between the virtual and the physical network.
46. The apparatus of claim 39, wherein the processor is further configured to:
- provision the physical network service equipment with the service context for each tenant; and
- configure the physical network service equipment with multiple policies, each policy within a service context for a particular tenant.
47. The apparatus of claim 46, wherein the processor is configured to, through a cloud management platform, define a policy for each logical network to which virtual machines within a service context connect.
6735198 | May 11, 2004 | Edsall et al. |
6807172 | October 19, 2004 | Levenson et al. |
7558960 | July 7, 2009 | Cam Winget et al. |
7987272 | July 26, 2011 | Kumar et al. |
8037180 | October 11, 2011 | Smith et al. |
8274973 | September 25, 2012 | Sardar et al. |
8966035 | February 24, 2015 | Casado |
9049115 | June 2, 2015 | Rajendran et al. |
9069599 | June 30, 2015 | Martinez et al. |
20070258464 | November 8, 2007 | Hall |
20120281708 | November 8, 2012 | Chauhan |
20120317136 | December 13, 2012 | Papish |
20130044629 | February 21, 2013 | Biswas et al. |
20130268643 | October 10, 2013 | Chang |
20130297768 | November 7, 2013 | Singh |
20130332982 | December 12, 2013 | Rao |
20140016501 | January 16, 2014 | Kamath |
20140071983 | March 13, 2014 | Banavalikar |
20140096183 | April 3, 2014 | Jain |
- Joseph et al, A Policy-aware Switching layer for data centers, Technical Report UCB/EECS-2008-82, Jun. 24, 2008.
- Badidi et al., A Cloud-based approach for COntext Informaiton Provisioning ,World of COmputer science and information technology journal (WCSIT) ISSN:2221-0741, vol. 1, No. 3,63-70, 2011.
- Mudigonda, et al., “NetLord: A Scalable Multi-Tenant Network Architecture for Virtualized Datacenters,” SIGCOMM'11, Aug. 15-19, 2011, 12 pages.
- Cohen, et al., “DOVE: Distributed Overlay Virtual nEtwork Architecture,” IBM Research Report, H-0315 (HAI1206-006) Jun. 17, 2011, 15 pages.
Type: Grant
Filed: Jan 17, 2020
Date of Patent: Apr 12, 2022
Assignee: CISCO TECHNOLOGY, INC. (San Jose, CA)
Inventors: Saravankumar Rajendran (San Jose, CA), Ajit Sanzgiri (Los Gatos, CA)
Primary Examiner: John M Hotaling
Application Number: 16/745,558
International Classification: H04L 12/28 (20060101); H04L 12/46 (20060101); H04L 12/24 (20060101); H04L 12/66 (20060101); H04L 12/715 (20130101); H04L 12/931 (20130101); H04L 41/0806 (20220101); H04L 41/0823 (20220101); H04L 41/5041 (20220101); H04L 45/64 (20220101); H04L 49/00 (20220101); H04L 41/0893 (20220101);