Network fault sensing processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a network fault sensing processing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining alarm information, converting the alarm information into a script language, carrying out the network fault sensing processing, obtaining fault information, carrying out the fault diagnosis analysis processing of the fault information based on a heterogeneous interface arrangement mode, and obtaining a fault cause. And generating a corresponding disposal decision according to the fault reason, performing parameter verification and instruction rollback detection processing on the disposal decision, and performing execution operation on the instruction passing the detection. The embodiment of the invention can improve the network fault sensing processing efficiency, and can be widely applied to the technical field of computers.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a network fault perception and processing method, device, electronic device and storage medium. Background Art

[0002] In the field of network operation and maintenance, network fault diagnosis generally uses partially self-intelligent networks, that is, except for the execution of the system automatically, other capabilities are manually operated and interacted. This will result in a low degree of automation of the system, which cannot meet the increasing number of intelligent scenarios that require rapid iteration. In addition, the system uses hard code to implement automatic execution functions, which cannot form a rapid response capability, affecting the efficiency of operation and maintenance work. In summary, the technical problems existing in related technologies need to be improved. Summary of the invention

[0003] The main purpose of the embodiments of the present application is to propose a network fault perception and processing method, device, electronic device and storage medium, which can improve the efficiency of network fault perception and operation and maintenance work.

[0004] To achieve the above object, an embodiment of the present application provides a network fault perception processing method, the method comprising:

[0005] Get alarm information;

[0006] Convert the alarm information into a scripting language to perform network fault perception processing to obtain fault information;

[0007] Performing fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault;

[0008] A corresponding handling decision is generated according to the fault cause, and parameter verification and instruction rollback detection processing are performed on the handling decision, and the instructions that pass the detection are executed.

[0009] In some embodiments, converting the alarm information into a scripting language to perform network fault perception processing to obtain fault information includes the following steps:

[0010] Performing configuration parsing processing on the alarm information through scripting language code to obtain a parsing script;

[0011] Performing scenario arrangement processing on the parsing script to obtain a fault scenario;

[0012] The fault scenario is input into a model generator to perform fault type analysis and processing, and the fault information is obtained as an output.

[0013] In some embodiments, performing scenario arrangement processing on the parsing script to obtain a fault scenario includes the following steps:

[0014] Performing application capability analysis and serial arrangement processing on the parsed script to obtain virtual instructions;

[0015] The virtual instructions are uniformly arranged and processed according to functional applications to obtain the fault scenario.

[0016] In some embodiments, the performing fault diagnosis and analysis on the fault information based on the heterogeneous interface orchestration method to obtain the fault cause includes the following steps:

[0017] Perform configuration search processing on the fault information according to the manufacturer's instruction model to obtain configuration information;

[0018] Encapsulating the configuration information to obtain a heterogeneous interface;

[0019] Performing parameter arrangement processing on the heterogeneous interface to obtain a parameter arrangement interface;

[0020] The parameter arrangement interface is subjected to rule arrangement and process arrangement processing to obtain the cause of the fault.

[0021] In some embodiments, performing parameter arrangement processing on the heterogeneous interface to obtain a parameter arrangement interface includes the following steps:

[0022] Obtaining the communication network structure;

[0023] Performing topological division processing on the communication network networking structure to obtain a network topological structure;

[0024] Parameter definition processing is performed on the heterogeneous interface according to the network topology structure to obtain the parameter arrangement interface.

[0025] In some embodiments, the parameter verification and instruction rollback detection processing of the handling decision includes the following steps:

[0026] determining configuration parameters and configuration instructions according to the handling decision;

[0027] Perform parameter comparison processing on the configuration parameters according to the network link to obtain a verification result;

[0028] The configuration instruction is issued according to the verification result, and an abnormality detection is performed on the issued instruction. When an abnormality is detected, the issued instruction is rolled back.

[0029] In some embodiments, the step of performing abnormality detection on the issued instruction and rolling back the issued instruction when an abnormality is detected includes the following steps:

[0030] Performing label setting processing on the issued instruction to obtain a fallback label;

[0031] The issued instruction is run according to a preset trial operation time, and the issued instruction is tested according to a network operation state and a network performance index to obtain a test result;

[0032] When the detection result is that the sending is abnormal, the sending instruction is rolled back according to the rollback tag.

[0033] To achieve the above object, another aspect of an embodiment of the present application provides a network fault perception and processing device, the device comprising:

[0034] A first module is configured to obtain alarm information;

[0035] The second module is configured to convert the alarm information into a script language to perform network fault perception processing to obtain fault information;

[0036] The third module is configured to perform fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault;

[0037] The fourth module is configured to generate a corresponding handling decision according to the cause of the fault, perform parameter verification and instruction rollback detection processing on the handling decision, and execute the instructions that pass the detection.

[0038] To achieve the above-mentioned purpose, another aspect of an embodiment of the present application provides an electronic device, the electronic device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the above-mentioned method when executing the computer program.

[0039] To achieve the above objective, another aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0040] The embodiments of the present application include at least the following beneficial effects: The present application provides a network fault perception processing method, device, electronic device and storage medium. The scheme obtains alarm information, converts the alarm information into a scripting language to perform network fault perception processing to obtain fault information, and can autonomously perceive network faults in a scripting language, thereby improving the flexibility of the system. In addition, the scheme performs fault diagnosis and analysis processing on the fault information based on the heterogeneous interface orchestration method to obtain the cause of the fault, and can configure and orchestrate the diagnosis process to improve the efficiency of network fault diagnosis. In addition, the scheme generates corresponding disposal decisions based on the cause of the fault, and performs parameter verification and instruction rollback detection processing on the disposal decision, executes the instructions that pass the detection, and can verify and roll back the configuration decision, thereby improving the efficiency of network fault perception processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a flow chart of a network fault perception and processing method provided by an embodiment of the present application;

[0042] Figure 2 yes Figure 1 Flow chart of step S102 in FIG.

[0043] Figure 3 It is a schematic diagram of a network fault autonomous perception model provided in an embodiment of the present application;

[0044] Figure 4 yes Figure 1 Flow chart of step S103 in FIG.

[0045] Figure 5 It is a schematic diagram of a network fault autonomous diagnosis and analysis model provided in an embodiment of the present application;

[0046] Figure 6 is a schematic diagram of a network structure provided in an embodiment of the present application;

[0047] Figure 7 yes Figure 1 Flow chart of step S104 in FIG.

[0048] Figure 8 It is a schematic diagram of a fault autonomous handling decision process provided by an embodiment of the present application;

[0049] Fig. 9 It is a structural diagram of a network fault perception and processing device provided in an embodiment of the present application;

[0050] Fig.10 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.

[0052] It is understood that the terms "first", "second", etc. used in this application can be used to describe various concepts in this article, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another concept. For example, without departing from the scope of the embodiment of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".

[0053] The terms "at least one", "multiple", "each", "any", etc. used in this application, at least one includes one, two or more, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.

[0054] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0055] Before describing the embodiments of the present application in detail, some nouns and terms involved in the embodiments of the present application are first described. The nouns and terms involved in the embodiments of the present application are subject to the following explanations.

[0056] 1) Internet Protocol (IP): A network protocol used for data packet transmission and address allocation in computer networks. It defines how data is grouped, addressed, and routed in the network.

[0057] 2) Internet Protocol Radio Access Network (IPRAN): An Internet Protocol-based wireless access network architecture used to achieve the transmission and exchange of mobile communications and data services.

[0058] 3) Representational State Transfer Application Programming Interface (RESTful API): A design style and architectural principle for building network services and application programming interfaces based on the HTTP (Hypertext Transfer Protocol) protocol. Through the RESTful API, clients can use a unified interface to communicate with servers, requesting and transmitting representations of resources.

[0059] As artificial intelligence (AI) continues to evolve, the operation and maintenance of communication networks are gradually entering the deep waters of intelligence. TM Forum has defined the level of self-intelligent networks, which are divided into 6 levels from L0 to L5 to guide the automation and intelligence of networks and services, evaluate the value and advantages of self-intelligent network services, and create digital and intelligent operation and maintenance capabilities of "self-configuration, self-repair, and self-optimization". Among them, L0 represents manual operation and maintenance: the system provides auxiliary monitoring capabilities, and all dynamic tasks need to be performed manually. L1 represents auxiliary operation and maintenance: the system can perform specific repetitive subtasks according to pre-configuration to improve execution efficiency. L2 represents partially self-intelligent networks: in a specific external environment, the system can enable automated closed-loop operation and maintenance for specific units according to predefined rules / policies. L3 represents conditional self-intelligent networks: based on L2, the system can perceive environmental changes in real time, and perform self-optimization and self-adjustment in specific network specialties to adapt to the external environment. L4 represents highly self-intelligent networks: based on L3, the system can achieve predictive or proactive closed-loop management of business and customer experience-driven networks in a more complex cross-network domain environment, so as to analyze and make decisions. L5 stands for fully intelligent network: This level is the ultimate goal of telecommunications network evolution. The system has full-scenario closed-loop autonomy for multiple services, multiple fields, and the entire life cycle.

[0060] In the current network operation and maintenance field, the self-intelligence L2 (partially self-intelligence network) level is generally used, that is, except for "execution" which is automatic by the system, other capabilities are operated interactively by manual operation. The shortcomings of this level are obvious, mainly including: low degree of automation, unable to meet the increasing number of intelligent scenarios that require rapid iteration. The automatic execution function is implemented in a hard-coded way. When there are changes in network scenarios, equipment manufacturers and models, configuration scripts, business types, etc., the code needs to be modified and the system needs to be upgraded to meet them, and rapid response capabilities cannot be formed. The front and back ends of the system are highly coupled and cannot be heterogeneously decoupled, so it is difficult to have the capabilities of "autonomous perception", "autonomous analysis", and "autonomous decision-making".

[0061] In view of this, a network fault perception processing method, device, electronic device and storage medium are provided in the embodiments of the present application. The scheme obtains alarm information, converts the alarm information into a scripting language to perform network fault perception processing to obtain fault information, and can autonomously perceive network faults in a scripting language, thereby improving the flexibility of the system. In addition, the scheme performs fault diagnosis and analysis processing on the fault information based on a heterogeneous interface orchestration method to obtain the cause of the fault, and can configure and orchestrate the diagnosis process to improve the efficiency of network fault diagnosis. In addition, the scheme generates a corresponding disposal decision based on the cause of the fault, and performs parameter verification and instruction rollback detection processing on the disposal decision, executes the instructions that pass the detection, and can verify and roll back the configuration decision, thereby improving the efficiency of network fault perception processing.

[0062] A network fault perception processing method provided in an embodiment of the present application relates to the field of computer technology. A network fault perception processing method provided in an embodiment of the present application can be applied to a terminal, can also be applied to a server, and can also be software running in a terminal or a server. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and a car terminal, etc., but is not limited to this; the server side can be configured as an independent physical server, or it can be configured as a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network; the software can be an application that implements a network fault perception processing method, etc., but is not limited to the above forms.

[0063] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0064] Figure 1 is an optional flowchart of a network fault perception and processing method provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S101 to S104.

[0065] Step S101, obtaining alarm information;

[0066] Step S102, converting the alarm information into a script language to perform network fault perception processing to obtain fault information;

[0067] Step S103, performing fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault;

[0068] Step S104, generating a corresponding handling decision according to the fault cause, performing parameter verification and instruction rollback detection processing on the handling decision, and executing the instructions that pass the detection.

[0069] Steps S101 to S104 shown in the embodiment of the present application are to obtain alarm information and convert the alarm information into a script language and input it into a network fault autonomous perception model to perform network fault perception and obtain fault information. Among them, the alarm information is information uploaded by the device, and the corresponding alarm information can be sent through different equipment manufacturer instruction sets. The message content depends on the alarm reporting method, equipment manufacturer, model, version, alarm message type, etc. The alarm information is then converted into a script language, and the message content in the alarm information is parsed and configured using regular expressions, Python and other scripting languages, so as to design and arrange the corresponding alarm and hidden danger scenarios in a scripting language, and flexibly customize the generators of different types of alarms and hidden dangers in a building block manner, so as to realize the configurability of code, rules, processes, and tasks, and generate the corresponding fault information through configuration. Then, the fault information is analyzed and processed based on the heterogeneous interface orchestration method. The fault autonomous diagnosis and analysis process capability with heterogeneous interactive RESTful API as the core can configure and orchestrate the parameters, rules, conclusions, and instructions in the process. By reshaping the operation and maintenance model, the traditional black box, segmented, and manual operation and maintenance model is transformed into an active, pre-emptive, and R&D model, so as to diagnose and analyze the fault according to the corresponding orchestration process to obtain the cause of the fault. Finally, the corresponding disposal decision is generated according to the cause of the fault, and the disposal decision is verified and the instruction rollback detection is processed. The instructions that pass the detection are executed to ensure the safety and reliability of the autonomous disposal decision of the network fault. This solution can automatically check the parameters accurately before the configuration is issued by setting the capabilities of real-time parameter verification and automatic instruction rollback, and automatically set the rollback point to achieve rollback recovery once the disposal is abnormal.

[0070] In step S101 of some embodiments, alarm information can be obtained through data interaction instructions such as SNMP Trap, Syslog, Telemetry, etc. of major equipment manufacturers, but it is not limited thereto. Among them, SNMP Trap is an important component of the Simple Network Management Protocol (SNMP), which allows managed devices to actively send messages to the network management system (NMS) when specific events occur. This mechanism eliminates the need for network administrators to constantly poll devices, thereby saving computing resources. Syslog is a standard for transmitting log file messages on the Internet Protocol (TCP / IP) network. It allows devices such as servers, routers, firewalls, etc. to send event messages to designated log collection servers for centralized management and analysis. Telemetry is a technology for remotely collecting data from physical or virtual devices at high speed. The device periodically and actively sends information such as the device's interface traffic statistics, CPU or memory data to the collector through a push mode.

[0071] See also Figure 2 In step S102 of some embodiments, converting the alarm information into a script language for network fault perception processing to obtain fault information includes the following steps:

[0072] Step S201, performing configuration parsing processing on the alarm information through scripting language code to obtain a parsing script;

[0073] Step S202, performing scenario arrangement processing on the parsing script to obtain a fault scenario;

[0074] Step S203, performing fault type analysis processing on the fault scenario input model generator, and outputting the fault information.

[0075] In step S201 of some embodiments, a scripting language for parsing is developed for different alarm messages, and Python scripting can be used for parsing configuration, or regular expressions can be used for parsing configuration to obtain a parsing script for Syslog log messages. It is conceivable that the embodiment of the present application configures and parses the alarm information through scripting language code, and the parsing script can be directly configured into the system, thereby realizing the "white box" and "customization" of related functions, thereby solving the tight coupling problem of traditional software systems, achieving comprehensive decoupling, and being more conducive to the system to quickly respond and cope with network types, network structures, business scenarios, parameter changes, etc., and improving the efficiency of network fault perception and processing.

[0076] In step S202 of some embodiments, for the actual instructions generated by the scripting language, the system can provide a multi-level orchestration capability to perform scenario orchestration processing to obtain a fault scenario. The fault scenario can be orchestrated for multiple devices and multiple instruction sets to obtain a process, and the orchestration process can be a parallel process or a serial process, and can be applicable to network devices of different manufacturers, different versions, and different versions.

[0077] In step S203 of some embodiments, the fault scenario input model generator is subjected to fault type analysis and processing to output fault information, wherein the model generator is an automated model configured by the system according to the scripted language and scenario of the arrangement, which may include two categories: alarms and hidden dangers, wherein an alarm refers to a network fault that has been made explicit, such as equipment power failure, fiber interruption, protocol interruption, etc., which will generate corresponding alarms in real time. Hidden dangers refer to network faults that have not yet been made explicit, such as fiber quality degradation, which can still be used, but will cause the network quality to deteriorate. Another example is network link traffic congestion. Although the services on the link can still be used, they have already affected the user's download rate, application interaction delay, etc. There are more types of hidden dangers, and the judgment rules are more flexible and complex. Therefore, the system divides the model generator into two categories: an alarm model generator and a hidden danger model generator, but the real-time requirements for the two are different. It is conceivable that the embodiment of the present application configures different model generators according to the task. Different models can be targeted at different network types, introduce different orchestration scenarios, and set different execution cycles. Alarms can be more real-time, such as real-time, 5 minutes, 10 minutes, 20 minutes, etc. Hidden dangers can generally be longer, such as 1 hour, 1 day, etc. Through the configuration of alarm and hidden danger model generators, the system can independently realize flexible fault perception on the network side, and output corresponding fault information by analyzing the fault scenario.

[0078] See also Figure 3 In the embodiment of the present application, a network fault autonomous perception model can be pre-trained, and the instruction sets of various equipment manufacturers are input into the model for training, and the instruction sets (F1-F n ) to process the script language to obtain the parsing script, and then design the parsing script in combination with the instruction parameters to perform scene arrangement (S1-S m ) and then input into the alarm model generator M1 or the hidden danger model generator M2 for classification and output to obtain different alarm models and hidden danger models. After the training is completed, the real-time alarm information can be input into the network fault autonomous perception model for network fault perception to obtain fault information.

[0079] One of the above technical solutions has the following advantages or beneficial effects: The embodiment of the present application realizes the autonomous perception capability of network faults based on a scripting language, can adapt to the data interaction instructions such as SNMP Trap, Syslog, Telemetry of major network equipment manufacturers, and design and arrange the corresponding alarm and hidden danger scenarios in a scripting language. It can flexibly customize the generators of different types of alarms and hidden dangers in a building block manner, realize the configurability of codes, rules, processes, and tasks, and finally achieve the "perception" capability of L3 level self-intelligent network.

[0080] In step S202 of some embodiments, performing scenario arrangement processing on the parsed script to obtain a fault scenario includes the following steps:

[0081] Performing application capability analysis and serial arrangement processing on the parsed script to obtain virtual instructions;

[0082] The virtual instructions are uniformly arranged and processed according to functional applications to obtain the fault scenario.

[0083] In the embodiment of the present application, by analyzing the application function of the parsing script, the ability of the parsing script to realize a certain type of micro-application can be arranged as a virtual instruction, that is, the virtual instruction defines a capability for realizing a certain type of micro-application, and the real instruction is composed of a specific device-side instruction and a scripted language, and one or more real instructions can be arranged into a virtual instruction in a serial manner. Then the virtual instruction is arranged into a virtual instruction set, which is an arrangement set of multiple virtual instructions, and is often used to unify virtual instructions of different manufacturers, different models, and different versions into a virtual instruction set, so as to facilitate the upper layer application to perform autonomous calling. That is, the virtual instruction set is equivalent to an atomic capability that can shield the differences in manufacturers, models, and versions. Finally, the virtual instruction set is arranged into a scene. When the functional application needs to perform complex arrangement of multiple virtual instruction sets and form a unified capability, the scenario-based process arrangement can be performed. A scene can be arranged for multiple devices and multiple virtual instruction sets, and the arrangement process can be a parallel process or a serial process. Therefore, the scene is equivalent to the molecular capability of autonomously enclosing the atomic capability, which can unify the realization of a certain functional application. In a feasible embodiment, the system uniformly arranges a scenario of "IPRAN poor relay quality alarm" to realize the autonomous perception capability of alarm of poor relay quality, and the scenario is composed of multiple virtual instruction sets, virtual instructions, and real instructions, which can be applicable to network equipment of different manufacturers, different versions, and different versions.

[0084] One of the above technical solutions has the following advantages or beneficial effects: the embodiment of the present application performs application capability analysis on the parsing script to arrange the fault scenario, so that the arranged scenario can be applicable to different network devices, so that fault information can be quickly found based on the corresponding fault scenario, thereby improving data processing efficiency.

[0085] See also Figure 4 In step S103 of some embodiments, the fault diagnosis and analysis processing of the fault information based on the heterogeneous interface orchestration method to obtain the fault cause includes the following steps:

[0086] Step S401, performing configuration search processing on the fault information according to the manufacturer's instruction model to obtain configuration information;

[0087] Step S402, encapsulating the configuration information to obtain a heterogeneous interface;

[0088] Step S403, performing parameter arrangement processing on the heterogeneous interface to obtain a parameter arrangement interface;

[0089] Step S404: perform rule arrangement and process arrangement processing on the parameter arrangement interface to obtain the cause of the fault.

[0090] In step S401 of some embodiments, the fault information is configured and searched according to the manufacturer's instruction model, wherein the manufacturer's instruction model may include a CLI instruction model, a Netconf instruction model, and a Config instruction model. Specifically, the CLI instruction is the most common instruction method for network devices. Generally, the communication device can be logged in through SSH, and various information of the device, such as status, traffic, rate, packet loss, association, etc., can be viewed according to the instruction set defined by each manufacturer. Netconf is a new type of communication and interaction protocol between software systems and devices. Software systems such as network management can implement local management through the Netconf protocol, and perform operations such as installation, modification and deletion of the configuration of remote devices. The configuration information of the device can be restored, and the new configuration data can be loaded through the operation defined by the protocol, which is convenient for collecting various data states and configuration information stored on the network device. Netconf is a network configuration and management protocol based on the extensible markup language XML, and uses a simple RPC (Remote Procedure Call) mechanism to realize communication between the client and the server. The Config instruction model is another traditional instruction method. All network devices have their own device configuration files. When the external system modifies the configuration of the device based on the CLI or Netconf instruction, it will be stored in the device's own configuration file. Therefore, through the device's Config instruction model, the device's configuration information can be quickly obtained, thereby diagnosing various fault problems such as protocol configuration errors, IP address configuration errors, BGP Peer configuration errors, etc.

[0091] In step S402 of some embodiments, since the CLI instructions, Netconf instructions, and Config instructions input according to different manufacturers, models, and versions of devices have completely different instruction return results, the embodiments of the present application need to encapsulate the return results of these device-side real instructions into a unified JSON output result by developing corresponding virtual instructions, thereby obtaining a heterogeneous interface. Based on the development of virtual instructions, the development is carried out using a scripting language, and the heterogeneous interface is obtained by configuring the software system foreground page, which can facilitate rapid system configuration, flexible loading, and unified scheduling. Among them, there is a one-to-one correspondence between real instructions and virtual instructions, while there is a many-to-one relationship between virtual instructions and virtual instruction sets, which is mainly to avoid differences between different manufacturers, models, and versions. Taking the device optical port information viewing as an example, the instruction return results of different manufacturers are completely different. Therefore, if it is to be uniformly encapsulated into OPENAPI, i.e., a heterogeneous interface, it is necessary to normalize the instructions of different manufacturers at the virtual instruction level according to the unified input and output parameters. Then these virtual instructions are merged into a unified "Device Optical Port Query" virtual instruction set, namely Restful OPENAPI, to build a heterogeneous interface. For example, "RES_STN_IfTxPower_Query_API", this heterogeneous interface corresponds to the output parameter of the OPENAPI encapsulated CLI instruction of the optical port information of the device. The output parameter information includes the most core data in the result returned by the CLI instruction, such as received optical power, transmitted optical power, etc. When diagnosing optical path faults, it can be directly called heterogeneously across systems and platforms.

[0092] In step S403 of some embodiments, in a complex communication network, if one wants to perform configuration modeling through a unified Restful API, one needs to uniformly define and arrange the input and output parameters involved in the API to obtain a parameter arrangement interface.

[0093] In step S404 of some embodiments, by arranging the parameters of the parameter arrangement interface, that is, adding specific judgment rules, taking "RES_STN_IfTxPower_Query_API" as an example, it is judged whether the optical path is normal, which involves the judgment between multiple parameters in the return parameters of the RestfulAPI, and by arranging the rule that "the received optical power is between the lower threshold and the upper threshold of the received optical power, and the transmitted optical power is also between the lower threshold and the upper threshold of the transmitted optical power", the interface can be uniformly arranged on the foreground page of the software system, thereby ensuring the flexible configuration and modification of the rules. After the parameter arrangement and rule arrangement are completed, the process of various complex scenarios can be flexibly arranged. The embodiment of the present application arranges the parameters of the virtual instruction set, and the arrows of each virtual instruction set result involve the arrangement of "rules". All bifurcation positions, either to the virtual instruction set of the next step, or to directly obtain the diagnostic conclusion, can be flexibly arranged. After the process arrangement, the various conclusions obtained by the final design are the output of the autonomous fault diagnosis analysis. In a feasible embodiment, in an example of a diagnostic analysis, this diagnosis is automatically initiated by the system when a "status down" fault occurs, and the fault cause conclusion after automatic diagnostic analysis is the "optical path error" in the red box. Figure 5 The embodiment of the present application can pre-train a network fault autonomous diagnosis and analysis model, the input of which is different manufacturer instruction models. By converting different inputs into virtual instructions and virtual instruction sets, and then performing parameter arrangement, rule arrangement and process encoding through automatic reference parameter design, the corresponding diagnostic conclusions are output, such as optical path degradation, link congestion, etc.

[0094] One of the above technical solutions has the following advantages or beneficial effects: The embodiment of the present application implements autonomous diagnosis and analysis of network faults based on heterogeneous RESTful APIs, can perform heterogeneous interactions between different software systems, and also supports different network equipment manufacturers, models, versions, instruction types and capability sets. By enriching the capability set, the system can achieve autonomous diagnosis and analysis capabilities for flexible scheduling based on automated rules.

[0095] In step S403 of some embodiments, performing parameter orchestration processing on the heterogeneous interface to obtain a parameter orchestration interface includes the following steps:

[0096] Obtaining the communication network structure;

[0097] Performing topological division processing on the communication network networking structure to obtain a network topological structure;

[0098] Parameter definition processing is performed on the heterogeneous interface according to the network topology structure to obtain the parameter arrangement interface.

[0099] In the embodiments of the present application, the networking structure of the communication network is divided in detail, including four topological structures: a ring network structure, a multiple uplink structure, a U-shaped uplink structure, and a double cross uplink. Among them, a ring network refers to a group of devices that are interconnected in pairs in sequence, such as a device ring network; multiple uplinks (including single uplinks) refer to the interconnection between a single device and multiple devices, such as a broadband access server (BAS) and an optical line terminal (OLT) dual uplink; a U-shaped uplink refers to a pair of devices that are interconnected with another pair of devices in pairs, such as a U-shaped uplink between core devices and aggregation devices; a double cross uplink refers to a pair of devices that are interconnected with another pair of devices in pairs, such as the leaf-spine network architecture (Spine-Leaf) of a new metropolitan area network. After defining these network topological structures, the main parameters in the network can be referred to and defined. Please refer to Figure 6 , Figure 6 It is an IPRAN / STN network structure, involving a ring network and a port-shaped uplink mode. The figure includes a total of ten devices from device 601 to device 610. When the red circle device 605 in the figure fails (such as poor link relay quality), the faulty device is the starting device of the specified object, that is, the "local device". Based on this, it is possible to quickly define device 603 as the opposite device and the upstream device, device 606 as a parallel device, device 607 as a downstream device, and the corresponding local port, upstream port, parallel port, downstream port, etc. on the link. Through this specified definition, it can be designed and configured during process arrangement, and parameter variables can be used to ensure the effectiveness and accuracy of the Restful API call. In a feasible embodiment, the parameters of "RES_STN_IfTxPower_Query_API" refer to the configuration. Among them, the login device is the "uplink device", that is, if the fault is a Class B device, the query this time is the uplink device. The general parameters check the "uplink device downstream port", that is, the downstream port of the local ER device is checked during this API call. All Restful APIs have input parameters. The most commonly used input parameters are device IP and device port. Therefore, these parameters need to be accurately designed and configured to ensure the rationality and accuracy of the entire autonomous diagnosis process orchestration.

[0100] One of the above technical solutions has the following advantages or beneficial effects: The embodiment of the present application performs parameter arrangement for heterogeneous interfaces, and can ensure the effectiveness and accuracy of heterogeneous interface calls through parameter variables, thereby improving the rationality and accuracy of the entire autonomous diagnosis process arrangement.

[0101] See also Figure 7 In step S104 of some embodiments, the parameter verification and instruction rollback detection processing of the handling decision includes the following steps:

[0102] Step S701, determining configuration parameters and configuration instructions according to the handling decision;

[0103] Step S702, performing parameter comparison processing on the configuration parameters according to the network link to obtain a verification result;

[0104] Step S703: the configuration instruction is issued according to the verification result, and abnormality detection is performed on the issued instruction. When an abnormality is detected, the issued instruction is rolled back.

[0105] In the embodiment of the present application, the disposal decision can be implemented by the arrangement mode of heterogeneous interfaces (including parameter arrangement, rule arrangement, and process arrangement), but the fault disposal process is a write operation on the device side. If the disposal instruction is found to be wrong and the disposal parameter is wrong, it is possible to affect the network and the business. Therefore, the embodiment of the present application will analyze the disposal decision to obtain the configuration parameters and configuration instructions, verify the configuration parameters before issuing the configuration instructions, and compare the configuration parameters according to the network link to obtain the verification result. In a feasible embodiment, taking the modification of the link Cost (overhead) value as an example, it is necessary to query the Cost value of the target link before modification, the Cost value of the link with the same source end and the same destination end as the target link, and the Cost value of other links with equal-cost multi-path routing (Equal-Cost Multi-Path Routing, ECMP) with the target link, and compare these Cost values, and finally confirm the parameter value to be modified. After the verification is passed, the configuration instruction is issued, and the issued instruction is detected to be abnormal, and the issued instruction is rolled back when the abnormality is detected.

[0106] In step S703 of some embodiments, the performing of abnormality detection on the issued instruction and performing instruction rollback processing on the issued instruction when an abnormality is detected includes the following steps:

[0107] Performing label setting processing on the issued instruction to obtain a fallback label;

[0108] The issued instruction is run according to a preset trial operation time, and the issued instruction is tested according to a network operation state and a network performance index to obtain a test result;

[0109] When the detection result is that the sending is abnormal, the sending instruction is rolled back according to the rollback tag.

[0110] In the embodiment of the present application, before the device configuration is changed or the instruction is issued, the device rollback tag can be set to support the configuration rollback capability after the device configuration instruction is issued. When the configuration is issued abnormally, the executed configuration will be automatically rolled back to prevent junk data. Similarly, the embodiment of the present application supports the setting function of the device trial operation time: after the trial operation time is configured, the network operation status and network performance indicators can be observed during this period. If an abnormality occurs, the rollback can be done manually, or it can be rolled back automatically after a timeout. Please refer to Figure 8 , the embodiment of the present application sets a rollback indicator, then sends the first-order configuration data, performs anomaly detection on the configuration sending, rolls back the configuration data when anomalies exist, regenerates the configuration data, and returns to the step of setting the rollback indicator. When there are no anomalies, the second-order submission process is performed. If there is a configuration data timeout in the trial operation mode, the configuration data is regressed. If the configuration is effective and runs on the current network in the immediate execution mode, it can also be rolled back to the corresponding label point according to actual needs. The actual needs can be judged by observing the network operation status and network performance indicators.

[0111] The following is a detailed description of the embodiments of the present invention with reference to specific application examples:

[0112] See also Figure 8 , the embodiment of the present application realizes autonomous perception of network faults based on scripting language. By designing and arranging corresponding alarm and hidden danger scenarios in the form of scripting language by means of data interaction instructions, generators of different types of alarms and hidden dangers can be flexibly customized in a building block manner to realize the configurability of codes, rules, processes, and tasks. Then, autonomous diagnosis and analysis of network faults are realized based on heterogeneous RESTful API. Through the autonomous fault diagnosis and analysis process capability with heterogeneous interactive RESTful API (virtual instruction set) as the core, the parameters, rules, conclusions, and instructions in the process are configured and arranged. Finally, autonomous handling decisions of network faults are realized based on the self-protection mechanism, and capabilities such as real-time parameter verification and automatic rollback of instructions are set. By automatically checking the parameters for accuracy before the configuration is issued, and automatically setting the rollback point, once the handling and issuance exception is handled, rollback and recovery can be achieved.

[0113] See also Fig. 9 The embodiment of the present application also provides a network fault perception processing device, which can implement the above-mentioned network fault perception processing method, and the device includes:

[0114] The first module 901 is configured to obtain alarm information;

[0115] The second module 902 is configured to convert the alarm information into a script language to perform network fault perception processing to obtain fault information;

[0116] The third module 903 is configured to perform fault diagnosis and analysis on the fault information based on the heterogeneous interface orchestration method to obtain the cause of the fault;

[0117] The fourth module 904 is configured to generate a corresponding handling decision according to the fault cause, perform parameter verification and instruction rollback detection processing on the handling decision, and execute the instructions that pass the detection.

[0118] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0119] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned network fault perception and processing method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0120] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0121] See also Fig.10 , Fig.10 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0122] The processor 1001 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0123] The memory 1002 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other applications. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1002, and the processor 1001 calls and executes a network fault perception processing method of the embodiment of the present application;

[0124] Input / output interface 1003, used to implement information input and output;

[0125] The communication interface 1004 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0126] A bus 1005 , which transmits information between various components of the device (e.g., the processor 1001 , the memory 1002 , the input / output interface 1003 , and the communication interface 1004 );

[0127] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via the bus 1005 .

[0128] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned network fault perception and processing method is implemented.

[0129] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiments, the functions specifically implemented by the present storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0130] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0131] The embodiments of the present application provide a network fault perception processing method, device, electronic device and storage medium. The scheme obtains alarm information, converts the alarm information into a scripting language to perform network fault perception processing to obtain fault information, and can autonomously perceive network faults in a scripting language, thereby improving the flexibility of the system. In addition, the scheme performs fault diagnosis and analysis processing on the fault information based on the heterogeneous interface orchestration method to obtain the cause of the fault, and can configure and orchestrate the diagnosis process to improve the diagnosis efficiency of network faults. In addition, the scheme generates corresponding disposal decisions based on the cause of the fault, and performs parameter verification and instruction rollback detection processing on the disposal decisions, executes the instructions that pass the detection, and can verify and roll back the configuration decisions, thereby improving the efficiency of network fault perception processing.

[0132] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0133] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0134] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0135] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0136] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0137] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0138] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0139] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

[0140] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0141] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0142] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A network fault perception and processing method, characterized in that: The method comprises the following steps: Get alarm information; Convert the alarm information into a scripting language to perform network fault perception processing to obtain fault information; Performing fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault; A corresponding handling decision is generated according to the fault cause, and parameter verification and instruction rollback detection processing are performed on the handling decision, and the instructions that pass the detection are executed.

2. The method according to claim 1, characterized in that The step of converting the alarm information into a script language for network fault perception processing to obtain fault information comprises the following steps: Performing configuration parsing processing on the alarm information through scripting language code to obtain a parsing script; Performing scenario arrangement processing on the parsing script to obtain a fault scenario; The fault scenario is input into a model generator to perform fault type analysis and processing, and the fault information is obtained as an output.

3. The method according to claim 2, characterized in that The step of performing scenario arrangement processing on the parsing script to obtain a fault scenario includes the following steps: Performing application capability analysis and serial arrangement processing on the parsed script to obtain virtual instructions; The virtual instructions are uniformly arranged and processed according to functional applications to obtain the fault scenario.

4. The method according to claim 1, characterized in that The method of performing fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault includes the following steps: Perform configuration search processing on the fault information according to the manufacturer's instruction model to obtain configuration information; Encapsulating the configuration information to obtain a heterogeneous interface; Performing parameter arrangement processing on the heterogeneous interface to obtain a parameter arrangement interface; The parameter arrangement interface is subjected to rule arrangement and process arrangement processing to obtain the cause of the fault.

5. The method according to claim 4, characterized in that The performing parameter arrangement processing on the heterogeneous interface to obtain the parameter arrangement interface comprises the following steps: Obtaining the communication network structure; Performing topological division processing on the communication network networking structure to obtain a network topological structure; Parameter definition processing is performed on the heterogeneous interface according to the network topology structure to obtain the parameter arrangement interface.

6. The method according to any one of claims 1 to 5, characterized in that: The parameter verification and instruction rollback detection processing of the handling decision includes the following steps: determining configuration parameters and configuration instructions according to the handling decision; Perform parameter comparison processing on the configuration parameters according to the network link to obtain a verification result; The configuration instruction is issued according to the verification result, and an abnormality detection is performed on the issued instruction. When an abnormality is detected, the issued instruction is rolled back.

7. The method according to claim 6, characterized in that The step of performing abnormality detection on the issued instruction and rolling back the issued instruction when an abnormality is detected comprises the following steps: Performing label setting processing on the issued instruction to obtain a fallback label; The issued instruction is run according to a preset trial operation time, and the issued instruction is tested according to a network operation state and a network performance index to obtain a test result; When the detection result is that the sending is abnormal, the sending instruction is rolled back according to the rollback tag.

8. A network fault perception and processing device, characterized in that: The device comprises: A first module is configured to obtain alarm information; The second module is configured to convert the alarm information into a script language to perform network fault perception processing to obtain fault information; The third module is configured to perform fault diagnosis and analysis on the fault information based on the heterogeneous interface arrangement method to obtain the cause of the fault; The fourth module is configured to generate a corresponding handling decision according to the cause of the fault, perform parameter verification and instruction rollback detection processing on the handling decision, and execute the instructions that pass the detection.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images