Method and system for device automation joint debugging test

Abstract

The application discloses a kind of equipment automatic joint debugging test method and system.The method is carried out whole system, whole process management to the automatic joint debugging test of equipment using the architecture mode of server \ agent end.Server defines equipment joint test project, joint test plan, joint test process, executes joint debugging test, collects joint test data, monitors and controls joint test process on the visual graphical interface, and diagnoses joint test failure;Agent end uses the design mode of master-slave agent, executes joint test instruction, generates joint test process data and reports to server;SNMP protocol is used to transfer joint test instruction, instruction execution state and joint test process data between server and agent end.The method and system in the application can change the working mode of joint debugging test, liberate people from heavy joint debugging test work, greatly improve the efficiency and correctness of joint test work.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of test training, in particular to an automatic joint debugging test method and system for airborne measurement and control test training task equipment. BACKGROUND

[0002] The joint debugging test of airborne measurement and control test training task equipment is mainly used for daily inspection and maintenance of system technical state, test task preparation, and is an important technical means for checking the correctness of system functions and the reliability of information transmission between systems. Before each test training task is carried out, the participating equipment will undergo multiple joint debugging tests to ensure the smooth development of the test training task. The traditional joint debugging test of participating equipment is carried out in a manual scheduling manner, in which the test training task commander issues joint test projects through orders, and personnel at each post operate the system equipment and software to complete the corresponding joint test projects according to the orders. The commander collects the joint debugging test situation and makes correctness judgment on the joint test project inspection. However, with the rapid development of information technology, the participating equipment is becoming more and more complex, and the joint test project operation is becoming more and more tedious. The traditional manual scheduling method for equipment joint debugging test cannot meet the needs of application and technological development, and automatic joint debugging test has become inevitable to replace manual scheduling joint debugging test. SUMMARY

[0003] In view of the current development status of airborne measurement and control test training task participating equipment and the future development trend of automation and intelligentization, the present application provides an equipment automatic joint debugging test method and system, which detects the correctness, reliability, effectiveness and coordination of the airborne measurement and control system, realizes automatic joint debugging test management of the whole system and whole process of the participating equipment, and greatly improves the automatic level and work efficiency of the participating equipment joint debugging test.

[0004] The method in the present application comprises:

[0005] Step one defines the joint test project. According to the common joint debugging test content involved in the airborne measurement and control test training task, the joint test project is refined and the joint test project content is defined.

[0006] Step two compiles the joint test plan. The participating personnel formulates the joint test plan according to the joint test overall file, selects the participating joint test projects, and automatically generates the joint test flow.

[0007] Step three is the preparation before joint test. According to the formulated joint test plan, the preparation work before joint test is carried out. The joint test data is prepared, the joint test script and joint test parameters are distributed, the required parameters of each participating equipment are loaded, and the overall detection is started.

[0008] Step four: monitoring and controlling of the joint test process. Starting the joint test, automatically executing the joint test items according to the joint test flow, monitoring the joint test process on the visualized graphic interface, when the joint test appears a fault, carrying out fault diagnosis analysis and processing.

[0009] Step five: generating the joint test report. When all the joint test items in the joint test flow are executed, the whole joint test process is ended. After the joint test process is ended, the system can automatically generate the joint test report, summarizing the joint test plan execution process, giving the overall and each participating system evaluation.

[0010] In the step one, the specific process of defining the joint test item is as follows: (1) defining the participating system. Defining the system participating in the joint test item, the participating system content includes: system name, system code, system address. (2) defining the joint test item. The joint test item content includes: item name, item description, instruction code, duration, participating system. The joint test item mainly serves the joint test plan, one joint test item can be used by multiple joint test plans, one joint test plan can contain multiple joint test items. Each joint test item is equivalent to a joint test stage, each joint test item shows three steps in the joint test execution process: instruction issuing, instruction executing and result feedback. (3) setting the joint test script. The script editor edits the automatically executable action script according to the content of each participating system in the joint test item, each script file is named in the form of "joint test item instruction code-participating system code-CODE". Each joint test item contains a separate joint test script for each participating system. (4) setting the joint test parameter: the parameter editor edits the system joint test parameter according to the content of each participating system in the joint test item. Each parameter file is named in the form of "joint test item instruction code-participating system code-PARAM".

[0011] In the step two, the specific process of compiling the joint test plan is as follows: (1) compiling the joint test plan. According to the joint test overall file, formulating the joint test plan, the joint test plan content includes: plan name, joint test code, responsible person, start time, task code, joint test description, selecting the participating joint test item. (2) generating the joint test flow. According to the joint test item sequence selected in the joint test plan, automatically generating the visualized joint test flow, adjusting the joint test item sequence, which can change the joint test flow. The joint test process is the flow engine driving the automatic execution of the whole joint test flow.

[0012] The third step of the preparation process of the joint test is specifically as follows: (1) preparing joint test data, preparing joint test data required for joint test projects involved in this joint test according to joint test projects selected in the joint test plan; (2) distributing joint test scripts, distributing scripts for executing joint test projects to systems participating in the joint test projects, and loading the joint test scripts to corresponding devices for preparing execution; (3) distributing joint test parameters, distributing joint test parameters associated with joint test projects in the joint test plan to devices, and loading parameter files to the devices for preparing execution of the joint test projects; and (4) starting overall detection, distributing joint test detection instructions to all systems and devices in the joint test plan, collecting joint test detection results of all systems and devices in the joint test plan, and starting execution of the joint test plan after all systems and devices pass the detection, or re-performing joint test detection after excluding faults until all systems and devices pass the detection.

[0013] The fourth step of the joint test process monitoring and control is specifically as follows: starting the joint test plan and loading joint test projects for execution. Each joint test plan can include multiple joint test projects, and three steps are displayed for each joint test project, namely, instruction issuing, instruction execution, and result feedback. Each joint test project mainly performs the following: (1) issuing joint test instructions to participating devices; (2) executing joint test instructions by participating devices; (3) collecting states and feeding back results: during instruction execution, participating devices report instruction execution states and process data, and execution of the joint test project is displayed on a visual joint test execution state diagram; (4) determining whether the joint test project ends, stopping operation of participating devices of the joint test project when an end condition is met, and performing (5); when the end condition is not met, continuously collecting operation states and related data of the participating devices, and jumping to (3) for execution; (5) joint test fault judgment: when the joint test project ends, automatically analyzing and diagnosing faults, automatically generating test results of the joint test project, and determining whether a fault occurs in execution of the joint test project. If a fault occurs, (6) is performed; if no fault occurs, (8) is performed. (6) joint test fault processing: listing fault data and fault diagnosis results or even fault handling suggestions, and waiting for a joint test commander to handle the fault. (7) the joint test commander can directly handle the fault on the state diagram, and makes a decision. If the joint test project is re-executed, (1) is performed; if the joint test project ends, (8) is performed. (8) joint test project end processing: after execution of the joint test project ends, determining whether there is a next joint test project, and performing (1) if there is a next joint test project; or ending the joint test process if there is no next joint test project.

[0014] In the step five, the report of the joint test is generated, and the joint test process is ended. After the joint test process is ended, the system can automatically generate the report of the joint test. The commonly used joint test report template can be edited in advance, and the joint test report template is selected when the joint test report is generated. The joint test report in the format of the template is automatically generated. The joint test report summarizes the joint test plan execution process and gives the overall and each participating system evaluation.

[0015] The system of the application comprises: a framework mode of a server-side automatic joint test A and an agent-side automatic joint test B. The server-side automatic joint test A is responsible for formulating a joint test plan, starting joint test execution, issuing joint test instructions to the agent side, monitoring the joint test process, receiving the joint test instruction execution state and process data reported by the agent side, comprehensively processing, analyzing and displaying the execution state and process data, processing faults occurring in the joint test process, realizing automatic joint test management of participating devices, and managing all systems included in the joint test plan. The agent-side automatic joint test B is responsible for joint test instruction execution of each participating device / system, and the scope is each system, subsystem or component in the device. Meanwhile, the agent-side automatic joint test B provides the execution state and process data of the joint test instructions and other information for the server-side automatic joint test. The server side and the agent side use the SNMP protocol to transfer the joint test instructions, instruction execution states and joint test process data.

[0016] The server-side automatic joint test A comprises: an automatic joint test software a1, a protocol processing software a2 and a joint test database a3. The automatic joint test software a1 realizes joint test project management, joint test plan compilation, joint test execution starting, monitoring and control of the joint test execution process on a visual graphical interface, joint test fault processing, joint test report generation after the joint test is ended, etc. The protocol processing software a2 is a bridge connecting the server side and the agent side, and realizes joint test instruction issuing, joint test instruction execution state and process data collecting. The joint test database a3 stores joint test project, joint test plan, joint test execution process data, abnormality processing and other information, and is used to support joint test process display and playback.

[0017] The server-side automatic joint debugging test software a1 comprises: joint test project management a11, joint test plan compilation a12, command dispatching and monitoring a13, joint test report management a14, joint test process playback a15, and system management a16. The joint test project management a11 realizes the functions of adding, deleting, modifying, and querying joint test projects, and each joint test project corresponds to a joint test stage. The joint test plan compilation a12 provides the function of formulating a joint test plan, selects a joint test project, generates a joint test flow, prepares joint test data, configures a joint test project and related parameters and data according to the joint test plan. The command dispatching and monitoring a13 automatically dispatches the joint test operation of the entire task system according to a pre-set joint test flow and implements monitoring, completes the automatic configuration, operation control, information collection, fault diagnosis and analysis of the joint test flow, records process data, and displays the details of the joint test process in an image intuitive graphical manner. The joint test report management a14 has the function of automatically generating a joint test report. After the joint test is completed, the system can automatically generate a joint test report according to the working condition of the test equipment and give an evaluation of the joint test condition. The joint test process playback a15 plays back the entire automatic joint debugging test process, and during the playback process, operations such as pausing, continuing, and adjusting the speed can be performed. The system management a16 collects typical fault modes and optimal solutions in the previous automatic joint debugging test process, forms a fault knowledge base, records system operation logs, and facilitates audit inspection.

[0018] The server-side protocol processing software a2 comprises: data receiving a21, data forwarding a22, and data storage a23. The data receiving a21 realizes the function of receiving data information reported or issued by other software, including receiving joint test instructions issued by the server-side automatic joint debugging test software and receiving joint test instruction execution states and execution process data reported by the agent software (master) of the agent end device. The data forwarding a22 forwards the joint test instructions issued by the server-side automatic joint debugging test software a1 to the agent software (master) b1 of the agent end device. After receiving the joint test instruction execution states and process data reported by the agent software (master) b1 of the agent end device, the data storage a23 stores the data into the joint test database a3 and sends an information arrival notification to the server-side automatic joint debugging test software a2.

[0019] The agent end automatic joint debugging test B comprises: considering that the trial training participant systems and equipment are numerous, all are directly managed by the service end, the service end pressure is larger, and the service end and agent end information transmission is frequent and can cause network blockage, the agent end automatic joint debugging test in the application is realized in a master-slave mode, and the equipment is managed in groups taking the participant system as a unit. Each participant system of the agent end comprises a set of equipment agent software (master) b1, an equipment management information base b2 and equipment under the jurisdiction of the system respectively deploying equipment agent software (slave) b3. The equipment agent software (master) b1 realizes distribution of received joint test instructions to the specified equipment agent software (slave) b3 for execution, receives the joint test instruction execution state and process data reported by the equipment agent software (slave) b3, and reports the joint test instruction execution state and process data to the service end protocol processing software a2 after fusion processing. The equipment agent software (slave) b3 receives the joint test instruction, executes the joint test instruction, generates the joint test instruction execution state and process data and reports the joint test instruction execution state and process data to the equipment agent software (master) b1. The equipment management information base b2 is used for storing the MIB format instruction execution state and process data.

[0020] The equipment agent software (master) b1 of the agent end comprises: data receiving b11, data processing b12, data sending b13 and data storage b14. The data receiving b11 receives the joint test instruction forwarded by the service end protocol processing software a2. The data processing b12 analyzes the received joint test instruction, distributes the instruction to the equipment agent software (slave) b3 for execution, receives the joint test instruction execution state and process data sent by each equipment agent software (slave) b3 in the system, performs fusion processing on the data, generates the joint test instruction system-level execution state and process data, and performs format processing on the processed data to generate the MIB format. The data sending b13 assembles the MIB format instruction execution state and execution process data into the Trap PDU of the SNMP protocol and sends it to the service end protocol processing software a2. The data storage b14 stores the processed instruction execution state and execution process data in the MIB format into the equipment management information base b2.

[0021] The equipment agent software (slave) b3 of the agent end comprises: data receiving b31, joint test execution b32 and data sending b33. The data receiving b31 receives the joint test instruction sent by the equipment agent software (master) b1. The joint test execution b32 analyzes the joint test instruction, loads the instruction execution script, executes the joint test instruction according to the pre-set steps in the script, and generates the instruction execution state and process data. The data sending b33 sends the generated instruction execution state and process data to the equipment agent software (master) b1.

[0022] The application has the advantages and beneficial effects that the application provides a device automatic joint debugging test method and system, the method formulates a joint test plan according to a joint test overall file, defines joint test stages and joint test projects, configures joint test parameters and joint test data, realizes automatic execution, process monitoring, information collection, fault diagnosis and analysis processing of joint debugging test stages, realizes automatic joint debugging test management of a whole system and a whole process of a test device, and greatly improves the automatic level and work efficiency of joint debugging test of the test device. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 A device automatic joint debugging test method flow chart is provided in the application.

[0024] Figure 2 A device automatic joint debugging test method architecture schematic diagram is provided in the application. DETAILED DESCRIPTION

[0025] The specific implementation steps of the application are further described below in combination with the accompanying drawings. Figures 1-2 The specific implementation steps of the application are further described below in combination with the accompanying drawings.

[0026] Step one, defining joint test projects. According to the common joint debugging test content involved in the airborne measurement and control test training task data processing device, the joint test projects are refined and the joint test project content is defined.

[0027] 1.1 Defining test systems. The systems participating in the joint test projects are defined, and the test system content includes: system name, system code, system address.

[0028] 1.1.1 System name: the Chinese name of the test system. The systems related to the airborne measurement and control test training task data processing include: data processing system, command display system and operation management system.

[0029] 1.1.2 System code: defining the unique identification of the test system. The system code is used to represent the test system in the joint test instruction issuing, instruction execution process information reporting data packet. The system codes related to the airborne measurement and control test training task data processing are as follows: the data processing system code is SJCL, the command display system code is ZHXS, and the operation management system code is YGXT.

[0030] 1.1.3 System address: the IP address of the device agent software (master) deployed by the test system. Each system contains multiple subsystems (or software) and devices, and each system deploys a device agent software (master), and the devices within the jurisdiction of the system deploy device agent software (slave), which are coordinated by the device agent software (master) to participate in the joint test work. The system addresses related to the airborne measurement and control test training task data processing are as follows:

[0031] (1) The data processing system includes 3 data processing servers, 1 KVM switch, integrated processing software, security control processing software, duplex management software, and simulation software. The device agent software (master) of the data processing system is deployed on data processing server 1, with an IP address of 192.168.32.50. Device agent software (slave) is deployed on data processing server 2 and data processing server 3 respectively.

[0032] (2) The command and display system consists of two workstations. Each workstation is equipped with two LCDs and command and display software. The device agent software (master) of the command and display system is deployed on workstation 1, with the IP address 192.168.32.60. The device agent software (slave) is deployed on workstation 2.

[0033] (3) The operation and management system includes 2 operation and management servers, 2 operation and management terminals, operation and management agent software, and status monitoring software. The operation and management system device agent software (master) is deployed on operation and management server 1, with IP address 192.168.32.70. Device agent software (slave) is deployed on operation and management server 2, operation and management terminal 1, and operation and management terminal 2 respectively.

[0034] 1.2 Define the joint test project. The content of the joint test project includes: project name, project description, instruction code, duration, and participating system. The joint test project mainly serves the joint test plan. Each joint test project is equivalent to a joint test phase. During the joint test execution process, three steps are displayed for each joint test project: instruction issuance, instruction execution, and result feedback.

[0035] 1.2.1 Project Name: Name the joint test projects based on the extracted functions. The project name is a text message with a length ≤ 50 characters, consisting of Chinese, English, and numeric characters. Joint test projects related to data processing for airborne telemetry and control test training missions include joint test detection, T0 information check, comprehensive information check, and ballistic check.

[0036] 1.2.2 Project Description: Describe the specific content of the joint testing project. The project description can help you understand the functions implemented by the joint testing project.

[0037] (1) Joint test: Test whether all equipment related to data processing for airborne telemetry and control test and training missions can work normally after being powered on.

[0038] (2) T0 information check: Check the consistency of T0 information of all equipment related to data processing of airborne telemetry and control test training mission.

[0039] (3) Comprehensive information check: Check the correctness of all equipment related to data processing for airborne telemetry and control test and training missions and the external data transmission links.

[0040] (4) Ballistic check: Check whether the other related software can normally receive and process the theoretical ballistic information sent by the simulation software.

[0041] 1.2.3 Instruction code: Define the unique identification of the joint test project. The instruction code is composed of text information with English characters ≤ 50 in length. The instruction code will represent the joint test project between the server and the agent. The instruction code of the joint test project related to the airborne TT&C test training task data processing is defined as follows: the instruction code of the joint test LSJC, the instruction code of the T0 information check T0JC, the instruction code of the comprehensive information check ZHJC, and the instruction code of the ballistic check DDJC.

[0042] 1.2.4 Duration: The expected execution time of the joint test project, in seconds. The duration here is the expected value, which is only a rough estimate of the project duration, and may differ from the actual execution time.

[0043] 1.2.5 Test system: Select the system participating in the joint test project. List all the test systems defined in 1.1 for selection. A joint test project can include multiple test systems, and a test system can participate in multiple joint test projects.

[0044] 1.3 Set up the joint test script. The script editor edits the automatically executable action script according to the content executed by each test system in this joint test project.

[0045] 1.3.1 Edit the joint test script: The script editor edits the script on the visual graphical interface according to the content executed by each test system in this joint test project. The script editor can complete the editing work through simple operations such as mouse dragging and data configuration. The system then automatically generates a language script based on these editing data. The contents that are not convenient to configure on the graphical editing interface can be further edited and modified on this language script. After the final editing is completed, the system provides automatic checking of the script to confirm the logical correctness of the script, so as to ensure that the edited script is executable. After the script is edited, it is named in the form of "joint test project instruction code-test system code-CODE". Each joint test project includes a separate joint test script for each test system. The system seat operator usually acts as the script editor, and the system seat operator is very familiar with the operations that need to be performed during the joint test of the system and equipment under his / her responsibility.

[0046] Take the joint test detection project in the airborne TT&C test training task data processing as an example to edit the joint test script.

[0047] (1) Data processing system

[0048] The joint test script of the data processing system is named "LSJC-SJCL-CODE".

[0049] 1) The script executed by the device agent software (master) deployed on the data processing server 1 is converted into the logical description as follows:

[0050] Determine whether the integrated processing software process deployed on the data processing server 1 is working normally.

[0051] Determine whether the security control processing software process deployed on the data processing server 1 is working normally.

[0052] Determine whether the CPU usage of the data processing server 1 <= maxCPU.

[0053] Determine whether the memory usage of the data processing server 1 <= maxMemory.

[0054] Determine whether the hard disk usage of the data processing server 1 <= maxDisk.

[0055] If all the above determinations are normal, the joint test result of the data processing server 1 is normal, otherwise the joint test result of the data processing server 1 is abnormal.

[0056] Listen within maxTime time:

[0057] Receive the joint test result of the data processing server 2 fed back by the device agent software (slave) deployed on the data processing server 2.

[0058] Receive the joint test result of the data processing server 3 fed back by the device agent software (slave) deployed on the data processing server 3.

[0059] If no feedback is received within maxTime, it is considered that the device is abnormal.

[0060] Determine the joint test results of the devices of the data processing servers 1-3, and if all are normal, the joint test result of the data processing system is normal, otherwise the joint test result of the data processing system is abnormal.

[0061] 2) The script executed by the device agent software (slave) deployed on the data processing server 2 is converted into the logical description as follows:

[0062] Determine whether the simulation software process deployed on the data processing server 2 is working normally.

[0063] Determine whether the KVM switch 1 is working normally.

[0064] Determine whether the CPU usage of the data processing server 2 <= maxCPU.

[0065] Determine whether the memory usage of the data processing server 2 <= maxMemory.

[0066] Judge the hard disk usage rate of data processing server 2 <= maxDisk.

[0067] If all the above judgments are normal, the joint test result of data processing server 2 is normal, otherwise the joint test result of data processing server 2 is abnormal.

[0068] Report the joint test result of data processing server 2 to data processing server 1.

[0069] 3) The script executed by the device agent software (master) deployed on data processing server 3 is converted into the following logical description:

[0070] Judge whether the duplex management software process deployed on data processing server 3 is working normally.

[0071] Judge the CPU usage rate of data processing server 3 <= maxCPU.

[0072] Judge the memory usage rate of data processing server 3 <= maxMemory.

[0073] Judge the hard disk usage rate of data processing server 3 <= maxDisk.

[0074] If all the above judgments are normal, the joint test result of data processing server 3 is normal, otherwise the joint test result of data processing server 3 is abnormal.

[0075] Report the joint test result of data processing server 3 to data processing server 1.

[0076] (2) Command display system

[0077] The joint test script of the command display system is named "LSJC-ZHXS-CODE".

[0078] 1) The script executed by the device agent software (master) deployed on workstation 1 is converted into the following logical description:

[0079] Judge whether the command display software process deployed on workstation 1 is working normally.

[0080] Judge whether LCD1 is working normally.

[0081] Judge whether LCD2 is working normally.

[0082] Judge the CPU usage rate of workstation 1 <= maxCPU.

[0083] Judge the memory usage rate of workstation 1 <= maxMemory.

[0084] Judge the hard disk usage rate of workstation 1 <= maxDisk.

[0085] If all the above judgments are normal, the joint test result of workstation 1 is normal, otherwise the joint test result of workstation 1 is abnormal.

[0086] Listen within maxTime time:

[0087] Receive the joint test result of workstation 2 fed back by the device agent software deployed on workstation 2.

[0088] If no feedback is received within maxTime, it is considered that the device is abnormal.

[0089] Judge the joint test result of workstation 1 and workstation 2. If all the above judgments are normal, the joint test result of the command display system is normal, otherwise the joint test result of the command display system is abnormal.

[0090] 2) The script executed by the device agent software deployed on workstation 2 (slave) is converted into a logical description as follows:

[0091] Judge whether the command display software process deployed on workstation 2 is working normally.

[0092] Judge whether LCD3 is working normally.

[0093] Judge whether LCD4 is working normally.

[0094] Judge whether the CPU usage of workstation 2 is <= maxCPU.

[0095] Judge whether the memory usage of workstation 2 is <= maxMemory.

[0096] Judge whether the hard disk usage of workstation 2 is <= maxDisk.

[0097] If all the above judgments are normal, the joint test result of workstation 2 is normal, otherwise the joint test result of workstation 2 is abnormal.

[0098] Report the joint test result of workstation 2 to workstation 1.

[0099] 3) Operation management system

[0100] The joint test script of the operation management system is named "LSJC-YGXT-CODE".

[0101] 1) The script executed by the device agent software deployed on operation management server 1 (master) is converted into a logical description as follows:

[0102] Judge whether the operation management agent software process deployed on operation management server 1 is working normally.

[0103] Judge whether the CPU usage of operation management server 1 is <= maxCPU.

[0104] Judge the memory usage rate of the management server 1 <= maxMemory.

[0105] Judge the hard disk usage rate of the management server 1 <= maxDisk.

[0106] If the above judgments are all normal, the joint test result of the management server 1 is normal, otherwise the joint test result of the management server 1 is abnormal.

[0107] Listen within maxTime time:

[0108] Receive the joint test result of the management server 2 fed back by the device agent software deployed on the management server 2.

[0109] Receive the joint test result of the management terminal 1 fed back by the device agent software deployed on the management terminal 1.

[0110] Receive the joint test result of the management terminal 2 fed back by the device agent software deployed on the management terminal 2.

[0111] If no feedback is received within maxTime, it is considered that the device is abnormal.

[0112] Judge the joint test result of the devices of the management server 1, the management server 2, the management terminal 1 and the management terminal 2, and if all are normal, the joint test result of the management system is normal, otherwise the joint test result of the management system is abnormal.

[0113] 2) The script executed by the device agent software deployed on the management server 2 is converted into a logical description as follows:

[0114] Judge whether the management agent software process deployed on the management server 2 is working normally.

[0115] Judge the CPU usage rate of the management server 2 <= maxCPU.

[0116] Judge the memory usage rate of the management server 2 <= maxMemory.

[0117] Judge the hard disk usage rate of the management server 2 <= maxDisk.

[0118] If the above judgments are all normal, the joint test result of the management server 2 is normal, otherwise the joint test result of the management server 2 is abnormal.

[0119] Report the joint test result of the management server 2 to the management server 1.

[0120] 3) The script executed by the device agent software deployed on the management terminal 1 is converted into a logical description as follows:

[0121] Determine if the state monitoring software process deployed on the management terminal 1 is working properly.

[0122] Determine if the CPU usage of the management terminal 1 <= maxCPU.

[0123] Determine if the memory usage of the management terminal 1 <= maxMemory.

[0124] Determine if the hard disk usage of the management terminal 1 <= maxDisk.

[0125] If all the above determinations are normal, the joint test result of the management terminal 1 is normal, otherwise, the joint test result of the management terminal 1 is abnormal.

[0126] Report the joint test result of the management terminal 1 to the management server 1.

[0127] 4) The script executed by the device agent software deployed on the management terminal 2 is converted into the following logical description:

[0128] Determine if the state monitoring software process deployed on the management terminal 2 is working properly.

[0129] Determine if the CPU usage of the management terminal 2 <= maxCPU.

[0130] Determine if the memory usage of the management terminal 2 <= maxMemory.

[0131] Determine if the hard disk usage of the management terminal 2 <= maxDisk.

[0132] If all the above determinations are normal, the joint test result of the management terminal 2 is normal, otherwise, the joint test result of the management terminal 2 is abnormal.

[0133] Report the joint test result of the management terminal 2 to the management server 1.

[0134] 1.3.2 Upload joint test script: Upload the locally saved joint test script to the server, and record the association between the joint test script and the joint test project and the storage location of the joint test script in the database.

[0135] 1.4 Set joint test parameters: The parameter editor edits the system joint test parameters according to the content executed by each participating system in this joint test project.

[0136] 1.4.1 Edit joint test parameters: Set joint test parameters for each system participating in the joint test project, and save the joint test parameters in the form of key / value to the parameter file. There is one parameter file for each participating system, and the parameter file is named in the form of "joint test project instruction code-participating system code-PARAM".

[0137] Take airborne test control test training task data processing in the joint test detection project as an example to illustrate the parameter file.

[0138] (1) Data processing system

[0139] The parameter file of joint test detection of data processing system is named "LSJC-SJCJ-PARAM.xml"

[0140] maxTime: 50ms / / The maximum time for the device agent software (main) to wait for the device agent software (slave) to return information. If there is no return result beyond the set time, the device detection is considered to fail.

[0141] maxCPU: 75% / / The maximum value of the health status of device CPU usage

[0142] maxMemory: 70% / / The maximum value of the health status of device memory usage

[0143] maxDisk: 70% / / The maximum value of the health status of device hard disk usage

[0144] 2) Command display system

[0145] The parameter file of joint test detection of command display system is named "LSJC-ZHXS-PARAM.xml"

[0146] maxTime: 50ms / / The maximum time for the device agent software (main) to wait for the device agent software (slave) to return information. If there is no return result beyond the set time, the device detection is considered to fail.

[0147] maxCPU: 70% / / The maximum value of the health status of device CPU usage

[0148] maxMemory: 75% / / The maximum value of the health status of device memory usage

[0149] maxDisk: 70% / / The maximum value of the health status of device hard disk usage

[0150] 3) Operation management system

[0151] The parameter file of joint test detection of operation management system is named "LSJC-YGXS-PARAM.xml"

[0152] maxTime: 50ms / / The maximum time for the device agent software (main) to wait for the device agent software (slave) to return information. If there is no return result beyond the set time, the device detection is considered to fail.

[0153] maxCPU: 75% / / The maximum value of the health status of device CPU usage

[0154] maxMemory: 70% / / max value of memory usage health status

[0155] maxDisk: 75% / / max value of disk usage health status

[0156] Step two: compile the joint test plan. According to the joint test overall document, the joint test plan is formulated, the joint test project is selected, and the joint test flow is automatically generated.

[0157] 2.1 Compile the joint test plan. According to the joint test overall document, the joint test plan is formulated, and the joint test plan content includes: plan name, joint test code, responsible person, start time, task code, joint test description, joint test project.

[0158] 2.1.1 Plan name: According to the purpose of this joint test, the joint test plan name is abstracted. The plan name is composed of Chinese, English and numerical characters, and the length is ≤50 text information. For example, define the joint test plan name as: KW launch task data processing related equipment joint debugging test.

[0159] 2.1.2 Joint test code: the unique identification of the joint test plan, the joint test code is composed of English, numbers and Chinese dash characters, and the length is ≤50 text information. For example, define the joint test code of KW launch task data processing related equipment joint debugging test as: KWLS.

[0160] 2.1.3 Responsible person: the name of the responsible person of the joint test plan, select the responsible person from the personnel list.

[0161] 2.1.4 Start time: set the start time of the joint test plan, select from the time control or manually input, the time format is: YYYY-MM-DD HH:MM:SS.

[0162] 2.1.5 Task code: the test and training task code associated with the joint test plan. The automated joint debugging test plan is for the test and training task, before each test and training task starts, multiple joint tests are carried out to ensure that each system and each device runs correctly and stably during the execution of the training task. For example, define the joint debugging test task code of KW launch task data processing related equipment as: KW.

[0163] 2.1.6 Joint test description: detailed function, purpose and other content of the formulated joint test plan. For example, define the joint test description of KW launch task data processing related equipment joint debugging test: before KW launch task, the joint debugging test of KW launch task data processing related equipment is carried out to ensure that the data processing related equipment, system and communication can be used normally before the task starts.

[0164] 2.1.7 Joint test project: select joint test projects involved in joint test plan, the system lists all joint test projects defined in step 1.2 for selection, multiple joint test projects can be selected in a joint test plan, and a joint test project can be selected by multiple joint test plans. For example, the joint test projects selected for the KW launch task data processing related equipment joint test are T0 information check, comprehensive information check, and trajectory check.

[0165] 2.2 Generate joint test flow. According to the joint test projects selected in the joint test plan, automatically generate joint test flow.

[0166] 2.2.1 Generate joint test flow. According to the sequence of joint test projects selected in the joint test plan, automatically generate visual joint test flow. For example, the joint test flow generated for the KW launch task data processing related equipment joint test is T0 information check → comprehensive information check → trajectory check.

[0167] 2.2.2 Adjust joint test flow. Adjust the sequence of joint test projects, which can change the joint test flow, and the joint test flow is visually displayed in the page in the form of a flowchart. The joint test process is driven by the flow engine to automatically run the entire joint test flow according to the sequence of the flowchart.

[0168] Step three: preparation before joint test. According to the joint test plan, prepare for the joint test. Prepare joint test data, distribute joint test scripts and joint test parameters, load parameters required by each participating device, and start overall detection.

[0169] 3.1 Prepare joint test data. According to the joint test projects selected in the joint test plan, prepare the data required for all joint test projects involved in this joint test. For example, theoretical trajectory data needs to be prepared for the simulation software in the trajectory check joint test project.

[0170] 3.2 Distribute joint test scripts. Distribute joint test scripts associated with joint test projects included in the joint test plan to each device.

[0171] 3.2.1 Server distributes joint test scripts. The server-side automatic joint test software sends the address of the joint test script file to each system agent device agent software (master) through the protocol processing software. The device agent software (master) receives the address of the joint test script, downloads the joint test script from the specified address, and prepares for execution. For example, the joint test script file LSJC-SJCL-CODE for the data processing system joint test is distributed to the device agent software (master) deployed on the data processing server 1 of the data processing system, and the joint test script file LSJC-ZHXS-CODE for the command display system is distributed to the device agent software (master) deployed on the workstation 1 of the command display system.

[0172] 3.2.2 Agent end distribution of joint test scripts: The agent software (master) of the agent end device distributes the address of the joint test script file to the agent software (slave) of the device, and the agent software (slave) downloads the joint test script from the specified address to prepare for execution. For example, the agent software (master) deployed on the data processing server 1 of the data processing system in the joint test detection project distributes the joint test script file LSJC-SJCL-CODE to the agent software (slave) deployed on the data processing server 2 and the agent software (slave) deployed on the data processing server 3.

[0173] 3.3 Distribution of joint test parameters. The joint test parameters associated with the joint test items in the joint test plan are distributed to each device.

[0174] 3.3.1 Server distribution of joint test parameters. The server automated joint test software sends the address of the joint test parameter file to each system agent end device agent software (master) through the protocol processing software. The agent software (master) receives the address of the joint test parameter file, downloads the parameter file from the specified address, and loads the required parameters for system operation according to the parameter file. For example, in the joint test detection project, the joint test parameter file LSJC-SJCL-PARAM of the data processing system is distributed to the agent software (master) deployed on the data processing server 1 of the data processing system, and the joint test parameter file LSJC-ZHXS-PARAM of the command display system is distributed to the agent software (master) deployed on the workstation 1 of the command display system.

[0175] 3.3.2 Agent end distribution of joint test parameters: The agent software (master) of the agent end device distributes the address of the joint test parameter file to the agent software (slave) of the device, and the agent software (slave) downloads the joint test parameter file from the specified address to load the required parameters for device operation according to the joint test parameter file. For example, the agent software (master) deployed on the data processing server 1 of the data processing system in the joint test detection project distributes the joint test parameter file LSJC-SJCL-PARAM to the agent software (slave) deployed on the data processing server 2 and the agent software (slave) deployed on the data processing server 3.

[0176] 3.4 Start overall detection. Issue joint test detection instructions to all participating systems and devices, collect all participating system and device detection results, and only after all systems and devices pass the detection can the joint test be executed. If not all can pass, the problem is excluded and the detection is re-performed until all systems and devices pass the detection.

[0177] 3.4.1 Service end issued joint test detection instruction: the service end automatic joint test software sends joint test detection instruction to the protocol processing software, and the protocol processing software sends joint test detection instruction to each system agent device agent software (main) by GetRequest command of SNMP protocol. In the SNMP protocol, information exchange is carried out in the form of SNMP message. Each SNMP message contains protocol version number (Version), community identifier (Community) and protocol data unit (PDU). The variable binding format of the SNMP protocol data unit (PDU) in the method for sending instruction or feedback execution information is defined as shown in the following table.

[0178] Table 1 variable binding of sent or feedback information

[0179] MIB variable encoding Variable name Data type Value 1.6.2.3.2.7.3.2.0 Instruction sending or feedback time int Quantization unit 0.1 ms, Beijing time (24h system) 1.6.2.3.2.7.3.2.1 Branch entry String System branch entry Branch entry.1.0 System identification String Identification of the instruction sending or feedback system Branch entry.1.1 Joint test instruction String Joint test instruction code value Branch entry.1.2 Configuration number int Configuration number carried by the joint test instruction Branch entry.1.2.1 Joint test project duration int Joint test project duration, unit is s Branch entry.1.2.2 Joint test plan ID String ID of the joint test plan being executed Branch entry.1.2.3 Joint test project ID String ID of the joint test project being executed Branch entry.1.3 Execution code int Instruction execution information code Branch entry.1.4 Instruction execution information description String Successively give the execution result; give the failure reason for execution failure

[0180] For example, the variable binding content in the PDU data packet of the service end issued joint test detection instruction to the data processing system is as follows:

[0181] {

[0182] 1.6.2.3.2.7.3.2.0: 32600 / / Instruction sending or feedback time

[0183] 1.6.2.3.2.7.3.2.1: '1.3.6.1.4.1.732.17' / / Branch entrance of data processing system

[0184] 1.3.6.1.4.1.732.17.1.0: 'SJCL' / / Identification of data processing system

[0185] 1.3.6.1.4.1.732.17.1.1: 'LSJC' / / Code of joint test detection instruction

[0186] 1.3.6.1.4.1.732.17.1.2: 2 / / Number of configuration information carried when issuing joint test detection instruction

[0187] 1.3.6.1.4.1.732.17.1.2.1: '2c08c2b2c7c6e79a11cd8ab77ce4e494' / / Joint test plan ID

[0188] 1.3.6.1.4.1.732.17.1.2.2: '9c8c4c1135d0c27a2d8e219862958239' / / Joint test project ID

[0189] 1.3.6.1.4.1.732.17.1.3: / / execute code, this parameter is empty when issuing the joint test instruction, the content can be filled in after the instruction is executed.

[0190] 1.3.6.1.4.1.732.17.1.4: / / execute information description, this parameter is empty when issuing the joint test instruction, the content can be filled in after the instruction is executed.

[0191] }

[0192] 3.4.2 Agent-side joint test instruction: The agent software (master) receives the joint test instruction, parses the joint test instruction, and distributes the joint test instruction to all device agent software (slave) in the system jurisdiction for execution. The device agent software (master) deployed on the data processing server 1 distributes the joint test instruction to the device agent software (slave) deployed on the data processing server 2 and the device agent software (slave) deployed on the data processing server 3.

[0193] 3.4.3 Execute joint test instruction: The device agent software (master) executes the joint test instruction, and the device agent software (slave) receives the joint test instruction, parses the joint test instruction, and executes the joint test according to the execution script of the joint test instruction. The device agent software (master) listens to whether all device agent software (slave) in the jurisdiction have reported the test results, collects all test results, and forms the system-level joint test results.

[0194] Taking the execution of the joint test instruction by the data processing system as an example:

[0195] (1) The script executed by the device agent software (master) deployed on the data processing server 1:

[0196] Determine whether the data processing software process deployed on the data processing server 1 is working normally.

[0197] Determine whether the security control processing software process deployed on the data processing server 1 is working normally.

[0198] Determine whether the CPU usage of the data processing server 1 <= maxCPU

[0199] Determine whether the memory usage of the data processing server 1 <= maxMemory

[0200] Determine whether the hard disk usage of the data processing server 1 <= maxDisk

[0201] If all the above determinations are normal, the joint test result of the data processing server 1 is normal, otherwise the joint test result of the data processing server 1 is abnormal.

[0202] Listen within maxTime time:

[0203] Receive the joint test detection result of data processing server 2 fed back by the device agent software deployed on data processing server 2.

[0204] Receive the joint test detection result of data processing server 3 fed back by the device agent software deployed on data processing server 3.

[0205] If no feedback is received within maxTime, it is considered that the device is abnormal.

[0206] Determine the joint test detection result of the devices of data processing server 1, data processing server 2 and data processing server 3. If all are normal, the joint test detection result of the data processing system is normal, otherwise the joint test detection result of the data processing system is abnormal.

[0207] (2) The script executed by the device agent software deployed on data processing server 2:

[0208] Determine whether the simulation software process deployed on data processing server 2 is working normally.

[0209] Determine whether KVM switch 1 is working normally.

[0210] Determine whether the CPU usage of data processing server 2 <= maxCPU

[0211] Determine whether the memory usage of data processing server 2 <= maxMemory

[0212] Determine whether the hard disk usage of data processing server 2 <= maxDisk

[0213] If all the above determinations are normal, the joint test detection result of data processing server 2 is normal, otherwise the joint test detection result is abnormal.

[0214] Report the joint test detection result of data processing server 2 to data processing server 1.

[0215] (3) The script executed by the device agent software deployed on data processing server 3

[0216] Determine whether the duplex management software process deployed on data processing server 3 is working normally.

[0217] Determine whether the CPU usage of data processing server 3 <= maxCPU

[0218] Determine whether the memory usage of data processing server 3 <= maxMemory

[0219] Judgment data processing server 3 hard disk usage rate <= maxDisk

[0220] If the above judgment is all normal, the joint test detection result of the data processing server 3 is normal, otherwise the joint test detection result of the data processing server 3 is abnormal.

[0221] Report the joint test detection result of the data processing server 3 to the data processing server 1.

[0222] 3.4.4 Report joint test detection result: The device agent software (main) adds the system level joint test detection result to the current system time, encapsulates it into the data packet of the Trap command of the SNMP protocol, saves it to the device management information base and reports it to the protocol processing software of the server. The protocol processing software of the server parses the data packet, saves the system level joint test detection result to the joint test database, and sends the information arrival notification to the server automation joint test software. Taking the execution of the joint test detection instruction of the data processing system as an example, the variable binding content in the PDU data packet in the joint test detection result reported by the data processing system is as follows:

[0223] {

[0224] 1.6.2.3.2.7.3.2.0: 33200 / / Instruction sending or feedback time

[0225] 1.6.2.3.2.7.3.2.1: '1.3.6.1.4.1.732.17' / / Branch entry of data processing system

[0226] 1.3.6.1.4.1.732.17.1.0: 'SJCL' / / Identification of data processing system

[0227] 1.3.6.1.4.1.732.17.1.1: 'LSJC' / / Code of joint test detection instruction

[0228] 1.3.6.1.4.1.732.17.1.2: 2 / / Number of configuration information carried when issuing joint test instruction

[0229] 1.3.6.1.4.1.732.17.1.2.1: '2c08c2b2c7c6e79a11cd8ab77ce4e494' / / Joint test plan ID

[0230] 1.3.6.1.4.1.732.17.1.2.2: '9c8c4c1135d0c27a2d8e219862958239' / / Joint test project ID

[0231] 1.3.6.1.4.1.732.17.1.3: 2 / / execution information code, 2 indicates that the instruction is successfully executed. See Table 2 for specific execution code meanings.

[0232] 1.3.6.1.4.1.732.17.1.4:'success' / / execution information description, fill in the data processing system joint test detection result here.

[0233] }

[0234] Table 2 Execution code format

[0235] Serial number Execution code Execution content 1 0 Received instruction, start executing instruction 2 1 Received instruction, unable to start execution 3 2 Instruction successfully executed 4 3 Instruction execution failed

[0236] 3.4.5 Processing joint test results: The service-side automated joint test software receives information arrival notification, obtains system joint test results from the joint test database, judges whether the joint test results reported by each system are normal or abnormal, and if abnormal, directly displays the abnormality in red font on the detection page; if normal, judges whether the reporting time is within maxTime, if within maxTime, directly displays normal in green font on the detection page, if greater than maxTime, displays time abnormality in red font; if no system detection result is received, the detection page displays no detection in gray font.

[0237] Step four Joint test process monitoring and control. Start joint test, automatically execute joint test items according to joint test process, monitor joint test process on visual graphical interface, and when joint test fails, perform fault diagnosis analysis and processing.

[0238] 4.1 Start joint test plan, load joint test items, and automatically execute each joint test item according to joint test process.

[0239] 4.1.1 Start joint test plan: In the service-side automated joint test software joint test list, select the joint test plan to be executed, click the "start" button, start the joint test plan, and load the joint test items for execution.

[0240] 4.1.2 Execute joint test: automatically execute joint test items one by one according to joint test process, and the joint test process automatic execution process is displayed on the visual graphical interface.

[0241] 4.2 Each joint test item displays three steps on the service-side automated joint test software joint test process display page: instruction issuing, instruction execution, and result feedback.

[0242] 4.2.1 Instruction issuing: (1) The server-side automated joint debugging test software issues joint test instructions to the participating system agent software (master) of each participating system proxy device through the protocol processing software. (2) The protocol processing software issues joint test instructions using the GetRequest command of the SNMP protocol, and the instruction variable binding format is shown in Table 1. (3) The participating system device agent software (master) receives the joint test instruction data packet and feeds back that the joint test instruction has been received to the automated joint debugging test software through the protocol processing software of the server-side using the Response command of the SNMP protocol. (4) The server-side automated joint debugging test software receives the feedback that the joint test instruction has been received from all system agent ends of the joint test project, and then updates the state of the joint test project on the joint test process display page to change “instruction issuing” to green. (5) The agent software (master) of the device parses the joint test instruction, loads and parses the joint test script corresponding to “joint test project instruction code-participating system code-CODE”, obtains the devices participating in the joint test of the system, and distributes the joint test instruction to the device agent software (slave) participating in the joint test project.

[0243] Taking the process executed by the data processing system in the T0 information inspection as an example. (1) The device agent software (master) of the data processing system receives the joint test instruction data packet and obtains the T0JC joint test instruction after parsing. (2) The device agent software (master) loads the “T0JC-SJCL-CODE” file, and extracts the devices involved in the T0 information inspection in the script file, which are data processing server 1 and data processing server 2. (3) The device agent software (master) sends the T0JC joint test instruction data packet to the device agent software (slave) deployed on the data processing server 2. Since the device agent software (master) is deployed on the data processing server 1, it does not need to distribute the T0JC joint test instruction to the data processing server 1.

[0244] 4.2.2 Instruction execution: The device agent software (slave) of each proxy receives the joint test instruction, parses it, loads and parses the joint test script corresponding to “joint test project instruction code-participating system code-CODE”, locates the script content that needs to be executed by the device, loads the parameter file corresponding to “joint test project instruction code-participating system code-PARAM”, executes the script, and reports the script execution state information and process data to the device agent software (master). The device agent software (master) obtains the joint test instruction execution state and process data reported by each device agent software (slave), executes the script that needs to be executed by the device agent software (master) in the joint test script, and feeds back the joint test instruction execution state and process data to the server-side automated joint debugging test software through the protocol processing software using the Trap instruction of the SNMP protocol. The joint test process display page of the automated joint debugging test software updates the state of the joint test project to change “instruction execution” of the joint test project to violet, indicating that it is being executed.

[0245] The process executed by the data processing system in the T0 information checking is taken as an example to illustrate the instruction execution process. The device agent software (slave) deployed on the data processing server 2 executes the T0 information checking process: (1) The device agent software (slave) of the data processing server 2 receives and parses the T0 JC joint test instruction data packet. (2) The “T0JC-SJCL-CODE” file is loaded, and the script location where the data processing server 2 executes the script is located. (3) In the script, the T0 information publishing instruction is sent to the simulation software (software deployed on the data processing server 2), and the T0 information publishing duration is obtained from the T0 JC joint test instruction data packet, which is 5 seconds. (4) The simulation software executes the T0 information publishing instruction, and publishes the T0 information for 5 seconds. (5) The device agent software (slave) of the data processing server 2 obtains the T0 information published by the simulation software, and sends it to the device agent software (master) deployed on the data processing server 1.

[0246] The device agent software (master) deployed on the data processing server 1 executes the T0 information checking process: (1) The device agent software (master) loads the “T0JC-SJCL-CODE” file, locates the script location where the device agent software (master) needs to execute the script, and executes the script. (2) In the script, the simulation software continuously sends the T0 information to the device agent software (master), and the received T0 information is sent to the device agent software (master). (3) The safety control processing software receives the T0 information continuously sent by the simulation software, and sends the received T0 information to the device agent software (master).

[0247] 4.2.3 Result feedback: The device agent software (slave) executes the joint test instruction, sends the execution result to the device agent software (master), the device agent software (master) gathers the joint test instruction execution results reported by each device agent software (slave) in the system jurisdiction, integrates the execution results of each device into the system level instruction execution result, and reports the instruction execution result to the automatic joint test software of the server. The automatic joint test software obtains the joint test instruction execution results fed back by each system, judges whether all systems in the joint test project have fed back the execution results, updates the state of the joint test project in the joint test process display page, including the overall states such as normal completion, abnormal completion and execution, and marks the start time and end time of each process execution and other more detailed information, to provide intuitive and comprehensive decision information for the joint test personnel.

[0248] Take the process executed by the data processing system in the T0 information inspection as an example. The device agent software (master) in the data processing system executes the joint test instruction process: the device agent software (master) receives the T0 information sent by the analog simulation software, the comprehensive processing software and the safety control processing software, executes the steps according to the T0 information inspection in the "T0JC-SJCL-CODE" script file, and performs time comparison on the T0 information sent by the three software. If all the requirements within maxTimeDiff are met, the T0 information inspection comparison result of the data processing system is normal, if there is software that does not meet the requirements, the T0 information inspection comparison result of the data processing system is abnormal. The system-level inspection result is sent to the automatic joint test software through the service end protocol processing software by using the Trap instruction of the SNMP protocol.

[0249] 4.2.4. Determine whether the current joint test project is finished: the service end automatic joint test software determines the end condition of the current joint test project test flow, stops the operation of the test equipment in the current joint test project when the end condition is met, and executes 4.2.5; when the end condition is not met, continues to collect the running state and related data of each test equipment, and jumps to 4.2.2 for execution.

[0250] 4.2.5. Joint test fault judgment: when the joint test project joint test flow is finished, the service end automatic joint test software automatically analyzes and diagnoses faults according to the collected various data, automatically generates the test result of the current joint test project, and judges whether a fault occurs in the execution of the current joint test project. If a fault occurs, execute 4.2.6; if no fault occurs, jump to 4.2.8 for execution.

[0251] 4.2.6. Joint test fault processing: when a fault occurs in the joint test flow, list the fault data and fault diagnosis result, even the fault handling suggestion, and wait for the joint test commander to handle.

[0252] 4.2.7. The joint test commander can directly operate on the state diagram, such as viewing the execution result of each flow, or selectively viewing fault information and fault diagnosis result, obtaining fault handling suggestions based on the matching of similar fault solutions in the fault library, and solving the fault and making decisions according to the information. If the current joint test project is executed again after the fault is handled, jump to 4.2.1 for execution; if the next joint test project is entered, execute 4.2.8. The two controls can be directly operated on the state diagram.

[0253] 4.2.8. Joint test project end processing: after the execution of the current joint test project is finished, it is judged whether there is a next joint test project. If there is, jump to 4.2.1 for execution; if there is not, the whole joint test process is finished.

[0254] Step five: joint test report generation. All joint test items in the joint test process are executed, and the entire joint test process is completed. After the joint test process is completed, the system can automatically generate a joint test report, summarize the joint test plan execution process, and give an overall and each participating system evaluation of the joint test situation.

[0255] 5.1 Edit joint test report format: The joint test report format is edited in a WYSIWYG graphical editing mode to develop the format of the joint test report. Text, tables, pictures, analysis graphics, and other types of report content can be inserted. Mixed types of content are supported. The joint test report format editing finally forms a format template.

[0256] 5.2 Automatic generation of joint test report: Based on the joint test report format template, the dynamic content and the joint debugging result data are associated, the joint debugging data is queried, the required content is dynamically generated, and the static content is fused together according to the layout requirements to automatically generate a complete joint test report.

[0257] Those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment methods can be completed by programs instructing related hardware, and the programs can be stored in a computer readable storage medium, such as ROM / RAM, a magnetic disc, an optical disc, etc.

[0258] The above only describes the preferred embodiments of the present application. It should be noted that those skilled in the art can make several improvements and refinements without departing from the principles of the present application. These improvements and refinements should also be considered within the scope of protection of the present application.

Claims

1. A device automation joint debugging test system, characterized in that, Comprise: The architecture mode is realized by using the architecture mode of service end and agent end, the architecture mode of service end automatic test (A) and agent end automatic test (B); the service end automatic test (A) is responsible for making test plan, starting test execution, issuing test instruction to agent end, monitoring test process, receiving test instruction execution state and process data reported by agent end, comprehensively processing, analyzing and displaying the execution state and process data, processing faults in test process, realizing automatic test management of test equipment, and the management range is all systems included in test plan; the agent end automatic test (B) is responsible for test instruction execution of each test equipment / system, and the range is each system, subsystem or component in equipment, and provides test instruction execution state and process data information for service end automatic test; the service end and agent end use SNMP protocol to transfer test instruction, instruction execution state and test process data; Wherein, the service end automatic test (A) comprises: automatic test software (a1), protocol processing software (a2), test database (a3); the automatic test software (a1) realizes test project management, test plan preparation, test execution starting, monitoring and controlling test execution process on visual interface, processing test faults, and generating test report after test; the protocol processing software (a2) is a bridge connecting service end and agent end, and realizes issuing test instruction, collecting test instruction execution state and process data; the test database (a3) stores test project, test plan, test execution process data and abnormal processing information, and is used for supporting test process display and playback; Wherein, the agent end automatic test (B) comprises: the agent end automatic test uses master-slave mode to realize, and test systems are grouped to manage equipment; each test system of agent end comprises a first equipment agent software (b1), equipment management information database (b2) and a second equipment agent software (b3) disposed in each equipment under jurisdiction of the system; wherein, the first equipment agent software (b1) is set as master mode, and the second equipment agent software (b3) is set as slave mode; the first equipment agent software (b1) realizes distributing received test instruction to specified second equipment agent software (b3) for execution, receiving test instruction execution state and process data reported by second equipment agent software (b3), and reporting to service end protocol processing software (a2) after fusion processing; the second equipment agent software (b3) receives test instruction, executes test instruction, generates test instruction execution state and process data and reports; the equipment management information database (b2) is used for storing MIB format instruction execution state and process data.

2. The device automatical joint debugging test system according to claim 1, wherein, The service end automatic joint debugging test software (a1) comprises: joint test project management (a11), joint test plan compilation (a12), command dispatching and monitoring (a13), joint test report management (a14), joint test process playback (a15) and system management (a16); the joint test project management (a11) realizes the functions of adding, deleting, modifying and inquiring a joint test project, and each joint test project is equivalent to a joint test stage; the joint test plan compilation (a12) provides the function of making a joint test plan, selects a joint test project, generates a joint test flow, prepares joint test data, configures a joint test project and related parameters and data according to the joint test plan; the command dispatching and monitoring (a13) automatically dispatches the joint test operation of the whole task system according to a pre-set joint test flow and implements monitoring, completes the automatic configuration, operation control, information collection, fault diagnosis and analysis of the joint test flow, records process data, and exhibits the details of the joint test process in an image intuitive graphical manner; the joint test report management (a14) has the function of automatically generating a joint test report, and after the joint test is completed, the system can automatically generate a joint test report according to the working condition of a test equipment and give an evaluation on the joint test condition; the joint test process playback (a15) plays back the whole automatic joint debugging test process, and the playback process is paused, continued and speed-adjusted; the system management (a16) collects typical fault modes and optimal solutions in the past automatic joint debugging test process, forms a fault knowledge base, records system operation logs and facilitates audit inspection.

3. The device automatical joint debugging test system according to claim 1, wherein, The service end protocol processing software (a2) comprises: data receiving (a21), data forwarding (a22) and data storage (a23); the data receiving (a21) realizes the function of receiving data information reported or issued by other software, including receiving a joint test instruction issued by the service end automatic joint debugging test software and receiving a joint test instruction execution state and execution process data reported by the agent end second equipment agent software (b3); the data forwarding (a22) forwards the joint test instruction issued by the service end automatic joint debugging test software (a1) to the agent end first equipment agent software (b1); after the data storage (a23) receives the joint test instruction execution state and process data reported by the agent end first equipment agent software (b1), the data storage (a23) stores the joint test instruction execution state and process data into a joint test database (a3) and sends an information arrival notification to the service end automatic joint debugging test software (a2).

4. The device automatical joint debugging test system according to claim 1, characterized in that, The first device agent software (b1) of the agent side comprises: data receiving (b11), data processing (b12), data sending (b13) and data storage (b14); the data receiving (b11) receives the joint test instruction forwarded by the service end protocol processing software (a2); the data processing (b12) analyzes the received joint test instruction, and distributes the instruction to the second device agent software (b3) to execute; the joint test instruction execution state and process data sent by each second device agent software (b3) in the system are received, the data is fused, and the joint test instruction system level execution state and process data are generated; the processed data is formatted, and the MIB format is generated; the data sending (b13) sends the processed instruction execution state and execution process data to the service end protocol processing software (a2) in the form of the Trap PDU of the SNMP protocol; and the data storage (b14) stores the processed instruction execution state and execution process data in the MIB format into the device management information base (b2).

5. The device automatical joint debugging test system according to claim 1, characterized in that, The second device agent software (b3) of the agent side comprises: data receiving (b31), joint test execution (b32) and data sending (b33); the data receiving (b31) receives the joint test instruction sent by the first device agent software (b1); the joint test execution (b32) analyzes the joint test instruction, loads the instruction execution script, executes the joint test instruction according to the pre-set steps in the script, and generates the instruction execution state and process data; and the data sending (b33) sends the generated instruction execution state and process data to the first device agent software (b1).

Images