Reliability test method, device and computer readable medium of cloud management platform

Abstract

The application provides a cloud management platform reliability testing method, device and computer readable medium. The scheme simulates any use condition of a user in an actual business scenario through a random selection mode. In a test task, as long as one operation is successfully executed and meets an expected result, a random selection is performed on all operations to continue execution. Therefore, theoretically, all operation combinations can be constructed, and any real use condition in an actual scenario is avoided to be omitted in the test. Meanwhile, when a test operation is executed incorrectly, the reliability of the cloud management platform can be accurately quantified through recording a fault-free running duration.

Description

Technical Field

[0001] This application relates to the field of information technology, and in particular to a reliability testing method, equipment, and computer-readable medium for a cloud management platform. Background Technology

[0002] Reliability refers to the probability that a system will produce correct output that meets specific performance standards within a specified time period. Currently, reliability testing for cloud management platforms generally includes stress testing, long-term stability testing, and negative testing. Stress testing involves subjecting the cloud management platform to a certain load state, or exceeding its designed maximum load, to verify its operation under high resource utilization. Long-term stability testing tests the cloud management platform's ability to operate continuously for an extended period under certain stress conditions. Negative testing constructs abnormal business scenarios through abnormal operations, abnormal business configurations, or abnormal business traffic to test the operational status of the cloud management platform.

[0003] When testing the reliability of a cloud management platform using the above testing scheme, testers need to follow pre-built test procedures. These test procedures are generally composed of different test operations combined by testers based on practical experience. However, with the development of technology, business scenarios have become more complex, and this method of pre-built test procedures often fails to fully simulate real user usage, resulting in inaccurate test results. Summary of the Invention

[0004] One object of this application is to provide a reliability testing method, device, and computer-readable medium for a cloud management platform.

[0005] To achieve the above objectives, this application provides a reliability testing method for a cloud management platform, the method comprising:

[0006] Randomly select one operation from the operation set file as the current test operation. The operation set file includes all operations involved in the cloud management platform.

[0007] Based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution;

[0008] Based on the execution parameters, the corresponding interface is called to actually execute the test operation;

[0009] If the actual execution is successful and the actual execution result meets the expected result, randomly select an operation from the operation set file again as the current test operation and continue testing until the target duration of the reliability test is reached. Record the target duration as the fault-free running time of this test.

[0010] If the actual execution fails, or if the actual execution succeeds but the result does not meet expectations, an error message is generated and the fault-free runtime is recorded.

[0011] The reliability test results are determined based on the fault-free operating time.

[0012] Furthermore, before simulating the execution of the test operation based on the resources required by the test operation and obtaining the execution parameters required during actual execution, the process also includes:

[0013] The test environment is pre-processed according to the pre-processing conditions corresponding to the test operation.

[0014] Furthermore, the method also includes:

[0015] Configure the pre-processing conditions corresponding to each operation in the pre-processing file in advance;

[0016] After selecting a test operation, the pre-processing conditions corresponding to the test operation are determined from the pre-processing file.

[0017] Furthermore, based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution, including:

[0018] Select the resources required for the test operation from the resource file containing the custom resource classes;

[0019] Based on the selected resources, simulate the execution of test operations to obtain the execution parameters required for actual execution.

[0020] Furthermore, based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution, including:

[0021] Based on the resources required for the test operation, the execution of the test operation is simulated. If the simulation fails, fault information is generated and the fault-free runtime is recorded. If the simulation succeeds, the execution parameters required for actual execution are obtained.

[0022] Furthermore, the method also includes:

[0023] If the simulation fails, the actual execution fails, or the actual execution succeeds but the actual result does not meet the expected result, a new operation is randomly selected from the operation set file as the current test operation to continue testing until the target duration of the reliability test is reached.

[0024] The average of the fault-free runtime recorded multiple times is calculated, and the reliability test results are determined based on the average of the fault-free runtime.

[0025] Furthermore, based on the execution parameters, the corresponding interface is called to actually execute the test operation, including:

[0026] Based on the operation name and corresponding execution parameters of the test operation, the corresponding interface is called in the mechanical operation file, and the test operation is actually executed with the execution parameters.

[0027] Furthermore, the method also includes:

[0028] All operations involved in this reliability test of the cloud management platform are written into the operation set file in advance.

[0029] Based on another aspect of this application, a reliability testing device for a cloud management platform is also provided. The device includes a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein when the computer program instructions are executed by the processor, the device is triggered to execute the reliability testing method of the cloud management platform.

[0030] This application also provides a computer-readable medium storing computer program instructions that can be executed by a processor to implement the reliability testing method for the cloud management platform.

[0031] Compared with existing technologies, this application provides a reliability testing scheme for a cloud management platform. This scheme randomly selects an operation from an operation set file (which includes all operations involved in the cloud management platform) as the current test operation. Based on the resources required for the test operation, it simulates the execution of the test operation and obtains the execution parameters needed for actual execution. According to the execution parameters, it calls the corresponding interface to actually execute the test operation. If the actual execution is successful and the result meets expectations, it randomly selects another operation from the operation set file as the current test operation to continue testing until the target duration of the reliability test is reached. The target duration is recorded as the fault-free runtime for this test. If the actual execution fails, or if the actual execution is successful but the result does not meet expectations, an error message is generated, and the fault-free runtime for this test is recorded. The reliability test result is determined based on the fault-free runtime. Since in the test task, as long as an operation is executed successfully and meets the expected result, another operation will be randomly selected from all operations to continue execution, theoretically all operation combinations can be constructed to avoid missing any real-world usage scenarios in the test. At the same time, when the test operation fails, the reliability of the cloud management platform can be accurately quantified by recording the fault-free runtime. Attached Figure Description

[0032] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0033] Figure 1 This is a test execution flowchart of a reliability testing method for a cloud management platform according to an embodiment of this application;

[0034] Figure 2 This is a test execution flowchart of a reliability testing method for another cloud management platform in this application embodiment;

[0035] The same or similar reference numerals in the accompanying drawings represent the same or similar parts. Detailed Implementation

[0036] The present application will now be described in further detail with reference to the accompanying drawings.

[0037] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, 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.

[0038] In a typical configuration of this application, the terminal and the service network devices each include one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0039] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0040] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only optical disc (CD-ROM), digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0041] This application provides a reliability testing method for a cloud management platform. The method executes test tasks cyclically until the target duration of the reliability test is reached. Then, the reliability test result is determined based on the fault-free runtime recorded during the execution process. Since as long as an operation in the test task is executed successfully and meets the expected result, another operation will be randomly selected from all operations to continue execution, theoretically all operation combinations can be constructed, avoiding the omission of any real-world usage scenarios in the test. At the same time, when an operation fails, the reliability of the cloud management platform can be accurately quantified by recording the fault-free runtime.

[0042] In practical scenarios, the executing entity of the method may include user equipment, network equipment, or a device composed of user equipment and network equipment integrated through a network, or it may be an application running on the aforementioned devices. The user equipment includes, but is not limited to, various terminal devices such as computers, mobile phones, and tablets; the network equipment includes, but is not limited to, network hosts, single network servers, servers aggregated from multiple network servers, or servers in a distributed cloud network. Here, the distributed cloud network consists of a large number of hosts or network servers based on cloud computing.

[0043] This application provides a reliability testing method for a cloud management platform, the execution flow of which is as follows: Figure 1 As shown, the processing steps include the following:

[0044] Step S101: Randomly select an operation from the operation set file as the current test operation. The operation set file includes all operations involved in the cloud management platform. For example, in this embodiment, the operation set file can be a function file, which may include at least operations such as creating a virtual machine, starting a virtual machine, stopping a virtual machine, creating a backup, creating an image, and creating a snapshot. These operations are all operations that the cloud management platform may need to perform during actual operation.

[0045] In practical scenarios, all operations involved in the cloud management platform during the reliability test can be pre-written into an operation set file beforehand. Therefore, when the test task begins, any operation can be randomly selected from the operation set file as the current test operation. For example, in this embodiment, stopping the virtual machine can be selected as the current test operation.

[0046] Step S103: Based on the resources required for the test operation, simulate the execution of the test operation and obtain the execution parameters required for actual execution.

[0047] In real-world business scenarios, cloud management platforms utilize real resources within the cloud environment for various operations. However, using real resources in testing scenarios could lead to numerous test operations failing to meet expectations, resulting in a large number of test errors. To avoid this, this solution does not use real resources from the cloud environment for the resources required by the current test operation. Instead, it selects the resources needed for the test operation from a resource file of a custom resource class. Then, it simulates the execution of the test operation based on the selected resources to ensure that the simulated execution results meet expectations as much as possible, thereby obtaining the execution parameters required for actual execution. For example, in this embodiment, the resource file can be a resource file, which can define different resource classes such as virtual machines, cloud disks, snapshots, and images. When simulating the execution of a test operation, the resources required for the test operation can be selected from the resource file. Taking the backup creation operation as an example, the required resource is a virtual machine.

[0048] The expected result refers to the desired execution outcome of each operation performed during normal operation of the cloud management platform. Taking the virtual machine creation operation as an example, a satisfactory result means the virtual machine is successfully created and running, while an unsatisfactory result means the virtual machine is not successfully created, or the virtual machine is created but stopped due to some factors. The execution parameters are the parameters required when each operation is actually executed by calling the interface. For example, taking the backup creation operation as an example, the corresponding execution parameters may include the name of the virtual machine and the backup method.

[0049] When the simulation result meets the expected result, the obtained execution parameters can be used for the actual execution process of subsequent interface calls. Therefore, when simulating the execution of the test operation based on the resources required by the test operation, the judgment process in step S104 can be executed: if the simulation execution fails, it means that the test task in this round has failed, and an error message can be generated to report the error, while recording the fault-free runtime. If the simulation execution is successful, the execution parameters required for actual execution are obtained, and the subsequent steps in the test task continue.

[0050] Step S105: Based on the execution parameters, call the corresponding interface to actually execute the test operation. Since the execution parameters required for actual execution have been obtained through simulation in the previous step, it can be ensured that the execution results obtained during actual execution meet the expected results as much as possible, making the test results more consistent with the actual business scenario.

[0051] In some embodiments of this application, the interfaces that need to be called during actual execution can be pre-written into a machine operation file, which is a method library for calling interfaces. For example, in this embodiment, the machine operation file can be a robot_action file. Based on the execution parameters returned by the resource file, the execution parameters required by the corresponding interface will be configured in this robot_action file, and then called to actually execute the test operation.

[0052] In real-world testing scenarios, although appropriate execution parameters are pre-obtained through simulation to ensure the operation's results meet expectations, various factors can still lead to execution failures or results that do not meet expectations. For example, in a test operation to create a virtual machine, creation might fail due to a network disconnection or physical machine downtime, causing the test operation to fail. Another example is where the virtual machine is successfully created, but remains in a stopped state due to certain factors, while the expected result is a running virtual machine. This situation exemplifies a successful test operation with a result that does not meet expectations.

[0053] Therefore, for the actual execution of the test operation via the corresponding interface, there will be at least three different outcomes: actual execution failure, actual execution success but the actual execution result not meeting expectations, and actual execution success and the actual execution result meeting expectations. Based on these different outcomes, the branch judgment in step S106 can be executed as follows:

[0054] If the actual execution is successful and the actual execution result meets the expected result, an operation is randomly selected from the operation set file as the current test operation to continue testing. This causes the processing flow to return to step S101 to continue testing. This cycle continues until the target duration of the reliability test is reached. At this point, the target duration can be recorded as the fault-free runtime for this test. The target duration can be determined based on the indicators required for the actual test. For example, in this embodiment, the target duration can be set to a fixed value, such as 7×24 hours. Alternatively, the target duration can be set to a dynamic value, such as dynamically increasing with the current test time. After the test time reaches the initial target duration, the target duration value is increased one or more times. If the actual execution fails, or if the actual execution is successful but the result does not meet the expected result, an error message is generated to report the error, and the fault-free runtime for this test is recorded.

[0055] Once the target runtime is reached or an error is reported, the test can be terminated. At this point, the reliability test result is determined based on the fault-free runtime. A longer fault-free runtime indicates higher reliability, and vice versa.

[0056] In real-world scenarios, when an error message is generated during testing, the test can continue from step S101 without terminating. This allows for the recording of multiple fault-free runtimes, and the average of these fault-free runtimes is used to evaluate the reliability test results. Therefore, the method may further include:

[0057] If the simulated execution fails, the actual execution fails, or the actual execution succeeds but the result does not meet expectations, a new operation is randomly selected from the operation set file as the current test operation to continue testing until the target duration of the reliability test is reached. The average of the recorded fault-free runtimes is calculated, and the reliability test result is determined based on this average. For example, in this embodiment, during the process from the start of the test to reaching the target duration of the reliability test, a total of 3 errors occurred. The time from the start of the test to the first error is t1, the time from the first error to the second error is t2, the time from the second error to the third error is t3, and the time from the third error to reaching the target duration is t4. Therefore, this test can record 4 fault-free runtimes, namely t1, t2, t3, and t4. By calculating the average of these 4 fault-free runtimes, the reliability test result can be quantitatively reflected; that is, the larger the average, the higher the reliability, and vice versa.

[0058] Because the test scheme in this application selects each test operation randomly, and the order of these test operations is logically unrelated, a single execution operation may fail due to the inability to meet the preconditions. For example, to correctly execute operations such as creating a backup, stopping a virtual machine, or restarting a virtual machine, the prerequisite is that a running virtual machine is required. If there is no virtual machine or the virtual machine is stopped, the operation will fail.

[0059] To address this issue, this application embodiment also provides a reliability testing method. In addition to the aforementioned processing steps, this method can further perform step S102 before simulating the execution of the test operation based on the resources required for the test operation and obtaining the execution parameters needed for actual execution. Specifically, it performs pre-processing on the test environment according to the pre-processing conditions corresponding to the test operation. For example, taking the aforementioned backup creation operation as an example, if backup creation is randomly selected as the test operation, pre-processing can be performed before simulation execution, such as starting a stopped virtual machine or creating a new virtual machine, thereby ensuring that the current test environment meets the pre-conditions for the test operation.

[0060] In this method, the pre-processing conditions corresponding to each operation are pre-configured in a pre-processing file. This allows the pre-processing conditions for each operation to be configured in the pre-processing file beforehand. Then, after selecting a test operation, the pre-processing conditions corresponding to that test operation are determined from the pre-processing file, thus pre-processing the test environment before executing the test operation. For example, in this embodiment, the pre-processing file can be an action file. Before testing, the pre-processing conditions corresponding to each different test can be pre-written into this action file. When a test operation is randomly selected, the corresponding pre-processing is executed through the action file.

[0061] Therefore, this solution can simulate any usage scenario of a user in a real business scenario by randomly selecting options, which makes the test more accurate. At the same time, through pre-processing and simulation execution, it can ensure that each test operation can be executed successfully and meet the expected results, thus ensuring the smooth progress of the test and enabling the test results to better reflect the actual situation of the business scenario.

[0062] Based on the same inventive concept, this application also provides a reliability testing device for a cloud management platform. The method corresponding to this device is the reliability testing method for the cloud management platform in the aforementioned embodiments, and its problem-solving principle is similar to that of the method. The reliability testing device for the cloud management platform provided in this application includes a memory for storing computer program instructions and a processor for executing the computer program instructions. When the computer program instructions are executed by the processor, the device is triggered to implement the methods and / or technical solutions of the aforementioned embodiments of this application.

[0063] The specific implementation of the device may include user equipment, network equipment, or a device composed of user equipment and network equipment integrated through a network, or it may be an application running on the aforementioned device. The user equipment includes, but is not limited to, various terminal devices such as computers, mobile phones, and tablets; the network equipment includes, but is not limited to, network hosts, single network servers, servers aggregated from multiple network servers, or servers in a distributed cloud network. Here, the distributed cloud network consists of a large number of hosts or network servers based on cloud computing.

[0064] In particular, the methods and / or embodiments in this application can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. When the computer program is executed by a processing unit, it performs the functions defined in the methods of this application.

[0065] It should be noted that the computer-readable medium described in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0066] In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wireline, optical fiber, RF, etc., or any suitable combination thereof.

[0067] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0068] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-specific system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0069] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The aforementioned computer-readable medium carries one or more computer program instructions, which may be executed by a processor to implement the methods and / or technical solutions of the various embodiments of this application.

[0070] It should be noted that this application can be implemented in software and / or a combination of software and hardware, for example, using an application-specific integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device. In some embodiments, the software program of this application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of this application (including related data structures) can be stored in a computer-readable recording medium, such as RAM memory, a magnetic or optical drive, a floppy disk, or similar devices. Furthermore, some steps or functions of this application can be implemented in hardware, for example, as circuitry that cooperates with a processor to perform the various steps or functions.

[0071] It will be apparent to those skilled in the art that this application is not limited to the details of the exemplary embodiments described above, and that this application can be implemented in other specific forms without departing from the spirit or essential characteristics of this application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within this application. No reference numerals in the claims should be construed as limiting the scope of the claims. Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in the apparatus claims may also be implemented by a single unit or device through software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any specific order. The numerical order of the sequence numbers corresponding to the steps does not indicate any specific execution order; the steps may be executed in any combination of orders provided that the execution logic is met.

Claims

1. A reliability testing method for a cloud management platform, characterized in that, The method includes: Randomly select one operation from the operation set file as the current test operation. The operation set file includes all operations involved in the cloud management platform. Based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution; Based on the execution parameters, the corresponding interface is called to actually execute the test operation; If the actual execution is successful and the actual execution result meets the expected result, randomly select an operation from the operation set file again as the current test operation and continue testing until the target duration of the reliability test is reached. Record the target duration as the fault-free running time of this test. If the actual execution fails, or if the actual execution succeeds but the result does not meet expectations, an error message is generated and the fault-free runtime is recorded. The reliability test results are determined based on the fault-free operating time.

2. The method according to claim 1, characterized in that, Before simulating the execution of the test operation based on the resources required for the test operation and obtaining the execution parameters required for actual execution, the process also includes: The test environment is pre-processed according to the pre-processing conditions corresponding to the test operation.

3. The method according to claim 2, characterized in that, The method further includes: Configure the pre-processing conditions corresponding to each operation in the pre-processing file in advance; After selecting a test operation, the pre-processing conditions corresponding to the test operation are determined from the pre-processing file.

4. The method according to claim 1, characterized in that, Based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution, including: Select the resources required for the test operation from the resource file containing the custom resource classes; Based on the selected resources, simulate the execution of test operations to obtain the execution parameters required for actual execution.

5. The method according to claim 1, characterized in that, Based on the resources required for the test operation, the execution of the test operation is simulated to obtain the execution parameters required during actual execution, including: Based on the resources required for the test operation, the execution of the test operation is simulated. If the simulation fails, fault information is generated and the fault-free runtime is recorded. If the simulation succeeds, the execution parameters required for actual execution are obtained.

6. The method according to claim 5, characterized in that, The method further includes: If the simulation fails, the actual execution fails, or the actual execution succeeds but the actual result does not meet the expected result, a new operation is randomly selected from the operation set file as the current test operation to continue testing until the target duration of the reliability test is reached. The average of the fault-free runtime recorded multiple times is calculated, and the reliability test results are determined based on the average of the fault-free runtime.

7. The method according to claim 1, characterized in that, Based on the execution parameters, the corresponding interface is called to actually execute the test operation, including: Based on the operation name and corresponding execution parameters of the test operation, the corresponding interface is called in the mechanical operation file, and the test operation is actually executed with the execution parameters.

8. The method according to claim 1, characterized in that, The method further includes: All operations involved in this reliability test of the cloud management platform are written into the operation set file in advance.

9. A reliability testing device for a cloud management platform, the device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein, When the computer program instructions are executed by the processor, the device is triggered to perform the method of any one of claims 1 to 8.

10. A computer-readable medium having stored thereon computer program instructions that can be executed by a processor to implement the method as described in any one of claims 1 to 8.

Images