Compiler-Based Data Processing for Platform-Independent Serialization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for processing data associated with computer programs, such as those in vehicles, are invasive and require meta-models, leading to increased effort and inefficiencies in serialization and transmission.

Innovation Solution

A non-invasive method using compiler operators and macros to determine and encode information about data elements, such as size and alignment, without requiring meta-models, enabling efficient serialization and transmission across platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If conventional methods are used for data serialization, then data can be transmitted and stored, but the process requires meta-models and code modifications which increase complexity and effort

Engineering Contradiction:
Improveease of serializationVSAvoidcomplexity of serialization process
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system uses self-descriptive data structures where the data carries its own type information and formatting requirements inherently, eliminating the need for external meta-models. The serialization process automatically determines how to handle data based on embedded type descriptors within the data structures themselves.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Type descriptors act as intermediaries between the data and the serialization process, providing all necessary information about data structure, size, and formatting requirements without requiring separate meta-models or code modifications. These descriptors enable the serialization system to adapt to different data types automatically.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If meta-models are used to interpret data elements, then data can be processed across platforms, but the effort and overhead increase significantly

Engineering Contradiction:
Improveplatform independenceVSAvoidtime for data processing
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

All necessary information for cross-platform data interpretation is prepared in advance and embedded within the type descriptors during data structure definition. This preliminary encoding of size, alignment, and formatting information eliminates the need for runtime meta-model interpretation, enabling fast platform-independent processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The essential type information is extracted from complex meta-models and condensed into compact type descriptors that contain only the necessary information for serialization and interpretation. This extraction reduces processing overhead while maintaining platform independence.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If data structures are serialized with full type information, then accuracy is maintained, but data transmission size increases

Engineering Contradiction:
Improvedata interpretation accuracyVSAvoiddata transmission size
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The type descriptors are designed as lightweight, minimal-structure objects that contain only the essential information needed for data interpretation. Rather than using comprehensive meta-models, the system employs these compact descriptors that are sufficient for accurate reconstruction of data structures during deserialization.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentEP4607337A1Method and device for processing data
Publication Date: 2025.08.27 ROBERT BOSCH GMBH
  • EP4607337A1 patent drawingFigure 1~2
  • EP4607337A1 patent drawingFigure 3~4
  • EP4607337A1 patent drawingFigure 5~7

AI summary

Method for processing data associated with a data element for a computer program, for example for a product such as a vehicle, comprising: determining first information characterizing at least one of the following elements: a) size of at least one data type associated with the data element, for example atomic, or b) orientation of at least one data type associated with the data element, for example atomic, providing the first information.