Voice Command Matching for Non-Phonetic Languages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional design tools fail to support the design and testing of voice-assisted application prototypes, especially for languages with non-phonetic alphabets, leading to high matching errors during voice command testing.
Innovation Solution
A voice interaction tool is developed that includes a phonetic language translator to convert non-phonetic voice commands into phonetic text strings, enabling accurate matching and execution of voice commands in languages like Mandarin Chinese and Japanese by translating them into phonetic alphabets such as Pinyin or Romaji, allowing for real-time comparison and action performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If voice command matching is performed directly using non-phonetic alphabets (e.g., Chinese characters, Japanese Kanji), then the system can support languages with non-phonetic alphabets, but the matching accuracy deteriorates significantly due to high error rates
Solution Approach 1:
The patent introduces a phonetic alphabet as an intermediary representation layer between the non-phonetic input alphabet and the voice command matching system. Non-phonetic characters are first transcribed into phonetic alphabets (e.g., Pinyin for Chinese, Romaji for Japanese), which then serve as the basis for accurate pattern matching. This intermediary step preserves language versatility while enabling reliable voice command recognition through phonetic equivalence.
Solution Approach 2:
The patent transforms the representation parameter of voice commands from non-phonetic character forms to phonetic alphabet forms. By changing the parameter from visual character representation to phonetic sound representation, the system maintains adaptability to multiple languages while achieving consistent and accurate matching based on pronunciation rather than character form.
2Ease of operation
If conventional design tools are used for application prototype testing, then the design process is simple and familiar, but voice functionality testing is not supported at all
Solution Approach 1:
The patent extends the functionality of conventional design tools by integrating voice command recognition and testing capabilities into the existing prototype design workflow. The system allows designers to define voice commands using phonetic alphabets and test them within the same environment where visual interface design is performed, making the design tool universal for both traditional and voice-based interaction design without requiring separate specialized tools.
3Measurement precision
If phonetic translation is implemented for voice command matching, then matching accuracy for non-phonetic languages is significantly improved, but the system complexity increases due to additional translation components
Solution Approach 1:
The patent performs phonetic translation in advance during the voice command definition and prototyping phase, rather than during actual voice recognition execution. Voice commands are pre-transcribed into phonetic alphabets and stored as patterns, so that when actual voice input is received, the system only needs to perform direct phonetic pattern matching without real-time translation complexity. This preliminary action reduces the complexity of the real-time recognition system while maintaining high accuracy.
Data Source
AI summary
Voice command matching during testing of voice-assisted application prototypes for languages with non-phonetic alphabets is described. A visual page of an application prototype is displayed during a testing phase of the application prototype. A speech-to-text service converts a non-phonetic voice command spoken in a language with a non-phonetic alphabet, captured by at least one microphone during the testing phase of the application prototype, into a non-phonetic text string in the non-phonetic alphabet of the voice command. A phonetic language translator translates the non-phonetic text string of the voice command into a phonetic text string in a phonetic alphabet of the voice command. A comparison module compares the phonetic text string of the voice command to phonetic text strings in the phonetic alphabet of stored voice commands associated with the application prototype to identify a matching voice command. A performance module performs an action associated with the matching voice command.