Object Warehousing for Intermittent Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information exchange systems are inflexible and struggle with intermittent connectivity, changing addresses, namespace mismatches, and varying communication mediums, particularly in environments like mobile vehicles where traditional data distribution models are not applicable.
Innovation Solution
An object warehousing system that includes a transport controller for managing data distribution and a rule engine for executing policies, allowing for flexible data exchange by storing and retrieving data objects based on attributes and policies, supporting various communication mediums and security protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a traditional data distribution model is used, then information exchange works in stable environments with unified namespace and fixed addresses, but it fails in mobile systems with intermittent connectivity and changing addresses
Solution Approach 1:
The patent introduces an object warehouse as an intermediary component between sender and receiver. The warehouse stores data objects with associated transport attributes (addresses, namespaces, distribution policies) and handles the complexity of delivery. This mediator allows senders to deposit objects without knowing recipient availability, while recipients can retrieve objects using persistent identifiers, solving the contradiction between reliable exchange and mobile adaptability.
Solution Approach 2:
The system performs preliminary actions by pre-storing data objects in the warehouse with all necessary transport metadata before actual retrieval. Transport attributes including addresses, namespaces, and distribution policies are established in advance, allowing the system to handle intermittent connectivity and address changes without requiring real-time coordination between sender and receiver.
2Loss of time
If buffering systems are used for information exchange, then time-displaced sending and retrieving is enabled, but the system becomes rigidly tied to underlying implementation details
Solution Approach 1:
The patent segments the information exchange system into distinct functional components: the object warehouse for storage, transport attributes for metadata, and distribution policies for delivery logic. This segmentation allows the buffering function to be separated from implementation details, enabling time-displaced exchange while maintaining system flexibility through independent, interchangeable components.
Solution Approach 2:
The object warehouse serves multiple functions: storing data objects, managing transport attributes, enforcing distribution policies, and handling various communication mediums. This universal component replaces multiple specialized buffering systems, reducing rigidity while maintaining time displacement capability across different scenarios.
3Reliability
If existing buffering solutions are implemented, then information can be exchanged without direct communication links, but namespace mismatches and communication medium differences cannot be handled
Solution Approach 1:
The system uses transport attributes as configurable parameters that adapt to different namespaces and communication mediums. Distribution policies can be modified based on the specific communication medium being used, allowing the same object warehouse to handle diverse exchange scenarios without requiring direct communication links between sender and receiver.
Data Source
AI summary
Embodiments of the present invention improve information exchange, and in particular, the exchange of data objects between different software systems. In one embodiment, the present invention includes a method of exchanging information comprising receiving a first transport request, the transport request comprising one or more first transport attributes, wherein the one or more first transport attributes are associated with a first data object, storing the one or more first transport attributes and the first data object or a reference to the first data object in a repository, receiving a second transport request, the second transport request comprising one or more second transport attributes, and executing an algorithm for generating a response to the second transport request based on the first or second transport attributes.