Service guarantee method and electronic equipment

By setting service level target SLO in the operation and maintenance management system and determining abnormal points in the network equipment to send guarantee instructions, the problem that EMS operation and maintenance capabilities in large network scenarios cannot guarantee low latency and high reliability in vertical industries is solved, and more efficient business guarantee and reliability are achieved.

CN120128955APending Publication Date: 2025-06-10ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311691816.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-12-08
Publication Date
2025-06-10

AI Technical Summary

Technical Problem

The EMS operation and maintenance capabilities that use large network scenarios in the prior art cannot guarantee the low latency and high reliability requirements of vertical industries.

Method used

A business guarantee method is proposed, by setting a service level target SLO based on the service connection request in the operation and maintenance management system, and sending the SLO to the network equipment, determining the network abnormal point, and sending the guarantee instructions to perform business guarantee.

Benefits of technology

By setting the SLO when establishing the connection service, the network equipment can perform self-guarantee based on the SLO, quickly determine the abnormal points and provide business guarantees when network abnormalities occur, improving the guarantee efficiency and business reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120128955A_ABST
    Figure CN120128955A_ABST
Patent Text Reader

Abstract

The invention discloses a service guarantee method and electronic equipment, and belongs to the field of network operation and maintenance management. The service guarantee method is applied to an operation and maintenance management system, and comprises the following steps: setting a service level target SLO based on a service target in a service connection request, and sending the SLO to network equipment, the service connection request being used for creating a connection service; determining a network abnormal point in the connection service based on the received service data sent by the network device; and sending a guarantee instruction to the network equipment based on the network abnormal point, wherein the guarantee instruction is used for indicating the network equipment to carry out service guarantee.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of network operation and maintenance management, and particularly relates to a service guarantee method and an electronic device. Background Art

[0002] In the related art, for the 5G private network service level objectives (SLOs), the operation and maintenance capabilities of the element management system (EMS) in the operator's large network scenario are basically relied on. When an SLO exception occurs, a passive demarcation and location process is generally adopted, that is, after a failure occurs, it is analyzed and processed by operation and maintenance personnel, resulting in a long time to solve the problem. When using the 5G private network in vertical industries, low latency and high reliability requirements are put forward for the 5G industry private network. At this time, if the EMS operation and maintenance capabilities in the large network scenario are still used, the low latency and high reliability requirements of vertical industries cannot be guaranteed. Summary of the Invention

[0003] This application aims to provide a service guarantee method and an electronic device, at least solving the problem that the EMS operation and maintenance capabilities in the large network scenario in the related art cannot guarantee the low latency and high reliability requirements of vertical industries.

[0004] In a first aspect, an embodiment of this application proposes a service guarantee method, which is applied to an operation and maintenance management system. The method includes:

[0005] Set a service level objective SLO based on the service objective in the service connection request, and send the SLO to a network device. The service connection request is used to create a connection service;

[0006] Determine a network anomaly point in the connection service based on the service data received from the network device;

[0007] Send a guarantee instruction to the network device based on the network anomaly point. The guarantee instruction is used to instruct the network device to perform service guarantee.

[0008] In a second aspect, an embodiment of this application proposes a service guarantee method, which is applied to a first network device. The method includes:

[0009] Receive the SLO sent by the operation and maintenance management system or the sub-SLO and the service packet feature model sent by a second network device. The SLO is the target corresponding to the connection service, and the service packet feature model is a model determined by the second network device based on the service packet features corresponding to the type of the connection service;

[0010] Collect service data based on the SLO or the sub-SLO;

[0011] Perform service self - assurance based on the SLO, the sub - SLO, the service message feature model, and the service data;

[0012] In the case of service self - assurance failure, send the service data to the operation and maintenance management system, or send the service data and the assurance failure information to the operation and maintenance management system and the second network device;

[0013] Receive the assurance instruction sent by the operation and maintenance management system based on the service data;

[0014] Perform service assurance according to the assurance instruction.

[0015] In a third aspect, an embodiment of the present application proposes a service assurance method applied to a second network device, and the method includes:

[0016] Receive the SLO sent by the operation and maintenance management system, and determine multiple sub - SLOs based on the SLO, where the SLO is the target corresponding to the connection service;

[0017] Obtain the preset service message features based on the type of the connection service;

[0018] Determine the service message feature model based on the service message features;

[0019] Send multiple sub - SLOs and the service message feature model to the first network device, so that the first network device performs service self - assurance based on the sub - SLO and the service message feature model.

[0020] In a fourth aspect, an embodiment of the present application proposes an electronic device, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, it implements the steps of the method as described in the first aspect, or implements the steps of the method as described in the second aspect, or implements the steps of the method as described in the third aspect.

[0021] In a fifth aspect, an embodiment of the present application proposes a storage medium, characterized in that a program or instruction is stored on the storage medium, and when the program or instruction is executed by a processor, it implements the steps of the method as described in the first aspect, or implements the steps of the method as described in the second aspect, or implements the steps of the method as described in the third aspect.

[0022] In a sixth aspect, a chip is provided, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect, or implement the steps of the method as described in the third aspect.

[0023] In a seventh aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0024] In an embodiment of the present application, first, a service level objective (SLO) is set based on the service objective in the service connection request, and the SLO is sent to the network device. The service connection request is used to create a connection service. Then, based on the service data sent by the received network device, the network anomaly points in the connection service are determined. Finally, a guarantee instruction is sent to the network device based on the network anomaly points. The guarantee instruction is used to instruct the network device to perform service guarantee. In the embodiment of the present application, the SLO is set when establishing the connection service, so that the network device is instructed to perform self-guarantee based on the SLO. When a network anomaly occurs in the connection service, the network anomaly points are determined, and a guarantee instruction is sent to the network device based on the anomaly points, so that the network device can perform service guarantee based on the guarantee instruction. By the service guarantee of the network device, the guarantee efficiency is improved and the reliability of the service is enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 is a schematic flowchart of a service guarantee method provided by an embodiment of the present application;

[0026] Figure 2 is a schematic flowchart of another service guarantee method provided by an embodiment of the present application;

[0027] Figure 3 is a schematic flowchart of yet another service guarantee method provided by an embodiment of the present application;

[0028] Figure 4 is a detailed schematic flowchart of a service guarantee method provided by an embodiment of the present application;

[0029] Figure 5 is a structural block diagram of a service guarantee system provided by an embodiment of the present application;

[0030] Figure 6 is a schematic diagram of a service guarantee process provided by an embodiment of the present application;

[0031] Figure 7 is a schematic structural diagram of a service guarantee device provided by an embodiment of the present application;

[0032] Figure 8 is a schematic structural diagram of another service guarantee device provided by an embodiment of the present application;

[0033] Figure 9 It is a schematic structural diagram of another service guarantee device provided by an embodiment of the present application;

[0034] Figure 10 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0035] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary only for explaining the present application and should not be construed as a limitation to the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0036] The terms "first" and "second" in the description and claims of the present application may explicitly or implicitly include one or more of such features. In the description of the present application, unless otherwise specified, the meaning of "a plurality" is two or more. In addition, "and / or" in the description and claims means at least one of the connected objects, and the character " / " generally means an "or" relationship between the associated objects before and after.

[0037] In the description of the present application, it should be understood that the orientation or positional relationship indicated by the terms "center", "longitudinal", "transverse", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc. is based on the orientation or positional relationship shown in the accompanying drawings, and is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as a limitation to the present application.

[0038] In the description of the present application, it should be noted that unless otherwise clearly specified and limited, the terms "mounted", "connected" and "connected" should be understood in a broad sense. For example, it may be a fixed connection, a detachable connection, or an integral connection; it may be a mechanical connection or an electrical connection; it may be directly connected, or indirectly connected through an intermediate medium, and it may be the communication inside two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to specific situations.

[0039] The following combines the attached Figures 1 to 10, the service guarantee method and electronic device provided by the embodiments of the present application are described in detail through specific embodiments and their application scenarios.

[0040] Figure 1 It is a schematic flowchart of a service guarantee method provided by an embodiment of the present application. As Figure 1 shown, this service guarantee method is applied to an operation and maintenance management system, and this service guarantee method may include the content shown in S101 to S103.

[0041] In S101, a service level objective SLO is set based on the service objective in the service connection request, and the SLO is sent to the network device. The service connection request is used to create a connection service.

[0042] Among them, the connection service refers to an end-to-end connection relationship. The service connection request carries the terminal address and / or application address. The end-to-end connection relationship may refer to the connection relationship from a single 5G module terminal customer premise equipment (CPE) to an industry application, or may refer to the connection relationship from a dual 5G module terminal CPE in a frame replication and elimination for reliability (FRER) mode to an industry application, or may also refer to the connection relationship from a 5G terminal to a 5G terminal. The SLO is determined according to the type of the connection service. Different connection services correspond to different SLOs. The SLO may include delay, reliability, delay jitter, etc., and specifically can be determined according to the actual application. This embodiment does not make a limitation.

[0043] In S102, the network anomaly points in the connection service are determined based on the service data sent by the received network device.

[0044] Among them, network anomaly means that the actual reliability of the industry service is lower than the reliability set by the SLO, and the delay is greater than the delay set by the SLO. For example, if the reliability set by the SLO is 99.999%, and the delay is 20 ms, while the actual reliability is lower than 99.99%, and the delay is 30 ms, it indicates that there is a network anomaly and the network anomaly points need to be determined.

[0045] In S103, a guarantee instruction is sent to the network device based on the network anomaly points. The guarantee instruction is used to instruct the network device to perform service guarantee.

[0046] It should be noted that the guarantee instructions can be divided into two categories. One is network optimization or expansion to reduce abnormal points at the network level, which involves network expansion, neighboring cell adjustment, and radio parameter adjustment. The other is the adjustment of service guarantee objectives related to service connections to optimize radio air interface scheduling, which involves the adjustment of 5G service quality indicators (5QIs) and service indicator adjustment (such as segment delay). Specifically, it will be described in detail in the following embodiments.

[0047] In the embodiment of the present application, first, a service level objective (SLO) is set based on the service objective in the service connection request, and the SLO is sent to the network device. The service connection request is used to create a connection service. Then, based on the service data received from the network device, the network abnormal points in the connection service are determined. Finally, a guarantee instruction is sent to the network device based on the network abnormal points. The guarantee instruction is used to instruct the network device to perform service guarantee. In the embodiment of the present application, the SLO is set when the connection service is established, so that the network device is instructed to perform self-guarantee based on the SLO. When network abnormalities occur in the connection service, the network abnormal points are determined, and a guarantee instruction is sent to the network device based on the abnormal points, so that the network device can perform service guarantee based on the guarantee instruction. The guarantee efficiency is improved through the service guarantee of the network device, and the reliability of the service is enhanced.

[0048] In a possible implementation manner of the present application, before setting the service level objective (SLO) based on the service objective in the service connection request, the method may further include: when receiving a service connection request, creating a terminal-to-terminal or terminal-to-application connection service according to the terminal address and / or application address, where the terminal address and / or application address are carried in the service connection request.

[0049] That is to say, the connection service can be a terminal-to-terminal connection service or a terminal-to-application connection service, which can be specifically determined according to the address information carried in the service connection request. Correspondingly, the SLO can be a terminal-level SLO or an application-level SLO. The network device can determine how to decompose the SLO into multiple sub-SLOs according to the SLO corresponding to the type of the connection service to better perform service guarantee.

[0050] The network device can be a single network device (i.e., the main network device). The main network device can perform service guarantee according to the SLO sent by the operation and maintenance management system. In the case where the main network device cannot perform service guarantee, it can jointly perform service guarantee with the cooperative network device. Specifically, in a possible implementation manner of the present application, the network device includes a first network device and a second network device; sending the SLO to the network device may include: sending the SLO to the second network device, so that the second network device determines multiple sub-SLOs based on the SLO and sends them to the first network device. The sub-SLO is the segmented guarantee objective of the SLO.

[0051] That is to say, if network devices are divided into a main network device (the first network device) and a collaborative network device (the second network device), the operation and maintenance management system sends the SLO to the collaborative network device. The collaborative network device decomposes the SLO into multiple sub-SLOs according to the type of the SLO. Among them, the multiple sub-SLOs respectively correspond to multiple segments between the end-to-end of the connected service. That is, the collaborative network device can be divided into multiple segments according to the network elements involved between the end-to-end of the connected service, or can be decomposed into multiple segments according to different network topologies. Specifically, it can be determined according to actual applications, and this embodiment does not make a limitation. The collaborative network device sends the multiple sub-SLOs to the main network device, so that the main network device performs segmented service guarantee according to the multiple sub-SLOs. The segmented service guarantee can more quickly determine network anomaly points, and then more quickly perform service guarantee on the network anomaly points to make it resume normal operation and make the connected service more stable.

[0052] For example, if the connected service is a connection from a terminal to an application, it is divided into several parts such as from the terminal to the air interface, inside the base station, from the base station to the collaborative network device, inside the collaborative network device, and from the collaborative network device to the application. Correspondingly, the SLO can be divided into five sub-SLOs.

[0053] In a possible implementation manner of this application, after sending the SLO to the network device, the service guarantee method may further include: receiving service data sent by the first network device, where the service data includes service level measurement indicators (Service Level Identifier, SLI), statistical data, alarms, status, signaling messages, and black box information.

[0054] Among them, the black box information refers to information such as an anomaly point location conclusion generated by the network device according to the analysis products (such as anomaly association rules, corresponding 5QI policies, fault points, etc.) obtained during the self-guarantee process when performing service self-guarantee.

[0055] In this embodiment, the operation and maintenance management system sends the SLO to the second network device. The second network device decomposes the SLO into multiple sub-SLOs. The second network device sends the multiple sub-SLOs to the first network device. The first network device can perform segmented service guarantee according to the multiple sub-SLOs. The first network device can send the collected service data to the operation and maintenance management system, so that the operation and maintenance management system determines the network anomaly points in the connected service according to the service data, and then sends a guarantee instruction to instruct the first network device to perform service guarantee, ensuring the stability and reliability of the connected service.

[0056] In a possible implementation of the present application, determining a network anomaly point in a connection service based on service data received from a network device may include: determining whether the reception and / or transmission of a terminal device in the connection service is abnormal; if the reception and / or transmission of the terminal device is abnormal, extracting statistical data associated with the terminal device in the service data, as well as alarms, statuses, signaling messages, and black box information sent by the terminal device; in the case where the statistical data, alarms, statuses, signaling messages, and / or black box information is abnormal, determining the network anomaly point in the connection service as the terminal device; in the case where the network anomaly point is a non-terminal device, analyzing the network anomaly point and tracing the root cause of the anomaly point based on service level measurement indicators SLI, SLO, a preset guarantee threshold, and the status of the network device, so as to determine the network anomaly point in the connection service.

[0057] It should be noted that according to historical data, most (80% - 90%) of the anomalies occur in terminal devices (CPE). Therefore, it is possible to preferentially analyze the group or individual faults of CPE, which can be determined by whether the reception and / or transmission of the terminal device in the connection service is abnormal. If the reception and / or transmission of the terminal device is abnormal, extract the statistical data associated with the terminal device in the service data, as well as data such as alarms, statuses, signaling messages, and black box information sent by the terminal device. That is, judge the information of the terminal device obtained by the network device and the information of the terminal device itself sent by the terminal device to the network device, and then judge whether the anomaly point is in the terminal device. If through the above judgment, the anomaly point is not in the terminal device, that is, in the case of a non-terminal device, based on SLI, SLO, a preset guarantee threshold, and the status of the network device in the service data, analyze the network anomaly point and trace the root cause of the anomaly point through preset or dynamically learned association rules, AI algorithms, etc., so as to determine the network anomaly point in the connection service.

[0058] In the case where it is detected that the SLI of the connection service does not meet the SLO, or the downward trend of the SLI exceeds the guarantee threshold, it is determined that a network anomaly has occurred in the connection service, and then the network anomaly point is analyzed and the root cause of the anomaly point is traced, so as to determine the network anomaly point in the connection service.

[0059] In a possible implementation of the present application, sending a guarantee instruction to a network device based on a network anomaly point may include: in the case where the network anomaly point is a non-terminal device, generating a service anomaly feature based on the network anomaly point and the network anomaly phenomenon; generating a network optimization or expansion instruction, or generating an instruction to adjust the service guarantee target of the service connection based on the service anomaly feature; sending the network optimization or expansion instruction, or the instruction to adjust the service guarantee target of the service connection, to the network device; receiving the analysis conclusion and guarantee result returned by the network device.

[0060] In this embodiment, when it is determined that the network anomaly point is not a terminal device, service anomaly features can be generated based on the network anomaly point and the network anomaly phenomenon. The service anomaly features can include network - related anomalies such as interference, coverage, capacity, etc.; the service anomaly features can also include radio - interface - related anomalies such as latency anomaly, packet re - transmission, block error rate (BLER) anomaly, etc. Corresponding safeguard instructions are generated according to the above - mentioned different service anomaly features. For example, network optimization or capacity expansion instructions are generated, or service safeguard target adjustment instructions for service connections are generated, and sent to the network device to instruct the network device to perform service safeguard. Then, the analysis conclusion and safeguard result returned by the network device are received.

[0061] That is to say, the network device can perform service self - safeguard according to the SLO sent by the operation and maintenance management system. That is, in the case of detecting an anomaly, it can dynamically adjust the Quality of Service (QoS) control strategy, adjust the radio - interface scheduling strategy and resource allocation of network elements for service self - safeguard, so as to achieve the SLO. In the case of the network device's safeguard failure, it can report to the operation and maintenance management system. The operation and maintenance management system determines the network anomaly point, generates service anomaly features based on the network anomaly point and the network anomaly phenomenon, and generates a positioning / self - healing processing execution instruction set, that is, a safeguard instruction, to perform operations such as diagnostic analysis, policy adjustment, parameter modification, and action on the network element device. The safeguard instructions can be divided into two categories. One category is network optimization or capacity expansion to reduce the network - level anomaly points, involving network capacity expansion, neighbor cell adjustment, radio parameter adjustment, etc.; the other category is the adjustment of service safeguard targets related to service connections to optimize radio - interface scheduling, involving 5QI adjustment, service index adjustment (such as segment latency), etc.

[0062] In a possible implementation manner of the present application, the service safeguard method may further include: when the safeguard result returned by the network device is a safeguard failure, generating a manual intervention processing suggestion according to the network anomaly point, network anomaly phenomenon, service anomaly features, service safeguard process, and service data after service safeguard in the analysis conclusion; updating the network anomaly point, network anomaly phenomenon, service anomaly features, service safeguard process, service data after service safeguard, manual intervention processing suggestion, and execution result in the analysis conclusion to a preset fault tree knowledge base.

[0063] That is to say, if the operation and maintenance management system sends a guarantee instruction to the network device, and the network device fails to guarantee the service after performing service guarantee according to the guarantee instruction, it is necessary to analyze the network anomaly points, network anomaly phenomena, service anomaly characteristics, service guarantee process, and service data after service guarantee in the analysis conclusion returned by the network device, and then generate suggestions for manual intervention for processing by operation and maintenance personnel to ensure the normal operation of the connection service. It is also possible to update information such as network anomaly points, network anomaly phenomena, service anomaly characteristics, service guarantee process, service data after service guarantee, suggestions for manual intervention, and execution results in the analysis conclusion to a preset fault tree knowledge base, so that in the event of the same or similar network anomalies, corresponding processing can be carried out, thereby improving the service guarantee efficiency.

[0064] Figure 2 It is a schematic flowchart of a service guarantee method provided by an embodiment of the present application. As Figure 2 shown, this service guarantee method is applied to the first network device, that is, the main network device, and this service guarantee method may include the content shown in S201 to S206.

[0065] In S201, receive the SLO sent by the operation and maintenance management system or the sub-SLO and service message feature model sent by the second network device.

[0066] Among them, the SLO is the target corresponding to the connection service, and the service message feature model is a model determined by the second network device based on the service message features corresponding to the type of the connection service. The sub-SLO is decomposed by the second network device (i.e., the collaborative network device) according to the type of the SLO. Specifically, it has been described in detail in the above embodiment and will not be repeated in this embodiment. For details, refer to the above text.

[0067] In S202, collect service data based on the SLO or sub-SLO.

[0068] In S203, perform service self-guarantee according to the SLO, sub-SLO, service message feature model, and service data.

[0069] Among them, service self-guarantee refers to the closed-loop guarantee performed by the first network device based on the obtained data, which can guarantee the reliable operation of the connection service without the assistance of external devices, making the SLO or sub-SLO reachable.

[0070] In S204, in the case of service self-guarantee failure, send the service data to the operation and maintenance management system, or send the service data and guarantee failure information to the operation and maintenance management system and the second network device.

[0071] That is to say, in the case of the failure of the self-guarantee of the first network device service, the operation and maintenance management system, or the operation and maintenance management system and the second network device need to intervene to jointly perform service guarantee to ensure the reliability of the connection service, that is, to make the SLO or sub-SLO reachable.

[0072] In S205, a guarantee instruction sent by the operation and maintenance management system is received based on service data.

[0073] In S206, service guarantee is performed according to the guarantee instruction.

[0074] In the embodiment of the present application, first, the SLO sent by the operation and maintenance management system or the sub-SLO and the service message feature model sent by the second network device are received, then based on the SLO or sub-SLO, service data is collected, and according to the SLO, sub-SLO, service message feature model and service data, service self-guarantee is performed. In the case of the failure of service self-guarantee, the service data is sent to the operation and maintenance management system, or the service data and the guarantee failure information are sent to the operation and maintenance management system and the second network device. Finally, a guarantee instruction sent by the operation and maintenance management system is received based on the service data, and service guarantee is performed according to the guarantee instruction. In the embodiment of the present application, the first network device can perform service self-guarantee based on the SLO sent by the operation and maintenance management system or the sub-SLO and the service message feature model sent by the second network device, ensure the reliable operation of the connection service, make the SLO or sub-SLO reachable, and in the case of the failure of self-guarantee, service guarantee can be performed based on the guarantee instruction sent by the operation and maintenance management system. Through multiple guarantee methods, the guarantee efficiency can be improved and the reliability of the service can be enhanced.

[0075] In a possible implementation manner of the present application, performing service self-guarantee according to the SLO, sub-SLO, service message feature model and service data may include: performing data correlation analysis on the signaling messages and statistical data in the service data corresponding to the SLO, analyzing network anomaly points and tracing the root cause of the anomaly points to determine the network anomaly points in the connection service; based on the SLO, network anomaly points, service anomaly features, and the corresponding relationship between the service anomaly features and the trained adjustment strategies, adjusting the priority of the quality of service QoS, radio air interface and resource scheduling strategies corresponding to the network anomaly points.

[0076] That is to say, the first network device can perform self-guarantee based on the SLO sent by the operation and maintenance management system, and adjust the priority of the quality of service QoS, radio air interface and resource scheduling strategies corresponding to the network anomaly points to ensure that the SLO is reachable.

[0077] In a possible implementation manner of the present application, performing service self-guarantee according to the SLO, sub-SLO, service message feature model, and service data may include: performing data correlation analysis on signaling messages and statistical data in the service data corresponding to the sub-SLO, analyzing network anomaly points and tracing the root causes of the anomaly points to determine the network anomaly points in the connection service; based on the sub-SLO, service message feature model, network anomaly points, service anomaly features, and the corresponding relationship between the service anomaly features and the trained adjustment strategies, adjusting the priority of QoS, radio air interface, and resource scheduling strategies corresponding to the network anomaly points.

[0078] In this embodiment, when the first network device fails in self-guarantee, it may jointly perform service guarantee with the second network device. That is, the second network device decomposes the SLO into multiple sub-SLOs based on the operation and maintenance management system and sends them. The first network device obtains the corresponding service data based on the sub-SLOs sent by the second network device, then performs data correlation analysis on the signaling messages and statistical data in the service data corresponding to the sub-SLO, analyzes network anomaly points and traces the root causes of the anomaly points to determine the network anomaly points in the connection service, and further adjusts the priority of QoS, radio air interface, and resource scheduling strategies corresponding to the network anomaly points to ensure that each sub-SLO is reachable and improve the reliability of the connection service.

[0079] In a possible implementation manner of the present application, performing service guarantee according to the guarantee instruction may include: receiving a network optimization or expansion instruction sent by the operation and maintenance management system; based on the network optimization or expansion instruction, adjusting network coverage, cell neighboring cells, and network service strategies to reduce network interference and handover frequency and improve network capacity.

[0080] That is to say, for the two types of guarantee instructions of the operation and maintenance management system, the first network device adopts different adjustment strategies. That is, for the network optimization or expansion instruction, it adjusts network coverage, cell neighboring cells, and network service strategies to reduce network interference and handover frequency and improve network capacity. For the second type of instruction of the operation and maintenance management system, as follows.

[0081] In a possible implementation manner of the present application, business guarantee according to a guarantee instruction may include: receiving a business guarantee target adjustment instruction of a business connection sent by an operation and maintenance management system; determining a plurality of sub-SLOs based on the terminal-level SLO and application-level SLO sent by the operation and maintenance management system; adjusting the sub-SLOs based on the business guarantee target adjustment instruction of the business connection; determining a message feature model according to the business message features in business data; performing data correlation analysis on signaling messages and statistical data in the business data, analyzing network anomaly points and tracing the root cause of the anomaly points to determine network anomaly points in the connection business; and adjusting the Qos priority, radio air interface, and resource scheduling strategy corresponding to the network anomaly points based on the business message feature model, the adjusted sub-SLOs, the network anomaly points, the business anomaly features, and the corresponding relationship between the business anomaly features and the trained adjustment strategies.

[0082] In this embodiment, for the second type of guarantee instruction of the operation and maintenance management system, that is, the business guarantee target adjustment instruction of the business connection, the business guarantee target, that is, SLO or sub-SLO, is adjusted based on the business guarantee target adjustment instruction of the business connection, and self-guarantee is performed again. Business data is collected, anomaly points are determined, and based on the business message feature model, the adjusted sub-SLOs, the network anomaly points, the business anomaly features, and the corresponding relationship between the business anomaly features and the trained adjustment strategies, the Qos priority, radio air interface, and resource scheduling strategy corresponding to the network anomaly points are adjusted to ensure that the SLO or sub-SLO is reachable.

[0083] Furthermore, the business guarantee result can be fed back to the operation and maintenance management system, or the operation and maintenance management system and the second network device. In the case of business guarantee failure, that is, the predetermined target cannot be achieved, an anomaly root cause location conclusion is output based on the analysis products during the guarantee process (such as anomaly association rules, corresponding 5QI strategies, and fault points), forming black box information and reporting it to the operation and maintenance management system.

[0084] Figure 3 It is a schematic flowchart of a business guarantee method provided by an embodiment of the present application. As Figure 3 shown, this business guarantee method is applied to the second network device, that is, the collaborative network device, and this business guarantee method may include the content shown in S301 to S304.

[0085] In S301, an SLO sent by the operation and maintenance management system is received, and a plurality of sub-SLOs are determined based on the SLO. The SLO is the target corresponding to the connection business.

[0086] Among them, the sub-SLOs are decomposed by the second network device according to the type of the SLO, and are specifically described in detail in the above embodiment and will not be repeated in this embodiment. See the above for details.

[0087] In S302, based on the type of the connection service, obtain the preset service message features.

[0088] Among them, the preset service message features correspond to the connection service. The corresponding service message features can be obtained according to the type of the connection service. If the subsequent service message features are updated, the updated service message features can be updated to the preset position for subsequent acquisition and use.

[0089] In S303, based on the service message features, determine the service message feature model.

[0090] In S304, send multiple sub-SLOs and the service message feature model to the first network device, so that the first network device performs service self-guarantee based on the sub-SLOs and the service message feature model.

[0091] In the embodiment of the present application, first receive the SLO sent by the operation and maintenance management system, and determine multiple sub-SLOs based on the SLO. The SLO is the target corresponding to the connection service. Then, based on the type of the connection service, obtain the preset service message features, and based on the service message features, determine the service message feature model. Finally, send multiple sub-SLOs and the service message feature model to the first network device, so that the first network device performs service self-guarantee based on the sub-SLOs and the service message feature model. In this embodiment, the second network device can decompose the SLO sent by the operation and maintenance management system into multiple sub-SLOs, so that the first network device can perform service self-guarantee in segments based on the multiple sub-SLOs, improving the reliability of the connection service.

[0092] In a possible implementation manner of the present application, the service guarantee method may further include: based on the connection service, statistically analyze the service messages of the connection service to obtain the corresponding service message features and the service message feature model; update the service message features to the preset service message features; based on the service message features and the preset period, obtain the SLI corresponding to the SLO or sub-SLO, and report the SLI to the operation and maintenance management system.

[0093] That is to say, the second network device can statistically analyze the service messages of the connection service to obtain the corresponding service message features and the service message feature model, and update them to the preset service message features for subsequent use. The second network device can also periodically obtain the SLI corresponding to the SLO or sub-SLO based on the service message features and the preset period (such as 5s), and report the SLI to the operation and maintenance management system, so that the operation and maintenance management system can determine the network anomaly points.

[0094] In a possible implementation of the present application, the service guarantee method may further include: when it is detected that the SLI of the connection service does not meet the SLO, or the downward trend of the SLI exceeds the guarantee threshold, or a guarantee failure message sent by the first network device is received, adjusting the sub-SLO and the service packet feature model.

[0095] That is to say, when the network is abnormal or the first network device fails to guarantee, it is necessary to adjust the sub-SLO and the service packet feature model so that the first network device can guarantee the normal operation of the connection service based on the adjusted sub-SLO and ensure that the SLO is reachable.

[0096] Figure 4 It is a detailed process schematic diagram of a service guarantee method. As Figure 4 shown, the operation and maintenance management system is used for connection service management. It can send the SLO guarantee requirements of the radio network element to the first network device (i.e., Figure 4 the radio network element A in it) so that the first network device can perform small closed-loop service self-guarantee based on the SLO, and send the cross-network element SLO guarantee requirements to the second network device (i.e., Figure 4 the collaborative network element B in it) so that the first network device and the second network device can jointly perform large closed-loop service guarantee. It should be noted that the first network device can first perform a small closed-loop. In the case of small closed-loop failure, it can jointly perform large closed-loop service guarantee with the second network device.

[0097] Among them, the radio network element A includes modules such as a radio intelligent agent, data statistical analysis, a signaling plane function entity, and a user plane function entity. Among them, the radio intelligent agent is used to implement active service guarantee and diagnostic self-healing disposal on the network side, and report information such as network element abnormal events, abnormal indicators, and black boxes to the operation and maintenance management system; the data statistical analysis module is used to report service statistical data and signaling statistical data, that is, to perform data association on the data obtained by the signaling plane function entity and the user plane function entity and report the statistical data to the radio intelligent agent; the signaling plane function entity and the user plane function entity are used to communicate with a terminal device (such as a CPE terminal) to obtain signaling packets and data packets.

[0098] The radio network element B includes modules such as a Qos guarantee collaboration entity, intelligent packet insight, service traffic statistics, and service flow outlet. Among them, the Qos guarantee collaboration entity provides the ability to decompose cross-network element collaboration guarantee goals and dynamically adjust guarantee parameters, and sends information such as segmented guarantee goals, service packet features of predefined services, and 5QI policy parameters to the radio network element A; intelligent packet insight and service traffic statistics periodically count new service packet features and report the observed SLI service metrics to the Qos guarantee collaboration entity; the service flow outlet is used to connect to the application.

[0099] It should be noted that the wireless agent and data statistical analysis of the wireless network element A can be collectively referred to as the AI intelligent guarantee module (i.e., the AI intelligent guarantee module in the first network device in Figure 5 ); the Qos guarantee collaboration entity, intelligent message insight, and service traffic statistics of the wireless network element B can be called the AI intelligent guarantee module (i.e., the AI intelligent guarantee module in the second network device in Figure 5 ). The AI intelligent guarantee modules of the wireless network element A and the wireless network element B can be co-located and their capabilities can be integrated to better perform service guarantee.

[0100] The embodiment of the present application provides a service guarantee system, including an operation and maintenance management system, a first network device, and a second network device. Among them, the structure of the first network device is the structure of the wireless network element A as shown in Figure 4 , and the structure of the second network device is the structure of the wireless network device B as shown in Figure 4 .

[0101] Figure 5 This is the specific structure of the operation and maintenance management system. As shown in Figure 5 , the operation and maintenance management system can include modules such as connection service management, service SLO monitoring, service anomaly tracing, service AI intelligent guarantee, effect evaluation, and wizard-style fault handling, to achieve automated closed-loop processing based on service guarantee goals, collaborate with network devices, and complete service guarantee in the case of network device or service anomaly scenarios.

[0102] Among them, the connection service management module: provides the creation of various end-to-end connections for network services, such as the connection relationship from a single 5G module terminal CPE to an industry application, the connection relationship from a dual 5G module terminal CPE FRER mode to an industry application, and the connection relationship from a 5G terminal to a 5G terminal; when creating an end-to-end connection for a network service, the service SLO guarantee goal at the UE level or APP level under this connection service can be set.

[0103] The service SLO monitoring module: presents the network service SLI indicators based on the end-to-end connection of the network service, including end-to-end indicators and segmented or uplink / downlink indicators; the data source can be directly from the network device or the indicator information obtained through DPI probe technology; based on the Site Reliability Engineering (SRE) operation and maintenance theory, when it is found that the service SLO goal or the downward trend of the service SLO goal exceeds the set guarantee threshold, a network service anomaly alarm is generated and the self-closed-loop processing process is automatically initiated.

[0104] Business exception tracing module: Provide business exception tracing analysis. Based on device fault alarms or network service exception alarms, KPI indicators, and service observation SLI indicators, analyze the exception points of the devices associated with the end-to-end connection of the network service based on the expert rule knowledge base / graph, AI correlation analysis, group fault / individual fault analysis methods, etc., and find the location where the exception occurs.

[0105] Business AI intelligent guarantee module: Provide system-level business AI intelligent guarantee. Based on the results of business exception tracing, implement system-level fault location processing. Also based on AI algorithms or expert knowledge base information, output fault location information through the AI engine, and conduct secondary confirmation on the service dial test, service self-healing (such as dynamically adjusting network resources), and diagnostic analysis of network devices (including CPE terminals).

[0106] Effect evaluation: Provide the effect evaluation ability and knowledge recycling ability of business AI intelligent guarantee, and dynamically generate fault handling suggestions that require manual intervention: Based on the self-healing results, output the conclusion of the effect evaluation analysis, and use the automated processing results of this exception as knowledge precipitation to complete knowledge recycling. If the self-healing result fails, based on the latest obtained self-healing diagnostic information and the fault tree knowledge base, dynamically generate fault handling suggestions that require manual intervention.

[0107] Wizard-style fault handling: Provide a wizard-style process for manual handling, which is convenient for manual handling of faults according to the wizard-style process, online feedback on the filling status, and guiding users to complete fault handling. The final processing process result is also sent to the effect evaluation module.

[0108] Figure 6 For the schematic diagram of the service guarantee process, as Figure 6 shown, the service guarantee process is as follows:

[0109] Service self-guarantee: For the established service connection, the service guarantee target SLO is set. Among them, the operation and maintenance management system is used to define the SLO guarantee template and dynamically load it, and issue the guarantee setting (slice + 5QI + UE or APP level) based on the service connection; based on the exception trend judgment of the SRE error budget, generate exception point events.

[0110] Network element devices: Divided into single-site small closed-loop (that is, the first network device conducts service guarantee alone) and cross-site large closed-loop (the first network device and the second network device jointly conduct service guarantee). Among them, the single-site small closed-loop specifically collects signaling and data packet information periodically, statistics service index types and service reliability index types, data correlation analysis, and discovers exception points; based on the issued SLO guarantee target (such as delay, reliability, 5QI), dynamically adjust the QoS control strategy and take effect dynamically.

[0111] The cross-site large closed-loop specifically refers to the second network device intelligently detecting and analyzing data-plane packets, obtaining service packet characteristics (such as packet size, periodicity, arrival time, flow direction, etc.) through AI technology; the second network device decomposes and segments service objectives (such as segmented delay) based on the UE-level and APP-level SLO guarantee objectives of the service connection; the second network device sends the packet characteristic model, segmented service guarantee objectives, and 5QI (customized or predefined) to the first network device; the first network device performs service SLO guarantee control in a single-site closed-loop manner.

[0112] Self-healing process: For service anomalies occurring in the system, relevant anomaly information is collected. Among them,

[0113] Operation and maintenance management system: Based on data such as service observation indicators SLI, alarms, performance KPIs, MRs, and probe packets reported by network elements, through AI algorithms, analyze anomaly points, trace the locations of anomaly points, and complete demarcation analysis; based on the locations of anomaly points and anomaly phenomena, generate service anomaly characteristics (such as network anomalies: interference, coverage, capacity; radio interface anomalies: delay anomalies, packet retransmission, BLER anomalies) through a fault handling tree knowledge graph, and generate guarantee instructions according to different service anomaly characteristics, and perform diagnostic analysis, policy adjustment, parameter modification, Action, etc. on network element devices; among them, the guarantee instructions include two categories. One category is network optimization or expansion to reduce anomaly points at the network level, involving network expansion, neighbor cell adjustment, and radio parameter adjustment. The other category is the adjustment of service guarantee objectives related to service connections, optimizing radio interface scheduling, involving 5QI adjustment and service indicator adjustment (such as segmented delay).

[0114] Network element device: For the first type of instruction, it is used to take effect based on the capabilities of the current network element device. The AI intelligent guarantee module needs to pay attention to changes in sensitive parameters to update the Qos guarantee policy. For the second type of instruction, it is used to adjust the service guarantee objective based on the new dynamic policy or segmented indicators issued by the operation and maintenance management system, re-attempt self-closed-loop (including large closed-loop), collect two statistical periods, and feedback the self-closed-loop effect; if the self-closed-loop result cannot reach the predetermined target, then based on the process analysis products (such as anomaly association rules, corresponding 5QI policies, fault points) of the self-closed-loop process, output the conclusion of abnormal root cause location, form black box information, and report it to the operation and maintenance management system.

[0115] The above processing procedures have been described in detail in the above embodiments, and will not be repeated in this embodiment. For details, please refer to the above embodiments.

[0116] After the operation and maintenance management system performs service self-guarantee and self-healing processing, it also includes processes such as effect evaluation and wizard-style fault handling.

[0117] Among them, effect evaluation: It is used to evaluate the effect and recycle knowledge based on the self-healing process and results for the completed system self-healing process for reuse; the operation and maintenance management system builds a knowledge base for handling network faults and anomalies based on knowledge graph technology; updates the node or relationship information in the knowledge base based on each abnormal phenomenon, abnormal feature, self-closed-loop processing process and results; updates the processing results obtained from the manual wizard-style fault handling process to the knowledge base based on the generated dynamic processing suggestion tree; provides a set of (and process of) processing suggestion actions corresponding to abnormal phenomena and features based on the knowledge information in the knowledge base.

[0118] Wizard-style fault handling: It is used for the completed effect evaluation and self-healing failure, and manual intervention is required; the operation and maintenance management system dynamically generates a wizard-style visual UI interface by calling the set of (and process of) fault handling suggestion actions provided by the effect evaluation module based on faults or service anomalies and related known information; according to the wizard-style interface, prompts the user to perform step-by-step operations to quickly complete the fault handling; for relatively fixed complex operations, provides a one-key operation execution to reduce the operation complexity and improve the operation efficiency; writes back the manual handling results and intermediate process status of the corresponding faults to the knowledge base of the effect evaluation module.

[0119] In a possible implementation manner of the present application, taking the scenario of a CPE terminal, a 5G wireless network (NR network element) (i.e., the first network device), and a 5G core network user plane function (UPF network element) (i.e., the second network device) as an example, and taking the instantiation of an SLO controlled by a Programmable Logic Controller (PLC) in industrial production (reliability 99.999%, latency <= 20ms), the following details how the entire system realizes the business guarantee closed-loop.

[0120] The user creates a new PLC connection service in the operation and maintenance management system by connecting to the service management module. When creating the connection service, the terminal type associated with this connection service needs to be specified; when creating the connection service, the corresponding SLO template needs to be associated according to the PLC control service scenario, and the corresponding service SLO (such as a latency of 20 ms, a reliability of five nines, a latency jitter of 3 ms, etc.) is set in the template. Specifically, when the creation of the connection service with the service SLO target guarantee is completed, the connection service management module notifies the AI intelligent guarantee module of the network device of the connection service information. The connection service management module gives priority to sending it to the UPF network element, and the UPF network element decomposes the SLO (such as a latency of 12 ms and a latency jitter of 3 ms) based on the large closed-loop process, and the UPF network element notifies the AI intelligent guarantee module of the NR network element; if the NR network element does not support the large closed-loop process, the connection service management module directly sends the SLO to the AI intelligent guarantee module of the NR network element; when the creation of the connection service with the service SLO target guarantee is completed, the connection service management module notifies the service SLO monitoring module of the connection service information.

[0121] The network element automatically guarantees based on the SLO and reports the real-time service status (and black box information) of the operation and maintenance management system. Specifically, after receiving the SLO setting of the corresponding connection service, the AI intelligent guarantee of the network device converts the SLO into an internal 5QI-level parameter or a physical resource block (PRB) resource scheduling strategy. And automatically starts the connection service guarantee process. When any SLO anomaly (spike) occurs during this process, this module will automatically analyze and record the signaling calls or abnormal events of relevant service modules such as the signaling plane function entity and the user plane function, and record the black box; the device side regularly (such as a 5s cycle) reports the service SLI metrics and black box information of the network element to the operation and maintenance management system.

[0122] The service SLO monitoring module presents the service SLI metrics of all connection services. When it identifies that the service SLO target or the downward curve trend of the service SLO target of a certain connection service exceeds the current guarantee level threshold, it actively initiates the self-healing closed-loop process, as shown in the above embodiments, which will not be described in detail in this embodiment.

[0123] The effect evaluation module of the operation and maintenance management system outputs the conclusion of the effect evaluation analysis of the automatic closed-loop of the current problem based on the self-healing and diagnosis results of the network element, and takes the phenomena, actions, and results of the automated processing of this abnormal scenario as the knowledge precipitation of an abnormal scenario processing to complete the knowledge recycling; if the self-healing evaluation result of this abnormal scenario is successful, then this guarantee closed-loop process ends.

[0124] If the system self-healing closed-loop of the current abnormal scenario fails, the wizard-based fault handling module of the operation and maintenance management system dynamically generates fault handling suggestions that require manual intervention based on the network element diagnosis and handling information and the fault tree knowledge base, and prompts the user to perform manual handling on the interface.

[0125] The user quickly handles the fault in a wizard-based process according to the fault handling suggestions displayed by the operation and maintenance management system, online feedbacks the filling status, and guides the user to complete the fault handling; the process results of the user's manual fault handling are also recorded in the effect evaluation module as the closed-loop feedback of the fault tree knowledge base.

[0126] Figure 7 Schematic diagram of a service guarantee device provided by an embodiment of the present application, as Figure 7 shown, this service guarantee device is applied to an operation and maintenance management system, and this service guarantee device may include: a setting module 701, a first receiving module 702, and a first sending module 703.

[0127] Among them, the setting module 701 is used to set a service level objective SLO based on the service objective in the service connection request and send the SLO to the network device, and the service connection request is used to create a connection service; the first receiving module 702 is used to determine the network anomaly point in the connection service based on the service data sent by the received network device; the first sending module 703 is used to send a guarantee instruction to the network device based on the network anomaly point, and the guarantee instruction is used to instruct the network device to perform service guarantee.

[0128] In the embodiment of the present application, first, the setting module 701 sets a service level objective SLO based on the service objective in the service connection request and sends the SLO to the network device, and the service connection request is used to create a connection service. Then, the first receiving module 702 determines the network anomaly point in the connection service based on the service data sent by the received network device. Finally, the first sending module 703 sends a guarantee instruction to the network device based on the network anomaly point, and the guarantee instruction is used to instruct the network device to perform service guarantee. In the embodiment of the present application, the SLO is set when establishing a connection service, so that the network device is instructed to perform self-guarantee based on the SLO. When a network anomaly occurs in the connection service, the network anomaly point is determined, and a guarantee instruction is sent to the network device based on the anomaly point, so that the network device can perform service guarantee based on the guarantee instruction, improving the guarantee efficiency through the service guarantee of the network device and enhancing the reliability of the service.

[0129] In a possible implementation manner of the present application, this service guarantee device may further include: a creation module.

[0130] Among them, a creation module is configured to create a connection service from terminal to terminal or from terminal to application according to a terminal address and / or an application address when receiving a service connection request, where the terminal address and / or the application address are carried in the service connection request.

[0131] In a possible implementation manner of this application, the network device includes a first network device and a second network device; a setting module 701 is configured to: send the SLO to the second network device, so that the second network device determines multiple sub-SLOs based on the SLO and sends them to the first network device, and the sub-SLO is a segmented guarantee target of the SLO.

[0132] In a possible implementation manner of this application, the service guarantee device may further include: a second receiving module.

[0133] Among them, it receives service data sent by the first network device, and the service data includes a service level measurement index SLI, statistical data, alarms, status, signaling messages, and black box information.

[0134] In a possible implementation manner of this application, a first receiving module 702 is configured to: determine whether the reception and / or transmission of the terminal device in the connection service is abnormal; if the reception and / or transmission of the terminal device is abnormal, extract the statistical data associated with the terminal device in the service data, as well as the alarms, status, signaling messages, and black box information sent by the terminal device; when the statistical data, alarms, status, signaling messages, and / or black box information is abnormal, determine that the network abnormal point in the connection service is the terminal device; when the network abnormal point is a non-terminal device, analyze the network abnormal point and trace the root cause of the abnormal point based on the service level measurement index SLI, SLO, preset guarantee threshold, and network device status in the service data, so as to determine the network abnormal point in the connection service.

[0135] In a possible implementation manner of this application, a first sending module 703 is configured to: generate a service abnormal feature based on the network abnormal point and the network abnormal phenomenon when the network abnormal point is a non-terminal device; generate a network optimization or expansion instruction, or generate a service guarantee target adjustment instruction for the service connection based on the service abnormal feature; send the network optimization or expansion instruction, or the service guarantee target adjustment instruction for the service connection to the network device; receive the analysis conclusion and guarantee result returned by the network device.

[0136] In a possible implementation manner of this application, the service guarantee device may further include: a generation module and an update module.

[0137] Among them, the generation module is used to generate manual intervention processing suggestions according to the network anomaly points, network anomaly phenomena, service anomaly characteristics, service guarantee process, and service data after service guarantee in the analysis conclusion when the guarantee result returned by the network device is guarantee failure; the update module is used to update the network anomaly points, network anomaly phenomena, service anomaly characteristics, service guarantee process, service data after service guarantee, manual intervention processing suggestions, and execution results in the analysis conclusion to the preset fault tree knowledge base.

[0138] The service guarantee device provided by the embodiment of the present application can implement Figure 1 each process implemented by the method embodiment, achieving the same technical effect. To avoid repetition, it will not be elaborated here.

[0139] Figure 8 As shown in Figure 8 the structure diagram of a service guarantee device provided by the embodiment of the present application. The service guarantee device is applied to the first network device and may include: a third receiving module 801, a collection module 802, a first guarantee module 803, a second sending module 804, a fourth receiving module 805, and a second guarantee module 806.

[0140] Among them, the third receiving module 801 is used to receive the SLO sent by the operation and maintenance management system or the sub-SLO and service message feature model sent by the second network device. The SLO is the target corresponding to the connection service, and the service message feature model is a model determined by the second network device based on the service message features corresponding to the type of the connection service; the collection module 802 is used to collect service data based on the SLO or sub-SLO; the first guarantee module 803 is used to perform service self-guarantee according to the SLO, sub-SLO, service message feature model, and service data; the second sending module 804 is used to send the service data to the operation and maintenance management system or send the service data and guarantee failure information to the operation and maintenance management system and the second network device when the service self-guarantee fails; the fourth receiving module 805 is used to receive the guarantee instruction sent by the operation and maintenance management system based on the service data; the second guarantee module 806 is used to perform service guarantee according to the guarantee instruction.

[0141] In the embodiment of the present application, first, the third receiving module 801 receives the SLO sent by the operation and maintenance management system or the sub-SLO and the service message feature model sent by the second network device. Then, the acquisition module 802 acquires service data based on the SLO or the sub-SLO. The first guarantee module 803 performs service self-guarantee according to the SLO, the sub-SLO, the service message feature model, and the service data. When the service self-guarantee fails, the second sending module 804 sends the service data to the operation and maintenance management system, or sends the service data and the guarantee failure information to the operation and maintenance management system and the second network device. Finally, the fourth receiving module 805 receives the guarantee instruction sent by the operation and maintenance management system based on the service data, and the second guarantee module 806 performs service guarantee according to the guarantee instruction. In the embodiment of the present application, the first network device can perform service self-guarantee based on the SLO sent by the operation and maintenance management system or the sub-SLO and the service message feature model sent by the second network device, guarantee the reliable operation of the connected service, and make the SLO or the sub-SLO reachable. In the case of self-guarantee failure, service guarantee can be performed based on the guarantee instruction sent by the operation and maintenance management system. Through multiple guarantee methods, the guarantee efficiency can be improved and the reliability of the service can be enhanced.

[0142] In a possible implementation manner of the present application, the first guarantee module 803 is configured to: perform data correlation analysis on signaling messages and statistical data in the service data corresponding to the SLO, analyze network anomaly points and trace the root cause of the anomaly points to determine the network anomaly points in the connected service; based on the SLO, the network anomaly points, the service anomaly features, and the correspondence between the service anomaly features and the trained adjustment strategies, adjust the priority of the quality of service (QoS) corresponding to the network anomaly points, the radio air interface, and the resource scheduling strategy.

[0143] In a possible implementation manner of the present application, the first guarantee module 803 is configured to: perform data correlation analysis on signaling messages and statistical data in the service data corresponding to the sub-SLO, analyze network anomaly points and trace the root cause of the anomaly points to determine the network anomaly points in the connected service; based on the sub-SLO, the service message feature model, the network anomaly points, the service anomaly features, and the correspondence between the service anomaly features and the trained adjustment strategies, adjust the priority of the QoS corresponding to the network anomaly points, the radio air interface, and the resource scheduling strategy.

[0144] In a possible implementation manner of the present application, the second guarantee module 806 is configured to: receive the network optimization or expansion instruction sent by the operation and maintenance management system; based on the network optimization or expansion instruction, adjust the network coverage, cell neighboring areas, and network service strategies to reduce network interference and handover frequency and improve network capacity.

[0145] In a possible implementation manner of the present application, the second guarantee module 806 is configured to: receive a service guarantee target adjustment instruction of a service connection sent by an operation and maintenance management system; determine multiple sub-SLOs based on the terminal-level SLO and the application-level SLO sent by the operation and maintenance management system; adjust the sub-SLOs based on the service guarantee target adjustment instruction of the service connection; determine a message feature model according to the service message features in service data; perform data correlation analysis on signaling messages and statistical data in the service data, analyze network anomaly points and trace the root causes of the anomaly points to determine network anomaly points in the connection service; and adjust the QoS priority, radio air interface, and resource scheduling policies corresponding to the network anomaly points based on the service message feature model, the adjusted sub-SLOs, the network anomaly points, the service anomaly features, and the correspondence between the service anomaly features and the trained adjustment policies.

[0146] The service guarantee device provided by the embodiments of the present application can implement Figure 2 each process implemented by the method embodiments, achieving the same technical effects. To avoid repetition, details are not described here again.

[0147] Figure 9 It is a schematic structural diagram of a service guarantee device provided by an embodiment of the present application. As Figure 9 shown, the service guarantee device is applied to a second network device, and the service guarantee device may include: a first determination module 901, an acquisition module 902, a second determination module 903, and a third sending module 904.

[0148] Among them, the first determination module 901 is configured to receive the SLO sent by the operation and maintenance management system and determine multiple sub-SLOs based on the SLO, where the SLO is the target corresponding to the connection service; the acquisition module 902 is configured to acquire the preset service message features based on the type of the connection service; the second determination module 903 is configured to determine the service message feature model based on the service message features; and the third sending module 904 is configured to send the multiple sub-SLOs and the service message feature model to the first network device, so that the first network device performs service self-guarantee based on the sub-SLOs and the service message feature model.

[0149] In an embodiment of the present application, first, the first determination module 901 receives the SLO sent by the operation and maintenance management system, determines multiple sub-SLOs based on the SLO, where the SLO is the target corresponding to the connection service. Then, the acquisition module 902 acquires the preset service message features based on the type of the connection service. The second determination module 903 determines the service message feature model based on the service message features. Finally, the third sending module 904 sends the multiple sub-SLOs and the service message feature model to the first network device, so that the first network device performs service self-guarantee based on the sub-SLOs and the service message feature model. In this embodiment, the second network device can decompose the SLO sent by the operation and maintenance management system into multiple sub-SLOs, so that the first network device can perform service self-guarantee in segments based on the multiple sub-SLOs, improving the reliability of the connection service.

[0150] In a possible implementation manner of the present application, the service guarantee device may further include: a statistics module, a second update module, and a second acquisition module.

[0151] Among them, the statistics module is used to statistically analyze the service messages of the connection service based on the connection service, and obtain the corresponding service message features and service message feature model; the second update module is used to update the service message features to the preset service message features; the second acquisition module is used to acquire the SLI corresponding to the SLO or sub-SLO based on the service message features and the preset period, and report the SLI to the operation and maintenance management system.

[0152] In a possible implementation manner of the present application, the service guarantee device may further include: an adjustment module.

[0153] Among them, the adjustment module is used to adjust the sub-SLO and the service message feature model when it is detected that the SLI of the connection service does not meet the SLO, or the downward trend of the SLI exceeds the guarantee threshold, or the guarantee failure information sent by the first network device is received.

[0154] The service guarantee device provided by the embodiment of the present application can implement Figure 3 each process implemented by the method embodiment, achieving the same technical effect. To avoid repetition, it will not be elaborated here.

[0155] As Figure 10 shown, an embodiment of the present application further provides an electronic device 1000, including a processor 1001, a memory 1002, a program or instruction stored on the memory 1002 and executable on the processor 1001. When the program or instruction is executed by the processor 1001, it implements each process of the above service guarantee method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0156] The embodiments of the present application further provide a storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the various processes of the business guarantee method embodiments provided in any of the above embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0157] Wherein, the processor is the processor in the electronic device described in the above embodiments. The storage medium includes computer storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disks or optical discs, etc.

[0158] The embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the business guarantee method embodiments described above, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0159] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system or system-on-chip, etc.

[0160] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the business guarantee method embodiments described above, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0161] The embodiments of the present application further provide a processing device, which is configured to execute the various processes of the business guarantee method embodiments described above, and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0162] It should be noted that in this text, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0163] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0164] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them fall within the protection scope of the present application.

Claims

1. A service guarantee method, characterized in that, applied to an operation and maintenance management system, the method includes: setting a service level objective (SLO) based on the service objective in the service connection request, and sending the SLO to a network device, where the service connection request is used to create a connection service; determining network anomaly points in the connection service based on the service data sent by the received network device; sending a guarantee instruction to the network device based on the network anomaly points, where the guarantee instruction is used to instruct the network device to perform service guarantee.

2. The method according to claim 1, characterized in that, before setting the service level objective (SLO) based on the service objective in the service connection request, the method further includes: when receiving a service connection request, creating a terminal-to-terminal or terminal-to-application connection service according to the terminal address and / or application address, where the terminal address and / or application address are carried in the service connection request.

3. The method according to claim 1, characterized in that, the network device includes a first network device and a second network device; sending the SLO to the network device includes: sending the SLO to the second network device, so that the second network device determines multiple sub-SLOs based on the SLO and sends them to the first network device, where the sub-SLO is a segmented guarantee objective of the SLO.

4. The method according to claim 3, characterized in that, after sending the SLO to the network device, the method further includes: receiving service data sent by the first network device, where the service data includes service level measurement indicators (SLI), statistical data, alarms, status, signaling messages, and black box information.

5. The method according to claim 1, characterized in that, determining network anomaly points in the connection service based on the service data sent by the received network device includes: determining whether the reception and / or transmission of the terminal device in the connection service is abnormal; if the reception and / or transmission of the terminal device is abnormal, extracting the statistical data associated with the terminal device in the service data, as well as the alarms, status, signaling messages, and black box information sent by the terminal device; when the statistical data, the alarms, status, signaling messages, and / or black box information are abnormal, determining the network anomaly point in the connection service as the terminal device; when the network anomaly point is a non-terminal device, analyzing the network anomaly point and tracing the root cause of the anomaly point based on the service level measurement indicator (SLI) in the service data, the SLO, a preset guarantee threshold, and the status of the network device, to determine the network anomaly point in the connection service.

6. The method according to claim 5, characterized in that, sending a guarantee instruction to the network device based on the network anomaly points includes: when the network anomaly point is a non-terminal device, generating a service anomaly feature based on the network anomaly point and the network anomaly phenomenon; generating a network optimization or expansion instruction based on the service anomaly feature, or generating a service guarantee objective adjustment instruction for the service connection. Send a network optimization or expansion instruction, or an instruction to adjust the service guarantee target of a service connection, to the network device; Receive the analysis conclusion and guarantee result returned by the network device.

7. The method according to claim 6, wherein, the method further includes: in the case where the guarantee result returned by the network device is a guarantee failure, generate a manual intervention processing suggestion according to the network anomaly point, network anomaly phenomenon, service anomaly feature, service guarantee process, and service data after service guarantee in the analysis conclusion; Update the network anomaly point, network anomaly phenomenon, service anomaly feature, service guarantee process, service data after service guarantee, manual intervention processing suggestion, and execution result in the analysis conclusion to a preset fault tree knowledge base.

8. A service guarantee method, wherein, applied to a first network device, the method includes: Receive the SLO sent by an operation and maintenance management system or the sub-SLO and service packet feature model sent by a second network device, where the SLO is the target corresponding to a connection service, and the service packet feature model is a model determined by the second network device based on the service packet features corresponding to the type of the connection service; Collect service data based on the SLO or the sub-SLO; Perform service self-guarantee according to the SLO, the sub-SLO, the service packet feature model, and the service data; In the case where the service self-guarantee fails, send the service data to the operation and maintenance management system, or send the service data and the guarantee failure information to the operation and maintenance management system and the second network device; Receive a guarantee instruction sent by the operation and maintenance management system based on the service data; Perform service guarantee according to the guarantee instruction.

9. The method according to claim 8, wherein, the performing service self-guarantee according to the SLO, the sub-SLO, the service packet feature model, and the service data includes: Perform data correlation analysis on the signaling packets and statistical data in the service data corresponding to the SLO, analyze network anomaly points and trace the root cause of the anomaly points, to determine the network anomaly points in the connection service; Based on the SLO, the network anomaly points, service anomaly features, and the correspondence between the service anomaly features and the trained adjustment strategies, adjust the priority of the quality of service (QoS) corresponding to the network anomaly points, the radio air interface, and the resource scheduling strategy.

10. The method according to claim 8, wherein, the performing service self-guarantee according to the SLO, the sub-SLO, the service packet feature model, and the service data includes: Perform data correlation analysis on the signaling packets and statistical data in the service data corresponding to the sub-SLO, analyze network anomaly points and trace the root cause of the anomaly points, to determine the network anomaly points in the connection service; Based on the sub-SLO, the service message feature model, the network anomaly point, the service anomaly feature, and the correspondence between the service anomaly feature and the trained adjustment strategy, adjust the QoS priority, radio air interface, and resource scheduling strategy corresponding to the network anomaly point.

11. The method according to claim 8, wherein, the performing service guarantee according to the guarantee instruction includes: receiving a network optimization or expansion instruction sent by the operation and maintenance management system; based on the network optimization or expansion instruction, adjusting network coverage, cell neighboring cells, and network service strategies to reduce network interference and handover frequency and improve network capacity.

12. The method according to claim 8, wherein, the performing service guarantee according to the guarantee instruction includes: receiving a service guarantee target adjustment instruction for a service connection sent by the operation and maintenance management system; determining multiple sub-SLOs based on the terminal-level SLO and the application-level SLO sent by the operation and maintenance management system; adjusting the sub-SLOs based on the service guarantee target adjustment instruction for the service connection; determining a message feature model according to the service message features in the service data; performing data correlation analysis on signaling messages and statistical data in the service data, analyzing network anomaly points and tracing the root causes of the anomaly points to determine network anomaly points in the connection service; based on the service message feature model, the adjusted sub-SLOs, the network anomaly points, the service anomaly features, and the correspondence between the service anomaly features and the trained adjustment strategies, adjusting the QoS priority, radio air interface, and resource scheduling strategy corresponding to the network anomaly points.

13. A service guarantee method, wherein, applied to a second network device, the method includes: receiving an SLO sent by an operation and maintenance management system, and determining multiple sub-SLOs based on the SLO, where the SLO is the target corresponding to a connection service; acquiring preset service message features based on the type of the connection service; determining a service message feature model based on the service message features; sending the multiple sub-SLOs and the service message feature model to a first network device so that the first network device performs service self-guarantee based on the sub-SLOs and the service message feature model.

14. The method according to claim 13, wherein, the method further includes: statistically analyzing service messages of the connection service based on the connection service to obtain corresponding service message features and a service message feature model; updating the service message features to the preset service message features; acquiring an SLI corresponding to the SLO or the sub-SLO based on the service message features and a preset period, and reporting the SLI to the operation and maintenance management system.

15. The method according to claim 13, wherein, the method further includes: In the case where the SLI of the connection service is detected to not meet the SLO, or the downward trend of the SLI exceeds the guarantee threshold, or a guarantee failure message sent by the first network device is received, adjust the sub-SLO and the service packet feature model.

16. An electronic device, characterized in that, it includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, and when the program or instruction is executed by the processor, it implements the steps of the service guarantee method according to any one of claims 1-15.

17. A storage medium, characterized in that, the storage medium stores a program or instruction, and when the program or instruction is executed by a processor, it implements the steps of the service guarantee method according to any one of claims 1-15.