KR-20260064398-A - Workflow-based FaaS platform for multi-event processing and service provision apparatus and method therefor

KR20260064398AKR 20260064398 AKR20260064398 AKR 20260064398AKR-20260064398-A

Abstract

The present invention discloses a workflow-based FaaS platform for multi-event processing and a device and method for providing services therefor. According to the present invention, a FaaS (Function as a Service) platform for multi-event processing based on Kubernetes is provided, comprising: an event-based framework that detects events input from a mobile network and events input from a cloud, and determines whether a plurality of subscribed event combinations satisfy a preset condition; a workflow that executes a series of functions for one of performing an action, waiting, or restarting according to the plurality of event combinations when the plurality of event combinations satisfy the preset condition; and a state store that stores one of a predetermined event detection information, a predetermined function execution completion information, execution information of a predetermined function within the workflow, and abnormal termination information of a predetermined function within the workflow, based on identification information of an event consumer subscribing to a predetermined event.

Inventors

김영한
서장원

Assignees

숭실대학교산학협력단

Dates

Publication Date: 20260507
Application Date: 20241111
Priority Date: 20241030

Claims (12)

As a FaaS (Function as a Service) platform for multi-event processing based on Kubernetes, An event-based framework that detects events input from a mobile network and events input from the cloud, and determines whether a combination of multiple subscribed events satisfies a preset condition; A workflow that executes a series of functions for performing an action, waiting, and restarting according to the plurality of event combinations when the plurality of event combinations satisfy a preset condition; and A FaaS platform for multi-event processing comprising a state store that stores one of the following based on identification information of an event consumer subscribing to a specific event: specific event detection information, specific function execution completion information, execution information of a specific function within a workflow, and abnormal termination information of a specific function within a workflow.
In paragraph 1, The above event-based framework is, Event source for each event that detects events, converts them into CloudEvents format, and delivers them; An event bus that transmits events input into the above event source to event consumers; and A FaaS platform for multi-event processing that includes an event processing service that determines whether multiple subscribed events transmitted from the above event bus satisfy a preset condition and executes a predetermined function within the above workflow.
In paragraph 1, The above event is a FaaS platform for multi-event processing including changes in the location of a user device, changes in network status, and whether a predetermined task has been completed.
In paragraph 1, The above conditions are a FaaS platform for multi-event processing including whether the plurality of events are detected sequentially or in parallel and the detection order.
In paragraph 1, A FaaS platform for multi-event processing that changes functions within the workflow according to the changed events and detection order when subscribed events change or the event detection order changes.
In paragraph 1, A FaaS platform for multi-event processing in which a timeout for waiting is set in a predetermined function of the above workflow, and restarts when the next event is detected within the preset timeout.
As a FaaS (Function as a Service) device for multi-event processing based on Kubernetes, processor; and It includes memory connected to the above processor, The above memory is, Detecting events input from a mobile network and events input from the cloud, and determining whether a combination of multiple subscribed events satisfies a preset condition, When the above combination of multiple events satisfies a preset condition, a series of functions for performing an action, waiting, and restarting according to the above combination of multiple events is executed, and Based on the identification information of an event consumer subscribing to a specified event, to store one of the specified event detection information, specified function execution completion information, execution information of a specified function within a workflow, or abnormal termination information of a specified function within a workflow, A FaaS device for multi-event processing that stores program instructions executed by the above processor.
As a method for providing a Function as a Service (FaaS) for Kubernetes-based multi-event processing, An event-based framework detects events input from a mobile network and events input from a cloud, and determines whether a combination of multiple subscribed events satisfies a preset condition; A workflow step of executing a series of functions for one of performing an action, waiting, and restarting according to the plurality of event combinations when the plurality of event combinations satisfy a preset condition; and A method for providing a FaaS service for multiple event processing, comprising the step of storing one of a predetermined event detection information, a predetermined function execution completion information, execution information of a predetermined function within a workflow, and abnormal termination information of a predetermined function within a workflow, based on identification information of an event consumer subscribing to a predetermined event.
In paragraph 8, The above-mentioned judgment step is, A step of detecting events through the event source for each event, converting them into CloudEvents format, and delivering them; A step of transmitting an event input to the event source to an event consumer via an event bus; and A method for providing a FaaS service for multiple event processing, comprising the step of determining whether multiple events transmitted from the event bus and subscribed to satisfy a preset condition through an event processing service, and executing a predetermined function within the workflow.
In paragraph 8, The above event is a method for providing a FaaS service for processing multiple events, including a change in the location of a user device, a change in network status, and whether a predetermined task has been completed.
In paragraph 8, The above conditions are a method for providing a FaaS service for multi-event processing, including whether the plurality of events are detected sequentially or in parallel and the order of detection.
In paragraph 8, A method for providing a FaaS service for multiple event processing, further comprising the step of changing a function within the workflow according to the changed event and detection order when a subscribed event changes or the event detection order changes.

Description

Workflow-based FaaS platform for multi-event processing and service provision apparatus and method therefor The present invention relates to a workflow-based Function as a Service (FaaS) platform for multi-event processing, and a service provision device and method for the same. Kubernetes is an open-source container orchestration platform that automates many of the manual processes involved in deploying, managing, and scaling containerized applications. In a Kubernetes environment, among various event sources, events originating from mobile networks such as 5G networks (events from Network APIs) and events originating from general cloud environments can be combined to provide more personalized services for specific situations. To this end, a platform for detecting events and executing services is required, along with the capability to handle multiple events. Depending on the service to be provided, the combinations and conditions of multiple events accommodated vary, and the system must be programmable to implement logic that responds to these variations. In this case, if all code that evaluates combinations of multiple events and conditions and performs actions accordingly is implemented in a single application, the logic can be executed quickly when the application is called. FIG. 1 is a diagram illustrating a multi-event processing method according to the prior art. As illustrated in FIG. 1, conventionally, for multi-event processing, an event-based framework for detecting multiple events and a multi-event processing application (Consumer A to Consumer C) are used in combination. When a multi-event processing application consumes events detected through an event-based framework, it determines the combination of events through programmed logic within the application to perform a specific task or publish events related to multi-event processing. Here, publishing represents the workflow, establishing a complex workflow that includes the order of tasks, serial/parallel execution, and dependency setup. This method is intuitive and fast because it performs programmed actions for programmed event patterns within the application. You can implement logic for all event patterns in a single application, or you can implement different logic for each application depending on the event pattern. However, in this approach, since event combinations, condition evaluations, and actions are programmed simultaneously into a multi-event processing application, a new event processing application must be created to perform various actions based on new event combinations. Furthermore, due to the coupling and dependencies between the logic defined within the existing application, there is no way to reuse it separately, which becomes a burden even when modifying the application. Therefore, there is a need for a method that allows developers to freely program and design according to the services they intend to provide, through a programmable, scalable, and reusable multi-event processing approach. FIG. 1 is a diagram illustrating a multi-event processing method according to the prior art. FIG. 2 is a diagram illustrating a FaaS platform for multiple event processing according to the present embodiment. FIG. 3 is a drawing illustrating a first scenario according to the present embodiment. FIG. 4 is a drawing illustrating a second scenario according to the present embodiment. FIG. 5 is a diagram illustrating a third scenario according to the present embodiment. FIG. 6 is a diagram illustrating an exemplary case in which a predetermined function is not completed within a set time due to a timeout set according to the present embodiment. FIG. 7 is a diagram illustrating, by way of example, a case where a specific task within a suspended workflow is restarted. The present invention is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the invention to specific embodiments, and it should be understood that the invention includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the invention. The terms used herein are merely for describing specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as “comprising” or “having” are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof. Furthermore, the components of the embodiments described with reference to each drawing are not limited to the respective embodiments and may be implemented to