A multitenant infrastructure server (MTIS) is configured to provide an environment to execute a computer routine of an arbitrary application. The MTIS receives a request from a webtask server to execute the computer routine in a webtask container. The computer routine is executed in the webtask container at the MTIS. Upon successful execution of the computer routine, a result set is returned to the webtask server. If the execution of the computer routine is unsuccessful, an error notification is returned to the webtask server. The resources consumed during the execution of the computer routine are determined. The webtask container is destroyed to prevent persistent storage of the computer routine on the MTIS.

Described is an improved approach to implement fast detection of node death. Instead of just relying on multiple heart beats to fail in order to determine whether a node is dead, the present approach performs an on demand validation using RDMA to determine whether the node is reachable, where the approach of using RDMA is significantly faster than the heartbeat approach.

Approaches for data processing are disclosed that include receiving, from a client, an application programming interface (API) request at an API endpoint of an API, where the API endpoint is configured to process data requests at a data plane of the API, identifying, from a header of the API request, a request for metadata associated with the API, redirecting the API request to a metadata plane of the API, retrieving, at the metadata plane of the API, the requested metadata based on the header of the API request, and transmitting, via the API endpoint and to the client, a response message indicating the requested metadata.

Approaches for data processing are disclosed that include receiving, from a client, an application programming interface (API) request at an API endpoint of an API, where the API endpoint is configured to process data requests at a data plane of the API, identifying, from a header of the API request, a request for metadata associated with the API, redirecting the API request to a metadata plane of the API, retrieving, at the metadata plane of the API, the requested metadata based on the header of the API request, and transmitting, via the API endpoint and to the client, a response message indicating the requested metadata.

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.

A computing device may be configured to provide a shared N4 termination function for a plurality of Session Management Function (SMF) instances of an SMF Set and interface with one or more User Plane Function (UPF) instances. To achieve this, the computing device may operate a server configured with a Remote Procedure Call (RPC)-based protocol (e.g. gRPC Remote Procedure Call or “gRPC”) for a Packet Forwarding Control Protocol (PFCP) message service for serving a plurality of client stubs respectively situated at the plurality of SMF instances. The server may perform processing associated with each client stub by receiving an RPC-based protocol message which indicates a request, unpacking the RPC-based protocol message for obtaining PFCP message request data, and operating or interfacing with a PFCP message handling client for sending a PFCP message having the PFCP message request data to an indicated one of the UPF instances.

A computing device may be configured to provide a shared N4 termination function for a plurality of Session Management Function (SMF) instances of an SMF Set and interface with one or more User Plane Function (UPF) instances. To achieve this, the computing device may operate a server configured with a Remote Procedure Call (RPC)-based protocol (e.g. gRPC Remote Procedure Call or “gRPC”) for a Packet Forwarding Control Protocol (PFCP) message service for serving a plurality of client stubs respectively situated at the plurality of SMF instances. The server may perform processing associated with each client stub by receiving an RPC-based protocol message which indicates a request, unpacking the RPC-based protocol message for obtaining PFCP message request data, and operating or interfacing with a PFCP message handling client for sending a PFCP message having the PFCP message request data to an indicated one of the UPF instances.

A system and method are provided for providing personalized notifications in mobile applications. The method includes receiving from an enterprise system, transactional activity data associated with a user of a client device; and receiving from at least one loyalty system, loyalty data associated with loyalty offers eligible to the user of the client device. The method also includes analyzing the activity data and the loyalty data to correlate at least one spending indicator from the activity data with at least one of the eligible loyalty offers and generating a personalized notification based on a correlation determined from the analyzing. The method also includes integrating the personalized notification into a graphical user interface of a mobile application provided by the enterprise system, receiving an indication of the selected loyalty offer, and sending to the corresponding loyalty system, an instruction to execute the selected eligible loyalty offer.

The present disclosure relates to systems and methods for providing cloud-based services securely to on-premises networks or other infrastructure. More particularly, the present disclosure relates to systems and methods for enriching first-party data (e.g., data collected directly by an on-premises server) stored within on-premises networks by enabling the on-premises networks to retrieve and process third-party data stored on cloud-based networks. As a technical benefit, cloud-based services can be performed on the first-party data within the on-premises networks.