WO2015051548A1

WO2015051548A1 - Virtual network migration method, apparatus and device

Info

Publication number: WO2015051548A1
Application number: PCT/CN2013/085106
Authority: WO
Inventors: 周伟
Original assignee: 华为技术有限公司
Priority date: 2013-10-12
Filing date: 2013-10-12
Publication date: 2015-04-16
Also published as: CN104995600B; CN104995600A

Abstract

Disclosed are a virtual network migration method, apparatus and device. The method comprises: a first virtual network entity sending context information of a virtual network to a second virtual network entity; the first virtual network entity disconnecting connections with controllers and switches according to the context information, and deactivating connection interface settings with the controllers and the switches, so that the second virtual network entity activates, according to the context information, connection interface settings with the controllers and the switches, so as to establish connections with the controllers and the switches. The method, the apparatus and the device can implement migration of a virtual network formed by a virtual network entity.

Description

Virtual network migration method, device and device

Technical field

[01] The present invention relates to the field of communications, and in particular, to a virtual network migration method, apparatus, and device. BACKGROUND [02] As a key node in a network, a switch has a limited interface open under the monopoly of an existing device provider, and many open ideas and protocols in the network cannot be tested and verified. OpenFlow emerged as an open interface and exchange standard that supports multiple controls. OpenFlow transforms traditional physical fixed hardware into a dynamically variable software-defined network (SDN), which separates the control plane from the forwarding plane.

Part [03] OpenFlow switches (Switch) include flow meter (Flow Table) secure channel (Secure Channel) and OpenFlow protocol (OF Protocol) ₀ switch in the flow table stored in the core of the information to implement lookup, forwarding, statistics and Filtering and other functions, through the OpenFlow protocol through a secure channel (Secure Channel) connected to an external controller (Controller), the controller queries and manages the flow table. The flow table contains match field counters (counters) and instruction sets (instructions). Different vendors can design different flow tables according to their needs.

[04] Based on the existing OpenFlow network, virtual network entities such as FlowVisor provide a technology for network virtualization. FlowVisor implements network virtualization between controllers and switches by using network sharding.

[05] See Figure 1, which is a schematic diagram of the network structure of FlowVisor. Among them, from the perspective of the controller, they think that they are connected to the real switch; for the switch, they think that they are connected to the real controller. In fact, whether it is a controller or a switch, the connection is FlowVisor. The FlowVisor functions as a switch and controller between the controller and the switch. It also analyzes the OpenFlow protocol packets and analyzes the flow table. Then, the OpenFlow protocol packets are connected to different controllers and switches.

[06] Through such processing, the same switch can actually be connected to multiple different controllers, that is, multiple controllers can control messages on one switch. At the same time, one control device can also control multiple switches. Due to this implementation of FlowVisor, the underlying transmission data can be processed by the controller through Slicing, which is represented by the function of network virtualization. [07] One of the current technologies for network virtualization is virtual machine migration technology, which means that virtual machines running on one physical machine can be smoothly migrated to another physical machine to maintain the original interconnection protocol (IP) address. , Media Access Control (MAC, Media Access Control) address and other information, and keep the upper layer of business uninterrupted. Since the computer network is composed of multiple virtual machines, the migration between the above virtual computer networks can be achieved by separately migrating each virtual machine. However, when this method is applied to a virtual network composed of Flowvisor, if the migration of each virtual machine is implemented by a single machine migration, the migration of the virtual network composed of Flowvisor cannot be realized. Summary of the invention

The embodiment of the invention provides a virtual network migration method, device and device, which can implement migration of a virtual network composed of virtual network entities.

[09] In a first aspect, a virtual network migration method is provided, including:

[10] The first virtual network entity sends context information of the virtual network to the second virtual network entity;

[11] The first virtual network entity disconnects the connection with each controller and each switch according to the context information, and deactivates the connection interface setting with each controller and each switch, so that the second virtual network entity according to the context The information is activated with the connection interface settings of each controller and each switch, and establishes a connection with each controller and each switch.

[12] In combination with the first aspect, in a first possible implementation manner of the first aspect, after the first virtual network entity sends the context information, the first virtual network entity disconnects from each controller according to the context information. Before the switch is connected, it also includes:

[13] The first virtual network entity sends a switch migration request to each controller that is connected to the controller; the switch migration request includes: an IP address of the second virtual network entity; and the first virtual network entity receives the Switch migration response; and,

[14] The first virtual network entity sends a controller migration request to each switch connected to the controller; the controller migration request includes: an IP address of the second virtual network entity; and the first virtual network entity receives the sending by the switch The controller migrates the response.

[15] In combination with the first aspect, and/or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the first virtual network entity sends the virtual network to the second virtual network entity Before the context information, it also includes:

[16] The first virtual network entity sends a network migration request to the second virtual network entity;

[17] The first virtual network entity receives a network migration response sent by the second virtual network entity; The shift response is sent by the second virtual network entity when determining to accept the network migration request of the first virtual network entity according to the network migration request.

[18] In combination with the first aspect, and/or the first possible implementation of the first aspect, and/or the second possible implementation of the first aspect, in the third possible implementation manner of the first aspect, After the virtual network entity sends the context information of the virtual network to the second virtual network entity, before disconnecting the connection with each controller and switch, the method further includes:

[19] when the first virtual network entity determines that the context information is transmitted, sending a migration completion request to the second virtual network entity;

[20] The first virtual network entity receives the migration completion response sent by the second virtual network entity.

[21] The second aspect provides a virtual network migration method, including:

[22] the second virtual network entity receives the context information of the virtual network sent by the first virtual network entity;

[23] The second virtual network entity activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch.

[24] In combination with the second aspect, in a first possible implementation manner of the second aspect, before the second virtual network entity receives the context information, the method further includes:

[25] the second virtual network entity receives the network migration request sent by the first virtual network entity;

[26] When the second virtual network entity determines to accept the request of the first virtual network entity according to the network migration request, the second virtual network entity sends a network migration response to the first virtual network entity.

[27] With reference to the second aspect, and/or the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, after the second virtual network entity receives the context information, Before establishing a connection with each switch, it also includes:

[28] the second virtual network entity receives a migration completion request sent by the first virtual network entity when determining that the context information is transmitted;

[29] The second virtual network entity sends a migration completion response to the first virtual network entity.

[30] In a third aspect, a virtual network migration apparatus is provided, including:

[31] a first sending unit, configured to send context information of the virtual network to the second virtual network entity;

[32] a first connecting unit, configured to disconnect the connection between each controller and each switch according to the context information sent by the first sending unit;

[33] a first processing unit, configured to deactivate a connection interface setting with each controller and each switch, so that the second virtual network entity activates a connection interface setting with each controller and each switch according to the context information, and each The controller establishes a connection with each switch. [34] In combination with the third aspect, in a first possible implementation manner of the third aspect, the first sending unit is further configured to: send a switch migration request to each controller that is connected to the device; And including: an IP address of the second virtual network entity; sending a controller migration request to each switch connected to the device; the controller migration request includes: an IP address of the second virtual network entity;

[35] The device further includes: a first receiving unit, configured to receive a switch migration response sent by the controller; and, receive a switch migration response sent by the controller.

[36] In combination with the third aspect, and/or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the first sending unit is further configured to: send to the second virtual network entity Network migration request;

The first receiving unit is further configured to: receive a network migration response sent by the second virtual network entity, where the network migration response is determined by the second virtual network entity to accept the network migration of the first virtual network entity according to the network migration request. Sent when requested.

[38] In combination with the third aspect, and/or the first possible implementation manner of the third aspect, and/or the second possible implementation manner of the third aspect, in the third possible implementation manner of the third aspect, a sending unit is further configured to: when determining that the context information is transmitted, send a migration completion request to the second virtual network entity;

[39] The first receiving unit is further configured to: receive a migration completion response sent by the second virtual network entity.

[40] In a fourth aspect, a virtual network migration apparatus is provided, including:

[41] a second receiving unit, configured to receive context information of the virtual network sent by the first virtual network entity;

[42] a second processing unit, configured to activate a connection interface setting with each controller and each switch according to the context information received by the second receiving unit;

[43] The second connection unit is configured to establish a connection with each controller and each switch according to the context information received by the second receiving unit.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the second receiving unit is further configured to: receive a network migration request that is sent by the first virtual network entity;

[45] The device further includes: a second sending unit, configured to send a network migration response to the first virtual network entity when determining, by the network migration request, the request to accept the first virtual network entity.

[46] In combination with the fourth aspect, and/or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the second receiving unit is further configured to: receive the first virtual network entity Determining a migration completion request sent when the context information is transmitted;

[47] The second sending unit is further configured to: send a migration completion response to the first virtual network entity.

[48] The fifth aspect provides a first virtual network entity, including: a processor and a transceiver; [49] a transceiver, configured to send context information of the virtual network to the second virtual network entity; disconnect the connection with each controller and each switch according to the context information;

[50] The processor is used to deactivate the connection interface settings with each controller and each switch.

[51] In combination with the fifth aspect, in a first possible implementation manner of the fifth aspect, the transceiver is further configured to:

After the context information is sent, the switch migration request is sent to each controller connected to the controller, and the switch migration request includes: The IP address of the virtual network entity; receiving the switch migration response sent by the controller; and sending a controller migration request to each switch connected to the controller; the controller migration request includes: an IP address of the second virtual network entity Receiving a controller migration response sent by the switch.

[53] In combination with the fifth aspect, and/or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the transceiver is further configured to: send to the second virtual network entity Before the context information of the virtual network, sending a network migration request to the second virtual network entity; receiving a network migration response sent by the second virtual network entity; the network migration response is determined by the second virtual network entity according to the network migration request Sent when a virtual network entity's network migration request is made.

[54] In combination with the fifth aspect, and/or the first possible implementation manner of the fifth aspect, and/or the second possible implementation manner of the fifth aspect, in the third possible implementation manner of the fifth aspect, The transceiver is further configured to: after sending the context information of the virtual network to the second virtual network entity, before disconnecting the connection with each controller and the switch, determining that the context information is transmitted, sending the migration to the second virtual network entity Completing the request; receiving a migration completion response sent by the second virtual network entity.

[55] The sixth aspect provides a second virtual network entity, including a transceiver and a processor, where

[56] a transceiver, configured to receive context information of a virtual network sent by the first virtual network entity; establish a connection with each controller and each switch;

[57] The processor is used to activate the connection interface settings with each controller and each switch.

[58] In combination with the sixth aspect, in a first possible implementation manner of the sixth aspect, the transceiver is further configured to: before receiving the context information, receive a network migration request sent by the first virtual network entity; When the network migration request determines that the request of the first virtual network entity is accepted, the network migration response is sent to the first virtual network entity.

[59] In combination with the sixth aspect, and/or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the transceiver is further configured to: after receiving the context information, Before receiving the connection with each controller and each switch, receiving the first virtual network entity determines that the context information is transmitted a migration completion request sent over time; sending a migration completion response to the first virtual network entity.

In the embodiment of the present invention, the first virtual network entity sends the context information of the virtual network to the second virtual network entity; the first virtual network entity disconnects the connection with each controller and each switch according to the context information, Deactivating a connection interface setting with each controller and each switch, so that the second virtual network entity activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch, thereby realizing The migration of virtual networks. DRAWINGS

[61] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and other drawings may be obtained from those skilled in the art without departing from the drawings.

[62] FIG. 1 is a schematic diagram of a network structure of a prior art Flow Visor;

2 is a schematic diagram of a first embodiment of a virtual network migration method according to the present invention;

FIG. 3 is a schematic diagram of a second embodiment of a virtual network migration method according to the present invention; FIG.

4 is a schematic diagram of a third embodiment of a virtual network migration method according to the present invention;

FIG. 5 is a schematic diagram of a fourth embodiment of a virtual network migration method according to the present invention; FIG.

6 is a schematic diagram of a first embodiment of a virtual network migration apparatus according to the present invention;

7 is a schematic diagram of a second embodiment of a virtual network migration apparatus according to the present invention;

8 is a schematic diagram of a first virtual network entity according to the present invention;

9 is a schematic diagram of a second virtual network entity according to the present invention. detailed description

The above described objects, features, and advantages of the embodiments of the present invention will become more apparent and understood. The technical solution is described in further detail.

[72] FIG. 2 is a schematic diagram of a first embodiment of a virtual network migration method according to the present invention, where the method includes:

[73] Step 201: The first virtual network entity sends context information of the virtual network to the second virtual network entity.

[74] Step 202: The first virtual network entity disconnects from each controller and each according to the context information. The connection of the switches, deactivating the connection interface settings with the respective controllers and the respective switches, so that the second virtual network entity activates the connection interface setting with each controller and each switch according to the context information, and each controller and each switch establish connection.

[75] In this embodiment, the first virtual network entity sends the context information of the virtual network to the second virtual network entity; the first virtual network entity disconnects the connection with each controller and each switch according to the context information, Activating connection interface settings with each controller and each switch, so that the second virtual network entity activates connection interface settings with each controller and each switch according to the context information, and establishes a connection with each controller and each switch, thereby realizing Virtual network connection;

[76] Moreover, the first virtual network entity disconnects from each controller and each switch, and the second virtual network entity establishes a connection with each controller and each switch, thereby ensuring continuity of the virtual network service.

[77] FIG. 3 is a schematic diagram of a second embodiment of a virtual network migration method according to the present invention, where the method includes:

[78] Step 301: The second virtual network entity receives the context information of the virtual network sent by the first virtual network entity.

[79] Step 302: The second virtual network entity activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch.

[80] In this embodiment, the second virtual network entity receives the context information, activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch, thereby implementing Migration of virtual networks.

[81] FIG. 4 is a schematic diagram of a third embodiment of a virtual network migration method according to the present invention, where the method includes:

[82] Step 401: The first virtual network entity sends a network migration request to the second virtual network entity.

[83] The network migration request may be implemented by using a normal Transmission Control Protocol (TCP) or a Stream Control Transmission Protocol (SCTP) request message, or may be customized through a virtual network entity. achieve.

[84] The network migration request may include: information about IP address information, network specification size, and migration reason of the first virtual network entity, where the related information may be provided to the second virtual network entity, so that the second virtual network The entity decides whether to accept the virtual network migration to the first virtual network entity.

[85] Step 402: The second virtual network entity sends a network migration response to the first virtual network entity when determining to accept the migration of the virtual network according to the network migration request.

[86] wherein the network migration response can be implemented by using a normal TCP or SCTP request message, It can be implemented through messages customized between virtual network entities.

[87] The network migration response is used to notify the first virtual network entity that the second virtual network entity accepts migration of the virtual network.

[88] Step 403: The first virtual network entity sends context information of the virtual network to the second virtual network entity.

[89] The context information includes: controller information connected to the virtual network, switch information connected to the virtual network, flow fragmentation information, control information of the first virtual network entity, and the like, and the first virtual network entity and the Interface information of each controller and each switch.

[90] Step 404: The first virtual network entity determines to send a migration completion request to the second virtual network entity when the context information is transmitted.

[91] The migration completion request may be implemented by using a normal TCP or SCTP request message, or may be implemented by a customized message between virtual network entities.

[92] When the second virtual network entity receives the migration completion request, indicating that the second virtual network entity has completed receiving the context information.

[93] Step 405: The second virtual network entity sends a migration completion response to the first virtual network entity.

[94] The migration completion response may be implemented by a normal TCP or SCTP request message, or may be implemented by a customized message between virtual network entities.

[95] The migration completion response is for notifying the first virtual network entity that the second virtual network entity has received the context information and the migration completion request.

[96] Step 406: The first virtual network entity disconnects the connection with each controller and each switch according to the context information, deactivates the connection interface setting with each controller and each switch; and, the second virtual network entity A connection interface setting with each controller and each switch is activated according to the context information, and a connection is established with each controller and each switch.

[97] In step 404, all virtual network context information migration has been completed, that is, the migration of the virtual network is completed; in step 405, the first virtual network entity is disconnected from each controller and each switch. Connecting, deactivating interface settings connected to each controller and each switch, and the second virtual network entity activates interface settings with each controller and each switch, establishes a connection with each controller and each switch, and is thereby connected by the second virtual The network entity maintains the context information of the original virtual network, thereby completing the migration of the entire virtual network. Since the second virtual network entity completely replicates the context information of the virtual network maintained by the first virtual network entity, communication between the subsequent controller and the switch and the second virtual network entity where the virtual network is located will continue to be maintained. [98] This embodiment is particularly applicable to the following scenario: when the entire network device is initialized, a connection is established between the first virtual network entity and the controller and the switch, and a virtual network is constructed; and after the second virtual network entity is started, Waiting for the migration request of the first virtual network entity to complete the migration process of the virtual network. [99] FIG. 5 is a schematic diagram of a fourth embodiment of a virtual network migration method according to the present invention, where the method includes:

[100] Step 501 505 is the same as step 401 405, and will not be described here.

[101] Step 506: The first virtual network entity sends a switch migration request to each controller that is connected to the controller. The switch migration request includes: an IP address of the second virtual network entity;

[102] The switch migration request is used to notify the controller that the switch connected to the controller needs to be migrated to the device corresponding to the IP address carried by the request.

[103] Step 507: The first virtual network entity receives a switch migration response sent by the controller.

The switch migration response is used to inform the first virtual network entity that the controller has accepted the migration request of the switch.

[105] Step 508: The first virtual network entity sends a controller migration request to each switch that is connected to the switch; the controller migration request includes: an IP address of the second virtual network entity;

[106] The controller migration request is used to notify the switch that the controller connected to the switch needs to be migrated to the device corresponding to the IP address carried by the request.

[107] Step 509: The first virtual network entity receives a controller migration response sent by the switch.

The controller migration response is for communicating to the first virtual network entity that the switch has accepted the migration request of the controller.

[109] wherein, the order of execution between steps 506 507 and 508 509 is not limited.

[110] The controller migration request, the controller migration response, the switch migration request, and the switch migration response may all be implemented by using a normal TCP or SCTP request message, or may be implemented by a customized message between the virtual network entities.

[111] Step 510 is the same as step 406, and is not described here.

[112] wherein the step of the second virtual network entity activating the connection interface setting with each controller and each switch may be performed at any time between steps 504 510, which is not limited herein.

The embodiments of the present invention are particularly applicable to the following scenarios: When the entire network device is initialized, the two virtual network entities are peer-to-peer virtual network entities. Specifically, the first virtual network entity establishes a connection with the controller and the switch to construct a virtual network; and, the second virtual network entity also establishes a connection with the controller and the switch, and constructs a virtual network, as shown in FIG. Not shown in the embodiment of the invention A controller and switch connected to a second virtual network entity.

[114] In this embodiment, the migration of all the virtual network context information is completed through the foregoing steps, that is, the migration of the virtual network is completed; and then, the first virtual network entity disconnects the connection with each controller and each switch. Deactivating interface settings connected to each controller and each switch, and the second virtual network entity activates interface settings with each controller and each switch, establishes a connection with each controller and each switch, and is thereby connected by the second virtual network The entity maintains the context information of the original virtual network, thereby completing the migration of the entire virtual network. Since the second virtual network entity migrates or integrates the virtual network maintained by the first virtual network entity as needed to the virtual network maintained by the second virtual network entity, the controller and the switch that previously connected to the first virtual network entity are subsequently followed by the second The virtual network entity remains in communication.

FIG. 6 is a schematic diagram of a first embodiment of a virtual network migration apparatus according to the present invention. The apparatus 600 includes:

[116] The first sending unit 610 is configured to send context information of the virtual network to the second virtual network entity.

The first connecting unit 620 is configured to disconnect the connection between each controller and each switch according to the context information sent by the first sending unit 610.

The first processing unit 630 is configured to: according to the context information sent by the first sending unit 610, deactivate a connection interface setting with each controller and each switch, so that the second virtual network entity is activated according to the context information. The connection interface with each controller and each switch is set up to establish a connection with each controller and each switch.

The first sending unit 610 is further configured to: send a switch migration request to each controller that is connected to the device; the switch migration request includes: an IP address of the second virtual network entity; Each switch connected to the device sends a controller migration request; the controller migration request includes: an IP address of the second virtual network entity;

The device 600 may further include: a first receiving unit, configured to receive a switch migration response sent by the controller; and receive a switch migration response sent by the controller.

The first sending unit 610 is further configured to: send a network migration request to the second virtual network entity;

The first receiving unit may be further configured to: receive a network migration response sent by the second virtual network entity, where the network migration response is determined by the second virtual network entity to receive the network of the first virtual network entity according to the network migration request. Sent when a migration request.

[123] The first sending unit 610 is further configured to: when determining that the context information is transmitted, The second virtual network entity sends a migration completion request;

The first receiving unit is further configured to: receive a migration completion response sent by the second virtual network entity.

[125] In this embodiment, the context information of the virtual network is sent to the second virtual network entity; according to the context information, the connection with each controller and each switch is disconnected, and the connection with each controller and each switch is activated. The interface is configured, so that the second virtual network entity activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch, thereby implementing a connection of the virtual network;

[126] Moreover, the first virtual network entity disconnects the connection with each controller and each switch, and the connection of the second virtual network entity with each controller and each switch ensures continuity of the virtual network service.

FIG. 7 is a schematic diagram of a second embodiment of a virtual network migration apparatus according to the present invention. The apparatus 700 includes:

[128] The second receiving unit 710 is configured to receive context information of the virtual network sent by the first virtual network entity.

[129] The second processing unit 720 is configured to activate, according to the context information received by the second receiving unit 710, a connection interface setting with each controller and each switch;

The second connecting unit 730 is configured to establish a connection with each controller and each switch according to the context information received by the second receiving unit 710.

The second receiving unit 710 is further configured to: receive a network migration request sent by the first virtual network entity;

[132] The method further includes: a second sending unit, configured to send a network migration response to the first virtual network entity when determining, by the network migration request, the request to accept the first virtual network entity.

[133] The second receiving unit 710 is further configured to: receive, by the first virtual network entity, a migration completion request sent to the second virtual network entity when determining that the context information is transmitted;

The second sending unit is further configured to: send a migration completion response to the first virtual network entity.

In this embodiment, the context information is received, and the connection interface setting with each controller and each switch is activated according to the context information, and a connection is established with each controller and each switch, thereby realizing migration of the virtual network. FIG. 8 is a schematic structural diagram of a first virtual network entity according to an embodiment of the present invention. The first virtual network entity 800 includes: a processor 810, a memory 820, a transceiver 830, and a bus 840. The processor 810, the memory 820, and the transceiver 830 are connected to each other through a bus 840; the bus 840 may be an ISA bus, a PCI bus, or an EISA bus. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.

[138] Memory 820, used to store the program. In particular, the program can include program code, the program code including computer operating instructions. Memory 820 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

[139] The transceiver 830 is used to connect to other devices and to communicate with other devices. The transceiver 830 is configured to: send context information of the virtual network to the second virtual network entity; disconnect the connection with each controller and each switch according to the context information.

The processor 810 executes the program code for deactivating connection interface settings with respective controllers and respective switches.

The transceiver 830 is further configured to: after sending the context information, send a switch migration request to each controller connected to the controller, before disconnecting the connection with each controller and the switch according to the context information; The switch migration request includes: an IP address of the second virtual network entity; receiving a switch migration response sent by the controller; and sending a controller migration request to each switch connected to the controller; the controller migration request includes : an IP address of the second virtual network entity; receiving a controller migration response sent by the switch.

[142] The transceiver 830 is further configured to: send a network migration request to the second virtual network entity before sending the context information of the virtual network to the second virtual network entity; receive the network migration sent by the second virtual network entity The network migration response is sent by the second virtual network entity when determining, according to the network migration request, that the network migration request of the first virtual network entity is accepted.

[143] The transceiver 830 may be further configured to: after sending the context information of the virtual network to the second virtual network entity, before disconnecting the connection with each controller and the switch, determining that the context information is transmitted, Sending a migration completion request to the second virtual network entity; receiving a migration completion response sent by the second virtual network entity.

[144] In this embodiment, the first virtual network entity sends the context information of the virtual network to the second virtual network entity; the first virtual network entity disconnects the connection with each controller and each switch according to the context information, Activating a connection interface setting with each controller and each switch, so that the second virtual network entity activates the connection interface setting with each controller and each switch according to the context information, and connects with each controller and each switch, thereby realizing Virtual network connection; [145] Moreover, the first virtual network entity disconnects the connection with each controller and each switch, and the connection of the second virtual network entity with each controller and each switch ensures continuity of the virtual network service.

FIG. 9 is a schematic structural diagram of a first virtual network entity according to an embodiment of the present invention. The first virtual network entity 900 includes: a processor 910, a memory 920, a transceiver 930, and a bus 940.

The processor 910, the memory 920, and the transceiver 930 are connected to each other through a bus 940; the bus 940 can be an ISA bus, a PCI bus, or an EISA bus. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.

[148] Memory 920, used to store programs. In particular, the program can include program code, the program code including computer operating instructions. Memory 920 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

[149] The transceiver 930 is used to connect to other devices and to communicate with other devices. The transceiver 930 is configured to: receive context information of the virtual network sent by the first virtual network entity; establish a connection with each controller and each switch.

The processor 910 executes the program code for activating connection interface settings with respective controllers and respective switches.

The transceiver 930 may be further configured to: before receiving the context information, receive a network migration request sent by the first virtual network entity; and determine, according to the network migration request, a request to accept the first virtual network entity. Send a network migration response to the first virtual network entity.

The transceiver 930 is further configured to: after receiving the context information, before receiving the connection with each controller and each switch, receiving a migration that is sent by the first virtual network entity when determining that the context information is transmitted. Completing the request; sending a migration completion response to the first virtual network entity.

In this embodiment, the second virtual network entity receives the context information, activates a connection interface setting with each controller and each switch according to the context information, and establishes a connection with each controller and each switch, thereby implementing Migration of virtual networks.

It will be apparent to those skilled in the art that the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, and the computer software product may be stored in a storage medium such as a ROM/RAM. , disk, CD, etc., including a number of instructions to make a computer device (can be a personal computer, server, or network device, etc.) The methods described in various embodiments of the invention or in certain portions of the embodiments are performed.

The various embodiments in the present specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The above described embodiments of the invention are not intended to limit the scope of the invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Rights request

1. A virtual network migration method, characterized by including:

The first virtual network entity sends the context information of the virtual network to the second virtual network entity; the first virtual network entity disconnects from each controller and each switch according to the context information, and deactivates the connection with each controller and each switch. The connection interface settings are configured so that the second virtual network entity activates the connection interface settings with each controller and each switch according to the context information, and establishes a connection with each controller and each switch.

2. The method according to claim 1, characterized in that after the first virtual network entity sends the context information and before the first virtual network entity disconnects from each controller and switch according to the context information, include:

The first virtual network entity sends a switch migration request to each controller to which it is connected; the switch migration request includes: the IP address of the second virtual network entity; the first virtual network entity receives the switch migration response sent by the controller ; and,

The first virtual network entity sends a controller migration request to each switch to which it is connected; the controller migration request includes: the IP address of the second virtual network entity; the first virtual network entity receives the controller migration request sent by the switch. response.

3. The method according to claim 1 or 2, characterized in that before the first virtual network entity sends the context information of the virtual network to the second virtual network entity, it further includes:

The first virtual network entity sends a network migration request to the second virtual network entity;

The first virtual network entity receives the network migration response sent by the second virtual network entity; the network migration response is sent when the second virtual network entity determines to accept the network migration request of the first virtual network entity according to the network migration request.

4. The method according to any one of claims 1 to 3, characterized in that after the first virtual network entity sends the context information of the virtual network to the second virtual network entity, before disconnecting the connection with each controller and switch , Also includes:

When the first virtual network entity determines that the context information transmission is completed, it sends a migration completion request to the second virtual network entity;

The first virtual network entity receives the migration completion response sent by the second virtual network entity.

5. A virtual network migration method, characterized by including:

The second virtual network entity receives the context information of the virtual network sent by the first virtual network entity; The second virtual network entity activates connection interface settings with each controller and each switch according to the context information, and establishes a connection with each controller and each switch.

6. The method according to claim 5, characterized in that before the second virtual network entity receives the context information, it further includes:

The second virtual network entity receives the network migration request sent by the first virtual network entity;

When the second virtual network entity determines to accept the request of the first virtual network entity based on the network migration request, the second virtual network entity sends a network migration response to the first virtual network entity.

7. The method according to claim 5 or 6, characterized in that, after the second virtual network entity receives the context information and before establishing a connection with each controller and each switch, it further includes: the second virtual network entity receives the third A migration completion request sent by a virtual network entity when it determines that the transmission of the context information is completed;

The second virtual network entity sends a migration completion response to the first virtual network entity.

8. A virtual network migration device, characterized by including:

The first sending unit is used to send the context information of the virtual network to the second virtual network entity; the first connection unit is used to disconnect from each controller and each switch according to the context information sent by the first sending unit. ;

The first processing unit is used to deactivate the connection interface settings with each controller and each switch, so that the second virtual network entity activates the connection interface settings with each controller and each switch according to the context information, and communicates with each controller and each switch. Each switch establishes a connection.

9. The device according to claim 8, wherein the first sending unit is further configured to: send a switch migration request to each controller connected to the device; the switch migration request includes: a second virtual network The IP address of the entity; sending a controller migration request to each switch connected to the device; the controller migration request includes: the IP address of the second virtual network entity;

The device further includes: a first receiving unit configured to receive a switch migration response sent by the controller; and, receive a switch migration response sent by the controller.

10. The device according to claim 8 or 9, characterized in that the first sending unit is further configured to: send a network migration request to the second virtual network entity;

The first receiving unit is also configured to: receive a network migration response sent by the second virtual network entity; the network migration response is sent when the second virtual network entity determines to accept the network migration request of the first virtual network entity according to the network migration request. .

11. The device according to any one of claims 8 to 10, characterized in that, the first sending unit Also used for: sending a migration completion request to the second virtual network entity when it is determined that the transmission of the context information is completed;

The first receiving unit is also configured to: receive a migration completion response sent by the second virtual network entity.

12. A virtual network migration device, characterized by including:

The second receiving unit is configured to receive the context information of the virtual network sent by the first virtual network entity; the second processing unit is configured to activate the connection interface with each controller and each switch according to the context information received by the second receiving unit. set up;

The second connection unit is configured to establish connections with each controller and each switch according to the context information received by the second receiving unit.

13. The device according to claim 12, wherein the second receiving unit is further configured to: receive a network migration request sent by the first virtual network entity;

The device further includes: a second sending unit configured to send a network migration response to the first virtual network entity when it is determined to accept the request of the first virtual network entity according to the network migration request.

14. The device according to claim 12 or 13, characterized in that the second receiving unit is further configured to: receive a migration completion request sent by the first virtual network entity when it determines that the context information transmission is completed; the second sending unit Also used for: sending a migration completion response to the first virtual network entity.

15. A first virtual network entity, characterized in that it includes: a processor and a transceiver; wherein the transceiver is used to send the context information of the virtual network to the second virtual network entity; according to the context information, disconnect Connections to individual controllers and individual switches;

Processor for deactivating connection interface settings with individual controllers and individual switches.

16. The first virtual network entity according to claim 15, characterized in that the transceiver is also used for:

After sending the context information, and before disconnecting from each controller and switch according to the context information, send a switch migration request to each controller to which it is connected; the switch migration request includes: the second virtual network entity The IP address of Controller migration response sent by the switch described above.

17. The first virtual network entity according to claim 15 or 16, wherein the transceiver is further configured to: before sending the context information of the virtual network to the second virtual network entity, The network entity sends a network migration request; receives a network migration response sent by the second virtual network entity; the network migration response is sent when the second virtual network entity determines to accept the network migration request of the first virtual network entity according to the network migration request.

18. The first virtual network entity according to any one of claims 15 to 17, characterized in that the transceiver is further configured to: after sending the context information of the virtual network to the second virtual network entity, disconnect from each Before the connection between the controller and the switch, when it is determined that the transmission of the context information is completed, send a migration completion request to the second virtual network entity; and receive the migration completion response sent by the second virtual network entity.

19. A second virtual network entity, characterized in that it includes a transceiver and a processor, wherein the transceiver is used to receive the context information of the virtual network sent by the first virtual network entity; establish with each controller and each switch connect;

Processor for activating connection interface settings with individual controllers and individual switches.

20. The second virtual network entity according to claim 19, wherein the transceiver is further configured to: before receiving the context information, receive a network migration request sent by the first virtual network entity; according to the network When the migration request determines that the request of the first virtual network entity is accepted, a network migration response is sent to the first virtual network entity.

21. The second virtual network entity according to claim 19 or 20, characterized in that the transceiver is further configured to: after receiving the context information, before connecting with each controller and each switch, receive the first virtual network entity A migration completion request sent by the network entity when it determines that the transmission of the context information is completed; sending a migration completion response to the first virtual network entity.