A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. The tool retrieves client connection information from a client request for data. The tool determines, based, at least in part, on the client connection information, a client application's operating system. The tool determines whether the data requested in the client request is BIDI data. Responsive to a determination that the data requested is BIDI data, the tool initiates a layout transformation of the data requested at a single point within the database server. The tool returns transformed BIDI data to the client application.

Systems, methods, and computer-readable media are presented herein for providing lower level physical-layer gateway functionalities and upper-level application functionalities; a system designed with flexible configurations in order to support a wide range of connected applications. The system can include a processor that executes machine instructions to perform operations. The operations can comprise: receiving, from a first device, a first packet representing first data formatted in a first protocol language; transforming the first data to second data formatted in a second protocol language; and transmitting a second packet representing the second data to a second device.

Systems, methods, and computer-readable media are presented herein for providing lower level physical-layer gateway functionalities and upper-level application functionalities; a system designed with flexible configurations in order to support a wide range of connected applications. The system can include a processor that executes machine instructions to perform operations. The operations can comprise: receiving, from a first device, a first packet representing first data formatted in a first protocol language; transforming the first data to second data formatted in a second protocol language; and transmitting a second packet representing the second data to a second device.

A system for processing messages of a high rate data stream and an apparatus including: a message processor including a plurality of processor sub-modules and configured to read an input data stream, process the input data stream, and to output an output data stream; at least one payload memory storing data related to the input data stream and accessible to the message processor; at least one instruction memory accessible to the message processor and storing computer program instructions configuring the message processor to process the input data stream; and an application processor configured to rewrite the at least one instruction memory.

Embodiments of the present disclosure provide for improved interoperable data management between a user-accessed software application and an embedded software application. In some contexts, a user-accessed application provides both its own functionality as well as enabling access to functionality of an embedded application. The embedded application is accessed via a data-driven connection that provides several technical advantages and addresses various data interoperability and persistence problems. In some embodiments, a user-accessed application may be configured to provide functionality of multiple embedded applications consistent with the innovations herein described.

Embodiments of the present disclosure provide for improved interoperable data management between a user-accessed software application and an embedded software application. In some contexts, a user-accessed application provides both its own functionality as well as enabling access to functionality of an embedded application. The embedded application is accessed via a data-driven connection that provides several technical advantages and addresses various data interoperability and persistence problems. In some embodiments, a user-accessed application may be configured to provide functionality of multiple embedded applications consistent with the innovations herein described.

Provided are methods, systems, devices, and tangible non-transitory computer readable media for providing data including vehicle map service data. The disclosed technology can perform operations including receiving vehicle map service data from a plurality of service systems that include a plurality of client systems associated with a vehicle. The vehicle map service data can include information associated with a geographic area. A local map of the geographic area within a predetermined distance of the vehicle can be generated based on the vehicle map service data. Portions of the local map to which each client system is subscribed can be determined for each client system of the plurality of client systems. Additionally, the portions of the local map to which each client system is subscribed can be sent to a respective client system of the plurality of client systems.

Provided are methods, systems, devices, and tangible non-transitory computer readable media for providing data including vehicle map service data. The disclosed technology can perform operations including receiving vehicle map service data from a plurality of service systems that include a plurality of client systems associated with a vehicle. The vehicle map service data can include information associated with a geographic area. A local map of the geographic area within a predetermined distance of the vehicle can be generated based on the vehicle map service data. Portions of the local map to which each client system is subscribed can be determined for each client system of the plurality of client systems. Additionally, the portions of the local map to which each client system is subscribed can be sent to a respective client system of the plurality of client systems.

An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.

An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.