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:
Operation of an autonomous vehicle is modified based on the driving style preferences of a passenger. A machine learning module for a motion planner of the autonomous vehicle accepts input relating to driving style of the autonomous vehicle including data representing autonomous vehicle speed, acceleration, braking, or steering during operation. The passenger also provides feedback relating to the vehicle's driving style during operation, and the passenger feedback is used to train the machine learning module to create a personal driving style decision-making model for the passenger that controls operation of the autonomous vehicle. A personal driving style preference profile for the passenger also may be obtained by collecting motion sensor data relating to driving habits of the passenger when the passenger is a driver. The driving style preference profile is used by the motion planner to modify operation of the autonomous vehicle in accordance with the driving style preference profile.
Abstract:
A computer-implemented method for accessing user resources in a virtual private cloud (VPC) using a serverless function within a network architecture includes instantiating a first warm application container for hosting the serverless function. The first warm application container includes a runtime language library without function code of the serverless function. A virtual machine for hosting a Port Address Translation (PAT) gateway is instantiated. The PAT gateway includes a first interface to the VPC and a second interface to the first warm application container. In response to detecting a trigger event for triggering the serverless function, the function code of the serverless function is mounted within the first warm application container. During execution of the function code from the first warm application container, VPC-addressed network packets associated with the serverless function are routed to the VPC via the second interface and the first interface within the PAT gateway.
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:
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.
Abstract:
A method implemented by a network controller, comprising receiving an address filter from a service chain orchestrator, wherein the address filter comprises a plurality of service instance (SI) addresses associated with a plurality of SIs in a network, obtaining network topology information from a plurality of service function (SF) forwarders controlled by the network controller, wherein the network topology information indicates a plurality of network devices communicatively coupled to the plurality of controlled SF forwarders, and wherein at least some of the network devices are SI hosting devices, and generating a service chain topology map by building mappings between at least some of the plurality of controlled SF forwarders, the SI hosting devices, and the plurality of SIs according to the network topology information and the address filter.
Abstract:
A method implemented in a network engine comprising receiving, by a service function (SF) orchestrator in the network engine, a registration request message from a third-party SF manager requesting registration of a SF comprising one or more SF instances in a network, wherein the registration request message comprises vendor identification information identifying a vendor of the SF and SF identification information identifying the SF, receiving a capability information message from the third-party SF manager indicating vendor-specific capability information associated with the SF, receiving a service request message from a service client requesting a network service and one or more policies for the service, generating the network service by utilizing the one or more SF instances according to the one or more policies and the vendor-specific capability information, and sending the one or more policies to the one or more SF instances.
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:
An example method embodiment for networking includes managing, by a network controller, network services for one or more network devices connected to the network controller. Managing network services includes receiving a packet in a traffic flow from a network device. The network device is one of the one or more network devices connected to the network controller. Managing network services further includes determining applicable services for the packet, transmitting the packet to a service provider in accordance with the applicable services for the packet, receiving, from the service provider, service results corresponding to the packet, and creating a forwarding entry providing instructions for handling the traffic flow in a service path table at the network device in accordance with the service results corresponding to the packet.