Task execution method, system and device, storage medium and program product

Abstract

The embodiment of the invention provides a task execution method, system and device, a storage medium and a program product, and relates to the technical field of computers. The method comprises a plurality of task scheduler clusters, each cluster comprises a plurality of electronic devices, one of the electronic devices is a target host device, and the method comprises the steps that the target host device receives a target task execution request sent by a management center through an HTTP / 3 protocol stack, and the request comprises a target execution strategy and a target execution event; storing the target execution event in a time wheel assembly according to the target execution strategy; when the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster through an HTTP / 3 protocol stack, so that the specified node executes the target task; the appointed node is a target node for obtaining the distributed lock in the target node cluster. The throughput of the system is improved, the parallel processing capability of the system is enhanced, and the response efficiency of tasks is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a task execution method, system, device, storage medium and program product. Background Art

[0002] With the continuous development of the Internet and computer technology, the content of online business has become increasingly rich. In order to cope with high-concurrency request scenarios, it is necessary to deploy a task scheduling platform based on a distributed architecture, which involves communication between distributed components in the task scheduling platform.

[0003] When the components deployed by the current task scheduling platform communicate, the HTTP / 1.1 or HTTP / 2.0 network input / output protocol is generally pre-installed and configured on each component, so that each component communicates based on the HTTP / 1.1 or HTTP / 2.0 network input / output protocol.

[0004] However, in high-concurrency request scenarios, the data transmission efficiency of the HTTP / 1.1 or HTTP / 2.0 network input / output protocol at the network input / output layer is low, resulting in a decrease in system throughput, reducing the system's parallel processing capabilities, and further reducing the response efficiency of the task. Summary of the invention

[0005] The embodiments of the present application provide a task execution method, system, device, storage medium and program product to improve the throughput of the system, enhance the parallel processing capability of the system, and thereby improve the response efficiency of the task.

[0006] In a first aspect, an embodiment of the present application provides a task execution method, including multiple task scheduler clusters, each of which includes multiple electronic devices, one of which is a target host device, and the method is applied to the target host device. The method includes: receiving a target task execution request sent by a management center through an HTTP / 3 protocol stack, wherein the target task execution request includes a target execution policy and a target execution event;

[0007] storing the target execution event in the time wheel component according to the target execution strategy;

[0008] When the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster through the HTTP / 3 protocol stack, so that the designated node executes the target task according to the target execution event; the designated node is the target node in the target node cluster that obtains the distributed lock.

[0009] In a possible implementation, the HTTP / 3 protocol stack includes: application layer protocol HTTP / 3, transport layer protocol QUIC and underlying transport mechanism UDP; receiving or sending relevant content through the HTTP / 3 protocol stack includes: based on the UDP, receiving the target task execution request sent by the management center through the QUIC connection, or sending the target execution event to each target node in the target node cluster.

[0010] In a possible implementation, before receiving the target task execution request sent by the management center through the HTTP / 3 protocol stack, it also includes: obtaining an initial node list corresponding to the target node cluster; sending a UDP data packet to the initial node in the initial node list, so that the target host device and the initial node shake hands through QUIC and establish a connection during the handshake process; and determining the connected initial node as the target node.

[0011] In a possible implementation, after obtaining the initial node list corresponding to the target node cluster, it also includes: in response to turning on the device self-discovery function, sending the target IP address related information in broadcast mode to the initial nodes located in the same network segment, and sending it in unicast mode to the initial nodes located in different network segments; receiving the corresponding node information sent by the initial node based on the target IP address related information, and determining the status of the initial node based on the corresponding node information; and executing the subsequent connection process when the status is normal operation.

[0012] In a possible implementation, after sending the target execution event to each target node in the target node cluster so that the designated node executes the target task according to the target execution event, it also includes: receiving corresponding current node information sent by the designated node; determining the current state of the designated node based on the corresponding current node information; and when the current state is a fault, displaying the fault information on the corresponding operation interface.

[0013] In a possible implementation, the target task execution request also includes: a target subject identifier; the target subject identifier corresponds to the target host device; the receiving of the target task execution request sent by the management center includes: receiving the target task execution request sent by the management center according to the target subject identifier.

[0014] In a second aspect, an embodiment of the present application provides a task execution device, including: a transceiver module, configured to receive a target task execution request sent by a management center through an HTTP / 3 protocol stack, wherein the target task execution request includes a target execution strategy and a target execution event;

[0015] A storage module, used for storing target execution events in the time wheel component according to the target execution strategy;

[0016] The transceiver module is also used to send the target execution event to each target node in the target node cluster through the HTTP / 3 protocol stack when the pointer of the time wheel component points to the target execution event, so that the designated node executes the target task according to the target execution event; the designated node is the target node in the target node cluster that obtains the distributed lock.

[0017] In a possible implementation, the HTTP / 3 protocol stack includes: an application layer protocol HTTP / 3, a transport layer protocol QUIC, and an underlying transport mechanism UDP;

[0018] When receiving or sending relevant content through the HTTP / 3 protocol stack, the transceiver module is specifically used to: based on the UDP, receive the target task execution request sent by the management center through the QUIC connection, or send the target execution event to each target node in the target node cluster.

[0019] In a possible implementation, the task execution device further includes: an acquisition module, a determination module;

[0020] The acquisition module is used to obtain the initial node list corresponding to the target node cluster before the transceiver module receives the target task execution request sent by the management center through the HTTP / 3 protocol stack; the transceiver module is also used to send UDP data packets to the initial nodes in the initial node list, so that the target host device and the initial node shake hands through QUIC and establish a connection during the handshake process; the determination module is used to determine the connected initial node as the target node.

[0021] In a possible implementation, the task execution device further includes: an execution module;

[0022] The transceiver module is also used to, after the acquisition module obtains the initial node list corresponding to the target node cluster, in response to starting the device self-discovery function, send the target IP address related information in broadcast mode to the initial nodes located in the same network segment, and send it in unicast mode to the initial nodes located in different network segments; receive the corresponding node information sent by the initial node according to the target IP address related information, the determination module is also used to determine the status of the initial node according to the corresponding node information; the execution module is used to execute the subsequent connection process when the status is normal operation.

[0023] In a possible implementation, the transceiver module is also used to receive the corresponding current node information sent by the designated node after the target execution event is sent to each target node in the target node cluster so that the designated node executes the target task according to the target execution event; the determination module is also used to determine the current state of the designated node based on the corresponding current node information; the transceiver module is also used to display fault information on the corresponding operation interface when the current state is a fault.

[0024] In a possible implementation manner, the target task execution request further includes: a target subject identifier; the target subject identifier corresponds to the target host device;

[0025] The transceiver module, when receiving the target task execution request sent by the management center, is specifically used to: receive the target task execution request sent by the management center according to the target subject identifier.

[0026] In a third aspect, an embodiment of the present application provides a task execution system, including: a management center, a plurality of task scheduler clusters, and a target node cluster corresponding to each task scheduler cluster;

[0027] The target host devices in each of the task scheduler clusters are respectively connected to the management center and the corresponding target node cluster using HTTP / 3 protocol stack communication;

[0028] The task scheduler cluster includes a target host device and multiple slave devices; the slave devices synchronize the operation data stored in the target host device in real time; and the slave devices automatically select the latest target host device from the multiple slave devices when the target host device is abnormal.

[0029] In a fourth aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0030] The memory stores computer-executable instructions;

[0031] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0032] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0033] In a sixth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0034] The task execution method, system, device, storage medium and program product provided by the embodiment of the present application, since each task scheduler cluster includes multiple electronic devices, and one of the multiple electronic devices is a target host device, the target host device can receive the target task execution request including the target execution strategy and the target execution event sent by the management center based on the HTTP / 3 protocol stack by connecting to the management center by using the HTTP / 3 protocol stack. And by connecting to the corresponding target node cluster by using the HTTP / 3 protocol stack, the target execution event can be stored in the time wheel component according to the target execution strategy, so that when the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster based on the HTTP / 3 protocol stack, so that the target node that obtains the distributed lock in the target node cluster, that is, the designated node, executes the target task according to the target execution event, improves the throughput of the system, enhances the parallel processing capability of the system, and thus improves the response efficiency of the task. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0036] Figure 1 A schematic diagram of a scenario for the task execution method provided in this application;

[0037] Figure 2a A flowchart of the task execution method provided for this application;

[0038] Figure 2b Schematic diagram of sending target IP address related information in different modes provided by this application;

[0039] Figure 3 A signaling interaction diagram of the task execution method provided in this application;

[0040] Figure 4 A schematic diagram of the structure of the task execution system provided for this application;

[0041] Figure 5 A schematic diagram of the structure of the task execution device provided for this application;

[0042] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0043] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0044] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0045] First, the terms involved in this application are explained:

[0046] HTTP / 3 protocol stack: refers to the latest version of the Hypertext Transfer Protocol (HTTP), which is designed to improve the efficiency and speed of network transmission. Unlike its predecessor HTTP / 2, HTTP / 3 is no longer based on TCP (Transmission Control Protocol), but uses the QUIC protocol as its transport layer.

[0047] Task scheduler: responsible for managing and executing tasks in the computer system and reasonably allocating system resources according to predetermined strategies and rules.

[0048] Time wheel: An efficient data structure often used to implement timer functions.

[0049] At present, when the components deployed by the task scheduling platform communicate, they generally pre-install and configure the HTTP / 1.1 or HTTP / 2.0 network input / output protocol on each component, so that each component communicates based on the HTTP / 1.1 or HTTP / 2.0 network input / output protocol. However, in high-concurrency request scenarios, the data transmission efficiency of the HTTP / 1.1 or HTTP / 2.0 network input / output protocol at the network input / output layer is low. For example, HTTP / 1.1 cannot send multiple requests in parallel on the same connection and must wait for the previous request to complete before sending the next one. In addition, although HTTP / 2.0 supports multiplexing, it may still affect real-time performance when managing a large number of TCP connections in high-concurrency situations, thereby reducing system throughput, reducing the system's parallel processing capabilities, and further reducing the response efficiency of tasks.

[0050] In order to solve the technical problems in the prior art, in order to improve the throughput of the system, enhance the parallel processing capability of the system, and thus improve the response efficiency of the task, instead of using the HTTP / 1.1 or HTTP / 2.0 network input / output protocol for connection, the HTTP / 3 protocol stack is pre-installed and configured between the components deployed by the task scheduling platform, and the task execution process is performed based on the HTTP / 3 protocol stack. Then, when the management center component obtains the specific content of the task sent by multiple clients, it forms the task execution request corresponding to each client based on the above content and the preset time strategy, and sends the task execution request to the host in the corresponding task scheduling component through the HTTP / 3 protocol stack. Further, the host determines the time of task execution according to the time strategy in the corresponding request, and when the time is reached, it sends the specific content of the task to each execution node in the corresponding execution node component through the HTTP / 3 protocol stack again. Finally, each execution node competes for the distributed lock, and the execution node that obtains the distributed lock executes the task according to the specific content of the task, thereby improving the throughput of the system, enhancing the parallel processing capability of the system, and thus improving the response efficiency of the task.

[0051] Figure 1 A schematic diagram of a scenario of a task execution method provided for this application, such as Figure 1 As shown, the system architecture corresponding to the task execution method provided by the present application includes: a management center 1, a task scheduling cluster 2, and a target node cluster 3. Among them, the management center 1 is used to generate requests and respond to client operations. Among them, the task scheduling cluster 2 is a cluster for task scheduling, which may specifically include multiple electronic devices, and among the multiple electronic devices, there is an electronic device that is a target host device 4. Among them, the target node cluster 3 is a node cluster corresponding to the task scheduler cluster 2, and the target nodes contained therein are used to execute the tasks issued by the target host device 2. Among them, the management center 1 uses the HTTP / 3 protocol stack based on the microservice architecture to communicate with the target host device 4 in the task scheduler cluster 2. The target host device 4 in the task scheduler cluster 2 is connected to the target node in the corresponding target node cluster 3 using the HTTP / 3 protocol stack in accordance with the corresponding relationship.

[0052] It is understandable that this system architecture supports high-concurrency scenarios. Therefore, the number of task scheduler clusters 2 is multiple, and correspondingly, the number of target node clusters 3 is also multiple. In this illustration, two task scheduler clusters 2 and two target node clusters 3 are used for illustration.

[0053] First, the management center 1 obtains the specific content of the target tasks sent by multiple clients, and based on the specific content of the corresponding target tasks, generates a target task execution request corresponding to each client, which includes a target execution strategy and a target execution time, and sends the target task execution request to the target host device 4 in the corresponding task scheduling cluster 2 through the HTTP / 3 protocol stack. Then, each target host device 4 responds to receiving the target task execution request sent by the management center 1, stores the target execution event in the time wheel component according to the target execution strategy, and when the pointer of the time wheel component points to the target execution event, sends the target execution event to each target node in the target node cluster 3 through the HTTP / 3 protocol stack, so that the designated node that obtains the distributed lock in the target node cluster 3 executes the target task according to the target execution event.

[0054] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0055] Figure 2a A flowchart of the task execution method provided for this application, such as Figure 2a As shown, the execution subject is a task execution device, which is located in an electronic device, specifically a target host device, which is located in a corresponding task scheduler cluster, which includes multiple electronic devices, one of which is the target host device, and the number of task scheduler clusters is multiple. The method includes:

[0056] S201. Receive a target task execution request sent by a management center through an HTTP / 3 protocol stack. The target task execution request includes a target execution strategy and a target execution event.

[0057] The task scheduler cluster is a cluster composed of multiple electronic devices that can be responsible for task scheduling. Among these electronic devices, there is an electronic device that is a target host device. The target host device is the device responsible for specific scheduling matters.

[0058] Among them, the above-mentioned electronic device can be any physical device, such as a server, a computer, etc., or can be any virtual device, such as a virtual machine, a virtual network device, a virtual switch, etc., which is not limited in this embodiment.

[0059] It should be noted that the determination of the target host device can be specifically as follows: before application, relevant R&D personnel configure one of the multiple electronic devices as the target host device, and then automatically configure according to preset rules based on the above configuration results and the status of the target host device, for example, according to the election rules, select and configure a new target host device from multiple electronic devices.

[0060] Exemplarily, before the implementation of this solution, if the relevant R&D personnel have designated a certain electronic device as the target host device, then when an abnormality or failure occurs in the electronic device, other electronic devices can automatically select the next target host device according to the election rules, and perform task scheduling based on the device. Among them, the above-mentioned election rules can specifically be rules for elections that rely on the open source Raft algorithm. It is understandable that in order to ensure that the next target host device can smoothly take over the work of the previous target host device, each determined target host device must synchronize data with other electronic devices, that is, regularly synchronize the data for executing task scheduling to other electronic devices to improve the success rate of task execution.

[0061] Among them, the HTTP / 3 protocol stack is the latest version of the HTTP protocol. It runs based on the QUIC protocol and aims to improve the speed and efficiency of network transmission by using UDP (User Datagram Protocol). The management center is the manager of the task scheduler cluster, which is used to receive user needs and forward the user needs to the corresponding target host device.

[0062] The target task execution request is a request to instruct the execution of the target task, which specifically includes a target execution strategy and a target execution event. The target execution strategy is a pre-configured time strategy to be followed when executing a task, such as executing a task every five seconds. The target execution event is used to characterize the task to be executed, which specifically may include detailed information of the task, required resource information, etc. This embodiment does not limit the specific content of the target execution strategy and the target execution event.

[0063] The target task is any task triggered by the user on the corresponding client, such as a query task, a reconciliation task, etc. This embodiment does not limit the specific target task.

[0064] In this embodiment, a communication connection can be established in advance between the management center and multiple task scheduler clusters using the HTTP / 3 protocol stack, and multiple users can perform trigger operations on corresponding target tasks through corresponding clients. Then, in response to the triggering of the above operations, multiple clients send the specific content of the corresponding target tasks to the management center. Correspondingly, the management center obtains the specific content of multiple target tasks, and generates corresponding target execution events based on the specific content of each target task, and then obtains the pre-configured target execution strategy, and generates a target task execution request containing the corresponding target execution event and target execution strategy based on each target execution event and target execution strategy, thereby obtaining the target task execution requests corresponding to multiple clients.

[0065] Furthermore, the management center sends each request to the target host device corresponding to the task scheduler cluster responsible for processing each request through the HTTP / 3 protocol stack. The corresponding client mentioned above can be a Web server or other device, which is not limited in this embodiment.

[0066] Based on this, the target host device receives the target task execution request through the HTTP / 3 protocol stack, and parses the target task execution request to obtain the target execution strategy and target execution event.

[0067] It is understandable that the task types that each task scheduler cluster is responsible for scheduling can be the same or different, and can be configured by relevant R&D personnel according to their needs. This application does not limit the task types that the target host device is responsible for scheduling. Among them, the task type can be specifically divided according to the subject, execution logic or other characteristics of the task.

[0068] For example, if there are three task types A, B, and C, corresponding task scheduler clusters can be configured for A, B, and C respectively. Furthermore, if the task demand for task type A is large, two corresponding task scheduler clusters can be configured for A.

[0069] In this scenario, after generating multiple target task execution requests, the management center can send each target task execution request to the target host device in the task scheduler cluster corresponding to the task type according to the task type corresponding to each target task execution request. Accordingly, each target host device receives the corresponding target task execution request and obtains the target execution policy and target execution event therein.

[0070] S202: Store the target execution event in the time wheel component according to the target execution strategy.

[0071] Among them, the time wheel component is responsible for storing the specific execution events of the target tasks that need to be scheduled by the task scheduler cluster.

[0072] In this embodiment, after obtaining the target execution strategy and the target execution event of the target task, the target host device stores the target execution event in the slot corresponding to the time wheel component according to the target execution strategy.

[0073] Exemplarily, if the target execution strategy is to execute a task every five seconds, and the slot interval of the time wheel is one second, then according to the strategy, the target execution event is placed five slots away from the current pointer position, so that the pointer moves every second and points to the slot after five seconds, thereby determining the target task corresponding to the target execution event.

[0074] It can be understood that the above examples are only for illustrative purposes, and this embodiment does not limit the specific strategy of the target execution strategy and the specific setting of the time wheel component.

[0075] S203. When the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster through the HTTP / 3 protocol stack, so that the designated node executes the target task according to the target execution event; the designated node is the target node in the target node cluster that obtains the distributed lock.

[0076] The target node cluster is a node cluster responsible for executing tasks issued by the corresponding task scheduler cluster, and specifically includes multiple target nodes. The target node is a node that has established a long connection with the task scheduler cluster using the HTTP / 3 protocol stack. The node can be a hardware device such as a server or a computer, or can be any virtual device, which is not limited in this embodiment.

[0077] Among them, the distributed lock is a pre-configured redis distributed lock, which can coordinate access to shared resources, ensure that only one process or node can access a specific resource at the same time, and improve the security of threads.

[0078] Optionally, the above-mentioned distributed lock may also be other types of distributed locks, which is not limited in this embodiment.

[0079] In this embodiment, a communication connection can be established in advance between each task scheduler cluster and the corresponding target node cluster using the HTTP / 3 protocol stack. Then, when the pointer of the time wheel component points to the slot where the target execution event is located, the target host device sends the target execution event to each target node in the target node cluster through the HTTP / 3 protocol stack. Correspondingly, each target node responds to receiving the target execution event and starts to compete for the distributed lock based on its own network status, current throughput, time of receiving the target execution event, and other information. The designated node that finally obtains the distributed lock executes the target task according to the content reflected by the target execution event, such as the detailed information of the task and the required resource information.

[0080] It is understandable that after the designated node acquires the distributed lock, other target nodes will no longer execute the target task based on the target execution event.

[0081] The designated node is a node that can execute the target task, that is, a target node in the target node cluster that obtains the distributed lock.

[0082] The task execution method provided in this embodiment, since each task scheduler cluster includes multiple electronic devices, and one of the multiple electronic devices is a target host device, the target host device can receive the target task execution request including the target execution strategy and the target execution event sent by the management center based on the HTTP / 3 protocol stack by connecting to the management center through the HTTP / 3 protocol stack. And by connecting to the corresponding target node cluster through the HTTP / 3 protocol stack, the target execution event can be stored in the time wheel component according to the target execution strategy, so that when the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster based on the HTTP / 3 protocol stack, so that the target node that obtains the distributed lock in the target node cluster, that is, the designated node, executes the target task according to the target execution event, improves the throughput of the system, enhances the parallel processing capability of the system, and thus improves the response efficiency of the task.

[0083] As an optional embodiment, based on the above embodiment, this embodiment further refines the content included in the HTTP / 3 protocol stack, and receiving or sending related content through the HTTP / 3 protocol stack. In this embodiment, the HTTP / 3 protocol stack includes: application layer protocol HTTP / 3, transport layer protocol QUIC and underlying transport mechanism UDP; when receiving or sending related content through the HTTP / 3 protocol stack, the following steps are specifically included:

[0084] Based on UDP, the target task execution request sent by the management center is received through the QUIC connection, or the target execution event is sent to each target node in the target node cluster.

[0085] In this embodiment, the HTTP / 3 protocol stack includes the application layer protocol HTTP / 3, the transport layer protocol QUIC, and the underlying transport mechanism UDP. The application layer protocol HTTP / 3 is the third major version of the HTTP protocol, inheriting the multiplexing, header compression and other features of HTTP / 2. The transport layer protocol QUIC is based on the underlying transport mechanism UDP, but adds connection management, encryption, flow control and congestion control functions to avoid head-of-line blocking problems. The underlying transport mechanism UDP is a simple, connectionless transport layer protocol.

[0086] In this embodiment, when the target host device receives the target task execution request sent by the management center through the HTTP / 3 protocol stack, or sends the target execution event to each target node in the target node cluster, it quickly establishes a communication channel with the management center or the corresponding target node cluster through QUIC based on the connectionless characteristics of UDP, thereby receiving the target task execution request sent by the management center, or sending the target execution event to each target node in the target node cluster.

[0087] The task execution method provided in this embodiment, because the HTTP / 3 protocol stack includes UDP with connectionless characteristics and QUIC that supports multiplexing, can quickly implement the receiving and sending actions when one or more target host devices need to receive the target task execution request sent by the management center, or send the target execution event to each target node in the target node cluster, by using QUIC connection based on UDP, thereby further improving the system throughput and enhancing the system's parallel processing capabilities.

[0088] As an optional embodiment, based on the above embodiment, this embodiment further includes the following steps before receiving the target task execution request sent by the management center through the HTTP / 3 protocol stack:

[0089] Step a1: Get the initial node list corresponding to the target node cluster.

[0090] It can be understood that a prerequisite for the implementation of this solution is that multiple task scheduler clusters respectively establish long connections with the management center and the corresponding target node clusters using the HTTP protocol stack.

[0091] Among them, the initial node list is a list of all initial nodes included in the target node cluster, which may include the IP address and port information of the initial node, or may also include other information. This embodiment does not limit this. The initial node is a node existing in the target node cluster.

[0092] In this embodiment, the relevant R&D personnel can obtain all the initial nodes contained in the target node cluster corresponding to each task scheduler cluster in advance according to the specific configuration, and create an initial node list based on all the initial nodes to obtain the initial node list corresponding to the target node cluster. Then, when it is necessary to establish a long connection with the corresponding target node cluster, each target host device obtains the initial node list of the corresponding target node cluster.

[0093] Step a2: Send a UDP data packet to the initial node in the initial node list, so that the target host device and the initial node handshake through QUIC and establish a connection during the handshake process.

[0094] Among them, UDP data packet is the basic unit of the underlying transmission mechanism UDP in the data transmission process.

[0095] In this embodiment, after obtaining the corresponding initial node list, a UDP data packet is sent to each initial node according to all the initial nodes included in the list and the IP address of each initial node. Then, in response to receiving the UDP data packet, the online initial node starts the QUIC protocol handshake process with the target host device, exchanges necessary information such as encryption keys, version information and other connection parameters, thereby establishing a connection.

[0096] Step a3: Determine the connected initial node as the target node.

[0097] It is understandable that for the initial nodes that are not online, it may not be possible to successfully obtain the UDP data packet. Therefore, for these initial nodes, they will not be able to successfully connect to the target host device in this connection.

[0098] Based on this, the initial node that is successfully connected is determined as the target node.

[0099] It should be noted that the process of connecting the target host device and the management center using HTTP / 3 is similar to the above process, that is, sending a UDP data packet to the management center, and based on the result of the management center receiving the UDP data packet, using QUIC handshake to establish a connection. The specific execution process is similar to the above execution process and will not be repeated here.

[0100] It is understandable that after the connection is established, the target host device can periodically send heartbeat signals to the target nodes in the corresponding target node cluster based on the HTTP / 3 protocol stack, and receive responses from the above target nodes based on the heartbeat signal feedback to ensure the normal state of the connection, thereby improving system stability.

[0101] The task execution method provided in this embodiment is based on the premise that a long connection has been established between the components based on the HTTP / 3 protocol stack. Therefore, by obtaining the initial node list corresponding to the target node cluster, a UDP data packet can be sent to the initial node in the initial node list, so that the target host device and the initial node shake hands through QUIC and establish a connection during the handshake process, thereby determining the connected initial node as the target node, thereby quickly determining all the initial nodes through the list, improving the efficiency of establishing long connections, and improving the success rate of subsequent task execution.

[0102] As an optional embodiment, based on the above embodiment, after obtaining the initial node list corresponding to the target node cluster, this embodiment further includes the following steps:

[0103] Step b1: In response to starting the device self-discovery function, the target IP address related information is sent in a broadcast mode to the initial node located in the same network segment, and is sent in a unicast mode to the initial node located in a different network segment.

[0104] In this embodiment, after obtaining the initial node list corresponding to the target node cluster, the target host device can also determine the status of the initial node based on the enabled device self-discovery function, and then perform the subsequent connection process based on the status. Based on this, the target IP address related information is sent to the initial node in the same network segment through the basic UDP protocol in broadcast mode, and is sent to the initial node in a different network segment through the basic UDP protocol in unicast mode.

[0105] The target IP address related information is used to characterize the IP address and other related information of the target host device. Each node can determine the IP address of the target host device through the target IP address related information and communicate with the target host device.

[0106] Broadcast mode is a network communication mode, that is, a mode in which broadcast packets can be sent to all nodes in a network. Unicast mode is a point-to-point communication mode, that is, broadcast packets are sent to a specific IP address instead of the entire network.

[0107] The same network segment refers to an IP address range under a subnet mask, which is usually managed by the same router or switch, and this embodiment does not limit this. Different network segments refer to nodes being located in different subnets.

[0108] It is understandable that in the same network segment, all nodes share a broadcast domain, and broadcast packets can be received by all devices in the network segment. However, nodes in different network segments are not in the same broadcast domain, so unicast mode is needed to ensure that data packets can cross network segments to reach specific nodes.

[0109] Specifically, the target host device identifies the initial nodes located in the same network segment and the initial nodes located in different network segments according to the IP addresses reflected in the corresponding initial node list, and encodes the target IP address related information using a preset encoding method, such as protobuf encoding method. Figure 2b As shown, the broadcast mode is adopted to send the broadcast packet containing the encoded target IP address related information to the initial nodes 1, 2, 3, and 4 located in the same network segment through the basic UDP protocol, and the initial node 5 in a different network segment is sent in unicast mode.

[0110] It is understandable that the above-mentioned preset encoding method may also be other encoding methods, and this embodiment does not limit this.

[0111] Step b2: Receive the corresponding node information sent by the initial node according to the target IP address related information, and determine the state of the initial node according to the corresponding node information.

[0112] Among them, the corresponding node information is the status information corresponding to the initial node, which may specifically include the IP address corresponding to the initial node, the name in the network, the server identifier, the online status, the load status, the network status and other information. This embodiment does not limit the specific content of the node information.

[0113] It is understandable that after obtaining the target IP address related information corresponding to the target host device, the initial node obtains its own node information and sends the corresponding node information to the target host device according to the target IP address related information.

[0114] Correspondingly, the corresponding node information sent by the initial node according to the target IP address related information is received and read, the state of each initial node is determined according to the reading result, and whether each initial node is operating normally is further determined according to the determination result.

[0115] Exemplarily, if the logical representation of the online status of the initial node is "1" and the logical representation of the offline status is "0", then whether the initial node is operating normally can be determined based on whether the online status in the corresponding node information is "1", that is, when it is determined to be "1", it is determined that the initial node is operating normally, and when it is determined to be "0", it is determined that the initial node is abnormal.

[0116] It should be understood that the above examples are only for illustrative purposes and should not constitute any limitation to the present application.

[0117] Step b3: When the status is normal operation, perform the subsequent connection process.

[0118] In this embodiment, after determining the status of the initial node, in response to the status of the initial node being normal operation, a UDP data packet is sent to the normally operating initial node in the initial node list, so that the target host device and the normally operating initial node handshake through QUIC, and establish a connection during the handshake process, thereby determining the connected initial node as the target node. The specific execution process is similar to step a2-step a3, and will not be repeated here.

[0119] The task execution method provided in this embodiment, because the device self-discovery function is turned on, can receive the corresponding node information sent by the initial node according to the relevant information of the target IP address by sending the target IP address related information in broadcast mode to the initial node in the same network segment and in unicast mode to the initial node in a different network segment before executing the connection process, and can determine the status of the initial node according to the corresponding node information, so as to execute the subsequent connection process when the status is normal operation. This ensures that the sent UDP data packet can be received smoothly, further improving the efficiency of establishing a long connection.

[0120] As an optional embodiment, based on any of the above embodiments, after sending the target execution event to each target node in the target node cluster so that the designated node executes the target task according to the target execution event, this embodiment further includes the following steps:

[0121] Step c1: Receive the corresponding current node information sent by the designated node.

[0122] The corresponding current node information is the node executing the target task, and the node information after the target task is completed.

[0123] It can be understood that the content of the corresponding current node information and the corresponding node information may be consistent or inconsistent. When inconsistent, the corresponding current node information may include the execution results of the target task and other relevant data. This embodiment does not limit the specific content of the corresponding current node information.

[0124] In this embodiment, in order to facilitate relevant R&D personnel to understand the running status of the node in real time, after executing the target task, the designated node obtains its own corresponding current node information and sends the corresponding current node information to the target host device.

[0125] Step c2: Determine the current state of the specified node according to the corresponding current node information.

[0126] Among them, the current state is the state of the node after completing the target task.

[0127] In this embodiment, after obtaining the corresponding current node information of the specified node, the target host device determines the status of the specified node based on the content in the corresponding current node information, such as the current online status, the current load status, the target task execution result, etc.

[0128] Exemplarily, if the current load state is represented by specific load data, when the load data is within a normal range, the current state of the specified node can be determined to be normal; and when the load data exceeds the normal range, the current state of the specified node can be determined to be abnormal.

[0129] Step c3: When the current state is a fault, the fault information is displayed on the corresponding operation interface.

[0130] Among them, the fault information is information that characterizes the failure of the node, for example, it can be the field where the fault is located, or it can be the field where the specific cause of the fault is located, such as the field where "load data exceeds the normal range" is located. This embodiment does not limit the specific content of the fault information.

[0131] In this embodiment, based on determining the status of the execution node, when the current status is a fault, fault information, such as "node A fails" or "load data of node A exceeds the normal range", is displayed on the corresponding operation interface.

[0132] It should be understood that the above exemplary descriptions are merely examples and should not constitute any limitation to the present application.

[0133] The task execution method provided in this embodiment can determine the current state of the specified node based on the corresponding current node information by receiving the corresponding current node information sent by the specified node, so that when the current state is a fault, the fault information is displayed on the corresponding operation interface, thereby realizing the management of the node, so that the relevant R&D personnel can promptly know the abnormal state of the node based on the fault information and take the next step of measures, thereby further improving the success rate of task execution.

[0134] As an optional embodiment, this embodiment further refines the content of the target task execution request and the target task execution request sent by the receiving management center on the basis of any of the above embodiments. In this embodiment, the target task execution request also includes: a target subject identifier; the target subject identifier corresponds to the target host device; when receiving the target task execution request sent by the management center, the following steps are specifically included:

[0135] The target task execution request sent by the receiving management center according to the target topic identifier.

[0136] As mentioned above, in a high-concurrency scenario, there are multiple task scheduler clusters, and the task types that each task scheduler cluster is responsible for can be the same or different, and the management center needs to send corresponding target task execution requests to the task scheduler clusters responsible for different task types. Therefore, the target task execution request sent by the user's corresponding client to the management center also includes the target subject identifier.

[0137] The target subject identifier is any subject identifier that represents the task type, such as the name and number of the task type. This embodiment does not limit the specific form of the target subject identifier.

[0138] In this embodiment, after receiving different target task execution requests, the management center obtains the target subject identifier contained therein, and determines the task type of the target task according to the identifier, and then sends the target task execution request to the target host device corresponding to the corresponding task scheduler cluster according to the task type responsible for each task scheduler cluster. Based on this, the target host device receives the target task execution request sent by the management center according to the target subject identifier.

[0139] The task execution method provided in this embodiment stores the target subject identifier in the target task execution request. Therefore, by receiving the target task execution request sent by the management center according to the target subject identifier, subsequent task execution operations can be performed on the target task of the responsible task type, so that each task scheduler cluster can accurately and orderly schedule tasks, further improving the success rate of task execution.

[0140] Figure 3 The signaling interaction diagram of the task execution method provided in this application is as follows: Figure 3 As shown, this embodiment describes in detail the complete process of the task execution method, which includes:

[0141] S301. The target host device obtains an initial node list corresponding to the target node cluster.

[0142] S302. In response to starting the device self-discovery function, the target host device sends information related to the target IP address in a broadcast mode to an initial node located in the same network segment, and sends it in a unicast mode to an initial node located in a different network segment.

[0143] S303: The initial node sends corresponding node information to the target host device according to the target IP address related information.

[0144] S304: The target host device receives the corresponding node information of the initial node, and determines the state of the initial node according to the corresponding node information.

[0145] S305: When the target host device is in normal operation, the target host device sends a UDP data packet to the initial node in the initial node list.

[0146] S306: The target host device shakes hands with the initial node through QUIC and establishes a connection during the handshake process.

[0147] S307: The target host device determines the connected initial node as the target node.

[0148] S308. The management center generates a target task execution request according to the specific contents of the target tasks sent by the multiple clients; the request includes a target execution strategy, a target execution event, and a target subject identifier.

[0149] S309: The management center sends a target task execution request to the target host device according to the target subject identifier.

[0150] S310, the target host device receives the target task execution request through the HTTP / 3 protocol stack.

[0151] Specifically, based on UDP, the target task execution request sent by the management center is received through the QUIC connection.

[0152] S311. The target host device stores the target execution event in the time wheel component according to the target execution policy.

[0153] S312: In response to the pointer of the time wheel component pointing to the target execution event, the target host device sends the target execution event to each target node in the target node cluster through the HTTP / 3 protocol stack.

[0154] Specifically, based on UDP, the target execution event is sent to each target node in the target node cluster through the QUIC connection.

[0155] S313. Each target node competes for the distributed lock.

[0156] S314: The designated node that obtains the distributed lock executes the target task according to the target execution event.

[0157] S315. The designated node sends the corresponding current node information to the target host device.

[0158] S316. The target host device receives the corresponding current node information of the designated node, and determines the current state of the designated node according to the corresponding current node information.

[0159] S317: When the target host device is in a current state of failure, the failure information is displayed on the corresponding operation interface.

[0160] Figure 4The structural diagram of the task execution device provided by this application is as follows: Figure 4 As shown, the task execution device 40 provided in this embodiment is located in an electronic device, specifically in a target host device. The task execution device 40 provided in this embodiment includes: a transceiver module 41 and a storage module 42.

[0161] Among them, the transceiver module 41 is used to receive the target task execution request sent by the management center through the HTTP / 3 protocol stack, and the target task execution request includes a target execution strategy and a target execution event; the storage module 42 is used to store the target execution event in the time wheel component according to the target execution strategy; the transceiver module 41 is also used to send the target execution event to each target node in the target node cluster through the HTTP / 3 protocol stack when the pointer of the time wheel component points to the target execution event, so that the designated node executes the target task according to the target execution event; the designated node is the target node in the target node cluster that obtains the distributed lock.

[0162] Optionally, the HTTP / 3 protocol stack includes: an application layer protocol HTTP / 3, a transport layer protocol QUIC, and an underlying transport mechanism UDP;

[0163] Accordingly, when receiving or sending relevant content through the HTTP / 3 protocol stack, the transceiver module 41 is specifically used to: based on UDP, receive the target task execution request sent by the management center through the QUIC connection, or send the target execution event to each target node in the target node cluster.

[0164] Optionally, the task execution device further includes: an acquisition module and a determination module;

[0165] Among them, the acquisition module is used to obtain the initial node list corresponding to the target node cluster before the transceiver module 41 receives the target task execution request sent by the management center through the HTTP / 3 protocol stack; the transceiver module 41 is also used to send UDP data packets to the initial nodes in the initial node list, so that the target host device and the initial node shake hands through QUIC and establish a connection during the handshake process; the determination module is used to determine the connected initial node as the target node.

[0166] Optionally, the task execution device further includes: an execution module;

[0167] Among them, the transceiver module 41 is also used to send the target IP address related information in broadcast mode to the initial node located in the same network segment in response to starting the device self-discovery function after the acquisition module obtains the initial node list corresponding to the target node cluster, and sends it to the initial node located in a different network segment in unicast mode; receive the corresponding node information sent by the initial node according to the target IP address related information, and determine the module, which is also used to determine the status of the initial node according to the corresponding node information; the execution module is used to execute the subsequent connection process when the status is normal operation.

[0168] Optionally, the transceiver module 41 is also used to send the target execution event to each target node in the target node cluster so that the designated node executes the target task according to the target execution event, and then receives the corresponding current node information sent by the designated node; the determination module is also used to determine the current state of the designated node based on the corresponding current node information; the transceiver module 41 is also used to display the fault information on the corresponding operation interface when the current state is a fault.

[0169] Optionally, the target task execution request further includes: a target subject identifier; the target subject identifier corresponds to the target host device;

[0170] Correspondingly, when receiving the target task execution request sent by the management center, the transceiver module 41 is specifically used to: receive the target task execution request sent by the management center according to the target subject identifier.

[0171] The task execution device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0172] Figure 5 This is a schematic diagram of the structure of the task execution system provided in this application. Figure 5 As shown, the task execution system 50 provided in this embodiment includes: a management center 51, a task scheduler cluster 52, and a target node cluster 53 corresponding to the task scheduler cluster 52; wherein, there are multiple task scheduler clusters 52, but only two are shown in the figure for a clearer description, and correspondingly, only two target node clusters 53 are also shown;

[0173] The target host devices in each task scheduler cluster 52 are respectively connected to the management center 51 and the corresponding target node cluster 53 using the HTTP / 3 protocol stack communication; the task scheduler cluster 52 includes a target host device and multiple slave devices; the slave devices synchronize the operating data stored in the target host device in real time; when the target host device is abnormal, the slave device automatically selects the latest target host device from multiple slave devices.

[0174] Optionally, the management center 51 may specifically include components such as a load balancer, a static server, a reverse proxy server, a backend gateway, a microservice architecture, and further include a database, a mail server, and a file transfer protocol server.

[0175] Optionally, the task execution system may further include a time wheel component and a memory database, such as a redis memory database, for storing data generated by executing the task execution method.

[0176] Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 provided in this embodiment includes: at least one processor 61 and a memory 62. Optionally, the device 60 also includes a communication component 63. The processor 61, the memory 62 and the communication component 63 are connected via a bus 64.

[0177] In a specific implementation process, at least one processor 61 executes the computer-executable instructions stored in the memory 62, so that at least one processor 61 executes the above method.

[0178] The specific implementation process of the processor 61 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0179] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0180] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0181] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0182] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0183] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0184] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0185] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0186] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0187] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0188] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0190] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0191] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A task execution method, characterized in that: The method comprises a plurality of task scheduler clusters, each of which comprises a plurality of electronic devices, one of which is a target host device, and the method is applied to the target host device, and the method comprises: Receiving a target task execution request sent by a management center through an HTTP / 3 protocol stack, wherein the target task execution request includes a target execution strategy and a target execution event; storing the target execution event in the time wheel component according to the target execution strategy; When the pointer of the time wheel component points to the target execution event, the target execution event is sent to each target node in the target node cluster through the HTTP / 3 protocol stack, so that the designated node executes the target task according to the target execution event; the designated node is the target node in the target node cluster that obtains the distributed lock.

2. The method according to claim 1, characterized in that The HTTP / 3 protocol stack includes: application layer protocol HTTP / 3, transport layer protocol QUIC and underlying transport mechanism UDP; Receive or send relevant content through the HTTP / 3 protocol stack, including: Based on the UDP, the target task execution request sent by the management center is received through the QUIC connection, or the target execution event is sent to each target node in the target node cluster.

3. The method according to claim 1, characterized in that Before receiving the target task execution request sent by the management center through the HTTP / 3 protocol stack, the method further includes: Obtain an initial node list corresponding to the target node cluster; Sending a UDP data packet to an initial node in the initial node list, so that the target host device and the initial node shake hands through QUIC and establish a connection during the handshake process; The connected initial node is determined as the target node.

4. The method according to claim 3, characterized in that After obtaining the initial node list corresponding to the target node cluster, the method further includes: In response to the device self-discovery function being enabled, information related to the target IP address is sent in a broadcast mode to an initial node located in the same network segment, and in a unicast mode to an initial node located in a different network segment; Receiving corresponding node information sent by the initial node according to the target IP address related information, and determining the state of the initial node according to the corresponding node information; When the state is normal operation, a subsequent connection process is performed.

5. The method according to any one of claims 1 to 4, characterized in that: After sending the target execution event to each target node in the target node cluster so that the designated node executes the target task according to the target execution event, the method further includes: Receiving the corresponding current node information sent by the designated node; Determining the current state of the designated node according to the corresponding current node information; When the current state is a fault, the fault information is displayed on the corresponding operation interface.

6. The method according to any one of claims 1 to 4, characterized in that: The target task execution request further includes: a target subject identifier; the target subject identifier corresponds to the target host device; The receiving of the target task execution request sent by the management center includes: Receive a target task execution request sent by the management center according to the target subject identifier.

7. A task execution system, characterized in that: include: A management center, multiple task scheduler clusters, and target node clusters corresponding to each task scheduler cluster; The target host devices in each of the task scheduler clusters are respectively connected to the management center and the corresponding target node cluster using HTTP / 3 protocol stack communication; The task scheduler cluster includes a target host device and a plurality of slave devices; The slave device synchronizes the operation data stored in the target host device in real time; The slave device automatically selects the latest target host device from the multiple slave devices when the target host device is abnormal.

8. An electronic device, characterized in that: include: Memory, processor, and transceiver; The memory stores computer-executable instructions; the transceiver user transmits and receives data; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images