Data Broker Gateway for Low-Latency Certified App Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The transportation industry, particularly in aviation, faces challenges with the integration of uncertified applications with certified applications, including data source dependencies, maintenance issues, and high latency due to inefficient data transfer and server interactions.
Innovation Solution
A vehicle electronics data broker gateway is introduced to facilitate seamless information exchange between certified and uncertified applications through APIs, utilizing configuration files, source selection, data abstraction, caching, and predictive data fetching mechanisms to manage data flow efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If uncertified applications directly interact with certified applications, then data exchange functionality is achieved, but system complexity and maintenance difficulty increase
Solution Approach 1:
The patent introduces a data broker as an intermediary component that sits between certified and uncertified applications. The data broker receives data from certified applications via the avionics bus and makes it available to uncertified applications through standardized APIs, eliminating direct interactions and reducing system complexity.
Solution Approach 2:
The system is segmented into distinct layers: the certified application layer communicating with the data broker, and the uncertified application layer accessing data through the broker. This segmentation allows independent development, deployment, and maintenance of each layer without affecting the other.
2Reliability
If multiple data sources are used for redundancy, then data availability is improved, but client application complexity increases
Solution Approach 1:
The data broker acts as a centralized intermediary that manages multiple data sources and redundancy logic. Client applications interact only with the broker through standardized APIs, while the broker handles source selection, failover, and redundancy management internally, keeping client applications simple.
Solution Approach 2:
The data broker provides universal access to multiple data sources through a single standardized interface. It consolidates the functionality of managing redundant sources, selecting optimal sources, and handling failures into one multi-functional component that serves all client applications.
3Productivity
If client applications directly request data from server applications, then data access is achieved, but latency increases due to multiple slow-speed elements
Solution Approach 1:
The data broker pre-fetches and caches data from certified applications before uncertified applications need it. By anticipating data requests and preparing data in advance, the broker reduces latency when uncertified applications need to access the data through the bus.
Solution Approach 2:
The data broker mediates data access by maintaining cached copies of data from certified applications. When uncertified applications request data, the broker can serve it from cache without requiring real-time access through the slow avionics bus, significantly reducing latency.
4Adaptability or versatility
If all client applications interact directly with server applications, then data exchange is achieved, but bus traffic and server performance are degraded
Solution Approach 1:
The data broker consolidates multiple client requests and serves data from its cache, reducing the number of individual transactions on the avionics bus. Instead of each client application directly querying server applications, the broker handles data distribution centrally, minimizing bus traffic.
Solution Approach 2:
The data broker merges multiple data access operations into centralized data collection and caching operations. By consolidating data retrieval at the broker level and serving multiple clients from cached data, the system reduces overall bus traffic and improves efficiency.
Data Source
AI summary
A system for information exchange comprises a vehicle electronics data broker gateway for exchanging information between vehicle electronics certified applications and uncertified applications. The data broker gateway comprises configuration files generated with a dedicated modeling tool; a source selection module operative to seamlessly choose a best data source; a source abstraction and data collection module operative to receive data from the data source; a data conversion module operative to convert the data received into a standard format; a data cache operative to store the data received before transmitting the data; and a client abstraction and data dispatch module operative to transmit the data to the client. The data broker gateway also includes a data pre-fetch module comprising a rule based engine operative to determine a time to pre-fetch data based on pre-defined rules; and a machine learning based engine operative to learn data fetching conditions for a given data source.