Plug-in management method, electronic equipment, storage medium and computer program product

Abstract

The invention provides a plug-in management method, electronic equipment, a storage medium and a computer program product, and relates to the technical field of plug-in services. The plug-in management method comprises the following steps: configuring a total probe container according to a demand function of a user side; a plurality of independent plug-in sub-containers are configured in the probe total container based on demand functions through probes in the probe total container; and managing the plurality of plug-in sub-containers through the probe. When related services are provided for a user, a user side can configure a corresponding probe total container based on a demand function selected by the user, a plurality of independent plug-in sub-containers are configured in the probe total container, and probes in the probe total container carry out isolation management on the plurality of independent plug-in sub-containers. Compared with the prior art, the method has the advantages that the isolation, the expandability and the flexibility among the plurality of plug-in sub-containers are effectively improved, the plurality of plug-in sub-containers can be efficiently monitored and managed in a multi-layer and dynamic network environment, the management effect of the probe on the plug-in is optimized, and various management requirements are met.

Description

Technical Field

[0001] The present application relates to the technical field of plug-in services, and in particular to a plug-in management method, electronic device, storage medium and computer program product. Background Art

[0002] In the context of the rapid development of containerization technology, how to efficiently manage and monitor container status has become an important challenge. As a key tool, probes can collect and transmit container operation status data in real time. However, in a dynamically changing and multi-level environment, the deployment and resource balancing management of probes face many problems. The management process requires manual intervention in the working status of the container. In addition, in a multi-container environment, the performance of probes may be affected by resource competition. In some scenarios with limited computing resources, unbalanced resource allocation may cause some probes to be overloaded, thereby affecting the accuracy and real-time performance of monitoring, resulting in poor management of containers by probes, which cannot meet the current various management needs. Summary of the invention

[0003] In view of this, an object of the embodiments of the present application is to provide a plug-in management method, an electronic device, a storage medium, and a computer program product to improve the problem of poor management effect of the probe on the container in the prior art.

[0004] In order to solve the above problems, in a first aspect, an embodiment of the present application provides a plug-in management method, the method comprising:

[0005] Configure the probe container according to the required functions of the user end;

[0006] By using the probes in the probe main container, based on the required functions, a plurality of independent plug-in sub-containers are configured in the probe main container;

[0007] The plurality of plug-in sub-containers are managed through the probe.

[0008] In the above implementation process, when providing relevant services to users, the user end can configure the corresponding probe general container based on the required functions selected by the user, and configure multiple independent plug-in sub-containers in the probe general container, so that multiple plug-in sub-containers can provide corresponding multiple plug-in services to the user end to meet the user's various service needs. The probes in the probe general container isolate and manage multiple independent plug-in sub-containers, effectively improving the isolation, scalability and flexibility between multiple plug-in sub-containers, and can efficiently monitor and manage multiple plug-in sub-containers in a multi-level and dynamic network environment, optimizing the management effect of the probe on the plug-in, and meeting the management needs in a variety of different service scenarios.

[0009] Optionally, configuring a plurality of independent plug-in sub-containers in the probe main container based on the required functions through the probes in the probe main container includes:

[0010] According to the required functions, determine the corresponding plug-in list;

[0011] Obtaining the plug-in sub-containers of multiple target versions corresponding to the plug-in list from a server through the probe based on a unified target communication protocol;

[0012] Through the probe, based on the probe function and container isolation technology, multiple independent plug-in sub-containers are loaded and configured in the probe main container.

[0013] In the above implementation process, when configuring, the user end can first determine the corresponding plug-in list containing multiple plug-ins according to the required functions selected by the user. The probe and the server can communicate and connect based on a unified target communication protocol to obtain plug-in sub-containers of multiple target versions in the plug-in list from the server through the probe. The probe can load and configure multiple independent plug-in sub-containers in the probe total container based on its own probe function and container isolation technology. The plug-in sub-container that needs to be configured can be selected according to the actual needs of the user to realize automatic acquisition and automatic installation of the plug-in sub-container. In addition, the probe can automatically obtain the plug-in sub-container of the required version from the server to reduce the unfavorable situations such as the inability to use normally due to expired versions, or repeated downloads due to repeated versions, effectively reducing the abnormal use of plug-in sub-containers and improving the installation efficiency and effectiveness of plug-in sub-containers.

[0014] Optionally, the acquiring, through the probe, the plug-in sub-containers of multiple target versions corresponding to the plug-in list from the server based on a unified target communication protocol includes:

[0015] Determining, by the probe and based on the target communication protocol, identification information of each of the plug-in sub-containers in the plug-in list from the server;

[0016] If the identification information is the same as the local historical identification information, determining that the corresponding plug-in sub-container is a non-target version;

[0017] If the identification information is different from the local historical identification information, it is determined that the corresponding plug-in sub-container is the target version.

[0018] In the above implementation process, in order to obtain the required target version of the plug-in sub-container, the probe can determine the identification information of each plug-in sub-container in the plug-in list from the server based on the target communication protocol, and compare the identification information with the local historical identification information of the user end. If the identification information is the same as the historical identification information, it indicates that the same plug-in sub-container has been configured in the probe's total container and no download is required. The corresponding plug-in sub-container is a non-target version that does not need to be downloaded; if the identification information is different from the historical identification information, it indicates that the same plug-in sub-container is not configured in the probe's total container, or the relevant plug-in sub-container configured in the probe's total container is a historical version, so the corresponding plug-in sub-container is the target version that needs to be downloaded. It is possible to determine whether to download the plug-in sub-container based on the unique identification information of the plug-in sub-container, effectively reducing the disadvantage of repeated downloading, reducing the transmission pressure during data download, and improving the stability and consistency of the probe management environment.

[0019] Optionally, managing the plurality of plug-in sub-containers through the probe includes:

[0020] Obtaining an updated version of the update plug-in sub-container through the probe;

[0021] Through the probe, based on the probe function and container isolation technology, the corresponding plug-in sub-container is upgraded in the probe main container according to the update plug-in sub-container.

[0022] In the above implementation process, considering that the same plug-in has corresponding version updates during use, therefore, in the process of the probe managing the plug-in sub-container, the probe can obtain the updated plug-in sub-container of the updated version in real time through the communication connection with the server, and based on its own probe function and container isolation technology, upgrade and update the original plug-in sub-container in the probe main container according to the obtained updated plug-in sub-container. It can automatically upgrade and update the corresponding plug-in sub-container when there is an update to the plug-in, effectively improving the flexibility and real-time performance of the probe in managing the plug-in sub-container, and improving the effectiveness of the plug-in sub-container when it works.

[0023] Optionally, managing the plurality of plug-in sub-containers through the probe includes:

[0024] Determining the validity period of each of the plug-in sub-containers in the probe master container by using the probe;

[0025] If it is determined that any of the validity periods has expired, the probe is used to stop the expired plug-in sub-container; wherein the stop operation includes at least one of closing, uninstalling or backing up.

[0026] In the above implementation process, considering that plug-ins may expire and users may stop certain plug-in services during use, the probe can obtain the validity period of each plug-in sub-container during the process of managing the plug-in sub-container, and perform various types of management such as closing, uninstalling, and backing up the plug-in sub-container when the validity period expires to stop the work of the plug-in sub-container. The plug-in sub-container can be stopped and managed accordingly according to the actual licensing status of the plug-in sub-container and the actual usage needs of the user, which effectively improves the effectiveness of the work of the plug-in sub-container.

[0027] Optionally, managing the plurality of plug-in sub-containers through the probe includes:

[0028] Obtaining status information of all the plug-in sub-containers in the probe main container through the probe;

[0029] Determine, by means of the probe, a target plug-in sub-container corresponding to the task type of the task sent by the server from among the plurality of plug-in sub-containers;

[0030] By means of the probe, based on the status information of each of the target plug-in sub-containers, an execution plug-in sub-container for executing the delivered task is selected from a plurality of the target plug-in sub-containers.

[0031] In the above implementation process, since the probe needs to manage multiple plug-in sub-containers, and there may be multiple plug-in sub-containers that provide the same service in multiple plug-in sub-containers, in order to improve the working efficiency of the plug-in, the probe can obtain the status information of all managed plug-in sub-containers, and the status information can represent the working status of each plug-in sub-container and the resource usage data. The probe can receive the dispatched tasks sent by the server, and identify the task type of the dispatched tasks, determine the target plug-in sub-container that can provide the plug-in service of the task type in multiple plug-in sub-containers, and perform task scheduling based on the status information of each target plug-in sub-container, and select the execution plug-in sub-container that executes the dispatched tasks in multiple target plug-in sub-containers. According to the status information of each plug-in sub-container and the type of plug-in service provided, the appropriate plug-in sub-container can be selected to execute the corresponding task, which effectively improves the rationality of task distribution, thereby improving the working efficiency of the plug-in sub-container and providing users with more efficient plug-in services.

[0032] Optionally, configuring the probe master container according to the required functions of the user terminal includes:

[0033] Determining the required function selected by the user terminal from a plurality of function templates;

[0034] Obtaining an installation script corresponding to the required function from the server through the user identity and the unified target communication protocol;

[0035] The installation script is run to configure the probe general container having the probe; wherein the probe is communicatively connected with the server via a target communication protocol.

[0036] In the above implementation process, multiple different types of function templates can be preset in the user end, and each function template has corresponding functions, so as to determine the user's required functions according to the user's choice. The user end can connect to the server end based on a unified target communication protocol to obtain the installation script corresponding to the required function from the server end according to its own user identity, so as to run the installation script locally and configure the probe general container with probes. The probe general container is a general container framework configured based on container isolation technology, and multiple other sub-containers can be created, run and managed inside the general container. It can automatically generate and install the corresponding probe general container according to the actual needs of the user, effectively improving the installation efficiency of the probe general container.

[0037] Optionally, the method further comprises:

[0038] Determining verification information according to the user identity of the user terminal;

[0039] Performing identity authentication with the server based on the verification information through the probe;

[0040] If the identity authentication of the probe is successful, the probe and the server are successfully connected through an encrypted channel based on the target communication protocol.

[0041] In the above implementation process, in order to ensure the uniqueness of the probe and control the user's authority, the corresponding verification information can be generated by the user identity, and then the verification information is sent to the server through the probe for identity authentication. When the identity authentication is successful, the encrypted channel between the probe and the server based on the target communication protocol is successfully connected to transmit data through the encrypted channel. The user end can be authenticated so that the probe has legal connection authority and data authority, which effectively improves the security and controllability of data transmission.

[0042] In a second aspect, an embodiment of the present application further provides a plug-in management device, the device comprising: a main container module, a sub-container module, and a management module;

[0043] The general container module is used to configure the probe general container according to the required functions of the user end;

[0044] The sub-container module is used to configure a plurality of independent plug-in sub-containers in the probe main container based on the required functions through the probes in the probe main container;

[0045] The management module is used to manage the plurality of plug-in sub-containers through the probe.

[0046] In the above implementation process, the corresponding probe main container is configured based on the required functions selected by the user through the main container module, and multiple independent plug-in sub-containers are configured in the probe main container through the sub-container module. The multiple plug-in sub-containers can provide corresponding multiple plug-in services to the user end to meet the user's various service needs. The management module uses the probes in the probe main container to isolate and manage multiple independent plug-in sub-containers.

[0047] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores program instructions, and when the processor reads and runs the program instructions, it executes the steps in any implementation of the above-mentioned plug-in management method.

[0048] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the steps in any implementation of the above-mentioned plug-in management method are executed.

[0049] In a fifth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program / instructions, and when the computer program / instructions are executed by a processor, the steps in any implementation of the above-mentioned plug-in management method are implemented.

[0050] In summary, the embodiments of the present application provide a plug-in management method, an electronic device, a storage medium and a computer program product. When providing relevant services to users, the user end can configure a corresponding probe main container based on the required functions selected by the user, and configure multiple independent plug-in sub-containers in the probe main container. The probes in the probe main container isolate and manage the multiple independent plug-in sub-containers, effectively improving the isolation, scalability and flexibility between the multiple plug-in sub-containers, and can efficiently monitor and manage multiple plug-in sub-containers in a multi-level and dynamic network environment, optimize the management effect of the probe on the plug-in, and meet various management needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0052] Figure 1 A block diagram of an electronic device provided in an embodiment of the present application;

[0053] Figure 2 A flowchart of a plug-in management method provided in an embodiment of the present application;

[0054] Figure 3 A detailed flowchart of step S300 provided in an embodiment of the present application;

[0055] Figure 4 A detailed flow chart of step S320 provided in an embodiment of the present application;

[0056] Figure 5 A detailed flowchart of the first step S400 provided in the embodiment of the present application;

[0057] Figure 6 A detailed flowchart of the second step S400 provided in the embodiment of the present application;

[0058] Figure 7 A detailed flowchart of the third step S400 provided in the embodiment of the present application;

[0059] Figure 8 A detailed flow chart of step S200 provided in an embodiment of the present application;

[0060] Fig. 9 A flowchart of another plug-in management method provided in an embodiment of the present application;

[0061] Fig.10 A schematic diagram of the structure of a plug-in management device provided in an embodiment of the present application.

[0062] Icons: 100 - electronic device; 111 - memory; 112 - storage controller; 113 - processor; 114 - peripheral interface; 115 - input and output unit; 116 - display unit; 500 - plug-in management device; 510 - main container module; 520 - sub-container module; 530 - management module. DETAILED DESCRIPTION

[0063] The technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments of the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the embodiments of the present application.

[0064] In a dynamically changing and multi-level environment, the deployment and resource balancing management of probes face many problems. For example, probes require manual intervention by staff or rely on complex script management, which is inefficient and error-prone. In addition, in a multi-container environment, probes may affect their performance due to resource competition. Especially in scenarios with limited computing resources, unbalanced resource allocation may cause some probes to be overloaded, thus affecting the accuracy and real-time performance of monitoring. Therefore, in the current plug-in management method, the management effect of probes on containers is poor and cannot meet the current multiple management needs.

[0065] In order to solve the above problems, an embodiment of the present application provides a plug-in management method, which is applied to electronic devices. The electronic devices can be servers, personal computers (PCs), tablet computers, smart phones, personal digital assistants (PDAs), and other electronic devices with logical computing functions. Multiple independent plug-in sub-containers can be configured and managed in the probe main container, thereby optimizing the management effect of the probe on the plug-in container.

[0066] It should be noted that the electronic device that executes the plug-in management method can be a user end that requires plug-in services. The user end is connected to a server end that provides services. The server end can be a cloud server or other platforms that can provide the data required by the user end. For example, SAAS (Software-as-a-Service) cloud service serves as a cloud business layer, which is responsible for managing and controlling the operation of the entire probe container. The server end and the probe communicate through corresponding communication protocols, and support operations such as downloading probes and plug-ins, configuration updates, and data uploads.

[0067] Optionally, see Figure 1 , Figure 1 The block diagram of an electronic device provided in an embodiment of the present application. The electronic device 100 may include a memory 111, a storage controller 112, a processor 113, a peripheral interface 114, an input and output unit 115, and a display unit 116. A person skilled in the art may understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the electronic device 100. For example, the electronic device 100 may further include Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0068] The memory 111, storage controller 112, processor 113, peripheral interface 114, input / output unit 115 and display unit 116 are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other via one or more communication buses or signal lines. The processor 113 is used to execute the executable module stored in the memory.

[0069] The memory 111 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc. The memory 111 is used to store programs, and the processor 113 executes the program after receiving the execution instruction. The method executed by the electronic device 100 defined by the process disclosed in any embodiment of the present application can be applied to the processor 113, or implemented by the processor 113.

[0070] The processor 113 may be an integrated circuit chip with signal processing capability. The processor 113 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor.

[0071] The peripheral interface 114 couples various input / output devices to the processor 113 and the memory 111. In some embodiments, the peripheral interface 114, the processor 113 and the memory controller 112 can be implemented in a single chip. In other embodiments, they can be implemented by separate chips.

[0072] The input / output unit 115 is used to provide input data to the user. The input / output unit 115 may be, but is not limited to, a mouse and a keyboard.

[0073] The above-mentioned display unit 116 provides an interactive interface (such as a user operation interface) between the electronic device 100 and the user or is used to display image data for the user's reference. In this embodiment, the display unit can be a liquid crystal display or a touch display. If it is a touch display, it can be a capacitive touch screen or a resistive touch screen that supports single-point and multi-point touch operations. Supporting single-point and multi-point touch operations means that the touch display can sense touch operations generated simultaneously from one or more positions on the touch display, and the sensed touch operations are handed over to the processor for calculation and processing. In an embodiment of the present application, the display unit 116 can display various data such as status information, configuration status, and operation status of multiple plug-in sub-containers.

[0074] The electronic device in this embodiment can be used to execute each step in each plug-in management method provided in the embodiment of the present application. The implementation process of the plug-in management method is described in detail below through several embodiments.

[0075] See also Figure 2 , Figure 2 A flowchart of a plug-in management method provided in an embodiment of the present application, the method may include steps S200-S400.

[0076] Step S200: configuring the probe master container according to the required functions of the user end.

[0077] Among them, the user end can be an electronic device used by the user that requires plug-in services, such as a mobile phone, computer, etc. used by the user. When providing relevant services to the user, the user end can configure the corresponding probe container based on the required functions selected by the user.

[0078] It should be noted that the probe main container includes the corresponding probes. The probe is a device or software used to monitor, detect and analyze network traffic and activities. It can be deployed at key locations in the network to collect data and provide information about network status, performance and security events. As a containerized service running on the user side, the probe main container is mainly responsible for data interaction and management between the server and the plug-in sub-container. The probes in the probe main container can perform two-way data transmission with the server through an efficient and secure communication channel, and support the server's remote monitoring and control of the probes, including the status reporting of the probes, the reception and execution of task instructions, etc. In addition, the probe main container is also responsible for managing the life cycle of the plug-in sub-container, including the dynamic installation, update, uninstallation and operation status monitoring of the plug-in sub-container.

[0079] Step S300 : configuring a plurality of independent plug-in sub-containers in the probe main container based on required functions through the probes in the probe main container.

[0080] Among them, in order to realize the corresponding multiple plug-in services, multiple independent plug-in sub-containers can be configured in the probe main container, and multiple plug-in sub-containers can provide corresponding multiple plug-in services for the user end to meet the user's multiple service needs. Each plug-in sub-container runs in the probe main container, and each plug-in sub-container is connected to the probe for communication, and multiple plug-in sub-containers are isolated from each other and do not affect each other.

[0081] It should be noted that the plug-in obtained by the user end is containerized, and the plug-in sub-container is a new, independent container running in the probe main container. The plug-in in each plug-in sub-container has a specific work service, such as: WEB leak scanning plug-in, host leak scanning plug-in, WEB availability monitoring plug-in, etc. In a probe main container, multiple or multiple plug-in sub-containers can be run at the same time.

[0082] Step S400: managing multiple plug-in sub-containers through probes.

[0083] Among them, the probes in the probe main container manage multiple independent plug-in sub-containers in isolation, which effectively improves the isolation, scalability and flexibility between multiple plug-in sub-containers. Since multiple plug-ins run independently in their own plug-in sub-containers, multiple plug-in sub-containers are isolated from each other, effectively reducing problems such as resource competition, memory leaks or conflicts between plug-ins, and enhancing stability and reliability during management.

[0084] Optionally, if a plug-in of a plug-in sub-container in the probe main container fails, the failure will only affect the corresponding plug-in sub-container, and will not affect other plug-in sub-containers and the probe.

[0085] The full life cycle management of the plug-in in this application can be achieved through a combination of one-click configuration and containerized operation, which significantly simplifies the complexity of plug-in installation, deployment and operation and maintenance management. By isolating the plug-in operating environment, it is ensured that different plug-ins do not interfere with each other, improving the overall stability of the probe system.

[0086] exist Figure 2 In the illustrated embodiment, multiple plug-in sub-containers can be efficiently monitored and managed in a multi-level, dynamic network environment, optimizing the management effect of the probe on the plug-in and meeting the management requirements in a variety of different service scenarios.

[0087] Optionally, see Figure 3 , Figure 3 A detailed flowchart of step S300 is provided for an embodiment of the present application. Step S300 may include steps S310-S330.

[0088] Step S310: Determine the corresponding plug-in list according to the required functions.

[0089] When performing configuration, the user terminal may first determine a corresponding plug-in list including multiple plug-ins according to the required functions selected by the user.

[0090] Optionally, the required functions may include multiple keywords selected by the user, such as vulnerability scanning, network monitoring, etc., and may also include parameters related to the configuration of the user terminal, such as the software version of the user terminal, hardware model and other data, so as to screen among various types of plug-ins according to the required functions and obtain a list of plug-ins that meet the needs of the user terminal. The plug-in list may include plug-ins with multiple different functions to provide multiple different plug-in services, and may also include multiple different plug-ins with the same function.

[0091] Step S320 , using the probe, based on the unified target communication protocol, obtains multiple target versions of plug-in sub-containers corresponding to the plug-in list from the server.

[0092] The probe and the server can communicate and connect based on a unified target communication protocol, so that the probe can obtain multiple target versions of the plug-in sub-container in the plug-in list from the server. The target communication protocol is used to achieve efficient and stable communication between the server, the probe and the plug-in sub-container, while meeting the requirements of sensitive data security, preventing unauthorized access and data leakage, improving the response speed and stability during management, and the performance and scalability of the probe system.

[0093] It should be noted that, considering that in the prior art, the communication between probes usually relies on multiple communication protocols, due to the differences in multiple communication protocols, the communication modules of the probes are separately written for different protocols to achieve multiple communication connections, and multiple protocols will also lead to low security of communication data, which may face the risk of data leakage or tampering. Therefore, in order to reduce communication costs and improve communication security, the probe can be connected to the server and plug-in sub-container based on a unified target communication protocol, so that the communication module of the probe can be standardized, code reuse can be achieved, and the computing cost required for writing for different protocols can be reduced.

[0094] Optionally, a lightweight, high-performance communication protocol can be selected as the target communication protocol. For example, selecting the MQTT (Message Queuing Telemetry Transport) protocol as the target communication protocol can significantly reduce communication overhead and is suitable for a variety of resource-constrained container environments. In addition, it can provide low-latency communication performance while enhancing security during data transmission to avoid sensitive information leakage. Using a unified target communication protocol for communication can reduce the difficulty of accessing probes and plug-in sub-containers, without the need to adapt to multiple protocols, and quickly support multiple communication scenarios.

[0095] Optionally, when downloading, the probe can automatically download a plug-in container package including multiple plug-in sub-containers, and support breakpoint resumption during downloading to ensure the integrity of the download.

[0096] Optionally, the target version may be the latest version of the plug-in sub-container when the user client submits the download request, or may be a specified version determined based on user selection information.

[0097] Step S330 : Through the probe, based on the probe function and container isolation technology, multiple independent plug-in sub-containers are loaded and configured in the probe main container.

[0098] Among them, the probe can load and configure multiple independent plug-in sub-containers in the probe main container based on its own probe function and container isolation technology.

[0099] Optionally, container isolation technology, namely Docker-in-Docker (DinD for short), can run other Docker engines in a Docker container, so that other containers can be created, run, and managed in the container. DinD technology allows the installation of a Docker engine in a Docker container, and by mounting the Docker socket on the host machine to this container, the Docker running in the container can communicate with the Docker on the host machine. In this way, the DinD container has the same Docker environment as the host machine, and can create, start, stop, and manage other Docker containers.

[0100] Optionally, the probe functions may include server-side authentication, probe permission, loading configuration, downloading configuration, loading plug-ins, plug-in installation / uninstallation, plug-in start / stop, plug-in log collection, probe backup, plug-in health check, plug-in upgrade / rollback, plug-in notification, task scheduling and other different types of functions. Based on the relevant functions of the loading configuration, multiple plug-in sub-containers can be independently installed in combination with container isolation technology.

[0101] For example, for the plug-in sub-container of the target version that needs to be installed, the probe can use the DinD technology to load it, and start the corresponding plug-in sub-container inside the probe main container. After the plug-in is started, it will communicate with the probe to prepare for the next step of initialization. The initialization process may include: after the plug-in in the plug-in sub-container is started, it first communicates with the probe through channels such as unixsocket to obtain the initial configuration of the plug-in. The initial configuration may include the connection parameters, working mode, task cycle, etc. required by the plug-in. After obtaining the configuration, the plug-in will perform initialization operations, such as establishing connections with other services, loading initial data, etc. After the initialization is completed, the plug-in will notify the probe itself to enter the ready state, indicating that it can start to execute the work task. After the plug-in is ready, it can also report heartbeat information and health status to the probe regularly through channels such as unix socket, including the current CPU, memory usage, task processing status, etc., so that the probe can determine the work and running status of the plug-in sub-container based on this information, such as whether the plug-in is online, whether it is busy, etc.

[0102] exist Figure 3 In the embodiment shown, the plug-in sub-container to be configured can be selected according to the actual needs of the user, and the plug-in sub-container can be automatically obtained and installed. In addition, the probe can automatically obtain the plug-in sub-container of the required version from the server to reduce the unfavorable situations such as the inability to use normally due to expired versions or repeated downloads due to duplicate versions, effectively reducing the abnormal use of the plug-in sub-container and improving the installation efficiency and effectiveness of the plug-in sub-container.

[0103] Optionally, see Figure 4 , Figure 4 A detailed flow chart of step S320 is provided for an embodiment of the present application. Step S320 may include steps S321-S323.

[0104] Step S321 : determining identification information of each plug-in sub-container in the plug-in list from the server through the probe based on the target communication protocol.

[0105] In order to obtain the required target version of the plug-in sub-container, the probe can determine the identification information of each plug-in sub-container in the plug-in list from the server based on the target communication protocol, and compare the identification information with the local historical identification information of the user end.

[0106] Optionally, the identification information may include identity information and version information of the plug-in subcontainer. The identity information may include unique information such as the name of the plug-in, such as a unique identity code, and the version information may be data such as a version number of the plug-in.

[0107] Step S322: If the identification information is the same as the local historical identification information, it is determined that the corresponding plug-in sub-container is a non-target version.

[0108] If the identification information is the same as the historical identification information, it indicates that the same plug-in sub-container has been configured in the probe main container and does not need to be downloaded again, and the corresponding plug-in sub-container is a non-target version that does not need to be downloaded.

[0109] Optionally, if the identification information is the same as the historical identification information, that is, the plug-in sub-container on the server is the same as the local plug-in sub-container and is of the same version, so there is no need to repeatedly download the same plug-in sub-container and mark it as a non-target version.

[0110] Step S323: If the identification information is different from the local historical identification information, the corresponding plug-in sub-container is determined to be the target version.

[0111] If the identification information is different from the historical identification information, it indicates that the same plug-in sub-container is not configured in the probe main container, or the related plug-in sub-container configured in the probe main container is a historical version. Therefore, the corresponding plug-in sub-container is the target version to be downloaded.

[0112] Optionally, if the identification information is different from the historical identification information, that is, the plug-in sub-container on the server is a different plug-in from the local plug-in sub-container, or a different version of the same plug-in. Therefore, there is no need to download different plug-in sub-containers and mark them as target versions.

[0113] It should be noted that when the user end downloads the plug-in sub-container, it can filter according to the marked non-target version and target version to specifically download the plug-in sub-container marked as the target version.

[0114] For example, the identification information can be uniquely determined by combining the identity information and version information, or the probe can download the installation package (containerized image) of the required plug-in through the encrypted channel of the target communication protocol, and verify the hash value of the installation package during the download process. If the probe already has the corresponding installation package locally and the hash value is consistent, it means that the package has not changed and does not need to be downloaded repeatedly, which reduces unnecessary traffic consumption and improves the efficiency of data download.

[0115] exist Figure 4 In the illustrated embodiment, it is possible to determine whether to download the plug-in sub-container based on the unique identification information of the plug-in sub-container, thereby effectively reducing the disadvantage of repeated downloads, reducing the transmission pressure during data download, and improving the stability and consistency of the probe management environment.

[0116] Optionally, see Figure 5 , Figure 5A detailed flowchart of the first step S400 provided in an embodiment of the present application, step S400 may include steps S411-S412.

[0117] Step S411: Obtain the update plug-in sub-container of the updated version through the probe.

[0118] Considering that the same plug-in may have corresponding version updates during use, the probe can obtain updated plug-in sub-containers of updated versions in real time through the communication connection with the server while the probe manages the plug-in sub-container.

[0119] Optionally, the probe can send the identity information of multiple local plug-in sub-containers to the server, which will search the database using the identity information as a keyword to determine whether there is an updated plug-in sub-container with a corresponding updated version. When there is an updated plug-in sub-container with an updated version, the server can send a notification probe through an encrypted channel of the target communication protocol. After receiving the update notification, the probe can initiate a download request to obtain the updated plug-in sub-container with an updated version.

[0120] Step S412: By means of the probe, based on the probe function and the container isolation technology, the corresponding plug-in sub-container is upgraded in the probe main container according to the update plug-in sub-container.

[0121] The probe can upgrade and update the original plug-in sub-container according to the obtained updated plug-in sub-container in the probe main container based on its own probe function and container isolation technology.

[0122] It should be noted that when there is a corresponding update plug-in sub-container, the user can choose to upgrade the plug-in immediately or at another time. The probe can read the user's upgrade request and update the plug-in sub-container at the corresponding time point. Before the update, the probe can automatically notify the plug-in sub-container of the historical version of the plug-in that it is about to stop (plug-in graceful stop), plug-in backup, etc. to ensure data security and resource release, and then configure and install the update plug-in sub-container after graceful stop and backup to achieve plug-in upgrade. If the upgrade fails, the probe can automatically start the backup historical version of the plug-in sub-container to provide normal plug-in services to the user.

[0123] exist Figure 5 In the illustrated embodiment, the corresponding plug-in sub-container can be automatically upgraded and updated when there is an update to the plug-in, which effectively improves the flexibility and real-time performance of the probe in managing the plug-in sub-container and improves the effectiveness of the plug-in sub-container when it works.

[0124] Optionally, see Figure 6 , Figure 6A detailed flowchart of the second step S400 provided in an embodiment of the present application, step S400 may include steps S421-S422.

[0125] Step S421: Determine the validity period of each plug-in sub-container in the probe main container through the probe.

[0126] Considering that a plug-in may be expired and a user may stop some plug-in services during use, the probe may obtain the validity period of each plug-in sub-container during the process of managing the plug-in sub-container by the probe.

[0127] Optionally, the validity period may be the permission period of the plug-in sub-container, as well as the validity period determined by the user. For example, if the user selects a two-hour vulnerability scanning plug-in service, the validity period is two hours.

[0128] Step S422: If it is determined that any validity period has expired, the probe is used to stop the expired plug-in sub-container.

[0129] When the validity period expires, the plug-in sub-container is managed in various ways, such as closing, uninstalling, backing up, etc., to stop the plug-in sub-container from working.

[0130] For example, the stop operation may include: closing, uninstalling or backing up and other processing of stopping the plug-in service. The backup processing may include regular backup and expired backup. For example, the probe may regularly back up the plug-in sub-container to ensure that it can be quickly restored when the probe main container or plug-in sub-container crashes. The backup content may include various data such as the configuration file, log data and current status information of the plug-in sub-container. The backup may be performed by local storage or uploading to the server. The probe uploads the data to the server for storage, and can quickly redeploy to restore the normal operation of the plug-in service after the probe main container crashes. When the plug-in sub-container fails or restarts, the probe can use the backup data to quickly restore the configuration and status of the plug-in sub-container to minimize the interruption time of the plug-in service. The uninstall processing may include automatic uninstallation and manual uninstallation. The user can choose to manually uninstall a plug-in sub-container, or when the license period of the plug-in sub-container expires, the probe will automatically uninstall the plug-in sub-container.

[0131] exist Figure 6 In the illustrated embodiment, the plug-in sub-container can be stopped and managed accordingly according to the actual permission status of the plug-in sub-container and the actual usage requirements of the user, thereby effectively improving the effectiveness of the work of the plug-in sub-container.

[0132] Optionally, see Figure 7 , Figure 7A detailed flowchart of the third step S400 provided in an embodiment of the present application, step S400 may include steps S431-S433.

[0133] Step S431: obtaining status information of all plug-in sub-containers in the probe main container through the probe.

[0134] Among them, since the probe needs to manage multiple plug-in sub-containers, and there may be multiple plug-in sub-containers providing the same service among the multiple plug-in sub-containers, in order to improve the working efficiency of the plug-in, the probe can obtain the status information of all managed plug-in sub-containers. The status information can represent the working status and resource usage of each plug-in sub-container and other data. The status information can be determined based on the current CPU, memory usage, task processing status, etc. of the plug-in sub-container.

[0135] Step S432: Determine, through the probe, a target plug-in sub-container corresponding to the task type of the task sent by the server from among the multiple plug-in sub-containers.

[0136] The probe can receive the task sent by the server, identify the task type of the task, and determine a target plug-in sub-container that can provide the plug-in service of the task type from among multiple plug-in sub-containers.

[0137] Optionally, the tasks sent can be various types of tasks related to plug-in services sent by the server, such as web vulnerability scanning tasks, etc., and the corresponding task type is vulnerability scanning. One or more target plug-in sub-containers with vulnerability scanning functions can be determined from multiple plug-in sub-containers.

[0138] Step S433: selecting an execution plug-in sub-container for executing the dispatched task from multiple target plug-in sub-containers through the probe based on the status information of each target plug-in sub-container.

[0139] The task scheduling may be performed based on the status information of each target plug-in sub-container, and an execution plug-in sub-container for executing the issued task may be selected from multiple target plug-in sub-containers.

[0140] Optionally, the probe may perform analysis based on multiple status information, and determine the execution plug-in sub-container with the lowest busyness, the least memory usage, and the completed task processing status among multiple target plug-in sub-containers to execute the dispatched task.

[0141] exist Figure 7 In the illustrated embodiment, it is possible to select a suitable plug-in sub-container to perform a corresponding task based on the status information of each plug-in sub-container and the type of plug-in service provided, thereby effectively improving the rationality of task distribution, thereby improving the working efficiency of the plug-in sub-container and providing users with more efficient plug-in services.

[0142] Optionally, see Figure 8 , Figure 8 A detailed flowchart of step S200 is provided for an embodiment of the present application. Step S200 may include steps S210-S230.

[0143] Step S210: determining a required function selected by the user terminal from a plurality of function templates.

[0144] Among them, a plurality of different types of function templates can be preset in the user terminal, and each function template has a corresponding function, so as to determine the user's required function according to the user's selection.

[0145] Optionally, the function templates may include different types of templates such as network security, data transmission, virus detection, etc., and corresponding plug-in services may be pre-configured according to different function templates. For example, the plug-in service corresponding to network security is vulnerability scanning, etc.

[0146] Step S220, obtaining an installation script corresponding to the required function from the server through the user identity and the unified target communication protocol.

[0147] Among them, the user end can be connected to the server end based on a unified target communication protocol to obtain an installation script corresponding to the required function from the server end according to its own user identity.

[0148] Optionally, the server can generate a corresponding installation script according to the required functions. After the user identity is successfully authenticated, if the user has the access authority, the user can obtain the installation script corresponding to the required functions.

[0149] For example, the installation script may be a shell script file, which may include the installation steps of the probe and may also automatically configure relevant information of the user and parameters such as the probe ID.

[0150] Step S230 , running the installation script to configure the probe master container having the probes.

[0151] The installation script can be run locally to configure a probe container with probes. The probe container is a container framework configured based on container isolation technology. Multiple sub-containers can be created, run and managed inside the container. The probe is connected to the server through the target communication protocol.

[0152] Optionally, the user can directly run the installation script to complete the automatic installation of the probe. During the installation process, authentication and binding of user information can be performed to ensure the uniqueness and permission control of the probe.

[0153] It should be noted that the probe main container supports flexible expansion. It can add new plug-in sub-containers or update existing plug-in sub-containers according to different business needs, realize the functions of automatic installation, upgrade, uninstallation and dynamic task scheduling of plug-ins, and improve the efficiency of the coordinated operation of probes and plug-ins. It can integrate a variety of plug-ins to provide services according to needs to meet the needs of various different business scenarios. The overall architecture of the probe main container is highly scalable, flexible and stable, and the plug-ins are deployed in containers to ensure the independence and portability of the plug-ins. Each plug-in runs in an independent sub-container to avoid conflicts with the probe itself or other plug-ins.

[0154] exist Figure 8 In the illustrated embodiment, the corresponding probe master container can be automatically generated and installed according to the actual needs of the user, thereby effectively improving the installation efficiency of the probe master container.

[0155] Optionally, see Fig. 9 , Fig. 9 This is a flow chart of another plug-in management method provided in an embodiment of the present application. The method may further include steps S241-S243.

[0156] Step S241, determining verification information according to the user identity of the user terminal.

[0157] In order to ensure the uniqueness of the probe and control user authority, corresponding verification information can be generated by the user identity, and the verification information can include various types of data such as a unique hash value, verification code, token, etc. generated based on the user identity.

[0158] Step S242, through the probe, identity authentication is performed with the server based on the verification information.

[0159] Among them, the probe can send verification information to the server for identity authentication.

[0160] Optionally, the server can parse and verify the obtained verification information. Through the parsed verification information, the server can verify the identity of the user. For example, the server can compare the parsed data with the user records in the database to check whether the username and password match, or verify the validity of the token, etc., to determine whether the user has the corresponding data authority.

[0161] For example, when the probe is started, it can first read the access code configured by the user as verification information, and send the verification information to the server for verification processing.

[0162] Step S243, if the identity authentication of the probe is successful, the probe and the server are successfully connected through an encrypted channel based on the target communication protocol.

[0163] Among them, when the identity authentication is successful, the encrypted channel between the probe and the server based on the target communication protocol is successfully connected, so that data transmission is carried out through the encrypted channel, thereby improving the security of data transmission.

[0164] Optionally, after the probe's identity authentication is successful, the probe can automatically download relevant licenses and configuration data from the server to control the probe's various behaviors, thereby realizing corresponding probe functions, such as which plug-ins should be enabled and the plug-in's operating parameters.

[0165] exist Fig. 9 In the illustrated embodiment, the user end can be authenticated so that the probe has legal connection authority and data authority, thereby effectively improving the security and controllability of data transmission.

[0166] See also Fig.10 , Fig.10 A schematic diagram of the structure of a plug-in management device provided in an embodiment of the present application. The plug-in management device 500 may include a main container module 510, a sub-container module 520, and a management module 530;

[0167] The general container module 510 is used to configure the probe general container according to the required functions of the user end;

[0168] The sub-container module 520 is used to configure multiple independent plug-in sub-containers in the probe main container based on the required functions through the probes in the probe main container;

[0169] The management module 530 is used to manage multiple plug-in sub-containers through probes.

[0170] In an optional embodiment, the sub-container module 520 is specifically used to: determine the corresponding plug-in list according to the required function; obtain multiple target versions of plug-in sub-containers corresponding to the plug-in list from the server through the probe based on a unified target communication protocol; and load and configure multiple independent plug-in sub-containers in the probe main container based on the probe function and container isolation technology.

[0171] In an optional embodiment, the sub-container module 520 is specifically used to: determine the identification information of each plug-in sub-container in the plug-in list from the server through a probe based on the target communication protocol; if the identification information is the same as the local historical identification information, determine that the corresponding plug-in sub-container is a non-target version; if the identification information is different from the local historical identification information, determine that the corresponding plug-in sub-container is a target version.

[0172] In an optional implementation, the management module 530 is specifically used to: obtain an updated version of the update plug-in sub-container through a probe; and upgrade the corresponding plug-in sub-container according to the update plug-in sub-container in the probe main container based on the probe function and container isolation technology.

[0173] In an optional embodiment, the management module 530 is specifically used to: determine the validity period of each plug-in sub-container in the probe main container through the probe; if any validity period is determined to be expired, stop the expired plug-in sub-container through the probe; wherein the stop operation includes: at least one of closing, uninstalling or backing up.

[0174] In an optional implementation, the management module 530 is specifically used to: obtain, through the probe, the status information of all plug-in sub-containers in the probe main container; determine, through the probe, from multiple plug-in sub-containers, a target plug-in sub-container corresponding to the task type of the task sent by the server; and, through the probe, select, based on the status information of each target plug-in sub-container, from multiple target plug-in sub-containers an execution plug-in sub-container that executes the sent task.

[0175] In an optional embodiment, the general container module 510 is specifically used to: determine the required function selected by the user end from multiple function templates; obtain the installation script corresponding to the required function from the server end through the user identity and a unified target communication protocol; run the installation script to configure the probe general container with the probe; wherein the probe is connected to the server end through the target communication protocol.

[0176] In an optional embodiment, the main container module 510 is also used to: determine verification information based on the user identity of the user end; perform identity authentication with the server end based on the verification information through the probe; if the probe identity authentication is successful, the probe and the server end are successfully connected through an encrypted channel based on the target communication protocol.

[0177] Since the principle of solving the problem by the plug-in management device 500 in the embodiment of the present application is similar to that of the embodiment of the aforementioned plug-in management method, the implementation of the plug-in management device 500 in this embodiment can refer to the description in the embodiment of the aforementioned plug-in management method, and the repeated parts will not be repeated.

[0178] The embodiment of the present application further provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are read and executed by a processor, the steps of any one of the plug-in management methods provided in the embodiment are executed.

[0179] An embodiment of the present application further provides a computer program product, which includes a computer program / instructions. When the computer program / instructions are executed by a processor, the steps in any implementation of the plug-in management method provided in this embodiment are implemented.

[0180] In several embodiments provided in the present application, it should be understood that the disclosed device can also be implemented in other ways. The device embodiments described above are merely schematic, for example, the block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices according to the multiple embodiments of the present application. In this regard, each box in the block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram, and the combination of the block diagrams, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0181] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0182] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable 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 methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0183] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0184] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

[0185] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

Claims

1. A plug-in management method, characterized in that: The method comprises: Configure the probe container according to the required functions of the user end; By using the probes in the probe main container, based on the required functions, a plurality of independent plug-in sub-containers are configured in the probe main container; The plurality of plug-in sub-containers are managed through the probe.

2. The method according to claim 1, characterized in that The configuring of a plurality of independent plug-in sub-containers in the probe main container based on the required functions through the probes in the probe main container includes: According to the required functions, determine the corresponding plug-in list; Obtaining the plug-in sub-containers of multiple target versions corresponding to the plug-in list from a server through the probe based on a unified target communication protocol; Through the probe, based on the probe function and container isolation technology, multiple independent plug-in sub-containers are loaded and configured in the probe main container.

3. The method according to claim 2, characterized in that The step of obtaining the plug-in sub-containers of multiple target versions corresponding to the plug-in list from the server through the probe based on a unified target communication protocol includes: Determining, by the probe and based on the target communication protocol, identification information of each of the plug-in sub-containers in the plug-in list from the server; If the identification information is the same as the local historical identification information, determining that the corresponding plug-in sub-container is a non-target version; If the identification information is different from the local historical identification information, it is determined that the corresponding plug-in sub-container is the target version.

4. The method according to claim 1, characterized in that: The managing the plurality of plug-in sub-containers through the probe includes: Obtaining an updated version of the update plug-in sub-container through the probe; Through the probe, based on the probe function and container isolation technology, the corresponding plug-in sub-container is upgraded in the probe main container according to the update plug-in sub-container.

5. The method according to claim 1, characterized in that: The managing the plurality of plug-in sub-containers through the probe includes: Determining the validity period of each of the plug-in sub-containers in the probe master container by using the probe; If it is determined that any of the validity periods has expired, the probe is used to stop the expired plug-in sub-container; wherein the stop operation includes at least one of closing, uninstalling or backing up.

6. The method according to claim 1, characterized in that The managing the plurality of plug-in sub-containers through the probe includes: Obtaining status information of all the plug-in sub-containers in the probe main container through the probe; Determine, by means of the probe, a target plug-in sub-container corresponding to the task type of the task sent by the server from among the plurality of plug-in sub-containers; By means of the probe, based on the status information of each of the target plug-in sub-containers, an execution plug-in sub-container for executing the delivered task is selected from a plurality of the target plug-in sub-containers.

7. The method according to any one of claims 1 to 6, characterized in that The configuration of the probe container according to the required functions of the user terminal includes: Determining the required function selected by the user terminal from a plurality of function templates; Obtaining an installation script corresponding to the required function from the server through the user identity and the unified target communication protocol; The installation script is run to configure the probe general container having the probe; wherein the probe is communicatively connected with the server via a target communication protocol.

8. The method according to claim 7, characterized in that in, The method further comprises: Determining verification information according to the user identity of the user terminal; Performing identity authentication with the server based on the verification information through the probe; If the identity authentication of the probe is successful, the probe and the server are successfully connected through an encrypted channel based on the target communication protocol.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory stores program instructions, and when the processor runs the program instructions, the steps in the method according to any one of claims 1 to 8 are executed.

10. A computer-readable storage medium, characterized in that: The readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by a processor, the steps of the method according to any one of claims 1 to 8 are executed.

11. A computer program product, characterized in that The computer program product comprises a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps in the method according to any one of claims 1 to 8 are implemented.

Images