Vehicle Communication System With Distributed Data Space
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle communication systems require significant memory space and code duplication due to the need for separate interfaces and services for each data exchange, lacking flexibility and efficiency.
Innovation Solution
A vehicle communication system utilizing a distributed data space with in-memory databases and self-describing binary formats, enabling unified access and reducing the need for custom interfaces by using a standardized CRUD interface and timestamp attributes for synchronization and data expiration strategies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate services and interface objects are created for each data exchange between processing units, then communication functionality is achieved, but memory space and code size increase significantly
Solution Approach 1:
The patent implements a universal data access mechanism where a single standardized interface (e.g., publish-subscribe pattern) serves multiple processing units and data types. Instead of creating dedicated service objects for each processing unit pair, a universal interface handles all data exchanges, allowing one interface implementation to serve multiple functions across different processing units and data streams.
Solution Approach 2:
The patent merges multiple separate service interfaces into a unified data access layer. Rather than having individual service objects for each processing unit combination, the system combines all data access operations through a single standardized interface that handles publishing, subscribing, and data retrieval operations centrally, reducing the number of interface objects needed.
2Adaptability or versatility
If custom interfaces are created for each service, then specific data exchange requirements are met, but code redundancy increases
Solution Approach 1:
The patent employs a universal standardized interface that can handle diverse data exchange requirements through configuration rather than custom code. The publish-subscribe mechanism provides a single interface pattern that adapts to different data types, processing units, and communication scenarios without requiring separate custom interface implementations for each case.
Solution Approach 2:
The system achieves adaptability for different data exchange scenarios by changing parameters (data types, subscription filters, processing unit identifiers) within a single interface framework, rather than creating different interface classes. The standardized interface accepts various parameters to accommodate different service requirements while maintaining a single codebase.
3Ease of operation
If multiple processing units access data through separate services, then data access is achieved, but system complexity and code maintenance difficulty increase
Solution Approach 1:
The patent implements a universal data access layer using publish-subscribe semantics that serves all processing units uniformly. Instead of requiring each processing unit to have its own service access code, all units interact with the same standardized interface, simplifying data access operations and reducing system complexity.
Solution Approach 2:
The standardized interface acts as an intermediary layer between processing units and the data exchange mechanism. This mediator handles all data publishing and subscription operations centrally, shielding processing units from the complexity of direct data exchange implementation and providing a simplified, uniform access method for all units.
Data Source
Figure 1
AI summary
The invention describes a vehicle communication system (1). The vehicle communication system (1) comprises a communication network, a plurality of processing units (10, 20, 30) being connected via the communication network with each other for transmitting and receiving data between them, each of the processing units (10, 20, 30) being either one of a first type processing unit implementing a data consuming application (12, 32), a second type processing unit providing data to other of the processing units (10, 20, 30), or a third type processing unit implementing a data consuming application (12, 32) and providing data to other of the processing units (10, 20, 30). Furthermore, it comprises a plurality of data providers (51-55), each of the data providers (51-55) being connected to a respective second type processing unit or a respective third type processing unit and providing respective data values (d(51)-d(55)) to the associated processing unit (20, 30). The second type processing unit and the third type processing unit are, upon receiving a data value (d(51)-d(55)) from an associated data provider (51-55), configured to convert the data value (d(51)-d(55)) into a self-describing binary format to add a timestamp attribute to the converted data value (d(51)-d(55)), the timestamp attribute comprising an absolute time information indicating an expiry of the data value (d(51)-d(55)) and/or indicating the time of creation of the data value (d(51)-d(55)), and to store the converted data value with timestamp attribute in a distributed data space, wherein the distributed data space comprises a set of in-memory databases (23, 33) of (d(51)-d(55)) second type processing unit and (d(51)-d(55)) third type processing unit (20, 30). The data consuming application (12, 32) of a respective second type processing unit and/or of a respective third type processing unit (20, 30) is adapted to access the converted data value (dc(51)-dc(55)) in the distributed data space via a predetermined standardized interface.