Method for managing traffic detection tasks, electronic device and medium

Abstract

The present disclosure provides a method for managing traffic detection tasks, an electronic device and a medium. The method for managing traffic detection tasks comprises: acquiring a service flow in a network device and key information of the service flow, the key information comprising service flow information and port information of a port through which the service flow in the network device passes, and the service flow information comprising sending end information, destination end information and protocol information; on the basis of the key information of the service flow, performing a target management operation on a target IOAM task corresponding to the service flow.

Description

Management method, electronic equipment and medium for flow detection tasks

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application CN 202410087312.4, entitled “Management method, electronic device and medium for traffic detection tasks”, filed on January 22, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the technical field of network management, and in particular to a management method, electronic device, and medium for flow detection tasks. Background Art

[0004] In-Band Operation, Administration, and Maintenance (IOAM) 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.

[0005] However, as the amount of wireless network data increases, existing methods cannot effectively manage IOAM tasks.

[0006] Summary of the Invention

[0007] Embodiments of the present disclosure provide a method, electronic device, and medium for managing a flow detection task.

[0008] An embodiment of the present disclosure provides a method for managing traffic detection tasks, comprising: obtaining a business flow in a network device and key information of the business flow, wherein the key information includes business flow information and port information of a port through which the business flow passes in the network device, and the business flow information includes: sending end information, destination end information, and protocol information; and performing target management operations on a target IOAM task corresponding to the business flow based on the key information of the business flow.

[0009] An embodiment of the present disclosure provides an electronic device, comprising: one or more processors; and a memory 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 according to the present disclosure.

[0010] An embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon. When the program is executed by a processor, the method for managing a traffic detection task according to the present disclosure is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG1 is a schematic diagram of an application scenario of a method for managing flow detection tasks provided by an embodiment of the present disclosure;

[0012] FIG2 is a flow chart of a method for managing flow detection tasks provided by an embodiment of the present disclosure;

[0013] FIG3 is a schematic diagram of an exemplary configuration interface of a management process provided in an embodiment of the present disclosure;

[0014] FIG4 is a schematic diagram of another configuration interface of an exemplary management process provided in an embodiment of the present disclosure;

[0015] FIG5 is a flowchart of a specific implementation method of step S2 in an embodiment of the present disclosure;

[0016] FIG6 is a flowchart of a specific implementation method of step S222 in an embodiment of the present disclosure;

[0017] FIG7 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure;

[0018] FIG8 is a schematic diagram of the structure of a computer-readable medium provided by an embodiment of the present disclosure;

[0019] FIG9 is a flowchart illustrating an exemplary process of creating a target IOAM task according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the management method, electronic device and medium of the flow detection task provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0021] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but the example 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 this disclosure to those skilled in the art.

[0022] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

[0023] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0024] The terms used herein are used only to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a," "an," 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 "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements, and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof is not excluded.

[0025] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled 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 consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless expressly defined as such herein.

[0026] In this disclosure, unless otherwise specified, the following technical terms should be understood as follows:

[0027] IOAM is a traffic detection technology based on the principle of on-path detection. It provides effective and rapid end-to-end and hop-by-hop detection capabilities for network service flows in scenarios such as Secret Private Networks (SPNs) and IP Radio Access Networks (IPRANs). In this way, IOAM can effectively monitor and analyze data flows in the network, quickly perceive network performance-related faults, and accurately define and locate them, thereby supporting network maintenance and optimization. In some embodiments, IOAM can be used to detect actual packet loss, delay introduction, jitter, etc. in end-to-end path services in the network system.

[0028] An IOAM task is a specific instance task in IOAM that detects business flows in a network system.

[0029] In the embodiments of the present disclosure, IOAM can be applied to scenarios such as the fourth generation mobile communication technology (4G) network, the fifth generation mobile communication technology (5G) network, SPN, and IPRAN, but the present disclosure is not limited to this.

[0030] The following describes an application scenario of an exemplary method for managing traffic detection tasks provided by an embodiment of the present disclosure with reference to the accompanying drawings.

[0031] Figure 1 is a schematic diagram of an application scenario for the traffic detection task management method provided by an embodiment of the present disclosure. Referring to Figure 1 , as an example, IOAM technology is applied to 5G services in an SPN scenario, deployed in a Layer 3 Virtual Private Network (L3VPN). With the widespread adoption of 5G networks, and due to their complex nature, 5G networks are placing higher demands on existing efficient and highly available traffic detection technologies.

[0032] Due to its high efficiency and quick response, IOAM can provide 5G networks with services such as rapid detection, traffic information observation, and accurate identification of traffic anomalies. In 5G network applications, IOAM is used to detect the network. A pair of network-side nodes (Network Provider-end PE, NPE) are set up in the network, namely NPE 1 and NPE 2. NPE nodes are nodes that connect to the service provider edge (SPE) equipment on the service side and face the network. NPE nodes are connected to the core network and are also connected to one or more pairs of SPE nodes (for example, SPE 1 and SPE 2 in Figure 1). Both NPE nodes and SPE nodes are core-side nodes.

[0033] The core-side node is connected to a user-side user plane function (UPF) node (not shown in Figure 1). The UPF node serves as a transition node between the core and user sides and is used to perform routing and forwarding functions for user-plane data packets in the 5G core network. Multiple user-end PE (UPE) nodes can also be connected to the transition UPF node. Multiple UPE nodes can form a ring network. The UPE nodes in the ring network are used to connect to user-side devices such as base stations. User-side devices send and receive packets through the UPE node and connect to the L3VPN.

[0034] In this example, the network is controlled and managed by a deployed network management server. The network management server communicates with each node device through a special channel. The network management server provides IOAM for the network to monitor service flows between user-side nodes (UPEs) and NPEs. IOAM is deployed between the UPEs and NPEs. The IOAM task from the UPE to the NPE (for example, service flows from user-side devices such as base stations flow from the UPE to the NPE in the order: UPE, SPE, NPE) is an uplink IOAM task, used to monitor service flows from user-side nodes to core-side nodes. The IOAM task from the NPE to the UPE (for example, service flows from the NPE to the UPE in the order: NPE, SPE, UPE; service flows from the UPE can also flow to user-side devices such as base stations) is a downlink IOAM task, used to monitor service flows from core-side nodes to user-side nodes.

[0035] In the aforementioned 5G network scenario, due to the large coverage area of ​​current 5G networks, the scope of flows to be monitored needs to be expanded, resulting in a massive amount of flow information to be detected and an increase in the number of IOAM tasks required. Consequently, the number of IOAM tasks on the 5G network management server will increase. In some related technologies, IOAM tasks are primarily configured manually, but due to limited human capabilities, it is difficult to maintain millions of IOAM tasks.

[0036] Therefore, there is an urgent need to provide a solution that can manage a large number of IOAM tasks.

[0037] Figure 2 is a flow chart of a method for managing flow detection tasks according to an embodiment of the present disclosure. Referring to Figure 2 , the method for managing flow detection tasks according to an embodiment of the present disclosure includes steps S1 to S2.

[0038] In step S1, the business flow in the network device and key information of the business flow are obtained, wherein the key information includes business flow information and port information of the port through which the business flow passes in the network device, and the business flow information includes: sending end information, destination end information, and protocol information.

[0039] In step S2, a target management operation is performed on a target IOAM task corresponding to the business flow according to the key information of the business flow.

[0040] In the embodiments of the present disclosure, traffic detection tasks include IOAM tasks. By acquiring and analyzing the service flows and key information of network devices, management operations for the target IOAM tasks corresponding to the service flows are determined and executed. This enables automated detection of IOAM tasks and effectively reduces the labor cost of network management. The embodiments of the present disclosure do not impose any specific restrictions on the method of acquiring service flows; service flows can be reported by network devices or collected by a collection module.

[0041] Key information about a service flow includes service flow information of the service flow and port information of the port of the network device. A network device refers to a device from which a service flow is obtained. Service flow information includes sender information, destination information, and protocol information. The service flow information of each service flow is unique. The sender refers to the source node of the service flow, and the destination refers to the destination node of the service flow. In some embodiments, the sender information includes the source node Internet Protocol (IP) address and source port number. The destination information includes the destination node IP address and destination port number. The protocol information includes a protocol number used to identify different types of service flows.

[0042] It is also worth noting that the embodiment of the present disclosure does not impose any special restrictions on the target management operations performed by the target IOAM task. It 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 operations performed on the target IOAM task can be adjusted according to actual needs.

[0043] In some embodiments, before step S1, the management method of the traffic detection task also includes at least one of the following: in response to a management start instruction, starting a management process of the IOAM task, the management process being used to perform target management operations on the target IOAM task corresponding to the business flow; in response to a flow range configuration instruction, determining a device whitelist, the device whitelist indicating at least one of the network devices that can be managed in the management process; in response to an active time configuration instruction, determining a preset management time period for running the management process of the IOAM task; in response to an aging time configuration instruction, determining a preset aging duration corresponding to the IOAM task.

[0044] In this embodiment, executing the target management operation on the target IOAM task corresponding to the business flow is a management process of the IOAM task. Before initiating 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 is started or not. Accordingly, in some embodiments, the management process of the IOAM task can also be shut down in response to a management shutdown instruction, that is, the target management operation of the target IOAM task corresponding to the business flow is no longer executed.

[0045] Management startup instructions, flow range configuration instructions, active time configuration instructions, aging time configuration instructions and other instructions are used to limit the startup and shutdown of the management process, the range of managed network devices, the operating time range, etc., effectively avoiding unnecessary resource overhead caused by long-term operation of the management process of IOAM tasks.

[0046] The flow range configuration instruction indicates a device whitelist of at least one network device that can be managed by the management process. In some embodiments, the device whitelist is presented to the user in the form of a list of network elements and base stations, and the management process only performs IOAM task management on network devices within the device whitelist.

[0047] Because the management process consumes a certain amount of system resources, a preset management time period can be determined in response to the active time configuration instruction to run the management process. The management process will only be started during this 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 to avoid affecting business at other time ends.

[0048] Regularly deleting IOAM tasks can prevent invalid IOAM tasks from occupying system resources. On this basis, since business flows may appear to disappear temporarily in the network due to triggering rerouting, temporary deactivation of services, etc., setting a preset aging time for each IOAM task can provide a buffer time for the IOAM task. When the business flow disappears for a preset aging time, 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 time corresponding to the IOAM task is determined to be 3 days.

[0049] It is worth noting that the disclosed embodiments do not impose any specific restrictions on how instructions such as management startup instructions, flow range configuration instructions, active time configuration instructions, and aging time configuration instructions are obtained. These instructions can be generated by users interacting on a visual interactive interface, or obtained through wired or wireless communication with other devices, depending on the actual scenario. In some embodiments, users only need to predetermine the deployment scope and deployment time of the IOAM task management process, thereby resolving the difficulty of managing large-scale IOAM deployments in engineering projects.

[0050] Figure 3 is a schematic diagram of the configuration interface of an exemplary management process provided by an embodiment of the present disclosure. Referring to Figure 3, as an example, the user interacts on the visual interactive interface of the flow self-identification configuration to generate instructions. The option to start flow self-identification is "Yes", which means that the current management process has been started, and a management start instruction is generated accordingly. The start time is 3:00 and the end time is 5:00, which means that the preset management time period of the management process running the IOAM task is 3:00 to 5:00, and an active time configuration instruction indicating that the preset management time period is 3:00 to 5:00 is generated accordingly. Whether to age is used to indicate whether it is necessary to set an aging time for the IOAM task. In Figure 3, it is "Yes", indicating 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 4320 seconds (s), and an aging time configuration instruction indicating that the duration of the aging time is 4320s is generated accordingly.

[0051] FIG4 is a schematic diagram of another configuration interface of an exemplary management process provided by an embodiment of the present disclosure. Referring to FIG4 , as another example, a user configures a device whitelist through the interface, wherein the network device in the device whitelist is a base station, and the user can configure the base station in the device whitelist on the interface, wherein the base station is displayed in the form of a network element list and other base station information for user selection and configuration. FIG4 shows the first base station in the device whitelist, the rule name of the first base station is 123, the sink IP is 2.2.2.2, the control domain is e2e, and the network element list is A-6180-V3; UPE2-6180H; A-650... (the latter half of the network element list is not shown).

[0052] FIG5 is a flowchart of a specific implementation method of step S2 in an embodiment of the present disclosure. Referring to FIG5 , in some embodiments, step S2 includes the following steps S21 to S222.

[0053] In step S21, the IOAM configuration database is searched to determine whether a target IOAM task exists in the IOAM configuration database, wherein the first business flow information in the configuration information of the target IOAM task is consistent with the business flow information in the key information.

[0054] In step S221, when the target IOAM task is found, conflict detection is performed on the found target IOAM task.

[0055] In step S222, if the target IOAM task is not found, a target IOAM task is created for the business flow.

[0056] The IOAM configuration database in the embodiment of the present disclosure is used to store all IOAM tasks that have been successfully created and not deleted. The business flow information of the business flow is compared with the first business flow information in the configuration information corresponding to each IOAM task stored in the IOAM configuration database. If the first business flow information in the configuration information corresponding to the IOAM task in the IOAM configuration database is consistent with the business flow information of the business flow, the IOAM task is determined as the target IOAM task.

[0057] If the target IOAM task is found, it means that the target IOAM task suitable for detecting the business flow already exists in the current IOAM configuration database, so there is no need to create a new IOAM task for the business flow. In this case, it is necessary to further determine whether the target IOAM task conflicts with the business flow, that is, to perform conflict detection on the found target IOAM task.

[0058] In some embodiments, conflict detection (i.e., step S221) on the target IOAM task found includes: determining whether the first port information in the configuration information of the target IOAM task is consistent with the port information in the key information; if it is determined 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.

[0059] In the embodiments of the present disclosure, whether a conflict exists between the target IOAM task and the service flow is determined by checking whether the first port information in the configuration information of the target IOAM task is consistent with the port information in the key information. If the first port information and the port information are inconsistent, it indicates that a conflict exists between the target IOAM task and the service flow, and the first port information of the target IOAM task needs to be modified. If the first port information and the port information are consistent, it indicates that there is no conflict between the target IOAM task and the service flow, and the service flow can be tested using the found target IOAM task.

[0060] In the case where the target IOAM task conflicts with the service flow due to inconsistency between the first port information and the port information, the first port information of the target IOAM task in the IOAM configuration database is modified to make the two consistent. In some embodiments, the bound port of the network device corresponding to the service flow also needs to be modified.

[0061] It is worth noting that when the target IOAM task is found, other conflict verification processes can be performed on the target IOAM task and the business flow. If the result of other conflict verification processes is that there is a conflict, the corresponding information in the target IOAM task or business flow can be further modified. This disclosure is not limited to this.

[0062] If the target IOAM task is not found, it means that the current IOAM configuration database does not have a target IOAM task suitable for detecting the business flow, which will trigger the creation of a new target IOAM task for the business flow.

[0063] Figure 6 is a flowchart of a specific implementation method of step S222 in an embodiment of the present disclosure. Referring to Figure 6, in some embodiments, creating a target IOAM task for the business flow (ie, step S222) includes the following steps S2221 to S2224.

[0064] In step S2221, the target configuration information of the target IOAM task is restored according to the key information, and the target IOAM task is initialized to obtain an initial state value.

[0065] In step S2222, the target IOAM task to be created is checked for detection requirements based on the target configuration information and the port information corresponding to the business flow.

[0066] In step S2223, if the verification passes, a domain identifier is applied for the target IOAM task.

[0067] In step S2224, 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 be created.

[0068] In the embodiments of the present disclosure, the initial state value includes at least one of the detection rate, detection type, address family, enablement state, and rollover period of the target IOAM task. The embodiments of the present disclosure do not impose any special restrictions on the verification process of the target IOAM task. The verification process may include verifying the node online status, verifying the interface type, confirming the device IOAM capability, confirming the hop-by-hop capability, confirming the license information, etc. The content to be verified can be determined based on the detection requirements of the service flow.

[0069] If verification passes, a domain identifier (FlowId) is requested for the target IOAM task. A domain refers to a specific network area designated for the target IOAM task to perform service flow detection. Requesting a domain identifier for the target IOAM task distinguishes the detection area from other IOAM tasks, facilitating the implementation of specific policies for certain IOAM tasks, such as setting the frequency of flow detection and obtaining service flow detection reports. In some embodiments, the allocation of all FlowIds within the management and control system can be managed and maintained through a pre-set module.

[0070] After determining the target configuration information, initial state value, key information, and domain identifier of the target IOAM task to be created, this information is sent to the network device corresponding to the target IOAM task. The network device corresponding to the target IOAM task refers to all network devices involved in the process of detecting business flows by the target IOAM task. It is worth noting that the embodiments of the present disclosure do not impose any special restrictions on the information sent to each network device, and can be set according to actual needs.

[0071] In some embodiments, target configuration information, initial state value, key information, and domain identifier are sent from the source node to the tail node in the target IOAM task (i.e., the node at the destination end of the business flow) so that the source node can color the business flow message so that the network device nodes that the business flow passes through later can distinguish and mark it.

[0072] Accordingly, in some embodiments, the tail node corresponding to the target IOAM task needs to unstain the business flow, configure the virtual routing and forwarding (VRF) binding at the tail node, and send the domain identifier, VRF information of the business flow, interface information, binding type, detection type and other information to the tail node.

[0073] 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, such as SPN scenario and L3VPN may be different task types, or it can be determined according to the transmission direction of the business flow, such as the uplink transmission direction and the downlink transmission direction may be different task types, and it may also be determined according to whether the business flow needs to be aggregated. The present disclosure is not limited to this.

[0074] In some embodiments, after step S2224, the method further includes: storing the target configuration information of the target IOAM task in the IOAM configuration database.

[0075] In this embodiment, the target configuration information of the target IOAM task is stored so that the user can view the created IOAM task and, at the same time, it is also convenient for the unified management of the created IOAM task. In some embodiments, other information of the target IOAM task can also be stored in the IOAM configuration database, but this disclosure is not limited to this.

[0076] In some embodiments, based on the key information, restoring the target configuration information of the target IOAM task (i.e., step S2221) includes: determining the business information based on the port information of the network device in the key information, wherein the business information includes at least one of the business type and VRF information, and the VRF information indicates the forwarding rules of the business flow between multiple network devices; based on the business flow information and the business information in the key information, restoring the target configuration information of the target IOAM task.

[0077] As an example, if the application scenario is L3VPN, the service type of the target IOAM task is determined to be a service under the L3VPN scenario, and the VRF information is a flag for defining the service.

[0078] In some embodiments, based on the business flow information and the business information in the key information, restoring the target configuration information of the target IOAM task includes: restoring the destination node and destination interface in the target configuration information of the target IOAM task based on the destination end information and the business information in the business flow information; and calculating the protocol type in the target configuration information of the target IOAM task based on the protocol information and the destination end information in the business flow information.

[0079] In this embodiment, the target configuration information includes the destination node and destination interface, which can be restored based on the destination information and service information in the service flow information. Based on the destination information (e.g., the IP address of the destination node) and service information (e.g., VRF information), the destination node (e.g., the destination node) and destination interface (e.g., the destination node interface) can be restored for the target IOAM task. Based on the protocol information (e.g., the protocol number) and the destination information (e.g., the destination port number), the protocol type can be calculated for the target IOAM task.

[0080] In some embodiments, before step S2224, it also includes: determining the task type corresponding to the target IOAM task to be created, wherein 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, 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 be created.

[0081] In an embodiment of the present disclosure, task types include: uplink aggregation tasks, downlink aggregation tasks, and detailed tasks. An uplink aggregation task means that the transmission direction of the business flow corresponding to the target IOAM task is the uplink direction, and there exists an IOAM task that has been created and not deleted and can be aggregated with the target IOAM task corresponding to the business flow. A downlink aggregation task means that the transmission direction of the business flow corresponding to the target IOAM task is the downlink direction, and there exists an IOAM task that has been created and not deleted and can be aggregated with the target IOAM task corresponding to the business flow. Detailed tasks do not need to distinguish the transmission direction of the corresponding business flow, but there is no IOAM task that has been created and not deleted and can be aggregated with it.

[0082] Next, a method for determining the task type corresponding to the target IOAM task is described.

[0083] In some embodiments, determining the task type corresponding to the target IOAM task to be created includes at least one of the following: when the first IOAM task is found, determining that the task type corresponding to the target IOAM task to be created is an uplink aggregation task, wherein the sending end of the first IOAM task is consistent with the sending end of the target IOAM task, the destination end of the first IOAM task is consistent with 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; when the second IOAM task is found, determining that the task type corresponding to the target IOAM task to be created is a downlink aggregation task, wherein the sending end of the second IOAM task is consistent with the sending end of the target IOAM task, the destination end of the second IOAM task is consistent with the destination end of the target IOAM task, and the business information corresponding to the second IOAM task is consistent with the business information corresponding to the target IOAM task; when the first IOAM task and the second IOAM task are not found, determining that the task type corresponding to the target IOAM task to be created is a detailed task.

[0084] In this embodiment, in the IOAM configuration database, if there is a first IOAM task whose sending end is consistent with the sending end of the target IOAM task, whose destination end is consistent with the destination end of the target IOAM task, and whose Internet Protocol IP address corresponding to the destination end and the IP address corresponding to the destination end of the target IOAM task are within the same preset planned network segment, it means that the transmission direction of the business flow is the upward direction, and the 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 special restrictions on the total number of IOAM tasks aggregated upstream. Aggregating more IOAM tasks into one IOAM task can increase the detection range of the same IOAM task.

[0085] In the IOAM configuration database, if there is a second IOAM task whose sending end is consistent with the sending end of the target IOAM task, whose destination end is consistent with the destination end of the target IOAM task, and whose corresponding business information is consistent with the business information corresponding to the target IOAM task, then it means that the transmission direction of the business flow is the upstream direction, and the 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.

[0086] In the IOAM configuration database, if neither the first IOAM task nor the second IOAM task exists, it means that the current target IOAM task is a detailed task, that is, a task that does not need to be aggregated.

[0087] In some embodiments, when the task type corresponding to the target IOAM task to be created is an uplink aggregation task, step S2224 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; and sending 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.

[0088] In this embodiment, the target IOAM task is aggregated with the first IOAM task for uplink tasks, and the first network segment and the second network segment are stored in the same repository (i.e., the first repository). This allows for better management of the addition and removal of aggregated IOAM tasks by maintaining the individual network segments in the repository, and facilitates presenting the destination information (e.g., the IP address of the destination node) of the aggregated IOAM tasks to the user in the format of network segments. This aggregation approach offers the advantages of simple operation, ease of scalability, and high reliability.

[0089] In some embodiments, when the task type corresponding to the target IOAM task to be created is a downstream aggregation task, step S2224 includes: performing downstream 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 to 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 the corresponding network devices.

[0090] In this embodiment, the target IOAM task and the second IOAM task are downlinked and aggregated, 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 the various interfaces in the repository, and the interface information of the aggregated IOAM tasks can be presented to the user through multiple interfaces.

[0091] It is worth noting that the embodiment of the present disclosure does not impose any special restrictions on the storage formats of the first repository and the second repository, which may be tables, lists, matrices, etc.

[0092] In some embodiments, when the task type corresponding to the target IOAM task to be created is a detailed task, step S2224 includes: adding the target IOAM task whose task type is a detailed task to a preliminary sampling pool; when the total number of IOAM tasks whose task type is a 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 to each network device corresponding to the target IOAM task.

[0093] In this embodiment, since the task type is a detailed task, one business flow corresponds to one target IOAM task, so excessive detailed tasks will lead to increased management complexity, affected network bandwidth and performance, etc. Therefore, the number of existing detailed tasks (that is, IOAM tasks with a task type of detailed task in the IOAM configuration database) is limited, that is, the total number of detailed tasks is limited to no more than a preset number. When the target IOAM task with a task type of detailed task is determined, the target IOAM task is added to the preliminary sampling pool.

[0094] When the total number of IOAM tasks with the task type of detailed tasks in the current IOAM configuration database is less than the preset number, it means that you can continue to create target IOAM tasks with the task type of detailed tasks, and send the target configuration information, initial status value, key information, and domain identifier to each network device corresponding to the target IOAM task to complete the creation of the target IOAM task.

[0095] When the total number of IOAM tasks with the task type of detailed tasks in the current IOAM configuration database is greater than or equal to the preset number, the target configuration information, initial state value, key information, and domain identifier are suspended from being sent to each network device corresponding to the target IOAM instance task, and the target IOAM task is stored in the preliminary sampling pool until the IOAM tasks with the task type of detailed tasks in the IOAM configuration database are deleted. Then, they are read from the preliminary sampling pool in the order in which they are added to the preliminary sampling pool, that is, the first-in-first-out order, and the target configuration information, initial state value, key information, and domain identifier are sent to each network device corresponding to the target IOAM task to complete the creation of the target IOAM task.

[0096] In some embodiments, the management method of traffic detection tasks also includes: performing aging time detection on the IOAM tasks in the IOAM configuration database, wherein the IOAM configuration database is used to store the created IOAM tasks; if the business flow corresponding to the IOAM task is not detected within the preset aging time, deleting the IOAM task.

[0097] In this embodiment, if the business flow corresponding to the IOAM task is not detected within the preset aging time, there may be a situation where the business flow is lost, so the IOAM task is deleted to avoid useless IOAM tasks increasing management complexity.

[0098] In some embodiments, when the task type corresponding to the target IOAM task is an uplink aggregation task, deleting the IOAM task includes: searching for the first aggregation IOAM task corresponding to the target IOAM task based on the target configuration information of the target IOAM task and the business flow information of the business flow; when the total number of network segments in the first repository corresponding to the first aggregation IOAM task is greater than one, deleting 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 aggregation IOAM task is equal to one, deleting the target IOAM task and the first repository.

[0099] In this embodiment, for the first aggregated IOAM task aggregated by multiple IOAM tasks, since the first repository stores the network segment of each IOAM task, 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.

[0100] In some embodiments, for a first aggregated IOAM task in which the total number of network segments in the corresponding first storage repository is greater than one, task splitting may be further performed, and accordingly, the network segments stored in the first storage repository may be split.

[0101] In some other embodiments, if the first repository corresponding to the first aggregated IOAM task found based on the target configuration information and the business flow information of the business flow is in a non-network segment format, it means that the first aggregated IOAM task has an error and the first aggregated IOAM task can be deleted.

[0102] In some embodiments, when the task type corresponding to the target IOAM task is a downlink aggregation task, deleting the IOAM task includes: analyzing the target IOAM task to determine the first interface corresponding to the target IOAM task; when the first interface is the last interface of the second aggregation IOAM task, deleting the second aggregation IOAM task; otherwise, moving the first interface out of the second repository corresponding to the second aggregation IOAM task.

[0103] In this embodiment, for the second aggregated IOAM task aggregated by multiple IOAM tasks, since the second repository stores the interface corresponding to each IOAM task, 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.

[0104] In some embodiments, if the first interface corresponding to the target IOAM task to be deleted is the last interface in the second aggregate IOAM task, the second aggregate IOAM task is deleted; otherwise, the first interface is moved out of the second storage library corresponding to the second aggregate IOAM task.

[0105] The above-mentioned embodiments of the present disclosure obtain and analyze the business flows and key information of network devices, thereby determining and executing management operations on target IOAM tasks corresponding to the business flows. IOAM tasks can be automatically managed according to changes in business flows in network devices, solving the problem that a large number of IOAM tasks cannot be managed manually. At the same time, for small-scale networks, labor costs are correspondingly reduced, thereby accelerating the commercialization of IOAM functions.

[0106] At the same time, as a flow detection tool, IOAM can make IOAM's detection of business flows more accurate, correct and targeted through the management of IOAM tasks, thereby improving the efficiency of IOAM. In addition, the creation of IOAM tasks through the method disclosed in this disclosure will not cause waste of resources and reduce the burden on network equipment (such as setting a preset number limit for detailed tasks, etc.).

[0107] 7 , an embodiment of the present disclosure provides an electronic device, comprising: one or more processors 701; 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 701, the one or more processors 701 implement a method for managing traffic detection tasks according to various embodiments of the present disclosure.

[0108] 7 , the electronic device may further include one or more I / O interfaces 703 connected between the processor 701 and the memory 702 and configured to implement information interaction between the processor 701 and the memory 702 .

[0109] The processor 701 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 702 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) 703 is connected between the processor 701 and the memory 702, and can realize information exchange between the processor 701 and the memory 702, including but not limited to a data bus (Bus), etc.

[0110] 8 , an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon. When the program is executed by a processor, the method for managing a traffic detection task according to each embodiment of the present disclosure is implemented.

[0111] 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 are described in detail below through specific examples.

[0112] Figure 9 is a flowchart of an exemplary process of creating a target IOAM task provided by an embodiment of the present disclosure. Referring to Figure 9, as an example, the network device reports the business flow, and when it is in a preset management time period, the flow information is converted according to the business flow to obtain key information, which includes the business flow information of the business flow and the port information of the network device. The first business flow information in the configuration information of the target IOAM task that is consistent with the business flow information in the key information is searched from the IOAM configuration database to determine whether the target IOAM task exists. 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, it is necessary to create a target IOAM task. The process of creating a target IOAM task includes the following steps 901 to 9011.

[0113] In step 901, the service information, such as VRF information, is loaded based on the port information in the key information. The target configuration information of the target IOAM task is restored based on the service flow information and service information in the key information. The initial state value is set for the target IOAM task.

[0114] In step 902, the tail node of the target IOAM task is determined according to the sink node IP address of the service flow.

[0115] In step 903, the port type corresponding to the target IOAM task is verified. If the verification passes, step 904 is executed; if the verification fails, creation of the target IOAM task is terminated.

[0116] In step 904, the device capability corresponding to the target IOAM task is determined. If the verification passes, step 905 is executed; if the verification fails, the creation of the target IOAM task is terminated.

[0117] In step 905, the hop-by-hop node corresponding to the target IOAM task is confirmed. If the verification passes, step 906 is executed; if the verification fails, the creation of the target IOAM task is terminated.

[0118] In step 906, the network element status corresponding to the target IOAM task, that is, the status of each network device, is checked. If the status of all network devices is online, step 907 is executed; if the status of any network device is offline, the creation of the target IOAM task is terminated.

[0119] In step 907, the license corresponding to the target IOAM task is confirmed. If the license is available, step 908 is executed; if the license is not available, the creation of the target IOAM task is terminated.

[0120] In step 908, creation and initialization are performed according to the task type of the target IOAM task, that is, the target IOAM task is aggregated or stored in a preliminary sampling pool.

[0121] In step 909, the relevant information corresponding to the target IOAM task to be created (target configuration information, initial status value, key information, domain identifier, etc.) is sent to each network device corresponding to the target IOAM task, and it is determined whether the sending is successful. If the sending is successful, execute step 9010; if the sending fails, execute step 9011.

[0122] Step 9010: If the delivery is successful, the target IOAM task is stored in the IOAM configuration database.

[0123] Step 9011: If the delivery fails, the relevant information of the target IOAM task is rolled back, that is, the information related to the target IOAM task is deleted.

[0124] By acquiring and analyzing the business flows and key information of network devices, the management operations for the target IOAM tasks corresponding to the business flows are determined and executed. IOAM tasks can be automatically managed according to changes in business flows in network devices, solving the problem that a large number of IOAM tasks cannot be managed manually.

[0125] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As is well known to those skilled 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 includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, 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, it is well known to those skilled in the art that communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0126] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for purposes of limitation. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly indicated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A management method for traffic detection tasks, comprising: Obtaining service flows in a network device and key information of the service flows, where 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 a target in-band operation management and maintenance IOAM task 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 service flows in a network device and key information of the service flows, the method further includes at least one of the following: Responding to a management start instruction to start a management process for an IOAM task, where 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, where 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, 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, where 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 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, Performing 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, 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, 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, where the service information includes at least one of service type and virtual routing and forwarding (VRF) information, and 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 traffic detection task according to claim 6, wherein, 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, 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, where 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, Determining the task type corresponding to the target IOAM task to be created includes at least one of the following: In the case where 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, where 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 planning network segment range; In the case where 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, where 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; In the case where the first IOAM task and the second IOAM task are not 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, 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, 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 9, wherein, When the task type corresponding to the target IOAM task to be created is a detailed 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 includes: Adding the target IOAM task with the task type of detailed task to the 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 task 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 method for managing a traffic detection task according to any one of claims 1 to 12 further includes: Performing an aging time detection on the IOAM tasks in the IOAM configuration database, where 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 includes: One or more processors; A memory storing one or more programs, which, when executed by the 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.

Images