Automatic network inspection method

Abstract

The invention discloses an automatic network inspection method, which comprises the following steps of: step 1, performing inspection preprocessing on an existing inspection command, if the inspection is passed, executing step 2, and if the inspection is not passed, returning to continue inspection; 2, generating an inspection script according to the inspection command passing the inspection, or manually writing the inspection script by an engineer; 3, analyzing the inspection script, and triggering an inspection task; and step 4, when one inspection period is completed, generating a visual report according to the inspection result. The invention relates to the technical field of network automatic inspection, and can solve the technical problems existing in network automatic inspection in the prior art.

Description

Technical Field

[0001] The present invention relates to the technical field of automatic network inspection, and in particular to a method for automatic network inspection. Background Art

[0002] For daily inspections of various equipment operations, the current conventional operation method is manual intervention inspection, which is not only time-consuming and labor-intensive, but also prone to errors; therefore, the use of network automatic inspection to replace manual inspection has emerged. Network automatic inspection focuses on improving labor efficiency and standardizing fragmented inspection plans. Usually, tasks that originally required human intervention are performed by programs or scripts. The existing network automatic inspection technology has the following shortcomings:

[0003] 1. Cost issue: Compared with traditional manual inspection methods, network automated inspection has higher costs in terms of initial investment, equipment purchase, software installation, and personnel training.

[0004] 2. Dependence on professional operations: Existing network automation inspection technologies still require professional technicians to operate and maintain them, which limits their popularity in automation applications.

[0005] 3. System integration and compatibility: When implementing network automation inspection, it is necessary to consider integration with the existing system environment. Due to the different system environments used by the equipment, there are problems with scalability and poor compatibility.

[0006] 4. The need for continuous optimization: Existing network automation inspection technologies need to be regularly optimized and adjusted to adapt to the ever-changing environment and needs.

[0007] Therefore, it is necessary to provide a network automated inspection method that can solve the above-mentioned technical problems existing in the network automated inspection of the prior art. Summary of the invention

[0008] The purpose of the present invention is to provide a network automated inspection method, which can solve the above technical problems existing in the network automated inspection of the prior art.

[0009] The present invention is achieved in that:

[0010] A network automated inspection method comprises the following steps:

[0011] Step 1: Check and preprocess the existing inspection command. If the inspection passes, execute step 2. If the inspection fails, return to continue the inspection.

[0012] Step 2: Generate an inspection script from the inspection commands that pass the inspection, or the inspection script is manually written by the engineer;

[0013] Step 3: Parse the inspection script and trigger the inspection task;

[0014] Step 4: When an inspection cycle is completed, generate a visual report of the inspection results.

[0015] In the step 1, the existing inspection commands include historical commands, task strings manually written according to the inspection task execution sequence, predefined inspection statements or commands composed of modules.

[0016] In the step 1, the inspection command check includes compliance check, security check and driver check; wherein, the security check includes: audit, vulnerability scanning, intrusion detection; the driver check refers to querying the hardware manufacturer API of the inspected device through crawler polling to ensure that the inspection command is also the latest after the driver is updated and there are no faults or incompatibility issues.

[0017] In step 2, the inspection script includes the following key elements: an inspection object and a series of detection points; wherein the inspection object includes the operating system version, installed applications, system configuration and security policies of the inspected device; each detection point corresponds to a specific inspection standard or operation corresponding to the inspected device.

[0018] The step 2 comprises the following sub-steps:

[0019] Step 2.1: Provide a graphical interface for displaying predefined inspection statements or modules and script component areas;

[0020] Step 2.2: The operator drags the predefined inspection statements or modules to the script component area by dragging and dropping to form an instruction set for the inspection task;

[0021] Step 2.3: Automatically splice and arrange the instruction set to generate an executable inspection script, simplifying the inspection script writing process;

[0022] Step 2.4: Test the generated inspection script and verify the response and processing capabilities of the inspection script by simulating various normal and abnormal system states of the inspected equipment;

[0023] Step 2.5: Enter the correct inspection script into the script library to complete the archiving of the inspection script.

[0024] In the step 2.3, during the inspection script generation process, the inspection script can be arranged and modified according to actual business needs and operating system characteristics. The arrangement and modification content includes adjusting the inspection cycle, adding or deleting specific detection items, setting threshold alarms, and defining exception handling processes, or the inspection cycle is manually designed.

[0025] The step 3 comprises the following sub-steps:

[0026] Step 3.1: Parse the inspection script through the parser. The parsing content includes: checking whether the grammatical structure in the inspection script conforms to the specification of the language, identifying the language elements of keywords, variables, function calls, and control flow statements in the inspection script, and ensuring that these language elements appear in the inspection script in the correct order and format;

[0027] Step 3.2: Perform logical analysis on the inspection script through the parser;

[0028] Step 3.3: Parse the inspection script into a specific code fragment corresponding to the operating system suitable for the required application through a parser;

[0029] Step 3.4: Optimize the inspection script code through the parser;

[0030] Step 3.5: Perform static code analysis on the inspection script through the parser;

[0031] Step 3.6: Trigger the inspection script and perform the inspection task on the inspected device according to the inspection script, that is, inspect and test the inspected device and its system.

[0032] In the step 4, a visual report template is provided. The visual report template is composed of different report modules or is manually arranged by an operator.

[0033] The visual report includes problems and anomalies found during the inspection process, as well as a detailed report on the system status of the inspected equipment, the changing trend of performance indicators, and an assessment of the safety status. After the visual report is generated, it is archived in the report library.

[0034] Compared with the prior art, the present invention has the following beneficial effects:

[0035] 1. The present invention adopts a modular inspection script, which can form an inspection script by splicing and arranging script components in a drag-and-drop manner, and can meet personalized customization requirements. Users can adjust inspection tasks according to inspection requirements, thereby supporting a variety of inspection strategies and processes, and having low professional requirements for operators. At the same time, the inspection script is parsed by a parser according to the system environment of the inspected equipment, and the same batch of inspection tasks can be executed on different types of equipment, different operating systems, and different network environments, and corresponding inspection results can be obtained. It has good scalability and compatibility to adapt to different inspection requirements and application scenarios, has a low initial investment cost, and can meet cross-domain, cross-language, and cross-system application requirements, reduce equipment purchase and operation costs, have a high degree of automation, and reduce the degree of manual intervention and error rate.

[0036] 2. Since the present invention generates a visual report after a periodic inspection is completed, the visual report can be arranged using standardized templates, and can intuitively display problems found in the inspection, related suggestions, etc., thereby reducing operational difficulty and reducing dependence on professional maintenance personnel. Conventional professional operations can be solidified into periodically executed tasks, which can reduce repetitive work of personnel; through analysis of the inspection results in the visual report, possible performance bottlenecks and logical defects in the inspection script can be discovered, so that corresponding adjustments and improvements can be made to it, thereby achieving continuous optimization of the inspection script. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a flow chart of the network automatic inspection method of the present invention. DETAILED DESCRIPTION

[0038] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments.

[0039] Please see attached Figure 1 , a network automated inspection method, comprising the following steps:

[0040] Step 1: Perform pre-processing on the existing inspection command. If the inspection passes, execute step 2. If the inspection fails, return to continue the inspection.

[0041] In the step 1, the existing inspection commands include historical commands, task strings manually written according to a certain inspection task execution sequence, predefined inspection statements or commands composed of modules, etc.

[0042] In the step 1, the inspection command inspection includes compliance inspection, security inspection and driver inspection; wherein, the security inspection includes: audit, vulnerability scanning, intrusion detection, etc.; the driver inspection refers to querying the hardware manufacturer API (Application Programming Interface) of the inspected device through crawler polling to ensure that the inspection command is also the latest after the driver is updated and there are no faults or incompatibility issues.

[0043] By checking the inspection command, it is ensured that the inspection script generated subsequently is logical and that inspections can be performed under safe and reliable inspection commands.

[0044] Step 2: Generate an inspection script from the inspection commands that pass the inspection. The inspection script can also be manually written by experienced engineers.

[0045] Preferably, most inspection scripts are written in Python or Bash programs. Inspection scripts written in Python programs can run on most Windows systems, Linux systems, UNIX systems and MacOS systems. Inspection scripts written in Bash programs can run on most Linux systems and MacOS systems. Complex logic and API calls can be integrated to achieve cross-platform system inspection.

[0046] In step 2, the inspection script includes the following key elements: an inspection object and a series of detection points; wherein the inspection object includes the operating system version, installed applications, system configuration, and security policies of the inspected device; each detection point corresponds to a specific inspection standard or operation corresponding to the inspected device.

[0047] For example, the inspection script may include checking the integrity of the operating system files of the inspected device, checking the running status of key services, scanning for operating system vulnerabilities, and verifying security configuration parameters.

[0048] The step 2 comprises the following sub-steps:

[0049] Step 2.1: Provide a graphical interface for displaying predefined inspection statements or modules and a script component area.

[0050] For junior operators, the intuitive display of predefined inspection statements or modules through a graphical interface can reduce the complexity of the inspection script design process and reduce the requirements for the professionalism of operators.

[0051] Step 2.2: The operator drags the predefined inspection statements or modules to the script component area by dragging and dropping to form an instruction set for the inspection task.

[0052] Step 2.3: Automatically splice and arrange the instruction set to generate an executable inspection script, simplifying the inspection script writing process.

[0053] In step 2.3, during the generation of the inspection script, the inspection script can be arranged and modified according to the actual business needs and the characteristics of the operating system. The arrangement and modification content includes adjusting the inspection cycle, adding or deleting specific detection items, setting threshold alarms, and defining exception handling processes. In order to adapt to business fluctuations in different cycles, operators can also manually design flexible inspection cycles to ensure that appropriate monitoring intensity can be maintained during the peak and trough periods of the business of the inspected equipment.

[0054] Step 2.4: Test the generated inspection script. Specifically, during the inspection script testing process, the response and processing capabilities of the inspection script are verified by simulating various normal and abnormal system states of the inspected devices.

[0055] The inspection scripts are divided according to their functions, such as network detection module, system performance detection module, security compliance detection module, etc.

[0056] As a preferred embodiment, each module of the inspection script encapsulates specific detection logic and interacts with other modules through a unified interface; modular and object-oriented design principles are adopted to improve the reusability and maintainability of the inspection script. Standardized interfaces and open architecture design are used to ensure that the inspection script can be seamlessly integrated with the equipment system environment of the existing technology.

[0057] Preferably, the inspection script can be tested by unit testing and integration testing to ensure the stability and accuracy of each module in the inspection script and the entire inspection script.

[0058] Step 2.5: Enter the correct inspection script into the script library to complete the archiving of the inspection script.

[0059] By archiving inspection scripts, it is easier to maintain the inspection script history, track changes, and perform version control. At the same time, archiving and storage of inspection scripts can also help the operation and maintenance team quickly trace back and reproduce problems when needed, thereby improving the efficiency of problem solving.

[0060] Step 3: Parse the inspection script and trigger the inspection task.

[0061] The step 3 comprises the following sub-steps:

[0062] Step 3.1: Parse the inspection script through the parser. The parsing content includes: checking whether the grammatical structure in the inspection script conforms to the specification of the language, identifying the language elements such as keywords, variables, function calls, control flow statements, etc. in the inspection script, and ensuring that these language elements appear in the inspection script in the correct order and format.

[0063] If a syntax error is found during the parsing of the inspection script, such as missing semicolons, mismatched brackets, or misspelled keywords, the parser will point out the error by providing an error report so that the developer can correct the inspection script.

[0064] Since the inspection script is executed by the machine, and the inspection script is still a high-level language, it needs to be parsed into a lower-level machine language so that the specific execution machine can recognize the inspection script. The specific parsing requirements can be adaptively adjusted according to the execution requirements of the specific machine.

[0065] Step 3.2: Perform logical analysis on the inspection script through the parser.

[0066] The parser will check the logical flow in the inspection script to ensure the correctness of the logical structure such as conditional judgment, loop control, function call, etc. The purpose of logical analysis is to find potential logical loopholes, such as infinite loops, conditions that are always true or false, incorrect variable assignments, etc. Through logical analysis, it can be ensured that the subsequent trigger execution process of the inspection script can follow the expected logical path to avoid unexpected execution results.

[0067] Step 3.3: The inspection script is parsed into a specific code fragment corresponding to the operating system suitable for the required application by a parser.

[0068] Since the inspection script is a generalized program language script, the network element objects in the network environment may run on different operating systems. The generalized inspection script also needs to consider cross-platform compatibility issues. Therefore, the inspection script needs to be parsed specifically according to the different operating systems required for application to ensure that the inspection script can be correctly executed in different environments. For example: for Windows systems, the inspection script can be parsed into a PowerShell script; and for Linux systems, the inspection script can be parsed into a Bash script.

[0069] Step 3.4: Optimize the inspection script code through the parser.

[0070] The parser analyzes the code structure in the inspection script and identifies the parts that can be optimized, such as repeated code blocks, unnecessary loops, redundant variables, etc. By optimizing these optimizable codes, the execution efficiency of the inspection script can be improved, resource consumption can be reduced, and system performance can be improved.

[0071] Step 3.5: Use a parser to analyze the static code of the inspection script (that is, the code in the inspection script when the inspection script is not executed) to improve the reliability of the inspection script.

[0072] Without executing the inspection script, the parser performs static code analysis on the inspection script to analyze possible security vulnerabilities and code quality issues in the static code. It can identify potential security risks such as SQL injection, cross-site scripting attacks, unsafe API calls, as well as inconsistent code style, excessive complexity, poor readability, etc., thereby facilitating code optimization of the inspection script.

[0073] The parser can adopt the script parser of the existing technology, which has the functions of syntax checking, language element recognition, logic analysis, specific code fragment parsing, code optimization, static code analysis, etc. to meet the parsing requirements of the inspection script. The parsing process and working principle will not be described here.

[0074] Inspection scripts can be spliced ​​and arranged by dragging and dropping to meet the execution of different inspection tasks. At the same time, through the analysis and optimization of inspection scripts, automatic updating of inspection scripts can be achieved to ensure that the inspection scripts can be effectively executed on the inspected devices and obtain corresponding results. Inspection scripts have good reusability for different inspection devices and can meet various complex equipment scenarios.

[0075] Step 3.6: Trigger the inspection script and perform the inspection task on the inspected device according to the inspection script, that is, inspect and test the inspected device and its system.

[0076] Preferably, the inspection script may be triggered manually by an operator, or may be automatically triggered according to a set inspection cycle.

[0077] Preferably, a multi-mode communication system can be combined, for example, a communication system using cellular network, Wi-Fi, radio and other technologies, to enhance communication capabilities to ensure that the data of the inspection script can be uploaded and issued to different inspection devices in the first place. At the same time, an offline working mode can also be combined to ensure that inspection tasks in areas without network coverage can also be performed normally.

[0078] Step 4: When an inspection cycle is completed, generate a visual report of the inspection results.

[0079] In the step 4, a visual report template is provided. The visual report template can be composed of different report modules or can be manually arranged by an operator.

[0080] In an inspection cycle, it is also critical to prepare a visual report template for the inspection results. The early inspection scripts can be spliced ​​freely, and the visual report template can also be spliced ​​in a similar way (that is, using drag and drop to form a report component set in the report area, and splicing and arranging the report components to generate a visual report template), so that the inspection results can be displayed in a customizable manner.

[0081] Preferably, the visual report template may include trend charts of key indicators, lists of abnormal events, an overview of system health, etc. After the inspection task is completed, the visual report generated in combination with the visual report template can intuitively display the inspection results, problems found, corresponding suggestions and other template contents, which can not only provide a basis for in-depth analysis for technical personnel, but also enable management to quickly grasp the operating status of the inspected equipment, and decision makers with non-technical backgrounds can also quickly and accurately understand the conclusions and suggestions of the inspection.

[0082] The visual report may include problems and anomalies found during the inspection process, and may also include a detailed report on the system status of the inspected equipment, changing trends in performance indicators, assessments of safety conditions, etc. After the visual report is generated, it is archived in the report library to provide data support for the long-term health and stability of the system of the inspected equipment.

[0083] After generating a visualization report, by analyzing the inspection results in the visualization report, you can find possible performance bottlenecks and logical defects in the inspection script, so that you can make corresponding adjustments and improvements to it and achieve continuous optimization of the inspection script.

[0084] Please see attached Figure 1 The inspection, generation and execution of inspection scripts and the generation of visual reports can all be completed automatically by the machine and archived in the script library and report library, which can greatly reduce the degree of human intervention, improve the automation of network automated inspections, and reduce dependence on personnel and their expertise. At the same time, the inspection, generation and triggering of inspection scripts and the arrangement of visual reports can also be performed manually to meet different usage requirements.

[0085] As a better extended implementation example, the inspection script can continuously update the detection rules and processing strategies according to new security threats and system changes to adapt to the ever-changing network environment, and a remote update mechanism can be designed to facilitate the continuous iteration of system software and algorithms.

[0086] As a more optimal extended embodiment, an automatic inspection large screen can be configured to display relevant information of the automatic inspection. The display area of ​​the automatic inspection large screen can be modularly divided and combined to meet the information display needs of different contents.

[0087] The above are only preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Therefore, any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A network automated inspection method, characterized in that: The following steps are involved: Step 1: Check and preprocess the existing inspection command. If the inspection passes, execute step 2. If the inspection fails, return to continue the inspection. Step 2: Generate an inspection script from the inspection commands that pass the inspection, or the inspection script is manually written by the engineer; Step 3: Parse the inspection script and trigger the inspection task; Step 4: When an inspection cycle is completed, generate a visual report of the inspection results.

2. The network automated inspection method according to claim 1, characterized in that: In the step 1, the existing inspection commands include historical commands, task strings manually written according to the inspection task execution sequence, predefined inspection statements or commands composed of modules.

3. The network automated inspection method according to claim 1, characterized in that: In the step 1, the inspection command check includes compliance check, security check and driver check; wherein, the security check includes: audit, vulnerability scanning, intrusion detection; the driver check refers to querying the hardware manufacturer API of the inspected device through crawler polling to ensure that the inspection command is also the latest after the driver is updated and there are no faults or incompatibility issues.

4. The network automated inspection method according to claim 1, characterized in that: In step 2, the inspection script includes the following key elements: an inspection object and a series of detection points; wherein the inspection object includes the operating system version, installed applications, system configuration and security policies of the inspected device; each detection point corresponds to a specific inspection standard or operation corresponding to the inspected device.

5. The network automated inspection method according to claim 1, characterized in that: The step 2 comprises the following sub-steps: Step 2.1: Provide a graphical interface for displaying predefined inspection statements or modules and script component areas; Step 2.2: The operator drags the predefined inspection statements or modules to the script component area by dragging and dropping to form an instruction set for the inspection task; Step 2.3: Automatically splice and arrange the instruction set to generate an executable inspection script, simplifying the inspection script writing process; Step 2.4: Test the generated inspection script and verify the response and processing capabilities of the inspection script by simulating various normal and abnormal system states of the inspected equipment; Step 2.5: Enter the correct inspection script into the script library to complete the archiving of the inspection script.

6. The network automated inspection method according to claim 5, characterized in that: In the step 2.3, during the inspection script generation process, the inspection script can be arranged and modified according to actual business needs and operating system characteristics. The arrangement and modification content includes adjusting the inspection cycle, adding or deleting specific detection items, setting threshold alarms, and defining exception handling processes, or the inspection cycle is manually designed.

7. The network automated inspection method according to claim 1, characterized in that: The step 3 comprises the following sub-steps: Step 3.1: Parse the inspection script through the parser. The parsing content includes: checking whether the grammatical structure in the inspection script conforms to the specification of the language, identifying the language elements of keywords, variables, function calls, and control flow statements in the inspection script, and ensuring that these language elements appear in the inspection script in the correct order and format; Step 3.2: Perform logical analysis on the inspection script through the parser; Step 3.3: Parse the inspection script into a specific code fragment corresponding to the operating system suitable for the required application through a parser; Step 3.4: Optimize the inspection script code through the parser; Step 3.5: Perform static code analysis on the inspection script through the parser; Step 3.6: Trigger the inspection script and perform the inspection task on the inspected device according to the inspection script, that is, inspect and test the inspected device and its system.

8. The network automated inspection method according to claim 1, characterized in that: In the step 4, a visual report template is provided. The visual report template is composed of different report modules or is manually arranged by an operator.

9. The network automated inspection method according to claim 1 or 8, characterized in that: The visual report includes problems and anomalies found during the inspection process, as well as a detailed report on the system status of the inspected equipment, the changing trend of performance indicators, and an assessment of the safety status. After the visual report is generated, it is archived in the report library.

Images