Endpoint Device Relationship Traversal for Ambiguous User Inputs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing speech processing systems require precise invocation names for endpoint devices, leading to user frustration when the system cannot infer the intended device from ambiguous user inputs and fail to accurately determine which devices are associated, such as a stereo within a vehicle.
Innovation Solution
A system that uses an API to receive data on endpoint device relationships from manufacturers, allowing the system to integrate devices without prior knowledge and associate them based on user profiles, enabling traversal of device relationships during natural language understanding processing to accurately determine the intended device for user inputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the system requires precise invocation names for endpoint devices, then device identification accuracy is improved, but user experience deteriorates when inputs are ambiguous
Solution Approach 1:
The patent introduces an intermediary component that processes ambiguous device references by analyzing contextual information from the user input, device relationships, and user profiles to resolve the intended device without requiring precise invocation names from the user
2Measurement precision
If the system manually associates endpoint devices with user profiles, then device relationship accuracy is improved, but system complexity and setup time increase
Solution Approach 1:
The system automatically performs device association by having endpoint devices self-register with the service, where the device provides its own identification information and the system automatically establishes the relationship with user profiles without manual intervention
Solution Approach 2:
The system pre-establishes device relationships by receiving device data from manufacturers that includes hierarchical relationships (e.g., a stereo system within a vehicle), allowing the system to traverse these relationships later to resolve ambiguous device references
3Stability of the object's composition
If the system requires prior configuration to support endpoint devices, then system stability is improved, but adaptability to new devices deteriorates
Solution Approach 1:
The patent implements a universal interface that accepts device data from multiple sources (manufacturers, direct device connections) in various formats, allowing the system to integrate different types of endpoint devices without requiring device-specific configuration procedures
Data Source
AI summary
Techniques for enabling entities to provide a system with data representing specific relationships of various endpoint devices for the purpose of responding to user inputs are described. A system may include an application program interface (API) that enables an entity to provide the system with data describing related endpoint devices, as well as data representing terminology that a user may use to refer to a specific endpoint device. After the system receives such data, when a user associates an endpoint device with their user profile, the system can associate that endpoint device with various other endpoint devices based on data previously received from an entity. When the system receives a user input, the system may traverse endpoint device relationships, represented in a user profile, to determine an endpoint device that should be invoked to respond to the user input.