Method of operating a simulation device, terminal device simulator and electronic device

Abstract

The application relates to the technical field of automatic wharf equipment simulation, and provides a method for operating simulation equipment, a wharf equipment simulator and electronic equipment. The method comprises the following steps: obtaining an execution instruction containing a device type of simulation equipment and a to-be-executed operation; determining a meta-action set corresponding to the to-be-executed operation based on the device type and the to-be-executed operation; executing all instruction meta-actions in the meta-action set, and outputting an execution result of the simulation equipment, wherein the execution result at least comprises a final working condition of the simulation equipment, and is used for determining whether corresponding software testing is passed. Through standardized and reusable meta-action design, the universality and reusability of the simulator are greatly improved, repeated development and resource waste are reduced, the development and delivery cycle is shortened, the simulation execution is stable and reliable, and the software testing efficiency of the automatic wharf is effectively improved.

Description

Technical Field

[0001] This application relates to the field of automated terminal equipment simulation technology, and in particular to a method for operating simulation equipment, a terminal equipment simulator, and electronic equipment. Background Technology

[0002] The automation of a port is the result of the collaborative work of numerous hardware devices and various software systems. During the construction of an automated port, port equipment simulators are used to simulate the operation of automated equipment and interact with software systems. This helps the software systems complete most of the functional tests related to the interaction between hardware devices and requirements, which can significantly reduce the debugging time between hardware and software systems and accelerate the construction process of automated ports.

[0003] In actual operation, the execution process of instructions in a dock equipment simulator may vary depending on the project. In some projects, the equipment needs to stop at a fixed location with containers, awaiting permission to continue or cancellation; in others, this is not necessary. Some projects involve directly grabbing / placing containers on the ground when operating in the landside area, while others use manned or unmanned trucks, and some combine these methods. Therefore, the requirements for the simulator differ, leading to the use of different simulators for different projects. However, this also introduces new problems:

[0004] The execution process of the same type of instructions for the same dock equipment varies across different projects. However, each project develops a new simulator, which not only leads to duplication of work and waste of resources, but also results in time-consuming, labor-intensive, and untimely delivery issues. Summary of the Invention

[0005] In view of this, this application provides a method for operating simulation equipment, a dock equipment simulator, and an electronic device, which can avoid the problem of needing to develop different simulators for different projects.

[0006] Some embodiments of this application provide a method for operating a simulation device. The application is described below from multiple perspectives, and the embodiments and beneficial effects described below can be referenced interchangeably.

[0007] In a first aspect, this application provides a method for operating a simulation device, applied to a dock equipment simulator, comprising:

[0008] Obtain the execution instructions of the simulation device, wherein the execution instructions include the device type of the simulation device and the operation to be performed, and the simulation device includes at least the main vehicle;

[0009] Based on the device type and the operation to be executed, a set of meta-actions corresponding to the operation to be executed is determined. The set of meta-actions includes multiple instruction meta-actions. Instruction meta-actions are the smallest execution units with reusability and standardized interfaces, used to enable the simulation device to execute the operation to be executed automatically and in a standardized manner.

[0010] Execute all instruction meta-actions in the meta-action set, output the execution result of the simulation device, the execution result includes at least the final operating condition of the simulation device, and the execution result is used to determine whether the software test corresponding to the simulation device has passed.

[0011] According to the embodiments of this application, the above-described technical solution of this application has at least the following beneficial effects:

[0012] The various operations to be performed by the simulated equipment are broken down into reusable, standardized instruction meta-actions. These instruction meta-actions are the smallest unit of simulation execution, breaking away from the traditional development model that tightly binds simulators to specific projects. For the same type of equipment operation in different automated terminal projects, there is no need to redevelop the entire simulator. Operation simulation can be achieved simply by combining and configuring standardized meta-actions, which greatly reduces repetitive development work, reduces the waste of manpower, time and other resources, and significantly improves the development and use efficiency of the simulator.

[0013] By employing a dual matching logic of device type and operation to be performed, the corresponding set of meta-actions is dynamically determined, enabling rapid adaptation to the personalized needs of different projects. No modifications to the simulator's core architecture are required; only the combination of meta-actions or configuration parameters need to be adjusted to meet the simulation requirements of different projects. This breaks through the limitations of traditional simulators that require a separate simulator for each project, achieving coverage of multiple projects and scenarios with a single simulator, greatly improving the simulator's versatility and adaptability.

[0014] In one possible implementation of the first aspect above, the instruction action includes a configurable expectation value and an encapsulated executable code unit, wherein the expectation value is used to determine whether the instruction action is successfully executed and as a triggering condition for the next instruction action, and the executable code unit is used to control the simulation device to perform a corresponding operation, wherein the operation includes at least forward, backward, and upward.

[0015] According to the implementation of this application, by designing instruction actions as configurable expected values ​​and encapsulated executable code units, it not only achieves accurate judgment of the execution state of instruction actions and accurate triggering of the next instruction action, but also standardizes, modularizes, and reuses basic operations, thereby improving the adaptability, stability, and maintenance efficiency of the simulator.

[0016] In one possible implementation of the first aspect above, a set of meta-actions corresponding to the operation to be performed is determined based on the device type and the operation to be performed, including:

[0017] Verify the validity of the executed instructions;

[0018] If the instruction is valid, determine the set of meta-actions corresponding to the operation to be executed based on the device type and the operation to be executed.

[0019] According to the embodiments of this application, adding a validity verification step for the execution instructions before determining the set of meta-actions can filter out invalid, erroneous or illegal execution instructions in advance, avoiding problems such as mis-execution, logical confusion or simulation abnormalities caused by abnormal instructions in the simulation equipment, thereby improving the safety, stability and execution reliability of the simulation process, while reducing invalid simulation processes and improving the overall testing efficiency and result credibility of the automated terminal equipment simulator.

[0020] In one possible implementation of the first aspect above, verifying the validity of the executed instructions includes:

[0021] Acquire real-time status data of the simulation equipment, which includes at least the current operating conditions of the simulation equipment;

[0022] The validity of the executed instructions is verified based on real-time status data and executed instructions.

[0023] According to the implementation method of this application, by combining the real-time status data of the simulation device to verify the validity of the execution instructions, the instruction verification no longer relies solely on the information of the instruction itself, but dynamically matches it with the actual working conditions of the device. This effectively avoids execution anomalies caused by conflicts between the instruction and the current state of the device, improves the accuracy, rationality and reliability of instruction verification, and further ensures the stability of the simulation device operation process and the authenticity of the simulation results.

[0024] In one possible implementation of the first aspect above, the meta-action set includes multiple instruction meta-actions with the same executable code unit. The instruction meta-actions with the same executable code unit may be located at different positions in the meta-action set, and the instruction meta-actions with the same executable code unit at different positions are configured with corresponding expected values.

[0025] According to the implementation of this application, by allowing the meta-action set to contain multiple instruction meta-actions with the same executable code unit but independently configurable expected values, and these meta-actions with the same execution logic can be placed in different positions in the process, it not only achieves a high degree of reuse of the same execution logic, but also meets the execution condition requirements of different steps and different working conditions through differentiated configuration of expected values, further improving the configuration flexibility and scenario adaptability of the simulation process, enabling the simulator to adapt to the differences in instruction execution processes in different projects more precisely and realistically.

[0026] In one possible implementation of the first aspect above, the instruction meta-action includes a pre-order meta-action and a post-order meta-action, wherein, in the execution order of the set of meta-actions, the post-order meta-action is located after the pre-order meta-action, and the execution of the post-order meta-action depends on the successful execution of the pre-order meta-action.

[0027] Execute all instruction meta-actions in the meta-action set and output the execution results of the emulator, including:

[0028] Based on the execution order of the meta-action set, the preceding meta-actions are obtained sequentially;

[0029] Execute the preceding action, and if the preceding action is successfully executed, output the expected value corresponding to the preceding action.

[0030] Based on this expected value, the subsequent meta-action operation corresponding to this expected value is triggered and executed until the set of meta-actions is traversed.

[0031] After traversing the set of meta-actions, output the execution result.

[0032] According to the implementation of this application, by dividing instruction meta-actions into pre-sequence meta-actions and post-sequence meta-actions according to the execution order, and using the expected value output after the successful execution of the pre-sequence meta-action as the condition for triggering the post-sequence meta-action, orderly, controllable, and dependent chain execution between meta-actions is realized, ensuring that the simulation device operates stably according to the preset logic.

[0033] In one possible implementation of the first aspect above, if it is determined that the preceding action was not successfully executed, the preceding action output is empty, and the execution of the following action is stopped.

[0034] According to the implementation method of this application, when the preceding meta-action is not successfully executed, the preceding meta-action does not output any result, which can intuitively and quickly locate the specific location where the exception occurred during the simulation execution process. This allows staff to clearly determine which instruction meta-action the exception occurred in simply by whether the meta-action outputs a result, without having to deeply understand the underlying code logic or analyze the code execution results line by line. This significantly reduces the debugging difficulty of the simulation process and improves the efficiency of fault location and the convenience of problem investigation.

[0035] Secondly, this application provides a dock equipment simulator, comprising:

[0036] The instruction acquisition module is used to acquire the execution instructions of the simulation device. The execution instructions include the device type of the simulation device and the operation to be performed. The simulation device includes at least the main trolley.

[0037] The meta-action set determination module is used to determine the meta-action set corresponding to the operation to be executed based on the device type and the operation to be executed. The meta-action set includes multiple instruction meta-actions. The instruction meta-action is the smallest execution unit with reusability and standardized interface, which is used to enable the simulation device to execute the operation to be executed automatically and in a standardized manner.

[0038] The execution module is used to execute all instruction meta-actions in the meta-action set and output the execution results of the simulation device. The execution results include at least the final operating condition of the simulation device and are used to determine whether the software test corresponding to the simulation device has passed.

[0039] Thirdly, this application provides an electronic device including a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded and executed by the processor to implement the method of operating a simulated device as disclosed in the first aspect and any possible implementation thereof.

[0040] Fourthly, this application provides a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or at least one program is loaded and executed by a processor to implement the method of operating a simulation device as disclosed in the first aspect and any possible implementation thereof.

[0041] Fifthly, this application provides a computer program product comprising: computer instructions that, when executed on an electronic device, cause the electronic device to perform the method of operating a simulated device as disclosed in the first aspect and any possible implementation thereof.

[0042] The beneficial effects of the second to fifth aspects can be found in the first aspect and the beneficial effects of any possible implementation of the first aspect, and will not be repeated here. Attached Figure Description

[0043] Figure 1 This is a flowchart of the method for operating the simulation device in the embodiments of this application;

[0044] Figure 2 This is a flowchart illustrating the process of determining the set of meta-actions in this application embodiment;

[0045] Figure 3 This is a flowchart illustrating the execution instruction verification process in an embodiment of this application.

[0046] Figure 4 This is a flowchart illustrating the operation process of the dock equipment simulator in this application embodiment;

[0047] Figure 5 This is a flowchart illustrating the execution steps of the meta-action set in the embodiments of this application;

[0048] Figure 6 This is a block diagram of the electronic device in the embodiments of this application;

[0049] Figure 7 This is a block diagram of a system-on-chip (SoC) in the embodiments of this application. Detailed Implementation

[0050] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0051] The technical problems to be solved by the embodiments of this application will be described below.

[0052] As described in the background technology section above, the construction of automated terminals relies on the collaborative work of hardware equipment and software systems. Terminal equipment simulators can simulate equipment operation and interact with software systems, helping to complete functional tests related to hardware interaction in the software system, shortening the software and hardware integration time, and accelerating the construction process.

[0053] However, in practical applications, different automated terminal projects have different requirements for the execution of equipment commands. For example, some projects require equipment to remain with containers awaiting permission or cancellation instructions, while others do not require this step. This necessitates the development of dedicated simulators for different projects, leading to problems such as redundant development, resource waste, time-consuming and labor-intensive development and maintenance, and untimely simulator delivery, severely impacting the software testing efficiency and overall construction progress of automated terminals. Therefore, it is crucial to provide a highly adaptable and reusable method for simulating equipment operation to address the issues of existing simulators being tightly bound to specific projects, lacking versatility, and resulting in redundant development, resource waste, and low delivery efficiency.

[0054] Therefore, in order to solve the above problems, this application provides a method for running simulation equipment, a terminal equipment simulator, and an electronic device. By decomposing equipment operations into reusable and standardized instruction actions, and dynamically matching a set of meta-actions composed of multiple instruction actions according to the equipment type and operation, the method effectively solves the problems of poor adaptability and repetitive development in traditional simulator projects, improves the simulator's versatility and reusability, reduces development resource waste, shortens the development and delivery cycle, and ensures stable and reliable simulation execution, thereby improving the efficiency of automated terminal software testing.

[0055] To better understand a method for operating a simulation device according to an embodiment of this application, the following description is provided in conjunction with the appendix to the specification. Figure 1 —5. The solutions corresponding to the methods and apparatus of the embodiments of this application will be described in detail.

[0056] Reference Figure 1 , Figure 1 This is a flowchart of the method for operating the simulation device in the embodiments of this application.

[0057] In one embodiment of the application, a method for operating a simulation device includes steps S100-S300.

[0058] S100 is used to obtain the execution instructions of the simulation device.

[0059] like Figure 1 As shown, step S100 corresponds to step A, obtaining device instructions.

[0060] It is understood that the above execution instructions include the device type of the simulation device and the operation to be performed, and the simulation device may at least include the main vehicle.

[0061] The aforementioned main trolley is the core motion unit of the quay crane or yard crane, which travels along the main beam or front beam track, carries the lifting mechanism and spreader, and undertakes the vertical lifting and horizontal transfer of containers. It is a key execution component for the quay crane to realize ship loading and unloading operations.

[0062] For example, the above execution command can be used to automatically grab boxes for the main trolley. Here, the equipment type is the main trolley, and the operation to be performed is automatic box grabbing.

[0063] S200, based on the device type and the operation to be performed, determines the set of meta-actions corresponding to the operation to be performed.

[0064] like Figure 1 As shown, step S200 above corresponds to step B, which involves selecting a set of meta-actions.

[0065] It is understandable that the set of meta-actions includes multiple instruction meta-actions. An instruction meta-action is the smallest execution unit with reusability and a standardized interface, used to enable the simulation device to automate and standardize the execution of the operation to be performed.

[0066] For example, taking the above-mentioned automatic container grabbing command of the main trolley as an example, when the terminal equipment simulator executes the automatic container grabbing command of the main trolley, it needs to complete a series of operations such as selecting a container, preparing to grab the container, checking whether the main trolley has completed the movement, and moving the spreader to a safe height.

[0067] The set of meta-actions corresponding to the main trolley's automatic container grabbing includes: selecting meta-actions, preparing to execute meta-actions, checking whether the main trolley has completed the movement meta-action, and moving the spreader to a safe height meta-action, among other command meta-actions. It can be seen that the command meta-actions correspond one-to-one with the actions to be performed by the dock equipment simulator.

[0068] It should be noted that staff can store all meta-action sets in the database and establish connections between equipment type, pending operation, and meta-action sets. The dock equipment simulator can determine the meta-action set corresponding to the pending operation from the database based on the equipment type and the pending operation. This part can be found in existing technology and will not be elaborated here.

[0069] S300 executes all instruction meta-actions in the meta-action set and outputs the execution results of the simulation device.

[0070] like Figure 1 As shown, step S300 corresponds to step C. First, the next instruction meta-action is obtained from the meta-action set, and it is determined whether there is a subsequent instruction meta-action. If there is a subsequent instruction meta-action, the instruction meta-action is executed, and then it is determined whether the instruction meta-action was executed successfully. If it was executed successfully, the next instruction meta-action is obtained again until there is no subsequent instruction meta-action; if there is no subsequent instruction meta-action, the process ends.

[0071] It is understood that the above execution results include at least the final operating condition of the simulated equipment, and the execution results are used to determine whether the software test corresponding to the simulated equipment has passed.

[0072] It should be noted that after the dock equipment simulator successfully executes the instruction meta-action in the meta-action set, the simulator's display can show the simulated equipment operation process, which serves as the execution result of the simulated equipment.

[0073] Therefore, compared with the prior art, the method for operating simulation equipment provided in this application solves the technical problems of repeated development of equipment simulators for different automated terminal projects, poor versatility, resource waste, long development cycles, and untimely delivery. By decomposing execution instructions into reusable and standardized instruction actions and dynamically matching and executing them, the versatility and reusability of the simulator are greatly improved, redundant development is reduced, the development and integration cycle is shortened, and software testing efficiency is improved.

[0074] To facilitate understanding of the technical solution of this application, the above steps S200-S300 will be described in detail below.

[0075] In some embodiments, instruction meta-actions include configurable expected values ​​and encapsulated executable code units.

[0076] Understandably, the aforementioned expected value is used to determine whether the instruction action was successfully executed and serves as the triggering condition for the next instruction action. The executable code unit is used to control the simulation device to perform corresponding operations, which at least include forward, backward, and upward movements. Furthermore, the aforementioned expected value can be freely configured by the operator.

[0077] By setting instruction actions to a structure that includes configurable expected values ​​and encapsulated executable code units, not only can the expected values ​​be used to accurately determine the execution status of the instruction action and precisely trigger the next instruction action, enhancing the controllability of the simulation process and the reliability of the execution results, but the encapsulated executable code units also enable the standardization and modularization of basic operations such as forward, backward, and upward, improving code reusability and ease of maintenance. The combination of these two aspects further improves the simulator's adaptability, execution stability, and testing accuracy, better adapting to the differentiated simulation needs of different projects.

[0078] In some embodiments, the meta-action set includes multiple instruction meta-actions with the same executable code unit. The instruction meta-actions with the same executable code unit may be located at different positions in the meta-action set, and the instruction meta-actions with the same executable code unit at different positions are configured with corresponding expected values.

[0079] For example, a set of meta-actions includes four instruction meta-actions: A1, B1, A2, and C1, which are executed in the order A1, B1, A2, and C1. The expected value of A1 is configured as 1, the expected value of B1 as 2, the expected value of A2 as 3, and the expected value of C1 as 4. A1 and A2 have the same executable code unit but are configured with different expected values.

[0080] Since A1 and A2 have the same executable code unit, their default execution results are also the same. If A1 and A2 are assigned the same expected value, or if no expected value is assigned, it is difficult for operators to distinguish whether the final result is output by A1 or A2, making it difficult to pinpoint the location of the fault in the meta-action set. Furthermore, B1 and C1 belong to different processing steps. If A1 and A2 are assigned the same expected value, or if only the result of their executable code unit is used as the final result, after the program executes A1 or A2, it is uncertain whether B1 or C1 should be executed next, causing the program to malfunction.

[0081] Since A1 and A2 are assigned different expected values, when A1 executes successfully, it outputs the expected value 1. Because B1 corresponds to expected value 1, when the output of expected value 1 is detected, the instruction action B1 is invoked and executed. When A2 fails, it outputs no value, allowing staff to know that A2 has malfunctioned and thus modify A2 accordingly.

[0082] Understandably, by setting multiple instruction meta-actions with identical execution code and independently configurable expected values ​​in the meta-action set, and applying them to different positions in the meta-action set, while achieving high reuse of execution logic, the execution conditions of different steps and working conditions can be met through differentiated expected value configuration, thereby improving the configuration flexibility and scenario adaptability of the simulation process, making the simulator more refined and more in line with the instruction execution differences of actual projects.

[0083] refer to Figure 2 , Figure 2 A flowchart illustrating the determination of the set of meta-actions in an embodiment of this application is shown.

[0084] like Figure 2 As shown, in some embodiments, a set of meta-actions corresponding to the operation to be performed is determined based on the device type and the operation to be performed, including steps S210-S220.

[0085] S210 verifies the validity of the executed instruction.

[0086] refer to Figure 3 , Figure 3 A flowchart illustrating the execution instruction verification process in an embodiment of this application is shown.

[0087] like Figure 3 As shown, in some embodiments, verifying the validity of the execution instructions includes steps S211-S12.

[0088] S211, acquire real-time status data of the simulation equipment, the real-time status data including at least the current operating conditions of the simulation equipment.

[0089] S212 verifies the validity of the executed instructions based on real-time status data and the executed instructions.

[0090] For example, if the current operating status of the main trolley is that it is idle, and the execution command received by the terminal equipment simulator at this time is for the main trolley to actively grab a container, then the terminal equipment simulator's built-in discrimination code will perform a logical judgment between the two and determine that the execution command is valid. Otherwise, it will determine that the execution command is invalid.

[0091] It should be noted that the process by which the dock equipment simulator judges the current operating conditions and executes commands can refer to existing technologies, and will not be elaborated here.

[0092] S220: If the execution instruction is valid, determine the set of meta-actions corresponding to the operation to be executed based on the device type and the operation to be executed.

[0093] Understandably, by combining real-time status data of the simulated equipment, such as its current operating conditions, to validate the execution of instructions, instruction validation no longer relies solely on the information of the instruction itself. Instead, it dynamically matches and judges the legality of the instructions with the real-time operating conditions of the equipment. This effectively avoids execution anomalies, logical confusion, and even simulation failures caused by conflicts between instructions and the current state of the equipment, or by invalid instructions. It significantly improves the accuracy, rationality, and reliability of instruction validation, further ensuring the stability and security of the simulated equipment's operation, enhancing the consistency between the simulated process and the actual operation of the equipment, ensuring the authenticity and reliability of the simulation results, and providing more reliable support for the testing of automated terminal software systems.

[0094] refer to Figure 4 and Figure 5 , Figure 4 A flowchart illustrating the operation process of the dock equipment simulator in an embodiment of this application is shown. Figure 5 This is a flowchart of the execution steps of the meta-action set in the embodiments of this application.

[0095] In some embodiments, instruction meta-actions include pre-sequence meta-actions and post-sequence meta-actions.

[0096] It is understandable that in the order of the meta-action set, the subsequent meta-action is placed after the preceding meta-action, and the execution of the subsequent meta-action depends on the successful execution of the preceding meta-action.

[0097] like Figure 4 As shown, in some embodiments, all instruction meta-actions in the meta-action set are executed, and the execution result of the simulation device is output, including steps S310-S340.

[0098] S310: Based on the order of the meta-action set, sequentially obtain the preceding meta-actions.

[0099] It is understandable that in a set of meta-actions arranged in a preset order, except for the first and last instruction meta-actions, each instruction meta-action possesses the dual attributes of both a preceding and following meta-action. For its immediately preceding instruction meta-action, it is a preceding meta-action, and its expected output after successful execution serves as the condition for triggering the execution of subsequent instruction meta-actions. For its immediately preceding instruction meta-action, it is a following meta-action, which can only be triggered by the successful execution result of its preceding instruction meta-action, ultimately forming an ordered chain of execution logic.

[0100] S320: Execute the preceding action. If the preceding action is successfully executed, output the expected value corresponding to the preceding action.

[0101] S330, based on the expected value corresponding to the preceding meta-action, triggers the execution of the following meta-action operation corresponding to the preceding meta-action, until the meta-action set has been traversed.

[0102] S340: After traversing the set of meta-actions, output the execution result.

[0103] like Figure 5 As shown, taking the automatic container grabbing command of the main trolley as an example, after the terminal equipment simulator determines the set of meta-actions corresponding to the automatic container grabbing command of the main trolley, it will execute the corresponding meta-actions one by one. For example, selecting a container, preparing to grab the container, checking whether the main trolley has completed the movement, moving the spreader to a safe height, etc., until all the instruction meta-actions in the set of meta-actions are executed.

[0104] Understandably, by dividing instruction actions into pre-sequence and post-sequence actions according to their execution order, and using the expected value output after the successful execution of a pre-sequence action as the condition for triggering the execution of the corresponding post-sequence action, it is possible to achieve orderly, controllable, and dependent chain execution between instruction actions. This ensures that the simulated equipment operates stably in strict accordance with the preset process and business logic, effectively avoiding abnormal situations such as disordered execution order or triggering subsequent actions when conditions are not met. This improves the rigor, traceability, and execution reliability of the simulation process, making the simulation process closer to the actual operating rules of real quay crane equipment, and further improving the accuracy and credibility of software test results.

[0105] In some embodiments, if it is determined that the preceding meta-action was not successfully executed, the preceding meta-action output is empty, and the execution of the following meta-action is stopped.

[0106] It is understandable that no result is output when the preceding meta-action is not successfully executed, in order to avoid misjudgment by staff who do not understand the computer program if the result of the unsuccessful execution is output.

[0107] This approach eliminates the need for testers and debuggers to deeply understand the underlying code implementation logic or analyze code execution logs or results line by line. They can clearly and intuitively determine which instruction or meta-action the exception occurred in simply by observing whether the meta-action outputs. This significantly lowers the debugging threshold and difficulty of automated terminal equipment simulators, effectively reduces troubleshooting time, and significantly improves fault location efficiency, debugging convenience, and system maintainability. At the same time, it enhances the stability, traceability, and credibility of the simulation process and software test results.

[0108] This application provides a dock equipment simulator, including:

[0109] The instruction acquisition module is used to acquire the execution instructions of the simulation device. The execution instructions include the device type of the simulation device and the operation to be performed. The simulation device includes at least the main trolley.

[0110] The meta-action set determination module is used to determine the meta-action set corresponding to the operation to be executed based on the device type and the operation to be executed. The meta-action set includes multiple instruction meta-actions. The instruction meta-action is the smallest execution unit with reusability and standardized interface, which is used to enable the simulation device to execute the operation to be executed automatically and in a standardized manner.

[0111] The execution module is used to execute all instruction meta-actions in the meta-action set, output the execution results of the simulation device, the execution results include at least the final operating condition of the simulation device, and the execution results determine whether the software test corresponding to the simulation device has passed.

[0112] The dock equipment simulator in this application embodiment executes the methods described in the above embodiments. Its specific functions and corresponding technical effects can be found in the above embodiments. Figure 1-5 The methods explained will not be repeated here.

[0113] This application provides an electronic device, which includes a processor and a memory. The memory stores at least one instruction or at least one program. When the processor loads and executes the instruction or program, the electronic device performs the method for operating a simulated device described in the above embodiments. Its specific functions and corresponding technical effects can be found in the above embodiments. Figure 1 - Figure 5 The method for operating the simulation equipment, as explained above, will not be repeated here. The following section will combine... Figure 6 The electronic devices described in the embodiments of this application will be described in detail.

[0114] refer to Figure 6The diagram shows a block diagram of an electronic device 1200 according to one embodiment of this application. The electronic device 1200 may include one or more processors 1201 coupled to a controller hub 1203. In at least one embodiment, the controller hub 1203 communicates with the processor 1201 via a multi-branch bus such as a front side bus (FSB) 1210, a point-to-point interface such as a quick path interconnect (QPI), or a similar connection. The processor 1201 executes instructions controlling general types of data processing operations. In one embodiment, the controller hub 1203 includes, but is not limited to, a graphics memory controller hub (GMCH) (not shown) and an input / output hub (IOH) (which may be on a separate chip) (not shown), wherein the GMCH includes memory and a graphics controller and is coupled to the IOH.

[0115] Electronic device 1200 may also include a coprocessor 1202 and a memory 1204 coupled to a controller hub 1203. Alternatively, one or both of the memory and the GMCH may be integrated within the processor (as described in this application), with memory 1204 and coprocessor 1202 directly coupled to processor 1201 and controller hub 1203, which resides on a single chip with the IOH. Memory 1204 may be, for example, dynamic random access memory (DRAM), phase change memory (PCM), or a combination of both. In one embodiment, coprocessor 1202 is a dedicated processor, such as, for example, a high-throughput MIC (many integerized core) processor, a network or communication processor, a compression engine, a graphics processor, a general-purpose computing on GPU (GPGPU), or an embedded processor, etc. Optional properties of coprocessor 1202 are indicated by dashed lines. Figure 6 middle.

[0116] As a computer-readable storage medium, memory 1204 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. For example, memory 1204 may include any suitable non-volatile memory such as flash memory and / or any suitable non-volatile storage device such as one or more hard-disk drives (HDDs), one or more compact disc (CD) drives, and / or one or more digital versatile disc (DVD) drives.

[0117] In one embodiment, electronic device 1200 may further include a network interface controller (NIC) 1206. Network interface 1206 may include a transceiver for providing a radio interface for electronic device 1200 to communicate with any other suitable device, such as a front-end module, antenna, etc. In various embodiments, network interface 1206 may be integrated with other components of electronic device 1200. Network interface 1206 can implement the functions of the communication unit in the above embodiments.

[0118] Electronic device 1200 may further include input / output (I / O) device 1205. I / O device 1205 may include: a user interface designed to enable a user to interact with electronic device 1200; a peripheral component interface designed to enable peripheral components to also interact with electronic device 1200; and / or sensors designed to determine environmental conditions and / or location information related to electronic device 1200.

[0119] It is worth noting that, Figure 6 This is merely an example. That is, although... Figure 6 The electronic device 1200 shown includes multiple devices such as a processor 1201, a coprocessor 1202, a controller hub 1203, and a memory 1204. However, in practical applications, devices using the methods of this application may include only a portion of the devices in the electronic device 1200. For example, it may include only the processor 1201 and the network interface 1206. Figure 6 The properties of the optional devices are shown in dashed lines. According to some embodiments of this application, the memory 1204, which is a computer-readable storage medium, stores instructions or programs that, when executed on a computer, perform the method for operating the simulation device described in the above embodiments. Specific details can be found in the methods of the above embodiments, and will not be repeated here.

[0120] Now for reference Figure 7The diagram shown is a block diagram of a system-on-chip (SoC) 1300 according to an embodiment of this application. Figure 7 In the diagram, similar components share the same reference numerals. Additionally, dashed boxes are an optional feature for more advanced SoCs. Figure 7 In this SoC 1300, the following are included: an interconnect unit 1350 coupled to an application processor 1310; a system proxy unit 1380; a bus controller unit 1390; an integrated memory controller unit 1340; a group or one or more coprocessors 1320, which may include integrated graphics logic, an image processor, an audio processor, and a video processor; a static random access memory (SRAM) unit 1330; and a direct memory access (DMA) unit 1360. In one embodiment, the coprocessor 1320 includes a dedicated processor, such as, for example, a network or communication processor, a compression engine, a GPGPU, a high-throughput MIC processor, or an embedded processor.

[0121] The static random access memory (SRAM) cell 1330 may include one or more computer-readable media for storing data and / or instructions. The computer-readable storage medium may store instructions, specifically, temporary and permanent copies of those instructions. These instructions may include, when executed by at least one unit in the processor, causing the SoC 1300 to perform a method for operating a simulated device according to the above embodiments, as detailed in the methods described above, which will not be repeated here.

[0122] This application provides a computer-readable storage medium storing at least one instruction or at least one program. The at least one instruction or at least one program is loaded and executed by a processor to implement the method for operating a simulation device described in the above embodiments. Its specific functions and corresponding technical effects can be referred to the above embodiments. Figure 1 - Figure 5 The method for operating the simulation equipment, as explained, will not be repeated here.

[0123] This application provides a computer program product, including: computer instructions, which, when executed on an electronic device, cause the electronic device to implement the method for operating a simulated device described in the above embodiments. Its specific functions and corresponding technical effects can be found in the above embodiments. Figure 1 - Figure 5 The method for operating the simulation equipment, as explained, will not be repeated here.

[0124] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0125] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0126] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0127] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, compact disc read-only memory (CD-ROMs), magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable media include any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0128] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the accompanying drawings. Furthermore, including structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0129] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than those shown in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0130] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0131] It should be noted that in the examples and description of this application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0132] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art should understand that various changes in form and detail may be made thereto without departing from the spirit and scope of this application.

Claims

1. A method for operating a simulation device, applied to a dock equipment simulator, characterized in that, include: Obtain execution instructions from the simulation device, the execution instructions including the device type of the simulation device and the operation to be performed, the simulation device including at least a main trolley; Based on the device type and the operation to be executed, a set of meta-actions corresponding to the operation to be executed is determined. The set of meta-actions includes multiple instruction meta-actions. Each instruction meta-action is a minimum execution unit with reusability and a standardized interface, used to enable the simulation device to execute the operation to be executed automatically and in a standardized manner. Execute all the instruction meta-actions in the set of meta-actions, output the execution result of the simulation device, the execution result including at least the final operating condition of the simulation device, and the execution result is used to determine whether the software test corresponding to the simulation device has passed.

2. The method according to claim 1, characterized in that, The instruction action includes a configurable expected value and an encapsulated executable code unit. The expected value is used to determine whether the instruction action is successfully executed and as a trigger condition for the next instruction action. The executable code unit is used to control the simulation device to perform corresponding operations, wherein the operations include at least forward, backward, and upward.

3. The method according to claim 1, characterized in that, The step of determining the set of meta-actions corresponding to the operation to be executed based on the device type and the operation to be executed includes: Verify the validity of the execution instructions; If the execution instruction is valid, the set of meta-actions corresponding to the operation to be executed is determined based on the device type and the operation to be executed.

4. The method according to claim 3, characterized in that, The verification of the validity of the execution instruction includes: Acquire real-time status data of the simulation device, wherein the real-time status data includes at least the current operating condition of the simulation device; The validity of the execution instruction is verified based on the real-time status data and the execution instruction.

5. The method according to claim 2, characterized in that, The meta-action set includes multiple instruction meta-actions that are identical to the executable code units. The instruction meta-actions that are identical to the executable code units are located at different positions in the meta-action set, and the instruction meta-actions that are identical to the executable code units at different positions are configured with corresponding expected values.

6. The method according to claim 2, characterized in that, The instruction meta-actions include pre-order meta-actions and post-order meta-actions, wherein, in the execution order of the set of meta-actions, the post-order meta-actions are located after the pre-order meta-actions, and the execution of the post-order meta-actions depends on the successful execution of the pre-order meta-actions. The execution of all the instruction meta-actions in the meta-action set and the output of the execution result of the simulation device include: Based on the execution order of the set of meta-actions, the preceding meta-actions are obtained sequentially; Execute the preceding meta-action, and if it is determined that the preceding meta-action was successfully executed, output the expected value corresponding to the preceding meta-action; Based on the expected value, the subsequent meta-action operation corresponding to the expected value is triggered and executed until the set of meta-actions is traversed. After traversing the set of meta-actions, output the execution result.

7. The method according to claim 6, characterized in that, If it is determined that the preceding meta-action was not successfully executed, the preceding meta-action output is empty, and the execution of the following meta-action is stopped.

8. A dock equipment simulator, characterized in that, include: The instruction acquisition module is used to acquire the execution instructions of the simulation device. The execution instructions include the device type of the simulation device and the operation to be performed. The simulation device includes at least a main trolley. The meta-action set determination module is used to determine a set of meta-actions corresponding to the operation to be executed based on the device type and the operation to be executed. The set of meta-actions includes multiple instruction meta-actions, and each instruction meta-action is a minimum execution unit with reusability and a standardized interface, used to enable the simulation device to execute the operation to be executed automatically and in a standardized manner. An execution module is used to execute all the instruction meta-actions in the meta-action set, output the execution result of the simulation device, the execution result including at least the final operating condition of the simulation device, and the execution result is used to determine whether the software test corresponding to the simulation device has passed.

9. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the method of operating the simulation device as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the method of operating a simulation device as described in any one of claims 1 to 7.

Images