Synthetic Sensor Orchestration for Cross-Domain Vehicle Data Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern vehicles face challenges in sharing electronic sensor data across different operating systems or domains due to varying certification requirements and fixed algorithms, making it burdensome to update or deploy new applications that utilize relationships between existing sensor data.
Innovation Solution
A synthetic sensor service and orchestration environment that allows for the deployment of synthetic sensors across vehicles, enabling data flow between domains and allowing new logical code to determine outputs from existing sensor data, without altering existing code or degrading certification levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fixed control algorithms and fixed rules for sharing electronic sensor data are used, then system reliability is maintained, but adaptability deteriorates
Solution Approach 1:
The system segments sensor data sharing into separate domains (safety domain and non-safety domain) with different certification requirements. Each domain operates independently with its own control algorithms, allowing updates in the non-safety domain without affecting the certified safety domain. This enables new applications to be deployed in the entertainment operating system domain without altering or degrading the certification levels of the safety operating system domain.
Solution Approach 2:
A domain gateway acts as an intermediary between the safety operating system domain and the entertainment operating system domain. The gateway enables controlled data sharing between domains while maintaining isolation, allowing sensor data to flow between domains through defined interfaces without compromising the certification integrity of either domain.
2Reliability
If independent operating system domains are used, then certification requirements are met, but information sharing deteriorates
Solution Approach 1:
The domain gateway serves as an intermediary that enables information sharing between independent operating system domains. It provides controlled access to sensor data across domain boundaries, allowing the entertainment operating system domain to access sensor information from the safety operating system domain through defined interfaces, thereby reducing information loss while maintaining domain independence and certification requirements.
Solution Approach 2:
The domain gateway provides universal access to sensor data across multiple domains through a standardized interface. It enables different types of data sharing (read access, write access, controlled access) while maintaining the independence of each domain, allowing sensor information to be universally accessible to authorized components across domain boundaries.
3Stability of the object's composition
If fixed rules for data sharing are used, then system stability is maintained, but ease of operation deteriorates
Solution Approach 1:
The system segments the operating system into multiple independent domains with fixed data sharing rules within each domain. This allows the entertainment operating system domain to be updated and modified without affecting the stability of the safety operating system domain. The fixed rules are maintained at the domain level, while flexibility is provided through the ability to add new domains or modify non-critical domains.
Solution Approach 2:
While maintaining fixed data sharing rules for stability, the system enables dynamic addition of new domains and modification of existing non-critical domains. The domain gateway provides dynamic data routing capabilities, allowing new applications and sensors to be integrated without changing the fundamental fixed rules that ensure system stability.
Data Source
AI summary
A system comprising one or more computers implements a synthetic sensor service configured to deploy synthetic sensors to an in-vehicle computing device implementing a synthetic sensor orchestration environment for a vehicle. The synthetic sensor orchestration environment determines a placement decision for a new synthetic sensor to be added to the vehicle based on one or more annotations included in a synthetic sensor package for the new synthetic sensor. The synthetic sensor service and respective synthetic sensor orchestration environments implemented in various types of vehicles provide a consistent way to remotely add additional synthetic sensors and/or other functionality to different types of vehicles after the vehicles have already been put in use by respective owners or operators of the vehicles.