# US 2017/0289030 A1 · Multiple provider framework for virtual switch data planes and data plane migration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0289030 A1
- Document ID: US20170289030A1
- Status: Published application
- Kind: A1
- Application number: 15/084,952
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: Futurewei Technologies, Inc.
- Applicants: Futurewei Technologies, Inc.
- Inventors: Yunsong Lu; Yan Chen
- Web page: https://patentgrep.com/patent/US20170289030A1

## CPC

- H04L 45/56: {Routing software}
- H04L 45/02: Topology update or discovery
- H04L 45/586: of virtual routers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The disclosure relates to technology for supporting a virtual switch to change data plane providers on a framework supporting multiple data plane providers. A processing device receives a request to change a first data plane provider, where the virtual switch is configured with a topology on the first data plane provider to use a flow management protocol. The virtual switch includes network interfaces connected to ports to enable communication among entities attached to the network interfaces by forwarding data packets within a first datapath of the first data plane. In response to the change, the network interfaces are disconnected, the first datapath is removed and a second datapath is created. The virtual switch is then configured to operate with the second datapath while retaining the flow management protocol and the topology, such that the entities communicate by forwarding data packets within the second datapath on the second data plane.

## Claims

### Claim 1

A method for supporting multiple data plane providers in a processing device, comprising:
receiving a request to change a first data plane provider, wherein a virtual switch is configured with a topology on a first data plane provider to use a flow management protocol, the virtual switch including one or more first network interfaces respectively connected to one or more ports to enable communication among one or more entities attached to the one or more first network interfaces by forwarding data packets within a first datapath of the first data plane;
disconnecting the one or more first network interfaces;
removing the first datapath of the virtual switch;
creating a second datapath on a second data plane of a second data plane provider using the topology and the flow management protocol;
configuring the virtual switch to operate with the second datapath and retaining the flow management protocol and the topology, the virtual switch including one or more second network interfaces; and
connecting the one or more second network interfaces to a respective one of the one or more ports to enable communication among the one or more entities attached to each of the network interfaces by forwarding data packets within the second datapath on the second data plane.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
constructing the topology of the virtual switch by creating a virtual switch object on a virtual switch framework;
adding the one or more ports to the virtual switch to form the topology; and
creating the first datapath on the first data plane provider using the topology with the first flow management protocol.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
detecting the first data plane provider, the first data plane provider discoverable via a first pluggable software module that identifies the first data plane of the first data plane provider with one or more network interfaces and enables one or more flow management protocols; and
detecting the second data plane provider, the second data plane provider discoverable via a second pluggable software module that identifies the second data plane of the second data plane provider with one or more network interfaces and enables the one or more flow management protocols.

### Claim 4 (depends on 3)

The method of claim 3, wherein the virtual switch is configurable during runtime with the one or more flow management protocols without changing the topology.

### Claim 5 (depends on 1)

The method of claim 1, wherein the entities are at least one of virtual machines, namespaces and containers.

### Claim 6 (depends on 3)

The method of claim 3, further comprising storing the first and second pluggable software modules of the first and second data plane providers in a data store.

### Claim 7 (depends on 3)

The method of claim 3, wherein the detecting comprises discovering the first and second pluggable software modules by monitoring the data store for at least one of newly added plugins for enabling at least one of new data plane providers and changing the first virtual switch to the second virtual switch.

### Claim 8 (depends on 3)

The method of claim 3, wherein the first and second pluggable software modules of the first and second data planes are dynamically loadable during runtime to enable at least one of adding another data plane provider and changing one of the first and second virtual switches without reconfiguring the topology and the flow management protocol.

### Claim 9 (depends on 1)

The method of claim 1, wherein the network interface is one of a virtual network interface and a physical network interface.

### Claim 10 (depends on 1)

The method of claim 1, further comprising configuring the virtual switch with a first network interface of the one or more first network interfaces connected a first port of the one or more ports and a second network interface of the one or more first network interfaces connected to a second port of the one or more ports.

### Claim 11

A non-transitory computer-readable medium storing computer instructions for supporting multiple protocols in a processing device, that when executed by one or more processors, perform the steps of:
receiving a request to change a first data plane provider, wherein a virtual switch is configured with a topology on a first data plane provider to use a flow management protocol, the virtual switch including one or more first network interfaces respectively connected to one or more ports to enable communication among one or more entities attached to the one or more first network interfaces by forwarding data packets within a first datapath of the first data plane;
disconnecting the one or more first network interfaces;
removing the first datapath of the virtual switch;
creating a second datapath on a second data plane of a second data plane provider using the topology and the flow management protocol;
configuring the virtual switch to operate with the second datapath and retaining the flow management protocol and the topology, the virtual switch including one or more second network interfaces; and
connecting the one or more second network interfaces to a respective one of the one or more ports to enable communication among the one or more entities attached to each of the network interfaces by forwarding data packets within the second datapath on the second data plane.

### Claim 12 (depends on 11)

The non-transitory computer-readable medium of claim 11, with the one or more processors further performing the steps of:
constructing the topology of the virtual switch by creating a virtual switch object on a virtual switch framework;
adding the one or more ports to the virtual switch to form the topology; and
creating the first datapath on the first data plane provider using the topology with the first flow management protocol.

### Claim 13 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the one or more processors further performing the steps of:
detecting the first data plane provider, the first data plane provider discoverable via a first pluggable software module that identifies the first data plane of the first data plane provider with one or more network interfaces and enables one or more flow management protocols; and
detecting the second data plane provider, the second data plane provider discoverable via a second pluggable software module that identifies the second data plane of the second data plane provider with one or more network interfaces and enables the one or more flow management protocols.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the virtual switch is configurable during runtime with the one or more flow management protocols without changing the topology.

### Claim 15 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the entities are at least one of virtual machines, namespaces and containers.

### Claim 16 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the one or more processors further performing the steps of storing the first and second pluggable software modules of the first and second data plane providers in a data store.

### Claim 17 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the detecting comprises discovering the first and second pluggable software modules by monitoring the data store for at least one of newly added plugins for enabling at least one of new data plane providers and changing the first virtual switch to the second virtual switch.

### Claim 18 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the first and second pluggable software modules of the first and second data planes are dynamically loadable during runtime to enable at least one of adding another data plane provider and changing one of the first and second virtual switches without reconfiguring the topology and the flow management protocol.

### Claim 19 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the network interface is one of a virtual network interface and a physical network interface.

### Claim 20 (depends on 11)

The non-transitory computer-readable medium of claim 11, further comprising configuring the virtual switch with a first network interface of the one or more first network interfaces connected a first port of the one or more ports and a second network interface of the one or more first network interfaces connected to a second port of the one or more ports.

### Claim 21

A node for supporting multiple protocols in a network, comprising:
a memory storage comprising instructions; and
one or more processors coupled to the memory that execute the instructions to:
receive a request to change a first data plane provider, wherein a virtual switch is configured with a topology on a first data plane provider to use a flow management protocol, the virtual switch including one or more first network interfaces respectively connected to one or more ports to enable communication among one or more entities attached to the one or more first network interfaces by forwarding data packets within a first datapath of the first data plane;
disconnect the one or more first network interfaces;
remove the first datapath of the virtual switch;
create a second datapath on a second data plane of a second data plane provider using the topology and the flow management protocol;
configure the virtual switch to operate with the second datapath and retaining the flow management protocol and the topology, the virtual switch including one or more second network interfaces; and
connect the one or more second network interfaces to a respective one of the one or more ports to enable communication among the one or more entities attached to each of the network interfaces by forwarding data packets within the second datapath on the second data plane.

### Claim 22 (depends on 21)

The node of claim 21, wherein the one or more processors further execute the instructions to:
construct the topology of the virtual switch by creating a virtual switch object on a virtual switch framework;
add the one or more ports to the virtual switch to form the topology; and
create the first datapath on the first data plane provider using the topology with the first flow management protocol.

### Claim 23 (depends on 21)

The node of claim 21, wherein the one or more processors further execute the instructions to:
detect the first data plane provider, the first data plane provider discoverable via a first pluggable software module that identifies the first data plane of the first data plane provider with one or more network interfaces and enables one or more flow management protocols; and
detect the second data plane provider, the second data plane provider discoverable via a second pluggable software module that identifies the second data plane of the second data plane provider with one or more network interfaces and enables the one or more flow management protocols.

### Claim 24 (depends on 21)

The node of claim 21, wherein the virtual switch is configurable during runtime with the one or more flow management protocols without changing the topology.

### Claim 25 (depends on 21)

The node of claim 21, wherein the one or more processors further execute the instructions to configure the virtual switch with a first network interface of the one or more first network interfaces connected a first port of the one or more ports and a second network interface of the one or more first network interfaces connected to a second port of the one or more ports.
