A method and system for troubleshooting configuration of a 5G core network sub-slice

Abstract

The application discloses a 5G core network sub-slice configuration troubleshooting method and system, wherein the method comprises the following steps: sending a sub-slice work order number to a preset slice verification agent; calling the first log interface to obtain work order receiving conditions according to the sub-slice work order number; if the work order receiving conditions are normal, calling the second log interface to obtain script generation conditions; if the script generation conditions are normal, calling the third log interface to obtain sub-slice configuration conditions; and performing troubleshooting through the agent knowledge base according to the work order receiving conditions, the script generation conditions and the sub-slice configuration conditions to obtain troubleshooting results and fault repair suggestions. According to the preset rules, the application can automatically verify the configuration process of the sub-slice work order through the slice verification agent and the knowledge base, and greatly improves the efficiency and accuracy of troubleshooting.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method and system for troubleshooting configuration problems of 5G core network sub-slices. Background Art

[0002] Network slicing is a new concept introduced in 5G. To provide independent operations and maintenance for specific services, a stable and efficient network requires the use of several independent subnetworks to support 5G application scenarios. These subnetworks' radio, bearer, and core network resources are completely isolated from other networks. These isolated subnetworks are called network slices or subslices. The configuration and activation of 5G subslices are critical to ensuring the stability of 5G dedicated line services, requiring significant R&D investment in technical breakthroughs and optimization upgrades.

[0003] The existing configuration verification of 5G core network sub-slice dedicated lines mainly relies on manual operations. During the sub-slice configuration, the system will generate a configuration script and corresponding log records. If a configuration failure occurs, it is necessary to manually analyze the above log records and gradually troubleshoot the possible causes of the failure to deliver the dedicated line configuration. This process requires the operator to have a deep understanding of the system configuration and a thorough inspection of the network environment. If an unresolvable problem is encountered during the troubleshooting process, a more in-depth query on the system is required. This requires the operator to have not only professional technical knowledge but also practical operation experience. Therefore, the configuration verification requirements for sub-slice dedicated lines are high, resulting in high labor costs and low efficiency of manual troubleshooting. Summary of the Invention

[0004] This application proposes a configuration troubleshooting method and system for 5G core network sub-slices. Through a slice verification agent and a knowledge base, the configuration process of sub-slice work orders is automatically verified according to preset rules, greatly improving the efficiency and accuracy of troubleshooting.

[0005] A first aspect of the present application provides a method for troubleshooting configuration failures of a 5G core network sub-slice, the method comprising:

[0006] Send the sub-slice work order number to a preset slice verification agent; wherein the slice verification agent includes a first log interface, a second log interface, a third log interface and an agent knowledge base, the first log interface is used to call the access result log recording the work order reception process, the second log interface is used to call the script generation log recording the sub-slice configuration script generation process, and the third log interface is used to call the configuration delivery log recording the sub-slice configuration script configuration process;

[0007] According to the sub-slice work order number, call the first log interface to obtain the work order reception status;

[0008] If the work order reception status is normal, calling the second log interface to obtain the script generation status;

[0009] If the script generation is normal, the third log interface is called to obtain the sub-slice configuration;

[0010] According to the work order reception situation, script generation situation and sub-slice configuration situation, troubleshooting is performed through the agent knowledge base to obtain troubleshooting results and fault repair suggestions.

[0011] In the above scheme, a preset slice verification agent is used to obtain logs recording different situations of the work order in the configuration process by calling different interfaces according to the sub-slice work order number, so as to realize automated log query. First, the sub-slice dedicated line is queried through the first log interface to see whether it has been cancelled, to determine whether the sub-slice dedicated line has been successfully connected, and to obtain the work order reception situation; when it is determined that the fault did not occur in the work order reception process, it is determined whether the sub-slice configuration script has been generated. If it is determined that the sub-slice configuration script has been successfully generated, the sub-slice configuration process is checked; the above sub-slice configuration process situations are all based on the slice verification agent calling the corresponding log interface and analyzing it. According to these situations, automated fault troubleshooting is effectively realized through the agent knowledge base, and suggestions related to fault repair can be accurately extracted from a large amount of data, which can help to quickly solve sub-slice configuration problems.

[0012] In a possible implementation method of the first aspect, the sub-slice work order number is sent to a preset slice verification agent, specifically:

[0013] Create a slice verification agent and a chat assistant on the pre-set AI agent;

[0014] The sub-slice work order number is transmitted to the slice verification agent through the chat assistant.

[0015] The above solution builds an AI-based slice verification agent and configures a chat assistant for the slice verification agent to receive sub-slice work order numbers, realizing interactive troubleshooting. By entering the sub-slice work order number into the chat assistant, the slice verification agent can troubleshoot the slice configuration, reducing labor costs.

[0016] In a possible implementation method of the first aspect, according to the sub-slice work order number, calling the first log interface to obtain work order receipt status is specifically as follows:

[0017] According to the sub-slice work order number, call the first log interface to obtain the access result log;

[0018] Query the access status of the sub-slice dedicated line based on the access result log to obtain the work order receipt status.

[0019] The above solution first obtains the access result log based on the sub-slice work order number. It then analyzes the access result log to determine whether the sub-slice dedicated line has been successfully connected to the system. This allows for a check to determine if there is an access failure in the sub-slice dedicated line. If the problem is confirmed to be at the dedicated line access stage, the cause of the failure can be promptly reported.

[0020] In a possible implementation method of the first aspect, if the work order reception status is normal, calling the second log interface to obtain the script generation status is specifically as follows:

[0021] If the work order reception is normal, then the second log interface is called according to the sub-slice work order number to obtain a script generation log;

[0022] Query the generation status of the sub-slice configuration script according to the script generation log to obtain the script generation status.

[0023] After confirming that the dedicated line has been successfully connected, the above solution will investigate whether there are any problems with the subslice configuration script. First, call the second log interface to obtain the script generation log. By analyzing the script generation log, we can check whether the script was successfully generated. Further, we can obtain the script generation status for subsequent troubleshooting of the script generation process.

[0024] In a possible implementation method of the first aspect, if the script generation is normal, calling the third log interface to obtain the sub-slice configuration is as follows:

[0025] If the script generation is normal, the third log interface is called according to the sub-slice work order number to obtain the configuration delivery log;

[0026] According to the configuration delivery log, query the configuration status of the sub-slice configuration script to obtain the sub-slice configuration status.

[0027] After confirming successful dedicated line access and script generation, the above solution conducts troubleshooting on the script configuration process. First, the third logging interface is called to obtain the configuration delivery log. This log is used to verify successful script configuration and subslice configuration status, providing data support for subsequent confirmation that the fault occurred during the script configuration phase.

[0028] In a possible implementation method of the first aspect, based on the work order reception, script generation, and sub-slice configuration, troubleshooting is performed through the agent knowledge base to obtain troubleshooting results and troubleshooting suggestions, specifically:

[0029] If the work order reception is abnormal, then based on the repair suggestion template of the agent knowledge base, the fault troubleshooting results and fault repair suggestions are obtained through the NLP generation method;

[0030] If the script generation situation or sub-slice configuration situation is abnormal, the real-time network element configuration information is obtained through the agent knowledge base, and then based on the repair suggestion template, the fault troubleshooting results and fault repair suggestions are obtained through the NLP generation method.

[0031] In the above solution, if the fault is confirmed to have occurred during dedicated line access, NLP generation methods are used based on a pre-defined repair suggestion template to generate natural language-based troubleshooting results and repair suggestions. This makes it easier for users to understand the cause of the fault. If the fault is confirmed to have occurred during script generation or script configuration, real-time network element configuration information is obtained from the agent knowledge base to obtain more detailed configuration information and obtain more accurate troubleshooting results.

[0032] In a possible implementation method of the first aspect, obtaining the real-time network element configuration information through the agent knowledge base is specifically:

[0033] Obtaining corresponding query instructions from the proxy knowledge base according to the script generation situation or sub-slice configuration situation;

[0034] The query instruction is executed in the network element corresponding to the query instruction to obtain corresponding real-time network element configuration information.

[0035] A second aspect of the present application provides a 5G core network sub-slice configuration troubleshooting system, the system comprising: a verification agent startup module, a work order reception status check module, a script generation status check module, a sub-slice configuration status check module, and a troubleshooting result generation module;

[0036] Among them, the verification agent startup module is used to send the sub-slice work order number to the preset slice verification agent; wherein, the slice verification agent includes a first log interface, a second log interface, a third log interface and an agent knowledge base, the first log interface is used to call the access result log recording the work order reception process, the second log interface is used to call the script generation log recording the sub-slice configuration script generation process, and the third log interface is used to call the configuration delivery log recording the sub-slice configuration script configuration process;

[0037] The work order reception status checking module is used to call the first log interface to obtain the work order reception status according to the sub-slice work order number;

[0038] The script generation status checking module is used to call the second log interface to obtain the script generation status if the work order reception status is normal;

[0039] The sub-slice configuration status checking module is configured to call the third log interface to obtain the sub-slice configuration status if the script generation status is normal;

[0040] The troubleshooting result generation module is used to perform troubleshooting through the agent knowledge base based on the work order reception status, script generation status and sub-slice configuration status, and obtain troubleshooting results and troubleshooting suggestions.

[0041] A third aspect of the present application provides a terminal device, which includes: a terminal device including a processor and a memory, the memory storing a computer program, and the processor implementing the steps of a 5G core network sub-slice configuration troubleshooting method described in any one of the embodiments of the present application when executing the computer program.

[0042] A fourth aspect of the present application provides a storage medium storing computer-readable program code, which, when executed, implements the steps of a 5G core network sub-slice configuration troubleshooting method described in any one of the embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for use in the implementation. Obviously, the drawings described below are only some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0044] Figure 1 This is a schematic diagram of a specific process of a 5G core network sub-slice configuration troubleshooting method provided by an embodiment of the present application;

[0045] Figure 2 This is a server interaction diagram of a 5G core network sub-slice configuration troubleshooting method provided by an embodiment of the present application;

[0046] Figure 3 A structural diagram of a 5G core network sub-slice configuration troubleshooting system provided in one embodiment of the present application;

[0047] Figure 4 A structural diagram of a terminal device is provided for a certain embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0049] It should be understood that the step numbers used herein are only for convenience of description and are not intended to limit the order in which the steps are to be executed.

[0050] First embodiment

[0051] High-end and industry customers have strict requirements for network bandwidth, priority, SLAs, and security. Therefore, 5G sub-slicing dedicated line services are needed to ensure the stability and security of their dedicated line networks. Sub-slicing dedicated line configuration is a key prerequisite for the smooth launch of 5G sub-slicing dedicated line services. Therefore, detailed troubleshooting of the sub-slicing dedicated line configuration process is necessary to accurately identify the causes of configuration failures and provide customers with stable 5G sub-slicing dedicated line services.

[0052] Existing methods for troubleshooting sub-slice dedicated line configuration faults rely primarily on manual troubleshooting, which requires not only professional technical knowledge but also extensive practical experience, increasing human resource costs and reducing the efficiency of manual troubleshooting. Therefore, the present invention aims to automate the troubleshooting of sub-slice dedicated line configuration faults through an AI-based slice verification agent, reducing labor costs and improving the efficiency of troubleshooting analysis and verification, as well as the accuracy of analysis results, thereby enhancing operational efficiency and user experience.

[0053] like Figure 1 As shown, Figure 1 A specific flow chart of a method for troubleshooting configuration failures of a 5G core network sub-slice is provided for a certain embodiment of the present application. The method for troubleshooting configuration failures of a 5G core network sub-slice of this embodiment includes steps S1 to S5, which are described in detail as follows:

[0054] Step S1: Send the sub-slice work order number to the preset slice verification agent.

[0055] In an embodiment of the present application, three servers are first used to build a troubleshooting environment. The first server is used to deploy a slice management system and is configured with a MySQL database. The second server is used to deploy an AI agent. The third server is used to connect to the network element system and query network element information related to the sub-slice dedicated line deployment configuration.

[0056] Optionally, in the embodiment of the present application, the three servers are all Linux servers.

[0057] After the AI ​​agent is deployed, a slice verification agent and a chat assistant are newly created on the AI ​​agent to be responsible for troubleshooting the sub-slice dedicated line, and then the first server provides the relevant information of the sub-slice work order to the slice verification agent.

[0058] Furthermore, the receiving logic of the sub-slice work order, the generation logic of the sub-slice configuration script, the sending logic of the sub-slice configuration script, and the task content that the sub-slice configuration script is responsible for can be provided to the slice verification agent in a prompt manner, and three log call interfaces are registered in the slice verification agent based on this information, namely, the first log interface for calling the access result log of the work order receiving process, the second log interface for calling the script generation log of the sub-slice configuration script generation process, and the third log interface for calling the configuration sending log of the sub-slice configuration script configuration process.

[0059] This AI-based slice verification agent can realize automated monitoring and troubleshooting of the sub-slice work order configuration process. It can also process large amounts of data simultaneously and perform intelligent analysis and judgment based on preset rules, thereby greatly improving the efficiency and accuracy of troubleshooting.

[0060] At the same time, an agent knowledge base is configured for the slice verification agent, and the MML commands required for configuration issuance in the sub-slice configuration script, as well as command descriptions, logs of successful MML command execution, logs of execution exceptions, and modification suggestions for exceptions are uploaded to the agent knowledge base in the form of files through a third server, and these contents are vectorized. Among them, the MML command is a basic human-machine language command set for managing network equipment, mainly used to modify and adjust system parameters, including internal communication methods and end-to-end detection parameters. In the embodiment of the present application, the MML command is mainly executed on the network element related to the sub-slice dedicated line deployment configuration to realize the troubleshooting of the sub-slice configuration script generation process and the script configuration process.

[0061] The embodiment of the present application establishes an agent knowledge base including MML commands, command descriptions, log information, etc., and vectorizes this information, so that the slice check agent can quickly understand and process various information in the sub-slice configuration process, providing strong data support for sub-slice configuration troubleshooting.

[0062] After creating the slice verification agent on the second server, the operator sends the sub-slice work order number to be checked to the slice verification agent through the chat assistant. The slice verification agent obtains the sub-slice work order number through NLU technology. Among them, NLU technology can convert human speech into structured ontology, enabling computers to understand and interpret the meaning and intention of human natural language. In this embodiment of the application, NLU technology can convert the sub-slice work order number entered by the human into information that the slice verification agent can understand, so as to carry out subsequent troubleshooting, realizing human-computer interaction.

[0063] In order to better demonstrate the interactive relationship between the troubleshooting environment based on three servers, Figure 2 This is a server interaction diagram, in which the second server deployed with the AI ​​agent interacts with the first server and the third server respectively, indicating that the slice verification agent can obtain relevant information about the sub-slice work order from the slice management system, and can also obtain information related to the sub-slice configuration script from the third server.

[0064] Step S2: According to the sub-slice work order number, call the first log interface to obtain the work order reception status.

[0065] After obtaining the sub-slice work order number, call the first log interface through HTTP request according to the sub-slice work order number to obtain the access result log.

[0066] Different types of sub-slice work orders have different receiving processes, and the access result log will record the exceptions that occur during the receiving process. Common types of sub-slice work orders and corresponding access result logs that record exceptions are as follows:

[0067] (1) Sub-slice work orders for dedicated line activation: The process of receiving this type of work order involves access number uniqueness verification, DNN name uniqueness verification, VLAN ID automatic allocation, slice ID automatic allocation, etc. If the same access number and DNN name are found in the slice management system, a corresponding verification exception information will be generated in the access result log; due to the limited number of VLAN IDs or slice IDs, if no VLAN ID or slice ID can be allocated to the sub-slice dedicated line, an exception log about VLAN ID or slice ID resource exhaustion will be generated;

[0068] (2) Sub-slice work orders for dedicated line changes: The receiving process of this type of work order must first determine whether the dedicated line to be changed in the work order exists and whether the dedicated line status is in a non-cancelled state. If the dedicated line of the access number in the sub-slice work order is not found in the slice management system, the "no access number parameter" exception information will be recorded in the corresponding access result log; if the dedicated line of the access number is in a canceled state, the "the dedicated line status is in a canceled state and cannot be changed" exception information will be recorded in the corresponding access result log. Then determine whether there are fields in the work order that can be changed. If not, the "no fields to be changed" exception information will be recorded. Finally, compare the values ​​of the changed fields before and after the change to see if they are the same. If the values ​​of all changed fields before and after the change are the same, the "original value and modified value are the same" exception information will be recorded. If no exception information is recorded after the above checks, the access result log will record the successful reception of the sub-slice work order.

[0069] (3) Sub-slice work order for dedicated line deregistration: The receiving process of this type of work order only needs to verify whether the dedicated line exists and whether the dedicated line is in a non-deregistered state; if the dedicated line does not exist, it records the abnormal information of "no dedicated line with this access number"; if the dedicated line is in a deregistered state, it records the abnormal information of "the dedicated line is already in a deregistered state and cannot be deregistered again"; otherwise, it records the information of "successful reception".

[0070] Then analyze the content in the access result log to determine whether there is any abnormality in the access of the sub-slice dedicated line. If the above-mentioned abnormal record appears in the access result log, it can be considered that the work order reception is abnormal, indicating that the configuration failure of the corresponding sub-slice work order occurs in the work order reception process.

[0071] Step S3: If the work order reception status is normal, call the second log interface to obtain the script generation status.

[0072] In an embodiment of the present application, if it is determined that there is no abnormality in the work order reception, the second log interface is called according to the sub-slice work order number to obtain the script generation log.

[0073] Furthermore, the script generation log records any anomalies during the sub-slice configuration script generation process, which is divided into two steps: parameter verification and script generation. The parameters involved are the DNN name, VLAN ID, slice ID, and client terminal IP address pool. The three parameters, DNN name, VLAN ID, and slice ID, all have corresponding verification rules on the network element. That is, DNN names cannot be repeated on the same network element, a VLAN ID can only be bound to one DNN name, and a slice ID can be bound to multiple DNN names, but DNN names cannot be repeated.

[0074] During the parameter verification phase, you need to log in to the NE system to verify that the above parameters have been configured. If there are any configuration issues, a corresponding exception will be recorded in the script generation log, such as if the DNN name already exists on the NE. In addition, the client terminal IP address pool parameter only needs to be verified to ensure that its format conforms to CIDR notation, without further verification on the NE system. If it does not conform, an exception log message "Client terminal IP address pool format error" will be recorded in the script generation log.

[0075] The script generation phase mainly involves filling parameters into the preset template. Since there are generally no abnormal situations, there are no abnormal records of this phase in the script generation log.

[0076] After obtaining the script generation log, we analyze it, primarily to check the parameter verification of the sub-slice configuration script. Whether the script generation log contains any exceptions related to the parameter verification phase determines whether the script was successfully generated, and the sub-slice configuration status is obtained. Based on the sub-slice configuration status, we can confirm that the configuration failure of the sub-slice work order occurred during the sub-slice configuration script generation process.

[0077] Step S4: If there is no abnormality in the script generation, the third log interface is called to obtain the sub-slice configuration status.

[0078] In an embodiment of the present application, after confirming that there is no abnormality in the sub-slice configuration, the third log interface is called according to the sub-slice work order number to obtain the configuration delivery log.

[0079] Because sub-slice configuration delivery executes the corresponding MML script configuration commands line by line on the network element, if a configuration command fails to execute, the configuration delivery log will record this configuration command and the configuration failure information returned by executing this configuration command. If all configuration commands are executed successfully, the configuration success information will be recorded in the configuration delivery log.

[0080] Parse the configuration delivery log to check whether there are configuration failure or success information in the log. If there is failure information, it means that the sub-slice configuration script configuration process has failed; if there is success information, it means that the sub-slice configuration script configuration process has not failed, thus obtaining the sub-slice configuration status.

[0081] Step S5: Based on the work order reception, script generation, and sub-slice configuration, troubleshooting is performed through the agent knowledge base to obtain troubleshooting results and troubleshooting suggestions.

[0082] In the embodiment of the present application, it is first determined whether the work order reception situation is abnormal. If the work order reception situation is abnormal, indicating that the fault occurred during the work order reception process, then based on the repair suggestion template of the agent knowledge base, the slice check agent uses the NLP generation method based on the access result log and the corresponding abnormal repair suggestions obtained from the agent knowledge base to generate human natural language troubleshooting results and fault repair suggestions, and outputs the troubleshooting results and fault repair suggestions to the chat assistant for display.

[0083] After confirming that there are no abnormalities in the receipt of the work order, the script generation situation is judged. If the script generation situation is abnormal, it means that the fault occurred in the sub-slice configuration script generation process, and the parameter configuration problem is determined based on the agent knowledge base and the script generation log. If there are three parameters that need to be queried in the network element system, namely DNN name, vlan ID and slice ID, first obtain the MML query instruction for the configuration parameters required for the instruction to be generated from the agent knowledge base, and log in to the network element system and use the network element corresponding to the query instruction to execute the query instruction to obtain real-time network element configuration information. Finally, based on the real-time network element configuration information and the corresponding abnormality repair suggestions obtained from the agent knowledge base, generate human natural language troubleshooting results and fault repair suggestions, and output the troubleshooting results and fault repair suggestions to the chat assistant for display.

[0084] After confirming that there are no abnormalities in the script generation, the sub-slice configuration is finally judged. If the sub-slice configuration is abnormal, indicating that the fault occurred during the sub-slice configuration script configuration process, the MML query instruction for the script configuration is obtained from the agent knowledge base based on the MML script configuration command, and the MML query instruction is executed in the network element corresponding to the MML query instruction to determine whether the sub-slice configuration conflicts with the existing network and obtain the corresponding real-time network element configuration information. Finally, based on the real-time network element configuration information and the corresponding abnormality repair suggestions obtained from the agent knowledge base, the troubleshooting results and fault repair suggestions in human natural language are generated, and the troubleshooting results and fault repair suggestions are output to the chat assistant for display.

[0085] The implementation of the embodiments of the present application has the following beneficial effects:

[0086] The embodiment of the present application first builds a slice verification agent based on the AI ​​intelligent body and includes an agent knowledge base. After the sub-slice work order number is transmitted to the slice verification agent, the slice verification agent will call three different log call interfaces respectively to troubleshoot the sub-slice configuration work order receiving process, the sub-slice configuration script generation process and the sub-slice configuration script configuration process, thereby realizing automatic monitoring and troubleshooting of the sub-slice work order configuration process, thereby greatly improving the efficiency and accuracy of troubleshooting and further reducing labor costs; by checking whether the log contains abnormal records, determining the link where the fault occurs, and then using NLP technology to generate human natural language troubleshooting results and fault repair suggestions based on the abnormal repair suggestion template provided by the agent knowledge base, the accuracy of the analysis results is improved.

[0087] Second embodiment

[0088] Furthermore, in order to execute the configuration troubleshooting system of the 5G core network sub-slice corresponding to the above method embodiment to achieve the corresponding functions and technical effects, Figure 3 A structural diagram of a 5G core network sub-slice configuration troubleshooting system is provided. For ease of illustration, only the parts related to this embodiment are shown. The 5G core network sub-slice configuration troubleshooting system provided in this embodiment of the application includes:

[0089] The verification agent startup module 201 is used to send the sub-slice work order number to the preset slice verification agent; wherein, the slice verification agent includes a first log interface, a second log interface, a third log interface and an agent knowledge base, the first log interface is used to call the access result log that records the work order reception process, the second log interface is used to call the script generation log that records the sub-slice configuration script generation process, and the third log interface is used to call the configuration delivery log that records the sub-slice configuration script configuration process.

[0090] In this embodiment of the present application, a slice verification agent and a chat assistant are newly created on a pre-set AI agent; wherein, the sub-slice work order number is transmitted to the slice verification agent via the chat assistant. The slice verification agent also includes an agent knowledge base.

[0091] The work order reception status checking module 202 is used to call the first log interface to obtain the work order reception status according to the sub-slice work order number.

[0092] In this embodiment of the present application, the first log interface is called based on the sub-slice work order number to obtain an access result log. The access status of the sub-slice dedicated line is queried based on the access result log to obtain the work order receipt status. Different types of sub-slice work orders have different receipt processes, and the access result log records any exceptions that occur during the receipt process.

[0093] Analyze the contents in the access result log to determine whether there is any abnormality in the access of the sub-slice dedicated line. If there is an abnormal record in the access result log, it can be considered that the work order reception is abnormal, indicating that the configuration failure of the corresponding sub-slice work order occurs in the work order reception process.

[0094] The script generation status checking module 203 is configured to call the second log interface to obtain the script generation status if the work order reception status is normal.

[0095] In an embodiment of the present application, if the work order reception status is normal, the second log interface is called according to the sub-slice work order number to obtain a script generation log. After obtaining the script generation log, it is parsed, mainly to check the parameter verification of the sub-slice configuration script. Whether the script generation log contains abnormal logs related to the parameter verification phase is used to determine whether the script was successfully generated, thereby obtaining the sub-slice configuration status. Based on the sub-slice configuration status, it can be confirmed that the configuration failure of the sub-slice work order occurred during the sub-slice configuration script generation process.

[0096] The script generation log records any anomalies during the sub-slice configuration script generation process, which is divided into two steps: parameter verification and script generation. The parameters involved are the DNN name, VLAN ID, slice ID, and client terminal IP address pool. The three parameters, DNN name, VLAN ID, and slice ID, all have corresponding verification rules on the network element. DNN names cannot be repeated on the same network element, a VLAN ID can only be bound to one DNN name, and a slice ID can be bound to multiple DNN names, but DNN names cannot be repeated.

[0097] The sub-slice configuration status checking module 204 is used to call the third log interface to obtain the sub-slice configuration status if the script generation status is normal.

[0098] In an embodiment of the present application, if there is no abnormality in the script generation, the third log interface is called according to the sub-slice work order number to obtain the configuration delivery log.

[0099] Because sub-slice configuration delivery executes the corresponding MML script configuration commands line by line on the network element, if a configuration command fails to execute, the configuration delivery log will record this configuration command and the configuration failure information returned by executing this configuration command. If all configuration commands are executed successfully, the configuration success information will be recorded in the configuration delivery log.

[0100] Parse the configuration delivery log to check whether there are configuration failure or success information in the log. If there is failure information, it means that the sub-slice configuration script configuration process has failed; if there is success information, it means that the sub-slice configuration script configuration process has not failed, thus obtaining the sub-slice configuration status.

[0101] The troubleshooting result generation module 205 is used to perform troubleshooting through the agent knowledge base according to the work order reception status, script generation status and sub-slice configuration status, and obtain troubleshooting results and troubleshooting suggestions.

[0102] In an embodiment of the present application, if the work order reception situation is abnormal, the troubleshooting results and fault repair suggestions are obtained through the NLP generation method based on the repair suggestion template of the agent knowledge base; if the script generation situation or the sub-slice configuration situation is abnormal, the real-time network element configuration information is obtained through the agent knowledge base, and then based on the repair suggestion template, the troubleshooting results and fault repair suggestions are obtained through the NLP generation method.

[0103] In some embodiments, the verification agent startup module 201 further includes:

[0104] A slice verification agent and a chat assistant are newly created on the AI ​​agent to be responsible for troubleshooting sub-slice dedicated lines, and then the relevant information of the sub-slice work order is provided to the slice verification agent.

[0105] Furthermore, the receiving logic of the sub-slice work order, the generation logic of the sub-slice configuration script, the sending logic of the sub-slice configuration script, and the task content that the sub-slice configuration script is responsible for can be provided to the slice verification agent in a prompt manner, and three log call interfaces are registered in the slice verification agent based on this information, namely, the first log interface for calling the access result log of the work order receiving process, the second log interface for calling the script generation log of the sub-slice configuration script generation process, and the third log interface for calling the configuration sending log of the sub-slice configuration script configuration process.

[0106] This AI-based slice verification agent can realize automated monitoring and troubleshooting of the sub-slice work order configuration process. It can also process large amounts of data simultaneously and perform intelligent analysis and judgment based on preset rules, thereby greatly improving the efficiency and accuracy of troubleshooting.

[0107] At the same time, an agent knowledge base is configured for the slice verification agent, and the MML commands required for configuration issuance in the sub-slice configuration script, as well as command descriptions, logs of successful MML command execution, logs of execution exceptions, and modification suggestions for exceptions are uploaded to the agent knowledge base in the form of files, and these contents are vectorized. Among them, the MML command is a basic human-machine language command set for managing network equipment, mainly used to modify and adjust system parameters, including internal communication methods and end-to-end detection parameters. In the embodiment of the present application, the MML command is mainly executed on the network element related to the sub-slice dedicated line deployment configuration to realize the troubleshooting of the sub-slice configuration script generation process and the script configuration process.

[0108] The embodiment of the present application establishes an agent knowledge base including MML commands, command descriptions, log information, etc., and vectorizes this information, so that the slice check agent can quickly understand and process various information in the sub-slice configuration process, providing strong data support for sub-slice configuration troubleshooting.

[0109] After creating the slice verification agent, the operator sends the sub-slice work order number to be checked to the slice verification agent through the chat assistant. The slice verification agent obtains the sub-slice work order number through NLU technology. Among them, NLU technology can convert human speech into structured ontology, enabling computers to understand and interpret the meaning and intention of human natural language. In this embodiment of the application, NLU technology can convert the sub-slice work order number entered by the human into information that the slice verification agent can understand, so as to carry out subsequent troubleshooting, realizing human-computer interaction.

[0110] In some embodiments, the work order reception status checking module 202 further includes:

[0111] There are three common types of sub-slice work orders and corresponding access result logs that record abnormal situations:

[0112] (4) Sub-slice work orders for dedicated line activation: The process of receiving this type of work order involves access number uniqueness verification, DNN name uniqueness verification, VLAN ID automatic allocation, slice ID automatic allocation, etc. If the same access number and DNN name are found in the slice management system, a corresponding verification exception information will be generated in the access result log; due to the limited number of VLAN IDs or slice IDs, if no VLAN ID or slice ID can be allocated to the sub-slice dedicated line, an exception log about VLAN ID or slice ID resource exhaustion will be generated;

[0113] (5) Sub-slice work orders for dedicated line changes: The receiving process of this type of work order must first determine whether the dedicated line to be changed in the work order exists and whether the dedicated line status is in a non-cancelled state. If the dedicated line of the access number in the sub-slice work order is not found in the slice management system, the "no access number parameter" exception information will be recorded in the corresponding access result log; if the dedicated line of the access number is in a canceled state, the "the dedicated line status is in a canceled state and cannot be changed" exception information will be recorded in the corresponding access result log. Then determine whether there are fields in the work order that can be changed. If not, the "no fields to be changed" exception information will be recorded. Finally, compare the values ​​of the changed fields before and after the change to see if they are the same. If the values ​​of all changed fields before and after the change are the same, the "original value and modified value are the same" exception information will be recorded. If no exception information is recorded after the above checks, the access result log will record the successful reception of the sub-slice work order.

[0114] Sub-slice work order for dedicated line deregistration: The receiving process of this type of work order only needs to verify whether the dedicated line exists and is in a non-deregistered state; if the dedicated line does not exist, it will record "No dedicated line with this access number"; if the dedicated line is in a deregistered state, it will record the exception message "The dedicated line is already in a deregistered state and cannot be deregistered again"; otherwise, it will record the message "Received successfully".

[0115] In some embodiments, the script generation status checking module 203 further includes:

[0116] The sub-slice configuration script generation process consists of two steps: parameter verification and script generation. The script generation log records any failures that occur during these two stages and leaves exception records. During the parameter verification phase, you need to log in to the network element system to verify that the above parameters have been configured. If there is a parameter configuration problem, a corresponding exception record will be included in the script generation log, such as if the DNN name already exists on the network element. In addition, the client terminal IP address pool parameter only needs to be verified to ensure that its format conforms to CIDR notation, without verification on the network element system. If it does not conform, the "Client terminal IP address pool format error" exception log will be recorded in the script generation log.

[0117] The script generation phase mainly involves filling parameters into the preset template. Since there are generally no abnormal situations, there are no abnormal records of this phase in the script generation log.

[0118] In some embodiments, the troubleshooting result generating module 205 further includes:

[0119] First, determine whether the work order reception is abnormal. If the work order reception is abnormal, indicating that the fault occurred during the work order reception process, then based on the repair suggestion template in the agent knowledge base, the slice check agent uses the NLP generation method based on the access result log and the corresponding abnormal repair suggestions obtained from the agent knowledge base to generate human natural language troubleshooting results and fault repair suggestions. The troubleshooting results and fault repair suggestions are output to the chat assistant for display.

[0120] After confirming that there are no abnormalities in the receipt of the work order, the script generation situation is judged. If the script generation situation is abnormal, it means that the fault occurred in the sub-slice configuration script generation process, and the parameter configuration problem is determined based on the agent knowledge base and the script generation log. If there are three parameters that need to be queried in the network element system, namely DNN name, vlan ID and slice ID, first obtain the MML query instruction for the configuration parameters required for the instruction to be generated from the agent knowledge base, and log in to the network element system and use the network element corresponding to the query instruction to execute the query instruction to obtain real-time network element configuration information. Finally, based on the real-time network element configuration information and the corresponding abnormality repair suggestions obtained from the agent knowledge base, generate human natural language troubleshooting results and fault repair suggestions, and output the troubleshooting results and fault repair suggestions to the chat assistant for display.

[0121] After confirming that there are no abnormalities in the script generation, the sub-slice configuration is finally judged. If the sub-slice configuration is abnormal, indicating that the fault occurred during the sub-slice configuration script configuration process, the MML query instruction for the script configuration is obtained from the agent knowledge base based on the MML script configuration command, and the MML query instruction is executed in the network element corresponding to the MML query instruction to determine whether the sub-slice configuration conflicts with the existing network and obtain the corresponding real-time network element configuration information. Finally, based on the real-time network element configuration information and the corresponding abnormality repair suggestions obtained from the agent knowledge base, the troubleshooting results and fault repair suggestions in human natural language are generated, and the troubleshooting results and fault repair suggestions are output to the chat assistant for display.

[0122] The implementation of the embodiments of the present application has the following beneficial effects:

[0123] The embodiment of the present application realizes automatic troubleshooting of the automated process of slicing work orders by creating a slice verification agent in an AI agent, reducing labor costs, improving analysis and verification efficiency and the accuracy of analysis results, thereby improving operational efficiency and user experience. Among them, the troubleshooting process of the slice verification agent does not require human intervention, reducing the need for manual troubleshooting and manual operation, greatly improving the efficiency of troubleshooting, and the AI ​​agent can also process large amounts of data in real time, so it can discover and solve problems in a short time, avoiding the expansion and spread of faults. Moreover, the chat assistant configured for the slice verification agent also realizes natural language interaction with operators through NLP technology. This not only improves the user experience, but also can more accurately understand the user's needs and problems, thereby providing more accurate troubleshooting suggestions.

[0124] Third embodiment

[0125] Further, Figure 4 This is a structural diagram of a terminal device provided in one embodiment of the present application. Figure 4 As shown, the terminal device 3 of this embodiment includes: at least one processor 30 (in Figure 4 Only one is shown) and a memory 31 and a computer program 32 stored in the memory 31 and executable on the at least one processor. When the processor 30 executes the computer program 32, the steps of a method for troubleshooting configuration of a 5G core network sub-slice as described in any one of the embodiments of the present application can be implemented.

[0126] The terminal device 3 may be a computing device such as a desktop computer, a cloud server, or a laptop computer. The computing device may include but is not limited to a processor 30 and a memory 31 . Figure 4 This is merely an example of the terminal device 3 and does not constitute a limitation on the terminal device 3 , which may include more or fewer components than those shown in the figure.

[0127] An embodiment of the present application provides a storage medium storing computer-readable program code, which, when executed, implements the steps of the above-mentioned method for troubleshooting configuration of a 5G core network sub-slice.

[0128] The specific embodiments described above further illustrate the purpose, technical solutions, and beneficial effects of this application. It should be understood that the above description is merely a specific embodiment of this application and is not intended to limit the scope of protection of this application. In particular, it should be noted that for those skilled in the art, any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application should be included in the scope of protection of this application.

Claims

1. A method for troubleshooting configuration failures of 5G core network sub-slices, characterized in that: include: Send the sub-slice work order number to a preset slice verification agent; wherein the slice verification agent includes a first log interface, a second log interface, a third log interface and an agent knowledge base, the first log interface is used to call the access result log recording the work order reception process, the second log interface is used to call the script generation log recording the sub-slice configuration script generation process, and the third log interface is used to call the configuration delivery log recording the sub-slice configuration script configuration process; According to the sub-slice work order number, call the first log interface to obtain the work order reception status; If the work order reception status is normal, calling the second log interface to obtain the script generation status; If the script generation is normal, the third log interface is called to obtain the sub-slice configuration; According to the work order reception situation, script generation situation and sub-slice configuration situation, troubleshooting is performed through the agent knowledge base to obtain troubleshooting results and fault repair suggestions.

2. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 1, wherein: The sub-slice work order number is sent to the preset slice verification agent, specifically: Create a slice verification agent and a chat assistant on the pre-set AI agent; The sub-slice work order number is transmitted to the slice verification agent through the chat assistant.

3. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 1, wherein: The first log interface is called according to the sub-slice work order number to obtain the work order reception status, specifically: According to the sub-slice work order number, call the first log interface to obtain the access result log; Query the access status of the sub-slice dedicated line based on the access result log to obtain the work order receipt status.

4. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 1, wherein: If the work order reception status is normal, the second log interface is called to obtain the script generation status, specifically: If the work order reception is normal, then the second log interface is called according to the sub-slice work order number to obtain a script generation log; Query the generation status of the sub-slice configuration script according to the script generation log to obtain the script generation status.

5. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 1, wherein: If the script generation is normal, the third log interface is called to obtain the sub-slice configuration, specifically: If the script generation is normal, the third log interface is called according to the sub-slice work order number to obtain the configuration delivery log; According to the configuration delivery log, query the configuration status of the sub-slice configuration script to obtain the sub-slice configuration status.

6. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 1, wherein: According to the work order reception, script generation and sub-slice configuration, the agent knowledge base is used to perform troubleshooting to obtain troubleshooting results and troubleshooting suggestions, specifically: If the work order reception is abnormal, then based on the repair suggestion template of the agent knowledge base, the fault troubleshooting results and fault repair suggestions are obtained through the NLP generation method; If the script generation situation or sub-slice configuration situation is abnormal, the real-time network element configuration information is obtained through the agent knowledge base, and then based on the repair suggestion template, the fault troubleshooting results and fault repair suggestions are obtained through the NLP generation method.

7. The method for troubleshooting configuration failures of a 5G core network sub-slice according to claim 6, wherein: The real-time network element configuration information is obtained through the agent knowledge base, specifically: Obtaining corresponding query instructions from the proxy knowledge base according to the script generation situation or sub-slice configuration situation; The query instruction is executed in the network element corresponding to the query instruction to obtain corresponding real-time network element configuration information.

8. A 5G core network sub-slice configuration troubleshooting system, characterized in that: include: Verify the agent startup module, work order reception status check module, script generation status check module, sub-slice configuration status check module and troubleshooting result generation module; Among them, the verification agent startup module is used to send the sub-slice work order number to the preset slice verification agent; wherein, the slice verification agent includes a first log interface, a second log interface, a third log interface and an agent knowledge base, the first log interface is used to call the access result log recording the work order reception process, the second log interface is used to call the script generation log recording the sub-slice configuration script generation process, and the third log interface is used to call the configuration delivery log recording the sub-slice configuration script configuration process; The work order reception status checking module is used to call the first log interface to obtain the work order reception status according to the sub-slice work order number; The script generation status checking module is used to call the second log interface to obtain the script generation status if the work order reception status is normal; The sub-slice configuration status checking module is configured to call the third log interface to obtain the sub-slice configuration status if the script generation status is normal; The troubleshooting result generation module is used to perform troubleshooting through the agent knowledge base based on the work order reception status, script generation status and sub-slice configuration status, and obtain troubleshooting results and troubleshooting suggestions.

9. A terminal device, characterized in that: It includes a processor and a memory, the memory stores a computer program, and when the processor executes the computer program, it implements the steps of a configuration troubleshooting method for a 5G core network sub-slice according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores computer-readable program code, which, when executed, implements the steps of a 5G core network sub-slice configuration troubleshooting method according to any one of claims 1 to 7.

Images