Future Wei Technologies, Inc.

Huawei Technologies Co., Limited

Huawei Cloud Computing Technologies Co., Ltd.

Henry Louis Fourie

Hong Zhang

Farhad P Sunavala

Fei Rao

A system, computer-implemented method, and/or non-transitory computer-readable media may provide a warm start technique for cloud-hosted functions. Included is a non-transitory memory storage comprising instructions, and one or more processors in communication with the memory, wherein the one or more processors execute the instructions to identify a cloud-hosted function configured to be executed within a cloud computing environment. The cloud-hosted function is instantiated within the cloud-hosted computing environment.

Instantiation of cloud-hosted functions based on call to function graph

A network mapping events to workflow instances. One or more event messages are received with an embedded token from one or more event sources associated with an application. A workflow specification is received that specifies a location of the token embedded in the one or more event messages, and the token is extracted from the one or more event messages using the location of the token specified in the workflow specification. The events are then mapped to a workflow instance of the application based on the token the one or more event messages.

Event to serverless function workflow instance mapping mechanism

A system, computer-implemented method, and/or non-transitory computer-readable media may provide a warm start technique for cloud-hosted functions. A call is received from a web application. In response to the received call, a function graph is activated and includes a collection of functions associated with the web-application. The function graph also includes a plurality of states and transitions between the states. In response to the activation of the function graph, a cloud-hosted function associated with a particular state in the plurality of states included in the function graph is determined Before the particular state is triggered within the function graph to execute the cloud-hosted function, the determined cloud-hosted function is instantiated.

A computer-implemented method for processing serverless functions includes mapping a received event to an event state of a plurality of event states in a function graph according to a mapping rule, the function graph including one or more actions for the event state. A data package of a previous event state of the plurality of event states is filtered to generate a filtered data package, using a payload filter associated with the event state. The actions of the event state are executed, where the one or more actions satisfy the mapping rule. A modified data package is sent to a computer system to trigger executing one or more serverless functions associated with the executed one or more actions. The modified data package is based on a data package of the event and the filtered data package. One or more responses are received based on execution of the serverless functions.

Event-driven serverless function orchestration

An architecture, method, and/or non-transitory computer-readable media provide a service graph based serverless cloud architecture. The service graphs can orchestrate cloud-hosted functions into a coordinated micro-service application, and thus control the execution of the cloud-hosted functions in a prescribed manner. Additionally, service graphs permit a user to arrange cloud-hosted functions to execute in sequence or concurrently, manage error conditions by re-invoking function calls, handle scaling to accommodate varying event loads, and the like. Service graphs also allow a user to define rendezvous points (i.e., states) to wait for pre-defined events before executing a cloud-hosted function and progressing through the service graph. The advantages of coordinating the execution of cloud-hosted functions with service graphs is that the service graphs provide a consistent framework for managing cloud-hosted functions without the user having to solve the coordination problems on their own.

Service graph based serverless cloud platform

The disclosure relates to technology for coordinating execution of serverless functions. One or more events are received from one or more event sources. The one or more events are mapped to one or more event states of a function graph according to a mapping rule, the one or more event states including one or more actions, and the one or more actions which satisfied the mapping rule are executed. The received events are sent to a computer system to trigger the computer system initiating one or more computing resource groups for executing one or more serverless functions associated with the one or more actions. One or more responses are received from the serverless functions.

An embodiment device includes a network interface, a non-transitory computer readable medium having executable instructions thereon, and a processor coupled to the network interface and the computer readable medium. The executable instructions cause the processor to receive an Intent representing requirements for data traffic on a network having a plurality of endpoints, with the Intent specifying one or more traffic parameters identifying one or more of the endpoints, and and at least one first service. The executable instructions also include instructions to generate one or more networking commands identifying the at least one first service according to the traffic parameters, send the networking commands to one or more network devices on the network and cause the network devices to perform the at least one first service on a first data transmission in response to parameters of the data transmission satisfying the one or more networking commands.

Intent based network configuration

The disclosure relates to technology for coordinating execution of serverless functions. One or more events are received from one or more external sources. The one or more events are mapped to one or more event states of a processing graph according to mapping rules, the one or more event states including one or more actions, and the one or more actions are executed in response to the one or more events satisfying conditions of the mapping rules. An event response is the received in reply to the received one or more events, where the event response is based on execution of one or more tasks corresponding to a sequence of the executed one or more actions.

A method for service function chaining across subnetworks includes receiving a packet at a virtual switch integration bridge from a first service function (SF) that is in a service function chain (SFC) and that is on a first subnetwork, determining a next SF in the SFC in a different subnetwork, and sending the received packet directly from the virtual switch integration bridge to the next SF.

Service function chaining across multiple subnetworks

Packets of data can be processed by a chain or sequence of service functions which include both virtual and physical service functions. In one approach, the original header and/or payload of a packet is analyzed at a software switch to determine whether the packet should be processed by the chain. If such processing is indicated, a next service function to process the packet is identified. The packet is then forwarded to a virtualized or physical device which implements the next service function. A portion of the header, such as a MAC destination address, may be modified to direct the packet to the next function. Further, in some cases, a service function chain (SFC) header with a chain identifier may be added to, or removed from, the packet.

Integrating physical and virtual network functions in a service-chained network environment

A novel scheme is defined for supporting service graphs to allow specific service functions to be applied to selected subsets of packet flows. According to one or more embodiments, a service graph is modeled as chains or sequences of 'flow steering entities' and 'service instances.' According to an embodiment, a flow steering entity (FSE) is configured to identify the flow, and select the next hop service instance in the chain. After a service instance returns the flow packet, the FSE steers the packet to the next FSE in the graph. An initial FSE is used to select matching traffic to enter the service graph. Wherever path forking and merging is required in the service graph, additional classifiers are positioned with the FSE to steer a subset of traffic along different paths of service function instances.

Growing community of inventors

Livermore, CA, United States of America

Henry Louis Fourie