Flow detection task management method, electronic equipment and medium
By obtaining and analyzing the service flow information of network equipment, and automatically managing IOAM tasks, a large number of IOAM task management problems in 5G networks are solved, reducing labor costs and improving detection efficiency.
Patent Information
- Application Number
- CN202410087312.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-22
- Publication Date
- 2025-07-22
AI Technical Summary
The existing technology cannot effectively manage a large number of IOAM tasks, resulting in high labor costs and difficult to meet the needs of complex traffic detection in 5G networks.
By obtaining the service flow of network devices and its key information, IOAM tasks are automatically managed, including creating, modifying, and deleting target IOAM tasks, and conflict detection and aggregation management are carried out through IOAM configuration database.
Automatic detection of IOAM tasks is realized, which reduces the labor cost of network management, improves the accuracy and efficiency of detection, and reduces resource waste.
Smart Images
Figure CN120358180A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of network management technologies, and particularly to a method for managing traffic detection tasks, an electronic device, and a medium. Background Art
[0002] IOAM (In-Band OAM, in-band traffic detection) is a type of traffic detection technology that can provide services such as rapid detection, observation of traffic information, and accurate identification of traffic anomalies for wireless networks.
[0003] However, with the growth of wireless network data volume, the existing methods cannot effectively manage IOAM tasks. Summary of the Invention
[0004] Embodiments of the present disclosure provide a method for managing traffic detection tasks, an electronic device, and a medium.
[0005] In a first aspect, embodiments of the present disclosure provide a method for managing traffic detection tasks, where the method includes:
[0006] Obtain traffic flows in a network device and key information corresponding to the traffic flows; the key information includes traffic flow information and port information of ports through which the traffic flows pass in the network device, and the traffic flow information includes: sender information, destination information, and protocol information;
[0007] Perform a target management operation on a target in-band traffic detection IOAM task corresponding to the traffic flow according to the key information of the traffic flow.
[0008] In a second aspect, embodiments of the present disclosure provide an electronic device, including:
[0009] One or more processors;
[0010] A memory having one or more programs stored thereon, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method for managing traffic detection tasks described in the first aspect.
[0011] In a third aspect, embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, and when the program is executed by a processor, the method for managing traffic detection tasks described in the first aspect is implemented.
[0012] The method for managing traffic detection tasks provided by embodiments of the present disclosure realizes automated detection of IOAM tasks by obtaining and analyzing traffic flows in a network device and their key information, and thus determining and performing a management operation on a target IOAM task corresponding to a traffic flow, effectively reducing the labor cost of network management. Description of the Drawings
[0013] Figure 1 Schematic diagram of an application scenario of a management method for a traffic detection task provided by an embodiment of the present disclosure;
[0014] Figure 2 Flowchart of a management method for a traffic detection task provided by an embodiment of the present disclosure;
[0015] Figure 3 Schematic diagram of a configuration interface of an exemplary management process provided by an embodiment of the present disclosure;
[0016] Figure 4 Schematic diagram of another exemplary configuration interface of a management process provided by an embodiment of the present disclosure;
[0017] Figure 5 Flowchart of a specific implementation method of step S2 in an embodiment of the present disclosure;
[0018] Figure 6 Flowchart of a specific implementation method of step S222 in an embodiment of the present disclosure;
[0019] Figure 7 Schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure;
[0020] Figure 8 Schematic diagram of the structure of a computer-readable medium provided by an embodiment of the present disclosure;
[0021] Figure 9 Schematic diagram of a process for creating a target IOAM task provided by an embodiment of the present disclosure. Detailed implementation manners
[0022] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the management method for a traffic detection task, the electronic device, and the medium provided by the present disclosure will be described in detail below with reference to the accompanying drawings.
[0023] Hereinafter, the exemplary embodiments will be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
[0024] Without conflict, the various embodiments of the present disclosure and the various features in the embodiments may be combined with each other.
[0025] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.
[0026] The terms used herein are for describing specific embodiments only and are not intended to limit the present disclosure. As used herein, the singular forms "a" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms "comprises" and / or "consists of" are used in this specification, it specifies the presence of the stated features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups.
[0027] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0028] In the present disclosure, unless otherwise specified, the following technical terms should be understood according to the following explanations:
[0029] IOAM is a traffic detection technology based on the in-band detection principle, which provides effective and fast end-to-end and hop-by-hop detection capabilities for network traffic flows in scenarios such as SPN (Secret Private Network) and IPRAN (IP Radio Access Network). In this way, IOAM can effectively monitor and analyze data flows in the network, quickly sense network performance-related faults, and perform precise demarcation and location, thereby supporting network maintenance and optimization. In some embodiments, IOAM can be used to detect the actual packet loss situation, latency introduction, jitter, etc. in end-to-end path services in a network system.
[0030] An IOAM task is a specific instance task in IOAM for detecting traffic flows in a network system.
[0031] In the embodiments of the present disclosure, IOAM can be applied to scenarios such as 4G (4th Generation Mobile Communication Technology) networks, 5G networks, SPN, and IPRAN, but the present disclosure is not limited thereto.
[0032] Next, an application scenario of a management method for an exemplary traffic detection task provided in an embodiment of the present disclosure will be described in conjunction with the accompanying drawings:
[0033] Figure 1 It is a schematic diagram of an application scenario of a management method for a traffic detection task provided in an embodiment of the present disclosure. Refer toFigure 1 , as an example, when the IOAM technology is applied to 5G services in the SPN scenario environment, it is deployed in the L3VPN (Layer 3 Virtual Private Networks). With the popularization of the 5G (5th Generation Mobile Communication Technology) network, due to the intricate characteristics of the 5G network, the 5G network has started to have higher requirements for the original efficient and highly available traffic detection technology.
[0034] Since IOAM has the characteristics of high efficiency and fast response, it can provide services such as rapid detection, observation of traffic information, and accurate identification of traffic anomaly points for the 5G network. Therefore, in this application scenario, the network is detected through IOAM. There is a pair of NPE (Network Provider-end PE) nodes in the network, namely NPE 1 and NPE 2. The NPE node is a node that connects to the SPE (Service Provider Edge) and faces the network side. The NPE node is connected to the core network and is also connected to one or more pairs of SPE nodes (for example, Figure 1 SPE 1 and SPE 2 in the figure), and both the NPE node and the SPE node are core-side nodes.
[0035] The core-side node is connected to the downlink UPF (User Plane Function) node close to the user side ( Figure 1 not shown in the figure). The downlink UPF node is a transitional node between the core side and the user side, and is used to perform functions related to the routing and forwarding of user plane data packets in the 5G core network. Multiple UPE nodes can also be connected to the transitional UPE node. The multiple UPE nodes can form a ring network. In the ring network, the UPE (User-end PE) node is used to connect user-side devices such as base stations. When the user-side device sends and receives packets, it is all achieved through the UPE node connected to the L3VPN.
[0036] In this example, the deployed network management server controls and manages the network. The network management server communicates with each node device through a special channel. The network management server can provide IOAM for the network to detect the traffic flow between the user-side node UPE and the NPE. The IOAM is deployed between the UPE and the NPE. Among them, the IOAM task from the UPE to the NPE (for example, the order of the traffic flow passing through the user-side device such as the base station from the UPE to the NPE is: UPE, SPE, NPE) is an upstream IOAM task, which is used to detect the traffic flow situation between the user-side node and the core-side node. The IOAM task from the NPE to the UPE (for example, from the NPE to the UPE in sequence: NPE, SPE, UPE, and the traffic flow passing through the UPE can also flow to the user-side device such as the base station) is a downstream IOAM task, which is used to detect the traffic flow situation between the core-side node and the user-side node.
[0037] Based on the above 5G network scenario, since the current 5G network has a large coverage area, that is, the range of the traffic flow to be monitored needs to be increased, resulting in a large amount of traffic flow information that needs to be detected, that is, the number of IOAMs that need to be performed increases, and thus the number of IOAM tasks needs to be increased on the network management server of the 5G network. In some related technologies, the IOAM tasks are mainly configured manually. Due to the limited ability of humans, it is difficult to maintain millions of IOAM tasks.
[0038] Therefore, there is an urgent need to provide a solution that can manage a large number of IOAM tasks.
[0039] Figure 2 The flowchart of a method for managing traffic detection tasks provided by an embodiment of the present disclosure. In a first aspect, referring to Figure 2 , an embodiment of the present disclosure provides a method for managing traffic detection tasks, including:
[0040] S1. Obtain the traffic flow in the network device and the key information of the traffic flow; the key information includes traffic flow information and port information of the ports through which the traffic flow passes in the network device, and the traffic flow information includes: sending end information, destination end information, and protocol information;
[0041] S2. Perform a target management operation on the target traffic flow in-band detection IOAM task corresponding to the traffic flow according to the key information of the traffic flow.
[0042] In an embodiment of the present disclosure, the traffic detection task includes an IOAM task. By acquiring and analyzing the traffic flow of a network device and its key information, a management operation for a target IOAM task corresponding to the traffic flow is determined and executed, realizing the automated detection of the IOAM task and effectively reducing the labor cost of network management. The embodiment of the present disclosure does not impose special restrictions on the acquisition method of the traffic flow, which can be reported by the network device or obtained through a collection module.
[0043] Among them, the key information of the traffic flow includes the traffic flow information of the traffic flow and the port information of the port of the network device. The network device refers to the device from which the traffic flow is obtained. The traffic flow information includes the sender information, the destination information, and the protocol information. The traffic flow information of each traffic flow is unique. The sender refers to the source node of the traffic flow, and the destination refers to the sink node of the traffic flow. In some embodiments, the sender information includes the source node IP (Internet Protocol) address and the source port number. The destination information includes the sink node IP address and the sink port number. The protocol information includes the protocol number used to identify different types of traffic flows.
[0044] In addition, it is worth noting that the embodiment of the present disclosure does not impose special restrictions on the target management operation executed on the target IOAM task, which can be creating a target IOAM task, deleting a target IOAM task, modifying a target IOAM task, searching for a target IOAM task, etc. The management operation executed on the target IOAM task can be adjusted according to actual needs.
[0045] In some embodiments, before S1, it further includes at least one of the following:
[0046] In response to a management start instruction, starting a management process for the IOAM task; the management process is used to execute a target management operation on the target IOAM task corresponding to the traffic flow;
[0047] In response to a flow range configuration instruction, determining a device white list, where the device white list indicates at least one of the network devices that can be managed in the management process;
[0048] In response to an active time configuration instruction, determining a preset management time period for running the management process of the IOAM task;
[0049] In response to an aging time configuration instruction, determining a preset aging duration corresponding to the IOAM task.
[0050] In this embodiment, performing a target management operation on the target IOAM task corresponding to the service flow is the management process of the IOAM task. Before starting the management of the IOAM task, the management process can be managed or configured in response to an instruction. The management start instruction can control whether the management process starts or not. Correspondingly, in some embodiments, the management process of the IOAM task can also be closed in response to a management close instruction, that is, the target management operation of the target IOAM task corresponding to the service flow is no longer performed.
[0051] Instructions such as the management start instruction, the flow range configuration instruction, the active time configuration instruction, and the aging time configuration instruction are used to restrict the start and stop of the management process, the range of network devices to be managed, the running time range, etc., effectively avoiding unnecessary resource overhead caused by the long-term operation of the management process of the IOAM task.
[0052] Among them, the flow range configuration instruction indicates the device whitelist of at least one network device that can be managed in the management process. In some embodiments, the device whitelist is presented to the user in the form of a network element list and a base station, and the management process will only be executed on the network devices within the device whitelist range.
[0053] Since the management process will occupy a certain amount of system resources, the preset management time period for running the management process can be determined in response to the active time configuration instruction, and the management process will only be started within the preset management time period. In some embodiments, the preset management time period can be configured to be from 0:00 to 07:00 every day, so as to avoid affecting the services in other time periods.
[0054] Regularly deleting the IOAM tasks can avoid the situation where invalid IOAM tasks occupy system resources. On this basis, since the service flow may disappear temporarily in the network due to reasons such as triggering re-routing and temporarily deactivating the service, setting a preset aging duration for each IOAM task can provide a buffer duration for the IOAM task. When the service flow disappears for the preset aging duration, the deletion operation is triggered, effectively improving the reliability of management. In some embodiments, in response to the aging time configuration instruction, the preset aging duration corresponding to the IOAM task is determined to be 3 days.
[0055] It should be noted that the present disclosure embodiment does not impose special restrictions on the acquisition methods of instructions such as the management start instruction, the flow range configuration instruction, the active time configuration instruction, and the aging time configuration instruction. They can be instructions generated correspondingly after the user interacts on the visual interaction interface, or obtained through wired or wireless communication with other devices, which can be determined according to the actual scenario environment. In some embodiments, the user only needs to pre-determine the deployment range, deployment time, etc. of the management process of the IOAM task, and then the problem of difficult management in large-scale deployment of IOAM in engineering can be solved.
[0056] Figure 3 This is a schematic diagram of a configuration interface for an exemplary management process provided by an embodiment of the present disclosure. Referring to Figure 3 , as an example, a user interacts on a visual interaction interface for flow self-identification configuration to generate instructions. Among them, the option to start flow self-identification is "yes", indicating that the current management process has been started, and accordingly, a management start instruction is generated. The start time is 3:00 and the end time is 5:00, indicating that the preset management time period for the management process running the IOAM task is from 3:00 to 5:00, and accordingly, an active time configuration instruction indicating the preset management time period from 3:00 to 5:00 is generated. Whether to age is used to indicate whether it is necessary to set an aging time for the IOAM task, Figure 3 and "yes" in it indicates that it is necessary to set an aging time for the IOAM task. The aging time indicates that the duration of the aging time set for each created IOAM task is 4320s, and accordingly, an aging time configuration instruction indicating the duration of the aging time is 4320s is generated.
[0057] Figure 4 This is another schematic diagram of a configuration interface for an exemplary management process provided by an embodiment of the present disclosure. Referring to Figure 4 , as another example, a user configures a device white list through this interface. Among them, the network devices in the device white list are base stations, and the user can configure the base stations in the device white list on this interface. Among them, the base stations are displayed in the form of a network element list and other information of the base station for the user to select and configure, Figure 4 The first base station shown in the device white list has a rule name of 123, a destination IP of 2.2.2.2, a management domain of e2e, and a network element list of A-6180-V3; UPE2-6180H; A-650... (the latter half of the network element list is not shown).
[0058] Figure 5 This is a flowchart of a specific implementation method for step S2 in an embodiment of the present disclosure. Referring to Figure 5 , in some embodiments, S2 includes:
[0059] S21. Search the IOAM configuration database to determine whether there is a target IOAM task in the IOAM configuration database; the first service flow information in the configuration information of the target IOAM task is consistent with the service flow information in the key information;
[0060] S221. In the case of finding the target IOAM task, perform conflict detection on the found target IOAM task;
[0061] S222. When the target IOAM task is not found, create a target IOAM task for the service flow.
[0062] The IOAM configuration database in the embodiments of the present disclosure is used to store all successfully created and undeleted IOAM tasks. Compare the service flow information of the service flow with each IOAM task stored in the IOAM configuration database. When the first service flow information in the configuration information corresponding to the IOAM task in the IOAM configuration database is consistent with the service flow information of this service flow, determine this IOAM task as the target IOAM task.
[0063] When the target IOAM task is found, it means that there is already a target IOAM task applicable to detect this service flow in the current IOAM configuration database, so there is no need to create a new IOAM task for this service flow. At this time, it is also necessary to further determine whether there is a conflict between this target IOAM task and the service flow, that is, perform conflict detection on the found target IOAM task.
[0064] In some embodiments, the conflict detection on the found target IOAM task in S221 includes:
[0065] Determine whether the first port information in the configuration information of the target IOAM task is consistent with the port information in the key information;
[0066] When it is determined that the first port information is inconsistent with the port information in the key information, modify the first port information corresponding to the target IOAM task to the port information in the key information.
[0067] In the embodiments of the present disclosure, it is determined whether there is a conflict between the target IOAM task and the service flow by whether the first port information in the configuration information of the target IOAM task is consistent with the port information in the key information. When the first port information is inconsistent with the port information, it means that there is a conflict between the target IOAM task and the service flow, and then the first port information of the target IOAM task needs to be modified; when the first port information is consistent with the port information, it means that there is no conflict between the target IOAM task and the service flow, and then the found target IOAM task can be used to detect the service flow.
[0068] When there is a conflict between the target IOAM task and the service flow due to the inconsistency between the first port information and the port information, modify the first port information of the target IOAM task in the IOAM configuration database to make them consistent. In some embodiments, it is also necessary to modify the bound port of the network device corresponding to this service flow.
[0069] It should be noted that, in the case where the target IOAM task is found, other conflict verification processes can also be performed on the target IOAM task and the service flow. In the case where the result of other conflict verification processes indicates a conflict, the corresponding information in the target IOAM task or the service flow can be further modified. The present disclosure is not limited thereto.
[0070] In the case where the target IOAM task is not found, it means that there is no target IOAM task applicable to detecting the service flow in the current IOAM configuration database, and thus a new target IOAM task will be triggered to be created for the service flow.
[0071] Figure 6 This is a flowchart of a specific implementation method for step S222 in the embodiments of the present disclosure. Refer to Figure 6 , in some embodiments, creating a target IOAM task for the service flow in S222 includes:
[0072] S2221. According to the key information, restore the target configuration information of the target IOAM task, and initialize the target IOAM task to obtain an initial state value;
[0073] S2222. Check the detection requirements for the target IOAM task to be created according to the target configuration information and the port information corresponding to the service flow;
[0074] S2223. Apply for a domain identifier for the target IOAM task when the verification passes;
[0075] S2224. Send the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created.
[0076] In the embodiments of the present disclosure, the initial state value includes at least one of the detection rate, detection type, address family, enable state, and flip period of the target IOAM task. The embodiments of the present disclosure do not impose special restrictions on the verification process of the target IOAM task. It can be to verify the online state of nodes, verify the interface type, confirm the IOAM capabilities of devices, confirm the hop-by-hop capabilities, confirm the License (license information), etc., and the content to be verified can be determined according to the detection requirements for the service flow.
[0077] In the case of successful verification, apply for a domain identifier (flowId) for the target IOAM task. The domain refers to a specific network area divided for the target IOAM task to perform business flow detection. Applying for a domain identifier for the target IOAM task can distinguish the detection area from other IOAM tasks and facilitate the implementation of specific policies for some IOAM tasks, such as setting the flow detection frequency and obtaining the detection report of the business flow. In some embodiments, the allocation of all FlowIds within the control can be maintained through a preset module management.
[0078] When the target configuration information, initial state value, key information, and domain identifier of the target IOAM task to be created are determined, these information are sent to the network devices corresponding to the target IOAM task. The network devices corresponding to the target IOAM task here refer to all the network devices involved in the process of the target IOAM task detecting the business flow. It should be noted that the embodiments of the present disclosure do not impose special restrictions on the information sent to each network device and can be set according to actual needs.
[0079] In some embodiments, the target configuration information, initial state value, key information, and domain identifier are sent from the source node to the tail node (i.e., the node at the destination end of the business flow) in the target IOAM task, so as to facilitate the source node to dye the packets of the business flow, so that the subsequent network device nodes passed by the business flow can distinguish and mark it.
[0080] Correspondingly, in some embodiments, the tail node corresponding to the target IOAM task needs to configure the de - coloring of the business flow, and it is necessary to configure the VRF (Virtual Routing and Forwarding) binding at the tail node, and send information such as the domain identifier, the VRF information of the business flow, interface information, binding type, and detection type to the tail node.
[0081] In addition, the task type corresponding to the target IOAM task to be created can be determined according to the application scenario corresponding to the target IOAM task. For example, the SPN scenario and the L3VPN may be different task types, or it can be determined according to the transmission direction in which the business flow exists. For example, the upstream transmission direction and the downstream transmission direction may be different task types, or it may also be determined according to whether the business flow needs to be aggregated. The present disclosure is not limited thereto.
[0082] In some embodiments, after S2224, it further includes:
[0083] Store the target configuration information of the target IOAM task in the IOAM configuration database.
[0084] In this embodiment, the target configuration information of the target IOAM task is stored to facilitate the user to view the created IOAM task, and at the same time, it is also convenient to uniformly manage the created IOAM task. In some embodiments, other information of the target IOAM task may also be stored in the IOAM configuration database, and the present disclosure is not limited thereto.
[0085] In some embodiments, in S2221, restoring the target configuration information of the target IOAM task according to the key information includes:
[0086] Determining service information according to the port information of the network device in the key information; the service information includes at least one of a service type and virtual routing and forwarding (VRF) information; the VRF information indicates the forwarding rule of the service flow between multiple network devices;
[0087] Restoring the target configuration information of the target IOAM task according to the service flow information and the service information in the key information.
[0088] As an example, if the application scenario is L3VPN, then it is determined that the service type of the target IOAM task is the service in the L3VPN scenario, and the VRF information is a flag defining the service.
[0089] In some embodiments, restoring the target configuration information of the target IOAM task according to the service flow information and the service information in the key information includes:
[0090] Restoring the destination node and the destination interface in the target configuration information of the target IOAM task according to the destination information in the service flow information and the service information;
[0091] Calculating the protocol type in the target configuration information of the target IOAM task according to the protocol information and the destination information in the service flow information.
[0092] In this embodiment, the target configuration information includes a destination node and a destination interface, which can be restored according to the destination information and the service information in the service flow information. According to the destination information (such as the destination node IP) and the service information (such as the VRF information), the destination node (such as the destination node) and the destination interface (such as the destination node interface) can be restored for the target IOAM task. According to the protocol information (such as the protocol number) and the destination information (such as the destination port number), the protocol type can be calculated for the target IOAM task.
[0093] In some embodiments, before S2224, it further includes:
[0094] Determine the task type corresponding to the target IOAM task to be created; the task types include: uplink aggregation task, downlink aggregation task, and detail task;
[0095] According to the task type corresponding to the target IOAM task to be created, send the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created.
[0096] In the embodiments of the present disclosure, the task types include: uplink aggregation task, downlink aggregation task, and detail task. Among them, the uplink aggregation task means that the transmission direction of the service flow corresponding to the target IOAM task is the uplink direction, and there are created and undeleted IOAM tasks that can be aggregated with the target IOAM task corresponding to the service flow. The downlink aggregation task means that the transmission direction of the service flow corresponding to the target IOAM task is the downlink direction, and there are created and undeleted IOAM tasks that can be aggregated with the target IOAM task corresponding to the service flow. The detail task does not need to distinguish the transmission direction of the corresponding service flow, but there are no created and undeleted IOAM tasks that can be aggregated with it.
[0097] Next, the method for determining the task type corresponding to the target IOAM task will be described:
[0098] In some embodiments, determining the task type corresponding to the target IOAM task to be created includes at least one of the following:
[0099] In the case of finding the first IOAM task, determine that the task type corresponding to the target IOAM task to be created is an uplink aggregation task; the sending end of the first IOAM task is the same as the sending end of the target IOAM task, the destination end of the first IOAM task is the same as the destination end of the target IOAM task, and the Internet Protocol (IP) address corresponding to the destination end of the first IOAM task and the IP address corresponding to the destination end of the target IOAM task are within the same preset planned network segment range;
[0100] In the case of finding the second IOAM task, determine that the task type corresponding to the target IOAM task to be created is a downlink aggregation task; the sending end of the second IOAM task is the same as the sending end of the target IOAM task, the destination end of the second IOAM task is the same as the destination end of the target IOAM task, and the service information corresponding to the second IOAM task is the same as the service information corresponding to the target IOAM task;
[0101] In the case where the first IOAM task and the second IOAM task are not found, determine that the task type of the target IOAM task to be created is a detailed task.
[0102] In this embodiment, in the IOAM configuration database, if there is a first IOAM task whose sender is the same as the sender of the target IOAM task, the receiver is the same as the receiver of the target IOAM task, and the Internet Protocol (IP) address corresponding to the receiver is within the same preset planned network segment range as the IP address corresponding to the receiver of the target IOAM task, it indicates that the transmission direction of this traffic flow is the upstream direction, and this first IOAM task can be aggregated with the target IOAM task. If there are other IOAM tasks that can be aggregated with the aggregated target IOAM task, further aggregation can be performed. That is, the present disclosure does not impose any special restrictions on the total number of upstream-aggregated IOAM tasks. Aggregating more IOAM tasks into one IOAM task can increase the detection range of the same IOAM task.
[0103] In the IOAM configuration database, if there is a second IOAM task whose sender is the same as the sender of the target IOAM task, the receiver is the same as the receiver of the target IOAM task, and the corresponding service information is the same as the service information corresponding to the target IOAM task, it indicates that the transmission direction of this traffic flow is the upstream direction, and this second IOAM task can be aggregated with the target IOAM task. If there are other IOAM tasks that can be aggregated with the aggregated target IOAM task, further aggregation can be performed. That is, the present disclosure does not impose any special restrictions on the total number of downstream-aggregated IOAM tasks.
[0104] In the IOAM configuration database, if there are no first IOAM task and second IOAM task, it indicates that the current target IOAM task is a detailed task, that is, a task that does not require aggregation.
[0105] In some embodiments, in the case where the task type of the target IOAM task to be created is an upstream aggregation task, S2224 includes:
[0106] Perform upstream task aggregation on the target IOAM task and the first IOAM task to obtain a first aggregated IOAM task, and store the first network segment corresponding to the target IOAM task and the second network segment corresponding to the first IOAM task in a first repository;
[0107] Send the target configuration information, the initial state value, the key information, and the domain identifier corresponding to the first aggregated IOAM task to the corresponding network devices.
[0108] In this embodiment, the target IOAM task and the first IOAM task are aggregated for uplink tasks, and the first network segment and the second network segment are stored in the same repository (i.e., the first repository), so that the increase and decrease of the aggregated IOAM tasks can be better managed by maintaining each network segment in the repository, and it is also convenient to present the destination information (such as the destination node IP address) of the aggregated IOAM tasks to the user in the format of the network segment. This aggregation method has the advantages of simple operation, easy expansion, and high reliability.
[0109] In some embodiments, when the task type corresponding to the target IOAM task to be created is a downlink aggregation task, S2224 includes:
[0110] Aggregate the target IOAM task and the second IOAM task for downlink tasks to obtain a second aggregated IOAM task, and store the first interface corresponding to the target IOAM task and the second interface corresponding to the second IOAM task in the second repository;
[0111] Send the target configuration information, the initial state value, the key information, and the domain identifier corresponding to the second aggregated IOAM task to the corresponding network devices.
[0112] In this embodiment, the target IOAM task and the second IOAM task are aggregated for downlink tasks, and the second interface and the second interface are stored in the same repository (i.e., the second repository), so that the increase and decrease of the aggregated IOAM tasks can be better managed by maintaining each interface in the repository, and it is also convenient to present the interface information of the aggregated IOAM tasks to the user in the multi-interface manner.
[0113] It should be noted that the present disclosure embodiment does not impose special restrictions on the storage forms of the first repository and the second repository, which can be tables, lists, matrices, etc.
[0114] In some embodiments, when the task type corresponding to the target IOAM task to be created is a detailed task, S2224 includes:
[0115] Add the target IOAM task of which the task type is a detailed task to the preparatory sampling pool;
[0116] When the total number of IOAM tasks of which the task type is a detailed task in the IOAM configuration database is less than the preset number, obtain the IOAM tasks from the preparatory sampling pool in the order in which the IOAM tasks are added to the preparatory sampling pool;
[0117] When the IOAM task obtained from the preliminary sampling pool is the target IOAM task, the target configuration information, the initial state value, the key information, and the domain identifier are sent to each network device corresponding to the target IOAM task.
[0118] In this embodiment, since a detailed task in terms of task type means that one service flow corresponds to one target IOAM task, an excessive number of detailed tasks will cause problems such as increased management complexity, affected network bandwidth and performance, etc. Therefore, by restricting the quantity of existing detailed tasks (i.e., IOAM tasks with the task type of detailed task in the IOAM configuration database), that is, restricting the total number threshold of detailed tasks to a preset quantity, when determining the target IOAM task with the task type of detailed task, the target IOAM task is added to the preliminary sampling pool.
[0119] When the total number of IOAM tasks with the task type of detailed task in the current IOAM configuration database is less than the preset quantity, it means that the creation of the target IOAM task with the task type of detailed task can continue. Then, the target configuration information, the initial state value, the key information, and the domain identifier are sent to each network device corresponding to the target IOAM task to complete the creation of the target IOAM task.
[0120] When the total number of IOAM tasks with the task type of detailed task in the current IOAM configuration database is greater than or equal to the preset quantity, the sending of the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM instance task is suspended. The target IOAM task is stored in the preliminary sampling pool and awaits the deletion of the IOAM task with the task type of detailed task in the IOAM configuration database. Then, according to the order of addition to the preliminary sampling pool, that is, the first-in, first-out order, it is read from the preliminary sampling pool, and the target configuration information, the initial state value, the key information, and the domain identifier are sent to each network device corresponding to the target IOAM task to complete the creation of the target IOAM task.
[0121] In some embodiments, the management method of the traffic detection task further includes:
[0122] Detect the aging time of the IOAM tasks in the IOAM configuration database; the IOAM configuration database is used to store the created IOAM tasks;
[0123] When the service flow corresponding to the IOAM task is not detected within the preset aging duration, the IOAM task is deleted.
[0124] In this embodiment, if no service flow corresponding to the IOAM task is detected within a preset aging duration, there may be a situation of service flow loss. Therefore, the IOAM task is deleted to avoid increasing the management complexity due to useless IOAM tasks.
[0125] In some embodiments, when the task type corresponding to the target IOAM task is an uplink aggregation task, the deleting of the IOAM task includes:
[0126] According to the target configuration information of the target IOAM task and the service flow information of the service flow, search for the first aggregated IOAM task corresponding to the target IOAM task;
[0127] When the total number of network segments in the first repository corresponding to the first aggregated IOAM task is greater than one, delete the first network segment corresponding to the target IOAM task; when the total number of network segments in the first repository corresponding to the first aggregated IOAM task is equal to one, delete the target IOAM task and the first repository.
[0128] In this embodiment, for the first aggregated IOAM task aggregated by multiple IOAM tasks, since the network segments of each IOAM task are stored in the first repository, when the target IOAM task ages, that is, when it is determined that the target IOAM task is to be deleted, the first network segment corresponding to the target IOAM task is deleted from the first repository.
[0129] In some embodiments, for the first aggregated IOAM task with the total number of network segments in the corresponding first repository greater than one, task splitting can also be performed. Correspondingly, the network segments stored in the first repository are split.
[0130] In still other embodiments, if the format of the content in the first repository corresponding to the first aggregated IOAM task found according to the target configuration information and the service flow information is not a network segment format, it indicates that the first aggregated IOAM task is in error, and the first aggregated IOAM task can be deleted.
[0131] In some embodiments, when the task type corresponding to the target IOAM task is a downlink aggregation task, the deleting of the IOAM task includes:
[0132] Analyze the target IOAM task to determine the first interface corresponding to the target IOAM task;
[0133] When the first interface is the last interface of the second aggregated IOAM task, delete the second aggregated IOAM task; otherwise, remove the first interface from the second repository corresponding to the second aggregated IOAM task.
[0134] In this embodiment, for the second aggregated IOAM task aggregated by multiple IOAM tasks, since the interfaces corresponding to each IOAM task are stored in the second repository, when the target IOAM task ages, that is, when it is determined that the target IOAM task is to be deleted, the first interface corresponding to the target IOAM task is deleted from the second repository.
[0135] In some embodiments, when the first interface corresponding to the target IOAM task to be deleted is the last interface in the second aggregated IOAM task, the second aggregated IOAM task is deleted; otherwise, the first interface is removed from the second repository corresponding to the second aggregated IOAM task.
[0136] Through the above embodiments of the present disclosure, by obtaining and analyzing the traffic flow of the network device and its key information, the management operation of the target IOAM task corresponding to the traffic flow is determined and executed, and the IOAM tasks can be automatically managed according to the changes in the traffic flow in the network device, solving the problem that a large number of IOAM tasks cannot be managed manually. At the same time, for small-scale networks, the labor cost is also correspondingly reduced, accelerating the commercialization of the IOAM function.
[0137] At the same time, as a traffic detection tool, IOAM can make the detection of traffic flow by IOAM more accurate, correct and targeted through the management of IOAM tasks, improving the efficiency of IOAM. In addition, the creation of IOAM tasks in the manner of the present disclosure will not cause resource waste and reduce the burden on the network device (for example, setting a preset number limit for detailed tasks, etc.).
[0138] In a second aspect, referring to Figure 7 , the embodiments of the present disclosure provide an electronic device, which includes:
[0139] One or more processors 701;
[0140] A memory 702, on which one or more programs are stored. When the one or more programs are executed by the one or more processors, the one or more processors implement the management method of the traffic detection task in any one of the above.
[0141] One or more I / O interfaces 703, connected between the processor and the memory, configured to implement information interaction between the processor and the memory.
[0142] Among them, the processor 701 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 702 is a device with data storage capabilities, including but not limited to a random access memory (RAM, more specifically such as SDRAM, DDR, etc.), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory (FLASH); the I / O interface (read / write interface) 703 is connected between the processor 701 and the memory 702, and can realize the information interaction between the processor 701 and the memory 702, including but not limited to a data bus (Bus), etc.
[0143] In a third aspect, referring to Figure 8 , an embodiment of the present disclosure provides a computer-readable medium, on which a computer program is stored, and when the program is executed by a processor, it implements the management method of any one of the above traffic detection tasks.
[0144] In order to enable those skilled in the art to more clearly understand the technical solutions provided by the embodiments of the present disclosure, the technical solutions provided by the embodiments of the present disclosure will be described in detail through specific embodiments as follows:
[0145] Figure 9 FIG. Figure 9 shows a schematic flow diagram of an exemplary creation of a target IOAM task provided by an embodiment of the present disclosure. Referring to
[0146] , as an example, a network device reports a service flow. When in a preset management time period, the flow information is transformed according to the service flow to obtain key information including the service flow information of the service flow and the port information of the network device. Search for the first service flow information in the configuration information of the target IOAM task that is consistent with the service flow information in the key information from the IOAM configuration database to determine whether there is a target IOAM task; if it exists, it means that the target IOAM task already exists and there is no need to create a new target IOAM task. If it does not exist, a target IOAM task needs to be created. The process of creating a target IOAM task is as follows:
[0147] Step 901, load the affiliated service information according to the port information in the key information, such as VRF information. Restore the target configuration information of the target IOAM task according to the service flow information and service information in the key information. At the same time, set an initial state value for the target IOAM task.
[0148] Step 902, determine the tail node of the target IOAM task according to the destination node IP address of the service flow.
[0149] Step 904: Determine the device capabilities corresponding to the target IOAM task. If the verification passes, execute Step 905. If the verification fails, end the creation of the target IOAM task.
[0150] Step 905: Confirm the hop-by-hop nodes corresponding to the target IOAM task. If the verification passes, execute Step 906. If the verification fails, end the creation of the target IOAM task.
[0151] Step 906: Verify the network element status corresponding to the target IOAM task, i.e., the status of each network device. If the status of all network devices is the online state, execute Step 907. If there is a network device with an offline status, end the creation of the target IOAM task.
[0152] Step 907: Confirm the License corresponding to the target IOAM task. If the License is available, execute Step 908. If the License is not available, end the creation of the target IOAM task.
[0153] Step 908: Perform creation initialization according to the task type of the target IOAM task, i.e., aggregate the target IOAM task or store it in the preparatory sampling pool.
[0154] Step 909: Send the relevant information (target configuration information, initial status value, key information, domain identifier, etc.) corresponding to the target IOAM task to be created to each network device corresponding to the target IOAM task, and determine whether the sending is successful. If the sending is successful, execute Step 9010. If the sending fails, execute Step 9011.
[0155] Step 9010: If the sending is successful, store the target IOAM task in the IOAM configuration database.
[0156] Step 9011: If the sending fails, roll back the relevant information of the target IOAM task, i.e., delete the information related to the target IOAM task.
[0157] By obtaining and analyzing the service flows and their key information of network devices, the management operations for the target IOAM tasks corresponding to the service flows are determined and executed, and the IOAM tasks can be automatically managed according to the changes in the service flows in the network devices, solving the problem that a large number of IOAM tasks cannot be managed manually.
[0158] Those of ordinary skill in the art will understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations. In the hardware implementation, the division between the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be executed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory, or other memory technologies, CD-ROM, digital versatile disks (DVDs), or other optical disk storage, magnetic cassettes, tapes, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.
[0159] Example embodiments have been disclosed herein, and although specific terms have been used, they are used for and should be construed only as general illustrative meanings and not for purposes of limitation. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and / or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in connection with other embodiments. Accordingly, those skilled in the art will understand that various forms and details may be changed without departing from the scope of the disclosure as set forth in the appended claims.
Claims
1. A management method for traffic detection tasks, wherein, The method includes: Obtaining service flows in a network device and key information of the service flows; the key information includes service flow information and port information of ports through which the service flows pass in the network device, and the service flow information includes: sender information, destination information, and protocol information; Performing a target management operation on an in-band detection IOAM task of a target service flow corresponding to the service flow according to the key information of the service flow.
2. The management method of the traffic detection task according to claim 1, wherein, Before obtaining the service flows in the network device and the key information of the service flows, at least one of the following is further included: Responding to a management start instruction to start a management process of an IOAM task; the management process is used to perform a target management operation on a target IOAM task corresponding to the service flow; Responding to a flow range configuration instruction to determine a device white list, and the device white list indicates at least one of the network devices that can be managed in the management process; Responding to an active time configuration instruction to determine a preset management time period for running the management process of the IOAM task; Responding to an aging time configuration instruction to determine a preset aging duration corresponding to the IOAM task.
3. The management method of the traffic detection task according to claim 1, wherein, The performing a target management operation on a target IOAM task corresponding to the service flow according to the key information of the service flow includes: Searching an IOAM configuration database to determine whether a target IOAM task exists in the IOAM configuration database; first service flow information in configuration information of the target IOAM task is consistent with the service flow information in the key information; In the case of finding the target IOAM task, performing a conflict detection on the found target IOAM task; In the case of not finding the target IOAM task, creating a target IOAM task for the service flow.
4. The management method of the traffic detection task according to claim 3, wherein, The performing a conflict detection on the found target IOAM task includes: Determining whether first port information in the configuration information of the target IOAM task is consistent with the port information in the key information; In the case of determining that the first port information is inconsistent with the port information in the key information, modifying the first port information corresponding to the target IOAM task to the port information in the key information.
5. The management method of the traffic detection task according to claim 3, wherein, The creating a target IOAM task for the service flow includes: Restoring target configuration information of the target IOAM task according to the key information, and initializing the target IOAM task to obtain an initial state value; Performing a detection requirement verification on the target IOAM task to be created according to the target configuration information and port information corresponding to the service flow; In the case of passing the verification, applying for a domain identifier for the target IOAM task; Sending the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created.
6. The management method of the traffic detection task according to claim 5, wherein, The restoring target configuration information of the target IOAM task according to the key information includes: Determine service information according to the port information of the network device in the key information; the service information includes at least one of service type and virtual routing and forwarding (VRF) information; the VRF information indicates the forwarding rules of the service flow between multiple network devices. Restore the target configuration information of the target IOAM task according to the service flow information and the service information in the key information.
7. The management method of the flow detection task according to claim 6, wherein, The restoring the target configuration information of the target IOAM task according to the service flow information and the service information in the key information includes: Restore the destination node and destination interface in the target configuration information of the target IOAM task according to the destination information in the service flow information and the service information. Calculate the protocol type in the target configuration information of the target IOAM task according to the protocol information and destination information in the service flow information.
8. The management method of the flow detection task according to claim 5, wherein, The sending the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created includes: Determine the task type corresponding to the target IOAM task to be created; the task type includes: uplink aggregation task, downlink aggregation task, and detailed task. According to the task type corresponding to the target IOAM task to be created, send the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created.
9. The management method of the traffic detection task according to claim 8, wherein, The determining the task type corresponding to the target IOAM task to be created includes at least one of the following: When a first IOAM task is found, determine that the task type corresponding to the target IOAM task to be created is an uplink aggregation task; The sending end of the first IOAM task is the same as the sending end of the target IOAM task, the destination end of the first IOAM task is the same as the destination end of the target IOAM task, and the Internet Protocol (IP) address corresponding to the destination end of the first IOAM task and the IP address corresponding to the destination end of the target IOAM task are within the same preset planned network segment range. When a second IOAM task is found, determine that the task type corresponding to the target IOAM task to be created is a downlink aggregation task; The sending end of the second IOAM task is the same as the sending end of the target IOAM task, the destination end of the second IOAM task is the same as the destination end of the target IOAM task, and the service information corresponding to the second IOAM task is the same as the service information corresponding to the target IOAM task. When neither the first IOAM task nor the second IOAM task is found, determine that the task type corresponding to the target IOAM task to be created is a detailed task.
10. The management method of the traffic detection task according to claim 9, wherein, When the task type corresponding to the target IOAM task to be created is an uplink aggregation task, the step of sending the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created includes: Performing uplink task aggregation on the target IOAM task and the first IOAM task to obtain a first aggregated IOAM task, and storing the first network segment corresponding to the target IOAM task and the second network segment corresponding to the first IOAM task in a first repository; Sending the target configuration information, the initial state value, the key information, and the domain identifier corresponding to the first aggregated IOAM task to each corresponding network device.
11. The management method of the traffic detection task according to claim 9, wherein, When the task type corresponding to the target IOAM task to be created is a downlink aggregation task, the step of sending the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created includes: Performing downlink task aggregation on the target IOAM task and the second IOAM task to obtain a second aggregated IOAM task, and storing the first interface corresponding to the target IOAM task and the second interface corresponding to the second IOAM task in a second repository; Sending the target configuration information, the initial state value, the key information, and the domain identifier corresponding to the second aggregated IOAM task to each corresponding network device.
12. The management method of the traffic detection task according to claim 5, wherein, When the task type corresponding to the target IOAM task to be created is a detailed task, the step of sending the target configuration information, the initial state value, the key information, and the domain identifier to each network device corresponding to the target IOAM task to be created includes: Adding the target IOAM task with the task type of detailed task to a preliminary sampling pool; When the total number of IOAM tasks with the task type of detailed task in the IOAM configuration database is less than a preset number, obtaining the IOAM tasks from the preliminary sampling pool in the order in which the IOAM tasks are added to the preliminary sampling pool; When the IOAM task obtained from the preliminary sampling pool is the target IOAM task, sending the target configuration information, the initial state value, the key information, and the domain identifier corresponding to the target IOAM task to each corresponding network device.
13. The management method of the traffic detection task according to any one of claims 1 to 12, wherein, The method further includes: Detecting the aging time of the IOAM tasks in the IOAM configuration database; the IOAM configuration database is used to store the created IOAM tasks; Deleting the IOAM task when no service flow corresponding to the IOAM task is detected within a preset aging duration.
14. An electronic device, including: One or more processors; A memory storing one or more programs which, when executed by one or more processors, cause the one or more processors to implement the management method of the traffic detection task according to any one of claims 1 to 13.
15. A computer-readable medium storing a computer program which, when executed by a processor, implements the management method of the traffic detection task according to any one of claims 1 to 13.