CN116669082A - Intelligent inspection method, device, equipment and storage medium for core network element - Google Patents
Intelligent inspection method, device, equipment and storage medium for core network element Download PDFInfo
- Publication number
- CN116669082A CN116669082A CN202310679355.7A CN202310679355A CN116669082A CN 116669082 A CN116669082 A CN 116669082A CN 202310679355 A CN202310679355 A CN 202310679355A CN 116669082 A CN116669082 A CN 116669082A
- Authority
- CN
- China
- Prior art keywords
- inspection
- result
- network element
- abnormal
- core network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007689 inspection Methods 0.000 title claims abstract description 333
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000002159 abnormal effect Effects 0.000 claims abstract description 225
- 238000012795 verification Methods 0.000 claims description 10
- 238000013507 mapping Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 description 20
- 230000006870 function Effects 0.000 description 13
- 238000012545 processing Methods 0.000 description 9
- 238000013461 design Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a core network element intelligent inspection method, device, equipment and storage medium. The method comprises the following steps: acquiring network element configuration information of a core network to be inspected, and generating a target inspection task of the core network to be inspected according to the network element configuration information; the core network to be inspected is inspected according to the target inspection task, and a core network inspection result is obtained, wherein the core network inspection result comprises a normal result and an abnormal result; when the core network inspection result is an abnormal result, generating a target emergency plan matched with the abnormal result according to a preset emergency plan library; pushing the core network inspection result and the target emergency plan to a user side. According to the method, the running health degree of the equipment is judged through the inspection condition of the equipment, and the corresponding emergency plan is automatically generated, so that the problems that the manual inspection is low in efficiency and the effective and timely emergency plan is lost are solved.
Description
Technical Field
The present application relates to communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for intelligent inspection of a core network element.
Background
The 5G communication network is used as the latest generation mobile communication technology, the service architecture of the core network is based on the cloud original architecture design, the micro service concept is used for reference, and the whole with a plurality of functions is split into a plurality of individuals with independent functions, so that the core network is more flexible. The network element is the minimum unit capable of being monitored and managed in network management, the structure and the function of the 5G core network element are gradually complex, the network is required to stably operate, the performance of the network element is required to be relied, and the hidden danger of the network element operation is required to be found through daily maintenance and regular inspection.
The conventional 5G core network element inspection is usually performed manually, and an operation and maintenance personnel periodically inspect each network element according to the type, inspection content and index of the network element provided by a network element manufacturer. When the related index inspection of the network element is abnormal, the operation and maintenance personnel communicate with the network element manufacturer according to experience, and jointly draw a solution.
The manual inspection mode requires operation and maintenance personnel to be familiar with and master inspection contents and indexes of various manufacturers, the manual inspection efficiency is low, the technical threshold is high, and when inspection abnormal results are encountered, the operation and maintenance personnel are often relied on to judge the inspection abnormal results, so that a standard and effective solution is difficult to provide in time.
Disclosure of Invention
The application provides a core network element intelligent inspection method, device, equipment and storage medium, which are used for solving the problems of low manual inspection efficiency and missing of an effective and timely emergency plan.
In a first aspect, the present application provides a method for intelligent inspection of a core network element, including:
acquiring network element configuration information of a to-be-inspected core network, and generating a target inspection task of the to-be-inspected core network according to the network element configuration information, wherein the core network comprises a plurality of network elements, the network element configuration information comprises an inspection task set and an inspection instruction set of each network element, and the inspection task set and the inspection instruction set have a mapping relation;
the core network to be inspected is inspected according to the target inspection task, and a core network inspection result is obtained, wherein the core network inspection result comprises a normal result and an abnormal result;
when the core network inspection result is an abnormal result, generating a target emergency plan matched with the abnormal result according to a preset emergency plan library, wherein the emergency plan library comprises a historical abnormal result and a solution corresponding to the historical abnormal result, and is used for matching the abnormal result with the historical abnormal result and generating the target emergency plan according to the matched solution corresponding to the historical abnormal result;
Pushing the core network inspection result and the target emergency plan to a user side.
In a possible implementation manner, the generating the target inspection task of the core network to be inspected according to the network element configuration information includes:
selecting part or all of the patrol tasks from the patrol task set of the network element as the to-be-patrol tasks of the network element;
taking a patrol instruction corresponding to the task to be patrol as an instruction to be verified, logging in a network element, inputting the instruction to be verified, and judging whether the instruction to be verified is executed correctly;
if yes, the instruction to be verified is successfully verified;
if not, the verification of the instruction to be verified fails, the instruction to be verified which fails to be verified is modified until the instruction to be verified is executed correctly, and the modified instruction to be verified covers the original inspection instruction;
traversing all network elements of the core network to be inspected, and generating a target inspection task according to the tasks to be inspected of all network elements and inspection instructions corresponding to the tasks to be inspected.
In a possible implementation manner, the target inspection task includes a network element list, an inspection task to be inspected of each network element in the network element list, and an inspection instruction corresponding to the inspection task to be inspected, and the inspecting the core network to be inspected according to the target inspection task to obtain a core network inspection result includes:
Issuing a patrol instruction to the network element according to the task to be patrol, wherein the patrol instruction is used for controlling the network element to execute the patrol task;
responding to an execution result of the inspection instruction, and generating an inspection result of the task to be inspected;
traversing the network element task to be inspected to generate a network element inspection result;
traversing network elements in the network element list to generate a core network inspection result.
In a possible implementation manner, the target inspection task further includes a standard index range corresponding to an inspection instruction, and the generating, in response to an execution result of the inspection instruction, an inspection result of the task to be inspected includes: comparing the execution result with the standard index range, and if the execution result accords with the standard index range, determining that the inspection result of the task to be inspected accords with the standard;
if the inspection results of the task to be inspected in the network element are all in accordance with the standard, the inspection results of the network element are normal results;
and when the network element inspection results in the core network are all normal results, the core network inspection results are normal results, otherwise, the core network inspection results are abnormal results.
In a possible implementation manner, the abnormal result and the historical abnormal result each include an abnormal network element type, an abnormal inspection task and an abnormal instruction execution value, and the generating a target emergency plan matched with the abnormal result according to a preset emergency plan library includes:
Generating an abnormal inspection model according to the abnormal network element type and the abnormal inspection task, acquiring a historical abnormal result which has the same abnormal inspection model as the abnormal result from the emergency plan library, and generating a first set, wherein the first set comprises at least one historical abnormal result;
if the number of the historical abnormal results corresponding to the same abnormal inspection model is not less than two, for the historical abnormal results with the same abnormal inspection model, calculating the difference value between the abnormal instruction execution value of the abnormal result and the abnormal instruction execution value of each historical abnormal result, and taking the historical abnormal result with the smallest absolute value of the difference value as the reference result of the abnormal inspection model;
a solution corresponding to the reference result is acquired as a target contingency plan.
In one possible implementation manner, if there is no historical abnormal result with the same abnormal network element type and the same abnormal inspection task as the abnormal result, the target emergency plan is a blank file, and a first label is added to the target emergency plan.
In a possible implementation manner, after pushing the core network inspection result and the target emergency plan to the user side, the method further includes:
Receiving an actual solution fed back by a user side, and comparing the target emergency plan with the actual solution;
and if the actual solution is different from the target emergency plan, feeding back the abnormal result and the actual solution to the emergency plan library.
In a second aspect, the present application provides an intelligent inspection device for a core network element, including:
the configuration module is used for acquiring network element configuration information of the core network to be inspected and generating a target inspection task of the core network to be inspected according to the network element configuration information; the core network comprises a plurality of network elements, the network element configuration information comprises a patrol task set and a patrol instruction set of each network element, and the patrol task set and the patrol instruction set have a mapping relation;
the inspection module is used for inspecting the core network to be inspected according to the target inspection task to obtain a core network inspection result, wherein the core network inspection result comprises a normal result and an abnormal result;
the emergency plan generation module is used for generating a target emergency plan matched with the abnormal result according to a preset emergency plan library when the core network inspection result is the abnormal result, wherein the emergency plan library comprises a historical abnormal result and a solution corresponding to the historical abnormal result, and the emergency plan library is used for matching the abnormal result with the historical abnormal result and generating the target emergency plan according to the solution corresponding to the matched historical abnormal result;
And the sending module is used for pushing the core network inspection result and the target emergency plan to the user side.
In a third aspect, the present application provides an electronic device, including a memory, a processor, and computer-executable instructions stored in the memory and executable on the processor, where the processor implements the core network element intelligent patrol method according to any one of the first aspects when executing the computer-executable instructions.
In a fourth aspect, the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the core network element intelligent patrol method of any one of the first aspects.
According to the core network element intelligent inspection method, device, equipment and storage medium provided by the application, network element configuration information of the core network to be inspected is obtained, a target inspection task of the core network to be inspected is generated according to the network element configuration information, the core network to be inspected is inspected according to the target inspection task, and a core network inspection result is obtained, wherein the core network inspection result comprises a normal result and an abnormal result, and the intellectualization and automation of equipment inspection and unified management of the running states of multiple types of equipment are realized; when the core network inspection result is an abnormal result, a target emergency plan matched with the abnormal result is generated according to a preset emergency plan library, the core network inspection result and the target emergency plan are pushed to a user side, the abnormal inspection result is matched, and a corresponding emergency plan is generated through the preset emergency plan library, so that the hidden danger of equipment operation can be found in time and processed in time, and the operation and maintenance cost is reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic diagram of an application scenario of an intelligent core network element inspection method according to an embodiment of the present application.
Fig. 2 is a flowchart of an intelligent inspection method for a core network element according to an embodiment of the present application.
Fig. 3 is a flowchart of a method for generating a target inspection task of the core network to be inspected according to the network element configuration information provided in this embodiment.
Fig. 4 is a flowchart of a method for generating a target emergency plan matched with the abnormal result according to a preset emergency plan library provided in this embodiment.
Fig. 5 is a schematic diagram of an intelligent core network element inspection device according to an embodiment of the present application.
Fig. 6 is a schematic structural diagram of an electronic device for intelligent inspection of a core network element according to an embodiment of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
First, the terms involved in the present application will be explained:
core network: is one of three components of a communication network and is responsible for processing and distributing data.
Network Element (Network Element): refers to a network element, which is the smallest unit that can be monitored and managed in network management. In the present application, the Network element of the 5G core Network also refers to a Network Function (Network Function).
In the related art, network element inspection of a 5G core network is mainly performed manually by operation and maintenance personnel, and according to a planned inspection period, the operation and maintenance personnel logs in each network element manually, so that the network elements execute instructions one by one, the result of each inspection item is judged according to the output of the instructions, whether the analysis equipment is abnormal or not is checked manually, the inspection efficiency is low, and because the types of the network elements are different, the inspection contents of the network elements are also different, and the problems of missing inspection and missing inspection are easy to occur. If the inspection result is abnormal, the individual experience and judgment of the operation and maintenance personnel are often relied on when the solution is prepared, and the solutions of different operation and maintenance personnel to the same problem are possibly different, so that the process is not strict and standard, key steps are easy to be omitted, and the abnormality cannot be handled in time.
Aiming at the technical problems, the embodiment of the application aims at providing an intelligent inspection method, device, equipment and storage medium for a core network element, wherein the core idea of the method is to access the core network element through an intelligent inspection platform, and automatically issue instructions and acquire results to each network element according to different configurations of the network element so as to realize the intellectualization and automation of equipment inspection; and by matching historical abnormal results with abnormal inspection results, a corresponding emergency plan is generated, so that the hidden trouble of equipment operation can be found out in time and processed in time, and the operation and maintenance cost is reduced.
In order to better understand the scheme of the embodiment of the present application, an application scenario related to the embodiment of the present application is described below.
Referring to fig. 1, fig. 1 is a schematic application scenario diagram of an intelligent inspection method for a core network element according to an embodiment of the present application, as shown in fig. 1, including an intelligent inspection platform 100 and a core network 200. The core network 200 includes a plurality of network elements, and the network elements respond to the instruction sent by the intelligent patrol platform 100 and perform related work. It should be noted that the network elements in the core network may be of the same type or different types. Illustratively, the network element may include a user plane function ((The User plane function, UPF), user data management (Unit Deployment Manager, UDM), unlicensed mobile access network core (UMA Network Controller, UNC), centralized coordination function (Point Coordination Function, PCF), binding support function (Binding Support Function, BSF), etc., and embodiments of the present application are not limited herein.
The intelligent inspection platform 100 establishes communication connection with the core network 200, sends an inspection instruction to network elements in the core network 200, and receives an inspection result. The intelligent patrol platform 100 includes a network element patrol configuration module, a network element patrol module, a data processing module, and an emergency plan library. The network element inspection configuration module can be used for configuring corresponding inspection content, inspection instructions and inspection period according to the type of the core network element to be inspected, verifying the executable of the inspection instructions through the northbound interface access network element, and finally generating a set of inspection tasks; the network element inspection module can be used for logging in the network element for inspection according to the inspection task and generating an inspection result; the emergency plan library can be used for storing historical abnormal data and solutions corresponding to the historical abnormal data; the data processing module can be used for selecting a historical abnormal result matched with the abnormal inspection result from the emergency plan library when the inspection result is abnormal, generating an emergency plan according to the corresponding relation between the historical abnormal result and the solution, and pushing the abnormal inspection result and the emergency plan to operation and maintenance personnel.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of an intelligent inspection method for a core network element according to an embodiment of the present application. As shown in fig. 2, the method of the present embodiment includes:
s201: the method comprises the steps of obtaining network element configuration information of a to-be-inspected core network, and generating a target inspection task of the to-be-inspected core network according to the network element configuration information, wherein the core network comprises a plurality of network elements, the network element configuration information comprises an inspection task set and an inspection instruction set of each network element, and the inspection task set and the inspection instruction set have a mapping relation.
The execution main body of the embodiment of the application can be a server or an intelligent patrol platform in the server, wherein the intelligent patrol platform can be realized by software.
The intelligent inspection platform can be in communication connection with the inspection core network to acquire network element configuration information in the inspection core network. Specifically, the network element configuration information may include the number of network elements in the routing inspection core network, the network element type, the routing inspection task set and the routing inspection instruction set of each network element.
It is understood that the network elements in the patrol core network may be of the same type or of different types. Different types of network elements have different patrol contents, and according to the patrol contents, the network elements have respective patrol task sets and patrol instruction sets corresponding to the patrol task sets. The inspection task set comprises a plurality of inspection tasks, the inspection instruction set comprises inspection instructions corresponding to the inspection tasks, and one inspection task can correspond to one inspection instruction or a plurality of inspection instructions. The network element executes the inspection instruction, namely the process that the network element completes the corresponding task.
In this step, the target inspection task of the core network to be inspected may include all the inspection tasks in the inspection task set of each network element, or may include only part of the inspection tasks in the inspection task set of each network element.
S202: and carrying out inspection on the core network to be inspected according to the target inspection task to obtain a core network inspection result, wherein the core network inspection result comprises a normal result and an abnormal result.
In the step, corresponding inspection instructions are issued to network elements in the core network to be inspected through a socket protocol according to a target inspection task, the network elements execute the inspection instructions and then feed back execution results, and core network inspection results are summarized and generated.
It can be understood that when a problem occurs in the execution of the inspection instruction by the network element, such as incapability of executing the inspection instruction, or an abnormal result of the inspection instruction is executed, the network element of the core network to be inspected is abnormal, and the inspection result of the core network is an abnormal result; when all network elements in the core network to be inspected normally execute inspection instructions, the inspection result of the core network is a normal result.
S203: and when the core network inspection result is an abnormal result, generating a target emergency plan matched with the abnormal result according to a preset emergency plan library.
In this embodiment, the emergency plan library includes a historical abnormal result and a solution corresponding to the historical abnormal result, and is configured to match the abnormal result with the historical abnormal result, and generate a target emergency plan according to the matched solution corresponding to the historical abnormal result.
In the step, a history abnormal result which is most matched with the abnormal result is selected from a preset emergency plan library, and specifically, the matched history abnormal result can be determined by the type of an abnormal network element, an abnormal inspection task and other elements in the abnormal result. If the abnormal result is that the inspection result of the a network element executing the A1 inspection task is abnormal, and the first historical abnormal result of the inspection result abnormality caused by the a network element executing the A1 inspection task is also present in the emergency plan library, the abnormal result and the first historical abnormal result can be considered to be matched, and a solution corresponding to the first historical abnormal result can be used as a target emergency plan, so that the operation and maintenance personnel can conveniently process the abnormal result.
S204: pushing the core network inspection result and the target emergency plan to a user side.
In the step, the core network inspection result and the target emergency plan are sent to the user side together, and the core network inspection result and the target emergency plan are presented through an interface, so that maintenance personnel can conveniently and intuitively check the core network inspection result and the target emergency plan, and abnormal network elements can be processed in time.
According to the intelligent core network element inspection method provided by the embodiment, the network element configuration information of the core network to be inspected is obtained, the target inspection task of the core network to be inspected is generated according to the network element configuration information, the core network to be inspected is inspected according to the target inspection task, the core network inspection result is obtained, operation and maintenance personnel do not need to log in the network elements one by one and then manually inspect, automatic network element inspection is realized, and inspection efficiency is improved; when the core network inspection result is an abnormal result, a target emergency plan matched with the abnormal result is generated according to a preset emergency plan library, the emergency plan library comprises a historical abnormal result and a solution corresponding to the historical abnormal result, the emergency plan library is used for matching the abnormal result with the historical abnormal result, the target emergency plan is generated according to the matched solution corresponding to the historical abnormal result, and the core network inspection result and the target emergency plan are pushed to a user side.
The technical scheme of the intelligent inspection method for the core network element is described in detail below.
In a possible implementation manner, in the core network element intelligent inspection method provided in this embodiment, when the target inspection task of the core network to be inspected is generated according to the network element configuration information, executable verification is performed on the inspection instruction corresponding to the target inspection task, so as to ensure reliability of inspecting the network element. Fig. 3 is a flowchart of a method for generating a target inspection task of the core network to be inspected according to the network element configuration information provided in this embodiment, where, as shown in fig. 3, the method includes:
s301: and selecting part or all of the patrol tasks from the patrol task set of the network element as the to-be-patrol tasks of the network element.
In this step, all the tasks of the inspection task set of the network element can be used as the to-be-inspected tasks of the network element, or part of the tasks in the inspection task set of the network element can be selected as the to-be-inspected tasks of the network element according to different emphasis points of inspection contents or inspection requirements.
It will be appreciated that for the same type of network elements in the core network to be inspected, different inspection tasks may be selected, depending on where the network elements are located.
S302: and taking the inspection instruction corresponding to the task to be inspected as an instruction to be verified, logging in a network element, inputting the instruction to be verified, and judging whether the instruction to be verified is executed correctly.
In the step, the corresponding network element can be logged in through the network management system of the northbound interface access network element, and the command to be verified is sent to the network element, so that the executable of the command to be verified is verified.
It can be understood that the network element feeds back the result of executing the instruction to be verified to the network management system of the network element, and the network management system automatically judges whether the result is normal and outputs "correct execution" or "execution failure" to the intelligent inspection platform.
S303: if yes, the instruction to be verified is successfully verified.
S304: if not, the verification of the instruction to be verified fails, the instruction to be verified which fails to be verified is modified until the instruction to be verified is executed correctly, and the modified instruction to be verified covers the original inspection instruction.
In the step, the instruction to be verified, which fails to verify, can be modified by replacing the inspection instruction, modifying the characters of the inspection instruction, and the like. And the modified instruction to be verified is sent to the network element again for verification until the network element can execute the instruction to be verified correctly. And because the modified command to be verified can be correctly executed by the network element, the modified command to be verified is written into the inspection command set corresponding to the network element, and a corresponding relation is established with the corresponding inspection task, so that the original inspection command is covered.
S305: traversing the network element of the core network to be inspected, and generating a target inspection task according to the task to be inspected of the network element and an inspection instruction corresponding to the task to be inspected.
In the step, executable verification is carried out on the to-be-inspected instruction of each network element in the to-be-inspected core network, the inspection instruction with failed verification is modified, and the inspection instruction passing verification and the corresponding inspection task are summarized to generate a target inspection task.
In the embodiment, the accuracy of the target inspection task is ensured by performing executable verification on the inspection instruction corresponding to the target inspection task, so that the error in the subsequent inspection of the network element caused by the error of the inspection instruction is avoided; the problem of confusion of inspection instructions of different types of network elements is avoided aiming at the network elements with different types in the core network.
In one possible implementation manner, the target inspection task includes a network element list, an inspection task to be inspected of each network element in the network element list, an inspection instruction corresponding to the inspection task, and a standard index range corresponding to the inspection instruction.
In this embodiment, the inspecting the core network to be inspected according to the target inspection task to obtain a core network inspection result includes: issuing a patrol instruction to the network element according to the task to be patrol, wherein the patrol instruction is used for controlling the network element to execute the patrol task; responding to an execution result of the inspection instruction, and generating an inspection result of the task to be inspected; traversing the network element task to be inspected to generate a network element inspection result; traversing network elements in the network element list to generate a core network inspection result.
In this embodiment, after receiving the execution result of the inspection instruction, the execution result and the standard index range may be compared, and if the execution result meets the standard index range, the inspection result of the task to be inspected meets the standard.
It can be understood that in this embodiment, the patrol architecture of the entire core network includes three layers from large to small: core network-each network element in the core network-each task to be patrolled and examined of network element. Therefore, the determination of the network element inspection result and the core network inspection result may be: if the inspection results of the task to be inspected in the network element are all in accordance with the standard, the inspection results of the network element are normal results; and when the network element inspection results in the core network are all normal results, the core network inspection results are normal results, otherwise, the core network inspection results are abnormal results.
In this embodiment, the network elements in the core network to be inspected are inspected according to the target inspection task, so that operation and maintenance personnel are not required to log in the network elements, and are not required to be familiar with inspection instructions of each type of network elements, all inspection operations can be efficiently executed strictly according to the preset target inspection task, and complete inspection results are automatically generated, so that the efficiency and the accuracy are high.
In one possible implementation, the exception result and the historical exception result each include an exception network element type, an exception patrol task, and an exception instruction execution value. Fig. 4 is a flowchart of a method for generating a target emergency plan matched with the abnormal result according to a preset emergency plan library, where, as shown in fig. 4, the generating a target emergency plan matched with the abnormal result includes:
s401: generating an abnormal inspection model according to the type of the abnormal network element and the abnormal inspection task, acquiring a historical abnormal result which has the same abnormal inspection model as the abnormal result from the emergency plan library, and generating a first set, wherein the first set comprises at least one historical abnormal result.
It will be appreciated that for an anomaly result there may be multiple anomalies, which may be from the same type of network element, or from different types of network elements, where anomalies for different inspection tasks may occur separately.
In this embodiment, according to the type of the abnormal network element and the abnormal routing task, the historical abnormal result matched with the abnormal result may be primarily screened out, so as to generate the first set. That is, if the network element type-network element inspection task is used as the network element inspection model, the historical abnormal result with the same network element inspection model as the abnormal result is screened from the preset emergency plan library.
S402: if the number of the historical abnormal results corresponding to the same abnormal inspection model is not less than two, for the historical abnormal results with the same abnormal inspection model, calculating the difference value between the abnormal instruction execution value of the abnormal result and the abnormal instruction execution value of each historical abnormal result, and taking the historical abnormal result with the smallest absolute value of the difference value as the reference result of the abnormal inspection model.
It will be appreciated that, due to the different execution values of the abnormal instructions, there may be a plurality of historical abnormal results having the same abnormal network element type and the same abnormal inspection task as the abnormal results, and the reference result may be only the historical abnormal result closest to the abnormal result.
In this step, for a plurality of historical abnormal results having the same abnormal inspection model, the historical abnormal result closest to the abnormal result is matched by comparing the absolute values of the differences.
S403: a solution corresponding to the reference result is acquired as a target contingency plan.
In this step, a solution corresponding to the reference result is acquired as a target emergency plan according to the correspondence between the history abnormality result and the solution. It can be understood that when there are multiple abnormal inspection models in the abnormal result, there are multiple corresponding target emergency plans.
It should be noted that, if there is no historical abnormal result with the same abnormal inspection model as the abnormal result, that is, the abnormal inspection model appears for the first time, the emergency plan library has no matched historical abnormal record, and no corresponding solution, and the operator needs to draw a solution. At this time, the target emergency plan can be blank file, and give the target emergency plan is added first label, first label can play the warning effect to fortune dimension personnel, for example, adopts the colour mark, like this, when the distribution, the priority lets experienced fortune dimension personnel handle, is favorable to distributing the manual resource more rationally, improves processing efficiency.
In this embodiment, an abnormal inspection model is generated according to the type of the abnormal network element and the abnormal inspection task, and the abnormal result is matched with the historical abnormal data with the abnormal inspection model in the emergency plan library to generate a corresponding emergency plan, so that the operation and maintenance personnel can perform effective and timely processing according to the emergency plan.
In a possible implementation manner, after pushing the core network inspection result and the target emergency plan to the user side, the method further includes: receiving an actual solution fed back by a user side, and comparing the target emergency plan with the actual solution; and if the actual solution is different from the target emergency plan, feeding back the abnormal result and the actual solution to the emergency plan library.
It can be understood that after the operation and maintenance personnel obtain the core network inspection result and the target emergency plan, related processing operations can be performed according to the target emergency plan, and the abnormal network elements can be processed according to experience or by using a new technology.
In the step, the intelligent inspection platform receives an actual solution adopted by an operation and maintenance person, compares the actual solution with a target emergency plan, and if the actual solution is different from the target emergency plan, proves that the operation and maintenance person has additional judgment on the abnormal result or adopts other feasible solutions, so that the corresponding relation between the abnormal result and the actual solution can be established and added into an emergency plan library.
In this embodiment, by comparing the actual solution with the target emergency plan, a corresponding relationship is established between the actual solution different from the target emergency plan and the abnormal result, and the corresponding relationship is added to the emergency plan library, so that the emergency plan library is continuously perfected.
Fig. 5 is a schematic diagram of an intelligent core network element inspection device according to an embodiment of the present application. As shown in fig. 5, the core network element intelligent patrol device includes a configuration module 51, a patrol module 52, an emergency plan generating module 53 and a sending module 54. Wherein:
The configuration module 51 is configured to obtain network element configuration information of a core network to be inspected, and generate a target inspection task of the core network to be inspected according to the network element configuration information; the core network comprises a plurality of network elements, the network element configuration information comprises a patrol task set and a patrol instruction set of each network element, and the patrol task set and the patrol instruction set have a mapping relation;
the inspection module 52 is configured to inspect the core network to be inspected according to the target inspection task to obtain a core network inspection result, where the core network inspection result includes a normal result and an abnormal result;
the emergency plan generating module 53 is configured to generate, when the core network inspection result is an abnormal result, a target emergency plan matched with the abnormal result according to a preset emergency plan library, where the emergency plan library includes a historical abnormal result and a solution corresponding to the historical abnormal result, and the emergency plan library is configured to match the abnormal result with the historical abnormal result, and generate the target emergency plan according to the solution corresponding to the matched historical abnormal result;
and the sending module 54 is configured to push the core network inspection result and the target emergency plan to the user side.
In one possible design, the configuration module 51 is specifically configured to:
selecting part or all of the patrol tasks from the patrol task set of the network element as the to-be-patrol tasks of the network element;
taking a patrol instruction corresponding to the task to be patrol as an instruction to be verified, logging in a network element, inputting the instruction to be verified, and judging whether the instruction to be verified is executed correctly;
if yes, the instruction to be verified is successfully verified;
if not, the verification of the instruction to be verified fails, the instruction to be verified which fails to be verified is modified until the instruction to be verified is executed correctly, and the modified instruction to be verified covers the original inspection instruction;
traversing all network elements of the core network to be inspected, and generating a target inspection task according to the tasks to be inspected of all network elements and inspection instructions corresponding to the tasks to be inspected.
In one possible design, the target inspection task includes a network element list, an inspection task to be inspected of each network element in the network element list, and an inspection instruction corresponding to the inspection task, and the inspection module 52 is specifically configured to:
issuing a patrol instruction to the network element according to the task to be patrol, wherein the patrol instruction is used for controlling the network element to execute the patrol task;
Responding to an execution result of the inspection instruction, and generating an inspection result of the task to be inspected;
traversing the network element task to be inspected to generate a network element inspection result;
traversing network elements in the network element list to generate a core network inspection result.
In one possible design, the target inspection task further includes a standard index range corresponding to an inspection instruction, and the inspection module 52 is specifically configured to:
comparing the execution result with the standard index range, and if the execution result accords with the standard index range, determining that the inspection result of the task to be inspected accords with the standard;
if the inspection results of the task to be inspected in the network element are all in accordance with the standard, the inspection results of the network element are normal results;
and when the network element inspection results in the core network are all normal results, the core network inspection results are normal results, otherwise, the core network inspection results are abnormal results.
In one possible design, the abnormal result and the historical abnormal result each include an abnormal network element type, an abnormal patrol task and an abnormal instruction execution value, and the emergency plan generation module 53 is specifically configured to:
generating an abnormal inspection model according to the type of the abnormal network element and the abnormal inspection task, acquiring a historical abnormal result which has the same abnormal inspection model as the abnormal result from the emergency plan library, and generating a first set, wherein the first set comprises at least one historical abnormal result;
If the number of the historical abnormal results corresponding to the same abnormal inspection model is not less than two, for the historical abnormal results with the same abnormal inspection model, calculating the difference value between the abnormal instruction execution value of the abnormal result and the abnormal instruction execution value of each historical abnormal result, and taking the historical abnormal result with the smallest absolute value of the difference value as the reference result of the abnormal inspection model;
a solution corresponding to the reference result is acquired as a target contingency plan.
In one possible design, if there is no historical abnormal result having the same abnormal network element type and the same abnormal inspection task as the abnormal result, the emergency plan generating module 53 is specifically configured to:
the generated target emergency plan is a blank file, and a first label is added to the target emergency plan.
In one possible design, the transmitting module 54 is further specifically configured to:
receiving an actual solution fed back by a user side, and comparing the emergency plan with the actual solution;
and if the actual solution is different from the emergency plan, feeding back the abnormal result and the actual solution to the emergency plan library.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
Fig. 6 is a schematic structural diagram of an electronic device for intelligent inspection of a core network element according to an embodiment of the present application. As shown in fig. 6, the electronic device of this embodiment includes: at least one processor 60 (only one shown in fig. 6), a memory 61, and a computer program stored in the memory 61 and executable on the at least one processor 60, the processor 60 implementing the steps in any of the various method embodiments described above when executing the computer program.
The electronic device may include, but is not limited to, a processor 60, a memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of an electronic device and is not meant to be limiting, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), the processor 60 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The specific implementation process of the processor 601 may refer to the above-mentioned method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.
The memory 61 may in some embodiments be an internal storage unit of the electronic device, such as a memory of the electronic device. The memory 61 may in other embodiments also be an external storage device of the electronic device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the electronic device. Further, the memory 61 may also include both an internal storage unit and an external storage device of the electronic device. The memory 61 is used to store an operating system, application programs, boot loader (BootLoader), data, and other programs and the like, such as program codes of computer programs and the like. The memory 61 may also be used to temporarily store data that has been output or is to be output.
The embodiments of the present application also provide a computer readable storage medium storing a computer program, which when executed by a processor implements steps of the above-described respective method embodiments.
The computer readable storage medium described above may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). The processor and the readable storage medium may reside as discrete components in the electronic device described above.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer-readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (10)
1. The intelligent inspection method for the core network element is characterized by comprising the following steps of:
acquiring network element configuration information of a to-be-inspected core network, and generating a target inspection task of the to-be-inspected core network according to the network element configuration information, wherein the core network comprises a plurality of network elements, the network element configuration information comprises an inspection task set and an inspection instruction set of each network element, and the inspection task set and the inspection instruction set have a mapping relation;
the core network to be inspected is inspected according to the target inspection task, and a core network inspection result is obtained, wherein the core network inspection result comprises a normal result and an abnormal result;
when the core network inspection result is an abnormal result, generating a target emergency plan matched with the abnormal result according to a preset emergency plan library, wherein the emergency plan library comprises a historical abnormal result and a solution corresponding to the historical abnormal result, and is used for matching the abnormal result with the historical abnormal result and generating the target emergency plan according to the matched solution corresponding to the historical abnormal result;
pushing the core network inspection result and the target emergency plan to a user side.
2. The method according to claim 1, wherein the generating the target routing task of the core network to be routed according to the network element configuration information comprises:
Selecting part or all of the patrol tasks from the patrol task set of the network element as the to-be-patrol tasks of the network element;
taking a patrol instruction corresponding to the task to be patrol as an instruction to be verified, logging in a network element, inputting the instruction to be verified, and judging whether the instruction to be verified is executed correctly;
if yes, the instruction to be verified is successfully verified;
if not, the verification of the instruction to be verified fails, the instruction to be verified which fails to be verified is modified until the instruction to be verified is executed correctly, and the modified instruction to be verified covers the original inspection instruction;
traversing the network element of the core network to be inspected, and generating a target inspection task according to the task to be inspected of the network element and an inspection instruction corresponding to the task to be inspected.
3. The method according to claim 1, wherein the target routing task includes a network element list, a routing task to be routed for each network element in the network element list, and a routing instruction corresponding to the routing task, and the routing of the core network to be routed according to the target routing task includes:
issuing a patrol instruction to the network element according to the task to be patrol, wherein the patrol instruction is used for controlling the network element to execute the patrol task;
Responding to an execution result of the inspection instruction, and generating an inspection result of the task to be inspected;
traversing the network element task to be inspected to generate a network element inspection result;
traversing network elements in the network element list to generate a core network inspection result.
4. The method of claim 3, wherein the target inspection task further comprises a standard index range corresponding to an inspection instruction, and wherein generating an inspection result of the task to be inspected in response to an execution result of the inspection instruction comprises: comparing the execution result with the standard index range, and if the execution result accords with the standard index range, determining that the inspection result of the task to be inspected accords with the standard;
if the inspection results of the task to be inspected in the network element are all in accordance with the standard, the inspection results of the network element are normal results;
and when the network element inspection results in the core network are all normal results, the core network inspection results are normal results, otherwise, the core network inspection results are abnormal results.
5. The method of claim 1, wherein the exception result and the historical exception result each comprise an exception network element type, an exception patrol task, and an exception instruction execution value, wherein generating a target emergency plan matching the exception result from a preset emergency plan library comprises:
Generating an abnormal inspection model according to the abnormal network element type and the abnormal inspection task, acquiring a historical abnormal result which has the same abnormal inspection model as the abnormal result from the emergency plan library, and generating a first set, wherein the first set comprises at least one historical abnormal result;
if the number of the historical abnormal results corresponding to the same abnormal inspection model is not less than two, for the historical abnormal results with the same abnormal inspection model, calculating the difference value between the abnormal instruction execution value of the abnormal result and the abnormal instruction execution value of each historical abnormal result, and taking the historical abnormal result with the smallest absolute value of the difference value as the reference result of the abnormal inspection model;
a solution corresponding to the reference result is acquired as a target contingency plan.
6. The method of claim 5, wherein the target emergency plan is a blank file and a first label is added to the target emergency plan if there is no historical anomaly result having the same anomaly network element type and the same anomaly routing task as the anomaly result.
7. The method of claim 1, wherein pushing the core network inspection result and the target emergency plan to the client further comprises:
Receiving an actual solution fed back by a user side, and comparing the target emergency plan with the actual solution;
and if the actual solution is different from the target emergency plan, feeding back the abnormal result and the actual solution to the emergency plan library.
8. An intelligent patrol device for a core network element, comprising:
the configuration module is used for acquiring network element configuration information of the core network to be inspected and generating a target inspection task of the core network to be inspected according to the network element configuration information; the core network comprises a plurality of network elements, the network element configuration information comprises a patrol task set and a patrol instruction set of each network element, and the patrol task set and the patrol instruction set have a mapping relation;
the inspection module is used for inspecting the core network to be inspected according to the target inspection task to obtain a core network inspection result, wherein the core network inspection result comprises a normal result and an abnormal result;
the emergency plan generation module is used for generating a target emergency plan matched with the abnormal result according to a preset emergency plan library when the core network inspection result is the abnormal result, wherein the emergency plan library comprises a historical abnormal result and a solution corresponding to the historical abnormal result, and the emergency plan library is used for matching the abnormal result with the historical abnormal result and generating the target emergency plan according to the solution corresponding to the matched historical abnormal result;
And the sending module is used for pushing the core network inspection result and the target emergency plan to the user side.
9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes the computer-executable instructions stored in the memory to implement the core network element intelligent patrol method according to any one of claims 1 to 7.
10. A computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and when executed by a processor, the computer executable instructions are configured to implement the core network element intelligent patrol method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310679355.7A CN116669082A (en) | 2023-06-08 | 2023-06-08 | Intelligent inspection method, device, equipment and storage medium for core network element |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310679355.7A CN116669082A (en) | 2023-06-08 | 2023-06-08 | Intelligent inspection method, device, equipment and storage medium for core network element |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116669082A true CN116669082A (en) | 2023-08-29 |
Family
ID=87714968
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310679355.7A Pending CN116669082A (en) | 2023-06-08 | 2023-06-08 | Intelligent inspection method, device, equipment and storage medium for core network element |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116669082A (en) |
-
2023
- 2023-06-08 CN CN202310679355.7A patent/CN116669082A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102622247B (en) | The BIOS information configuration-system of server and method | |
| US10268574B2 (en) | Deployment testing for infrastructure delivery automation | |
| US8990372B2 (en) | Operation managing device and operation management method | |
| CN110088744A (en) | A kind of database maintenance method and its system | |
| CN110058920A (en) | Virtual machine performance detection method and device, electronic equipment, storage medium | |
| CN105404268A (en) | Vehicle auditing and control of maintenance and diagnosis for vehicle systems | |
| CN110971464A (en) | Operation and maintenance automatic system suitable for disaster recovery center | |
| US20200033832A1 (en) | Techniques for providing a secured control parameter for multi-channel control of a machine | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| CN117422434A (en) | Wisdom fortune dimension dispatch platform | |
| CN106384283A (en) | Internet plus based service bus structure and service bus system | |
| CN111586022A (en) | Firewall opening verification method, electronic device, computer equipment and storage medium | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN110069382B (en) | Software monitoring method, server, terminal device, computer device and medium | |
| CN116669082A (en) | Intelligent inspection method, device, equipment and storage medium for core network element | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| EP3301564B1 (en) | Computer system, method of managing transmission of software with computer system, program therefor, and recording medium | |
| CN113168603A (en) | System and method for workload estimation | |
| CN111694724A (en) | Testing method and device of distributed table system, electronic equipment and storage medium | |
| CN113992491A (en) | Application program server group operation and maintenance management system, method and device | |
| CN115378812A (en) | Method and system for data center network equipment maintenance | |
| CN114168108A (en) | Code merging method and device, electronic equipment and computer readable storage medium | |
| CN114003250A (en) | Software deployment method and device | |
| CN113849378A (en) | Resource monitoring device, resource monitoring system, resource monitoring method, electronic device, and medium | |
| CN111638872A (en) | Automatic change reinforcement script system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |