Patent classifications
G06F2209/541
Distributed code execution involving a serverless computing infrastructure
A method for distributed code execution involving a first serverless computing infrastructure, the first serverless computing infrastructure comprising one or more first infrastructure nodes, the one or more first infrastructure nodes comprising a first invocation controller node and one or more first executing nodes, the one or more first infrastructure nodes being communicatively coupled to one or more client nodes, the one or more client nodes being external to the one or more first infrastructure nodes, the method comprising receiving event information, identifying application logic associated with the event information, selecting, from an invoker group, an invoker node for executing the application logic, causing the invoker node to execute the application logic, causing the invoker node to provide a result of the executed application logic, and receiving the result.
Client server communication system
Apparatus for communicating with a server application. A first request is received by a first agent application on a first client computer system from the server application to request that a second agent application on a second client computer system communicate with the server application. Responsive to receiving the first request, a second request is sent by the first agent application to the second agent application on the second client computer system to communicate with the server application.
DYNAMIC PERSONALIZED API ASSEMBLY
Methods, computer readable media, and devices for dynamic personalized API assembly are provided. One method may include receiving a data query from a client by a CDN, parsing the data query to generate a modified data query, transmitting the modified data query to an origin server, receiving a query response from the origin server, generating a modified query response based on the query response, and sending the modified query response to the client. Another method may include receiving an API call by an origin server, generating an API response by creating a payload file and adding markup directives indicating whether content is cacheable, and transmitting the API response.
Identity gray list
Account functionality may be modified in response to an event. A processor may determine that a status of at least one of a user, a device associated with the user, and data associated with the user is potentially insecure due to the event. The processor may identify an account of the user. The account may provide access to electronic financial transaction functionality. In response to the determining that the status of at least one of the user, the device associated with the user, and the data associated with the user is potentially insecure, the processor may modify a condition affecting the access to the electronic financial transaction functionality.
Thin client for mapping system
A method of operating a thin client in a mapping system includes receiving, by the thin client, a map adapter from a map server; loading the map adapter in the thin client, wherein the loaded map adapter comprises a map engine; receiving, by the thin client, map data from the map server; and displaying, by the thin client, the map data in the map engine in the map adapter.
Declarative and reactive data layer for component-based user interfaces
Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.
SERVER, APPARATUS, AND METHOD FOR ACCELERATING FILE INPUT-OUTPUT OFFLOAD FOR UNIKERNEL
Disclosed herein are an apparatus and method for accelerating file I/O offload for a unikernel. The method, performed by the apparatus and server for accelerating file I/O offload for the unikernel, includes; executing, by the apparatus, an application in the unikernal and calling, by the thread of the application, a file I/O function; generating, by the unikernal, a file I/O offload request using the file I/O function; transmitting, by the unikernal, the file I/O offload request to Linux of the server; receiving, by Linux, the file offload request from the thread of the unikernel and processing, by Linux, the file I/O offload request; transmitting, by Linux, a file FO offload result for the file I/O I/O offload request to the unikernel; and delivering the file I/O offload result to the thread of the application.
Method and Devices for Latency Compensation
The invention relates, amongst other things, to a method for operating a client device. If a first operation command is not received from a server device within a predetermined period of time in response to sending at least one first sensor signal, one of a plurality of predictions is selected depending on at least one first sensor signal and/or at least one currently detected sensor signal and a plurality of sensor signal hypotheses and the client device is operated with at least one operation command hypothesis of the selected prediction. The invention also relates, amongst other things, to a method for operating a server device.
METHOD AND SYSTEM FOR MANAGING A MAINTENANCE TASK OF A MOTOR VEHICLE
The invention relates to a distributed system (100) for managing a maintenance task of a motor vehicle and to a method for managing a maintenance task of a motor vehicle implemented by means of such a system.
Context-based notification processing system
In some implementations, a method may involve determining first feature vectors for a plurality of data items accessed by a user of one or more client devices, the first feature vectors representing first contextual data about the one or more client devices at times that respective data items of the plurality of data items were accessed, the plurality of data items including a first data item. A predictive model, configured to classify input feature vectors into context types, may be used to determine that the first feature vector for the first data item is classified as a first context type. A second feature vector representing second contextual data about a first client device operated by the user may be determined and the predictive model may be used to determined that the second feature vector is classified as the first context type. Based at least in part on the first and second feature vectors being classified as the first context type and the first and second data items being of a first data item type, the first client device may be caused to present the second data item.