Inspection task configuration method and system based on mandatory behavior interface and structured scene file

Abstract

The invention discloses an inspection task configuration method and system based on a mandatory behavior interface and a structured scene file, and the method comprises the steps: providing functional module items which forcibly achieve a unified behavior interface in a graphical designer, and enabling a user to form an inspection flow chart through dragging; writing the flow chart into a structured scene file through a serialization method defined by an interface; the emulator and the deployment tool load the file respectively, function module items are reconstructed through deserialization, an execution method of the function module items is directly called for logic verification, or robot instructions are generated through analysis. According to the method, a unified interface is used for binding graphs and logics, a single scene file is used for connecting the whole process of design, simulation and deployment, the problems that in a traditional scheme, operation is complex, and data splitting and semantics are inconsistent are solved, the purpose that line is achieved through programming is achieved, the configuration threshold is remarkably lowered, and development efficiency and system reliability are improved.

Description

Technical Field

[0001] This invention belongs to the field of industrial automation and robot inspection technology, and in particular relates to an inspection task configuration method and system based on a forced behavior interface and a structured scene file. Background Technology

[0002] Inspection robots are widely used in critical facilities such as power substations, chemical plants, and data centers to perform equipment status monitoring and environmental perception tasks. Currently, the mainstream method for configuring inspection tasks relies on traditional graphical configuration tools. These tools typically provide toolbars with numerous buttons, map display areas, and attribute editing panels, where users must manually set inspection points, paths, and motion parameters.

[0003] However, such existing technologies have significant drawbacks:

[0004] Complex operation and high barrier to entry: The tool interface is complex and the parameters are highly professional, requiring users to have a high level of technical background. It is difficult for non-professionals to get started quickly, and the training cost is high.

[0005] Low debugging efficiency: Task configuration and on-site debugging are highly coupled, and technicians must repeatedly modify parameters and run tests on-site. The process is cumbersome, resulting in long project delivery cycles and high labor costs.

[0006] Data fragmentation throughout the process: The graphical files used in the task design phase, the logical models used in the simulation phase, and the instruction scripts finally deployed to the robot often use different data structures and formats (such as .scene, .json, script, etc.). This data heterogeneity necessitates additional manual conversion or script bridging, which not only easily introduces errors but also makes it difficult to ensure consistency among the design, simulation, and deployment phases, often resulting in the problem of "simulation passing, on-site execution failing".

[0007] "Block-based" programming is ineffective: Although some advanced systems have introduced the concept of graphical drag-and-drop ("block-based programming"), these blocks are usually just visual symbols and are not deeply bound to the underlying executable logic and structured parameters. After dragging and dropping the graphics, users still need to edit parameter files or write scripts elsewhere, failing to achieve true "what you see is what you get" (WYSIWYG) and "what you write is what you execute".

[0008] Therefore, there is an urgent need in this field for a new configuration scheme that can run through the entire process of task design, simulation verification and field deployment, and ensure data and semantic consistency. Summary of the Invention

[0009] The purpose of this invention is to overcome the aforementioned deficiencies of the prior art and provide a method and system for configuring inspection tasks based on a mandatory behavior interface and structured scene files. This method aims to achieve seamless integration from graphical design and high-fidelity simulation to reliable deployment through a unified software architecture, completely resolving data fragmentation and semantic inconsistency issues, significantly reducing the operational threshold, and improving configuration efficiency and system reliability.

[0010] In a first aspect, the present invention provides a method for configuring inspection tasks based on a mandatory behavior interface and a structured scene file, including:

[0011] In the graphical design environment, multiple functional module items are provided. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file.

[0012] In response to the user's drag-and-drop and configuration operations in the graphical design environment, multiple functional module items are combined into an inspection task flowchart;

[0013] The serialization method implemented by each of the aforementioned functional module items is invoked to serialize all functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file;

[0014] The inspection logic simulator loads the unified structured scenario file, instantiates the corresponding functional module item object according to the type identifier in the data node, calls its deserialization method to reconstruct its state, and calls the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization.

[0015] The inspection deployment tool parses the same unified structured scene file and, based on the type identifier and configuration parameters in the data nodes, directly generates or maps a sequence of control instructions that can be executed by the inspection robot.

[0016] Secondly, the present invention provides an inspection task configuration system based on a mandatory behavior interface and a structured scene file, comprising:

[0017] The acquisition module is configured to provide multiple functional module items in a graphical design environment. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file.

[0018] The combined module is configured to respond to the user's drag-and-drop and configuration operations in the graphical design environment, combining multiple functional module items into an inspection task flowchart;

[0019] The calling module is configured to call the serialization method implemented by each of the aforementioned functional module items, and serialize all functional module items and their configuration parameters and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file;

[0020] The processing module is configured to load the unified structured scenario file into the inspection logic simulator, instantiate the corresponding functional module item object according to the type identifier in the data node, call its deserialization method to reconstruct its state, and call the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization.

[0021] The generation module is configured to parse the same unified structured scene file as the inspection deployment tool, and directly generate or map a sequence of control instructions that can be executed by the inspection robot based on the type identifier and configuration parameters in the data nodes.

[0022] Thirdly, an electronic device is provided, comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the steps of the inspection task configuration method based on a mandatory behavior interface and a structured scene file according to any embodiment of the present invention.

[0023] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein when the program instructions are executed by a processor, the processor performs the steps of the inspection task configuration method based on a mandatory behavior interface and a structured scene file according to any embodiment of the present invention.

[0024] The inspection task configuration method and system based on the mandatory behavior interface and structured scene file of this application, by forcing all functional module items to implement a unified behavior interface containing executable logic and serialization capabilities, and deeply binding it with the structured scene file, constructs a three-in-one object model of "graphics-logic-data", thereby systematically solving the three core pain points of existing inspection task configuration technology: high operation threshold, low debugging efficiency, and fragmented data throughout the process. Specifically, this method first endows graphical "building blocks" with realistic execution semantics, achieving true "what is programmed is what is executed," enabling even non-professional users to intuitively orchestrate complex tasks, significantly reducing the barrier to entry and training costs. Second, by using structured scenario files as the sole and authoritative data source for the design, simulation, and deployment phases, it completely eliminates the risks of data inconsistency and semantic distortion caused by multi-format conversion in traditional solutions, ensuring high consistency from virtual simulation to physical execution. Third, the simulator verifies by directly deserializing and calling the built-in execution methods of functional modules, abandoning the dependence on independent script interpreters, making the simulation path completely equivalent to the real deployment logic, thereby discovering most errors in the design phase, greatly reducing on-site debugging time and manpower investment, and improving development efficiency and system reliability. Finally, this architecture forms a loosely coupled, highly cohesive, and closed-loop verifiable configuration system, laying a solid technical foundation for the rapid deployment, reliable operation, and subsequent functional expansion of the inspection system. Attached Figure Description

[0025] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 A flowchart illustrating an inspection task configuration method based on a mandatory behavior interface and a structured scene file, provided in an embodiment of the present invention;

[0027] Figure 2 This is a structural block diagram of an inspection task configuration system based on a mandatory behavior interface and a structured scene file, provided in an embodiment of the present invention.

[0028] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] Please see Figure 1 The diagram shows a flowchart of an inspection task configuration method based on a mandatory behavior interface and a structured scene file, according to this application.

[0031] like Figure 1 As shown, the inspection task configuration method based on the mandatory behavior interface and structured scene files specifically includes the following steps:

[0032] Step S101: In the graphical design environment, multiple functional module items are provided. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file.

[0033] In this step, the unified behavior interface includes an execution method, which encapsulates and executes the specific inspection action logic represented by the functional module item.

[0034] The method for serializing to a structured file is used to convert the instance data of the functional module item, including its type identifier, business parameters and graphical attributes, into the data format of the corresponding node in the structured scene file and write it.

[0035] The method for deserializing from a structured file is used to read data from the corresponding node of the structured scene file and restore the instance state of the functional module item.

[0036] Step S102: In response to the user's drag-and-drop and configuration operations in the graphical design environment, combine the multiple functional module items into an inspection task flowchart.

[0037] In this step, the graphical design environment, the inspection logic simulator, and the inspection deployment tool share the same unified structured scenario file as the sole data source, achieving data consistency and semantic consistency throughout the entire process from task design and logic verification to on-site deployment.

[0038] Step S103: Invoke the serialization method implemented by each of the functional module items to serialize all the functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file.

[0039] In step S104, the inspection logic simulator loads the unified structured scenario file, instantiates the corresponding functional module item object according to the type identifier in the data node, calls its deserialization method to reconstruct its state, and calls the execution method of the functional module item object in the process sequence to simulate the execution process of the inspection task and perform a visual display.

[0040] In this step, the inspection logic simulator drives the simulation process by directly calling the execution methods of the reconstructed functional module item objects, without relying on an external script interpreter or a separate state machine model.

[0041] Step S105: The inspection deployment tool parses the same unified structured scene file and, based on the type identifier and configuration parameters in the data nodes, directly generates or maps a sequence of control instructions that can be executed by the inspection robot.

[0042] In this step, the unified structured scenario file adopts XML format, and the data node is an XML element node. Its attributes and child elements are used to store the type identifier, business parameters and graphic attributes of the functional module items.

[0043] In summary, the method of this application constructs a three-in-one object model of "graphics-logic-data" by forcing all functional modules to implement a unified behavioral interface that includes executable logic and serialization capabilities, and deeply binding it with structured scene files. This systematically solves the three core pain points of existing inspection task configuration technologies: high operation threshold, low debugging efficiency, and fragmented data throughout the entire process. Specifically, this method first endows graphical "building blocks" with realistic execution semantics, achieving true "what is programmed is what is executed," enabling even non-professional users to intuitively orchestrate complex tasks, significantly reducing the barrier to entry and training costs. Second, by using structured scenario files as the sole and authoritative data source for the design, simulation, and deployment phases, it completely eliminates the risks of data inconsistency and semantic distortion caused by multi-format conversion in traditional solutions, ensuring high consistency from virtual simulation to physical execution. Third, the simulator verifies by directly deserializing and calling the built-in execution methods of functional modules, abandoning the dependence on independent script interpreters, making the simulation path completely equivalent to the real deployment logic, thereby discovering most errors in the design phase, greatly reducing on-site debugging time and manpower investment, and improving development efficiency and system reliability. Finally, this architecture forms a loosely coupled, highly cohesive, and closed-loop verifiable configuration system, laying a solid technical foundation for the rapid deployment, reliable operation, and subsequent functional expansion of the inspection system.

[0044] Please see Figure 2 The diagram shows a structural block diagram of an inspection task configuration system based on a mandatory behavior interface and a structured scene file, according to this application.

[0045] like Figure 2 As shown, the inspection task configuration system 200 includes an acquisition module 210, a combination module 220, a calling module 230, a processing module 240, and a generation module 250.

[0046] The acquisition module 210 is configured to provide multiple functional module items in the graphical design environment. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file. The combination module 220 is configured to combine multiple functional module items into an inspection task flowchart in response to user drag-and-drop and configuration operations in the graphical design environment. The calling module 230 is configured to call the serialization method implemented by each functional module item to serialize all functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a single serializer. In a unified structured scenario file, each functional module item corresponds to a data node in the structured scenario file; the processing module 240 is configured to load the unified structured scenario file into the inspection logic simulator, instantiate the corresponding functional module item object according to the type identifier in the data node, call its deserialization method to reconstruct its state, and call the execution method of the functional module item object in the process sequence to simulate the execution process of the inspection task and perform visualization; the generation module 250 is configured to parse the same unified structured scenario file into the inspection deployment tool, and directly generate or map a sequence of control instructions that can be executed by the inspection robot according to the type identifier and configuration parameters in the data node.

[0047] It should be understood that Figure 2 The modules and references described in the document Figure 1 The steps described in the text correspond to those in the method described above. Therefore, the operations, features, and corresponding technical effects described above also apply to the method described in the text. Figure 2 The various modules in the document will not be described in detail here.

[0048] In other embodiments, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein when the program instructions are executed by a processor, the processor performs the inspection task configuration method based on a mandatory behavior interface and a structured scene file in any of the above method embodiments.

[0049] In one embodiment, the computer-readable storage medium of the present invention stores computer-executable instructions, which are configured as follows:

[0050] In the graphical design environment, multiple functional module items are provided. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file.

[0051] In response to the user's drag-and-drop and configuration operations in the graphical design environment, multiple functional module items are combined into an inspection task flowchart;

[0052] The serialization method implemented by each of the aforementioned functional module items is invoked to serialize all functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file;

[0053] The inspection logic simulator loads the unified structured scenario file, instantiates the corresponding functional module item object according to the type identifier in the data node, calls its deserialization method to reconstruct its state, and calls the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization.

[0054] The inspection deployment tool parses the same unified structured scene file and, based on the type identifier and configuration parameters in the data nodes, directly generates or maps a sequence of control instructions that can be executed by the inspection robot.

[0055] Computer-readable storage media may include a program storage area and a data storage area. The program storage area may store an operating system and an application program required for at least one function. The data storage area may store data created based on the use of the inspection task configuration system based on the mandatory behavior interface and structured scene files. Furthermore, the computer-readable storage medium may include high-speed random access memory and may also include memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the computer-readable storage medium may optionally include memory remotely configured relative to the processor, which can be connected to the inspection task configuration system based on the mandatory behavior interface and structured scene files via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0056] Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiment of the present invention, such as... Figure 3 As shown, the device includes a processor 310 and a memory 320. The electronic device may also include an input device 330 and an output device 340. The processor 310, memory 320, input device 330, and output device 340 can be connected via a bus or other means. Figure 3Taking a bus connection as an example, the memory 320 is the computer-readable storage medium described above. The processor 310 executes various server functions and data processing by running non-volatile software programs, instructions, and modules stored in the memory 320, thereby implementing the inspection task configuration method based on the mandatory behavior interface and structured scene files described in the above method embodiment. The input device 330 can receive input numeric or character information and generate key signal inputs related to user settings and function control of the inspection task configuration system based on the mandatory behavior interface and structured scene files. The output device 340 may include a display screen or other display device.

[0057] The aforementioned electronic device can execute the method provided in the embodiments of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the method provided in the embodiments of the present invention.

[0058] In one implementation, the aforementioned electronic device is applied to an inspection task configuration system based on a forced behavior interface and structured scene files, serving as a client, and includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0059] In the graphical design environment, multiple functional module items are provided. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file.

[0060] In response to the user's drag-and-drop and configuration operations in the graphical design environment, multiple functional module items are combined into an inspection task flowchart;

[0061] The serialization method implemented by each of the aforementioned functional module items is invoked to serialize all functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file;

[0062] The inspection logic simulator loads the unified structured scenario file, instantiates the corresponding functional module item object according to the type identifier in the data node, calls its deserialization method to reconstruct its state, and calls the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization.

[0063] The inspection deployment tool parses the same unified structured scene file and, based on the type identifier and configuration parameters in the data nodes, directly generates or maps a sequence of control instructions that can be executed by the inspection robot.

[0064] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or some parts of embodiments.

[0065] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for configuring inspection tasks based on a mandatory behavior interface and structured scene files, characterized in that, include: In the graphical design environment, multiple functional module items are provided. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file. In response to the user's drag-and-drop and configuration operations in the graphical design environment, multiple functional module items are combined into an inspection task flowchart; The serialization method implemented by each of the aforementioned functional module items is invoked to serialize all functional module items, their configuration parameters, and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file; The inspection logic simulator loads the unified structured scenario file, instantiates the corresponding functional module item object according to the type identifier in the data node, calls its deserialization method to reconstruct its state, and calls the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization. The inspection deployment tool parses the same unified structured scene file and, based on the type identifier and configuration parameters in the data nodes, directly generates or maps a sequence of control instructions that can be executed by the inspection robot.

2. The inspection task configuration method based on a mandatory behavior interface and structured scene files according to claim 1, characterized in that, In the unified behavior interface: The execution method is used to encapsulate and execute the specific inspection action logic represented by the functional module item; The method for serializing to a structured file is used to convert the instance data of the functional module item, including its type identifier, business parameters and graphical attributes, into the data format of the corresponding node in the structured scene file and write it. The method for deserializing from a structured file is used to read data from the corresponding node of the structured scene file and restore the instance state of the functional module item.

3. The inspection task configuration method based on a forced behavior interface and structured scene files according to claim 2, characterized in that, The inspection logic simulator drives the simulation process by directly calling the execution methods of the reconstructed functional module items, without relying on an external script interpreter or an independent state machine model.

4. The inspection task configuration method based on a mandatory behavior interface and structured scene files according to claim 1, characterized in that, The unified structured scenario file adopts XML format, and the data node is an XML element node. Its attributes and sub-elements are used to store the type identifier, business parameters and graphic attributes of the functional module items.

5. The inspection task configuration method based on a mandatory behavior interface and structured scene files according to claim 1, characterized in that, The graphical design environment, the inspection logic simulator, and the inspection deployment tool all share the same unified structured scenario file as the sole data source, achieving data consistency and semantic consistency throughout the entire process from task design and logic verification to on-site deployment.

6. A patrol task configuration system based on a mandatory behavior interface and structured scene files, characterized in that, include: The acquisition module is configured to provide multiple functional module items in a graphical design environment. Each functional module item is an instance of a class that inherits from the graphical item base class and enforces a unified behavior interface. The unified behavior interface declares at least an execution method, a method for serializing to a structured file, and a method for deserializing from a structured file. The combined module is configured to respond to the user's drag-and-drop and configuration operations in the graphical design environment, combining multiple functional module items into an inspection task flowchart; The calling module is configured to call the serialization method implemented by each of the aforementioned functional module items, and serialize all functional module items and their configuration parameters and connection relationships in the inspection task flowchart into a unified structured scene file, wherein each functional module item corresponds to a data node in the structured scene file; The processing module is configured to load the unified structured scenario file into the inspection logic simulator, instantiate the corresponding functional module item object according to the type identifier in the data node, call its deserialization method to reconstruct its state, and call the execution method of the functional module item object in the process order to simulate the execution process of the inspection task and perform visualization. The generation module is configured to parse the same unified structured scene file as the inspection deployment tool, and directly generate or map a sequence of control instructions that can be executed by the inspection robot based on the type identifier and configuration parameters in the data nodes.

7. An electronic device, characterized in that, include: At least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 1 to 5.

Images