System and method for activating components

Abstract

The invention relates to a system (S) for activating components (A, B, C, D), the system (S) having a plurality of components (A, B, C, D), each of the plurality of components (A, B, C, D) being designed to perform at least one task, the components (A, B, C, D) also being designed to exchange messages (E) with other components (A, B, C, D) in order to perform the tasks. The system (S) also comprises: a monitoring unit (UE) which is designed to monitor the exchange of messages (E) between the plurality of components (A, B, C, D); and an activation unit (SE) which is designed to detect a communication pattern based on the exchange of messages (E), to predict the behaviour of the plurality of components (A, B, C, D) based on the communication pattern, and, based on the prediction, to bring one or more components (A, B, C, D) into an active state.

Description

[0001] 202414023 Foreign version

[0002] 1

[0003] Description

[0004] System and procedure for activating components

[0005] The present invention relates to a system for activating components. Furthermore, the present invention relates to a method for activating components. Finally, the present invention relates to a computer program product that, on a program-controlled device, initiates the execution of the method for activating components.

[0006] In distributed computing systems, multiple components perform tasks independently. Together, these tasks solve more complex problems or processes (sometimes called workflows, which consist of multiple tasks or task chains); they can build upon each other's results or parallelize processing. The components can run on the same or multiple computing nodes.

[0007] The components coordinate the execution of their tasks by exchanging messages (or events) via an event messaging system or an intermediary / broker (e.g., a NATS broker). To save costs, computing power, and energy, however, not all components (and thus nodes) are constantly active (also known as a "hot state"). They can be switched to a standby mode (also known as a "cold state") and are started when needed, i.e., upon receiving a message. Starting a component or node from standby mode takes time and therefore delays the processing of the actual workflow.

[0008] Components can be used, for example, in serverless functions, virtual containers, virtual machines, or cloud infrastructures. If the components, or some of them, are not activated or are in standby mode, they must be started upon receiving an incoming message. However, if the components remain permanently activated, i.e., not in standby mode, they consume resources (money, memory, CPU, energy, etc.) even when no messages need to be processed.

[0009] Up to now, it has been accepted in such distributed computer systems that heating up or reactivating a component takes some time, and this is attributed to process / 202414023 Foreign version

[0010] 2

[0011] The workflow level is adjusted accordingly. Alternatively, a certain number of components are kept in an active state as a reserve / buffer so they can be used directly. This number can be adjusted for optimization by measuring the utilization of the components / nodes.

[0012] Regardless of the grammatical gender of a particular term, persons with male, female or other gender identities are included.

[0013] Against this background, one object of the present invention is to provide a way to ensure the execution of a workflow or, more generally, of tasks with a low delay in (distributed) computer systems, while simultaneously saving energy.

[0014] Accordingly, a system for activating components is proposed, wherein the system has several components, each of the several components being trained to perform at least one task, and wherein the components are further trained to exchange messages with other components in order to perform the respective tasks.

[0015] The system in question is, in particular, a distributed computing system, such as a cloud system or a software system with distributed containers, which comprises multiple components or nodes. These components can perform individual tasks that interact to form a workflow. As explained above, the components can exchange messages to execute their respective tasks.

[0016] In order to save energy compared to previous systems while simultaneously ensuring the execution of various workflows, the proposed system uses communication patterns to determine which components need to be activated before they are actually required. This means that, according to the proposed system, the components required for a workflow are not only activated when they are needed (which would lead to a delay in the workflow), but are "preheated" as soon as the system can foresee that the corresponding components will be needed to execute a workflow in the foreseeable future. 202414023 Foreign version

[0017] 3

[0018] For this purpose, the system comprises a monitoring unit and a startup unit. The respective unit, for example, the monitoring unit, can be implemented in hardware and / or software. In a hardware implementation, the respective unit can be a device or part of a device, for example, a computer, a microprocessor, or a control unit on a server, a host system, or similar. In a software implementation, the respective unit can be a computer program product, a function, a routine, part of program code, or an executable object.

[0019] The monitoring unit is designed to monitor the exchange of messages between the various components of the system. For this purpose, the monitoring unit can, for example, be interposed in the communication paths between the components. It is also possible for all messages exchanged between components to be transmitted to the monitoring unit.

[0020] The startup unit is then trained to detect a communication pattern based on the exchange of messages, to predict the behavior of multiple components based on this communication pattern, and to activate one or more components based on this prediction. When a component is activated, this means that the component is put into (immediate) readiness. This is also referred to as activating a component. In this state, the component does not yet perform any actions or receive any calls from the system, such as from a previous component, but is merely woken up from a standby or sleep mode and "preheated" so that it is already active and awake when it is actually supposed to perform an action, such as executing a task.

[0021] Since activation or switching to an active state is based on a prediction of component behavior based on the communication pattern, the activation or preheating of the respective components can occur at a time when the component is not yet actively involved in a workflow of tasks. Rather, the respective component is activated (e.g., woken from standby mode or even switched on) as soon as its involvement in a workflow or in the execution of tasks is probable, based on the detected communication pattern. 202414023 Foreign version

[0022] 4

[0023] In this way, it is possible to reduce delays in the execution of tasks and workflows (since the respective components are reactivated in advance), while at the same time saving energy and other resources, as components do not have to remain activated unnecessarily.

[0024] According to one embodiment, the monitoring unit is configured to recognize and store the time of a message and the sending component. Furthermore, the monitoring unit can be configured to recognize and store the receiving component for the message. Additionally, the monitoring unit can be configured to recognize and store the message type. The monitoring unit can store this information, for example, in a table. This provides a comprehensive overview of the messages sent by the components within the system. This information is typically already available and can be read by the monitoring unit. Furthermore, the message itself can also contain a unique identification number.

[0025] According to a further embodiment, the monitoring unit is configured to correlate messages from multiple components based on causality and to store a unique message identification number and a causality identification number for each message. The causality identification number indicates which message the message is correlated with due to a causality. A causality between messages indicates the causal relationship in which two messages occur. In particular, the causal relationship can also be a temporal one. For example, the monitoring unit can determine that when a message occurs, a specific other message always occurs next, and these two messages are therefore correlated. The causality identification number then indicates which other message a message is correlated with.This causal relationship allows the startup unit to recognize which component needs to be activated next when a specific message occurs.

[0026] According to another embodiment, the startup unit is configured to create a model of the message exchange between the multiple components based on the exchange of messages. Such a model can depict the exchange of messages between components and therefore provides a simple overview of which 202414023 foreign version

[0027] 5

[0028] The model can depict which components typically send messages and in what order. It can also represent situations where one component can send messages to multiple other components, i.e., when multiple components are involved in a workflow.

[0029] According to another embodiment, the starting unit is configured to detect the frequency of message occurrences within the exchanged messages and integrate this into the model to detect the communication pattern. The model can thus also indicate the frequency, and therefore the probability, of a second message being sent to a specific component after a first message. These probabilities cover the scenario where, for example, a first message to a first component is followed by a second message, which is sent to a second component with a first probability and to a third component with a second probability. The model can therefore also represent that the same components are not always required sequentially, but that other sequences of components are possible within a workflow.

[0030] According to another embodiment, the launch unit is configured to determine, based on the communication pattern, which components are involved in the communication pattern in order to predict the behavior of the multiple components. In particular, the launch unit can determine communication patterns for multiple workflows, where different components may be involved in different workflows. Once the launch unit has recognized a communication pattern, it can then easily determine, based on this communication pattern (i.e., the sending and receiving of messages by components), how one or more components will behave in relation to the communication pattern.This means that if a specific communication pattern is determined based on at least one message, the start unit can use this communication pattern to predict which components will subsequently receive and send messages and therefore need to be activated. In this way, the start unit can determine, even with simple switches, which components need to be activated if they are in an inactive state, e.g., standby mode.

[0031] According to another embodiment, the starting unit is designed to consider the messages over a predefined period in order to create the model.

[0032] In particular, the starting unit can be configured to determine the time period based on a selected forecast accuracy. If the forecast is to be more accurate, see 202414023 Foreign Version.

[0033] Option 6 allows the initial unit to consider a longer time period. This way, small deviations in the message flow are not significantly impacted by the larger overall data volume. Furthermore, the initial unit can disregard messages older than a predefined threshold. This allows older messages, which may be outdated due to system changes, to be ignored when creating the model. This makes the model more reliable and the prediction more accurate.

[0034] According to another embodiment, the startup unit is configured to create an activation plan for each message type based on the communication pattern, and to activate the corresponding components based on this activation plan when a message type occurs. In particular, the startup unit can be configured to activate the corresponding components in a defined sequence based on the activation plan. In this way, the startup unit can determine (e.g., read) the message type of the first message upon its arrival and, based on this, determine which components need to be activated and when. This enables a reliable workflow that begins with the first message without having to wait for the individual required components to be activated when they should already be active.At the same time, energy can be saved, as components do not have to remain active unnecessarily.

[0035] According to another aspect, a method for activating components in a system is proposed, wherein the system has multiple components, each of which performs at least one task, and the components exchange messages with other components to perform their respective tasks. The method comprises the following steps:

[0036] - Monitoring the exchange of messages between the multiple components,

[0037] - Detecting a communication pattern based on the exchange of messages,

[0038] - Predictions of the behavior of multiple components based on the communication pattern, and

[0039] - Activating one or more components based on the prediction of the behavior of the multiple components.

[0040] The embodiments and features described for the proposed system apply accordingly to the proposed method. Furthermore, it should be noted that 202414023 is the foreign version.

[0041] 7. The procedural steps may be carried out in the specified order, in a different order, or at least partially simultaneously.

[0042] Furthermore, a computer program product is proposed which, on a program-controlled device, initiates the execution of the procedure described above.

[0043] A computer program product, such as a computer program tool, can be provided or delivered from a server on a network, for example, as a storage medium such as a memory card, USB stick, CD-ROM, DVD, or as a downloadable file. This can be done, for example, in a wireless communication network by transmitting the corresponding file containing the computer program product or tool.

[0044] Other possible implementations of the invention also include combinations of features or embodiments described previously or subsequently with regard to the exemplary embodiments, even if not explicitly mentioned. In such cases, the person skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the invention.

[0045] Further advantageous embodiments and aspects of the invention are the subject of the dependent claims and the exemplary embodiments of the invention described below. The invention will be explained in more detail below with reference to preferred embodiments and the accompanying figures.

[0046] Fig. 1 shows a schematic block diagram of a system for activating components;

[0047] Fig. 2 shows a schematic flowchart of a procedure for activating components;

[0048] Fig. 3 shows a schematic diagram of a flow of messages in the system of Fig. 1;

[0049] Fig. 4 shows a model of message exchange in the system of Fig. 1; and

[0050] Fig. 5 shows an activation plan for the system of Fig. 1.

[0051] In the figures, identical or functionally equivalent elements have been labelled with the same reference symbols unless otherwise indicated. 202414023 Foreign version

[0052] 8

[0053] Fig. 1 shows a system S with several components A, B, C, D. System S can, for example, be a distributed computer system in which components A to D each perform tasks to execute different workflows. The tasks of the individual components A to D can interact and depend on each other or be executed in parallel.

[0054] To perform tasks, components A through D exchange messages, hereinafter also referred to as events E. This exchange of messages E takes place via an event messaging system (EMS). In previous systems, it was necessary for all components A through D to be permanently active to be able to execute a task at any time, which resulted in unnecessarily high energy consumption. Alternatively, if a component A through D was in a sleep or standby mode, it was only activated when actually needed, which led to a delay in the execution of the corresponding workflow.

[0055] To enable improved workflow execution with reduced latency and lower energy consumption, the system S described here includes a monitoring unit UE. This monitoring unit UE records when events or messages E are received by which component A to D. Based on this, a start unit SE determines a communication pattern for the messages E. For this purpose, the start unit SE can, for example, include an event analysis unit EAU.

[0056] This Event Analysis Unit (EAU) can correlate messages or events E using causality information. This means that each event E has a system-wide unique ID and also carries a causality ID, i.e., the ID of the event E that caused the publication or execution of that event E.

[0057] In the procedure as carried out by system S, the first step S1 involves monitoring the exchange of messages or events E between the several components A to D by the monitoring unit UE. Then, in step S2, the start unit SE detects the communication pattern based on the exchange of messages E.

[0058] The starting unit SE can then predict the behavior of the several components A to D in step S3 based on the communication pattern. Finally, the 202414023 foreign version

[0059] 9

[0060] The startup unit SE activates one or more components A to D, as needed and based on a prediction of their behavior. This can be done, for example, based on an activation plan AP. An activation signal unit ASE of the startup unit SE can send corresponding activation signals AS (see Fig. 5) to activate the relevant components A to D.

[0061] Fig. 3 shows components A to D of Fig. 1 with the logical communication taking place between them. Here, events or messages E are represented as triples of<Ereignistyp, Ereignis-ID, Ursachen-ID> The event type a, ß, y, 8 is an identifier for the type of message, the event ID 1 to 5 is a system-wide unique ID for the event, and the cause ID 1, 2 is the ID of the event that caused component A to D to publish the corresponding event.

[0062] In this way, the sequence in the communication process, along with its traceability, can be described. The sequence in the example shown in Fig. 3 is as follows:

[0063] (1) Component A completes its processing and releases an event of type ß. This event is assigned the system-wide unique ID 2. Since component A was previously triggered by the event E(a,1 ,-) with ID 1, the event is assigned the cause ID 1, thus generating E(ß, 2,1).

[0064] (2) When the event E(β, 2,1) is received by component C, this is reported to the monitoring unit UE. The monitoring unit UE records the time, the reporting component, and of course the event E(β, 2, 1) itself.

[0065] (3) Component C processes the event in a task (not shown further).

[0066] (4) As a result of the processing of component C, a new event is published. This event now has the type ö, the ID 5 and the cause ID 2 (since this was the event that component C triggered), therefore E(ö, 5, 2) is generated.

[0067] This process is repeated for each event that is processed by any of the components A to D within the system S.

[0068] The start of a workflow (i.e., a sequence of events or messages) is usually triggered by something outside of system S. These triggers do not have an ID that can be used as a cause ID, and therefore this field remains empty (see the initial event in Fig. 3). 202414023 Foreign version

[0069] For the workflow shown in Fig. 3, the monitoring unit records the messages or events in a table:

[0070] This table allows you to supplement the event information (event type, event ID, cause ID) with the component receiving the event (receiver) and a timestamp (timestamp) when components A through D receive the event. Optionally, the table can also include the sending component.

[0071] As described above with reference to Fig. 1, the start unit SE can process the communication data collected by the monitoring unit UE and can then predict the behavior of the system S based on the determined communication pattern. With this knowledge, the start unit SE can signal components A to D to switch to an active state (activation signals AP).

[0072] For prediction purposes, the starting unit SE can create a model based on the data from the monitoring unit UE, as shown, for example, in Fig. 4. For each event type a, β, y, 8, the starting unit SE aggregates the frequency of occurrence of subsequent events together with the components A to D that receive them.

[0073] In the example shown in Fig. 4, the event E The event E<ß> was published ten times. In seven cases, the event was published and processed by component C. In three cases, the event E <y>published and processed by component B. In the seven cases where C processes the event E<ß>, the event E<ö> is published twice and the event E <e>Published five times. Both are processed by component D. The dashed lines after components B and D indicate that the subsequent progression is no longer considered in this case.

[0074] The model shown in Fig. 4 can be constructed as follows: 202414023 Foreign version

[0075] 11

[0076] 1. The system stores information about which component processes which event type. This information indicates which components must be active for a specific event type and its workflow to be processed smoothly and without waiting time.

[0077] 2. For the preceding event type (determined using the cause ID), it is stored that the event type is a subsequent event type. Furthermore, the frequency of occurrence of this event type is stored. This ensures that it is always clear which event types will be processed or output next when a specific event type is received, along with the frequency of other event types. This information can be used to calculate probabilities for the subsequent event types of a given event type.

[0078] Together, both pieces of information can be used to construct a tree like the one in the following figure.

[0079] Then, an activation plan (AP) is created for each known event type. For each subsequent event type of a given type, the associated components A to D for the subsequent type are marked as preheated or activated (i.e., put into active mode) if the calculated probabilities exceed a predefined threshold.

[0080] An example of such an activation plan is shown in Fig. 5. This is based on the model in Fig. 4.

[0081] If an event of type E< / e> < / y> If the event type E<ß> occurs, the probability for the subsequent event type is 70% (7 out of 10 occurrences). The corresponding component of this type is component C. Therefore, assuming a threshold probability of 50%, it must be activated accordingly. Considering the subsequent event types for E<ß>, event type E <e>based on the initial count of 10 occurrences of E< / e> There is still a 50% probability, and component D must be activated. The activation schedule in Fig. 5 therefore stipulates that components C and D must be activated if component A triggers event E. receives.

[0082] The model in Fig. 4 and the activation plan AP can be continuously improved, particularly during operation. For this purpose, the monitoring unit UE can continuously collect data, as described above. 202414023 Foreign version

[0083] 12

[0084] When an event type is received by component A, the startup unit S searches for the corresponding activation plan and model. To activate components C and D according to the activation plan, the startup unit SE can send activation signals AS to the corresponding components C and D to put them into an active state. This ensures that the components are already in an active state when the current processing in component A is complete and before components C and D begin processing subsequent events.

[0085] The system and procedures described above are capable of learning patterns from communication and predicting component utilization. This allows the system to be better prepared for the various workflows that occur during operation, both when and before they occur. This also applies, for example, to workflows that do not occur frequently but lead to predictable behavior (e.g., in error handling).

[0086] Although the present invention has been described using exemplary embodiments, it can be modified in many ways.

Claims

202414023 Foreign version 13 Patent claims 1. A system (S) for activating components (A, B, C, D) is proposed, wherein the system (S) comprises several components (A, B, C, D), each of the several components (A, B, C, D) being configured to perform at least one task, the components (A, B, C, D) being further configured to exchange messages (E) with other components (A, B, C, D) in order to perform the respective tasks, the system (S) further comprising: - a monitoring unit (UE) that is trained to monitor the exchange of messages (E) between the multiple components (A, B, C, D), and - a startup unit (SE) trained to detect a communication pattern based on the exchange of messages (E), to predict the behavior of several components (A, B, C, D) based on the communication pattern, and to put one or more components (A, B, C, D) into an active state based on the prediction.

2. System according to claim 1, characterized in that the monitoring unit (UE) is configured to recognize and store a time of a message (E) and the sending component (A, B, C, D) for a message (E).

3. System according to claim 2, characterized in that the monitoring unit (UE) is configured to recognize and store the receiving component (A, B, C, D) for the message (E).

4. System according to claim 2 or 3, characterized in that the monitoring unit (UE) is configured to recognize and store a message type of the message (E).

5. System according to one of the preceding claims, characterized in that the monitoring unit (UE) is configured to correlate messages (E) from several components (A, B, C, D) based on causalities and to store for a message (E) a unique identification number of the message and a causality identification number, wherein the causality identification number indicates with which message (E) the message (E) is correlated due to a causality. 202414023 Foreign version 14 6. System according to one of the preceding claims, characterized in that the start unit (SE) is configured to create a model of message exchange between the multiple components (A, B, C, D) based on the exchange of messages (E).

7. System according to claim 6, characterized in that the start unit (SE) is configured to detect the frequency of occurrence of messages (E) within the exchanged messages (E) and to integrate these into the model in order to detect the communication pattern.

8. System according to claim 6 or 7, characterized in that the start unit (SE) is configured to determine, based on the communication pattern, which components (A, B, C, D) are involved in the communication pattern in order to predict the behavior of the multiple components (A, B, C, D).

9. System according to one of claims 6 to 8, characterized in that the start unit (SE) is configured to take the messages (E) into account over a predefined period in order to create the model.

10. System according to claim 9, characterized in that the starting unit (SE) is configured to determine the period based on a selected accuracy of the prediction.

11. System according to one of the preceding claims, characterized in that the start unit (SE) is configured to create an activation plan (AP) for each message type based on the communication pattern and to activate the components (A, B, C, D) based on the activation plan (AP) when a message type occurs.

12. System according to claim 11, characterized in that the start unit (SE) is configured to activate the corresponding components (A, B, C, D) in a defined temporal sequence based on the activation plan (AP).

13. Method for activating components (A, B, C, D) in a system (S), wherein the system (S) has several components (A, B, C, D), each of the several components (A, B, C, D) performing at least one task, wherein the components (A, B, C, 202414023 Foreign version 15 D) exchange messages (E) with other components (A, B, C, D) to communicate with each other to perform tasks, the procedure comprising the following steps: - Monitoring (S1) the exchange of messages (E) between the multiple components (A, B, C, D), - Detecting (S2) a communication pattern based on the exchange of News (E), - Predictions (S3) of the behavior of the multiple components (A, B, C, D) based on the communication pattern, and - Activating (S4) one or more components (A, B, C, D) based on the prediction of the behavior of the multiple components (A, B, C, D).

14. Method according to claim 13, characterized in that the functional features of the system according to any one of claims 2 to 12 are effected.

15. Computer program product which, on a program-controlled device, Implementation of the procedure according to claim 13 or 14.

Images