Vehicle Touch Screen Control Field Display Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to ensure that graphical control fields are correctly displayed on touch screens in motor vehicles, as they can be overlaid by other applications, and lack verification logic to confirm the display content.

Innovation Solution

An electronic control unit generates and verifies render data for a control field, using checksums to ensure that the touch screen input device correctly displays the graphical content by comparing calculated checksums from both the control unit and the render monitoring unit.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a control field is displayed on a graphical user interface, then the user can interact with vehicle functions, but the control field may be covered or overwritten by other applications

Engineering Contradiction:
Improveuser interaction capabilityVSAvoiddisplay accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the control unit receives confirmation from the touch screen input device about whether the control field is actually displayed. The touch screen input device monitors its own display output and sends status information back to the control unit, allowing the system to detect when a control field has been covered or not rendered correctly, and respond appropriately by redisplaying or alerting the user.

Inventive Principle:
Principle #23Feedback

2Productivity

If pixel data is set for displaying graphical content, then the graphical interface can be updated, but the pixel data may be disturbed or overwritten by other applications

Engineering Contradiction:
Improveinterface update speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The touch screen input device includes a monitoring function that continuously checks whether pixel data intended for display has been correctly rendered or if it has been overwritten. This feedback loop allows the system to detect display conflicts in real-time and take corrective action, maintaining data integrity while allowing rapid interface updates.

Inventive Principle:
Principle #23Feedback

3Device complexity

If no verification logic is implemented, then the system remains simple, but there is no way to confirm correct display content

Engineering Contradiction:
Improvesystem simplicityVSAvoiddisplay verification capability
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The touch screen input device performs self-verification by monitoring its own display output. The device includes internal logic that checks whether the graphical content it is supposed to display is actually being rendered correctly, without requiring external verification systems. This self-service approach adds verification capability while minimizing additional system complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3796147B1Method for coordinating an electronic control unit and a touch screen input device in a motor vehicle and vehicle operating apparatus and motor vehicle
Publication Date: 2021.11.10 AUDI AG
  • EP3796147B1 patent drawingFigure 1

AI summary

The invention is concerned with a method for coordinating an electronic control unit (16) and a touch screen input device (13) in a motor vehicle (10), wherein the electronic control unit (16) operates a graphical user interface (GUI) with a control field (15) and wherein a render monitoring unit (20) of the touch screen input device (13) controls a touch screen display (14) for displaying the graphical user interface (GUI). The method is characterized in that the control unit (16) receives second checksum data (27) from the render monitoring unit (20), the second checksum data (27) representing actually displayed pixel data (24) of the control field (15), and compares the received second checksum data (27) with first checksum data (29), the first checksum data (29) representing render instructions for the control field (15), and, if the checksum data (27, 29) differ, the control unit (16) generates an error signal (30).