Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

Techniques for transaction tracking for a high availability architecture are described herein. An aspect includes receiving a first request from a client, the first request corresponding to a start of a transaction having transaction affinity. Another aspect includes, based on receiving the first request from the client, generating a transaction tracking token. Another aspect includes sending the first request with the transaction tracking token to a gateway. Another aspect includes receiving a first response corresponding to the first request from the gateway, the first response including middleware instance information corresponding to a middleware instance, wherein a plurality of subsequent requests from the client corresponding to the transaction are processed by the middleware instance corresponding to the middleware instance information.

In an aspect of the present disclosure, there is provided a road side apparatus configured to relay a message. The apparatus may include a memory, a processor, and a transceiver. The processor may be configured to: check whether an identifier received together with a received message is previously stored; when the identifier is stored, replace a personal safety message (PSM) corresponding to the identifier in a pair of the PSM and the identifier with a PSM included in the received message and the store the PSM; when a timer for batch transmission expires or when a total size of stored PSMs exceeds a predetermined value, generate one batch message including all PSMs in stored pairs of PSMs and identifiers; and transmit the generated batch message. The identifier may be information for identifying a transmitter that transmits the message.

The invention is that of systems and methods for controllerless and distributed network connections to servers on a network by remote clients seeking their services. The invention comprises a central database where servers within a server group identified by a group name may post unique identifiers (UIDs) for retrieval by group clients configured with the group name, which may query the central database for server connection information such as uptime, downtime, and congestion in order to select a server for a preferential connection based on an overall availability profile as determined by the group client. In some embodiments, one server of the group is a “dummy server” that may aggregate and selectively transmit server information from other servers in the group, or other devices, and posts it to the central database for client access. The methods described herein eliminate a separate controller and thereby a single point of failure (SPOF).

The invention is that of systems and methods for controllerless and distributed network connections to servers on a network by remote clients seeking their services. The invention comprises a central database where servers within a server group identified by a group name may post unique identifiers (UIDs) for retrieval by group clients configured with the group name, which may query the central database for server connection information such as uptime, downtime, and congestion in order to select a server for a preferential connection based on an overall availability profile as determined by the group client. In some embodiments, one server of the group is a “dummy server” that may aggregate and selectively transmit server information from other servers in the group, or other devices, and posts it to the central database for client access. The methods described herein eliminate a separate controller and thereby a single point of failure (SPOF).

An aspect of the invention provides a method of performing a distributed task over a network comprising a plurality of nodes. The method comprises: a plurality of network nodes observing (300) data; applying a first linear code function to the data observed by at least one network node of the plurality of network nodes to obtain (302) at least one function output; applying errors (304) to the at least one function output; a query node selected from the network nodes performing (308) a mixing procedure to aggregate node observations to obtain a first set of aggregated values until a stopping criteria (306) is satisfied; applying (312) a second linear code function to the set of aggregated values to obtain a second set of aggregated values returned to their observed domain; and the query node outputting (314) the second set of aggregated values.

Provided are a method and device for generating a notification and a method and device for subscribing a notification message. The method for generating a notification (300) includes: receiving a subscription request (S310); creating a first subscription resource according to the subscription request, the first subscription resource including a plurality of first event notification criteria and a second event notification criterion (S320); receiving a plurality of first events generated according to the plurality of first event notification criteria (S330); determining whether the plurality of first events satisfy the second event notification criterion (S340); and generating a notification in a case where the plurality of first events satisfies the second event notification criterion, the notification indicating a second event (S350).

Provided are a method and device for generating a notification and a method and device for subscribing a notification message. The method for generating a notification (300) includes: receiving a subscription request (S310); creating a first subscription resource according to the subscription request, the first subscription resource including a plurality of first event notification criteria and a second event notification criterion (S320); receiving a plurality of first events generated according to the plurality of first event notification criteria (S330); determining whether the plurality of first events satisfy the second event notification criterion (S340); and generating a notification in a case where the plurality of first events satisfies the second event notification criterion, the notification indicating a second event (S350).

Apparatuses, systems, and techniques are directed to automatic coalescing of GPU-initiated network communications. In one method, a communication engine receives, from a shared memory application executing on a first graphics processing unit (GPU), a first communication request assigned to or having a second GPU as a destination to be processed. The communication engine determines that the first communication request satisfies a coalescing criterion and stores the first communication request in association with a group of requests that have a common property. The communication engine coalesces the group of requests into a coalesced request and transports the coalesced request to the second GPU over a network.

The described technology is directed towards locating and using a template for processing data item data from a general form into a client-specific form for returning in response to a client request. A client request includes a data item identifier and client-specific information. The data item's identifier is processed into a data type and/or identifier, e.g., a string. The client-specific information is used to determine a device class, device type and/or client platform software version. The template is found in a hierarchy of templates based upon the client-specific information and the data type or data ID string, e.g., the client-specific information may be used to determine a subset of template folders that is evaluated to find a file with a filename matching the string. The folders may be ordered from most-specific to least-specific, so as to locate the most specific template file that applies.