Vehicle Container Activation for Integrating New Sensor-Driven Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional head-up displays (HUDs) in vehicles lack real-time interaction with the driver's field of view and do not effectively utilize vehicle sensor data, and the integration of augmented reality HUDs requires stable data collection and authority settings that are not adequately addressed by existing vehicle network interfaces.
Innovation Solution
A method for activating new devices in vehicles using a data-centered architecture, where a container is requested from a server to control the new device's execution, leveraging vehicle and cloud-provided information without direct vehicle network access, and applying update patterns based on device associations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new device is added to the vehicle, then the functionality and adaptability of the vehicle system is improved, but the device complexity and integration difficulty increase
Solution Approach 1:
The patent segments the new device into a container that can be independently activated and managed. The container encapsulates the device's functionality and data requirements, allowing it to be added to the vehicle system without complex integration with existing components. The container manager handles the activation and data collection separately from other vehicle systems.
Solution Approach 2:
The patent introduces a container manager as an intermediary component that mediates between the new device (container) and the vehicle's existing data collection infrastructure. The container manager requests and collects sensor data from other vehicles or infrastructure through defined interfaces, avoiding direct complex integration between the new device and multiple existing systems.
2Ease of operation
If direct network access is used for data collection, then the ease of operation and data accessibility are improved, but the system stability deteriorates
Solution Approach 1:
The container manager acts as an intermediary that handles all data collection requests. Instead of the new device directly accessing vehicle networks or external systems, the container manager manages these connections, requests sensor data through defined interfaces, and provides data to the container. This maintains ease of data accessibility while preserving system stability through controlled access.
Solution Approach 2:
The container is designed to be self-contained with its own activation and data processing logic. The container manager activates the container and provides necessary data without requiring the container to directly interface with complex vehicle networks. This self-service approach simplifies operation while maintaining stability by isolating the new device from potential instability sources in the vehicle network.
3Device complexity
If conventional HUD methods are used, then the device complexity is reduced, but the measurement precision and real-time interaction capability deteriorate
Solution Approach 1:
The patent segments the HUD functionality into a container that can be independently activated. This container includes the specific algorithms and processing logic for augmented reality head-up display, allowing real-time interaction capabilities to be implemented without complicating the overall vehicle system. The containerized approach enables precise real-time processing while maintaining system simplicity through modular design.
Data Source
AI summary
A method of activating a new device in a vehicle based on a container includes: detecting the new device mounted in the vehicle using an interface implemented in the vehicle, identifying the detected new device, transmitting, to a server, (i) a request for a container for controlling an execution of the identified new device and (ii) information obtained by one or more sensors implemented in the vehicle, receiving, from the server, a container package including at least one container that is retrieved in the server in response to the request for the container, and controlling the execution of the new device by activating the at least one container.