Haptics API Mapping for Consistent Cross-Device Tactile Feedback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices with different types of haptic actuators produce inconsistent and non-varying haptic outputs, lacking uniformity and qualitative change in tactile quality for the same functionality.
Innovation Solution
A haptics application programming interface (API) provides an abstraction layer to ensure consistent haptic experiences across devices by mapping haptic sharpness and intensity to specific actuator types, using waveforms and intensity envelopes to generate uniform tactile sensations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different types of haptic actuators are used in different electronic devices, then device functionality and haptic variety are improved, but haptic output consistency and uniformity deteriorate
Solution Approach 1:
The patent introduces a haptics API as an intermediary layer between the application and the physical haptic actuator. This API provides a standardized interface that translates high-level haptic commands into device-specific actuator instructions, enabling consistent haptic outputs across different actuator types (ERM, LRA, piezoelectric) while preserving hardware diversity.
2Ease of operation
If simple haptic signaling is used, then ease of operation is improved, but haptic quality variation deteriorates
Solution Approach 1:
The haptics API introduces dynamic control parameters including intensity (0.0-1.0) and sharpness (0.0-1.0) that allow the same basic haptic command to produce varied tactile qualities. The sharpness parameter dynamically adjusts waveform characteristics (sine, square, sawtooth) and frequency content to create different tactile sensations ranging from soft and organic to sharp and precise, enabling rich haptic expression while maintaining simple programming.
Data Source
AI summary
Systems and methods are disclosed defining haptic patterns that include both haptic events and audio events, and optionally include video or animation. The haptic patterns can be called from an application or included as an attachment to a message and played on an electronic device that receives the message. A haptics application programming interface has a haptic experience mapping functionality that generates a same, or similar, haptic experience on different manufacturers or models of electronic devices having different haptic hardware. Haptic patterns can include synchronized haptic and audio events. Haptic event attributes include start time, sharpness, and intensity. Sharpness and/or intensity can be controlled via a parameter envelope for a single event, or for multiple events in a haptic pattern. Sharpness indicates a quality of the tactile sensation of a haptic event, from smooth or rounded, to sharp or precise.