A method, system, device and storage medium for updating a financial product

Abstract

Embodiments of the present application disclose a financial project updating method, system, device and storage medium. The method comprises the following steps: obtaining a first hash value of an old version of a financial project to be updated; obtaining a second hash value of a new version of the financial project to be updated; and obtaining a file to be updated of the financial project to be updated according to the first hash value and the second hash value. Only a compiling file corresponding to the file to be updated needs to be uploaded, and all files of the financial project to be updated do not need to be uploaded, so that the time of updating and deploying is shortened, bandwidth resources required when the financial project is deployed are reduced, and the speed and efficiency of putting the financial project online are improved.

Description

[Technical Field]

[0001] This invention relates to the field of computer technology, and in particular to a method, system, device, and storage medium for updating financial projects. [Background Technology]

[0002] In the current process of updating and deploying financial projects, it is usually necessary to upload all files and resources of the new version of the financial project to the server at once for deployment, in order to replace all files and resources of the old version. Because it is necessary to upload all files and resources of the entire financial project, this full deployment method has the drawback of long update and deployment time, and full deployment consumes a lot of bandwidth resources, thus affecting the speed and efficiency of financial project launch. [Summary of the Invention]

[0003] In view of this, the present invention provides a method, system, device and storage medium for updating financial projects, so as to reduce the time required for update deployment and accelerate the speed and efficiency of financial project launch.

[0004] The specific technical solution of the first embodiment of the present invention is as follows: a method for updating a financial project, the method comprising: obtaining a first hash value of an old version of the financial project to be updated; obtaining a second hash value of a new version of the financial project to be updated; obtaining an update file of the financial project to be updated based on the first hash value and the second hash value; the update file being a difference file between the new version and the old version; performing dependency analysis on the update file using a preset open source library to obtain a dependency graph of the update file; incrementally compiling the dependency graph using a preset front-end packaging tool to obtain a compiled file of the update file; and uploading the compiled file to a preset server to complete the update of the financial project to be updated.

[0005] Preferably, obtaining the first hash value of the old version of the financial project to be updated includes: obtaining the hash value of each old branch project in the old version of the financial project to be updated, wherein the first hash value includes the hash value of each old branch project in the old version; obtaining the second hash value of the new version of the financial project to be updated includes: obtaining the hash value of each new branch project in the new version of the financial project to be updated, wherein the second hash value includes the hash value of each new branch project in the new version; obtaining the file to be updated of the financial project to be updated based on the first hash value and the second hash value includes: comparing the hash value of each old branch project and the hash value of each new branch project to obtain the file to be updated.

[0006] Preferably, the step of comparing the hash value of each old branch project with the hash value of each new branch project to obtain the file to be updated includes: if there are a first target old branch project and a first target new branch project with the same branch project name, then the hash value of the first target old branch project is compared with the hash value of the first target new branch project to obtain a first comparison result; wherein, the first comparison result includes same and different; when the first comparison result is different, then the first target update branch project is determined to be the first update file; if there is no second target old branch project with the same name as the branch project of the second target new branch project, then the second target new branch project is determined to be the second update file; if there is no third target new branch project with the same name as the branch project of the third target old branch project, then an elimination flag is generated for the third target old branch project; the elimination flag is used to instruct the preset server to delete the third target old branch project; the file to be updated includes the first update file, the second update file, and the elimination flag.

[0007] Preferably, the step of performing dependency analysis on the file to be updated using a preset open-source library to obtain a dependency graph of the file to be updated includes: performing dependency analysis on the first updated file using a preset open-source library to obtain a first dependency graph of the first updated file; performing dependency analysis on the second updated file using a preset open-source library to obtain a second dependency graph of the second updated file; performing dependency analysis on the eviction marker using a preset open-source library to obtain a third dependency graph of the eviction marker; and merging the first dependency graph, the second dependency graph, and the third dependency graph according to a preset dependency structure graph to obtain the dependency graph of the file to be updated. 。

[0008] Preferably, the method further includes: obtaining the upload progress of the compiled file to the server; and when the upload of the compiled file is interrupted, resuming the upload of the compiled file using breakpoint resume technology and the upload progress.

[0009] Preferably, obtaining the second hash value of the new version of the financial project to be updated includes: obtaining the code package of the new version of the financial project to be updated; performing a hash operation on the code package according to a preset hash algorithm to obtain the second hash value of the new version of the financial project to be updated.

[0010] Preferably, the method further includes: when the financial project to be updated is rolled back from the new version to the old version, the first hash value is used to perform a rollback operation on the financial project to be updated.

[0011] The specific technical solution of the second embodiment of the present invention is as follows: a financial project update system, comprising: a hash value acquisition module, a file to be updated acquisition module, a dependency graph acquisition module, a compiled file acquisition module, and an update module; the hash value acquisition module is used to acquire a first hash value of the old version of the financial project to be updated, and a second hash value of the new version of the financial project to be updated; the file to be updated acquisition module is used to obtain the file to be updated of the financial project to be updated based on the first hash value and the second hash value; the file to be updated is the new version of the financial project to be updated replacing all files of the old version; the dependency graph acquisition module is used to perform dependency analysis on the file to be updated using a preset open source library to obtain the dependency graph of the file to be updated; the compiled file acquisition module is used to incrementally compile the dependency graph using a preset front-end packaging tool to obtain the compiled file of the file to be updated; the update module is used to upload the compiled file to a preset server to complete the update of the financial project to be updated.

[0012] The specific technical solution of the third embodiment of the present invention is as follows: a financial project update device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method as described in any one of the first embodiments of this application.

[0013] The specific technical solution of the fourth embodiment of the present invention is as follows: a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor performs the steps of the method as described in any one of the first embodiments of this application.

[0014] Implementing this invention will have the following beneficial effects: The invention obtains a first hash value of the old version of the financial project to be updated; obtains a second hash value of the new version of the financial project to be updated; obtains the file to be updated for the financial project based on the first and second hash values; the file to be updated is the file that differentiates the new version from the old version; performs dependency analysis on the file to be updated using a preset open-source library to obtain a dependency graph of the file to be updated; incrementally compiles the dependency graph using a preset front-end packaging tool to obtain a compiled file of the file to be updated; and uploads the compiled file to a preset server to complete the update of the financial project. Since only the compiled file corresponding to the file to be updated needs to be uploaded, instead of uploading all files of the entire financial project to be updated, the update deployment time is shortened, and the bandwidth resources required for deploying the financial project are reduced, thereby accelerating the speed and efficiency of the financial project's launch. [Attached Image Description]

[0015] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A flowchart outlining the steps involved in updating methods for financial projects;

[0017] Figure 2 Flowchart of steps to obtain the file to be updated;

[0018] Figure 3 A flowchart outlining the steps to obtain the dependency graph;

[0019] Figure 4 A flowchart illustrating the steps involved in uploading compiled files using the breakpoint resume technology;

[0020] Figure 5 Flowchart of steps to obtain the second hash value of the new version;

[0021] Figure 6 A structural diagram of the update system for financial projects;

[0022] Among them, 601 is the hash value acquisition module; 602 is the file to be updated acquisition module; 603 is the dependency graph acquisition module; 604 is the compilation file acquisition module; and 605 is the update module.

Detailed Implementation Methods

[0023] 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, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0024] Please see Figure 1 This is a flowchart of a financial project update method according to the first embodiment of this application, which reduces the bandwidth resources required when deploying financial projects, thereby accelerating the speed and efficiency of financial project deployment. The method includes:

[0025] Step 101: Obtain the first hash value of the old version of the financial project to be updated;

[0026] Step 102: Obtain the second hash value of the new version of the financial project to be updated;

[0027] Step 103: Obtain the file to be updated for the financial project to be updated based on the first hash value and the second hash value; the file to be updated is the difference file between the new version and the old version;

[0028] Step 104: Perform dependency analysis on the file to be updated using a preset open-source library to obtain the dependency graph of the file to be updated;

[0029] Step 105: Use a preset front-end packaging tool to incrementally compile the dependency graph to obtain the compiled file of the file to be updated;

[0030] Step 106: Upload the compiled file to the preset server to complete the update of the financial project to be updated.

[0031] Specifically, the process involves: obtaining the first hash value of the old version of the financial project to be updated (e.g., if the old version number is v1.0.0, the first hash value is Hash1); obtaining the second hash value of the new version of the financial project to be updated (e.g., if the new version number is v2.0.0, the second hash value is Hash2); obtaining the files to be updated using Hash1 and Hash2; performing dependency analysis on the files to be updated using preset open-source libraries to obtain a dependency graph; the preset open-source libraries include any one of Jarviz Java, Jarviz graphical tools, or Jarviz CLI tools; incrementally compiling the dependency graph using preset front-end packaging tools to obtain compiled files of the files to be updated; the preset front-end packaging tools include tools such as webpack and vite; setting the entry point of the dependency graph as the entry point of the preset front-end packaging tool, which then compiles the dependency graph from the set entry point to obtain compiled files; and uploading the compiled files to a preset server to complete the update of the financial project.

[0032] This embodiment obtains the first hash value of the old version of the financial project to be updated; obtains the second hash value of the new version of the financial project to be updated; obtains the file to be updated for the financial project based on the first and second hash values; the file to be updated is the file that distinguishes the new version from the old version; performs dependency analysis on the file to be updated using a preset open-source library to obtain a dependency graph of the file to be updated; incrementally compiles the dependency graph using a preset front-end packaging tool to obtain a compiled file of the file to be updated; and uploads the compiled file to a preset server to complete the update of the financial project. Since only the compiled file corresponding to the file to be updated needs to be uploaded, instead of uploading all files of the entire financial project to be updated, the update deployment time is shortened, and the bandwidth resources required for deploying the financial project are reduced, thereby accelerating the speed and efficiency of the financial project's launch.

[0033] In a specific embodiment, please refer to Figure 2 In step 101, the first hash value of the old version of the financial project to be updated is obtained, including:

[0034] Step 201: Obtain the hash value of each old branch project in the old version of the financial project to be updated, wherein the first hash value includes the hash value of each old branch project in the old version;

[0035] Step 102, which involves obtaining the second hash value of the new version of the financial project to be updated, includes:

[0036] Step 202: Obtain the hash value of each new branch project in the new version of the financial project to be updated, wherein the second hash value includes the hash value of each new branch project in the new version;

[0037] Step 103, which involves obtaining the file to be updated for the financial project based on the first hash value and the second hash value, includes:

[0038] Step 203: Compare the hash value of each old branch project with the hash value of each new branch project to obtain the file to be updated.

[0039] Specifically, the old version of the financial project to be updated includes m old branch projects with different functions. The hash value of each old branch project is obtained, and a first hash value is included. The new version of the financial project to be updated includes n new branch projects with different functions. The hash value of each new branch project is obtained, and a second hash value is included. Here, m and n can be the same or different. The hash values ​​of the m old branch projects and the hash values ​​of the n new branch projects are compared to obtain the file to be updated. By comparing the hash value of each old branch project with the hash value of each new branch project, all the branch projects to be updated are obtained, and all the branch projects to be updated constitute the file to be updated. Compared to simply comparing the hash values ​​of the old and new versions to obtain the file to be updated, obtaining different branch projects to be updated more accurately reflects the differences between the old and new versions, improving the accuracy of the financial project deployment.

[0040] In a specific embodiment, step 203, which compares the hash value of each old branch project with the hash value of each new branch project to obtain the file to be updated, includes:

[0041] If there are two target old branch projects and a target new branch project with the same branch project name, then the hash value of the first target old branch project and the hash value of the first target new branch project are compared to obtain a first comparison result; wherein, the first comparison result includes the same and different.

[0042] When the first comparison result is different, the first target update branch project is determined to be the first update file;

[0043] If there is no second target old branch project with the same name as the second target new branch project, then the second target new branch project is determined to be the second update file;

[0044] If no new branch project for the third target has the same name as the branch project of the old branch project of the third target, an elimination flag is generated for the old branch project of the third target; the elimination flag is used to instruct the preset server to delete the old branch project of the third target.

[0045] The file to be updated includes the first update file, the second update file, and the obsolescence identifier.

[0046] Specifically, the old version contains 5 old branch projects: A, B, C, D, and E. The new version contains 5 new branch projects: A, B, F, G, and H. Both the old and new branch projects contain A and B. The comparison results are: A in the old branch project is compared with A in the new branch project (comparison result S1); B's hash value is compared with the hash value of B in the old branch project and B in the new branch project (comparison result S2). If comparison result S1 is the same, then A is the same branch project in both the old and new versions, meaning A has not been improved and is not a file to be updated. If comparison result S2 is different, then B in the new and old versions is a different branch project, meaning B in the new branch is the first updated file. If the new branch project contains F, G, and H, while the old branch project does not, then F, G, and H in the new branch project are newly added branch projects in this update, and F, G, and H are the second updated files. If the old branch project contains C, D, and E, while the new branch project does not, then C, D, and E from the old branch project are the branch projects to be phased out in this update. An elimination identifier is generated for each of C, D, and E. The preset server identifies these identifiers and deletes C, D, and E. Alternatively, a shared elimination identifier can be generated for C, D, and E, and the preset server will then delete C, D, and E based on this shared identifier. By comparing the results of different scenarios, a more accurate identification of the first update file to be updated, the second update file to be added, and the elimination identifiers to be deleted is obtained. This improves the accuracy of the preset server's update and deployment of the new version, ensuring the stability of the financial project after the update.

[0047] In a specific embodiment, please refer to Figure 3 In step 104, a dependency analysis is performed on the file to be updated using a preset open-source library to obtain a dependency graph of the file to be updated, including:

[0048] Step 301: Perform dependency analysis on the first updated file using a preset open-source library to obtain the first dependency graph of the first updated file;

[0049] Step 302: Perform dependency analysis on the second update file using a preset open-source library to obtain a second dependency graph of the second update file;

[0050] Step 303: Perform dependency analysis on the eviction marker using a preset open-source library to obtain a third dependency graph of the eviction marker;

[0051] Step 304: Merge the first dependency graph, the second dependency graph, and the third dependency graph according to the preset dependency structure graph to obtain the dependency graph of the file to be updated.

[0052] Specifically, using pre-defined open-source libraries, dependency analysis is performed on the first updated file, the second updated file, and the eviction marker to obtain a first dependency graph for the first updated file, a second dependency graph for the second updated file, and a third dependency graph for the eviction marker. Then, a pre-defined dependency structure graph is used to merge the first, second, and third dependency graphs to obtain the dependency graph for the file to be updated. The pre-defined dependency structure graph is generated based on the dependencies between the new and old branch projects. Optionally, the dependencies between the new and old branch projects can be obtained using SQL syntax, Python regular expressions, or greedy algorithms. By merging the first dependency graph of the first updated file, the second dependency graph of the second updated file, and the third dependency graph of the eviction marker to obtain the dependency graph, the pre-defined front-end packaging tool only requires one incremental compilation to obtain the compiled file for the file to be updated, reducing the number of incremental compilations.

[0053] In a specific embodiment, a preset front-end packaging tool can be used to incrementally compile the first dependency graph to obtain a first compiled file of the first dependency graph; incrementally compile the second dependency graph to obtain a second compiled file of the second dependency graph; and incrementally compile the third dependency graph to obtain a third compiled file of the third dependency graph. The first, second, and third compiled files are then uploaded to a preset server. By incrementally compiling different dependencies separately to obtain different compiled files, and uploading these different compiled files to the preset server in batches for batch updates, when an anomaly occurs in the updated financial project, only the anomaly compiled file needs to be identified and updated to resolve the issue, eliminating the need to update all compiled files and simplifying the handling of anomalies in financial projects.

[0054] In a specific embodiment, please refer to Figure 4 The method further includes:

[0055] Step 401: Obtain the upload progress of the compiled file to the server;

[0056] Step 402: When the upload of the compiled file is interrupted, the upload of the compiled file is resumed using the breakpoint resume technology and the upload progress.

[0057] Specifically, the upload progress of the compiled file to the server is obtained in real time, such as when the upload progress is 80%; when the upload of the compiled file is interrupted, the upload progress is resumed at the point where the upload of the compiled file has been 80% completed, so that the part of the compiled file that has been uploaded does not need to be uploaded again, thus improving the upload efficiency of the compiled file.

[0058] In a specific embodiment, please refer to Figure 5 In step 102, the second hash value of the new version of the financial project to be updated is obtained, including:

[0059] Step 501: Obtain the code package for the new version of the financial project to be updated;

[0060] Step 502: Perform a hash operation on the code package according to a preset hash algorithm to obtain the second hash value of the new version of the financial project to be updated.

[0061] Specifically, the new version of the code package for the financial project to be updated is retrieved from a preset database. A hash calculation is then performed on the new version of the code package using a preset hash algorithm to obtain a second hash value for the new version. Similarly, the old version of the code package for the financial project to be updated is retrieved from the preset database. A hash calculation is then performed on the old version of the code package using a preset hash algorithm to obtain a first hash value for the old version. Specifically, the hash algorithm can be a consistent hash algorithm. The consistent hash algorithm, by introducing virtual nodes and a circular hash space, ensures that when a new version of the code package or an old version of the code package is added or removed, only the data corresponding to the added or removed code package needs to be remapped and migrated, reducing data migration costs.

[0062] In a specific embodiment, the method further includes: when the financial project to be updated is rolled back from the new version to the old version, performing a rollback operation on the financial project to be updated using the first hash value. Specifically, the code package of the old version of the financial project to be updated is found in the database using the first hash value, and the code package of the current new version is replaced with the code package of the old version of the financial project to be updated, completing the rollback operation of the financial project to be updated from the new version to the old version. By using hash values ​​to perform rollback operations on different versions of the financial project to be updated, the rollback operation of the financial project to be updated is simplified.

[0063] In a specific embodiment, please refer to Figure 6 The diagram below shows the structure of a financial project update system according to a second embodiment of this application. The system includes: a hash value acquisition module 601, a file to be updated acquisition module 602, a dependency graph acquisition module 603, a compiled file acquisition module 604, and an update module 605. The hash value acquisition module 601 is used to acquire the first hash value of the old version of the financial project to be updated and the second hash value of the new version of the financial project to be updated. The file to be updated acquisition module 602 is used to obtain the file to be updated of the financial project to be updated based on the first hash value and the second hash value. The file to be updated replaces all files of the old version of the financial project to be updated with the new version. The dependency graph acquisition module 603 is used to perform dependency analysis on the file to be updated using a preset open-source library to obtain the dependency graph of the file to be updated. The compiled file acquisition module 604 is used to incrementally compile the dependency graph using a preset front-end packaging tool to obtain the compiled file of the file to be updated. The update module 605 is used to upload the compiled file to a preset server to complete the update of the financial project to be updated.

[0064] By using the financial project update system in the second embodiment of this application, only the compiled file corresponding to the file to be updated needs to be uploaded, instead of uploading all files of the entire financial project to be updated. This shortens the update deployment time and reduces the bandwidth resources required when deploying the financial project, thereby accelerating the speed and efficiency of the financial project going online.

[0065] In a specific embodiment, the third embodiment of this application provides a financial project update device, including a memory and a processor. The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the method as described in any of the first embodiments of this application.

[0066] In a specific embodiment, a computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the steps of the method as described in any of the first embodiments of this application.

[0067] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0068] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0069] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for updating financial projects, characterized in that, The method includes: Obtain the hash value of each old branch project in the old version of the financial project to be updated, wherein the hash value includes the hash value of each old branch project in the old version; Obtain the hash value of each new branch project in the new version of the financial project to be updated, the hash value including the hash value of each new branch project in the new version; If there are two target old branch projects and one target new branch project with the same branch project name, then the hash value of the first target old branch project and the hash value of the first target new branch project are compared to obtain a first comparison result; wherein, the first comparison result includes the same and different. When the first comparison result is different, the first target new branch project is determined to be the first updated file; If there is no old branch project with the same name as the new branch project of the second target, then the new branch project of the second target is determined to be the second update file; If no new branch project for the third target has the same name as the old branch project for the third target, an elimination flag is generated for the old branch project for the third target; the elimination flag is used to instruct the preset server to delete the old branch project for the third target; the first update file, the second update file, and the elimination flag constitute the file to be updated; the file to be updated is the difference file between the new version and the old version; The first updated file is subjected to dependency analysis using a pre-defined open-source library to obtain the first dependency graph of the first updated file; The second update file is subjected to dependency analysis using a pre-defined open-source library to obtain a second dependency graph of the second update file; The dependency analysis of the elimination identifier is performed using a pre-defined open-source library to obtain a third dependency graph of the elimination identifier; The dependency graph of the file to be updated is obtained by merging the first dependency graph, the second dependency graph, and the third dependency graph according to the preset dependency structure graph. The dependency graph is incrementally compiled using a pre-defined front-end packaging tool to obtain the compiled file of the file to be updated; The compiled file is uploaded to a preset server to complete the update of the financial project to be updated.

2. The method for updating financial projects as described in claim 1, characterized in that, The method further includes: Obtain the upload progress of the compiled file to the server; When the upload of the compiled file is interrupted, the upload of the compiled file is resumed using breakpoint resume technology and the upload progress.

3. The method for updating financial projects as described in claim 1, characterized in that, The process of obtaining the hash value of each new branch project in the new version of the financial project to be updated includes: Obtain the code package for the new version of the financial project to be updated; The code package is hashed according to a preset hash algorithm to obtain the hash value of the new version of the financial project to be updated.

4. The method for updating financial projects as described in claim 1, characterized in that, The method further includes: When the financial project to be updated is rolled back from the new version to the old version, the first hash value is used to perform the rollback operation on the financial project to be updated.

5. A financial project update system, applied to the financial project update method as described in claim 1, characterized in that, include: The module includes a hash value acquisition module, a file to be updated acquisition module, a dependency graph acquisition module, a compiled file acquisition module, and an update module. The hash value acquisition module is used to obtain the first hash value of the old version of the financial project to be updated, and to obtain the second hash value of the new version of the financial project to be updated. The file to be updated acquisition module is used to obtain the file to be updated for the financial project to be updated based on the first hash value and the second hash value; the file to be updated is the difference file between the new version and the old version; The dependency graph acquisition module is used to perform dependency analysis on the file to be updated using a preset open-source library to obtain the dependency graph of the file to be updated. The compiled file acquisition module is used to incrementally compile the dependency graph using a preset front-end packaging tool to obtain the compiled file of the file to be updated; The update module is used to upload the compiled file to a preset server to complete the update of the financial project to be updated.

6. A device for updating financial projects, comprising a memory and a processor, characterized in that, The memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the method as described in any one of claims 1 to 5.

7. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, the processor performs the steps of the method as described in any one of claims 1 to 5.

Images