Equipment inspection method, device, electronic equipment and computer readable medium

Abstract

The present application discloses an equipment inspection method, device, electronic device and computer-readable medium, and relates to the field of computer technology. A specific implementation method includes: receiving an equipment inspection request, determining a mode identifier and a process identifier list corresponding to the equipment inspection request; calling a plug-in management interface to call a mode sub-plug-in corresponding to the mode identifier, and then updating the current system mode based on the mode sub-plug-in; based on the updated current system mode, starting the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtaining the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment. The upper-level variable business logic is divided into several execution combinations of sub-processes under different modes, and then the customized operation process requirements of the equipment inspection operation site are flexibly responded to by dynamically loading plug-ins, thereby improving the efficiency of equipment inspection.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a device inspection method, device, electronic device and computer-readable medium. Background Art

[0002] At present, when conducting track inspections, basically one type of equipment is used to inspect one item, and the multi-dimensional parameter inspection of the same section requires repeated use of multiple devices. This will increase the workload and complexity of the operators on the one hand, and reduce the efficiency of the entire track inspection on the other.

[0003] In the process of implementing this application, the inventors found that there are at least the following problems in the prior art:

[0004] When conducting track inspections, basically one type of equipment is used to detect one item. Multi-dimensional parameter detection of the same section requires repeated use of multiple devices, resulting in reduced efficiency of the entire track inspection. Summary of the invention

[0005] In view of this, the embodiments of the present application provide an equipment inspection method, device, electronic device and computer-readable medium, which can solve the problem that in the existing track inspection, basically one type of equipment is used to detect one content, and multi-dimensional parameter detection of the same section requires repeated use of multiple devices to perform operations, resulting in reduced efficiency of the entire track inspection.

[0006] To achieve the above object, according to one aspect of an embodiment of the present application, a device inspection method is provided, comprising:

[0007] Receive a device inspection request, and determine a list of mode identifiers and process identifiers corresponding to the device inspection request;

[0008] Call the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in;

[0009] Based on the updated current system mode, the sub-process plug-in corresponding to each process identifier in the process identifier list is started, and then the device data corresponding to the sub-process corresponding to each sub-process plug-in is obtained to inspect the equipment.

[0010] Optionally, before receiving the device inspection request, the method further includes:

[0011] Call the task scheduler to obtain the equipment inspection task list, and then determine the execution time of each equipment inspection task in the equipment inspection task list;

[0012] In response to determining that the current time reaches the execution time of any device inspection task in the device inspection task list, a device inspection request is generated based on the device inspection task that reaches the execution time.

[0013] Optionally, before calling the mode sub-plugin corresponding to the mode identifier, the method further includes:

[0014] Initialize the mode sub-plugin and initialize the sub-process plugin.

[0015] Optionally, initialize the mode sub-plugin, including:

[0016] Get the mode parameter information corresponding to the device inspection request;

[0017] The corresponding mode sub-plugin is located based on the mode identifier, and then based on the mode parameter information, the mode sub-plugin is updated to initialize the mode sub-plugin.

[0018] Optionally, initialize the subprocess plugin, including:

[0019] Get the process parameter information corresponding to the equipment inspection request;

[0020] The corresponding sub-process plug-ins are located based on the process identifier list, and then the sub-process plug-ins are updated based on the process parameter information to initialize the sub-process plug-ins.

[0021] Optionally, before calling the task scheduler, the method further includes:

[0022] Get task configuration parameters;

[0023] Initialize the task scheduler based on the task configuration parameters.

[0024] Optionally, before calling the plug-in management interface, the method further includes:

[0025] The calling interface corresponding to each mode sub-plugin and the calling interface corresponding to each sub-process plug-in are encapsulated to generate a plug-in management interface.

[0026] In addition, the present application also provides an equipment inspection device, including:

[0027] A receiving unit is configured to receive a device inspection request and determine a mode identifier and a process identifier list corresponding to the device inspection request;

[0028] An updating unit is configured to call a plug-in management interface to call a mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in;

[0029] The inspection unit is configured to start the sub-process plug-in corresponding to each process identifier in the process identifier list based on the updated current system mode, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment.

[0030] Optionally, the apparatus further comprises a request generating unit configured to:

[0031] Call the task scheduler to obtain the equipment inspection task list, and then determine the execution time of each equipment inspection task in the equipment inspection task list;

[0032] In response to determining that the current time reaches the execution time of any device inspection task in the device inspection task list, a device inspection request is generated based on the device inspection task that reaches the execution time.

[0033] Optionally, the device further includes an initialization unit configured to:

[0034] Initialize the mode sub-plugin and initialize the sub-process plugin.

[0035] Optionally, the initialization unit is further configured to:

[0036] Get the mode parameter information corresponding to the device inspection request;

[0037] The corresponding mode sub-plugin is located based on the mode identifier, and then based on the mode parameter information, the mode sub-plugin is updated to initialize the mode sub-plugin.

[0038] Optionally, the initialization unit is further configured to:

[0039] Get the process parameter information corresponding to the equipment inspection request;

[0040] The corresponding sub-process plug-ins are located based on the process identifier list, and then the sub-process plug-ins are updated based on the process parameter information to initialize the sub-process plug-ins.

[0041] Optionally, the request generation unit is further configured to:

[0042] Get task configuration parameters;

[0043] Initialize the task scheduler based on the task configuration parameters.

[0044] Optionally, the updating unit is further configured to:

[0045] The calling interface corresponding to each mode sub-plugin and the calling interface corresponding to each sub-process plug-in are encapsulated to generate a plug-in management interface.

[0046] In addition, the present application also provides an equipment inspection electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the equipment inspection method as described above.

[0047] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the device inspection method as described above is implemented.

[0048] One embodiment of the above invention has the following advantages or beneficial effects: the present application determines the mode identifier and process identifier list corresponding to the equipment inspection request by receiving the equipment inspection request; calls the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then updates the current system mode based on the mode sub-plug-in; based on the updated current system mode, starts the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtains the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment. The upper-level changeable business logic is divided into several sub-process execution combinations under different modes, and then the customized operation process requirements of the equipment inspection operation site are flexibly responded to by dynamically loading plug-ins, thereby improving the efficiency of equipment inspection.

[0049] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.

[0051] Figure 1 is a schematic diagram of the main process of the equipment inspection method according to the first embodiment of the present application;

[0052] Figure 2 is a schematic diagram of the main process of the equipment inspection method according to the second embodiment of the present application;

[0053] Figure 3 is a schematic diagram of an application scenario of the equipment inspection method according to the third embodiment of the present application;

[0054] Figure 4 is a schematic diagram of the main units of the equipment inspection device according to an embodiment of the present application;

[0055] Figure 5 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;

[0056] Figure 6 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0057] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0058] Figure 1 is a schematic diagram of the main process of the equipment inspection method according to the first embodiment of the present application, such as Figure 1 As shown, the equipment inspection method includes:

[0059] Step S101: receiving a device inspection request, and determining a list of mode identifiers and process identifiers corresponding to the device inspection request.

[0060] In this embodiment, the execution subject of the equipment inspection method (for example, a server) can receive the equipment inspection request through a wired connection or a wireless connection. The equipment can be railway equipment or aerospace equipment, etc., and the specific type of the equipment is not limited in this embodiment of the application.

[0061] Specifically, before receiving the device inspection request, the device inspection method further includes:

[0062] Call the task scheduler to obtain the equipment inspection task list, and then determine the execution time of each equipment inspection task in the equipment inspection task list; in response to determining that the current time has reached the execution time of any equipment inspection task in the equipment inspection task list, generate a device inspection request based on the equipment inspection task that has reached the execution time.

[0063] Specifically, before calling the task scheduler, the method further includes:

[0064] Get task configuration parameters; initialize the task scheduler based on the task configuration parameters.

[0065] During the actual track inspection operation, after the scheduling system is started, three nodes will be opened in parallel, namely the mode plug-in management node, the process plug-in management node and the scheduling node. After the scheduling node is started, the task configuration parameters configured according to the actual operation scenario are first loaded (such as the corresponding geometric inspection tasks, image inspection tasks, flaw detection inspection tasks, and image flaw detection inspection tasks, etc.). The task configuration parameters mainly determine the corresponding mode status and the list of processes that need to be executed in different types of inspection tasks. For example, the image inspection task needs to synchronously execute the basic information collection process, linear array camera collection process, 3D camera collection process, data storage process, and data reporting process in the task sub-mode state. Then the scheduling node will complete the initialization of the task scheduler and enter the state of waiting for task requests. At this point, the entire task scheduling system is initialized.

[0066] Step S102: calling the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then updating the current system mode based on the mode sub-plug-in.

[0067] Specifically, before calling the mode sub-plugin corresponding to the mode identifier, the method further includes:

[0068] Initialize the mode sub-plugin and initialize the sub-process plugin.

[0069] After the scheduling system is started, three nodes will be opened in parallel, namely the mode plug-in management node, the process plug-in management node and the scheduling node. The execution subject can call the mode plug-in management node to initialize the mode sub-plug-in, and can call the process plug-in management node to initialize the sub-process plug-in.

[0070] Specifically, the initialization mode sub-plugin includes:

[0071] Obtain mode parameter information corresponding to the device inspection request; locate the corresponding mode sub-plug-in based on the mode identifier, and then update the mode sub-plug-in based on the mode parameter information to initialize the mode sub-plug-in.

[0072] The execution subject can call the mode plug-in management node to load the mode parameter file (such as idle mode, maintenance mode, safety mode and task mode) configured according to the actual operation scenario, and then initialize the mode sub-plug-ins corresponding to each mode identifier according to the mode identifier in the mode parameter file, such as KX, WH, AQ, RW. For example, initialize the idle mode sub-plug-in corresponding to KX, the maintenance mode sub-plug-in corresponding to WH, the safety mode sub-plug-in corresponding to AQ, and the task mode sub-plug-in corresponding to RW. The embodiment of the present application does not specifically limit the specific representation form of the mode identifier, nor does it limit the specific correspondence between the mode identifier and the mode sub-plug-in.

[0073] Specifically, initialize the subprocess plugin, including:

[0074] Obtain process parameter information corresponding to the equipment inspection request; locate the corresponding sub-process plug-ins based on the process identification list, and then update the sub-process plug-ins based on the process parameter information to initialize the sub-process plug-ins.

[0075] The execution subject can call the process plug-in management node to load the process parameter file configured according to the actual operation scenario (such as self-test process, calibration process, diagnosis process, basic information collection process, geometric information collection process, image information collection process, flaw detection information collection process, motion control process, data reporting process and data storage process, etc.), and then initialize the sub-process plug-ins corresponding to each process identifier in the list according to the process identifier list in the process parameter file. The process identifier, for example, can be ZJ, BD, ZD, etc. The execution subject can initialize the self-test sub-process plug-in according to the process identifier ZJ, initialize the calibration sub-process plug-in according to the process identifier BD, and initialize the diagnosis sub-process plug-in according to the process identifier ZD. In addition, the execution subject can also divide the sub-process information secondary according to the specific sensor device identifier in the process parameter file, for example, according to the sensor device identifier XZ, initialize the basic information collection plug-in of the linear array camera; according to the sensor device identifier 3D, initialize the basic information collection plug-in of the 3D camera, etc.

[0076] Step S103, based on the updated current system mode, start the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment.

[0077] Under the updated current system mode, the execution subject starts the corresponding sub-process to obtain the corresponding device data by running each initialized sub-process plug-in to realize the inspection of the device.

[0078] After completing the initialization, the scheduling system parses and executes different inspection tasks. After receiving the inspection task request, the system first parses the inspection task type through the scheduler according to the information read from the task configuration parameters in the initialization phase, and determines the mode state and process execution list required for this inspection task. After all parameters are confirmed to be valid, the execution subject can first update the current system mode by switching the mode sub-plug-in through the task scheduling system. Then, the sub-process plug-ins that need to be executed are started in turn in the task state machine, and the status of each sub-process is monitored at the same time.

[0079] For example, in an image inspection task, the execution subject will start the basic information collection process, linear array camera collection process, 3D camera collection process, motion control process, data storage process and data reporting process in sequence through the scheduling system. The basic information collection process mainly collects the device's own parameter information through the hardware driver, the linear array camera and 3D camera collection process collects the corresponding image information through the camera driver, the motion control process controls the movement of the device through the motion driver, and the data storage and reporting process completes various data interaction functions through the data access driver. When all sub-processes are executed and exited, this inspection task also ends at the same time. The system returns to idle mode and waits for the next task request.

[0080] The overall software architecture of the task call system of the embodiment of the present application may include: an application layer, a plug-in management layer, a plug-in layer, and a general driver layer. The application layer runs the main task scheduling node (scheduler), which uses a planner and a state machine (FSM) to be responsible for the splitting and processing of the business logic and the interaction with the plug-in management layer. The plug-in management layer is mainly composed of a mode node (model_manager) for managing transient switching and a process node (procedure_manager) for managing process operation. The plug-in layer is composed of two corresponding groups of sub-plug-ins, each mode sub-plug-in (model_plugin) is mutually exclusive, and each process sub-plug-in (procedure_plugin) is in a parallel relationship. The general driver layer mainly provides a responsive function driver interface to each sub-plug-in, including a camera driver node (ccd_driver), a motion driver node (motion_driver), a data access driver node (dao_driver), and a hardware driver node (device_driver). By dividing the upper-level variable business logic into execution combinations of several sub-processes under different modes, it is possible to flexibly respond to the customized needs of the job site by dynamically loading plug-ins.

[0081] The operating mechanism of the entire architecture is that the scheduler of the application layer's main scheduling node communicates with the plug-in management node as needed, selects the correct mode and starts the corresponding process. Each process calls the public service of the driver layer to implement the relevant business logic operations. At the same time, the plug-in management node of the plug-in management layer sets a unified interface and diversified content. All content that needs to be interacted with the outside world is unified into a single designated interface, and the dynamic deletion of each sub-plug-in is realized by using a configuration file. This can greatly improve the adaptability of the entire set of running codes, and ultimately make the software system reusable and configurable.

[0082] The embodiment of the present application can quickly adapt different sensor hardware units in a variety of detection scenarios through the parameter configuration characteristics based on the plug-in architecture, and schedule the corresponding inspection task functions to perform operations, thereby greatly improving the versatility of the overall software and the timeliness of the inspection operations.

[0083] This embodiment receives a device inspection request, determines the mode identifier and process identifier list corresponding to the device inspection request; calls the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then updates the current system mode based on the mode sub-plug-in; based on the updated current system mode, starts the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtains the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the device. The upper-level variable business logic is divided into several sub-process execution combinations under different modes, and then the customized operation process requirements of the equipment inspection operation site are flexibly responded to by dynamically loading plug-ins, thereby improving the efficiency of equipment inspection.

[0084] Figure 2 is a schematic diagram of the main process of the equipment inspection method according to the second embodiment of the present application, such as Figure 2 As shown, the equipment inspection method includes:

[0085] Step S201: receiving a device inspection request, and determining a list of mode identifiers and process identifiers corresponding to the device inspection request.

[0086] The principle of step S201 is similar to that of step S101 and will not be described in detail here.

[0087] Step S202: encapsulate the calling interface corresponding to each mode sub-plug-in and the calling interface corresponding to each sub-process plug-in to generate a plug-in management interface.

[0088] The execution entity can unify all the content that needs to be interacted with externally into a single designated interface to encapsulate the calling interface corresponding to each mode sub-plug-in and the calling interface corresponding to each sub-process plug-in, and generate a plug-in management interface to achieve the reusability and configurability of the software system.

[0089] Step S203: calling the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then updating the current system mode based on the mode sub-plug-in.

[0090] Step S204, based on the updated current system mode, start the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment.

[0091] The principles of step S203 to step S204 are similar to those of step S102 to step S103 and will not be described in detail here.

[0092] Figure 3 : is a schematic diagram of an application scenario of the equipment inspection method according to the third embodiment of the present application. The equipment inspection method of the embodiment of the present application can be applied to the scenario of detecting multi-dimensional parameters of railway equipment on the same section. Figure 3 As shown, the server 302 receives the device inspection request 301, determines the mode identifier 303 and the process identifier list corresponding to the device inspection request 301

[0093] 306 (may specifically include process ID 1, process ID 2, ..., process ID n). Service

[0094] The plug-in management interface A is called by the device 302 to call the mode sub-plug-in corresponding to the mode identifier 303.

[0095] 304, and then update the current system mode 305 based on the mode sub-plug-in 304. Based on the updated current system mode 305, the server 302 starts the sub-process plug-in 307 (for example, it may include sub-process plug-in 1, sub-process plug-in 2, ..., sub-process plug-in n) corresponding to each process identifier in the process identifier list 306 (for example, it may include process identifier 1, process identifier 2, ..., process identifier n), and then obtains the device data 308 corresponding to the sub-process (for example, it may be the self-check process corresponding to the sub-process plug-in 1, the diagnosis process corresponding to the sub-process plug-in 2, ..., the basic information collection process corresponding to the sub-process plug-in n, and the embodiment of the present application does not limit the specific content of the sub-process corresponding to each sub-process plug-in) corresponding to each sub-process plug-in (for example, it may include sub-process plug-in 1, sub-process plug-in 2, ..., sub-process plug-in n) to perform inspection on the equipment.

[0096] The embodiment of the present application realizes general parameterized task scheduling by dynamically loading mode and process plug-ins, so that the detection equipment can quickly integrate various types of sensor units and use a unified software system to operate, greatly improving the software versatility and detection timeliness of the inspection equipment.

[0097] Figure 4 Schematic diagram of the main units of the equipment inspection device according to an embodiment of the present application. Figure 4 As shown, the equipment inspection device includes a receiving unit 401 , an updating unit 402 and an inspection unit 403 .

[0098] The receiving unit 401 is configured to receive a device inspection request and determine a mode identifier and a process identifier list corresponding to the device inspection request;

[0099] An updating unit 402 is configured to call a plug-in management interface to call a mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in;

[0100] The inspection unit 403 is configured to start the sub-process plug-in corresponding to each process identifier in the process identifier list based on the updated current system mode, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the device.

[0101] In some embodiments, the device further comprises Figure 4 The request generation unit not shown in the figure is configured to: call the task scheduler to obtain the equipment inspection task list, and then determine the execution time of each equipment inspection task in the equipment inspection task list; in response to determining that the current time has arrived at the execution time of any equipment inspection task in the equipment inspection task list, generate a device inspection request based on the equipment inspection task that has arrived at the execution time.

[0102] In some embodiments, the device further comprises Figure 4 The initialization unit not shown in the figure is configured as: an initialization mode sub-plug-in and an initialization sub-process plug-in.

[0103] In some embodiments, the initialization unit is further configured to: obtain mode parameter information corresponding to the device inspection request; locate the corresponding mode sub-plug-in based on the mode identifier, and then update the mode sub-plug-in based on the mode parameter information to initialize the mode sub-plug-in.

[0104] In some embodiments, the initialization unit is further configured to: obtain process parameter information corresponding to the device inspection request; locate the corresponding sub-process plug-ins based on the process identification list, and then update each sub-process plug-in based on the process parameter information to initialize each sub-process plug-in.

[0105] In some embodiments, the request generation unit is further configured to: obtain task configuration parameters; and initialize the task scheduler based on the task configuration parameters.

[0106] In some embodiments, the updating unit 402 is further configured to: encapsulate the calling interface corresponding to each mode sub-plug-in and the calling interface corresponding to each sub-process plug-in to generate a plug-in management interface.

[0107] It should be noted that the equipment inspection method and the equipment inspection device in the present application have a corresponding relationship in terms of specific implementation content, so the repeated content will not be explained again.

[0108] Figure 5 An exemplary system architecture 500 is shown to which the equipment inspection method or equipment inspection apparatus according to the embodiments of the present application can be applied.

[0109] like Figure 5As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0110] Users can use terminal devices 501, 502, 503 to interact with server 505 through network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0111] The terminal devices 501 , 502 , and 503 may be various electronic devices having a device inspection request processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0112] Server 505 can be a server that provides various services, such as a background management server that provides support for equipment inspection requests submitted by users using terminal devices 501, 502, and 503 (only as an example). The background management server can receive equipment inspection requests, determine the mode identifier and process identifier list corresponding to the equipment inspection request; call the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in; based on the updated current system mode, start the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment. The upper-level variable business logic is divided into execution combinations of several sub-processes under different modes, and then the customized operation process requirements of the equipment inspection operation site are flexibly responded to by dynamically loading plug-ins, thereby improving the efficiency of equipment inspection.

[0113] It should be noted that the equipment inspection method provided in the embodiment of the present application is generally executed by the server 505 , and accordingly, the equipment inspection device is generally set in the server 505 .

[0114] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0115] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer system 600 of a terminal device suitable for implementing an embodiment of the present application. Figure 6The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0116] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the computer system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0117] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.

[0118] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present application are executed.

[0119] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable storage media may include, for example, but are not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0120] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0121] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a receiving unit, an updating unit, and an inspection unit. The names of these units do not constitute limitations on the units themselves in some cases.

[0122] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device receives a device inspection request, determines the mode identifier and process identifier list corresponding to the device inspection request; calls the plug-in management interface to call the mode sub-plug-in corresponding to the mode identifier, and then updates the current system mode based on the mode sub-plug-in; based on the updated current system mode, starts the sub-process plug-in corresponding to each process identifier in the process identifier list, and then obtains the device data corresponding to the sub-process corresponding to each sub-process plug-in, so as to inspect the device.

[0123] According to the technical solution of the embodiment of the present application, the upper-level changeable business logic is divided into execution combinations of several sub-processes under different modes, and then the customized operation process requirements of the equipment inspection operation site are flexibly responded to by dynamically loading plug-ins, thereby improving the equipment inspection efficiency.

[0124] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A device inspection method, characterized in that: include: Receive a device inspection request, and determine a list of mode identifiers and process identifiers corresponding to the device inspection request; Call the plug-in management interface, initialize the mode sub-plug-in and initialize the sub-process plug-in, so as to call the mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in, wherein the initialization sub-process plug-in includes: calling the process plug-in management node to load the process parameter information configured according to the actual operation scenario, initializing the sub-process plug-ins corresponding to each process identifier in the list according to the process identifier list in the process parameter information, and performing secondary division on the sub-process plug-in according to the specific sensor device identifier in the process parameter information to initialize the corresponding sub-process plug-in; Based on the updated current system mode, the sub-process plug-in corresponding to each process identifier in the process identifier list is started, and then the device data corresponding to the sub-process corresponding to each sub-process plug-in is obtained to inspect the equipment.

2. The method according to claim 1, characterized in that Before receiving the device inspection request, the method further includes: Calling a task scheduler to obtain a device inspection task list, and then determining the execution time of each device inspection task in the device inspection task list; In response to determining that the current time reaches the execution time of any device inspection task in the device inspection task list, a device inspection request is generated based on the device inspection task that reaches the execution time.

3. The method according to claim 1, characterized in that The initialization mode sub-plugin includes: Obtaining mode parameter information corresponding to the device inspection request; The corresponding mode sub-plugin is located based on the mode identifier, and then based on the mode parameter information, the mode sub-plugin is updated to initialize the mode sub-plugin.

4. The method according to claim 2, characterized in that: Before calling the task scheduler, the method further includes: Get task configuration parameters; Initialize a task scheduler based on the task configuration parameters.

5. The method according to claim 1, characterized in that Before calling the plug-in management interface, the method further includes: The calling interface corresponding to each mode sub-plugin and the calling interface corresponding to each sub-process plug-in are encapsulated to generate a plug-in management interface.

6. An equipment inspection device, characterized in that: include: A receiving unit, configured to receive a device inspection request and determine a list of mode identifiers and process identifiers corresponding to the device inspection request; The initialization unit is configured to be an initialization mode sub-plug-in and an initialization sub-process plug-in; wherein, the initialization sub-process plug-in includes: calling the process plug-in management node to load the process parameter information configured according to the actual operation scenario, initializing the sub-process plug-ins corresponding to each process identifier in the list according to the process identifier list in the process parameter information, and performing secondary division on the sub-process plug-in according to the specific sensor device identifier in the process parameter information to initialize the corresponding sub-process plug-in; an updating unit, configured to call a plug-in management interface to call a mode sub-plug-in corresponding to the mode identifier, and then update the current system mode based on the mode sub-plug-in; The inspection unit is configured to start the sub-process plug-in corresponding to each process identifier in the process identifier list based on the updated current system mode, and then obtain the device data corresponding to the sub-process corresponding to each sub-process plug-in to inspect the equipment.

7. The device according to claim 6, characterized in that The apparatus further comprises a request generating unit configured to: Calling a task scheduler to obtain a device inspection task list, and then determining the execution time of each device inspection task in the device inspection task list; In response to determining that the current time reaches the execution time of any device inspection task in the device inspection task list, a device inspection request is generated based on the device inspection task that reaches the execution time.

8. An equipment inspection electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 5.

9. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images