Container mirror image management method and device, computer equipment, readable storage medium and program product
By creating triggers in the console and setting container image push event trigger conditions, automatically updating container images and redeploying workloads, the traditional container image management methods are solved, and efficient and automated mirror management is achieved.
Patent Information
- Application Number
- CN202411753356.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-02
- Publication Date
- 2025-03-18
AI Technical Summary
Traditional container image management methods have low automation, slow response speed and poor integration convenience, and are unable to respond to image updates in time, which increases the complexity and security risks of the system.
Automatically update the container image of the workload and redeploy by creating triggers in the console, specifying the container image repository, tag, cluster, and workload, and setting the trigger condition to receive a container image push event.
It has achieved improved automation, accelerated response speed, and enhanced integration convenience in container image management, and can respond to image updates in a timely manner, reducing system complexity and security risks.
Smart Images
Figure CN119645647A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of container technology, and in particular to a container image management method, apparatus, device, storage medium, and program product. Background Art
[0002] With the rapid development of containerization technology, container images have been widely used in the management and deployment of applications. Efficient management and automated updates of container images are important links to ensure stable operation and rapid iteration of the system.
[0003] However, the traditional container image management method has some shortcomings, which are mainly manifested in the following aspects: 1. Manual image update: Traditional container image updates often rely on manual operations by users, and the image addresses used by running containers need to be modified one by one. This method is not only inefficient, but also increases the probability of errors. 2. Lack of automated trigger mechanism: Although some existing container management platforms support automated deployment, they have limited support for trigger mechanisms for image updates. For example, after the image is updated, it does not automatically trigger the restart or update operation of the container, and additional scripts or tools are required for management. This method increases the complexity of the system and is not conducive to maintenance. 3. Unable to respond to image updates in a timely manner: In a fast-iterative development environment, application images may be updated frequently. If the image update cannot be responded to in a timely manner, the system may still use the old version of the image, which will not be able to fix known vulnerabilities or improve functions in a timely manner, affecting the security and performance of the system. 4. Difficulty in integration: Some existing solutions have certain difficulties when integrated into the continuous integration or continuous delivery (CI / CD) pipeline. Additional configuration and adjustment are required for different environments, which is not conducive to promotion and application in different environments.
[0004] Therefore, traditional container image management methods have disadvantages such as low automation, slow response speed, and poor integration convenience. How to improve the automation, response speed, and integration convenience of container image management is still an urgent problem to be solved. Summary of the invention
[0005] Based on this, it is necessary to provide a container image management method, device, equipment, storage medium and program product that can improve the automation, response speed and integration convenience of container image management in response to the above technical problems.
[0006] In a first aspect, the present application provides a container image management method, the method comprising:
[0007] Create a trigger in the console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger;
[0008] The trigger condition of the trigger is set to the console receiving a container image push event, and after the trigger is triggered, it is used to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload;
[0009] After receiving a container image push event based on the console, obtain the tag of the pushed container image corresponding to the container image push event, and after determining a target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
[0010] In one of the embodiments, before the console receives a container image push event, the method further includes:
[0011] After receiving the pushed container image based on the container image storage service, triggering a network hook in the container image storage service to send the container image push event to the console.
[0012] In one embodiment, before triggering the network hook in the container image storage service to send the container image push event to the console, the method further includes:
[0013] The event sending address of the network hook is configured as the event receiving address of the console.
[0014] In one embodiment, calling the corresponding container cluster to update the container image of the corresponding workload to the pushed container image through the target trigger, and redeploying the corresponding workload includes:
[0015] Through the target trigger, the gateway interface of the corresponding container cluster is called to obtain the pushed container image from the container image storage service;
[0016] The container image of the corresponding workload is updated to the pushed container image.
[0017] In one embodiment, the method further comprises:
[0018] Each time the trigger is triggered, a trigger record of the trigger and a result after the container image of the corresponding workload is updated are stored in the console.
[0019] In one embodiment, the method further comprises:
[0020] After a trigger is created in the console, the information of the created trigger, the information of the container image repository corresponding to the trigger, the container image tag, the container cluster information, and the workload information are stored in the database;
[0021] Accordingly, determining a target trigger that matches the tag of the pushed container image includes:
[0022] A target trigger corresponding to the tag of the pushed container image is queried from the database.
[0023] In a second aspect, the present application provides a container image management device, the device comprising:
[0024] A creation module, used to create a trigger in a console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger;
[0025] A processing module, used to set the trigger condition of the trigger to be that the console receives a container image push event, and to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload after the trigger is triggered;
[0026] An acquisition module, configured to acquire a tag of a pushed container image corresponding to a container image push event after receiving the container image push event based on the console;
[0027] The processing module is used to, after determining a target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
[0028] In a third aspect, the present application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in the first aspect are implemented.
[0029] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in the first aspect.
[0030] In a fifth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the method described in the first aspect.
[0031] The above-mentioned container image management method, device, equipment, storage medium and program product configure the container image repository and container image tag (Tag) with triggers effective through the console, combined with the notification capability of the container image push event, so that when the user pushes a new container image to the container image repository, the update of the container image can be quickly detected and the trigger can be triggered. Through the console configuration of the container cluster and workload with triggers effective, it can be realized that after detecting the image push, the container image of the corresponding workload is updated to the pushed container image, triggering the automatic deployment of the business. In other words, the method provided in this embodiment realizes the update of the container image of the workload by setting a trigger. The triggering method of the trigger only depends on the general capabilities provided by the event notification interface and the Apiserver interface, and can be easily integrated into various continuous integration or continuous delivery (Continuous Integration / Continuous Deployment Pipeline, CI / CD) tools and processes, and has high applicability. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions 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 related drawings can be obtained based on these drawings without paying creative work.
[0033] Figure 1 This is an application environment diagram of a container image management method in an embodiment;
[0034] Figure 2 It is a flowchart of a container image management method in one embodiment;
[0035] Figure 3 A partial flow chart of a method for managing container images in one embodiment;
[0036] Figure 4 This is a schematic diagram of the interaction of the console in the container image management method in another embodiment;
[0037] Figure 5 is a structural block diagram of a container image management device in one embodiment;
[0038] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0039] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0040] The container image management method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The server 104 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.
[0041] In an exemplary embodiment, Figure 2 As shown, a container image management method is provided, which is applied to Figure 1 The server 104 in the example is used as an example to illustrate, including the following steps 201 to 203. Among them:
[0042] Step 201: Create a trigger in a console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger.
[0043] Among them, a container image is an unchangeable static file that contains executable code to run isolated processes on an information technology (IT) infrastructure. A container image consists of system libraries, system tools, and other platform settings required for a software program to run on a containerized platform such as Docker. A container image shares the operating system kernel of its host machine.
[0044] Among them, the console is the core component that implements the trigger logic, responsible for monitoring changes in container images and triggering subsequent deployment processes.
[0045] Among them, the trigger is an automatic deployment function provided by the container image service. When the container image in the container image repository is updated, it can automatically trigger the workload in the container image cluster to pull the new container image and redeploy it, thereby realizing automatic update of the business.
[0046] In one embodiment, before the console creates a trigger, prepare a Kubernetes container cluster. You can use the Kubeadm tool to build multiple hosts into a container cluster, or use the minikube tool to build a local cluster on a host. Prepare a separate host and deploy the console, database, and image storage service (Harbor service) separately.
[0047] Step 202, setting the trigger condition of the trigger to the console receiving a container image push event, and setting the trigger to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload after the trigger is triggered.
[0048] When creating a trigger in the console, you need to specify the container image repository and container image tag (Tag) that the trigger corresponds to, and you also need to specify the container cluster and workload that the trigger corresponds to. When the container image in the container image repository is updated, the workload in the container image cluster can be automatically triggered to pull the new container image and redeploy it, thereby achieving automatic updates of the business.
[0049] Step 203, after receiving the container image push event based on the console, obtain the tag of the pushed container image corresponding to the container image push event, and after determining the target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
[0050] In one embodiment, the image storage service (Harbor service) configures a webhook, which is used to notify the console of the container image push event. More specifically, the target address of the webhook notification is set to the event receiving address corresponding to the console. The user pushes the container image to the image storage service. After the push is completed, the image storage service triggers the webhook to send the container image push event to the event receiving address of the console, so that the console receives the container image push event.
[0051] After receiving the container image push event, the console queries the target trigger that matches the tag of the pushed container image. If the target trigger can be found, the Apiserver interface of the container cluster is called to update the container image of the workload to the pushed container image.
[0052] In the above-mentioned container image management method, the container image repository and container image tag (Tag) where the trigger is effective are configured through the console, and combined with the notification capability of the container image push event, it can be realized that when the user pushes a new container image to the container image repository, the update of the container image can be quickly detected and the trigger can be triggered. Through the console configuration of the container cluster and workload where the trigger is effective, it can be realized that after detecting the image push, the container image of the corresponding workload is updated to the pushed container image, triggering the automatic deployment of the business. In other words, the method provided in this embodiment realizes the update of the container image of the workload by setting a trigger. The triggering method of the trigger only depends on the general capabilities provided by the event notification interface and the Apiserver interface, and can be easily integrated into various continuous integration or continuous delivery (Continuous Integration / Continuous Deployment Pipeline, CI / CD) tools and processes, and has high applicability.
[0053] In an exemplary embodiment, Figure 3 As shown, before step 203 based on the console receiving the container image push event, the container image management method further includes step 301. Among them:
[0054] Step 301: After receiving the pushed container image based on the container image storage service, trigger the network hook in the container image storage service to send the container image push event to the console.
[0055] Create a project in the container image storage service and set a container image in the project. Create a workload in the cluster and use the container image in the container image storage service to deploy the workload. Specifically, the workload pulls the container image in the container image storage server and starts the Pod. Pod is most commonly used in Kubernetes (K8s). In Kubernetes, a Pod is the smallest deployable computing unit that can be created and managed in a Kubernetes cluster. It usually contains one or more containers.
[0056] In addition, the project configures a webhook and configures the event sending address of the webhook as the event receiving address of the console. In this way, after the pushed container image is received based on the container image storage service, the webhook in the container image storage service is triggered to send the container image push event to the console.
[0057] The method provided in this embodiment configures the container image repository and container image tag of the trigger to take effect through the console, and combines the notification capability of the network hook to achieve that when the user pushes a new container image to the container image repository, the update of the container image can be quickly detected and subsequent deployment operations can be performed.
[0058] In an exemplary embodiment, in combination Figure 4 The interaction diagram shown is used for explanation.
[0059] Step 203 calls the corresponding container cluster to update the container image of the corresponding workload to the pushed container image through the target trigger, and redeploys the corresponding workload, including:
[0060] Step 1: Through the target trigger, call the gateway interface of the corresponding container cluster to obtain the pushed container image from the container image storage service.
[0061] That is to say, the target trigger calls the gateway interface (such as the Apiserver interface) of the corresponding container cluster to obtain the pushed container image from the container image storage service. After the container cluster receives the gateway interface call, it triggers the workload to pull the pushed container image and automatically redeploys it.
[0062] Step 2: Update the container image of the corresponding workload to the pushed container image.
[0063] After the container cluster receives the gateway interface call, it triggers the workload to pull the pushed container image and automatically redeploys it. Specifically, when checking the container image of the workload in the container cluster, if it is found that the container image address has been replaced with the address of the pushed container image, the pod redeployment is triggered.
[0064] The method provided in this embodiment is that the console configures the cluster and workload where the trigger takes effect, and combines the interface capabilities of the gateway interface (Apiserver) to detect the container image push event, update the container image of the corresponding workload, and trigger automatic business deployment.
[0065] In some embodiments, the container image management method further includes:
[0066] Step 1: Each time the trigger is triggered, a trigger record of the trigger and a result after the container image of the corresponding workload is updated are stored in the console.
[0067] The trigger record includes, for example, the trigger time, the trigger number, the trigger result, etc. The trigger result includes, for example, a successful trigger or a failed trigger.
[0068] The result after the container image of the corresponding workload is updated can be understood as the container image after the workload is updated, for example, the pushed container image is the container image after the workload is updated. The console can also record the image address of the corresponding workload, such as the image address of the pushed container image.
[0069] By recording in the console, users can view the trigger record, image address, container image of the workload and other information in the console.
[0070] In some embodiments, the container image management method further includes:
[0071] Step 1: After creating a trigger in the console, store the information of the created trigger, the information of the container image repository corresponding to the trigger, the container image tag, the container cluster information, and the workload information in the database.
[0072] Accordingly, when determining the target trigger that matches the tag of the pushed container image, the target trigger corresponding to the tag of the pushed container image is queried from the database.
[0073] It should be understood that, although the steps in the flowcharts of the embodiments described above are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.
[0074] Based on the same inventive concept, the embodiment of the present application also provides a container image management device for implementing the container image management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more container image management device embodiments provided below can refer to the limitations of the container image management method above, and will not be repeated here.
[0075] In an exemplary embodiment, Figure 5 As shown, a container image management device 50 is provided, including: a creation module 51, a processing module 52 and an acquisition module 53, wherein:
[0076] The creation module 51 is used to create a trigger in a console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger.
[0077] The processing module 52 is used to set the trigger condition of the trigger to the console receiving a container image push event, and, after the trigger is triggered, to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload.
[0078] The acquisition module 53 is used to acquire the tag of the pushed container image corresponding to the container image push event after receiving the container image push event based on the console.
[0079] The processing module 52 is used to, after determining a target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
[0080] In some embodiments, the processing module 52 is further configured to trigger a network hook in the container image storage service to send the container image push event to the console after the pushed container image is received based on the container image storage service.
[0081] In some embodiments, the processing module 52 is further configured to configure the event sending address of the network hook as the event receiving address of the console.
[0082] In some embodiments, the processing module 52 is used to call the gateway interface of the corresponding container cluster through the target trigger, obtain the pushed container image from the container image storage service; and update the container image of the corresponding workload to the pushed container image.
[0083] In some embodiments, the processing module 52 is used to store a trigger record of the trigger and a result after the container image of the corresponding workload is updated in the console each time the trigger is triggered.
[0084] In some embodiments, the processing module 52 is used to store the information of the created trigger, the information of the container image repository corresponding to the trigger, the container image tag, the container cluster information and the workload information in a database after the console creates the trigger. The target trigger corresponding to the tag of the pushed container image is queried from the database.
[0085] Each module in the container image management device 50 can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0086] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 6 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store information about triggers, information about the container image repository corresponding to the trigger, container image tags, information about container clusters and workload information, etc. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a container image management method is implemented.
[0087] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0088] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the container image management method provided in any of the above embodiments is implemented.
[0089] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the container image management method provided in any of the above embodiments is implemented.
[0090] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the container image management method provided in any of the above embodiments.
[0091] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0092] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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 application.
[0093] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A container image management method, characterized in that: The method comprises: Create a trigger in the console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger; The trigger condition of the trigger is set to the console receiving a container image push event, and after the trigger is triggered, it is used to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload; After receiving a container image push event based on the console, obtain the tag of the pushed container image corresponding to the container image push event, and after determining a target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
2. The method according to claim 1, characterized in that Before the console receives a container image push event, the method further includes: After receiving the pushed container image based on the container image storage service, triggering a network hook in the container image storage service to send the container image push event to the console.
3. The method according to claim 2, characterized in that Before triggering the network hook in the container image storage service to send the container image push event to the console, the method further includes: The event sending address of the network hook is configured as the event receiving address of the console.
4. The method according to claim 2, characterized in that: The calling, through the target trigger, of the corresponding container cluster to update the container image of the corresponding workload to the pushed container image, and redeploying the corresponding workload, includes: Through the target trigger, the gateway interface of the corresponding container cluster is called to obtain the pushed container image from the container image storage service; The container image of the corresponding workload is updated to the pushed container image.
5. The method according to claim 1, characterized in that The method further comprises: Each time the trigger is triggered, a trigger record of the trigger and a result after the container image of the corresponding workload is updated are stored in the console.
6. The method according to claim 1, characterized in that The method further comprises: After a trigger is created in the console, the information of the created trigger, the information of the container image repository corresponding to the trigger, the container image tag, the container cluster information, and the workload information are stored in the database; Accordingly, determining a target trigger that matches the tag of the pushed container image includes: A target trigger corresponding to the tag of the pushed container image is queried from the database.
7. A container image management device, characterized in that: The device comprises: A creation module, used to create a trigger in a console for managing container images, and specify the container image repository, container image tag, container cluster, and workload corresponding to the trigger; A processing module, used to set the trigger condition of the trigger to be that the console receives a container image push event, and to call the corresponding container cluster to update the container image of the corresponding workload and redeploy the corresponding workload after the trigger is triggered; An acquisition module, configured to acquire a tag of a pushed container image corresponding to a container image push event after receiving the container image push event based on the console; The processing module is used to, after determining a target trigger that matches the tag of the pushed container image, call the corresponding container cluster through the target trigger to update the container image of the corresponding workload to the pushed container image, and redeploy the corresponding workload.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.