Vehicle Browser Rendering Mobile Apps via HTML5
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current in-vehicle integration systems, such as MirrorLink, face challenges including display resolution mismatches between mobile devices and vehicle infotainment systems, high data transfer requirements, and the need for app developers to create multiple versions for different vehicle brands, leading to a poor user experience and reduced compatibility.
Innovation Solution
The system sends user interface code to the vehicle's browser application, using HTML5 and Cascading Style Sheets, allowing the same interface code to be rendered on both the mobile device and vehicle display, eliminating the need for additional coding and enabling vehicle manufacturers to control the look and feel, thus improving app integration and compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MirrorLink integration is used, then in-vehicle access to mobile device functions is enabled, but display resolution mismatches occur between mobile devices and vehicle infotainment systems
Solution Approach 1:
The patent changes the display parameters by sending user interface code with embedded style information (Cascading Style Sheets) that defines how the interface should be rendered. This allows the same interface code to be adapted to different display resolutions and characteristics, resolving the contradiction between display compatibility and resolution matching.
2Adaptability or versatility
If multiple app versions are created for different vehicle brands, then brand-specific interfaces are achieved, but development complexity and costs increase
Solution Approach 1:
The patent implements universality by creating a single app version that can operate across multiple vehicle brands. The user interface code includes embedded style information that allows it to adapt to different vehicle brand requirements, eliminating the need to create separate app versions for each brand while still achieving brand-specific interface customization.
Solution Approach 2:
The patent introduces an intermediary layer (the browser application on the vehicle infotainment system) that renders the user interface code. This intermediary handles the adaptation to different vehicle brands, allowing the app itself to remain universal while still providing brand-specific interfaces through the rendering process.
3Manufacturing precision
If high data transfer is used to ensure proper display rendering, then display quality is improved, but data transfer requirements and bandwidth consumption increase
Solution Approach 1:
The patent uses copying by sending user interface code that describes the interface structure and style information, rather than transferring complete rendered images or high-fidelity display data. The vehicle's browser application then renders the interface locally based on this code, achieving proper display rendering quality while minimizing data transfer volume.
Data Source
AI summary
In-vehicle access of mobile device functions is provided wherein a vehicle is coupled to the mobile device, and obtains a list of apps installed thereon. A user manipulates vehicle controls to operate a select app and the vehicle modifies its display based on the app.