Traffic sending method, device and related equipment

Abstract

The present application provides a traffic sending method, device and related equipment. The method executed by the network element management and operation platform includes: obtaining a first time point and a second time point, the first time point is the time point when the first flow table completes sending, the second time point is the time point when the first migrated virtual machine completes migration, and the first flow table is the flow table required by the first migrated virtual machine; according to the first time point and the second time point, determine the time point for sending traffic to the first migrated virtual machine. When controlling the sending of traffic, the network element management and operation platform of the present application not only considers the migration status of the migrated virtual machine, but also considers the sending status of the flow table required by the migrated virtual machine, thereby improving the reliability of traffic sending.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a traffic sending method, apparatus, and related equipment. Background Art

[0002] Virtual machines have high isolation and are widely used as a security solution in Network Functions Virtualization (NFV) production environments. Virtual machines can be moved between different physical machines.

[0003] In the prior art, the network element management and operation platform (EMS or OMC for short) can send traffic to the virtual machine after the virtual machine is successfully migrated. It can be seen that the existing traffic sending method only considers the migration of the virtual machine, which easily leads to low reliability of traffic sending. Summary of the invention

[0004] The embodiments of the present application provide a traffic sending method, apparatus and related equipment to solve the problem that the reliability of traffic sending is low because the existing traffic sending method only considers the migration status of the virtual machine.

[0005] To solve the above problems, this application is implemented as follows:

[0006] In a first aspect, an embodiment of the present application provides a traffic sending method, which is executed by a network element management and operation platform OMC, and the method includes:

[0007] Obtain a first time point and a second time point, the first time point being a time point when the first flow table completes sending, the second time point being a time point when the first migrating virtual machine completes migration, and the first flow table being a flow table required by the first migrating virtual machine;

[0008] A time point for sending traffic to the first migrated virtual machine is determined according to the first time point and the second time point.

[0009] In a second aspect, an embodiment of the present application provides a traffic sending method, which is executed by a virtual resource management platform VIM, and the method includes:

[0010] Sending a flow table requirement of the first migrated virtual machine to the software defined network controller SDNC;

[0011] receiving a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine;

[0012] The first time point is sent to the OMC.

[0013] In a third aspect, an embodiment of the present application provides a traffic sending method, which is executed by an SDNC, and the method includes:

[0014] Receive a flow table requirement of a first migration virtual machine sent by the VIM;

[0015] Sending a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine;

[0016] Recording a first time point, where the first time point is a time point when the first flow table completes sending;

[0017] The first time point is sent to the VIM.

[0018] In a fourth aspect, an embodiment of the present application further provides a flow sending device, including:

[0019] A first transceiver, for:

[0020] Obtain a first time point and a second time point, the first time point being a time point when the first flow table completes sending, the second time point being a time point when the first migrating virtual machine completes migration, and the first flow table being a flow table required by the first migrating virtual machine;

[0021] The first processor is configured to determine a time point for sending traffic to the first migrated virtual machine according to the first time point and the second time point.

[0022] In a fifth aspect, an embodiment of the present application further provides a flow sending device, including:

[0023] A second transceiver is used for:

[0024] Sending a flow table requirement of the first migrated virtual machine to the software defined network controller SDNC;

[0025] receiving a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine;

[0026] The first time point is sent to the OMC.

[0027] In a sixth aspect, an embodiment of the present application further provides a flow sending device, including:

[0028] The third transceiver is used for:

[0029] Receive a flow table requirement of a first migration virtual machine sent by the VIM;

[0030] Sending a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine;

[0031] A second transceiver, configured to record a first time point, where the first time point is a time point when the first flow table completes sending;

[0032] The third transceiver is further used to send the first time point to the VIM.

[0033] In the seventh aspect, an embodiment of the present application also provides a communication device, comprising: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is used to read the program in the memory to implement the steps in the method described in the first aspect above; or, the steps in the method described in the second aspect above; or, the steps in the method described in the third aspect above.

[0034] In an eighth aspect, an embodiment of the present application further provides a readable storage medium for storing a program, wherein when the program is executed by a processor, the program implements the steps in the method described in the first aspect, or implements the steps in the method described in the second aspect; or implements the steps in the method described in the third aspect.

[0035] In the embodiment of the present application, the network element management and operation platform can not only obtain the time point when the first migration virtual machine completes the migration, but also obtain the time point when the first flow table required by the first migration virtual machine completes the sending, and then can combine the two obtained time points to determine the time point when sending traffic to the first migration virtual machine. It can be seen that when controlling the sending of traffic, the network element management and operation platform of the embodiment of the present application not only considers the migration status of the migration virtual machine, but also considers the sending status of the flow table required by the migration virtual machine, thereby improving the reliability of traffic sending. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0037] Figure 1 It is one of the structural diagrams of the network system to which the embodiments of the present application can be applied;

[0038] Figure 2 This is one of the flow charts of the traffic sending method provided in the embodiment of the present application;

[0039] Figure 3 This is the second flow chart of the traffic sending method provided in the embodiment of the present application;

[0040] Figure 4 This is the third flow chart of the traffic sending method provided in the embodiment of the present application;

[0041] Figure 5 This is the second structural diagram of the network system applicable to the embodiment of the present application;

[0042] Figure 6 It is one of the structural schematic diagrams of the flow sending device provided by the implementation of this application;

[0043] Figure 7 This is the second structural diagram of the flow sending device provided by the present application;

[0044] Figure 8 This is the third structural diagram of the flow sending device provided by the present application;

[0045] Fig. 9 It is a structural diagram of the communication device provided by the implementation of this application. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] The terms "first", "second" etc. in the embodiments of the present application are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. In addition, the terms "include" and "have" and any variation thereof are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment. In addition, "and / or" is used in the present application to represent at least one of connected objects, such as A and / or B and / or C, representing the inclusion of separate A, separate B, separate C, and A and B all exist, B and C all exist, A and C all exist, and 7 situations that A, B and C all exist.

[0048] See also Figure 1 , Figure 1 It is a structural diagram of a network system that can be applied in the embodiments of the present application.

[0049] like Figure 1As shown, it includes network element function management and orchestration function platform (NFVO for short), virtualized network element management platform (VNFM for short), virtual resource management platform (VIM for short), software defined network controller (SDNC for short), network element management and operation platform (OMC / EMS for short), virtualized network element (VNF for short) and virtualization platform (Hypervisor).

[0050] Hypervisor includes virtualized switch (vSwitch for short). VNF and Hypervisor belong to the target node of virtual machine migration; NFVO, VNFM, VIM and SDNC belong to the network element function virtualization management and orchestration system (MANO for short).

[0051] Figure 1 The two platforms with a connection relationship in the figure indicate that they can communicate with each other. Specifically, SDNC can communicate with vSwitch and VIM; VIM can communicate with SDNC, Hypervisor, VNFM and NFVO; VNFM can communicate with VIM, OMC and NFVO; NFVO can communicate with OMC, VNFM and VIM; OMC can communicate with NFVO and VNFM.

[0052] The following describes the traffic sending method provided in an embodiment of the present application.

[0053] See also Figure 2 , Figure 2 This is one of the flow charts of the traffic sending method provided in the embodiment of the present application. Figure 2 The traffic sending method shown may be executed by the OMC.

[0054] like Figure 2 As shown, the traffic sending method may include the following steps:

[0055] Step 201, obtain a first time point and a second time point, the first time point is the time point when the first flow table completes sending, the second time point is the time point when the first migrating virtual machine completes migration, and the first flow table is the flow table required by the first migrating virtual machine.

[0056] In the embodiment of the present application, considering that the vSwitch of the target node relies on flow table lookup for data forwarding, if the target node does not obtain the flow table required by the first migration virtual machine, that is, the first flow table, then the vSwitch of the target node cannot look up the first flow table for data forwarding, which is likely to cause data forwarding delay or data packet loss. Therefore, in addition to obtaining the migration status of the first migration virtual machine, the OMC of the embodiment of the present application can also obtain the flow table required by the first migration virtual machine, that is, the delivery status of the first flow table. In this way, the OMC can determine the time to send traffic to the first migration virtual machine in combination with the migration status of the first migration virtual machine and the delivery status of the first flow table to improve the reliability of traffic transmission.

[0057] In specific implementation, when the first time point is obtained, it means that the first flow table has been sent down at the first time point; when the second time point is obtained, it means that the first migrating virtual machine has completed migration at the second time point.

[0058] Step 202: Determine a time point for sending traffic to the first migrated virtual machine according to the first time point and the second time point.

[0059] In specific implementation, the time point for sending traffic to the first migrated virtual machine can be the first time point or the second time point, or it can be after the first time point or the second time point. The specific time point can be determined according to actual conditions, and the embodiments of the present application do not limit this.

[0060] In the traffic sending method of the embodiment of the present application, the network element management and operation platform can not only obtain the time point when the first migration virtual machine completes the migration, but also obtain the time point when the first flow table required by the first migration virtual machine completes the sending, and then can combine the two obtained time points to determine the time point when sending traffic to the first migration virtual machine. It can be seen that when controlling the sending of traffic, the network element management and operation platform of the embodiment of the present application not only considers the migration status of the migration virtual machine, but also considers the sending status of the flow table required by the migration virtual machine, thereby improving the reliability of traffic sending.

[0061] In the embodiment of the present application, optionally, when the first time point is less than the second time point, traffic is sent to the first migration virtual machine at a third time point, and the third time point is the second time point or is after the second time point;

[0062] In a case where the first time point is greater than or equal to the second time point, traffic is sent to the first migration virtual machine at a fourth time point, and the fourth time point is the first time point or is located after the first time point.

[0063] In this optional implementation, the OMC can ensure that traffic is sent to the migrating virtual machine only when the migrating virtual machine completes migration and the flow table required by the migrating virtual machine completes sending. In this way, traffic sending loss caused by incomplete flow table sending can be avoided.

[0064] In a specific implementation, in a first implementation, the time point at which the OMC sends traffic to the first migrated virtual machine is the first time point or the second time point. That is, the OMC immediately sends traffic to the migrated virtual machine when the migrated virtual machine completes migration and the flow table required by the migrated virtual machine completes sending.

[0065] In the second implementation, the time point at which the OMC sends traffic to the first migrated virtual machine may be after the first time point or the second time point. That is, the OMC may wait for a period of time before sending traffic to the migrated virtual machine after the migration of the migrated virtual machine is completed and the flow table required by the migrated virtual machine is completed.

[0066] It can be seen that compared with the second implementation mode, the first implementation mode can ensure the timeliness of traffic sending while ensuring the reliability of traffic sending.

[0067] The following describes how to obtain the first time point in the embodiment of the present application.

[0068] Optionally, obtaining the first time point includes any of the following:

[0069] 1) Receiving a first time point sent by the network element function management and orchestration function platform NFVO through the first interface and the second interface;

[0070] 2) receiving a first time point sent by the NFVO through the third interface;

[0071] 3) receiving a first time point sent by the virtualized network element management platform VNFM through the second interface;

[0072] The first interface is an interface between NFVO and VNFM, the second interface is an interface between VNFM and OMC, and the third interface is an interface between NFVO and OMC.

[0073] In specific implementation, during the migration of the first migrating virtual machine, the VIM may inform the SDNC of the flow table requirements of the first migrating virtual machine, so that the SDNC sends the first flow table to the vSwitch of the target node. After the first flow table is sent, the SDNC may record the first time point when the first flow table is sent, and inform the VIM of the first time point.

[0074] In 1) and 2), VIM may inform NFVO of the first time point, so that OMC is informed of the first time point through NFVO. Specifically, in 1), NFVO informs OMC of the first time point through VNFM; in 2), NFVO directly informs OMC of the first time point through the interface between NFVO and OMC.

[0075] In 3), the VIM may inform the VNFM of the first time point, so that the VNFM informs the OMC of the first time point through an interface between the VNFM and the OMC.

[0076] It can be seen that the embodiment of the present application provides multiple forwarding methods at the first time point. In 1), the forwarding path at the first time point is: SDNC→VIM→NFVO→VNFM→OMC; in 2), the forwarding path at the first time point is: SDNC→VIM→NFVO→OMC; in 3), the forwarding path at the first time point is: SDNC→VIM→VNFM→OMC.

[0077] It should be noted that the communication interface between two adjacent devices in the above forwarding path can be an enhanced or newly added interface of an existing interface, which can be determined according to actual conditions, and the embodiments of the present application do not limit this. For example, the first interface can be an or-Vnfm interface, the second interface can be an Or-vnfm-em interface, and the third interface can be a traditional northbound enhanced interface.

[0078] See also Figure 3 , Figure 3 This is the second flow chart of the traffic sending method provided in the embodiment of the present application. The traffic sending method in the embodiment of the present application can be executed by VIM.

[0079] like Figure 3 As shown, the traffic sending method may include the following steps:

[0080] Step 301: Send a flow table requirement of a first migrated virtual machine to a software defined network controller SDNC.

[0081] Step 302: Receive a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine.

[0082] Step 303: Send the first time point to the OMC.

[0083] Optionally, the sending the first time point to the OMC includes any one of the following:

[0084] Sending the first time point to the OMC through the NFVO;

[0085] The first time point is sent to the OMC through the VNFM.

[0086] In this optional implementation, considering that there are multiple OMCs, and each OMC is responsible for the migration of different virtual machines, the NFVO and the VNFM can determine the OMC corresponding to the migrated virtual machine, and send information related to the migrated virtual machine to the corresponding OMC. Therefore, the VIM can send the first time point to the NFVO or VNFM to enable the NFVO or VNFM to send the first time point to the OMC.

[0087] It can be understood that, in the implementation method of sending the first time point to the OMC through the NFVO, the corresponding Figure 2 1) and 2); in the implementation manner where the first time point is sent to the OMC by the VNFM, corresponding to Figure 2 3) in the above.

[0088] In addition, in actual applications, the VIM may send first information to the SDNC, where the first information may include the flow table requirements of the first migrated virtual machine, identification information (such as ID) of the first migrated virtual machine, and the network requirements of the first migrated virtual machine. In this way, the SDNC may create a virtual network of the first migrated virtual machine on the target node through the interface between the SDNC and the target node, so that the first migrated virtual machine communicates with the outside through the virtual network, and sends the first flow table to the vSwitch of the target node.

[0089] The VIM may send second information to the NFVO or VNFM, where the second information includes the first time point and identification information of the first migrated virtual machine. In this way, the NFVO or VNFM may determine the OMC corresponding to the first migrated virtual machine based on the identification information of the first migrated virtual machine, and send the first time point to the OMC.

[0090] In a specific implementation, VIM can send the first information to SDNC through the northbound interface of the software defined network (SDN for short). SDNC can create a virtual network of the first migrated virtual machine at the target node through the southbound interface of SDN, and send the first flow table to the vSwitch of the target node. VIM can send the second information to NFVO through the Or-Vi interface. VIM can send the second information to VNFM through the Vi-Vnfm interface. It can be understood that the above interface is only an example, and does not limit the interface expression between the two devices.

[0091] It should be noted that this embodiment is an implementation of the VIM corresponding to the above method embodiment, and therefore, reference may be made to the relevant description in the above method embodiment, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be repeated here.

[0092] See also Figure 4 , Figure 4 This is the third flow chart of the traffic sending method provided in the embodiment of the present application. The traffic sending method in the embodiment of the present application can be executed by SDNC.

[0093] like Figure 4 As shown, the traffic sending method may include the following steps:

[0094] Step 401: Receive a flow table requirement of a first migrated virtual machine sent by a VIM.

[0095] Step 402: Send a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine.

[0096] Step 403: Record a first time point, where the first time point is the time point when the first flow table completes sending.

[0097] Step 404: Send the first time point to the VIM.

[0098] It should be noted that this embodiment is an implementation method of SDNC corresponding to the above method embodiment, and therefore, reference may be made to the relevant description in the above method embodiment, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be repeated here.

[0099] The various optional implementation modes introduced in the embodiments of the present application may be implemented in combination with each other or may be implemented separately if they do not conflict with each other, and the embodiments of the present application are not limited to this.

[0100] For ease of understanding, the following examples are provided:

[0101] In the embodiment of the present application, a linkage mechanism between the SDNC and MANO systems is added during the virtual machine migration process. When the SDNC flow table is sent down, the MANO system is informed through the northbound interface, and the MANO system translates it to the EMS. The EMS combines the virtual machine migration status and the flow table sending status to determine whether the load can be diverted to the migrated virtual machine.

[0102] The following combination Figure 5 The following describes the flow sending method:

[0103] Step 1: VIM starts the migration process and selects a suitable target computing node through a scheduling algorithm to start virtual machine migration.

[0104] Step 2: VIM notifies SDNC of the migrated virtual machine ID and related network and flow table requirements through the SDN northbound interface.

[0105] Step 3: SDNC creates a virtual network at the target node through the SDN southbound interface and issues the flow table configuration.

[0106] Step 4: When the virtual network and flow table configuration are issued, SDNC notifies VIM of the completion time through the SDN northbound interface.

[0107] Step 5: VIM transfers the notification of the completion of the migrated virtual machine ID and flow table configuration and the timestamp to NFVO through the Or-Vi interface.

[0108] Step 6: NFVO searches the database based on the migrated virtual machine ID and sends the timestamp notification to the corresponding EMS / OMC through the or-Vnfm and Or-vnfm-em interfaces.

[0109] Step 7: EMS / OMC compares the timestamp (T1) of the successful flow table issuance notification with the timestamp (T2) of the completion of the virtual machine migration. If T1 < T2, the traffic to the migrated virtual machine can be released at the T2 time point; if T1 > T2, the traffic to the migrated virtual machine can be released at the T1 time point.

[0110] In the prior art, the virtual machine migration solution in the NFV / SDN field only considers whether the virtual machine migration task is successful or not, and diverts traffic to the virtual machine immediately after the virtual machine migration is successful, without considering the result of the flow table issued by the target computing node SDNC. When the SDNC issues the flow table untimely or with a delay, diverting traffic to the virtual machine will cause business losses. The embodiment of the present application adds a full-node linkage mechanism to the NFV / SDN system. While migrating the virtual machine at the virtual layer, SDNC transfers the completion status of the flow table issuance through the VIM-NFVO-EMS interface. EMS determines whether the virtual machine migration process is completed by comprehensively comparing the timestamps of the virtual machine migration status and the flow table issuance status, and then diverts traffic, which can effectively avoid business losses caused by incomplete flow table issuance.

[0111] See Figure 6 , Figure 6 which is one of the structural diagrams of the traffic sending device provided by the embodiment of the present application. As Figure 6 shown, the traffic sending device 600 includes:

[0112] A first transceiver 601, used for:

[0113] Obtain a first time point and a second time point, the first time point being a time point when the first flow table completes sending, the second time point being a time point when the first migrating virtual machine completes migration, and the first flow table being a flow table required by the first migrating virtual machine;

[0114] The first processor 602 is configured to determine a time point for sending traffic to the first migrated virtual machine according to the first time point and the second time point.

[0115] Optionally, the first transceiver 601 is configured to:

[0116] In a case where the first time point is less than the second time point, sending traffic to the first migration virtual machine at a third time point, the third time point being the second time point or being after the second time point;

[0117] In a case where the first time point is greater than or equal to the second time point, traffic is sent to the first migration virtual machine at a fourth time point, and the fourth time point is the first time point or is located after the first time point.

[0118] Optionally, the first transceiver 601 is used for any of the following:

[0119] Receiving a first time point sent by the network element function management and orchestration function platform NFVO through the first interface and the second interface;

[0120] receiving a first time point sent by the NFVO through the third interface;

[0121] Receiving a first time point sent by the virtualized network element management platform VNFM through the second interface;

[0122] The first interface is an interface between NFVO and VNFM, the second interface is an interface between VNFM and OMC, and the third interface is an interface between NFVO and OMC.

[0123] The flow sending device 600 can realize the embodiment of the present application Figure 2 The various processes of the method embodiment and the same beneficial effects are achieved, and will not be described again here to avoid repetition.

[0124] See also Figure 7 , Figure 7 This is the second structural diagram of the flow sending device provided in the embodiment of the present application. Figure 7 As shown, the traffic sending device 700 includes:

[0125] The second transceiver 701 is configured to:

[0126] Sending a flow table requirement of the first migrated virtual machine to the software defined network controller SDNC;

[0127] receiving a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine;

[0128] The first time point is sent to the OMC.

[0129] Optionally, the second transceiver 701 is used for any of the following:

[0130] Sending the first time point to the OMC through the NFVO;

[0131] The first time point is sent to the OMC through the VNFM.

[0132] The flow sending device 700 can realize the embodiment of the present application Figure 3 The various processes of the method embodiment and the same beneficial effects are achieved, and will not be described again here to avoid repetition.

[0133] See also Figure 8 , Figure 8 This is the third structural diagram of the flow sending device provided in the embodiment of the present application. Figure 8 As shown, the traffic sending device 800 includes:

[0134] The third transceiver 801 is configured to:

[0135] Receive a flow table requirement of a first migration virtual machine sent by the VIM;

[0136] Sending a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine;

[0137] The second processor 802 is configured to record a first time point, where the first time point is a time point when the first flow table completes sending;

[0138] The third transceiver 801 is further configured to send the first time point to the VIM.

[0139] The flow sending device 800 can realize the embodiment of the present application Figure 4 The various processes of the method embodiment and the same beneficial effects are achieved, and will not be described again here to avoid repetition.

[0140] The present application also provides a communication device. Fig. 9 The communication device may include a processor 901, a memory 902, and a program 9021 stored in the memory 902 and executable on the processor 901.

[0141] When the communication device is an OMC, the program 9021 can be executed by the processor 901 to achieve Figure 2 Any steps in the corresponding method embodiments and achieving the same beneficial effects will not be repeated here.

[0142] When the communication device is a VIM, program 9021 can be executed by processor 901 to achieve Figure 3 Any steps in the corresponding method embodiments and achieving the same beneficial effects will not be repeated here.

[0143] When the communication device is a SDNC, the program 9021 can be executed by the processor 901 to achieve Figure 4 Any steps in the corresponding method embodiments and achieving the same beneficial effects will not be repeated here.

[0144] A person skilled in the art can understand that all or part of the steps of implementing the above-mentioned embodiment method can be completed by hardware related to program instructions, and the program can be stored in a readable medium. The present application also provides a readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned Figure 2 , Figure 3 or Figure 4 Any steps in the corresponding method embodiments can achieve the same technical effect and will not be repeated here to avoid repetition.

[0145] The storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0146] The above is a preferred implementation of the embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles described in the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A traffic sending method, executed by a network element management and operation platform OMC, characterized in that: The method comprises: Obtain a first time point and a second time point, the first time point being a time point when the first flow table completes sending, the second time point being a time point when the first migrating virtual machine completes migration, and the first flow table being a flow table required by the first migrating virtual machine; Determine, according to the first time point and the second time point, a time point for sending traffic to the first migrated virtual machine; The determining, according to the first time point and the second time point, a time point for sending traffic to the first migration virtual machine includes: In a case where the first time point is less than the second time point, sending traffic to the first migration virtual machine at a third time point, the third time point being the second time point or being after the second time point; In a case where the first time point is greater than or equal to the second time point, traffic is sent to the first migration virtual machine at a fourth time point, and the fourth time point is the first time point or is located after the first time point.

2. The method according to claim 1, characterized in that: The obtaining of the first time point includes any of the following: Receiving a first time point sent by the network element function management and orchestration function platform NFVO through the first interface and the second interface; receiving a first time point sent by the NFVO through the third interface; Receiving a first time point sent by the virtualized network element management platform VNFM through the second interface; The first interface is an interface between NFVO and VNFM, the second interface is an interface between VNFM and OMC, and the third interface is an interface between NFVO and OMC.

3. A traffic sending method, executed by a virtual resource management platform VIM, characterized in that: The method comprises: Sending a flow table requirement of the first migrated virtual machine to the software defined network controller SDNC; receiving a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine; The first time point is sent to the OMC.

4. The method according to claim 3, characterized in that The sending the first time point to the OMC includes any one of the following: Sending the first time point to the OMC through the NFVO; The first time point is sent to the OMC through the VNFM.

5. A traffic sending method, executed by SDNC, characterized in that: The method comprises: Receive a flow table requirement of a first migrated virtual machine sent by the VIM; Sending a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine; Recording a first time point, where the first time point is a time point when the first flow table completes sending; The first time point is sent to the VIM.

6. A flow sending device, characterized in that: include: A first transceiver is used for: Obtain a first time point and a second time point, the first time point being a time point when the first flow table completes sending, the second time point being a time point when the first migrating virtual machine completes migration, and the first flow table being a flow table required by the first migrating virtual machine; A first processor, configured to determine a time point for sending traffic to the first migration virtual machine according to the first time point and the second time point; The first transceiver is used for: In a case where the first time point is less than the second time point, sending traffic to the first migration virtual machine at a third time point, the third time point being the second time point or being after the second time point; In a case where the first time point is greater than or equal to the second time point, traffic is sent to the first migration virtual machine at a fourth time point, and the fourth time point is the first time point or is located after the first time point.

7. A flow sending device, characterized in that: include: A second transceiver is used for: Sending a flow table requirement of the first migrated virtual machine to the software defined network controller SDNC; receiving a first time point sent by the SDNC, where the first time point is a time point when the first flow table is finished sending, and the first flow table is a flow table required by the first migrated virtual machine; The first time point is sent to the OMC.

8. A flow sending device, characterized in that: include: The third transceiver is used for: Receive a flow table requirement of a first migrated virtual machine sent by the VIM; Sending a first flow table to a target node for migration of the first migrating virtual machine, where the first flow table is determined based on a flow table requirement of the first migrating virtual machine; A second processor is used to record a first time point, where the first time point is a time point when the first flow table completes sending; The third transceiver is further used to send the first time point to the VIM.

9. A communication device, comprising: A transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is used to read the program in the memory to implement the steps in the traffic sending method as described in any one of claims 1 to 2; or, the steps in the traffic sending method as described in any one of claims 3 or 4; or, the steps in the traffic sending method as described in claim 5.

10. A readable storage medium for storing a program, characterized in that: When the program is executed by the processor, the steps of the traffic sending method according to any one of claims 1 to 2 are implemented; Or, the steps in the traffic sending method as claimed in any one of claims 3 or 4; Or, the steps in the traffic sending method as described in claim 5.

Images