Touch Interaction Mediator for Embedded Views in Vehicle Displays

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a desktop framework architecture of a vehicle display system, embedded views such as Android views within Unity views cannot respond to touch events, limiting the provision of complete functions.

Innovation Solution

A method and device for implementing touch interaction that involves presenting views on a touch display screen, determining the type and proportional coordinates of touch events within an embedded view, and generating operation instructions to respond to these events through interprocess communication, allowing complete interaction capabilities within a multi-application-view embedded architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If an embedded view is used for display purposes, then the display function is achieved, but the touch interaction function is lost

Engineering Contradiction:
Improvedisplay functionVSAvoidtouch interaction function
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

The patent introduces an intermediary mechanism (the first application acting as a mediator) that receives touch events from the touch display screen, determines whether they occur within the embedded view's region, calculates proportional coordinates, and forwards them to the second application. This mediator enables the embedded view to receive and respond to touch events without requiring direct integration of touch handling capabilities into the embedded view itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the touch event handling process into distinct functional components: (1) touch event detection by the first application, (2) coordinate transformation and proportional coordinate calculation, (3) event type determination, and (4) event forwarding to the second application. This segmentation allows each component to perform its specific function independently, enabling the embedded view to maintain its display-only architecture while still achieving touch interaction capability through the coordinated action of these segmented functions.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If coordinate transformation is performed between different view frameworks, then accurate touch event mapping is achieved, but processing complexity increases

Engineering Contradiction:
Improvetouch event mapping accuracyVSAvoidcoordinate transformation processing
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent changes the parameter representation from absolute coordinates in the first view's coordinate system to proportional coordinates (normalized values between 0 and 1) that represent the relative position within the embedded view's region. This parameter transformation simplifies the coordinate mapping process by eliminating the need to handle different coordinate system offsets and scales, while still maintaining precise touch event mapping accuracy across different view frameworks.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4421606A1Method for implementing touch interaction, and touch interaction device
Publication Date: 2024.08.28 NIO TECH ANHUI CO LTD
  • EP4421606A1 patent drawingFigure 1~2
  • EP4421606A1 patent drawingFigure 3
  • EP4421606A1 patent drawingFigure 4

AI summary

The disclosure relates to computer interaction technologies, and specifically to a method for implementing touch interaction, and a touch interaction device for implementing this method. According to an aspect of the disclosure, the method for implementing touch interaction includes: presenting a first view and a second view on a touch display screen by a first application and a second application, respectively, where the second view is an embedded view of the first view; in response to a touch event occurring within a region in the first view that corresponds to the second view, determining, by the first application, the type of the touch event and proportional coordinates of the touch event within the second view; sending, by the first application, the type and the proportional coordinates to the second application; and generating, by the second application and based on the type and the proportional coordinates, an operation instruction to respond to the touch event.