WO2015051548A1 - Procédé, appareil et dispositif de migration de réseau virtuel - Google Patents

Procédé, appareil et dispositif de migration de réseau virtuel Download PDF

Info

Publication number
WO2015051548A1
WO2015051548A1 PCT/CN2013/085106 CN2013085106W WO2015051548A1 WO 2015051548 A1 WO2015051548 A1 WO 2015051548A1 CN 2013085106 W CN2013085106 W CN 2013085106W WO 2015051548 A1 WO2015051548 A1 WO 2015051548A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual network
network entity
migration
controller
switch
Prior art date
Application number
PCT/CN2013/085106
Other languages
English (en)
Chinese (zh)
Inventor
周伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2013/085106 priority Critical patent/WO2015051548A1/fr
Priority to CN201380003680.6A priority patent/CN104995600B/zh
Publication of WO2015051548A1 publication Critical patent/WO2015051548A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • 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.
  • SDN software-defined network
  • OpenFlow switches include flow meter (Flow Table) secure channel (Secure Channel) and OpenFlow protocol (OF Protocol) 0 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.
  • FlowVisor 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.
  • FIG. 1 is a schematic diagram of the network structure of 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.
  • the same switch can actually be connected to multiple different controllers, that is, multiple controllers can control messages on one switch.
  • one control device can also control multiple switches.
  • the underlying transmission data can be processed by the controller through Slicing, which is represented by the function of network virtualization.
  • 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.
  • a virtual network migration method including:
  • the first virtual network entity sends 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, 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.
  • the first virtual network entity disconnects from each controller according to the context information. Before the switch is connected, it also includes:
  • 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,
  • 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.
  • the first virtual network entity sends the virtual network to the second virtual network entity Before the context information, it also includes:
  • the first virtual network entity sends a network migration request to the second virtual network entity
  • 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.
  • the method further includes:
  • the first virtual network entity receives the migration completion response sent by the second virtual network entity.
  • the second aspect provides a virtual network migration method, 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 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.
  • the method further includes:
  • the second virtual network entity receives the network migration request sent by the first virtual network entity
  • 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.
  • the second virtual network entity receives the context information, Before establishing a connection with each switch, it also includes:
  • 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;
  • the second virtual network entity sends a migration completion response to the first virtual network entity.
  • a virtual network migration apparatus including:
  • a first sending unit configured to send context information of the virtual network to the second virtual network entity
  • 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
  • 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.
  • 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;
  • 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.
  • 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.
  • 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;
  • the first receiving unit is further configured to: receive a migration completion response sent by the second virtual network entity.
  • a virtual network migration apparatus including:
  • a second receiving unit configured to receive context information of the virtual network sent by the first virtual network entity
  • 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
  • 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.
  • the second receiving unit is further configured to: receive a network migration request that is 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 determining, by the network migration request, the request to accept the first virtual network entity.
  • 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.
  • 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;
  • the second sending unit is further configured to: send a migration completion response to the first virtual network entity.
  • 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;
  • the processor is used to deactivate the connection interface settings with each controller and each switch.
  • the transceiver is further configured to:
  • 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.
  • 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.
  • 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.
  • the sixth aspect provides a second virtual network entity, including a transceiver and a processor, where
  • 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;
  • the processor is used to activate the connection interface settings with each controller and each switch.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of a network structure of a prior art Flow Visor
  • FIG. 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.
  • FIG. 7 is a schematic diagram of a second embodiment of a virtual network migration apparatus according to the present invention.
  • FIG. 8 is a schematic diagram of a first virtual network entity according to the present invention.
  • FIG. 9 is a schematic diagram of a second virtual network entity according to the present invention. detailed description
  • 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:
  • Step 201 The first virtual network entity sends context information of the virtual network to the second virtual network entity.
  • Step 202 The first virtual network entity disconnects from each controller and each according to the context information.
  • 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;
  • 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.
  • 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:
  • Step 301 The second virtual network entity receives the context information of the virtual network sent by the first virtual network entity.
  • 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.
  • 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.
  • 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:
  • Step 401 The first virtual network entity sends a network migration request to the second virtual network entity.
  • 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.
  • TCP Transmission Control Protocol
  • SCTP Stream Control Transmission Protocol
  • 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.
  • 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.
  • 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.
  • 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.
  • Step 403 The first virtual network entity sends context information of the virtual network to the second virtual network entity.
  • 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.
  • 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.
  • 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.
  • Step 405 The second virtual network entity sends a migration completion response to the first virtual network entity.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • Step 501 505 is the same as step 401 405, and will not be described here.
  • 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;
  • 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.
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • Step 510 is the same as step 406, and is not described here.
  • 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:
  • the two virtual network entities are peer-to-peer virtual network entities.
  • 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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;
  • 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:
  • the second receiving unit 710 is configured to receive context information of the virtual network sent by the first virtual network entity.
  • 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;
  • 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.
  • 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.
  • 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.
  • Memory 820 used to store the program.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Memory 920 used to store programs.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé, un appareil et un dispositif de migration de réseau virtuel. Le procédé consiste : en ce qu'une première entité de réseau virtuel envoie des informations de contexte d'un réseau virtuel à une seconde entité de réseau virtuel ; en ce que la première entité de réseau virtuel déconnecte les connexions avec des contrôleurs et des commutateurs en fonction des informations de contexte et désactive les réglages d'interface de connexion avec les contrôleurs et les commutateurs, de sorte que la seconde entité de réseau virtuel active, en fonction des informations de contexte, des réglages d'interface de connexion avec les contrôleurs et les commutateurs, afin d'établir des connexions avec les contrôleurs et les commutateurs. Le procédé, l'appareil et le dispositif permettent de mettre en œuvre la migration d'un réseau virtuel formé par une entité de réseau virtuel.
PCT/CN2013/085106 2013-10-12 2013-10-12 Procédé, appareil et dispositif de migration de réseau virtuel WO2015051548A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2013/085106 WO2015051548A1 (fr) 2013-10-12 2013-10-12 Procédé, appareil et dispositif de migration de réseau virtuel
CN201380003680.6A CN104995600B (zh) 2013-10-12 2013-10-12 虚拟网络迁移方法、装置及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/085106 WO2015051548A1 (fr) 2013-10-12 2013-10-12 Procédé, appareil et dispositif de migration de réseau virtuel

Publications (1)

Publication Number Publication Date
WO2015051548A1 true WO2015051548A1 (fr) 2015-04-16

Family

ID=52812467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/085106 WO2015051548A1 (fr) 2013-10-12 2013-10-12 Procédé, appareil et dispositif de migration de réseau virtuel

Country Status (2)

Country Link
CN (1) CN104995600B (fr)
WO (1) WO2015051548A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100306381A1 (en) * 2009-05-31 2010-12-02 Uri Lublin Mechanism for migration of client-side virtual machine system resources
CN102118458A (zh) * 2011-03-10 2011-07-06 浪潮(北京)电子信息产业有限公司 一种虚拟机热迁移的方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100306381A1 (en) * 2009-05-31 2010-12-02 Uri Lublin Mechanism for migration of client-side virtual machine system resources
CN102118458A (zh) * 2011-03-10 2011-07-06 浪潮(北京)电子信息产业有限公司 一种虚拟机热迁移的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
XU, YIFEI: "The Dynamic Migration of Openflow Network in the Virtual Network Fragmentation", NETWORK SECURITY TECHNOLOGY & APPLICATION, September 2013 (2013-09-01), pages 53 *

Also Published As

Publication number Publication date
CN104995600B (zh) 2018-01-16
CN104995600A (zh) 2015-10-21

Similar Documents

Publication Publication Date Title
US9755967B2 (en) Method, apparatus, and system for configuring flow table in OpenFlow network
CN105072482B (zh) 一种多媒体播放设备的播放控制方法及装置
EP2843906B1 (fr) Procédé, appareil et système de transmission de données
WO2015143610A1 (fr) Procédé de mise en œuvre de service pour un système nfv, et unité de communication
WO2017162089A1 (fr) Procédé et dispositif de configuration de service pour service de réseau
CN109642923B (zh) 分流网络数据以执行负载平衡
WO2012106892A1 (fr) Procédé, appareil et système de traitement de flux de service
EP2696542A1 (fr) Procédé, commutateur ToR et système de mise en oeuvre d'une commutation de protection basée sur un réseau TRILL
WO2014047784A1 (fr) Procédé pour déterminer un trajet d'envoi de paquets, dispositif de réseau et dispositif de commande
WO2012116581A1 (fr) Procédé et dispositif pour établir une connexion de communication audio/vidéo
WO2014106387A1 (fr) Procédé d'établissement d'un canal de signalisation, d'un point d'acheminement et d'un dispositif de commande
US11991083B2 (en) Systems and methods for enhanced autonegotiation
JP6480452B2 (ja) パケット処理方法および装置
WO2021254001A1 (fr) Procédé, appareil et système d'établissement de session, et support de stockage informatique
CN104539539B (zh) 一种ac设备多业务板数据转发方法
JP2012533959A (ja) マルチキャスト対応ルータにおいて効果的なホスト・マネジメント・プロトコル
US20180123971A1 (en) Application Implementation Method and Service Controller
WO2013159492A1 (fr) Procédé et système pour le reporting et le téléchargement de données
WO2024027217A1 (fr) Procédé et système de mise en œuvre sensible au facteur temps pour un réseau central virtualisé
KR101341470B1 (ko) 서비스 품질 파라미터를 구성하기 위한 방법, 원격 액세스 서버 및 시스템
WO2012079374A1 (fr) Procédé, dispositif et système pour lier un port série virtuel et un port série physique
CN105052239B (zh) 策略控制方法、相关装置以及系统
CN113542395B (zh) 报文处理方法和报文处理系统
WO2015051548A1 (fr) Procédé, appareil et dispositif de migration de réseau virtuel
CN105519049A (zh) 一种报文传输方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13895257

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13895257

Country of ref document: EP

Kind code of ref document: A1