Data processing method and device, electronic equipment, and storage medium

Abstract

Embodiments of the present application disclose a data processing method and device, electronic equipment and storage medium, the method comprising: first obtaining a task adjustment request corresponding to an executed route update task, the route update task being used for updating route attribute information corresponding to a target network address set in a target network device; then, finding an updated network address set corresponding to the route update task and having undergone route attribute information updating from a database, and determining a to-be-updated network address set corresponding to the task adjustment request and having to undergo route attribute information updating according to the task adjustment request and the target network address set, so as to determine a to-be-adjusted network address according to the updated network address set and the to-be-updated network address set, thereby adjusting route attribute information of the to-be-adjusted network address in the target network device. The technical solution of the embodiments of the present application can improve the task adjustment efficiency of the route update task, and improve the success rate and accuracy of task adjustment.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a data processing method and apparatus, electronic device, storage medium, and program product. Background Technology

[0002] Routing is a key technology in network communication, determining the transmission path of data packets from their source address to their destination address. To enable route detection, network control, and other functions, route update tasks can be initiated to update the routing attribute information of each network address in network devices.

[0003] In related technologies, after the route update task is executed, the routing attribute information of each network address in the network device corresponding to the route update task can be adjusted based on the request, thereby realizing the adjustment of the route update task. However, the adjustment process takes a long time and the task adjustment efficiency is low. Summary of the Invention

[0004] The embodiments of this application provide a data processing method and apparatus, electronic device, storage medium, and program product, which can improve the task adjustment efficiency of routing update tasks and improve the success rate and accuracy of task adjustments.

[0005] In a first aspect, embodiments of this application provide a data processing method, the method comprising:

[0006] Obtain the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device;

[0007] The database is searched for the set of updated network addresses that have had their routing attribute information updated, corresponding to the routing update task. Based on the task adjustment request and the target network address set, the set of network addresses to be updated for the routing attribute information corresponding to the task adjustment request is determined.

[0008] Based on the updated network address set and the network address set to be updated, the network address to be adjusted is determined, and the routing attribute information of the network address to be adjusted in the target network device is adjusted.

[0009] Secondly, embodiments of this application provide a data processing apparatus, the apparatus comprising:

[0010] The acquisition module is configured to acquire the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device;

[0011] The determination module is configured to search the database for the updated network address set whose routing attribute information has been updated, corresponding to the routing update task, and determine the network address set to be updated whose routing attribute information is to be updated, corresponding to the task adjustment request, based on the task adjustment request and the target network address set.

[0012] The adjustment module is configured to determine the network address to be adjusted based on the updated network address set and the network address set to be updated, and to adjust the routing attribute information of the network address to be adjusted in the target network device.

[0013] Thirdly, embodiments of this application provide an electronic device, including:

[0014] At least one processor;

[0015] A storage device for storing at least one computer program, which, when executed by the at least one processor, causes the electronic device to perform the method described above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor of an electronic device, causes the electronic device to perform the method described above.

[0017] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described above.

[0018] In the technical solution provided by the embodiments of this application, the task adjustment request corresponding to the executed route update task is first obtained. The route update task is used to update the routing attribute information corresponding to the target network address set in the target network device. Then, the updated network address set corresponding to the route update task and whose routing attribute information has been updated is searched from the database. Based on the task adjustment request and the target network address set, the network address set to be updated corresponding to the task adjustment request is determined. Based on the updated network address set and the network address set to be updated, the network address to be adjusted is determined, thereby adjusting the routing attribute information of the network address to be adjusted in the target network device. Compared with related technologies, by storing the updated network address set corresponding to the route update task in the database, the network address to be adjusted can be quickly and accurately determined based on the updated network address set and the network address set to be updated corresponding to the task adjustment request. The routing attribute information of the network address to be adjusted in the target network device can then be adjusted, thereby realizing the task adjustment. This can improve the task adjustment efficiency and success rate, and further improve the task adjustment success rate and accuracy.

[0019] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0020] Figure 1 This is a schematic diagram illustrating an implementation environment as shown in an exemplary embodiment of this application;

[0021] Figure 2 This is a flowchart illustrating a data processing method in an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating a data processing method in an exemplary embodiment of this application;

[0023] Figure 4 This is a flowchart illustrating a data processing method in another exemplary embodiment of this application;

[0024] Figure 5 This is a flowchart illustrating a data processing method in another exemplary embodiment of this application;

[0025] Figure 6 This is a flowchart illustrating a data processing method in another exemplary embodiment of this application;

[0026] Figure 7 This is a schematic diagram illustrating a network segment task and a network segment subtask, as shown in another exemplary embodiment of this application;

[0027] Figure 8 This is a schematic diagram illustrating the processing procedure of a task adjustment request according to an exemplary embodiment of this application;

[0028] Figure 9 This is a schematic diagram illustrating the processing procedure of a task modification request according to an exemplary embodiment of this application;

[0029] Figure 10 This is a schematic diagram illustrating the processing procedure of a retransmission request in an exemplary embodiment of this application;

[0030] Figure 11 This is a schematic diagram illustrating an implementation environment as shown in an exemplary embodiment of this application;

[0031] Figure 12 This is a schematic diagram of the structure of a data processing apparatus shown in an exemplary embodiment of this application;

[0032] Figure 13 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0033] Exemplary embodiments will now be described in a more comprehensive manner with reference to the accompanying drawings. However, the exemplary embodiments can be implemented in various forms and should not be construed as limited to these examples; rather, these embodiments are provided so that this application will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art.

[0034] Furthermore, the features, structures, or characteristics described in this application can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to provide a full understanding of the embodiments of this application. However, those skilled in the art will recognize that when implementing the technical solutions of this application, not all the detailed features in the embodiments may be used, one or more specific details may be omitted, or other methods, elements, devices, steps, etc., may be employed.

[0035] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0036] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0037] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0038] It should also be noted that "multiple" as mentioned in this application refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0039] The technical solutions of the embodiments of this application are described in detail below:

[0040] In related technologies, after a route update task is executed, if an adjustment request for that task is obtained, it is usually necessary to traverse the task body of the route update task based on the adjustment request to determine which network addresses' routing attribute information needs to be adjusted before making the adjustment. This adjustment process is time-consuming and inefficient. Therefore, embodiments of this application provide a data processing method and apparatus, electronic device, storage medium, and program product that can improve the task adjustment efficiency of route update tasks and increase the success rate and accuracy of task adjustments.

[0041] Please see Figure 1 , Figure 1 This is a schematic diagram of an implementation environment involved in this application, which includes a data processing platform 110 and a network device 120.

[0042] The data processing platform 110 can be deployed on terminal devices, servers, business controllers, etc. Terminal devices can include, but are not limited to, mobile phones, tablets, laptops, computers, voice interaction devices, home appliances, vehicle terminals, aircraft, remote driving terminals, etc. Servers can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The business controller is responsible for the specific orchestration of business operations, orchestrating upper-layer business requirements (e.g., plane probing, plane isolation, line isolation, route canary deployment, route suppression, route whitelisting, etc.) into specific tasks. The business controller can support routing protocols for updating routing attribute information. For example, the business controller can support Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), and Intermediate System to Intermediate (ISI) protocols. At least one of the routing protocols such as System.io (IS-IS) is used. No restrictions are placed on the specific form of the terminal equipment, server, and service controller.

[0043] Network device 120 refers to devices in the network, including but not limited to routers, switches, firewalls, bridges, hubs, gateways, etc.

[0044] It should be noted that, Figure 1The number of data processing platforms 110 and network devices 120 is merely illustrative; any number of data processing platforms 110 and network devices 120 can be used as needed.

[0045] In an exemplary embodiment, the data processing method provided in the embodiments of this application can be executed by a data processing platform 110. For example, the data processing platform 110 can obtain a task adjustment request corresponding to an executed route update task; wherein the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device; then, it searches the database for the updated network address set corresponding to the route update task that has undergone routing attribute information updates, and determines the network address set to be updated corresponding to the task adjustment request based on the task adjustment request and the target network address set, so as to determine the network address to be adjusted based on the updated network address set and the network address set to be updated, and adjust the routing attribute information of the network address to be adjusted in the target network device. On the one hand, by storing the updated network address set corresponding to the route update task in the database... This allows for the rapid and accurate identification of network addresses to be adjusted based on the updated network address set and the network address set to be updated corresponding to the task adjustment request. It also enables the adjustment of the routing attributes of these network addresses in the target network device, thereby improving task adjustment efficiency and success rate. Furthermore, based on the updated network address set and the network address set to be updated corresponding to the task adjustment request, it can automatically reconcile and audit whether network address updates were missed during the execution of the routing update task, or whether network addresses outside the target network address set were updated. This allows for adjustments, improving the accuracy of routing update task execution, enhancing network security and stability, and reducing the difficulty of network operation and maintenance.

[0046] The embodiments of this application involve user-related data such as task adjustment requests. When the methods of this application are applied to specific products or technologies, user permission or consent is obtained, and the extraction, use and processing of related data comply with local security standards and local laws and regulations.

[0047] See Figure 2 , Figure 2 This is a flowchart illustrating a data processing method in an exemplary embodiment of this application. The method can be applied to... Figure 1 The implementation environment shown can be composed of Figure 1 The data processing platform 110 in the implementation environment shown is executed.

[0048] like Figure 2As shown, in an exemplary embodiment, the data processing method may include S210-S230, which are described in detail below:

[0049] S210, obtain the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device.

[0050] It should be noted that routing attribute information refers to the routing attributes of a network address, including but not limited to the network address's routing information (e.g., static and dynamic routes), routing priority, and whether it belongs to a routing whitelist. The routing information of a network address is used to indicate the route to send a packet to that network address. Correspondingly, the methods for updating the routing attribute information of a network address include, but are not limited to: reflecting, deleting, or revoking the routing information of the network address in the network device; modifying the routing priority of the network address; and writing / deleting the network address from the routing whitelist.

[0051] The route update task is used to update the routing attribute information of network addresses in network devices. Optionally, the route update task can also be used to update the routing attribute information of the probe destination address in the network plane. It should be noted that, for network domain governance, the network is divided into backbone networks and domain networks. The backbone network is further divided into multiple network planes, and each domain network is also divided into multiple network planes. Plane probing is a route probing method used to probe the network quality of the network plane to be probed. It requires that the probe flow can only be transmitted through the network plane to be probed to the probe destination address corresponding to the network plane to be probed. In one optional example, in order for the network plane to be probed to transmit the probe flow to the probe destination address based on routing information, a route update task can be initiated to reflect the routing information corresponding to the probe destination address in the network device corresponding to the network plane to be probed. In another optional example, the routes published in multiple network planes within the same network are equal-cost multi-path routes. In ECMP routing, if other network planes within the network to which the probed network plane belongs also contain routing information corresponding to the probed destination address, the probe flow will be transmitted through those other network planes to the probed destination address. Therefore, to avoid this situation, a route update task can be initiated to remove the routing information corresponding to the probed destination address of the probed network plane in other network planes. For example, a domain network in a certain area contains network planes 1-8. The probed destination address of network plane 1 is 33.0.1.0 / 25. To transmit probe flows with a destination network address of 33.0.1.0 / 25 only through network plane 1 to test the network quality of network plane 1, a route update task is initiated to remove the routing information for 33.0.1.0 / 25 in network planes 2-8. The network address can be an IP address or a network segment, such as 33.0.1.0 / 25.

[0052] The target network device refers to the network device that needs to update its routing attribute information during the execution of the routing update task. Its types include, but are not limited to, routers, switches, firewalls, bridges, hubs, and gateways. The target network address set contains network addresses that need to have their routing attribute information updated during the execution of the routing update task. The target network address set contains at least one network address, which can be a contiguous network address (i.e., a network segment) or a non-contiguous network address. Furthermore, the routing attribute information update methods corresponding to these at least one network address can be the same; for example, they can all be used to write the corresponding routing information into the network device. Alternatively, the routing attribute information update methods corresponding to these at least one network address can also be different.

[0053] The route update task includes task information such as device indication information and route update indication information. Device indication information indicates how to locate the target network device. This can be the device identifier information of the target network device, allowing direct location of the target network device based on the device identifier, or it can be device attribute information, identifying network devices matching the device attribute information as the target network device. For example, if the goal is to use network devices within the network plane as target network devices, the device indication information could be the device identifier information of the network devices within that network plane, or it could be the plane identifier information of that network plane. This allows locating the corresponding network plane based on the plane identifier information, and then identifying the network devices within that network plane as the target network devices. Route update indication information indicates how to update the routing attribute information of network addresses in the target network address set.

[0054] During the execution of a route update task, the routing attribute information of each network address in the target network address set is updated in the target network device. After the route update task is executed, if adjustments to the route update task are needed, a task adjustment request can be initiated.

[0055] The task adjustment request is used to adjust the route update task, and its types include, but are not limited to, task re-execution requests and task modification requests. The task re-execution request is used to request the re-execution of the route update task. The task modification request is used to request the modification of the route update task, and it contains modification instructions indicating how to modify the route update task. The modification method can be to cancel the update, add an update, etc. Canceling an update means canceling the update of the routing attribute information of some or all network addresses in the target network address set. Adding an update means updating the routing attribute information of network addresses outside the target network address set. For example, if the route update task is used to add routing information for network addresses 1-10 in the target network device, the task adjustment request can be used to delete the routing information for network addresses 1-2 and add routing information for network addresses 11-15 in the target network device.

[0056] S220: Search the database for the set of updated network addresses that have had their routing attribute information updated, corresponding to the routing update task. Based on the task adjustment request and the target network address set, determine the set of network addresses to be updated for the routing attribute information corresponding to the task adjustment request.

[0057] The updated network address set contains at least one updated network address, which refers to a network address whose routing attribute information has been updated. During the execution of a route update task, the updated network addresses corresponding to the route update task are stored in a database. Therefore, the updated network address set can be retrieved from the database. The specific storage method can be flexibly configured according to actual needs. In an optional example, the task identifier corresponding to the route update task can be associated with the updated network address and stored in the database. This allows retrieval of the updated network address set corresponding to the route update task based on the task identifier, where the task identifier can be a task identification number (ID), etc. Optionally, the task information of the route update task can also be stored in the database. Database types include, but are not limited to, MySQL databases, NoSQL databases, and distributed databases. Among them, MySQL is a popular open-source relational database management system; NoSQL, short for Not Only SQL, is a type of non-relational database, including MongoDB, Cassandra, etc. MongoDB is a non-relational database based on distributed file storage, while Cassandra is an open-source distributed NoSQL database system; distributed databases include HBase, TiDB, etc. TiDB is an open-source distributed relational database, while HBase is a distributed, scalable NoSQL database that supports massive data storage.

[0058] The set of network addresses to be updated is the set of network addresses corresponding to the task adjustment request that require updating their routing attribute information. In other words, after adjusting the routing update task according to the task adjustment request, the set of network addresses corresponding to the adjusted routing update task that requires updating its routing attribute information is also the target network address set corresponding to the adjusted routing update task. It can be determined based on the type of task adjustment request and the target network address set. Specifically, if the task adjustment request is a task re-execution request, the target network address set can be directly used as the set of network addresses to be updated. If the task adjustment request is a task modification request, the target network address set of the routing update task can be added or removed according to the modification instructions contained in the task modification request to obtain the set of network addresses to be updated. For example, if the routing update task is used to add routing information for network addresses 1-10 in the target network device, the task adjustment request can be used to delete routing information for network addresses 1-2 and add routing information for network addresses 11-15 in the target network device; then the set of network addresses to be updated would be network addresses 3-15.

[0059] In an optional implementation, after receiving a task adjustment request, to avoid conflicts between the execution of the route update task and the processing of the task adjustment request, the task status of the route update task corresponding to the task adjustment request can be checked first. If the task status is "execution completed," the task adjustment request is responded to. The database is then searched for the updated network address set corresponding to the route update task that has undergone route attribute information updates. Based on the task adjustment request and the target network address set, the network address set to be updated for route attribute information corresponding to the task adjustment request is determined. If the task status is not "execution completed," the task adjustment request is not responded to. In this case, the task adjustment request can be rejected, and a response error message can be sent to the initiator of the task adjustment request. The task status includes not executed, executing, and executed completed, etc. The executed completed status includes executed successfully and executed failed, etc. The database can store the execution status of the route update task. During the response to the task adjustment information, the execution status of the route update task can be changed to "execution in progress."

[0060] S230: Based on the updated network address set and the network address set to be updated, determine the network address to be adjusted, and adjust the routing attribute information of the network address to be adjusted in the target network device.

[0061] By comparing the updated network address set with the network address set to be updated, the network address to be adjusted can be determined. Then, the routing attribute information of the network address to be adjusted is modified in the target network device. The adjustment methods include, but are not limited to, revoking the update and updating.

[0062] Optionally, after successfully adjusting the routing attribute information of the network address to be adjusted in the target network device, the target network address set of the routing update task can be updated according to the network address set to be updated, so that the updated target network address set matches the network address set to be updated.

[0063] exist Figure 2 In the illustrated embodiment, by storing the updated network address set corresponding to the route update task in the database, the network address to be adjusted can be quickly and accurately determined based on the updated network address set and the network address set to be updated corresponding to the task adjustment request. The routing attribute information of the network address to be adjusted in the target network device can then be adjusted, thereby realizing the task adjustment. This can improve the efficiency and success rate of task adjustment, and further improve the success rate and accuracy of task adjustment.

[0064] In one exemplary embodiment, see Figure 3 , Figure 3 Is Figure 2 The flowchart illustrates a data processing method proposed based on the given information. This method can be applied to... Figure 1The implementation environment shown can be composed of Figure 1 The data processing platform 110 in the implementation environment shown is executed.

[0065] like Figure 3 As shown, S230 may include S310-S330, which are described in detail below:

[0066] S310: From the updated network address set, search for network addresses not included in the network address set to be updated to obtain the first network address to be adjusted; and from the network address set to be updated, search for routing information not included in the updated network address set to obtain the second network address to be adjusted.

[0067] The first network address exists in the updated network address set but not in the network address set to be updated. Therefore, in the route update task before adjustment, the routing attribute information of the first network address needs to be updated, while in the route update task after adjustment, the routing attribute information of the first network address does not need to be updated.

[0068] The second network address exists in the set of network addresses to be updated, but not in the set of network addresses that have already been updated. Therefore, in the route update task before adjustment, it is not necessary to update the routing attribute information of the second network address, but in the route update task after adjustment, it is necessary to update the routing attribute information of the second network address.

[0069] S320: Locate the overlapping network addresses between the updated network address set and the network address set to be updated to obtain the third network address to be adjusted.

[0070] The third network address exists in both the updated network address set and the network address set to be updated. Therefore, in both the pre-adjustment and post-adjustment route update tasks, it is necessary to update the routing attribute information of the first network address.

[0071] It should be noted that the terms "first," "second," and "third" in "first network address," "second network address," and "third network address" are only used to distinguish the categories of network addresses and are not used to limit the number or order of network addresses.

[0072] S330: In the target network device, the update of the routing attribute information of the first network address is cancelled, and the routing attribute information of the second network address is updated in the target network device, and the routing attribute information of the third network address is updated again.

[0073] For the first network address, since its routing attribute information has already been updated in the previous routing update task, and its routing attribute information does not need to be updated in the subsequent routing update task, the update of the network attribute information of the first network address is revoked in the target network device. The specific update and revocation methods can be flexibly set according to actual needs. In an optional example, if the update method is to reflect the routing information of the network address, then the revocation method is to delete the routing information of the network address.

[0074] For the second network address, since its routing attribute information was not updated in the previous routing update task, but is required to be updated in the subsequent routing update task, the routing attribute information of the second network address needs to be updated in the target network device. The update method can be obtained from the task adjustment request. In other words, the second network address is a newly added network address that requires routing attribute information updates.

[0075] For the third network address, since its routing attribute information has already been updated in the previous routing update task, and the routing attribute information still needs to be updated in the subsequent routing update task, the routing attribute information of the third network address can be updated again in the target network device. The update method can be obtained from the task information of the routing update task.

[0076] Specifically, the routing attribute information of the second and third network addresses can be updated after the update of the routing attribute information of the first network address is successfully revoked; alternatively, the update of the routing attribute information of the first network address can be revoked in the target network device after the update of the routing attribute information of the second and third network addresses is successful; or, the revocation of the update of the routing attribute information of the first network address can be performed simultaneously with the update of the routing attribute information of the second and third network addresses.

[0077] In an optional implementation, considering that the routing attribute information of the third network address has already been updated in the routing update task before adjustment, if the task adjustment request is not a task re-execution request, the third network address does not need to be searched. Instead, the routing attribute information of the first network address is undoed and the routing attribute information of the second network address is updated, thereby saving processing resources and simplifying the processing logic. If the task adjustment request is a task re-execution request, considering that the task re-execution request wants to re-execute the routing update task, even if the routing attribute information of the third network address has already been updated in the routing update task before adjustment, the third network address can still be searched to update the routing attribute information of the third network address again in the target network device, thereby ensuring different needs and avoiding errors or failures in the execution of the routing update task.

[0078] In an optional implementation, after successfully revoking the update of the routing attribute information of the first network address, the first network address can be deleted from the set of updated network addresses contained in the database; after successfully updating the routing attribute information of the second network address, the second network address can be added to the set of updated network addresses contained in the database, thereby updating the set of updated network addresses corresponding to the routing update task and adjusting the routing update task.

[0079] It should be noted that, Figure 3 For specific implementation details of S210-S220 shown, please refer to Figure 2 S210-S220 shown will not be described again here.

[0080] exist Figure 3 In the illustrated embodiment, in the target network device, for a first network address that is included in the updated network address set but not in the network address set to be updated, the update of its routing attribute information is revoked; for a second network address that is not included in the updated network address set but is included in the network address set to be updated, its routing attribute information is updated; and for a third network address that is included in both the updated network address set and the network address set to be updated, the routing attribute information is re-updated, thereby improving the success rate and accuracy of task adjustment.

[0081] In one exemplary embodiment, see Figure 4 , Figure 4 Is Figure 3 The flowchart illustrates a data processing method proposed based on the given information. This method can be applied to... Figure 1 The implementation environment shown can be composed of Figure 1 The data processing platform 110 in the implementation environment shown is executed.

[0082] like Figure 4 As shown, if the target network device includes network devices that match the device attribute information in the routing update task, S330 can include S410-S430, as detailed below:

[0083] S410, Obtain a first set of network devices; wherein the first set of network devices includes network devices whose device attribute information is matched during the execution of the route update task.

[0084] It should be noted that the route update task may include device attribute information to indicate how to locate the target network device. This device attribute information refers to the device attributes that the target network device must possess. Its specific content can be flexibly set according to actual needs. In one optional example, the device attribute information can be plane identification information, used to identify network devices contained in the network plane corresponding to the plane identification information as target network devices. In another optional example, the device attribute information can be a region, used to identify network devices located within that region as target network devices. In yet another optional example, the device attribute information can be user identification information, used to identify network devices belonging to that user as target network devices. For example, if the user is an enterprise user, then the network devices leased by that enterprise can be used as target network devices.

[0085] During the execution of the route update task, device attribute information is parsed from the route update task, and then the network devices that match the device attribute information are found to obtain the first network device set. Then, the route attribute information corresponding to the target network address set is updated for each network device in the first network device set. The first network device set can be associated with the task identifier information of the route update task and stored in the database so that the first network device set can be found from the database.

[0086] S420, among the network devices included in the first set of network devices, cancel the update of the routing attribute information of the first network address.

[0087] Since the routing attribute information of the first network address was updated only in each network device included in the first network device set during the execution of the routing update task, the update of the routing attribute information of the first network address was revoked only in each network device included in the first network device set.

[0088] S430: Locate the network device that matches the device attribute information to obtain the second network device set, and update the routing attribute information of the second network address in each network device included in the second network device set, and update the routing attribute information of the third network address again.

[0089] Considering the time difference between the execution time and acquisition time of the route update task, which leads to changes such as the addition or removal of network devices matching device attribute information in the network, in order to update the routing attribute information of the second and third network addresses in newly added network devices and save the resources consumed in searching for removed network devices, after receiving the task adjustment request, the network devices currently matching the device attribute information are searched to construct a second network device set. Then, the routing attribute information of the second network address is updated in each network device included in the second network device set, and the routing attribute information of the third network address is also updated in each network device included in the second network device set. Optionally, after updating the routing attribute information in each network device included in the second network device set, the first network device set stored in the database can be updated based on the second network device set, so that the updated first network device set matches the second network device set.

[0090] In an optional implementation, the process of finding network devices that currently match the device attribute information to obtain a second set of network devices, and updating the routing attribute information of the second network address in each network device included in the second set of network devices, and then updating the routing attribute information of the third network address again, may include:

[0091] If the task adjustment request is a task re-execution request to request the re-execution of the route update task, then find the network device that matches the device attribute information to obtain the second set of network devices, and update the routing attribute information of the second network address and the third network address in each network device included in the second set of network devices;

[0092] If the task adjustment request is not a task re-execution request, then the routing attribute information of the second network address is updated in each network device included in the first network device set.

[0093] In other words, upon receiving a task adjustment request, it can first be determined whether the request is a task re-execution request. If it is, the focus is on re-executing the route update task. Therefore, it is necessary to look up the third network address and the second set of network devices. Then, in each network device included in the first set of network devices, the update of the routing attribute information for the first network address is cancelled, and in each network device included in the second set of network devices, the routing attribute information for the second network address is updated. The routing attribute information for the third network address is then updated again. If the task adjustment request is not a task re-execution request, the focus is on modifying the route update task. Therefore, it is not necessary to look up the third network address and the second set of device identifiers. The update of the routing attribute information for the first network address can be cancelled directly in each network device included in the first set of network devices, and the routing attribute information for the second network address can be updated in each network device included in the first set of network devices. This saves resources and improves processing efficiency. It should be noted that, in other embodiments, if the task adjustment request is not a task re-execution request, the update of the routing attribute information of the first network address can be cancelled in each network device included in the first network device set, and the routing attribute information of the second network address can be updated in each network device included in the second network device set.

[0094] In an optional implementation, the routing update task can be used to reflect the routing information corresponding to each network address in the target network address set to the target network device. The device attribute information includes plane identification information. That is, the target network device is a network device contained in the network plane corresponding to the plane identification information. The routing update task is used to reflect the routing information corresponding to each network address in the target network address set to the network device contained in the network plane corresponding to the plane identification information. Under this condition, the process of canceling the update of the routing attribute information of the first network address in each network device contained in the first network device set in S420 can include: canceling the routing information of the first network address in each network device contained in the first network device set.

[0095] Correspondingly, in S430, the process of searching for network devices that match the current device attribute information to obtain a second set of network devices, and updating the routing attribute information of the second network address in each network device included in the second set of network devices, and updating the routing attribute information of the third network address again includes:

[0096] Find the network devices currently included in the network plane corresponding to the plane identification information to obtain the second set of network devices;

[0097] Among the network devices included in the second set of network devices, routing information for the second network address and routing information for the third network address are reflected.

[0098] In this context, the network devices in the first set of network devices are those network devices contained in the network plane corresponding to the plane identification information found during the execution of the routing update task. Methods for revoking the routing information of the first network address include, but are not limited to: deleting the routing information of the first network address from the first set of network devices, reducing the priority of the routing information of the first network address, hiding the routing information of the first network address, and increasing the overhead of the routing information of the first network address. Thus, if other network devices contain equivalent routing information for the first network address before revocation, after revoking the routing information of the first network address in each network device in the first set of network devices, since there is no routing information for the first network address in each network device in the first set of network devices, or even if there is routing information for the first network address, the overhead of such routing information is too high, therefore, packets with the first network address as the target network address will not be transmitted through each network device in the first set of network devices, but rather through other network devices.

[0099] Optionally, before searching the second set of network devices, it can be determined whether the task adjustment request is a task re-execution request. If so, the second set of network devices is searched, and the routing information of the second network address and the routing information of the third network address are reflected in each network device included in the second set of network devices. If not, the routing information of the second network address is reflected only in each network device included in the first set of network devices.

[0100] In this embodiment, a route update task can be used to input routing information for the destination address to be probed into the network plane to be probed. Correspondingly, the route update task can include the plane identification information of the network plane to be probed, and the target network address set includes the destination address to be probed. A task adjustment request can be used to cancel the routing information for the destination address to be probed in the network plane to be probed. For example, in a domain network containing network plane a and network plane b, in order to probe the network quality of network plane a through a probe flow with a destination IP address belonging to 33.0.1.0 / 25, a route update task can be initiated to... The network devices in network plane a reflect the routing information of 33.0.1.0 / 25. Then, based on the routing information of 33.0.1.0 / 25, a probing of network plane a is performed. After the probing is completed, if it is necessary to probe the network quality of network plane b through a probe flow with a destination IP address belonging to 33.0.1.0 / 25, a task adjustment request can be initiated. This will delete the routing information of 33.0.1.0 / 25 from the network devices in network plane a, so that probe flows with a destination IP address belonging to 33.0.1.0 / 25 will no longer be transmitted through the probe network plane a.

[0101] Optionally, after successfully revoking the update of the routing attribute information of the first network address, the first network address can be deleted from the updated network address set; after successfully updating the routing attribute information of the second network address, the second network address can be added to the updated network address set; after successfully updating the routing attribute information of the second network address and the third network address in each network device included in the second network device set, the first network device set can be updated according to the second network device set, so that the updated first network device set matches the second network device set.

[0102] It should be noted that, Figure 4 For specific implementation details of S210-S220 shown, please refer to Figure 2 S210-S220 shown, Figure 4 For specific implementation details of S310-S320 shown, please refer to Figure 3 S310-S320 shown will not be described again here.

[0103] exist Figure 4In the illustrated embodiment, the update of the routing attribute information of the first network address is revoked in each network device included in the first network device set. In each network device included in the second network device set, the routing attribute information of the second network address is updated, and the routing attribute information of the third network address is updated again. The first network device set includes network devices that match the device attribute information found during the execution of the routing update task. The second network device set includes network devices that match the device attribute information found after receiving the task adjustment request. This allows for accurate revocation of the update of the routing attribute information of the first network address in network devices that have already undergone routing attribute information updates, improving the revocation success rate. Furthermore, even if network devices that match the device attribute information are added or removed after the routing update task is executed, the update of the routing attribute information of the second and third network addresses can be performed in the newly added network devices, but not in the removed network devices. This solves the problem of missed or excessive updates of network devices during the task adjustment process caused by the scaling up or down of network devices after the routing update task is executed.

[0104] In one exemplary embodiment, see Figure 5 , Figure 5 Is Figure 2 The flowchart illustrates a data processing method proposed based on the given information. This method can be applied to... Figure 1 The implementation environment shown can be composed of Figure 1 The data processing platform 110 in the implementation environment shown is executed.

[0105] like Figure 5 As shown, S230 may include S510-S530, which are described in detail below:

[0106] S510, based on the updated network address set and the network address set to be updated, determine the network address to be adjusted.

[0107] The types of network addresses to be adjusted include a first network address, a second network address, and a third network address. The specific methods for determining the first network address, the second network address, and the third network address can be found in the description of the foregoing embodiments, and will not be repeated here.

[0108] In an optional implementation, if the task adjustment request is a task re-execution request, the network address to be adjusted includes a first network address, a second network address, and a third network address; if the task adjustment request is not a task re-execution request (for example, the task adjustment request is a task modification request), the network address to be adjusted includes the first network address and the second network address.

[0109] S520 generates a route adjustment task based on the network address to be adjusted.

[0110] The routing adjustment task includes the network address to be adjusted and the corresponding adjustment method for the network address. The adjustment method includes, but is not limited to, cancel update, update, and re-update. For example, for the first network address, a cancel update task is generated to cancel the update of the routing attribute information of the first network address in the target network device; for the second network address, a new update task is generated to update the routing attribute information of the second network address in the target network device; and for the third network address, a re-update task is generated to re-update the routing attribute information of the third network address in the target network device.

[0111] Optionally, the routing adjustment task may also include device identification information to locate the target network device based on the device identification information and perform the routing adjustment task in the target network device to adjust the routing attribute information of the network address to be adjusted in the target network device.

[0112] If the device indication information contained in the route update task is device identification information, then the device identification information contained in the route update task can be directly added to the cancel update task, add update task, and re-update task.

[0113] If the device indication information included in the routing update task is device attribute information, in one optional example, the device identifier information of each network device in the first network device set is added to the undo update task, the add update task, and the re-update task, thereby executing the undo update task, the add update task, and the re-update task in each network device in the first network device set. In another optional example, the device identifiers of each network device in the first network device set can be added to the undo update task, thereby executing the undo update task in each network device in the first network device set; the device identifiers of each network device in the second network device set can be added to the add update task and the re-update task, thereby executing the add update task and the re-update task in each network device in the second network device set. In another optional example, if the task adjustment request is a task re-execution request, then a cancel update task, a new update task, and a re-update task are generated, and the device identification information of each network device in the first network device set is added to the cancel update task, and the device identification information of each network device in the second network device set is added to the new update task and the re-update task; if the task adjustment request is not a task re-execution request, then a cancel update task and a new update task are generated, and the device identification information of each network device in the first network device set is added to the cancel update task and the new update task.

[0114] In an optional implementation, to improve the success rate of route adjustment tasks, the process of generating route adjustment tasks based on the network address to be adjusted may include:

[0115] If the number of network addresses to be adjusted is greater than the number threshold, then the network addresses to be adjusted are grouped according to the number threshold to obtain at least two network address groups.

[0116] Generate at least two routing adjustment tasks corresponding to each network address group.

[0117] To avoid crashes and errors caused by adjusting the routing attributes of a large number of network addresses during the execution of a single routing adjustment task, it's advisable to first determine if the number of network addresses to be adjusted exceeds a threshold. If so, the network addresses are grouped, with each group containing network addresses less than or equal to the threshold. Then, a routing adjustment task is generated for each network address group, where each task adjusts the routing attributes of the network addresses within that group. The specific value of the threshold can be flexibly set according to actual needs.

[0118] In this process, considering that different types of network addresses require different adjustment methods, to simplify the adjustment process, for each type of network address, if the number of such network addresses exceeds a threshold, then the network addresses of that type are grouped according to the threshold, resulting in at least two network address groups. A routing adjustment task is then generated for each network address group. For example, for a first network address, if the number of first network addresses exceeds the threshold, the first network address can be grouped into at least two network address groups. Each network address group contains at least two first network addresses, and the number of first network addresses in each group is less than or equal to the threshold. Then, a reversal update task is generated for each network address group.

[0119] Optionally, during the grouping of network addresses, consecutive network addresses of the same type can be grouped together.

[0120] S530 adds the route adjustment task to the task message queue so that the target route reflector connected to the target network device can obtain the route adjustment task from the task message queue and adjust the routing attribute information of the network address to be adjusted in the target network device according to the route adjustment task.

[0121] Task message queues are message queues used to cache routing adjustment tasks. Their types include, but are not limited to, Kafka, RabbitMQ, and ActiveMQ. Among them, Kafka is an open-source distributed event streaming platform that supports publish / subscribe patterns; RabbitMQ is an open-source message broker software that implements message queue functionality based on the AMQP protocol; and ActiveMQ is an open-source message middleware.

[0122] A route reflector (RR) is a type of router configured to reflect routing information. Optionally, a route reflector can be deployed in a controller that supports routing protocols, such as a BGP controller (e.g., a GOBGP controller), an OSPF controller, or an IS-IS controller. The controller then connects to network devices as a route reflector, updating the routing attribute information of network addresses in the connected network devices. GoBGP is an open-source BGP implementation written in Go.

[0123] A network deploys numerous route reflectors to connect to different network devices. Each route reflector reflects routing information back to its connected network device. Connection methods between the route reflector and the network device include, but are not limited to, Internal Border Gateway Protocol (iBGP), OSPF, and IS-IS connections. A route adjustment task is added to the task message queue. The route reflector connected to the target network device (i.e., the target route reflector) retrieves the route adjustment task from the task message queue and executes it to adjust the routing attribute information of the network address to be adjusted in the target network device. In other words, the adjustment of routing attribute information is performed by the target route reflector. Optionally, if the route adjustment task includes device identification information, the target route reflector can locate the corresponding target network device based on the device identification information and adjust the routing attribute information of the network address to be adjusted within the target network device.

[0124] To improve the success rate of updating and adjusting route attribute information, in an optional implementation, the process of adding the route adjustment task to the task message queue may include:

[0125] From the route reflector group corresponding to the network device set to which the target network device belongs, find the target route reflector that is connected to the target network device; the route reflector group corresponding to different network device sets is different.

[0126] Locate the target task message queue corresponding to the set of network devices to which the target network device belongs; note that different sets of network devices correspond to different task message queues.

[0127] Add the route adjustment task to the target task message queue so that the target route reflector can retrieve the route adjustment task from the target task message queue.

[0128] In this approach, network devices can be divided into at least two sets of network devices. Different sets of network devices correspond to different route reflector groups and task message queues, ensuring that the updates of routing attribute information for network devices in different sets are relatively independent. This means that even if a route reflector in one set fails, it will not affect the updates of routing attribute information in other sets of network devices. Alternatively, network devices within the same network plane can be grouped into the same set of network devices. For example, the network plane can be divided into multiple plane groups, and the network devices within the same plane group can be considered as a single set of network devices. For instance, network planes 1-4 can correspond to route reflector set 1 and task message queue 1. The network devices in network planes 1-4 are connected to the route reflectors in route reflector set 1, and the tasks corresponding to the network devices in network plane 104 are added to task message queue 1. Network planes 5-8 can correspond to route reflector set 2 and task message queue 2.

[0129] In an optional implementation, the types of route adjustment tasks include undo update tasks and other adjustment tasks besides undo update tasks (e.g., add update tasks, re-update tasks). To avoid dirty data, undo update tasks can be executed first, and other adjustment tasks can be executed after the undo update tasks are successfully executed. Correspondingly, the route adjustment tasks are added to the task message queue so that the target route reflector connected to the target network device can obtain the route adjustment tasks from the task message queue. The process of adjusting the routing attribute information of the network address to be adjusted in the target network device according to the route adjustment tasks may include:

[0130] Obtain the undo update task from the route adjustment task; the undo update task is generated based on the first network address to be adjusted, which is a network address that is included in the set of updated network addresses but not included in the set of network addresses to be updated.

[0131] Add the undo update task to the task message queue so that the target route reflector can retrieve the undo update task from the task message queue and, based on the undo update task, undo the update of the routing attribute information of the first network address in the target network device.

[0132] If the undo update task is detected as successfully executed, all other adjustment tasks in the route adjustment task, excluding the undo update task, are added to the task message queue so that the target route reflector can retrieve and execute the other adjustment tasks from the task message queue.

[0133] In other words, the undo update task is first added to the task message queue to be executed. Only after the undo update task is successfully executed will other adjustment tasks, such as add update tasks and re-update tasks, be added to the task message queue. After adding the undo update task to the task message queue, if the undo update task fails to execute, a task adjustment request failure response message can be generated to inform the object that the task adjustment request failed.

[0134] The specific method for detecting whether the reversal update task has been successfully executed can be flexibly set according to actual needs. In one optional implementation, after the target route reflector successfully reverses the update of the routing attribute information of the first network address, it can generate execution success information to indicate that the reversal update task has been successfully executed. Therefore, if the execution success information is obtained, it can be determined that the reversal update task has been successfully executed. In another optional implementation, if the number of target route reflectors includes at least two, that is, if the target network device is connected to at least two target route reflectors, in order to improve the task execution success rate, each target route reflector will obtain the reversal update task from the task message queue and execute the reversal update task to reverse the update of the routing attribute information of the first network address in the target network device. Under this condition, the data processing method may further include:

[0135] Retrieve the execution success information corresponding to the undo update task from the feedback message queue; the execution success information is generated after the target route reflector successfully undoes the update of the route attribute information of the first network address.

[0136] If the number of successful execution messages obtained matches the number of target route reflectors, then the undo update task is considered to have been successfully executed.

[0137] The feedback message queue is used to cache the execution result information of the task. After each target route reflector successfully cancels the update of the routing attribute information of the first network address, it will generate the execution success information corresponding to the cancellation update task, indicating that the target route reflector has successfully executed the cancellation update task, and add it to the feedback message queue. If the number of execution success information corresponding to the cancellation update task obtained from the feedback message queue matches the number of target route reflectors, it indicates that each target route reflector has successfully executed the cancellation update task. Therefore, the cancellation update task is determined to have been executed successfully. For example, if there are 2 target route reflectors, after obtaining 2 execution success information of cancellation update tasks, the cancellation update task is determined to have been executed successfully.

[0138] It should be noted that the method for determining whether other adjustment tasks or route update tasks have been executed successfully is similar to the method for determining whether undo update tasks have been executed successfully, and will not be elaborated here.

[0139] In another optional implementation, if the route adjustment task includes a rollback update task and other adjustment tasks, the rollback update task and other adjustment tasks can be executed in parallel. Correspondingly, the process of adding the route adjustment task to the task message queue may include:

[0140] Add the undo update task and other adjustment tasks included in the route adjustment task to the task message queue; wherein, the undo update task is used to undo the update of the route attribute information of the first network address to be adjusted in the target network device, the first network address being a network address included in the set of updated network addresses but not included in the set of network addresses to be updated.

[0141] Store the task adjustment information corresponding to the task adjustment request;

[0142] If any of the undo update task or other adjustment tasks fails, the routing attribute information in the target network device is rolled back based on the task adjustment information.

[0143] In other words, without specifying the execution order of the undo update task and other adjustment tasks, all undo update tasks and other adjustment tasks are added to the task message queue. This allows the target route reflector to retrieve and execute undo update tasks and other adjustment tasks from the task message queue, enabling parallel execution of these tasks and improving task adjustment efficiency. In this case, to avoid dirty data, task adjustment information corresponding to the task adjustment request can be stored. This task adjustment information describes how to adjust the route update task and may include task information corresponding to the undo update task and other adjustment tasks respectively. Then, if any task in the undo update task or other adjustment task fails, a rollback can be performed based on the task adjustment information, thereby rolling back the routing attribute information in the target network device to the state before the execution of the undo update task and other adjustment tasks.

[0144] It should be noted that, Figure 5 For specific implementation details of S210-S220 shown, please refer to Figure 2 S210-S220 shown will not be described again here.

[0145] exist Figure 5In the illustrated embodiment, adding the route adjustment task to the task message queue and having the route reflector retrieve and execute the route adjustment task through the task message queue can improve the success rate of task adjustment. Furthermore, by using the task message queue, the generation process and execution process of the route adjustment task are decoupled, reducing the probability of the task adjustment process crashing.

[0146] In one exemplary embodiment, see Figure 6 , Figure 6 Is Figure 2 The flowchart illustrates a data processing method proposed based on the given information. This method can be applied to... Figure 1 The implementation environment shown can be composed of Figure 1 The data processing platform 110 in the implementation environment shown is executed.

[0147] like Figure 6 As shown, before searching the database for the updated network address set whose route attribute information has been updated in S220, the data processing method may also include S610-S620, which are described in detail below:

[0148] S610: If a route update task is obtained, the routing attribute information corresponding to each network address in the target network address set of the target network device is updated according to the route update task.

[0149] Routing update tasks can be initiated by operations and maintenance personnel. For a detailed description of routing update tasks, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0150] After obtaining the route update task, it can be executed, updating the routing attribute information corresponding to each network address in the target network address set within the target network device. The route update task may include device indication information, which is used to locate the target network device, and then update the routing attribute information corresponding to each network address in the target network address set within that target network device. Optionally, the device indication information can be device attribute information. By searching for network devices that match the device attribute information, a first set of network devices is obtained, and then the routing attribute information corresponding to each network address in the target network address set is updated within each network device included in the first set.

[0151] Optionally, the route update task can be executed by the data processing platform. Alternatively, the route update task can be executed by the target route reflector. Under this condition, the specific methods for updating the routing attribute information corresponding to each network address in the target network address set of the target network device according to the route update task include, but are not limited to, the following two methods:

[0152] The first method involves adding the route update task to the task message queue, so that the target route reflector can obtain the route update task from the task message queue and execute the route update task to update the routing attribute information corresponding to each network address in the target network address set in the target network device.

[0153] The second approach, considering the large number of network addresses in the target network address set, can improve the task execution success rate by checking if the number of network addresses in the target network address set exceeds a threshold. If the number exceeds the threshold, the route update task is split into at least two route update subtasks based on the threshold. Each route update subtask is added to a task message queue, allowing the target route reflector to retrieve and execute the subtask. Each route update subtask corresponds to a subset of the target network address set and is used to update the routing attribute information of the network addresses contained in that subset. The subsets corresponding to at least two route subtasks constitute the target network address set.

[0154] S620: Create a database table corresponding to the route update task in the database, and add the network address corresponding to the route update task and whose route attribute information has been updated to the database table.

[0155] To record the updated network addresses of route update tasks, a database table corresponding to the route update task can be created in the database, and the updated network addresses of the route update task can be added to this database table.

[0156] Optionally, the database table for the route update task may also contain task information for the route update task, such as task identification information, target network address set, device indication information, and first network device set.

[0157] It should be noted that, Figure 6 For specific implementation details of S210-S230 shown, please refer to Figure 2 S210-S230 shown will not be described again here.

[0158] exist Figure 6 In the illustrated embodiment, a database table corresponding to the route update task is created in the database to store the network addresses corresponding to the route update task and whose route attribute information has been updated. This allows the corresponding database table to be quickly found during the task adjustment process, thereby finding the corresponding set of updated route addresses and improving the efficiency of task adjustment.

[0159] In an exemplary embodiment, to better understand the present invention, the example described herein is a network segment task used to reflect routing information of a target probe network segment in a network device contained in the target network plane. Here, the probe network segment refers to the network segment that serves as the target address for probe, and the routing information of the probe network segment is probe routing information used for plane probes, etc.

[0160] The processing of network segment tasks can include steps 1.1-1.5, which are detailed below:

[0161] Step 1.1: The service controller obtains network segment tasks.

[0162] Users (e.g., operations and maintenance personnel) can initiate network segment tasks to the service controller. These tasks contain routing information for at least two target probe network segments, as well as plane identification information (used to indicate the location of the corresponding target network plane). Optionally, network segment tasks can be used to update routing information for tens of thousands of target probe network segments.

[0163] Step 1.2: The service controller generates at least two sub-tasks for the network segment based on the network segment task.

[0164] The service controller detects the number of target probe network segments corresponding to a network segment task. If the number of target probe network segments is greater than a threshold, multiple network segment sub-tasks are generated. Specifically, if a network segment task contains routing information for M target probe network segments, Q network segment sub-tasks are generated, where Q = ceil(M ÷ N), N is the threshold, and ceil is the floor function. This distributes the routing information of the M target probe network segments among the Q network segment sub-tasks. The distribution method can be equal, meaning each network segment sub-task corresponds to the same number of probe network segments; or, the routing information of the M target probe network segments can be first obtained to generate routing information for N target probe network segments, and then network segment sub-tasks can be generated. If the remaining number of target probe network segments is less than N, then a single network segment sub-task is generated based on the routing information of the remaining target probe network segments. The value of N can be 100, 200, etc. As shown in Figure 7, in an optional example, a network segment task includes a task ID, and the target probe network segment set corresponding to the network segment task contains M target probe network segments. The network segment subtask contains the task ID of the subtask and the routing information of N target probe network segments. Therefore, the ratio between the number of network segment tasks and the number of target probe network segments is 1:M, the ratio between the number of target probe network segments and the number of network segment subtasks is N:1, and the ratio between the number of network segment tasks and the number of target probe network segments is N:M.

[0165] The service controller can also obtain plane identification information from the network segment task, find the network devices contained in the target network plane corresponding to the plane identification information, obtain the first network device set, and add the device identification information of each network device in the first network device set to each network segment subtask. Thus, according to the network segment subtask, the routing information of the target probe network segment contained in the first network device set is reflected in each network device of the network segment subtask.

[0166] Step 1.3: The business controller adds the network segment subtask to the task message queue.

[0167] Step 1.4: The BGP controller retrieves the network segment subtask from the task message queue and executes it.

[0168] After adding the network segment subtask to the task message queue, the BGP controller retrieves the network segment subtask from the task message queue and executes it to reflect the routing information of the probe network segment contained in the network segment subtask to the network device corresponding to the device identification information contained in the subtask.

[0169] Step 1.5: The service controller stores the probed network segments corresponding to the network segment tasks in the database based on the execution results of the network segment subtasks.

[0170] A probed network segment refers to a probed network segment that has already reflected routing information in the corresponding network devices. After receiving a network segment task, the service controller can create a database table corresponding to the network segment task. The database table can contain the task ID of the network segment task, and then add the information of the probed network segment to the database table according to the execution result of the network segment subtask.

[0171] The business controller can obtain the execution result information of the network segment subtask from the feedback message queue. If it is determined that the network segment subtask was successfully executed based on the execution result information, the target probe network segment corresponding to the network segment subtask will be stored as a probe network segment in the database table.

[0172] Optionally, the database table may also store the task status of the network segment task, the device identification information of each network device in the first network device set, the task ID and task status of each network segment subtask, and the target detection network segment set corresponding to the network segment task.

[0173] Then, the user can initiate a task adjustment request, where see [link to relevant documentation]. Figure 8 As shown, the process for handling a task adjustment request includes steps S801-S806, which are detailed below:

[0174] S801, the business controller receives a task adjustment request.

[0175] Users can initiate task adjustment requests to the business controller.

[0176] S802, the service controller parses the set of probe network segments to be sent.

[0177] Based on the task adjustment request, the set of probe network segments to be issued was determined.

[0178] The set of probe segments to be deployed contains probe segments that need to be deployed. These probe segments are those corresponding to the task adjustment request and whose routing information needs to be transmitted to the corresponding network devices. Specifically, the target probe segment set corresponding to the segment task can be found in the database table, and the target probe segment set can be adjusted according to the task adjustment request to obtain the set of probe segments to be deployed.

[0179] S803, the service controller retrieves the set of network segments that have been sent for probe from the database.

[0180] Based on the task ID of the network segment task contained in the task adjustment request, the database table corresponding to the task ID is searched from the database, and the probe network segments have been sent from the database table to obtain the set of probe network segments.

[0181] S804, the service controller generates deletion tasks, re-deployment tasks, and new tasks based on the already deployed probe network segment set and the probe network segment set to be deployed.

[0182] Specifically, based on the set of probe segments already issued and the set of probe segments to be issued, the following are determined: probe segments to be deleted (corresponding to the first network address), probe segments to be added (corresponding to the second network address), and probe segments to be reissued (corresponding to the third network address). Deleting a probe segment refers to a probe segment that exists in the set of issued probe segments but not in the set of probe segments to be issued; adding a probe segment refers to a probe segment that exists in the set of probe segments to be issued but not in the set of issued probe segments; and reissuing a probe segment refers to a probe segment that overlaps between the set of issued probe segments and the set of probe segments to be issued.

[0183] The delete task (corresponding to the undo update task) is used to instruct the network devices included in the target network plane to revoke (e.g., delete) the routing information of the deleted probe network segment. The add task (corresponding to the add update task) is used to instruct the network devices included in the target network plane to reflect the routing information of the added probe network segment. The redistribution task (corresponding to the redistribution update task) is used to instruct the network devices included in the target network plane to reflect the redistribution routing information of the probe network segment.

[0184] In S805, the business controller adds the generated task to the task message queue.

[0185] Add the generated deletion task, reissue task, and new task to the task message queue. You can add the deletion task to the task message queue first, and if the deletion task is executed successfully, then add the reissue task and new task to the task message queue.

[0186] In S806, the BGP controller retrieves tasks from the task message queue and executes them.

[0187] The BGP controller retrieves deleted tasks, reassigned tasks, and new tasks from the task message queue and executes them.

[0188] Optionally, task adjustment requests can be categorized into resubmission requests (i.e., task re-execution requests) and task modification requests. The processing procedures for resubmission requests and task modification requests differ; see [link to relevant documentation]. Figure 9 As shown, the process for handling a task modification request includes steps S901-S922, which are detailed below:

[0189] S901, the business controller receives a task modification request.

[0190] The service controller can provide a task modification interface. Users can call the task modification interface to send a task modification request to the service controller for a network segment task. The task modification request includes the task ID of the network segment task to be modified and the modification method.

[0191] S902, the service controller queries the database for task information corresponding to the network segment task.

[0192] The database stores database tables corresponding to network segment tasks. Based on the task ID of the network segment task included in the task modification request, the corresponding database table can be retrieved from the database, and the task information of the corresponding network segment task can be found.

[0193] S903 If not found, the business controller returns an error message and exits.

[0194] If no corresponding task information is found in the database, an error is reported to the user, and the user is logged out.

[0195] S904, the service controller parses out the set of probe network segments to be distributed based on the task modification request.

[0196] If the task information for the corresponding network segment task is found in the database, and the task status is either successful or failed, then the target probe network segment for the network segment task is retrieved from the database, resulting in a target probe network segment set. Based on the task modification request, this target probe network segment set is modified to obtain the probe network segment set to be deployed. Specifically, if the task modification request indicates that the routing information for the first probe network segment needs to be removed and the routing information for the second probe network segment needs to be added in the network devices included in the corresponding network plane, then the first probe network segment is deleted and the second probe network segment is added to the target probe network segment set, resulting in the probe network segment set to be deployed.

[0197] S905, the service controller queries the database for the set of network segments that have been sent for probe.

[0198] The database is queried to obtain the set of network segments that have been sent for exploration.

[0199] S906, the service controller compares the already issued probe network segment set with the probe network segment set to be issued to obtain the probe network segment to be deleted and the probe network segment to be added.

[0200] For details on deleting and adding probe segments, please refer to the aforementioned records, which will not be repeated here.

[0201] S907, the service controller updates the task status of the network segment task to "is being distributed".

[0202] The business controller updates the task status of the network segment task in the database to "being distributed".

[0203] S908, the service controller sends a success message to the user.

[0204] After determining whether to delete or add a probe segment, the business controller can send a success message to the user indicating that the task modification interface call was successful. This will inform the user that the task modification request was successfully initiated. Once the user receives the response, they can exit, and the subsequent modification process will be handled asynchronously by the business controller.

[0205] S909, the service controller generates deletion tasks based on the deleted probe network segment and adds new tasks based on the added probe network segment.

[0206] If the number of probe segments to be deleted exceeds the threshold, at least two probe segments can be grouped into multiple segment groups, and a deletion task corresponding to each segment group can be generated. The number of probe segments to be deleted in each segment group is less than or equal to the threshold. If the number of probe segments to be deleted does not exceed the threshold, a single deletion task is generated, containing all probe segments to be deleted. The generation process for new probe segments is similar to that for deletion tasks, and will not be elaborated here. For example, deletion tasks can include del_task1, del_task2, etc., and new tasks can include add_task1, add_task2, etc.

[0207] Optionally, a first set of network devices can be retrieved from the database, and the device identification information of each network device in the first set of network devices can be added to each new task and deletion task.

[0208] In S910, the business controller pushes the deletion task to the message queue.

[0209] Specifically, the deletion task will be pushed to the task message queue.

[0210] S911, the BGP controller retrieves deletion tasks from the message queue.

[0211] The BGP controller, connected to the network device in the target network plane, retrieves the deletion task from the task message queue.

[0212] S912, the BGP controller performs the deletion task.

[0213] During the execution of the deletion task, the BGP controller searches for the routing information corresponding to the deletion probe network segment included in the deletion task among the network devices corresponding to the device identification information included in the deletion task, and then deletes it.

[0214] S913, the BGP controller adds the execution result information of the deletion task to the message queue.

[0215] After each BGP controller executes the deletion task, it generates execution result information based on the execution result and adds it to the feedback message queue.

[0216] S914, the business controller retrieves the execution result information of the deletion task from the message queue.

[0217] Retrieve execution result information from the feedback message queue.

[0218] S915, the business controller updates the task status of the deleted task in the database based on the execution result information.

[0219] Based on the execution result information of the deletion task, the business controller updates the task status of the deletion task in the database to "execution successful" if it determines that the deletion task was successfully executed, and updates the task status of the deletion task in the database to "execution failed" if it determines that the deletion task was unsuccessful.

[0220] S916 If the deletion task is executed successfully, the business controller will delete the corresponding deletion probe network segment from the network segment tasks in the database.

[0221] If the deletion task is executed successfully, the corresponding deletion probe segment will be found in the database of the network segment tasks that have been issued for probe segment execution, and then deleted.

[0222] Specifically, after any deletion task is successfully executed, the corresponding deletion probe segment can be deleted from the distributed probe segments corresponding to the network segment task contained in the database; alternatively, after all deletion tasks corresponding to the network segment task are successfully executed, the corresponding deletion probe segment can be deleted from the distributed probe segments corresponding to the network segment task contained in the database.

[0223] In S917, the business controller pushes new tasks to the message queue.

[0224] After all deletion tasks corresponding to the task modification request have been successfully executed, the new task will be pushed to the task message queue.

[0225] S918, the BGP controller retrieves new tasks from the task message queue.

[0226] The BGP controller connected to the network device in the target network plane retrieves new tasks from the task message queue.

[0227] S919, the BGP controller executes a new task.

[0228] The routing information of the newly probed network segment corresponding to the newly added task can be reflected in the network device corresponding to the device identification information contained in the newly added task.

[0229] The S920 and BGP controllers add the execution results of newly added tasks to the message queue.

[0230] Based on the execution results of the new task, generate the execution result information of the new task and add it to the feedback message queue.

[0231] S921, the business controller retrieves the execution result information of the newly added task from the message queue.

[0232] S922, the business controller updates the task status based on the execution result information of the newly added task.

[0233] Based on the execution results of newly added tasks, the business controller updates the task status in the database to "execution successful" if the task is successful, and updates it to "execution failed" if the task fails. After confirming a successful task, the business controller can also add the corresponding new probe network segment to the database's list of already deployed probe network segments for network segment tasks. If all newly added tasks corresponding to a network segment task execute successfully, the task status of that network segment task in the database is updated to "execution successful"; if any newly added task corresponding to a network segment task fails, the task status of that network segment task in the database is updated to "execution failed".

[0234] Optionally, after the addition and deletion of tasks corresponding to the network segment task are successfully executed, the target probe network segment set corresponding to the network segment task in the database can be updated according to the probe network segment set to be issued, so that the updated target probe network segment set matches the probe network segment set to be issued, thereby updating the network segment task.

[0235] See Figure 10 As shown, the process of retransmitting the request includes S1001-S1022, which are described in detail below:

[0236] S1001, the business controller obtains a resubmission request.

[0237] Users can call the task modification interface to send a re-deployment request for a network segment task to the business controller. The re-deployment request contains the task ID of the network segment task to be re-executed.

[0238] S1002, the service controller queries the database for the task information corresponding to the network segment task.

[0239] S1003 If not found, the business controller returns an error message and exits.

[0240] The specific methods of S1002-S1003 are similar to those of S902-S903 mentioned above, and will not be repeated here.

[0241] S1004, the service controller parses out the set of probe segments to be sent based on the retransmission request.

[0242] If the task information of the corresponding network segment task is found in the database, and the task status of the network segment task is either successful or failed, then the target probe network segment set is retrieved from the database and used as the network segment set to be probed.

[0243] S1005, the service controller queries the database for the set of network segments that have been sent for probe.

[0244] The database is queried to obtain the set of network segments that have been sent for exploration.

[0245] S1006, the service controller compares the already issued probe network segment set with the probe network segment set to be issued, and obtains the probe network segment to be deleted, the probe network segment to be added, and the probe network segment to be reissued.

[0246] S1007, the service controller updates the task status of the network segment task to "issuing".

[0247] S1008, the service controller sends a success message to the user.

[0248] The system sends a success message to the user indicating that the task modification API call was successful. Once the user receives the response, they can exit, and the subsequent modification process will be handled asynchronously by the business controller.

[0249] S1009, the service controller generates deletion tasks based on deleted probe segments, new tasks based on newly added probe segments, and re-deployment tasks based on re-deployment probe segments.

[0250] The processes for generating deleted and added tasks can be found in the description of S909 above. The process for generating redispatch tasks is similar to that for generating added tasks, and will not be repeated here. For example, deleted tasks may include del_task1, del_task2, etc., added tasks may include add_task1, add_task2, etc., and redispatch tasks may include reDispatch_task1, reDispatch_task2, etc.

[0251] Specifically, the process involves retrieving a first set of network devices from the database and adding the device identifiers of each network device in the first set to each deletion task. Based on the plane identifier information, the process also involves retrieving the network devices currently included in the target network plane to obtain a second set of network devices, and adding the device identifier information of each network device in the second set to each addition task and re-deployment task.

[0252] S1010, the business controller pushes the deletion task to the message queue.

[0253] S1011, the BGP controller retrieves the deletion task from the message queue.

[0254] S1012, the BGP controller executes the deletion task.

[0255] S1013, the BGP controller adds the execution result information of the deletion task to the message queue.

[0256] S1014, the business controller retrieves the execution result information of the deletion task from the message queue.

[0257] S1015, the business controller updates the task status of the deleted task in the database based on the execution result information.

[0258] S1016 If the deletion task is executed successfully, the business controller deletes the corresponding deletion probe network segment from the network segment tasks in the database.

[0259] The specific processes of S1010-S1016 are similar to those of S910-S916 mentioned above, and will not be repeated here.

[0260] In S1017, the business controller pushes new tasks and re-deployment tasks to the message queue respectively.

[0261] After all deletion tasks are successfully executed, the newly added tasks and resend tasks will be pushed to the task message queue respectively.

[0262] S1018, the BGP controller retrieves new tasks and resend tasks from the message queue respectively.

[0263] The BGP controller connected to the network device in the target network plane retrieves new tasks and resend tasks from the task message queue.

[0264] S1019, the BGP controller executes the new task and the re-send task respectively.

[0265] The execution process of the newly added task can be found in the aforementioned S919, and will not be repeated here.

[0266] During the execution of the retransmission task, the routing information of the retransmission probe network segment corresponding to the retransmission task is reflected in the network device corresponding to the device identification information included in the retransmission task.

[0267] S1020, the BGP controller adds the execution result information of newly added tasks and resent tasks to the message queue respectively.

[0268] Based on the execution results of the new task, generate the execution result information of the new task; based on the execution results of the re-deployed task, generate the execution result information of the re-deployed task; and add each execution result information to the feedback message queue.

[0269] S1021, the business controller retrieves the execution result information of the newly added task and the re-deployed task from the message queue respectively.

[0270] Retrieve the execution result information for newly added tasks and reissued tasks from the feedback message queue.

[0271] S1022, the business controller updates the task status based on the execution result information.

[0272] If the newly added task is confirmed to have executed successfully, its status in the database will be updated to "execution successful." If the newly added task is confirmed to have failed, its status in the database will be updated to "execution failed." Similarly, if the re-deployed task is confirmed to have executed successfully, its status in the database will be updated to "execution successful." If the re-deployed task is confirmed to have failed, its status in the database will be updated to "execution failed."

[0273] After confirming that the new task has been successfully executed, the new probe segment corresponding to the new task can be added to the already issued probe segments of the network segment tasks contained in the database, so that the new probe segment can be regarded as the issued probe segment.

[0274] Optionally, after the addition and deletion of tasks corresponding to the network segment task are successfully executed, the target probe network segment set corresponding to the network segment task in the database can be updated according to the probe network segment set to be issued, so that the updated target probe network segment set matches the probe network segment set to be issued, thereby updating the network segment task.

[0275] Optionally, if all newly added tasks corresponding to a network segment task are executed successfully, the task status of the network segment task in the database is updated to "execution successful". If any newly added task corresponding to a network segment task fails, the task status of the network segment task in the database is updated to "execution failed".

[0276] See Figure 11 As shown, Figure 11This is a schematic diagram of an implementation environment involved in this embodiment. The implementation environment includes: a service controller, a BGP controller, a task message queue, a feedback message queue, a task consumption and distribution device, a cache, and a network plane; each network plane contains at least two network devices. The BGP controller is divided into multiple BGP controller groups, and each BGP controller group contains at least two BGP controllers (the diagram illustrates two BGP controllers as an example). Furthermore, the network plane is divided into at least two plane groups, each corresponding to one BGP controller group. Different plane groups have different task message queues, task consumption and distribution devices, and caches. To improve the task execution success rate, each network device connects to two BGP controllers. The BGP controllers act as route reflectors, establishing iBGP connections with the network devices. Network devices within the same network plane are connected to the same BGP controller group, meaning that different BGP controller groups correspond to different network planes. This ensures that even if one BGP controller group fails, it does not affect the updating of routing attribute information in other network planes. Moreover, different BGP controller groups have different caches, task consumption and distribution devices, and task message queues.

[0277] Under these conditions, for each task among network segment subtasks, deleted tasks, added tasks, and reassigned tasks, the process of the service controller adding the task to the task message queue includes: finding the task message queue corresponding to the target network plane to which the plane identifier information belongs, and adding the task to the found task message queue. After the task is added to the task message queue, the task consumption and distribution device corresponding to the task message queue retrieves the task from the task message queue and adds it to the corresponding cache. Correspondingly, the process of the BGP controller retrieving the task from the task message queue includes: the BGP controller retrieves the task from the corresponding cache and executes it. In the process of determining whether the task has been successfully executed based on the task execution result information, since each network device is connected to two BGP controllers, both of which retrieve the task from the corresponding cache and execute it, it can be determined whether the number of successful execution messages for the task retrieved from the feedback message queue is two. If yes, the task is considered successfully executed; otherwise, the task is considered to have failed.

[0278] In this embodiment, the already deployed probe network segments for network segment tasks are stored. Upon receiving a task adjustment request for a network segment task, the system quickly determines the probe network segment to be adjusted based on the already deployed probe network segments and the corresponding probe network segments to be deployed in the task adjustment request. A corresponding adjustment task is then generated and executed, thereby improving task adjustment efficiency. This is particularly significant for large-scale network segment tasks. In related tests, for a network segment task requiring the deployment of routing information for 30,000 probe network segments, the task adjustment process time was reduced from minutes to approximately 15 seconds. For re-deployment requests, the adjustment process time was further reduced to approximately 13 seconds. Furthermore, the efficiency of operations and maintenance personnel was improved, with task modification time reduced by 60%. The processing flow for re-deployment requests and task modification requests was adjusted accordingly, not only meeting different needs but also shortening task adjustment time and simplifying the processing flow. Simultaneously, the network segment task is split into at least two sub-tasks, reducing database read / write pressure during the process of updating the deployed network segments corresponding to the sub-tasks to the database, ensuring stable system operation.

[0279] See Figure 12 , Figure 12 This is a block diagram illustrating a data processing apparatus according to an exemplary embodiment of this application. Figure 9 As shown, the device includes:

[0280] The acquisition module 1201 is configured to acquire the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the route attribute information corresponding to the target network address set in the target network device;

[0281] The determination module 1202 is configured to search the database for the updated network address set whose routing attribute information has been updated, corresponding to the route update task, and determine the network address set to be updated whose routing attribute information is to be updated, corresponding to the task adjustment request, based on the task adjustment request and the target network address set.

[0282] The adjustment module 1203 is configured to determine the network address to be adjusted based on the updated network address set and the network address set to be updated, and to adjust the routing attribute information of the network address to be adjusted in the target network device.

[0283] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0284] From the updated network address set, search for network addresses that are not included in the network address set to be updated to obtain the first network address to be adjusted; and from the network address set to be updated, search for routing information that is not included in the updated network address set to obtain the second network address to be adjusted.

[0285] Find the overlapping network addresses between the updated network address set and the network address set to be updated to obtain the third network address to be adjusted;

[0286] In the target network device, the update of the routing attribute information for the first network address is revoked, and in the target network device, the routing attribute information for the second network address is updated, and the routing attribute information for the third network address is updated again.

[0287] In an exemplary embodiment, based on the foregoing scheme, where the target network device includes a network device that matches the device attribute information in the routing update task, the adjustment module 1203 is specifically configured as follows:

[0288] Obtain a first set of network devices; wherein the first set of network devices includes network devices whose device attribute information is matched during the execution of the route update task;

[0289] In each network device included in the first set of network devices, the update of the routing attribute information for the first network address is revoked;

[0290] Find the network devices that match the device attribute information to obtain the second set of network devices. Then, update the routing attribute information of the second network address for each network device in the second set of network devices, and update the routing attribute information of the third network address again.

[0291] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0292] If the task adjustment request is a task re-execution request to request the re-execution of the route update task, then find the network device that matches the device attribute information to obtain the second set of network devices, and update the routing attribute information of the second network address and the third network address in each network device included in the second set of network devices;

[0293] If the task adjustment request is not a task re-execution request, then the routing attribute information of the second network address is updated in each network device included in the first network device set.

[0294] In an exemplary embodiment, where the routing update task is used to reflect the routing information corresponding to each network address in the target network address set to the target network device, and the device attribute information includes plane identification information, based on the aforementioned scheme, the adjustment module 1203 is specifically configured as follows:

[0295] In each network device included in the first set of network devices, the routing information for the first network address is revoked;

[0296] Find the network devices currently included in the network plane corresponding to the plane identification information to obtain the second set of network devices;

[0297] Among the network devices included in the second set of network devices, routing information for the second network address and routing information for the third network address are reflected.

[0298] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0299] Generate a route adjustment task based on the network address to be adjusted;

[0300] Add the route adjustment task to the task message queue so that the target route reflector connected to the target network device can obtain the route adjustment task from the task message queue and adjust the routing attribute information of the network address to be adjusted in the target network device according to the route adjustment task.

[0301] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0302] From the route reflector group corresponding to the network device set to which the target network device belongs, find the target route reflector that is connected to the target network device; the route reflector group corresponding to different network device sets is different.

[0303] Locate the target task message queue corresponding to the set of network devices to which the target network device belongs; note that different sets of network devices correspond to different task message queues.

[0304] Add the route adjustment task to the target task message queue so that the target route reflector can retrieve the route adjustment task from the target task message queue.

[0305] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0306] Obtain the undo update task from the route adjustment task; the undo update task is generated based on the first network address to be adjusted, which is a network address that is included in the set of updated network addresses but not included in the set of network addresses to be updated.

[0307] Add the undo update task to the task message queue so that the target route reflector can retrieve the undo update task from the task message queue and, based on the undo update task, undo the update of the routing attribute information of the first network address in the target network device.

[0308] If the undo update task is detected as successfully executed, all other adjustment tasks in the route adjustment task, excluding the undo update task, are added to the task message queue so that the target route reflector can retrieve and execute the other adjustment tasks from the task message queue.

[0309] In an exemplary embodiment, based on the foregoing scheme, when the number of target route reflectors includes at least two, the device further includes a determination module configured to:

[0310] Retrieve the execution success information corresponding to the undo update task from the feedback message queue; the execution success information is generated after the target route reflector successfully undoes the update of the route attribute information of the first network address.

[0311] If the number of successful execution messages obtained matches the number of target route reflectors, then the undo update task is considered to have been successfully executed.

[0312] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0313] Add the undo update task and other adjustment tasks included in the route adjustment task to the task message queue; wherein, the undo update task is used to undo the update of the route attribute information of the first network address to be adjusted in the target network device, the first network address being a network address included in the set of updated network addresses but not included in the set of network addresses to be updated.

[0314] Store the task adjustment information corresponding to the task adjustment request;

[0315] If any of the undo update task or other adjustment tasks fails, the routing attribute information in the target network device is rolled back based on the task adjustment information.

[0316] In an exemplary embodiment, based on the foregoing scheme, the specific configuration of module 1203 is adjusted as follows:

[0317] If the number of network addresses to be adjusted is greater than the number threshold, then the network addresses to be adjusted are grouped according to the number threshold to obtain at least two network address groups.

[0318] Generate at least two routing adjustment tasks corresponding to each network address group.

[0319] In one exemplary embodiment, based on the foregoing solution, the device further includes a processing module configured to:

[0320] If a route update task is obtained, the routing attribute information corresponding to each network address in the target network address set of the target network device is updated according to the route update task.

[0321] Create a database table corresponding to the route update task in the database, and add the network addresses corresponding to the route update task that have had their route attribute information updated to the database table.

[0322] It should be noted that, Figure 12 The data processing apparatus provided is based on the same concept as the data processing method provided in the above embodiments. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments and will not be repeated here.

[0323] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more computer programs, which, when executed by one or more processors, cause the electronic device to implement the data processing methods provided in the above embodiments.

[0324] Figure 13 A schematic diagram of a computer system suitable for implementing an electronic device according to embodiments of this application is shown. The electronic device may be... Figure 1 The devices in the data processing platform 113 shown.

[0325] It should be noted that, Figure 13 The computer system 1300 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0326] like Figure 13 As shown, the computer system 1300 includes a Central Processing Unit (CPU) 1301, which can perform various appropriate actions and processes based on a computer program stored in Read-Only Memory (ROM) 1302 or a computer program loaded from storage portion 1308 into Random Access Memory (RAM) 1303, such as executing the data processing method described in the above embodiments. Various computer programs and data required for system operation are also stored in RAM 1303. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via bus 1304. An Input / Output (I / O) interface 1305 is also connected to bus 1304.

[0327] In some embodiments, the following components are connected to the I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the I / O interface 1305 as needed. A removable medium 1311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1310 as needed so that computer programs read from it can be installed into the storage section 1308 as needed.

[0328] In particular, according to embodiments of this application, a computer program implementing the data processing method can be carried on a computer-readable medium, which can be downloaded and installed from a network via the communication section 1309, and / or installed from a removable medium 1311.

[0329] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a computer program that can be used by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer program contained in the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0330] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and a computer program.

[0331] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0332] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor of an electronic device, causes the electronic device to perform the aforementioned data processing method. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0333] Another aspect of this application provides a computer program product, which includes a computer program that, when executed by a processor, implements the data processing methods provided in the various embodiments described above. The computer program can be stored in a computer-readable storage medium. The computer program product can be a computer program as a product, such as an APP (Application), webpage, mini-program, etc.; or, the computer program product can also be a storage medium, device, terminal, virtual machine, etc., containing the computer program.

[0334] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A data processing method, characterized in that, The method includes: Obtain the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device; The database is searched for the set of updated network addresses that have had their routing attribute information updated, corresponding to the routing update task. Based on the task adjustment request and the target network address set, the set of network addresses to be updated for the routing attribute information corresponding to the task adjustment request is determined. Based on the updated network address set and the network address set to be updated, the network address to be adjusted is determined, and the routing attribute information of the network address to be adjusted in the target network device is adjusted.

2. The method as described in claim 1, characterized in that, The step of determining the network address to be adjusted based on the updated network address set and the network address set to be updated, and adjusting the routing attribute information of the network address to be adjusted in the target network device, includes: From the updated network address set, search for network addresses not included in the network address set to be updated to obtain a first network address to be adjusted; and from the network address set to be updated, search for routing information not included in the updated network address set to obtain a second network address to be adjusted. Find the overlapping network addresses between the updated network address set and the network address set to be updated to obtain the third network address to be adjusted; In the target network device, the update of the routing attribute information of the first network address is revoked, and in the target network device, the routing attribute information of the second network address is updated, and the routing attribute information of the third network address is updated again.

3. The method as described in claim 2, characterized in that, The target network device includes network devices that match the device attribute information in the routing update task; The step of revoking the update of the routing attribute information of the first network address in the target network device, and updating the routing attribute information of the second network address and updating the routing attribute information of the third network address again in the target network device includes: Obtain a first set of network devices; wherein the first set of network devices includes network devices that match the device attribute information found during the execution of the routing update task; In each network device included in the first set of network devices, the update of the routing attribute information of the first network address is revoked; Find the network device that matches the device attribute information to obtain a second set of network devices. Then, update the routing attribute information of the second network address in each network device in the second set of network devices, and update the routing attribute information of the third network address again.

4. The method as described in claim 3, characterized in that, The process of finding network devices that currently match the device attribute information to obtain a second set of network devices, and updating the routing attribute information of the second network address in each network device included in the second set of network devices, and updating the routing attribute information of the third network address again, includes: If the task adjustment request is a task re-execution request to request the re-execution of the route update task, then the network device that currently matches the device attribute information is searched to obtain a second network device set, and the routing attribute information of the second network address and the third network address is updated in each network device included in the second network device set; If the task adjustment request is not the task re-execution request, then the routing attribute information of the second network address is updated in each network device included in the first network device set.

5. The method as described in claim 3, characterized in that, The routing update task is used to reflect the routing information corresponding to each network address in the target network address set to the target network device, and the device attribute information includes plane identification information; The step of revoking the update of the routing attribute information of the first network address among the network devices included in the first set of network devices includes: In each network device included in the first set of network devices, the routing information for the first network address is revoked; The process of finding network devices that currently match the device attribute information to obtain a second set of network devices, and updating the routing attribute information of the second network address in each network device included in the second set of network devices, and updating the routing attribute information of the third network address again, includes: Find the network devices currently included in the network plane corresponding to the plane identification information to obtain the second set of network devices; In each network device included in the second set of network devices, the routing information of the second network address and the routing information of the third network address are reflected.

6. The method as described in claim 1, characterized in that, The adjustment of the routing attribute information of the network address to be adjusted in the target network device includes: Based on the network address to be adjusted, a route adjustment task is generated; The routing adjustment task is added to the task message queue so that the target route reflector connected to the target network device can obtain the routing adjustment task from the task message queue and adjust the routing attribute information of the network address to be adjusted in the target network device according to the routing adjustment task.

7. The method as described in claim 6, characterized in that, Adding the route adjustment task to the task message queue includes: From the route reflector group corresponding to the network device set to which the target network device belongs, find the target route reflector connected to the target network device; wherein, the route reflector group corresponding to different network device sets is different; Locate the target task message queue corresponding to the network device set to which the target network device belongs; wherein, different network device sets correspond to different task message queues; The route adjustment task is added to the target task message queue so that the target route reflector can retrieve the route adjustment task from the target task message queue.

8. The method as described in claim 6, characterized in that, The step of adding the route adjustment task to the task message queue, so that the target route reflector connected to the target network device can obtain the route adjustment task from the task message queue, and adjust the routing attribute information of the network address to be adjusted in the target network device according to the route adjustment task, includes: Obtain the undo update task from the route adjustment task; the undo update task is generated based on the first network address to be adjusted, the first network address being a network address included in the set of updated network addresses but not included in the set of network addresses to be updated; The undo update task is added to the task message queue so that the target route reflector can obtain the undo update task from the task message queue and, according to the undo update task, undo the update of the routing attribute information of the first network address in the target network device. If the undo update task is detected as successfully executed, then the other adjustment tasks in the route adjustment tasks, excluding the undo update task, are added to the task message queue, so that the target route reflector can obtain the other adjustment tasks from the task message queue and execute the other adjustment tasks.

9. The method as described in claim 8, characterized in that, The number of target route reflectors includes at least two; The method further includes: Obtain the execution success information corresponding to the revoked update task from the feedback message queue; wherein, the execution success information is generated after the target route reflector successfully revoks the update of the routing attribute information of the first network address; If the number of successful execution messages obtained matches the number of target route reflectors, then the undo update task is determined to have been executed successfully.

10. The method as described in claim 6, characterized in that, Adding the route adjustment task to the task message queue includes: The undo update task and other adjustment tasks included in the routing adjustment task are added to the task message queue; wherein, the undo update task is used to undo the update of the routing attribute information of the first network address to be adjusted in the target network device, the first network address being a network address included in the updated network address set and not included in the network address set to be updated. Store the task adjustment information corresponding to the task adjustment request; If any of the revoked update task and the other adjustment tasks are detected to have failed, the routing attribute information in the target network device is rolled back according to the task adjustment information.

11. The method as described in claim 6, characterized in that, The step of generating a route adjustment task based on the network address to be adjusted includes: If the number of network addresses to be adjusted is greater than the number threshold, then the network addresses to be adjusted are grouped according to the number threshold to obtain at least two network address groups. Generate routing adjustment tasks corresponding to the at least two network address groups respectively.

12. A data processing apparatus, characterized in that, The device includes: The acquisition module is configured to acquire the task adjustment request corresponding to the executed route update task; wherein, the route update task is used to update the routing attribute information corresponding to the target network address set in the target network device; The determination module is configured to search the database for the updated network address set whose routing attribute information has been updated, corresponding to the routing update task, and determine the network address set to be updated whose routing attribute information is to be updated, corresponding to the task adjustment request, based on the task adjustment request and the target network address set. The adjustment module is configured to determine the network address to be adjusted based on the updated network address set and the network address set to be updated, and to adjust the routing attribute information of the network address to be adjusted in the target network device.

13. An electronic device, characterized in that, include: At least one processor; A storage device for storing at least one program, which, when executed by the at least one processor, causes the electronic device to perform the method as described in any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, It stores computer-readable instructions that, when executed by a computer's processor, cause the computer to perform the method described in any one of claims 1-11.

Images