Method, device, equipment, storage medium and program product for deleting flow table information

By evaluating and progressively processing the flow table information of the host machine, the network instability caused by flow table deletion in the cloud platform was resolved, ensuring the connectivity and stability of network links.

CN119520391BActive Publication Date: 2026-02-10CHINA TELECOM CLOUD TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411749211.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-02
Publication Date
2026-02-10
Estimated Expiration
2044-12-02

AI Technical Summary

Technical Problem

Deleting the flow table corresponding to the old version of the CNP controller directly in the cloud platform can easily lead to poor network stability.

Method used

By acquiring all flow table information on the host machine, network link connectivity is assessed, and flow table information that does not correspond to the current version number is gradually deleted based on the assessment results. This includes sending high-priority specific flow table information, flow table information corresponding to the current version number, or all flow table information to the host machine to ensure that network link connectivity meets preset requirements.

Benefits of technology

While ensuring network link connectivity, flow table information that does not correspond to the current version number of the controller is safely deleted, thus improving network stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119520391B_ABST
    Figure CN119520391B_ABST
Patent Text Reader

Abstract

The application relates to a flow table information deletion method and device, equipment, a storage medium and a program product. The method comprises the following steps: obtaining all flow table information on a host computer, in the case that target flow table information exists in the all flow table information, evaluating link connectivity of a network where the host computer is located to obtain a first evaluation result, and performing a deletion operation on the target flow table information according to the first evaluation result, the target flow table information being flow table information that does not correspond to a current version number of a controller where the host computer is located. The above method realizes the following: in the case that flow table information that does not correspond to a current version number of a controller where a host computer is located exists on the host computer, first, the link connectivity of the network where the host computer is located is evaluated, and in the case that the link connectivity of the network where the host computer is located meets preset connectivity requirements, the flow table information that does not correspond to the current version number of the controller is deleted, so that the link connectivity of the network where the host computer is located is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cloud platforms, and in particular to a flow table information deletion method and device, equipment, a storage medium and a program product. BACKGROUND

[0002] With the continuous popularity of cloud computing, the development of communication technology and the increasing demand of users for cloud computing platforms, the resource pool function of the cloud computing platform needs to be constantly updated, and accordingly, the version of the Cloud Network Plateform (CNP) controller in the cloud computing platform also needs to be iterated.

[0003] Since the CNP controller manages multiple host computers, each host computer issues corresponding flow tables when network flows pass through, and different versions of the CNP controller have different flow tables issued by the corresponding host computers. Therefore, with the iterative update of the CNP controller version, the flow tables corresponding to the host computers also need to be updated, that is, the flow tables corresponding to the old version of the CNP controller are deleted to ensure the stability of the currently used network.

[0004] However, directly deleting the flow tables corresponding to the old version of the CNP controller in the current running process of the cloud platform can easily cause poor network stability. SUMMARY

[0005] Therefore, it is necessary to provide a flow table information deletion method, device, equipment, storage medium and program product capable of deleting the flow tables corresponding to the old version of the controller while ensuring network stability.

[0006] In a first aspect, the present application provides a flow table information deletion method, comprising:

[0007] obtaining all flow table information on a host computer;

[0008] In the case where it is determined that there is target flow table information in all flow table information, evaluating the link connectivity of the network where the host computer is located to obtain a first evaluation result, and performing a deletion operation on the target flow table information according to the first evaluation result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host computer is located.

[0009] In one of the embodiments, the deletion operation on the target flow table information according to the first evaluation result comprises:

[0010] If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the network's link connectivity is evaluated a second time to obtain the second evaluation result. If the second evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0011] In one embodiment, before assessing the link connectivity of the network where the host machine resides, the method further includes:

[0012] Send high-priority specific flow table information to the host machine; high-priority specific flow table information is necessary for effectively assessing link connectivity.

[0013] If the second evaluation result indicates that the network's link connectivity meets the preset link requirements, then the high-priority specific flow table information on the host machine will be deleted.

[0014] In one embodiment, the above-mentioned equalization processing of the deletion operation based on the second evaluation result includes:

[0015] Send the flow table information corresponding to the current version number to the host machine;

[0016] A third assessment of network link connectivity is conducted to obtain the third assessment result. If the third assessment result indicates that the network link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the third assessment result.

[0017] In one embodiment, the above-mentioned equalization processing of the deletion operation based on the third evaluation result includes:

[0018] Send all flow table information to the host machine;

[0019] The network link connectivity is evaluated a fourth time to obtain the fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, the deletion operation process ends.

[0020] In one embodiment, the method further includes:

[0021] All flow table information is backed up and stored.

[0022] In one embodiment, the method further includes:

[0023] Determine whether the target flow table information exists in all flow table information;

[0024] Determine whether the target flow table information exists in all flow table information, including:

[0025] If there is flow table information in all flow table information that does not correspond to the current version number of the controller, then it is determined that there is target flow table information in all flow table information.

[0026] If all flow table information corresponds to the current version number of the controller, then it is determined that the target flow table information does not exist in the total flow table information.

[0027] Secondly, this application also provides a device for deleting flow table information, comprising:

[0028] The acquisition module is used to acquire all flow table information on the host machine;

[0029] The deletion module is used to assess the link connectivity of the host network when it is determined that the target flow table information exists in all flow table information, obtain a first assessment result, and delete the target flow table information according to the first assessment result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host is located.

[0030] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0031] The acquisition module is used to acquire all flow table information on the host machine;

[0032] The deletion module is used to assess the link connectivity of the host network when it is determined that the target flow table information exists in all flow table information, obtain a first assessment result, and delete the target flow table information according to the first assessment result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host is located.

[0033] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0034] The acquisition module is used to acquire all flow table information on the host machine;

[0035] The deletion module is used to assess the link connectivity of the host network when it is determined that the target flow table information exists in all flow table information, obtain a first assessment result, and delete the target flow table information according to the first assessment result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host is located.

[0036] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0037] The acquisition module is used to acquire all flow table information on the host machine;

[0038] The deletion module is used to assess the link connectivity of the host network when it is determined that the target flow table information exists in all flow table information, obtain a first assessment result, and delete the target flow table information according to the first assessment result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host is located.

[0039] The aforementioned method, apparatus, device, storage medium, and program product for deleting flow table information first acquires all flow table information on the host machine. If the target flow table information exists among all the flow table information, the link connectivity of the network where the host machine resides is evaluated to obtain a first evaluation result. Based on the first evaluation result, the target flow table information is deleted. The target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine resides. This method implements a solution where, when flow table information exists on the host machine that does not correspond to the current version number of the controller where the host machine resides, the link connectivity of the network where the host machine resides is first evaluated. If the link connectivity of the network where the host machine resides meets a preset connectivity requirement, the flow table information that does not correspond to the current version number of the controller is deleted, thus ensuring the link connectivity of the network where the host machine resides. Compared with existing methods that directly delete flow table information that does not correspond to the current version number of the controller, this method considers the link connectivity of the network and, to a certain extent, ensures the link stability of the network. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 This is an application environment diagram of a method for deleting flow table information in one embodiment;

[0042] Figure 2 This is a flowchart illustrating a method for deleting flow table information in one embodiment;

[0043] Figure 3 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0044] Figure 4 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0045] Figure 5This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0046] Figure 6 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0047] Figure 7 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0048] Figure 8 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0049] Figure 9 This is a flowchart illustrating a method for deleting flow table information in another embodiment;

[0050] Figure 10 This is a structural block diagram of a flow table information deletion device in one embodiment;

[0051] Figure 11 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0053] With the increasing popularity of cloud computing, the development of communication technology, and the growing demands of users for cloud computing platforms, the resource pool function of cloud computing platforms needs to be constantly updated. Consequently, the version of the Cloud Network Platform (CNP) controller in the cloud computing platform also needs to be iterated accordingly.

[0054] Since the CNP controller manages multiple hosts, each host will issue corresponding flow tables when the network is in operation. Different versions of the CNP controller will issue different flow tables to the corresponding hosts. Therefore, as the CNP controller is updated, the flow tables corresponding to the hosts also need to be updated, that is, the flow tables corresponding to the old version of the CNP controller are deleted to ensure the stability of the network currently in use.

[0055] However, directly deleting the flow tables corresponding to the old version of the CNP controller during current cloud platform operation can easily lead to poor network stability. This application aims to solve this problem.

[0056] Having described the background technology of the flow table information deletion method provided in the embodiments of this application, the implementation environment involved in the flow table information deletion method provided in the embodiments of this application will be briefly described below. The flow table information deletion method provided in the embodiments of this application can be applied to, for example... Figure 1 The cloud platform shown includes a controller 102 and multiple host machines 104. The controller 102 is connected to each host machine 104. The controller 102 controls each host machine 104. For example, the controller 102 issues certain control commands to each host machine 104 so that each host machine 104 completes the corresponding control operation according to the control command and feeds back the operation result to the controller 102 after the operation is completed. Alternatively, the controller 102 obtains all flow table information on the host machine 104, determines the target flow table information corresponding to the old version of the controller 102 from all flow table information, and issues an instruction to the host machine 104 to delete the target flow table information so that the host machine 104 deletes the target flow table information after receiving the instruction to delete the target flow table information.

[0057] In other possible implementations, the method for deleting flow table information provided in this application embodiment can also be applied to a terminal. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc.

[0058] After introducing the application scenarios of the flow table information deletion method provided in the embodiments of this application above, the following focuses on the flow table information deletion method described in this application.

[0059] In one embodiment, such as Figure 2 As shown, a method for determining flow table information is provided, which is then applied to... Figure 1 Taking controller 102 as an example, the following steps are included:

[0060] S201. Obtain all flow table information on the host machine.

[0061] The host machine refers to any host machine managed by the controller in the cloud platform. All flow table information includes flow table information corresponding to the old version of the controller, as well as flow table information corresponding to the current version of the controller.

[0062] It should be noted that the flow tables issued by the host machine differ for different versions of the controller. There is a one-to-one correspondence between a controller version and the flow table information issued by the host machine under that version. For example, there is a one-to-one correspondence between the old version of the controller and the flow table information issued by the host machine under the old version, and there is a one-to-one correspondence between the current version of the controller and the flow table information issued by the host machine under the current version.

[0063] For example, the flow table cookie information sent by the controller to the host is 64 bits long. For example, the flow table cookie information can be: 0x0000000000000000, where each bit is a hexadecimal number [63 62 …0]. The high bits [59 … 40] of the flow table cookie information are taken as the version flag. Under this premise, assuming the controller version number is: 1.2.3, where 1 represents the current implementation framework. If the controller framework is refactored, this value will increment by 1. 2 represents a stable version. Every time the controller releases a stable version, this value will increment by 1. 3 represents that the previous stable version needs to release an SP version. The value will increment sequentially based on the original stable version. Therefore, the controller version number (1.2.3) is integrated into the flow table cookie information, which is the flow table cookie information 0x0102030000000000 that incorporates the controller version number. Thus, a one-to-one correspondence between the flow table cookie information and the controller version number is achieved.

[0064] In this embodiment of the application, when it is necessary to update the flow table corresponding to the host machine, it is necessary to delete the flow table information on the host machine that does not correspond to the current version number of the controller. At this time, the controller needs to first obtain all the flow table information on the host machine so as to analyze all the flow table information in the future to determine the flow table information that does not correspond to the current version number of the controller, and provide a data basis for deleting the flow table information that does not correspond to the current version number of the controller.

[0065] S202. If it is determined that the target flow table information exists in all flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted according to the first evaluation result.

[0066] Among them, the target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0067] The first evaluation result includes whether the network link connectivity meets the preset connectivity requirements and whether the network link connectivity does not meet the preset connectivity requirements.

[0068] In this embodiment of the application, after obtaining all flow table information on the host machine, it can be determined one by one whether all flow table information corresponds to the current version number of the controller. If there is no flow table information corresponding to the current version number of the controller, it means that all flow table information is the target flow table information. If there is flow table information corresponding to the current version number of the controller and flow table information that does not correspond to the current version number of the controller, it means that the flow table information that does not correspond to the current version number of the controller is the target flow table information. If there is no flow table information that does not correspond to the current version number of the controller, it means that all flow table information is not the target flow table information, that is, the target flow table information does not exist in the entire flow table information.

[0069] Furthermore, if the target flow table information is found in all flow table information, the link connectivity of the host network is evaluated to obtain a first evaluation result. Optionally, the network link connectivity test can be implemented by performing gateway ping tests using the vpping test script. That is, the controller can call the vpping test script to perform gateway ping tests to obtain a first evaluation result indicating whether the network link connectivity of the host meets the preset connectivity requirements or whether the network link connectivity of the host does not meet the preset connectivity requirements.

[0070] It should be noted that the vpping test script monitors the virtual machine traffic corresponding to the host machine. It checks whether the virtual machine traffic remains consistent before and after deleting the target flow table information. It should also be noted that the vpping test script will be called to verify the connectivity of the virtual machine traffic network link before and after deleting the target flow table information, and the results of the two ping tests will be compared. This solution also considers the possibility of virtual machines being blocked from ping. Therefore, during script execution, it retrieves the gateway information corresponding to the virtual machine based on the virtual machine information, and then automatically adds high-priority specific flow table information for the gateway that allows inbound and outbound traffic. Before deleting residual flow tables, it ensures the connectivity of the ping link from the tenant gateway to the virtual machine. After deleting the target flow table information, it immediately performs a gateway ping test on the virtual machine and compares the results before and after the deletion of the residual flow table. If the network link connectivity meets the preset connectivity conditions before deleting the target flow table information, but does not meet the preset connectivity conditions after deleting the target flow table information, it can be considered that the flow table pipeline is interrupted, the target flow table information is still being used, and the relevant flow tables involved in the currently running stable version have not been distributed. This ping test method can quickly detect whether the customer's business is affected, and may also further discover whether the code has introduced problems.

[0071] Furthermore, if the first evaluation result indicates that the network link connectivity corresponding to the host machine meets the preset connectivity requirements, the controller may delete the target flow table information; if the first evaluation result indicates that the network link connectivity corresponding to the host machine does not meet the preset connectivity requirements, the controller may not delete the target flow table information.

[0072] The method for deleting flow table information provided in this application first obtains all flow table information on the host machine. If a target flow table information is found among all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result. Based on the first evaluation result, the target flow table information is deleted. The target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located. This method implements a solution where, when flow table information exists on the host machine that does not correspond to the current version number of the controller where the host machine is located, the link connectivity of the network where the host machine is located is first evaluated. If the link connectivity of the network where the host machine is located meets a preset connectivity requirement, the flow table information that does not correspond to the current version number of the controller is deleted, thus ensuring the link connectivity of the network where the host machine is located. Compared with existing methods that directly delete flow table information that does not correspond to the current version number of the controller, this method considers the link connectivity of the network and, to a certain extent, ensures the link stability of the network.

[0073] In one embodiment, in Figure 2 Based on the illustrated embodiment, the process of deleting target flow table information according to the first evaluation result can be described, see [link to example]. Figure 3 That is, the above-mentioned S202 "delete the target flow table information according to the first evaluation result" includes:

[0074] S203. If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the network's link connectivity is evaluated a second time to obtain the second evaluation result. If the second evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0075] The second evaluation result includes whether the network link connectivity meets the preset connectivity requirements and whether the network link connectivity does not meet the preset connectivity requirements.

[0076] In this embodiment, if the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After detecting that the host machine has completely deleted the target flow table information, a second evaluation is performed on the link connectivity of the network where the host machine is located. This yields a second evaluation result indicating that the network's link connectivity meets the preset connectivity requirements, or a second evaluation result indicating that the network's link connectivity does not meet the preset connectivity requirements. If the second evaluation result indicates that the network's link connectivity meets the preset connectivity requirements, then the deleted target flow table information is considered to be flow table information that is no longer in use. If the second evaluation result indicates that the network's link connectivity does not meet the preset connectivity requirements, then it is considered that there are still flow table information in the deleted target flow table information that is currently in use. Deleting these currently in use flow table information causes the network's link connectivity to fail to meet the preset connectivity conditions. Therefore, it is necessary to re-identify the currently in use flow table information in the target flow table information and not delete the currently in use flow table information to ensure the network's link connectivity.

[0077] It should be noted that the second evaluation is used to test the network link connectivity. This can be achieved by using the vpping test script to perform gateway ping tests. That is, the controller can call the vpping test script to perform gateway ping tests and obtain the second evaluation result: either the network link connectivity of the host machine meets the preset connectivity requirements, or the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0078] The above-mentioned method for deleting flow table information, by evaluating the network link connectivity of the host machine after deleting the target flow table information, can not only ensure that the network link connectivity meets the requirements after deleting the target flow table information, but also ensure that the host machine is further processed when the network link connectivity does not meet the requirements after deleting the target flow table information, thereby ensuring that the network link connectivity of the host machine meets the requirements under any circumstances.

[0079] In one embodiment, in Figure 3 Based on the illustrated embodiment, before evaluating the link connectivity of the host network, please refer to... Figure 4 The above methods also include:

[0080] S204. Send high-priority specific flow table information to the host machine.

[0081] Among these, high-priority specific flow table information is essential for effectively assessing link connectivity. By adding high-priority specific flow table information, the host machine ensures that the client's virtual machines are not blocked from PING during subsequent network link connectivity assessments.

[0082] In this embodiment of the application, before assessing the link connectivity of the network where the host machine is located, the controller can first send high-priority specific flow label information to the host machine so that the host machine can add high-priority specific flow label information, thereby avoiding the situation where the client's virtual machine is blocked from PING when the network link connectivity is assessed later.

[0083] S205. If the second evaluation result indicates that the network link connectivity meets the preset link requirements, delete the high-priority specific flow table information on the host machine.

[0084] In this embodiment of the application, if the second evaluation result indicates that the network link connectivity meets the preset link requirements, then the target flow table information to be deleted is considered to be flow table information that is no longer used. That is, deleting the target flow table information has no impact on the network link connectivity. At this time, a deletion command can be sent to the host machine so that the host machine can delete the high-priority specific flow table information on it.

[0085] The method for deleting flow table information provided in this application avoids the situation where the client's virtual machine is blocked from PING when performing network link connectivity assessment by adding high-priority specific flow table information on the host machine.

[0086] In one embodiment, in Figure 3 Based on the illustrated embodiment, the process of balancing the deletion operation according to the second evaluation result can be described, see [link to relevant documentation]. Figure 5 That is, the above-mentioned S203 "balancing the deletion operation based on the second evaluation result" includes:

[0087] S301: Send the flow table information corresponding to the current version number to the host machine.

[0088] In this embodiment of the application, if the second evaluation result indicates that the network link connectivity fails to meet the preset link requirements, it means that there is currently used flow table information in the deleted target flow table information. In this case, in order to exclude the flow table information corresponding to the current version number of the controller from being deleted, the flow table information of the current version number can be resent to the host machine.

[0089] S302. Perform a third evaluation on the network link connectivity to obtain the third evaluation result. If the third evaluation result indicates that the network link connectivity fails to meet the preset link requirements, perform balanced processing on the deletion operation based on the third evaluation result.

[0090] In this embodiment, after detecting that the host machine has received flow table information corresponding to the current version number, a third evaluation can be performed on the link connectivity of the network where the host machine is located. The third evaluation result is either that the network link connectivity meets the preset connectivity requirements or that the network link connectivity does not meet the preset connectivity requirements. If the third evaluation result is that the network link connectivity meets the preset connectivity requirements, it is considered that the target flow table information to be deleted includes the flow table information corresponding to the current version number, indicating a false deletion. If the third evaluation result is that the network link connectivity does not meet the preset connectivity requirements, it is considered that the target flow table information to be deleted still contains flow table information corresponding to historical version numbers that are currently in use. Deleting these currently used flow table information corresponding to historical version numbers makes the network link connectivity not meet the preset connectivity conditions. Therefore, it is necessary to re-determine the flow table information currently in use in the target flow table information and not delete the currently used flow table information to ensure the network link connectivity.

[0091] Optionally, if the third evaluation result indicates that the network link connectivity meets the preset connectivity requirements, it is considered that the target flow table information to be deleted includes the flow table information corresponding to the current version number, indicating a case of accidental deletion. In this case, the high-priority specific flow table information on the host machine can be deleted.

[0092] It should be noted that the third evaluation is used to test the network link connectivity. This can be achieved by using the vpping test script to perform gateway ping tests. That is, the controller can call the vpping test script to perform gateway ping tests and obtain the third evaluation result, which indicates whether the network link connectivity of the host machine meets the preset connectivity requirements, or whether the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0093] The aforementioned method for deleting flow table information assesses the network connectivity of the host machine after the flow table information corresponding to the current version number has been distributed. This ensures that the network connectivity failure is not caused by the accidental deletion of the flow table information corresponding to the current version number. If the network connectivity failure is not caused by the accidental deletion of the flow table information corresponding to the current version number, further processing is performed on the host machine to ensure that the network connectivity of the host machine meets the requirements under any circumstances.

[0094] In one embodiment, in Figure 5 Based on the illustrated embodiment, the process of balancing the deletion operation according to the third evaluation result can be described, see [link to relevant documentation]. Figure 6 That is, the above-mentioned S302 "balancing the deletion operation based on the third evaluation result" includes:

[0095] S401: Send all flow table information to the host machine.

[0096] In this embodiment of the application, if the third evaluation result indicates that the network link connectivity fails to meet the preset link requirements, it means that the deleted target flow table information contains flow table information corresponding to a historical version that is currently in use. In this case, all flow table information can be resent to the host machine.

[0097] S402. Perform a fourth evaluation on the network link connectivity to obtain the fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, end the deletion operation process.

[0098] In this embodiment, after detecting that the host machine has received all flow table information, a fourth evaluation can be performed on the link connectivity of the network where the host machine is located. The fourth evaluation result is either that the link connectivity of the network meets the preset connectivity requirements, or that the link connectivity of the network does not meet the preset connectivity requirements. If the fourth evaluation result is that the link connectivity of the network meets the preset connectivity requirements, it is considered that the target flow table information to be deleted includes the flow table information corresponding to the historical version number that is currently in use. The deletion operation process needs to be terminated. The deletion operation is performed again after the flow table information corresponding to the historical version number that is currently in use has been used, so as to ensure the link connectivity of the network.

[0099] Optionally, if the fourth evaluation result indicates that the network's link connectivity meets the preset connectivity requirements, then the high-priority specific flow table information on the host machine can be deleted.

[0100] It should be noted that the fourth evaluation is used to test the network link connectivity. This can be achieved by using the vpping test script to perform gateway ping tests. That is, the controller can call the vpping test script to perform gateway ping tests and obtain the fourth evaluation result, which indicates whether the network link connectivity of the host machine meets the preset connectivity requirements, or whether the network link connectivity of the host machine does not meet the preset connectivity requirements.

[0101] The above-mentioned method for deleting flow table information assesses the network connectivity of the host machine after all flow table information has been distributed, ensuring that network connectivity issues are not caused by the accidental deletion of flow table information corresponding to historical version numbers. If the network connectivity issues are caused by the accidental deletion of flow table information corresponding to historical version numbers, the deletion operation is terminated.

[0102] In one embodiment, in Figures 2-6 Based on the illustrated embodiment, see also Figure 7 The above methods also include:

[0103] S206. Back up and store all flow table information.

[0104] In this embodiment of the application, if it is determined that the target flow table information exists in all flow table information, all flow table information can be backed up and stored first. After the backup and storage of all flow table information is completed, the flow table information corresponding to the current version number is resent to the host machine, and the link connectivity of the network where the host machine is located is evaluated to obtain the first evaluation result.

[0105] The method for backing up and storing all flow table information provided in this application provides a data foundation for subsequently distributing all flow table information to the host machine.

[0106] In one embodiment, in Figures 2-6 Based on the illustrated embodiment, see also Figure 8 The above methods also include:

[0107] S207. Determine whether the target flow table information exists in all flow table information.

[0108] In this embodiment of the application, after obtaining all flow table information on the host machine, it can be determined whether each flow table information in the total flow table information corresponds to the current version number of the controller. If each flow table information corresponds to the current version number of the controller, it indicates that there is no target flow table information in the total flow table information. If there is flow table information in the total flow table information that does not correspond to the current version number of the controller, it indicates that there is target flow table information in the total flow table information.

[0109] Optionally, the above-mentioned S207 "determine whether the target flow table information exists in all flow table information" includes: if there is flow table information in all flow table information that does not correspond to the current version of the controller, then determine that the target flow table information exists in all flow table information; if all flow table information corresponds to the current version of the controller, then determine that the target flow table information does not exist in all flow table information.

[0110] The method for deleting flow table information provided in this application determines the target flow table information among all flow table information by using the controller's version number, thus providing a data basis for subsequent deletion of the target flow table information.

[0111] In one embodiment, see Figure 9 It also provides a method for deleting flow table information, including:

[0112] S10. Obtain all flow table information on the host machine;

[0113] S11. Back up and store all flow table information;

[0114] S12. If it is determined that the target flow table information exists in all flow table information, send the high-priority specific flow table information to the host machine.

[0115] S13. Evaluate the link connectivity of the network where the host machine is located and obtain the first evaluation result;

[0116] S14. If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, delete the target flow table information.

[0117] S15. After performing the deletion operation, perform a second evaluation of the network link connectivity to obtain the second evaluation result;

[0118] S16. If the second evaluation result indicates that the network link connectivity fails to meet the preset link requirements, send the flow table information corresponding to the current version number to the host machine.

[0119] S17. Perform a third evaluation on the network link connectivity to obtain the third evaluation result;

[0120] S18. If the third evaluation result indicates that the network link connectivity fails to meet the preset link requirements, send all flow table information to the host machine.

[0121] S19. Perform a fourth evaluation on the network link connectivity to obtain a fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, end the deletion operation process and delete the high-priority specific flow table information.

[0122] The above method addresses the issue of flow table information on the host machine that does not correspond to the current version number of the controller. It first assesses the link connectivity of the host machine's network and, if the network connectivity meets preset connectivity requirements, deletes the flow table information that does not correspond to the controller's current version number. This ensures the link connectivity of the host machine's network. Compared to existing methods that directly delete flow table information that does not correspond to the controller's current version number, the above method considers network link connectivity and, to a certain extent, guarantees network link stability.

[0123] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0124] Based on the same inventive concept, this application also provides a flow table information deletion apparatus for implementing the flow table information deletion method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more flow table information deletion apparatus embodiments provided below can be found in the limitations of the flow table information deletion method described above, and will not be repeated here.

[0125] In one exemplary embodiment, such as Figure 10 As shown, a device for deleting flow table information is provided, including: an acquisition module 10 and a deletion module 11, wherein:

[0126] Module 10 is used to obtain all flow table information on the host machine.

[0127] The deletion module 11 is used to evaluate the link connectivity of the network where the host machine is located when it is determined that the target flow table information exists in all flow table information, obtain a first evaluation result, and perform a deletion operation on the target flow table information according to the first evaluation result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0128] In an exemplary embodiment, the deletion module 11 includes: a first deletion unit, specifically configured to perform a deletion operation on the target flow table information when the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirements, and after performing the deletion operation, perform a second evaluation on the link connectivity of the network to obtain a second evaluation result, and perform balanced processing on the deletion operation according to the second evaluation result when the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements.

[0129] In an exemplary embodiment, before assessing the link connectivity of the network where the host machine resides, the above apparatus further includes: a distribution unit and a second deletion unit, wherein:

[0130] The distribution unit is specifically used to distribute high-priority specific flow table information to the host machine; the high-priority specific flow table information is necessary for effectively assessing link connectivity.

[0131] The second deletion unit is specifically used to delete high-priority specific flow table information on the host machine when the second evaluation result indicates that the network link connectivity meets the preset link requirements.

[0132] In an exemplary embodiment, the second deletion unit is specifically used to send flow table information corresponding to the current version number to the host machine; to perform a third evaluation on the network link connectivity to obtain a third evaluation result; and to perform balanced processing on the deletion operation based on the third evaluation result if the third evaluation result indicates that the network link connectivity fails to meet the preset link requirements.

[0133] In an exemplary embodiment, the second deletion unit is specifically used to send all flow table information to the host machine; perform a fourth evaluation on the network link connectivity to obtain a fourth evaluation result; and end the deletion operation process when the fourth evaluation result indicates that the network link connectivity meets the preset link requirements.

[0134] In one exemplary embodiment, the above apparatus further includes a backup module for backing up and storing all flow table information.

[0135] In an exemplary embodiment, the above apparatus further includes: a determining module, configured to determine whether target flow table information exists in all flow table information;

[0136] The determining module includes: a first determining unit and a second determining unit, wherein:

[0137] The first determining unit is specifically used to determine that the target flow table information exists in all flow table information when there is flow table information in all flow table information that does not correspond to the current version number of the controller.

[0138] The second determining unit is specifically used to determine that the target flow table information does not exist in all flow table information when all flow table information corresponds to the current version number of the controller.

[0139] Each module in the aforementioned flow table information deletion device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0140] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 11As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores flow table information. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a method for deleting flow table information.

[0141] Those skilled in the art will understand that Figure 11 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0142] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0143] Obtain all flow table information on the host machine;

[0144] If the target flow table information is found in all flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted based on the first evaluation result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0145] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0146] If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the network's link connectivity is evaluated a second time to obtain the second evaluation result. If the second evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0147] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0148] Send high-priority specific flow table information to the host machine; high-priority specific flow table information is necessary for effectively assessing link connectivity.

[0149] If the second evaluation result indicates that the network's link connectivity meets the preset link requirements, then the high-priority specific flow table information on the host machine will be deleted.

[0150] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0151] Send the flow table information corresponding to the current version number to the host machine;

[0152] A third assessment of network link connectivity is conducted to obtain the third assessment result. If the third assessment result indicates that the network link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the third assessment result.

[0153] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0154] Send all flow table information to the host machine;

[0155] The network link connectivity is evaluated a fourth time to obtain the fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, the deletion operation process ends.

[0156] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0157] All flow table information is backed up and stored.

[0158] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0159] Determine whether the target flow table information exists in all flow table information;

[0160] Determine whether the target flow table information exists in all flow table information, including:

[0161] If there is flow table information in all flow table information that does not correspond to the current version number of the controller, then it is determined that there is target flow table information in all flow table information.

[0162] If all flow table information corresponds to the current version number of the controller, then it is determined that the target flow table information does not exist in the total flow table information.

[0163] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0164] Obtain all flow table information on the host machine;

[0165] If the target flow table information is found in all flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted based on the first evaluation result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0166] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0167] If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the network's link connectivity is evaluated a second time to obtain the second evaluation result. If the second evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0168] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0169] Send high-priority specific flow table information to the host machine; high-priority specific flow table information is necessary for effectively assessing link connectivity.

[0170] If the second evaluation result indicates that the network's link connectivity meets the preset link requirements, then the high-priority specific flow table information on the host machine will be deleted.

[0171] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0172] Send the flow table information corresponding to the current version number to the host machine;

[0173] A third assessment of network link connectivity is conducted to obtain the third assessment result. If the third assessment result indicates that the network link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the third assessment result.

[0174] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0175] Send all flow table information to the host machine;

[0176] The network link connectivity is evaluated a fourth time to obtain the fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, the deletion operation process ends.

[0177] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0178] All flow table information is backed up and stored.

[0179] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0180] Determine whether the target flow table information exists in all flow table information;

[0181] Determine whether the target flow table information exists in all flow table information, including:

[0182] If there is flow table information in all flow table information that does not correspond to the current version number of the controller, then it is determined that there is target flow table information in all flow table information.

[0183] If all flow table information corresponds to the current version number of the controller, then it is determined that the target flow table information does not exist in the total flow table information.

[0184] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0185] Obtain all flow table information on the host machine;

[0186] If the target flow table information is found in all flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result, and the target flow table information is deleted based on the first evaluation result; the target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located.

[0187] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0188] If the first evaluation result indicates that the network's link connectivity performance meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the network's link connectivity is evaluated a second time to obtain the second evaluation result. If the second evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result.

[0189] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0190] Send high-priority specific flow table information to the host machine; high-priority specific flow table information is necessary for effectively assessing link connectivity.

[0191] If the second evaluation result indicates that the network's link connectivity meets the preset link requirements, then the high-priority specific flow table information on the host machine will be deleted.

[0192] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0193] Send the flow table information corresponding to the current version number to the host machine;

[0194] A third assessment of network link connectivity is conducted to obtain the third assessment result. If the third assessment result indicates that the network link connectivity fails to meet the preset link requirements, the deletion operation is balanced according to the third assessment result.

[0195] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0196] Send all flow table information to the host machine;

[0197] The network link connectivity is evaluated a fourth time to obtain the fourth evaluation result. If the fourth evaluation result indicates that the network link connectivity meets the preset link requirements, the deletion operation process ends.

[0198] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0199] All flow table information is backed up and stored.

[0200] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0201] Determine whether the target flow table information exists in all flow table information;

[0202] Determine whether the target flow table information exists in all flow table information, including:

[0203] If there is flow table information in all flow table information that does not correspond to the current version number of the controller, then it is determined that there is target flow table information in all flow table information.

[0204] If all flow table information corresponds to the current version number of the controller, then it is determined that the target flow table information does not exist in the total flow table information.

[0205] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0206] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0207] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0208] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for deleting flow table information, characterized in that, The method includes: Obtain all flow table information on the host machine; If the target flow table information is found in all the flow table information, the link connectivity of the network where the host machine is located is evaluated to obtain a first evaluation result. If the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirements, the target flow table information is deleted. After the deletion operation is performed, the link connectivity of the network is evaluated a second time to obtain a second evaluation result. If the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result. The target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located. The step of balancing the deletion operation based on the second evaluation result includes: Send the flow table information corresponding to the current version number to the host machine; The network's link connectivity is evaluated a third time to obtain a third evaluation result. If the third evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, all flow table information is sent to the host machine. The link connectivity of the network is evaluated for the fourth time to obtain the fourth evaluation result. If the fourth evaluation result indicates that the link connectivity of the network meets the preset link requirements, the deletion operation process ends.

2. The method according to claim 1, characterized in that, Before assessing the link connectivity of the network where the host machine resides, the method further includes: The host machine is issued high-priority specific flow table information; the high-priority specific flow table information is necessary information for effectively assessing link connectivity. If the second evaluation result indicates that the network's link connectivity meets the preset link requirements, the high-priority specific flow table information on the host machine will be deleted.

3. The method according to claim 1 or 2, characterized in that, The method further includes: All the flow table information is backed up and stored.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Determine whether the target flow table information exists among all the flow table information; Determining whether the target flow table information exists among all the flow table information includes: If there is flow table information in all flow table information that does not correspond to the current version number of the controller, then it is determined that the target flow table information exists in all flow table information. If all the flow table information corresponds to the current version number of the controller, then it is determined that the target flow table information does not exist in the total flow table information.

5. A device for deleting flow table information, characterized in that, The device includes: The acquisition module is used to acquire all flow table information on the host machine; The deletion module is used to, when it is determined that target flow table information exists in all flow table information, evaluate the link connectivity of the network where the host machine is located to obtain a first evaluation result. If the first evaluation result indicates that the link connectivity performance of the network meets the preset link requirements, then the target flow table information is deleted. After the deletion operation is performed, the link connectivity of the network is evaluated a second time to obtain a second evaluation result. If the second evaluation result indicates that the link connectivity of the network fails to meet the preset link requirements, the deletion operation is balanced according to the second evaluation result. The target flow table information is flow table information that does not correspond to the current version number of the controller where the host machine is located. The step of balancing the deletion operation based on the second evaluation result includes: The process involves sending the flow table information corresponding to the current version number to the host machine; performing a third evaluation on the network's link connectivity to obtain a third evaluation result; and, if the third evaluation result indicates that the network's link connectivity fails to meet the preset link requirements, sending all flow table information to the host machine; performing a fourth evaluation on the network's link connectivity to obtain a fourth evaluation result; and, if the fourth evaluation result indicates that the network's link connectivity meets the preset link requirements, ending the deletion operation process.

6. The apparatus according to claim 5, characterized in that, The device further includes: The distribution unit is used to distribute high-priority specific flow table information to the host machine; the high-priority specific flow table information is necessary information for effectively evaluating link connectivity. The second deletion unit is used to delete high-priority specific flow table information on the host machine when the second evaluation result indicates that the link connectivity of the network meets the preset link requirements.

7. The apparatus according to claim 5 or 6, characterized in that, The device further includes: The backup module is used to back up and store all the flow table information.

8. The apparatus according to claim 5 or 6, characterized in that, The device further includes: The determination module is used to determine whether the target flow table information exists in all the flow table information; The determining module includes: The first determining unit is specifically used to determine that the target flow table information exists in all flow table information if there is flow table information in all flow table information that does not correspond to the current version number of the controller; The second determining unit is specifically used to determine that the target flow table information does not exist in all the flow table information if all the flow table information corresponds to the current version number of the controller.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Citation Information

Patent Citations

  • Flow table deletion method and device and related equipment

    CN118740767A

  • Flow table updating method and device, network system and electronic equipment

    CN118802743A