Abstract: 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.

Abstract: 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.

Abstract: 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. The one or more processors additionally execute the instructions to determine a hold (preservation) time to maintain the instantiation of the cloud-hosted function within the cloud computing environment, based on a plurality of function execution metrics calculated for the cloud-hosted function. The one or more processors further execute the instructions to maintain the instantiation of the cloud-hosted function within the cloud computing environment for the determined hold time.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: The disclosure relates to technology for 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A system, computer-implemented method, and/or non-transitory computer-readable media may provide a warm start technique for cloud-hosted functions. This warm start technique may reduce latency associated with a time to execution of a cloud-hosted function, such as by determining a cloud-hosted function associated with an activated function graph and instantiating the cloud-hosted function ahead of its execution in association with the activated function graph (e.g. in anticipation of a later requested execution of the cloud-hosted function), and/or maintaining an already instantiated cloud-hosted function for a hold time that is dynamically determined for the cloud-hosted function (in anticipation of a later requested execution of the cloud-hosted function being made during that hold time).

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A method for re-querying for routing information is disclosed. The method transmits an initial admission query to a gatekeeper or a request for routing information and receives an admission confirmation or routing information response with a destination address. The method then tries to establish a connection with the destination address. Upon reception of a call failure message including a failure cause, the method, optionally, increments a counter and transmits a re-query to the gatekeeper or other routing entity, and the re-query includes the failure cause and, optionally, a value of the query counter.

Abstract: A Voice over Packet (VoP) network includes an ingress gateway and an egress gateway for transparent transport of signaling messages between source and destination telephony switches utilizing respective source and destination telephony signaling protocols. The ingress gateway is configured for interfacing with the source telephony switch according to the source telephony signaling protocol and the egress gateway is configured for interfacing with the destination telephony switch according to the destination telephony signaling protocol. The ingress gateway and the egress gateway are configured for sharing information, based on a signaling message received by the ingress gateway from the source telephony switch, to determine a selected exchange type to be used by the ingress gateway and egress gateway in transporting the signaling message to the destination telephony switch.

Abstract: An IP-based node in communication with IP-based gateway devices is configured for executing circuit selection for a prescribed trunk group having multiple sets of connected trunk groups, the multiple sets of connected trunk groups managed by the respective IP-based gateway devices. The prescribed trunk group is configured for connecting with a two-way trunk group of a switch, for example a PSTN-based switch, having substantially more circuits than any one of the multiple sets of connected trunk groups for the IP-based gateway devices. The IP-based node executes circuit selection at least based on a first message, received from one of the IP-based gateway devices via an IP connection and specifying circuit availability for at least a portion of the corresponding set of connected trunk groups.