File updating method and device in redundant environment and electronic equipment

Abstract

According to the file updating method in the redundant environment, the redundant environment in the method can comprise a master module and a slave module which have a master-slave relation, and the method is applied to the slave module. The method can comprise the steps that a slave module determines whether a slave module file needs to be updated or not according to the consistency of master module file information and slave module file information, then the slave module obtains an update file from a master module and generates updated slave module file information, and after it is determined that the slave module file information is consistent with the master module file information, the slave module file information is updated. And the slave module performs updating according to the updated file. According to the method provided by the invention, the slave module can take the master module as a data source to automatically update the file and take effect of loading, so that the file updating safety and efficiency of the slave module are ensured, and the reliability of a redundant environment can be ensured.

Description

Technical Field

[0001] The present application relates to the field of file updating, and in particular to a file updating method, device and electronic device in a redundant environment. Background Art

[0002] In the field of industrial control, redundant devices are widely used to ensure the stability and reliability of the system. The inventor of this application found that the two common file synchronization strategies in the redundant environment have shortcomings, including

[0003] (1) Manual update between the master and slave modules. This method uses manual operation to keep the files of the master and slave modules synchronized, but has the disadvantages of cumbersome operation and low reliability of redundant systems.

[0004] (2) The master and slave modules automatically synchronize the file data in the memory, and the loading and taking effect of the files that need to be restarted is done manually. This method has the disadvantages of a long loading and taking effect time, slow file taking effect, and a single type of files that are automatically updated. Summary of the invention

[0005] According to the first aspect of the present application, a file update method in a redundant environment is proposed, wherein the redundant environment in the method may include a master module and a slave module having a master-slave relationship, and the method is applied to the slave module and may include the following steps: when the slave module meets the verification update conditions, sending an information acquisition request to the master module; receiving the master module file information sent by the master module; when the master module file information and the first slave module file information are inconsistent, sending a file acquisition request to the master module; receiving an update file set sent by the master module; obtaining the second slave module file information according to the update file set; and when the master module file information and the second slave module information are consistent, updating according to the update file set.

[0006] According to the above implementation, in the method proposed in the present application, the slave module determines whether the slave module file needs to be updated based on the consistency of the master module file information and the slave module file information, and then the slave module obtains the update file from the master module and generates the updated slave module file information. After determining that the slave module file information is consistent with the master module file information, the slave module is updated according to the updated file. According to the method proposed in the present application, the slave module can use the master module as a data source, automatically update files and load them to take effect, ensure the safety and efficiency of the slave module file update, and thus ensure the reliability of the redundant environment.

[0007] According to some embodiments, verifying the update condition may include: the slave module is in a power-on startup phase; or the slave module receives a file change signal sent by the master module.

[0008] According to the above implementation, the method of the present application sets the verification update condition to the slave module being in the power-on startup phase or the slave module receiving a file change signal sent by the master module, wherein the slave module in the power-on startup phase includes the situation where a new slave module is added to the redundant environment and the situation where the redundant environment is restarted. The verification update condition of the present application can cover all situations where the slave module needs to be updated, ensuring the reliability of the update.

[0009] According to some embodiments, the method of the first aspect of the present application may also include: when the file information of the main module is consistent with the file information of the first slave module, filtering the ineffective files in the existing files of the slave module as the second file set; loading the files in the second file set to complete the file update.

[0010] According to the above implementation, the method proposed in the present application verifies the consistency of the main module file information and the slave module file information when the verification update conditions are met, and loads the ineffective files in the slave module file when there is consistency, thereby ensuring the correct effectiveness of files that require restart to take effect.

[0011] According to the second aspect of the present application, a file updating device in a redundant environment is proposed, and the device may include: a sending module, which can be used to send an information acquisition request to the main module when the verification update condition is met, and send a file acquisition request to the main module when the main module file information and the first slave module file information are inconsistent; a receiving module, which can be used to receive the main module file information sent by the main module, and receive the update file set sent by the main module; a processing module, which can be used to obtain the second slave module file information according to the update file set, and update according to the update file set when the main module file information and the second slave module information are consistent.

[0012] According to the third aspect of the present application, a file update system in a redundant environment is proposed, which system may include: a main module, which can be used to receive information acquisition requests and file acquisition requests sent by a slave module, and send the main module file information and update file set to the slave module; the slave module can be used to execute the method described in the first aspect of the present application.

[0013] According to the fourth aspect of the present application, an electronic device is proposed, which may include: a processor; and a memory storing a computer program, wherein when the computer program is executed by the processor, the processor executes the method described in the first aspect of the present application.

[0014] According to the fifth aspect of the present application, a non-transitory computer-readable storage medium is provided, on which computer-readable instructions are stored. When the instructions are executed by a processor, the processor executes the method described in the first aspect of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without exceeding the scope of protection required by the present application.

[0016] Figure 1 It is a structural diagram of a file updating system 1000 in a redundant environment of the present application;

[0017] Figure 2 A schematic diagram of the steps of the file updating method 2000 in a redundant environment of the present application;

[0018] Figure 3 This is a schematic diagram of step S106-A in the method 2000 of the present application;

[0019] Figure 4 This is a schematic diagram of step S106-B in the method 2000 of the present application;

[0020] Figure 5 A schematic diagram of the steps of a file updating method 3000 in a redundant environment of the present application;

[0021] Figure 6 It is a structural diagram of a file updating device 4000 in a redundant environment of the present application;

[0022] Figure 7 A schematic diagram of a specific embodiment 5000 of the file update method in a redundant environment of the present application;

[0023] Figure 8 This is a structural diagram of an electronic device of the present application.

[0024] Description of reference numerals:

[0025] File update system in redundant environment-1000; master module-101; slave module-102;

[0026] File updating device in redundant environment-4000; receiving module-401; processing module-402; sending module-403;

[0027] Embodiment-5000; master module-501; slave module-502. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0029] Figure 1 FIG. 1 is a schematic diagram of the structure of the file update system 1000 in the redundant environment of the present application. Figure 1 As shown, the system 1000 includes a master module 101 and a slave module 102 .

[0030] In some specific embodiments, the system 1000 is applied to a SIS (Safety Instrumented System) to improve the hardware fault margin of the system and ensure that a single fault will not cause the loss of the SIS safety function. In some specific embodiments, the types of files loaded and validated in the master module 101 and the slave module 102 include files that require restart and files that do not require restart. Among them, after the files are stored, the system needs to be powered off and restarted to load and take effect. Files that do not require restart can be directly loaded and taken effect after being stored.

[0031] In some specific embodiments, in the system 1000, the files in the master module 101 and the slave module 102 need to be consistent. In the system 1000, the master module 101 and the slave module 102 can perform data communication, such as exchanging messages or files. Optionally, the master module 101 and the slave module 102 perform data communication via a wired backplane base. In some specific embodiments, the master module 101 and the slave module 102 perform data communication via a wireless communication module.

[0032] Figure 2 FIG. 2 is a schematic diagram of the steps of the file update method 2000 in the redundant environment of the present application. Figure 2 As shown, method 2000 includes steps S201 to S206.

[0033] In some specific embodiments, in step S201, when the verification update condition is met, the file update device in the redundant environment (such as a slave module in the redundant environment, which is described below using the slave module as an example) sends an information acquisition request to the master module.

[0034] In some specific embodiments, in step S201, verifying the update condition includes that the slave module is in the power-on startup phase. In some specific embodiments, the slave module is in the power-on startup phase including that the slave module is added to a redundant environment, and the slave module does not include files, and at this time the slave module needs to synchronize files with the master module. In some specific embodiments, the slave module is in the power-on startup phase including that the master-slave module in the redundant environment is restarted, and at this time there are files that have been stored but not loaded and taken effect in the slave module, and at this time the slave module needs to synchronize files with the master module again to ensure the validity of the slave module update.

[0035] In some specific embodiments, in step S201, verifying the update condition includes receiving a file change signal sent by the master module from the slave module. In some specific embodiments, the file change signal indicates that a file of the master module in the redundant environment has changed, and the slave module needs to synchronize files with the master module.

[0036] In some specific embodiments, in step S201, the slave module satisfies the verification update condition, and the slave module sends an information acquisition request to the master module to obtain the master module file information in the master module.

[0037] In step S202, the slave module receives the master module file information sent by the master module. In some specific embodiments, the master module file information in step S202 includes file identification information of the file in the master module, such as a file verification code.

[0038] In step S203, when the file information of the master module is inconsistent with the file information of the first slave module, the slave module sends a file acquisition request to the master module.

[0039] In some specific embodiments, in step S203, the master module file information is inconsistent with the first slave module file information, indicating that there is a difference between the existing file in the slave module and the file in the master module, and the slave module sends a file acquisition request to the master module to obtain the file that needs to be updated in the slave module. Optionally, the master module file information and the slave module file information include a file checksum.

[0040] In step S204, the slave module receives the update file set sent by the master module.

[0041] In some specific embodiments, in step S204, the update file set includes files that need to be updated from the module. Optionally, the files in the update file set include files that require restart to take effect and / or files that can take effect without restarting.

[0042] In step S205, the slave module obtains the second slave module file information according to the update file set. In some specific embodiments, after the slave module receives the update file set sent by the master module, the second slave module file information is obtained according to all files included in the slave module itself (including files in the newly received update file set).

[0043] In step S206, when the master module file information and the second slave module file information are consistent, the slave module is updated according to the update file set. In some specific embodiments, in step S206, the master module file information and the second slave module file information are consistent, indicating that the files in the updated slave module and the files in the master module have completed file synchronization, but at this time, the files in the update file set of the slave module have not been loaded and taken effect. In some specific embodiments, in step S206, the slave module confirms that the second slave module file information is consistent with the master module file information, and then updates according to the update file set.

[0044] In some specific embodiments, in step S206, there are files in the update file set that require a restart to take effect, the slave module filters the files in the update file set that can take effect without a restart to form a first file set, and then loads the files in the first file set and restarts the slave module. In some specific embodiments, in step S206, there are no files in the update file set that require a restart to take effect, and the slave module loads the files in the update file set to complete the file update.

[0045] In the method proposed in the present application, the slave module determines whether the slave module file needs to be updated based on the consistency of the master module file information and the slave module file information, then the slave module obtains the update file from the master module and generates the updated slave module file information, after determining that the slave module file information is consistent with the master module file information, the slave module is updated according to the updated file. According to the method proposed in the present application, the slave module can use the master module as a data source, automatically update files and load them to take effect, ensure the safety and efficiency of the slave module file update, and thus ensure the reliability of the redundant environment.

[0046] Figure 3 Schematic diagram of step S206-A in method 2000 of the present application. Figure 3 As shown, step S206-A includes steps S601 and S602.

[0047] In step S601, the slave module determines whether there is a file in the update file set that requires a reboot to take effect. In some specific embodiments, in step S601, the slave module determines for each file in the update file set whether the file is a file that can take effect without a reboot or a file that requires a reboot to take effect based on the content of the file.

[0048] In step S602, if there is no file in the update file set that requires restart to take effect, the file in the update file set is loaded from the module to complete the file update. In some specific embodiments, in step S602, all files in the update file set are files that can take effect without restarting, and at this time, the file in the update file set is loaded from the module to complete the file update.

[0049] Figure 4 Schematic diagram of step S206-B in method 2000 of the present application. Figure 4 As shown, step S206-B includes steps S611 to S613, wherein steps S611 and Figure 3 The same as step S601 in the above description, which will not be repeated here.

[0050] In step S612, if there are files in the update file set that require a restart to take effect, the slave module filters the first file set in the update file set that can take effect without a restart. In some specific embodiments, in step S612, the update file set includes files that require a restart to take effect and files that can take effect without a restart. At this time, the slave module filters out the files that can take effect without a restart to form the first file set, so as to complete the update of the files that can take effect without a restart.

[0051] In step S613, the slave module loads the files in the first file set and restarts the slave module. In some specific embodiments, in step S613, the slave module loads the files in the first file set to complete the update of the files that can take effect without restarting. In some specific embodiments, in step S613, after loading the files in the first file set, the file update is not completed, and the slave module needs to be restarted at this time to complete the update of the files in the update file set that need to be restarted to take effect.

[0052] Figure 5 FIG. 3 is a schematic diagram of the steps of the file update method 3000 in the redundant environment of the present application. Figure 5 As shown, method 3000 includes steps S301 to S308, wherein steps S301 to S306 and Figure 2 Steps S201 to S206 of method 2000 are the same and will not be repeated here.

[0053] In step S307, when the file information of the master module is consistent with the file information of the first slave module, the slave module filters the ineffective files in the existing files of the slave module as the second file set. In some specific embodiments, in step S307, the file information of the master module is consistent with the file information of the first slave module, indicating that the slave module at this time is neither newly added to the redundant environment nor has just received the file update signal of the master module, that is, the verification update condition satisfied by the slave module at this time is that the slave module has just completed restarting.

[0054] In some specific embodiments, in step S307, the slave module has just completed restarting, and before the restart, the slave module includes files that have been stored but not updated, that is, files that need to be restarted to take effect. In some specific embodiments, in step S307, the slave module filters the ineffective files from the existing files as the second file set, wherein the second file set includes files that have been stored but not updated by the slave module before the restart.

[0055] In step S308, files in the second file set are loaded from the module to complete the file update. In some specific embodiments, in step S308, files in the second file set are loaded from the module, that is, the update of files that require restart to take effect is completed. Since the update of files that can take effect without restart has been completed before the restart, all file updates are completed in step S308.

[0056] Figure 6 FIG. 4 is a schematic diagram of the structure of the file updating device 4000 in the redundant environment of the present application. Figure 6 As shown, the device 4000 includes a receiving module 401 , a processing module 402 and a sending module 403 .

[0057] In some specific embodiments, when the verification update condition is met, the sending module 403 sends an information acquisition request to the main module.

[0058] In some specific embodiments, the verification update condition includes that the slave module is in the power-on startup phase. In some specific embodiments, the slave module is in the power-on startup phase including that the slave module is added to a redundant environment, and the slave module does not include files, and at this time the slave module needs to synchronize files with the master module. In some specific embodiments, the slave module is in the power-on startup phase including that the master-slave module in the redundant environment is restarted, and at this time there are files that have been stored but not loaded and taken effect in the slave module, and at this time the slave module needs to synchronize files with the master module again to ensure the validity of the slave module update.

[0059] In some specific embodiments, verifying the update condition includes receiving a file change signal sent by the master module from the slave module. In some specific embodiments, the file change signal indicates that a file of the master module in the redundant environment has changed, and the slave module needs to synchronize files with the master module.

[0060] In some specific embodiments, if the slave module meets the verification update condition, the sending module 403 sends an information acquisition request to the master module to obtain the master module file information in the master module.

[0061] In some specific embodiments, the receiving module 401 receives the main module file information sent by the main module. In some specific embodiments, the main module file information includes file identification information of the file in the main module, such as a checksum of the file.

[0062] In some specific embodiments, when the file information of the master module is inconsistent with the file information of the first slave module, the sending module 403 sends a file acquisition request to the master module.

[0063] In some specific embodiments, the master module file information is inconsistent with the first slave module file information, indicating that there is a difference between the existing file in the slave module and the file in the master module. At this time, the sending module 403 sends a file acquisition request to the master module to obtain the file that needs to be updated in the slave module. Optionally, the master module file information and the slave module file information include a file check code.

[0064] In some specific embodiments, the receiving module 401 receives the update file set sent by the main module.

[0065] In some specific embodiments, the update file set includes files that need to be updated from the module. Optionally, the files in the update file set include files that require restart to take effect and / or files that can take effect without restarting.

[0066] In some specific embodiments, the processing module 402 obtains the second slave module file information according to the update file set. In some specific embodiments, after the receiving module 401 receives the update file set sent by the master module, the processing module 402 obtains the second slave module file information according to all files included in the slave module itself (including files in the newly received update file set).

[0067] In some specific embodiments, when the master module file information and the second slave module file information are consistent, the processing module 402 performs updating according to the update file set. In some specific embodiments, the master module file information and the second slave module file information are consistent, indicating that the files in the updated slave module and the files in the master module have completed file synchronization, but at this time, the files in the update file set of the slave module have not been loaded and taken effect. In some specific embodiments, the processing module 402 confirms that the second slave module file information is consistent with the master module file information, and then performs updating according to the update file set.

[0068] In some specific embodiments, there are files in the update file set that require a restart to take effect, and the processing module 402 selects the files in the update file set that can take effect without a restart to form a first file set, and then loads the files in the first file set and restarts the slave module. In some specific embodiments, there are no files in the update file set that require a restart to take effect, and the processing module 402 loads the files in the update file set to complete the file update.

[0069] Figure 7 FIG. 5 is a schematic diagram of a specific embodiment 5000 of the file update method in a redundant environment of the present application. Figure 7 As shown, the embodiment 5000 includes a master module 501 and a slave module 502 .

[0070] exist Figure 7 In the embodiment 5000 shown, the files in the main module 501 have changed, including updating the original file 1 to file 1' and adding file 4, wherein file 1' is a file that can take effect without restarting, and file 4 is a file that needs to be restarted to take effect. The main module 501 sends a file update signal to the slave module 502. After receiving the file update signal, the slave module 502 sends an information acquisition request to the main module 501. In response to the information acquisition request, the main module 501 sends the main module file information to the slave module 501. In the embodiment 5000, the main module file information in the main module 501 includes {(file 1': no ​​restart required), (file 2: restart required), (file 3: no restart required), (file 4: restart required)}.

[0071] In the embodiment 5000, the first slave module file information in the slave module 502 includes {(file 1: no restart required), (file 2: restart required), (file 3: restart required)}. The slave module 502 compares the master module file information with the first slave module file information, and finds that the two are inconsistent, and the slave module 502 sends a file acquisition request to the master module 501. In the embodiment 5000, the file acquisition request includes the inconsistent part of the master module file information and the first slave module file information, that is, {(file 1': no ​​restart required), (file 4: restart required)}. In response to the file acquisition request, the master module 501 sends file 1' and file 4 to the slave module 502. The slave module 502 forms an update file set with the received file 1' and file 4.

[0072] The slave module 502 determines the second slave module file information according to the update file set as: {(file 1': no ​​restart required), (file 2: restart required), (file 3: no restart required), (file 4: restart required). In the embodiment 5000, the second slave module file information is consistent with the master module file information, and the slave module 502 is updated according to the update file set.

[0073] In embodiment 5000, slave module 502 determines that there are files in the update file set that require restart to take effect, and selects files in the update file that can take effect without restart, that is, file 1'. In embodiment 5000, slave module 502 loads file 1' and restarts.

[0074] After the slave module 502 completes the restart, the verification and update condition of the slave module in the power-on startup phase is met at this time, and the slave module 502 starts the file update, and obtains the main module file information of the main module 501 again. At this time, the first slave module file information is the information of the files currently included in the slave module 502, that is, {(file 1': no ​​restart is required), (file 2: restart is required), (file 3: no restart is required), (file 4: restart is required), and the first slave module file information is consistent with the main module file information. In embodiment 5000, the slave module 502 filters the file that is not effective in the existing files of the slave module, that is, file 4, and loads file 4 to complete the file update.

[0075] Figure 8 The present application provides a structural diagram of an electronic device, including a processor and a memory. The memory stores computer instructions. When the computer instructions are executed by the processor, the processor executes the computer instructions to achieve the following Figure 2 The method and refinement scheme shown.

[0076] It should be understood that the above device embodiments are only illustrative, and the device disclosed in the present invention can also be implemented in other ways. For example, the division of units / modules described in the above embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0077] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present invention may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0078] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor or chip may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the on-chip cache, the off-chip memory, and the memory may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0079] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0080] The present application also provides a non-transitory computer storage medium storing a computer program. When the computer program is executed by a plurality of processors, the processors execute the following Figure 2 The method and refinement scheme shown.

[0081] The embodiments of the present application are described in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and its core idea of ​​the present application. At the same time, changes or deformations made by those skilled in the art based on the ideas of the present application, the specific implementation methods and the scope of application of the present application, all belong to the scope of protection of the present application. In summary, the content of this specification should not be construed as a limitation on the present application.

Claims

1. A file updating method in a redundant environment, wherein the redundant environment comprises a master module and a slave module in a master-slave relationship, wherein the method is applied to the slave module. It is characterized in that include: When the slave module meets the verification and update conditions, sending an information acquisition request to the master module; Receiving main module file information sent by the main module; When the file information of the master module is inconsistent with the file information of the first slave module, sending a file acquisition request to the master module; Receiving an update file set sent by the main module; Obtaining second slave module file information according to the update file set; When the master module file information is consistent with the second slave module file information, updating is performed according to the update file set.

2. The method according to claim 1, It is characterized in that The verification update conditions include: The slave module is in the power-on startup phase; or The slave module receives a file change signal sent by the master module.

3. The method according to claim 2, It is characterized in that The updating according to the update file set comprises: Determine whether there is a file in the update file set that requires restart to take effect; In the case that there is no file in the update file set that requires restart to take effect, the files in the update file set are loaded to complete the file update.

4. The method according to claim 2, It is characterized in that The updating according to the update file set further comprises: If there are files in the update file set that require restart to take effect, select a first file set in the update file set that can take effect without restarting; Load the files in the first file set and restart the slave module.

5. The method according to claim 4, It is characterized in that Also includes: When the file information of the master module is consistent with the file information of the first slave module, filtering ineffective files from existing files of the slave module as a second file set; The files in the second file set are loaded to complete the file update.

6. The method according to any one of claims 1 to 5, It is characterized in that The master module file information and the slave module file information include a file check code.

7. A file updating device in a redundant environment, It is characterized in that include: A sending module, used to send an information acquisition request to the master module when the verification update condition is met, and to send a file acquisition request to the master module when the file information of the master module and the file information of the first slave module are inconsistent; A receiving module, used for receiving the main module file information sent by the main module, and receiving the update file set sent by the main module; The processing module is used to obtain the second slave module file information according to the update file set, and update according to the update file set when the master module file information is consistent with the second slave module information.

8. A file update system in a redundant environment, It is characterized in that include: A master module, configured to receive information acquisition requests and file acquisition requests sent by slave modules, and to send master module file information and update file sets to the slave modules; A slave module, configured to execute the method according to any one of claims 1-6.

9. An electronic device, It is characterized in that include: processor; A memory storing a computer program, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 6.

10. A non-transitory computer-readable storage medium, It is characterized in that Computer-readable instructions are stored thereon, and when the instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1-6.

Images