WO2024067382A1 - Operations, administration and maintenance task processing method, and electronic device and computer-readable medium - Google Patents

Abstract

Provided in the present disclosure is an operations, administration and maintenance task processing method. The method comprises: acquiring an in-band operations, administration and maintenance task, which is configured for a received service flow; determining a task aggregation type according to the direction of the service flow; and when it is determined according to flow information of the acquired service flow that the configured in-band operations, administration and maintenance task meets an aggregation condition corresponding to the task aggregation type, performing aggregation processing on the configured in-band operations, administration and maintenance task and an in-band operations, administration and maintenance task which meets the aggregation condition, so as to obtain an aggregated in-band operations, administration and maintenance task. Further provided in the present disclosure are an operations, administration and maintenance task processing apparatus, and a device and a computer-readable medium.

Description

Detection task processing method, electronic device and computer readable medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to Chinese patent application 202211173338.8 filed with the State Intellectual Property Office of China on September 26, 2022, and the disclosure of this Chinese patent application is incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a detection task processing method, an electronic device, and a computer-readable medium.

Background technique

With the development of communication technology, operators are deploying the fifth generation mobile communication technology (5th Generation Mobile Communication Technology, 5G) network.

There are higher requirements for efficient and highly available traffic detection technology.

In-band Operations, Administration and Maintenance (IOAM) is a traffic measurement and monitoring technology. For traffic flows obtained from the communication network, IOAM tasks can provide end-to-end performance detection of network nodes involved in the traffic flow, so that users can perform traffic detection and observe traffic information. When processing a large number of IOAM tasks, it is necessary to improve the processing efficiency of IOAM tasks.

Summary of the invention

The present disclosure provides a detection task processing method, an electronic device, and a computer-readable medium.

In a first aspect, an embodiment of the present disclosure provides a detection task processing method, the method comprising: obtaining an in-band detection task configured for a received service flow; determining a task aggregation type according to a direction of the service flow; and, if it is determined that the configured in-band detection task satisfies an aggregation condition corresponding to the task aggregation type according to the acquired flow information of the service flow, The in-band detection tasks that meet the aggregation conditions are aggregated to obtain the aggregated in-band detection tasks.

The direction of the service flow includes an uplink direction and a downlink direction. The uplink direction is the direction from the user-side operator edge device to the network-side operator edge device, and the downlink direction is the direction from the network-side operator edge device to the user-side operator edge device. According to the direction of the service flow, the task aggregation type is determined, including: when the direction of the service flow is an uplink direction, the task aggregation type is determined to be an uplink aggregation; when the direction of the service flow is a downlink direction, the task aggregation type is determined to be a downlink aggregation.

The task aggregation type is uplink aggregation, and when it is determined based on the acquired flow information of the business flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including: receiving a target network segment; when the target network segment is a pre-created and planned network segment, obtaining a pre-created uplink aggregation task corresponding to the target network segment; and adding the configured in-band detection task to the uplink aggregation task to obtain the aggregated in-band detection task.

The task aggregation type is uplink aggregation, and when it is determined based on the acquired flow information of the service flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including: obtaining the source network address and the destination network address from the flow information of the service flow; when the network segment where the destination network address is located is within the pre-created planned network segment, and the network segment where the source network address is located is not within the planned network segment, creating a new uplink aggregation task based on the flow information of the service flow; and adding the configured in-band detection task to the new uplink aggregation task to obtain the aggregated in-band detection task.

A new uplink aggregation task is created based on the flow information of the business flow, including: setting basic parameters of the new uplink aggregation task according to the flow information of the business flow, wherein the basic parameters include at least one of the five-tuple information of the business flow, the task name, the task identifier and the flow identifier; taking the network segment where the host network address is located as the first planned network segment, obtaining the user side port in the first planned network segment, and obtaining the egress port with the first planned network segment as the target network segment from the private network routing; obtaining the host port corresponding to the new uplink aggregation task according to the union of the user side port and the egress port; taking the network address contained in the first planned network segment as the new uplink aggregation task; obtaining the user side port corresponding to ... The sink network address corresponding to the aggregation task; and creating a new uplink aggregation task according to the basic parameters, the port information of the sink port corresponding to the new uplink aggregation task, and the sink network address corresponding to the new uplink aggregation task.

After obtaining the source network address and the destination network address from the flow information of the service flow, the method further includes: when the network segment where the destination network address is located and the network segment where the source network address is located are both within the planned network segment, or when neither is within the planned network segment, obtaining the source port information and the destination port information from the flow information of the service flow, and creating an in-band detection task for the service flow from the source port to the destination port.

The task aggregation type is downlink aggregation, and when it is determined based on the acquired flow information of the service flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including: obtaining parameter information of the in-band detection task corresponding to the service flow as parameter query information; wherein the parameter query information at least includes: virtual routing forwarding information and a host network address corresponding to the service flow; when the parameter query information is queried from the parameter information of the created downlink aggregation task, the source port information of the service flow is obtained; and when the source port information of the service flow is queried from the port information of the access controller of the created downlink aggregation task, the in-band detection task contained in the created downlink aggregation task is used as the aggregated in-band detection task.

After obtaining the source port information of the service flow, the method also includes: if the source port information of the service flow is not queried from the port information of the access controller of the created downlink aggregation task, after adding the source port information of the service flow to the port information of the access controller, the in-band detection task included in the created downlink aggregation task is used as the aggregated in-band detection task.

The parameter query information also includes at least one of the following information items of the service flow: host node information, network address family, protocol number, source port number; wherein the source port to which the source port number belongs is a port of a communication protocol that supports in-band detection task aggregation.

In a second aspect, the present disclosure provides a detection task processing device, comprising: a receiving module, which is configured to receive a business flow; at least one processor, which is configured to: obtain an in-band detection task configured for the received business flow; determine a task aggregation type according to the direction of the business flow; and determine the configured in-band detection task according to the flow information of the acquired business flow. When the task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain an aggregated in-band detection task.

In a third aspect, an embodiment of the present disclosure provides an electronic device comprising one or more memories and one or more processors; the memories store a computer program that can be executed by the processors, and the computer program implements the following steps when executed by the processors: obtaining an in-band detection task configured for a received business flow; determining a task aggregation type according to the direction of the business flow; and when it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task meets an aggregation condition corresponding to the task aggregation type, aggregating the configured in-band detection task with the in-band detection task that meets the aggregation condition to obtain an aggregated in-band detection task.

In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the following steps when the computer program is executed by a processor: obtaining an in-band detection task configured for a received business flow; determining a task aggregation type according to a direction of the business flow; and when it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task satisfies an aggregation condition corresponding to the task aggregation type, aggregating the configured in-band detection task with the in-band detection task that satisfies the aggregation condition to obtain an aggregated in-band detection task.

BRIEF DESCRIPTION OF THE DRAWINGS

In the accompanying drawings of the embodiments of the present disclosure:

FIG1 is a flow chart of a detection task processing method according to an embodiment of the present disclosure;

FIG2a is a schematic diagram of an IOAM detailed task according to an embodiment of the present disclosure;

FIG2 b is a schematic diagram of an aggregated IOAM task according to an embodiment of the present disclosure;

FIG3 is a block diagram of a detection task processing device according to an embodiment of the present disclosure;

FIG. 4 is a block diagram of an electronic device according to an embodiment of the present disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the detection task processing method, device, equipment and computer-readable medium provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

The present disclosure will be described more fully below with reference to the accompanying drawings, but the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as being limited to the embodiments set forth below. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete, and will enable those skilled in the art to fully understand the scope of the present disclosure.

The accompanying drawings of the embodiments of the present disclosure are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification, and are used together with the detailed embodiments to explain the present disclosure, and do not constitute a limitation of the present disclosure. By describing the detailed embodiments with reference to the accompanying drawings, the above and other features and advantages will become more apparent to those skilled in the art.

The present disclosure may be described with reference to plan views and/or cross-sectional views by means of ideal schematic views of the present disclosure. Therefore, the exemplary illustrations may be modified according to manufacturing techniques and/or tolerances.

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

The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the present disclosure. The term "and/or" as used in the present disclosure includes any and all combinations of one or more related enumerated items. The singular forms "one" and "the" as used in the present disclosure are also intended to include plural forms, unless the context clearly indicates otherwise. The terms "including", "made of..." as used in the present disclosure specify the presence of the features, wholes, steps, operations, elements and/or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and/or groups thereof.

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

The present disclosure is not limited to the embodiments shown in the drawings, but includes modifications of the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the drawings have schematic properties, and the shapes of the regions shown in the drawings illustrate the specific shapes of the regions of the elements, but are not intended to be limiting.

In the embodiments of the present disclosure, IOAM is a network measurement and flow detection technology in the field of data communication, for example, it can provide on-line detection (also called IOAM on-line detection) of service flows in the network for Slicing Packet Network (SPN). The flow detection technology detects each network node through which the service flow passes by adding a flow ID as a label in the service, and can measure and obtain two original data: the number of packets and the timestamp. After the controller summarizes and calculates, the following performance indicators can be obtained: packet loss rate, one-way/two-way delay, and at least one of delay jitter. In the related technology, the IOAM task is a detailed task (abbreviated as IOAM detailed task). An IOAM detailed task means that each IOAM task is an end-to-end IOAM measurement task created for a service flow (for example, interface A1 of node device A to interface B1 of node device B).

As an example, the node device analyzes the service flow and obtains the five-tuple information of the service flow, which includes: source network address, sink network address, communication protocol number, source port number, and sink port number. The communication protocol number is used to identify the type of transport layer protocol, the sink network address is also called the destination network address, and the sink port number is also called the destination port number.

Node device A sends the data collection instruction from interface A1 to interface B1 of node device B hop by hop. The node device at each hop collects measurement data according to the data collection instruction. The control node in the network can analyze the measurement data collected by each node to detect and observe the traffic information between node device A and node device B, so as to quickly perceive network performance-related faults and accurately demarcate and locate the faults.

In some scenarios, for multiple business flows issued by the same route, if IOAM tasks are created only based on the network addresses of the head and tail nodes, a large number of IOAM tasks will appear in the engineering scenario, which will be cumbersome to handle and increase internal operation and maintenance costs.

The present disclosure provides a detection task processing method for solving the problem that a large number of IOAM tasks are complicated to process and increase internal operation and maintenance costs.

Referring to Fig. 1, an embodiment of the present disclosure provides a detection task processing method. Fig. 1 is a flow chart of the detection task processing method according to an embodiment of the present disclosure. As shown in Fig. 1, the detection task processing method in the embodiment of the present disclosure may include steps S110 to S130.

In step S110, an in-band detection task configured for the received service flow is obtained.

In step S120, the task aggregation type is determined according to the direction of the business flow.

In step S130, when it is determined that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type according to the acquired flow information of the service flow, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain an aggregated task. The in-band detection task.

According to the detection task processing method of the embodiment of the present invention, the aggregation type of the in-band detection task can be determined according to the direction of the received business flow. If it is determined according to the flow information of the business flow that the in-band detection task of the business flow meets the corresponding aggregation condition, the in-band detection tasks that meet the aggregation condition will be aggregated to obtain the aggregated in-band detection tasks. The aggregation of in-band detection tasks can reduce the number of a large number of IOAM tasks in the project, so that server resources can be reasonably allocated, and the network performance is optimized. At the same time, it also reduces the burden on network administrators by manually issuing IOAM task information, reduces the difficulty of operation, is easy to expand and has high reliability, and greatly improves the user experience.

In some embodiments, in step S120, the direction of the service flow includes an uplink direction and a downlink direction; the uplink direction includes the direction from the user-side operator edge device to the network-side operator edge device, and the downlink direction includes the direction from the network-side operator edge device to the user-side operator edge device.

The User-end Provider Edge (UPE) device on the user side is a network device that is directly connected to the user device and is used to implement the user access function. The Network Provider Edge (NPE) device on the network side is a Service Provider-end Provider Edge (SPE) device that is connected to the aggregation side endpoint and faces the network side. The SPE device is used to implement the management and release of Virtual Private Network (VPN) routes. For example, in a Layer 3 Virtual Private Network (L3VPN), the NPE device is the endpoint device on the core network side, the SPE device is the endpoint device on the aggregation side, and the UPE device is the endpoint device on the access side.

In some embodiments, step S120 may specifically include: when the direction of the business flow is an uplink direction, determining the task aggregation type to be an uplink aggregation; when the direction of the business flow is a downlink direction, determining the task aggregation type to be a downlink aggregation.

In the disclosed embodiment, the IOAM tasks can be divided into two categories according to the direction of the service flow: the uplink IOAM tasks from the UPE device to the NPE device and the downlink IOAM tasks from the NPE device to the UPE device. Correspondingly, the aggregation IOAM tasks are also divided into two corresponding categories: the uplink aggregation IOAM tasks and the downlink IOAM tasks. The uplink aggregation IOAM tasks correspond to the uplink IOAM tasks, referred to as the uplink aggregation tasks, and the downlink IOAM tasks correspond to the downlink aggregation IOAM tasks, referred to as the downlink aggregation tasks.

In the disclosed embodiment, the uplink aggregation processing includes: obtaining the destination network address corresponding to the IOAM task, determining the network segment where the destination network address is located, accessing the source node (i.e., the ingress node) of the service flow, and coloring the message (or the data packet corresponding to the message) in a certain network segment interval with the network address of the destination node, so as to aggregate the IOAM corresponding to the message in the network segment interval.

The on-path detection technology can use the on-path detection information carried in the message to feature the service flow in the network. The feature marking can also be called coloring (AltMarking), and coloring can be understood as a marking action in the IOAM task processing flow. Exemplarily, within a on-path detection cycle, the message can be colored according to the characteristics of the message. For example, the message with specified five-tuple information can be colored. In some embodiments, the colored message (or the data packet corresponding to the message) of the source node needs to be stripped and bound at the destination node to avoid service interruption.

In the disclosed embodiment, for uplink aggregation, if the IOAM task is sent to the wrong destination, it may cause service interruption. Therefore, the service flow from the UPE device to the NPE device is analyzed through uplink aggregation, the destination network address of the flow information of the service flow to which the IOAM task belongs is obtained, and the network segment corresponding to the destination network address is obtained. If the network segment is included in the pre-created planned network segment, the message of the network segment accessed by the ingress node and corresponding to the destination network address in a certain planned network segment interval can be colored to form an IOAM aggregation task, which is used to aggregate the IOAM tasks of the message of the network segment to which the destination network address belongs in a certain planned network segment interval.

In the embodiments of the present disclosure, since there are likely to be multiple business flows under the same route, the aggregation task is of great significance to the business flows with the same route. For example, if the network segment input by the user is 1.1.1.1/0, it means that all business flows can be tracked based on this network segment. This situation is not allowed in actual application scenarios. Therefore, for end-to-end business flows, it is necessary to determine whether the destination network segment input by the user is legal based on the destination network element associated with the network segment corresponding to the destination network of the business flow. However, if the static routes of all destination network elements are queried end-to-end and then analyzed, the efficiency is extremely low. Therefore, the embodiments of the present disclosure implement network segment planning by pre-creating a planned network segment. When creating an uplink aggregation IOAM task, for the IOAM task of a certain business flow, you can select the created network segment (that is, the pre-created planned network segment) and add the IOAM task of the business flow to the created network segment. In the IOAM aggregation task of the network segment, the uplink aggregation of the in-band detection task is realized.

In the embodiments of the present disclosure, a network element is a device in a network. A network element can generally be regarded as the smallest unit that can be monitored and managed in network management. For example, when an end-to-end IOAM measurement task (e.g., interface A1 of node device A to interface B1 of node device B) is created for a service flow, node device B is the destination network element.

In some embodiments, the task aggregation type is uplink aggregation; step S130 may specifically include steps S11 to S13.

In step S11, a target network segment is received.

The received target network segment is: the network segment corresponding to the target network address of the received service flow.

It should be understood that when manually creating an IOAM aggregation task for uplink aggregation, there are multiple ways to implement receiving the target network segment. For example, the network segment directly input by the user through an input device can be received to obtain the target network segment; at least one created network segment can be displayed through a page, and the page provides a corresponding selection control (such as a radio button or a radio button) for each created network segment. In response to the operation of selecting the selection control, the created network segment corresponding to the selected selection control is used as the target network segment; or the user can input the target network segment in advance and store it in a designated device, and this device receives the target network segment sent by the designated device. Among them, the designated device can be, for example, a pre-set storage device, which can be set according to actual conditions.

Exemplarily, if a network segment is received that is directly input by a user through an input device, then for an end-to-end service flow, it is not necessary to input a sink port of the service flow.

In step S12, when the target network segment is within the pre-created planned network segment, a pre-created uplink aggregation task corresponding to the input target network segment is obtained.

The pre-created planned network segment may include at least one created network segment; the target network segment being within the pre-created planned network segment indicates that the target network segment is a created network segment. In this case, obtaining the uplink aggregation IOAM task pre-created for the network segment can obtain the IOAM task for the uplink direction of the service flow that has been aggregated under the network segment.

In step S13, the configured in-band detection task is added to the uplink aggregation task to obtain the aggregated in-band detection task.

After step S13, that is, adding the configured in-band detection task to the uplink aggregation task After the service is completed, the uplink aggregation of the configured in-band detection task is completed.

In an embodiment of the present disclosure, an IOAM task configured for a received business flow is obtained, and when it is determined that the direction of the business flow is an upward direction and the task aggregation type is an upward aggregation, a target network segment is received. When the target network segment is a pre-created and planned network segment, the IOAM task configured for the business flow is added to a pre-created upward aggregation task corresponding to the target network segment, and data packets of business flows whose ingress access destination is within a certain network segment interval are uniformly colored, thereby realizing the upward aggregation of the IOAM task configured for the business flow.

In the embodiment of the present disclosure, uplink aggregation is to aggregate the in-band detection tasks of the service flow in the uplink direction from the user-side operator edge device to the network-side operator edge device. Therefore, for the network-side operator edge device, uplink aggregation is the task aggregation performed by analyzing the service flow from the user-side operator edge device to the network-side operator edge device at the sink end of the service flow.

In some embodiments, the task aggregation type is uplink aggregation; step S130 may specifically include steps S21 to S23.

In step S21, a source network address and a destination network address are obtained from flow information of the service flow.

In step S22, when the network segment where the sink network address is located is within the pre-created planned network segment, and the network segment where the source network address is located is not within the planned network segment, a new uplink aggregation task is created based on the flow information of the service flow.

In this step, if the network segment to which the destination network address belongs is within a planned network segment interval, and the network segment to which the source network address belongs is not within any planned network segment interval, step S23 is executed to create an uplink aggregation IOAM task.

In step S23, the configured in-band detection task is added to the new uplink aggregation task to obtain the aggregated in-band detection task.

Through the above steps S21 to S23, after receiving the service flow, the source network address and the destination network address are obtained from the flow information of the service flow, and it is determined whether the network segment to which the obtained source network address belongs and the network segment to which the destination network address belongs are in the pre-created planned network segment. If it is determined that the network segment to which the source network address belongs is not in the planned network segment, and the network segment to which the destination network address belongs is in the planned network segment, then an uplink aggregation IOAM task is automatically created according to the flow information of the service flow. Through this method, the service flow of the base station is differentiated according to the destination network segment, and the in-band detection task corresponding to the service flow whose destination network address belongs to the planned network segment is aggregated. It improves task processing efficiency and saves server resources.

According to the detection task processing method of the embodiment of the present disclosure, aggregation technology can be applied to IOAM tasks, and multiple uplink IOAM tasks can be aggregated according to network segments. The method is simple to operate, easy to expand, and highly reliable.

In some embodiments, in the above step S22, the step of creating a new uplink aggregation task based on the flow information of the service flow may specifically include steps S31 to S35.

In step S31, basic parameters of a new uplink aggregation task are set according to the flow information of the service flow, wherein the basic parameters include at least one of quintuple information of the service flow, a task name, a task identifier, and a flow identifier.

In this step, the five-tuple information of the service flow includes the source network address, destination network address, communication protocol number, source port number, and destination port number of the service flow. The task name is used to indicate the name of the IOAM task used to indicate the uplink aggregation task, the task identifier is used to uniquely identify the uplink aggregation task, and the flow identifier is used to uniquely identify the service flow.

In step S32, the network segment where the destination network address is located is taken as the first planned network segment, the user side port in the first planned network segment is obtained, and the egress port with the first planned network segment as the target network segment is obtained from the private network routing.

In step S33, a sink port corresponding to a new uplink aggregation task is obtained according to the union of the user-side port and the egress port.

In step S34, the network address included in the first planned network segment is used as the sink network address corresponding to the new uplink aggregation task.

In steps S32 and S34, in the process of creating the uplink aggregation IOAM task, in addition to setting the basic parameters of the uplink aggregation task, for the working network elements (main network elements) and protection network elements (backup network elements) in the planned network segment, the union of the user-side ports (also called user-side interfaces) in the planned network segment and the egress ports (also called egress interfaces) in the private network routing whose target network segment is the planned network segment is obtained, and the egress port of the target network segment of the created uplink aggregation task is obtained, and the network address in the planned network is used as the host network address of the created uplink aggregation task.

In step S35, a new uplink aggregation task is created according to the basic parameters, the port information of the sink port corresponding to the new uplink aggregation task, and the sink network address corresponding to the new uplink aggregation task.

In the embodiment of the present disclosure, after receiving the service flow, the flow information of the service flow is The source network address and the sink network address are obtained. If it is determined that the network segment to which the source network address belongs is not within the planned network segment, and the network segment to which the sink network address belongs is within the planned network segment, the basic parameters of the new uplink aggregation task, the port information of the corresponding sink port, and the corresponding sink network address can be automatically set according to the flow information of the service flow, thereby realizing the automatic creation of the uplink aggregation IOAM task.

In some embodiments, in step S21, after obtaining the source network address and the destination network address from the flow information of the service flow, the detection task processing method also includes: S41, when the network segment where the destination network address is located and the network segment where the source network address is located are both within the pre-created planned network segment, or when neither is within the pre-created planned network segment, obtaining the source port information and the destination port information from the flow information of the service flow, and creating an in-band detection task for the service flow from the source port to the destination port.

In this embodiment, if both the source network address and the destination network address are not within the planned network segment, it means that the IOAM task of the business flow is not within the planned scope of the aggregation task to be created. Therefore, a new IOAM task can be created for the business flow in a detailed manner, that is, based on the flow information of the business flow, an IOAM task is created for the business flow separately, and no aggregation processing is performed on the IOAM task of the business flow.

In this embodiment, if the source network address and the destination network address are both within the planned network segment, it indicates that the service flow does not belong to an uplink direction from the UPE device to the NPE device. For example, the service flow may be some service flow within the network and is not suitable for aggregation tasks.

In this embodiment, for the case where both the source network address and the destination network address are not within the planned network segment, or are both within the planned network segment, the source port information and the destination port information can be obtained from the flow information of the business flow, and an in-band detection task for the business flow from the source port to the destination port is created, thereby creating an IOAM task for the business flow based on the flow information of the business flow, and obtaining a detailed task for the business flow.

In the disclosed embodiment, the downlink aggregation is to aggregate the in-band detection tasks of the downlink service flow in the direction from the NPE device to the UPE device. Therefore, for the NPE device, the downlink aggregation is the task aggregation performed by analyzing the service flow from the NPE to the UPE device at the source end of the service flow. In addition, since the downlink aggregation is performed at the source end of the service flow, as the entrance of the service flow, there is no need to worry about the service flow being sent to the wrong device. Even if the worst result of sending to the wrong device is that the service flow is useless, it will not cause service interruption.

In some embodiments, the task aggregation type is downlink aggregation; step S130 may specifically include steps S51 to S53.

In step S51, parameter information of the in-band detection task corresponding to the service flow is obtained as parameter query information, wherein the parameter query information at least includes: virtual routing forwarding information and a sink network address corresponding to the service flow.

In this step, at least the virtual routing and forwarding (VRF) information and the destination network address of the service flow are used as parameter query information to query whether the preset IOAM data table contains the same information.

In some embodiments, the parameter query information may also include: at least one of the following information items of the service flow: host node information, network address family, protocol number, source port number, wherein the source port to which the source port number belongs is a port of a communication protocol that supports in-band detection task aggregation.

In this embodiment, the parameter query information may include at least one of the following: the destination node information, the network address family, the protocol number, and the source port number, in addition to the virtual routing forwarding information and the destination network address. The source port number is used to identify the source port, and the port identified by the source port number should support the relevant communication protocols for in-band detection task aggregation. For example, the source port number of the service flow with the protocol number of 132 does not support the relevant protocols for in-band detection task aggregation, and the IOAM task cannot be aggregated.

In some embodiments, after acquiring the in-band detection task configured for the received service flow, the method further includes: filtering service flows of related protocols that do not support in-band detection task aggregation, thereby filtering out service flows that do not support aggregation.

It should be understood that in actual application scenarios, there may be ports of multiple related protocols for in-band detection task aggregation, and there may also be ports of other related protocols that do not support in-band detection task aggregation. The protocol number and source port number in the parameter query information are obtained based on actual conditions, and the present disclosed embodiment does not make specific limitations.

In step S52, when parameter query information is queried from the parameter information of the created downstream aggregation task, source port information of the service flow is acquired.

In this step, if the same information as the parameter query information is found in the IOAM data table, the source port information of the service flow is obtained, such as the port number of the source port, the port type and other port information.

In step S53, when the source port information of the service flow is queried from the port information of the access controller of the created downlink aggregation task, the in-band detection task included in the created downlink aggregation task is used as the aggregated in-band detection task.

In step S53, it can be determined whether the port information of the current source port already exists in the port information of the multi-access controller (AC) of the downstream aggregation IOAM task. The multi-access controller indicates that the current network is a networking of multiple access controllers. If so, there is no need to create a new downstream aggregation task, and the in-band detection task contained in the created downstream aggregation IOAM task can be directly used as the in-band IOAM task after aggregation.

Through steps S51 to S53, the IOAM tasks of the service flows starting from the same source device (the same NPE device) to the same destination device (the same base station) are aggregated. The aggregation process can be achieved by manual creation or automatic creation. The in-band detection tasks corresponding to the service flows from the same network side operator edge device and with the same routing forwarding information and host network address (for example, going to the same base station) are aggregated to improve task processing efficiency and save server resources.

In some embodiments, NetFlow is a traffic data statistics standard. In actual application scenarios, it can be implemented as: a toolkit for analyzing network data packet information, and is widely used in routers and switches. Netfow technology can be used to detect IP traffic information on the network. The collected Netflow traffic information can monitor and record all traffic in and out of the port, which is beneficial to network planning, network management, traffic billing and virus detection; automatic flow creation is to use Netflow to automatically detect the flow existing in the network and automatically create end-to-end IOAM measurement tasks for the corresponding flow.

In some embodiments, in the process of automatically creating a downlink aggregation IOAM task, the creation process of synchronized traffic data statistics (NetFlow) and automatic flow creation can also be added to the creation mode of the aggregation IOAM, so that aggregation tasks can be issued in 5G services without manual intervention by users, reducing a large number of user manual operations and improving the processing efficiency of IOAM tasks.

In this embodiment, NetFlow can be used to synchronously measure and count the high-speed forwarding service flows. Specifically, the collected service flow data can be synchronously analyzed to provide visibility on the flow and traffic, and track where the traffic comes from, where it flows to, and the traffic generated at any time. The recorded information can be used for usage monitoring, anomaly detection, and other purposes. and various other network management tasks.

According to the detection task processing method of the embodiment of the present disclosure, aggregation tasks can be issued in 5G services without manual intervention by users, which reduces a large number of manual operations of users, is easy to expand and has high reliability.

In some embodiments, after obtaining the source port information of the service flow in step S52, the detection task processing method also includes: S54, when the source port information of the service flow is not queried from the port information of the access controller of the created downlink aggregation task, after adding the source port information of the service flow to the port information of the access controller, the in-band detection task contained in the created downlink aggregation task is used as the aggregated in-band detection task.

In this embodiment, if the source port information of the service flow is not queried, it is necessary to modify the IOAM data table and add the source port information to the IOAM data table; the data table contains information of multiple access controllers, and an access controller information is added to the data table. The IOAM tasks of the service flow corresponding to the source port information are aggregated through the added access controller, and the IOAM tasks are aggregated into the downlink aggregation tasks created above.

In some embodiments, to add an access controller information in a data table, it is necessary to modify the access controller information list (ACList) in the end-to-end data table. Exemplarily, the IOAM data table can be modified by sending a modification command from a single point.

According to the detection task processing method of the embodiment of the present disclosure, the aggregation IOAM tasks can be divided into two categories according to the direction of the business flow: uplink IOAM tasks (corresponding to the business flow from the UPE device to the NPE device) and downlink IOAM tasks (corresponding to the business flow from the NPE device to the UPE device); the aggregation IOAM tasks are therefore divided into two categories: uplink aggregation IOAM tasks and downlink aggregation IOAM tasks. For the uplink aggregation IOAM tasks, the network segment of the host network address of the business flow corresponding to the uplink IOAM task is obtained, and the network address of the destination node accessed from the source node (i.e., the entry node) of the business flow is colored in a certain network segment interval (or the data packet corresponding to the message) to aggregate the IOAM corresponding to the message in the network segment interval; for the downlink aggregation IOAM tasks, the business flow IOAM tasks starting from the same source device (such as the same NPE device) to the same destination device (such as the same base station) can be aggregated. By aggregating IOAM tasks, the number of a large number of IOAM tasks in the project can be reduced, so that server resources can be reasonably allocated. It optimizes network performance, reduces user operation difficulty, and greatly improves user experience.

In actual application scenarios, there may be old equipment on the project site, and the old network equipment has low performance and can support a small number of configurable IOAMs. When the aggregated IOAM task is introduced, these devices can support traffic monitoring of multiple IP service flows. Therefore, the detection task processing method of the embodiment of the present disclosure can be compatible with devices with low performance.

In the disclosed embodiments, in-band detection of service flows is a traffic detection technology that can be applied to Ethernet services and L3VPN services. The purpose is to detect the actual packet loss of end-to-end path services, the actual packet loss of end-to-end path services, the delay introduced by each node device on the path (each node device on each link), and the packet loss of each node on the path when the delay is introduced. It is also an important basis for on-site fault diagnosis, such as diagnosing the network status of the node device, including but not limited to delay, packet loss, etc.

In order to better understand the detection task processing method of the present disclosure, the detection task processing method of the present disclosure is described below in conjunction with Figures 2a and 2b, taking row aggregation as an example. Figure 2a is a schematic diagram of an IOAM detailed task according to an embodiment of the present disclosure, and Figure 2b is a schematic diagram of an IOAM task after aggregation according to an embodiment of the present disclosure.

In Figures 2a and 2b, NPE node devices in a local network of L3VPN services, such as NPE1 and NPE2, UPE node devices in L3VPN, such as UPE1 and UPE2, user plane function (UPF) node devices, such as UPF1, UPF2, UPF3 and UPF4, and user base station devices, such as base station 1 and base station 2 are exemplarily shown.

UPF1 is connected to NPE1 via interface 1, UPF2 is connected to NPE1 via interface 2, UPF3 is connected to NPE2 via interface 3, and UPF4 is connected to NPE2 via interface 4. FIG. 2a and FIG. 2b also show interfaces of UPE1 such as interface 5 and interfaces of UPE2 such as interface 6. Interface 5 is used to receive service flows from NPE1 and NPE2 to UPE1, and interface 6 is used to receive service flows from NPE1 and NPE2 to UPE2. Base station 1 is connected to the user side interface library of UPE1, and base station 2 is connected to the user side interface library of UPE2.

It should be understood that the number of devices in Figures 2a and 2b is only for illustration. It can be flexibly adjusted according to actual application needs. For example, the NPE node device, the UPE node device, the UPF node device and the user base station device can all be one node device. It can also be a larger number of node devices. In addition, this architecture can also include some auxiliary devices, such as routers, switches, etc. It can be flexibly configured according to needs, and there is no restriction on this aspect.

In Figures 2a and 2b, the line segments represent business flows, and the arrows represent the directions of the business flows. The detail numbers on the line segments represent the detailed IOAM tasks configured for the business flows represented by the line segments, such as Detail 1 to Detail 10 in Figure 2a, which represent Detail Tasks 1 to Detail Tasks 10.

Referring to Figure 2a, in this local L3VPN network, since the direction of the service flow is from the NPE device to the UPE device, such as the service flow from NPE1 to UPE1 and UPE2, and the service flow from NPE2 to UPE1 and UPE2 shown in Figure 2a; therefore, it is necessary to perform downstream aggregation on the detailed IOAM tasks of each service flow.

Referring to FIG. 2 b , according to the detection task processing method of the embodiment of the present disclosure, the following downlink aggregation processing is performed on each IOAM detailed task shown in FIG. 2 a .

As shown in "Aggregation 1" in Figure 2b, the IOAM detail tasks (Detail 1, Detail 2) of the two service flows sent by UPF1 to base station 1 of UPE1 through NPE1 are aggregated with the IOAM detail task (Detail 4) of the one service flow sent by UPE2 to base station 1 of UPE1 through NPE1.

As shown in "Aggregation 2" in Figure 2b, the IOAM detail task (detail 7) of a service flow sent by UPF3 to base station 1 of UPE1 through NPE2 is aggregated with the IOAM detail task (detail 9) of a service flow sent by UPF4 to base station 1 of UPE1 through NPE2.

As shown in "Aggregation 3" in Figure 2b, the IOAM detail tasks (Detail 3) of a service flow sent by UPF1 to base station 2 of UPE2 through NPE1 are aggregated with the IOAM detail tasks (Detail 5 and Detail 6) of two service flows sent by UPE2 to base station 2 of UPE2 through NPE1.

As shown in "Aggregation 4" in Figure 2b, the IOAM detail task (detail 8) of a service flow sent by UPF3 to base station 2 of UPE2 through NPE2 is aggregated with the IOAM detail task (detail 10) of a service flow sent by UPF4 to base station 2 of UPE2 through NPE2.

As shown in Figure 2a and Figure 2b, by aggregating the downlink of IOAM detailed tasks, the same source device (the same NPE device) can be sent to the same destination device. (The same base station) business flow IOAM tasks are aggregated. By aggregating IOAM tasks, the number of IOAM tasks in the project can be reduced, so that server resources can be reasonably allocated, network performance is optimized, and user operation difficulty is reduced, greatly improving user experience.

In the detection task processing method of the disclosed embodiment, a new category of IOAM task, namely, aggregated IOAM task, is provided. As can be seen from the aggregation process of the detailed IOAM tasks described in combination with Figures 2a and 2b, originally multiple detailed IOAM tasks are aggregated, and the number of detailed IOAM tasks at the engineering site will only be more than the number of detailed IOAM tasks shown in Figures 2a and 2b, so the aggregation of detailed IOAM tasks is very necessary.

For the service flow in the downstream direction (the service flow from the NPE device to the UPE device), the IOAM tasks of the service flow starting from the same source device (such as the same NPE device) to the same destination device (such as the same base station) can be aggregated, thereby reducing the number of a large number of IOAM tasks in the project, thereby saving server resources, allocating server resources reasonably, optimizing network performance, reducing user operation difficulty, and greatly improving user experience.

For the service flow in the uplink direction (the service flow from the UPE device to the NPE device), for the IOAM tasks of the service flows from different base stations, the detailed IOAM tasks of the service flows with the destination network segment (the network segment to which the host network address of the service flow belongs) in the predetermined network segment interval are aggregated. Creating aggregated IOAM tasks based on network segments has the advantages of simple creation process, convenient management and high task processing efficiency. Furthermore, the reduction in the number of IOAM tasks can save server resources, so that server resources can be reasonably allocated. At the same time, when processing IOAM tasks, the cost of processing one aggregated task is much lower than processing one hundred detailed tasks. While saving resources, it improves efficiency, optimizes network performance, reduces user operation difficulty, and thus improves user experience.

According to the detection task processing method of the embodiment of the present disclosure, after using the aggregation technology for IOAM tasks, on the one hand, it is possible to operate IOAM tasks, detect traffic and manage networks more simply and conveniently; on the other hand, it is possible to be compatible with various devices. Low-end devices with relatively poor performance can support a relatively small maximum number of IOAMs. After using the aggregation technology, even if these devices are encountered, a large number of IOAM tasks can be configured through aggregation. When the aggregation technology is integrated into the IOAM task processing, it can enable large-scale deployment of IOAM tasks on the engineering site. Improve business detection mechanism.

3 , an embodiment of the present disclosure provides a detection task processing device. FIG3 is a schematic diagram of the structure of a detection task processing device provided according to an embodiment of the present disclosure. As shown in FIG3 , the detection task processing device may include a receiving module 310 and at least one processor 320 .

The receiving module 310 is configured to receive a service flow. The processor 320 is configured to: obtain an in-band detection task configured for the received service flow; determine a task aggregation type according to a direction of the service flow; and, when it is determined according to the acquired flow information of the service flow that the configured in-band detection task satisfies an aggregation condition corresponding to the task aggregation type, aggregate the configured in-band detection task with the in-band detection task that satisfies the aggregation condition to obtain an aggregated in-band detection task.

According to the detection task processing device of the embodiment of the present application, the aggregation type of in-band detection tasks can be determined according to the direction of the received business flow. If it is determined according to the flow information of the business flow that the in-band detection task of the business flow meets the corresponding aggregation condition, the in-band detection tasks that meet the aggregation condition will be aggregated to obtain the aggregated in-band detection tasks. The aggregation of in-band detection tasks can reduce the number of a large number of IOAM tasks in the project, so that server resources can be reasonably allocated, and the network performance is optimized. At the same time, it also reduces the burden of network administrators who manually issue IOAM task information, reduces the difficulty of operation, is easy to expand and has high reliability, and greatly improves the user experience.

In some embodiments, the direction of the service flow includes an uplink direction and a downlink direction. The uplink direction includes the direction from the UPE device to the NPE device, and the downlink direction includes the direction from the NPE device to the UPE device. When the processor 320 performs the step of determining the task aggregation type according to the direction of the service flow, it is configured to: when the direction of the service flow is the uplink direction, determine the task aggregation type as uplink aggregation; when the direction of the service flow is the downlink direction, determine the task aggregation type as downlink aggregation.

In some embodiments, the task aggregation type is uplink aggregation, and the processor 320 is configured to: receive a target network segment; when the target network segment is a pre-created in-band detection task, the processor 320 performs aggregation processing on the configured in-band detection task and the in-band detection task that meets the aggregation condition corresponding to the task aggregation type according to the acquired flow information of the service flow, and obtains the aggregated in-band detection task; In the case of a planned network segment, obtain the pre-created uplink aggregation task corresponding to the target network segment; add the configured in-band detection task to the uplink aggregation task to obtain the aggregated in-band detection task.

In some embodiments, the task aggregation type is uplink aggregation; the processor 320 is configured to: obtain the source network address and the host network address from the flow information of the business flow; when the network segment where the host network address is located is within the pre-created planned network segment, and the network segment where the source network address is located is not within the pre-created planned network segment, create a new uplink aggregation task based on the flow information of the business flow; add the configured in-band detection task to the created uplink aggregation task to obtain the aggregated in-band detection task, when it is determined based on the acquired flow information of the business flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type.

In some embodiments, when executing the step of creating a new uplink aggregation task based on the flow information of the business flow, the processor 320 is configured to: set basic parameters of the new uplink aggregation task according to the flow information of the business flow; wherein the basic parameters include at least one of the five-tuple information of the business flow, the task name, the task identifier and the flow identifier; take the network segment where the host network address is located as the first planned network segment, obtain the user-side port within the first planned network segment, and obtain the egress port with the first planned network segment as the target network segment from the private network routing; obtain the host port corresponding to the new uplink aggregation task according to the union of the user-side port and the egress port; take the network address contained in the first planned network segment as the host network address corresponding to the new uplink aggregation task; create a new uplink aggregation task according to the basic parameters, the port information of the host port corresponding to the new uplink aggregation task, and the host network address corresponding to the new uplink aggregation task.

In some embodiments, after executing the step of obtaining the source network address and the destination network address from the flow information of the service flow, the processor 320 is further configured to obtain the source port information and the destination port information from the flow information of the service flow, and create an in-band detection task for the service flow from the source port to the destination port, when the network segment where the destination network address is located and the network segment where the source network address is located are both within the pre-created planned network segment, or when neither is within the pre-created planned network segment.

In some embodiments, the task aggregation type is downlink aggregation, and the processor 320 performs The method comprises the following steps: when it is determined that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type according to the acquired flow information of the service flow, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, and the in-band detection task is configured to: obtain the parameter information of the in-band detection task corresponding to the service flow as the parameter query information; wherein the parameter query information includes at least the virtual routing forwarding information and the host network address corresponding to the service flow; when the parameter query information is queried from the parameter information of the created downlink aggregation task, the source port information of the service flow is obtained; when the source port information of the service flow is queried from the port information of the access controller of the created downlink aggregation task, the in-band detection task contained in the created downlink aggregation task is used as the aggregated in-band detection task.

In some embodiments, after executing the step of obtaining the source port information of the service flow, the processor 320 is further configured to execute the following steps: if the source port information of the service flow is not queried from the port information of the access controller of the created downlink aggregation task, after adding the source port information of the service flow to the port information of the access controller, the in-band detection task included in the created downlink aggregation task is used as the aggregated in-band detection task.

In some embodiments, the parameter query information also includes at least one of the following information items of the business flow: host node information, network address family, protocol number, source port number, wherein the source port to which the source port number belongs is a port of a communication protocol that supports in-band detection task aggregation.

According to the detection task processing module of the embodiment of the present application, for the service flow in the downlink direction (the service flow from the NPE device to the UPE device), the IOAM tasks of the service flow starting from the same source device (for example, the same NPE) to the same destination device (for example, the same base station) can be aggregated, thereby reducing the number of a large number of IOAM tasks in the project, thereby saving server resources, allocating server resources reasonably, optimizing network performance, reducing user operation difficulty, and greatly improving user experience.

According to the detection task processing module of the embodiment of the present application, for the uplink service flow (service flow from UPE device to NPE device), for the IOAM tasks of service flows from different base stations, the detailed IOAM tasks of the service flows with the destination network segment (the network segment to which the host network address of the service flow belongs) in the predetermined network segment interval are aggregated. Creating aggregated IOAM tasks based on network segments has the advantages of simple creation process, convenient management and efficient task processing. Furthermore, the reduction in the number of IOAM tasks can save server resources and allow server resources to be reasonably allocated. At the same time, when processing IOAM tasks, the cost of processing an aggregate task is much lower than processing a hundred detailed tasks. While saving resources, it improves efficiency, optimizes network performance, reduces user operation difficulty, and thus improves user experience.

A processor is a device with data processing capabilities, including but not limited to a central processing unit (CPU); a memory 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); an I/O interface (read-write interface) is connected between the processor and the memory, and can realize information exchange between the memory and the processor, including but not limited to a data bus (Bus), etc.

It should be clear that the present invention is not limited to the specific configurations and processes described in the above embodiments and shown in the figures. For the convenience and brevity of description, a detailed description of the known methods is omitted here, and the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, which will not be repeated here.

FIG. 4 is a structural diagram of an exemplary hardware architecture of an electronic device capable of implementing the detection task processing method and apparatus according to an embodiment of the present invention.

As shown in Fig. 4, the electronic device 400 includes an input device 401, an input interface 402, a central processing unit 403, a memory 404, an output interface 405, and an output device 406. The input interface 402, the central processing unit 403, the memory 404, and the output interface 405 are connected to each other via a bus 410, and the input device 401 and the output device 406 are connected to the bus 410 via the input interface 402 and the output interface 405, respectively, and then connected to other components of the electronic device 400.

Specifically, the input device 401 receives input information from the outside, and transmits the input information to the central processing unit 403 through the input interface 402. The central processing unit 403 processes the input information based on the computer executable instructions stored in the memory 404 to generate output information, stores the output information temporarily or permanently in the memory 404, and then transmits the output information to the output device 406 through the output interface 405. The output device 406 outputs the output information to the outside of the electronic device 400 for the user to use.

In one embodiment, the electronic device shown in FIG4 may include: one or more A memory and one or more processors; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, the following steps are implemented: obtaining an in-band detection task configured for a received business flow; determining a task aggregation type according to a direction of the business flow; and when it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task satisfies an aggregation condition corresponding to the task aggregation type, aggregating the configured in-band detection task with the in-band detection task that satisfies the aggregation condition to obtain an aggregated in-band detection task.

In some embodiments, the electronic device may also execute any of the detection task processing methods described in the above embodiments.

The above are only exemplary embodiments of the present application and are not intended to limit the scope of protection of the present application. In general, various embodiments of the present application can be implemented in hardware or special circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

The block diagram of any logic flow in the accompanying drawings of the present application can represent program steps, or can represent interconnected logic circuits, modules and functions, or can represent a combination of program steps and logic circuits, modules and functions. The computer program can be stored on a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory device and system (digital versatile disc DVD or CD disc), etc. Computer-readable media may include non-transient storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FGPA) and a processor based on a multi-core processor architecture.

By way of exemplary and non-limiting examples, the foregoing description has provided an exemplary embodiment of the present application. Detailed description of the embodiments. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the drawings and claims, but will not depart from the scope of the invention. Therefore, the proper scope of the invention will be determined according to the claims.

Claims (11)

1. A detection task processing method, comprising:

   Obtaining the in-band detection task configured for the received service flow;

   Determining a task aggregation type according to the direction of the business flow; and

   When it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task.
2. The method according to claim 1, wherein the direction of the service flow includes an uplink direction and a downlink direction, the uplink direction is the direction from the user-side operator edge device to the network-side operator edge device, the downlink direction is the direction from the network-side operator edge device to the user-side operator edge device, and

   Wherein, determining the task aggregation type according to the direction of the business flow includes:

   In a case where the direction of the service flow is the uplink direction, determining that the task aggregation type is uplink aggregation; and

   When the direction of the service flow is the downlink direction, the task aggregation type is determined to be downlink aggregation.
3. The method according to claim 1, wherein the task aggregation type is uplink aggregation, and

   Wherein, when it is determined according to the acquired flow information of the service flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including:

   Receive the target network segment;

   In the case where the target network segment is a pre-created and planned network segment, obtaining a pre-created uplink aggregation task corresponding to the target network segment; and

   Add the configured in-band detection task to the uplink aggregation task, and obtain Aggregated in-band detection tasks.
4. The method according to claim 1, wherein the task aggregation type is uplink aggregation, and

   Wherein, when it is determined according to the acquired flow information of the service flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including:

   Acquire a source network address and a destination network address from the flow information of the service flow;

   When the network segment where the destination network address is located is within the pre-created planned network segment, and the network segment where the source network address is located is not within the planned network segment, creating a new uplink aggregation task based on the flow information of the service flow; and

   The configured in-band detection task is added to the new uplink aggregation task to obtain the aggregated in-band detection task.
5. The method according to claim 4, wherein creating a new uplink aggregation task based on the flow information of the service flow comprises:

   Setting basic parameters of the new uplink aggregation task according to the flow information of the service flow, wherein the basic parameters include at least one of quintuple information of the service flow, a task name, a task identifier, and a flow identifier;

   Taking the network segment where the destination network address is located as a first planned network segment, obtaining a user-side port in the first planned network segment, and obtaining an egress port with the first planned network segment as a target network segment from a private network route;

   Obtaining a sink port corresponding to the new uplink aggregation task according to a union of the user-side port and the egress port;

   Using the network address included in the first planned network segment as the sink network address corresponding to the new uplink aggregation task; and

   The new uplink aggregation task is created according to the basic parameters, the port information of the sink port corresponding to the new uplink aggregation task, and the sink network address corresponding to the new uplink aggregation task.
6. The method according to claim 4, wherein after obtaining the source network address and the destination network address from the flow information of the service flow, the method further comprises:

   When the network segment where the destination network address is located and the network segment where the source network address is located are both within the planned network segment, or when neither is within the planned network segment, the source port information and the destination port information are obtained from the flow information of the service flow, and an in-band detection task for the service flow from the source port to the destination port is created.
7. The method according to claim 1, wherein the task aggregation type is downlink aggregation, and

   Wherein, when it is determined according to the acquired flow information of the service flow that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task, including:

   Acquire parameter information of the in-band detection task corresponding to the service flow as parameter query information, wherein the parameter query information at least includes: virtual routing forwarding information and a sink network address corresponding to the service flow;

   When the parameter query information is queried from the parameter information of the created downlink aggregation task, the source port information of the service flow is acquired; and

   When the source port information of the service flow is queried from the port information of the access controller of the created downlink aggregation task, the in-band detection task included in the created downlink aggregation task is used as the aggregated in-band detection task.
8. The method according to claim 7, wherein, after obtaining the source port information of the service flow, the method further comprises:

   In the case that the source port information of the service flow is not found from the port information of the access controller of the created downlink aggregation task,

   After the source port information of the service flow is added to the port information of the access controller, the in-band detection task included in the created downlink aggregation task is used as the aggregated in-band detection task.
9. According to the method of claim 7, the parameter query information also includes at least one of the following information items of the business flow: host node information, network address family, protocol number, source port number; wherein the source port to which the source port number belongs is a port of a communication protocol that supports in-band detection task aggregation.
10. An electronic device comprises one or more memories and one or more processors, wherein the memories store a computer program executable by the processors, and when the computer program is executed by the processors, the following steps are implemented:

    Obtaining the in-band detection task configured for the received service flow;

    Determine the task aggregation type according to the direction of the business flow;

    When it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task.
11. A computer readable medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

    Obtaining the in-band detection task configured for the received service flow;

    Determine the task aggregation type according to the direction of the business flow;

    When it is determined, based on the acquired flow information of the business flow, that the configured in-band detection task meets the aggregation condition corresponding to the task aggregation type, the configured in-band detection task is aggregated with the in-band detection task that meets the aggregation condition to obtain the aggregated in-band detection task.