Carrier Phrase Registration for Voice Query Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile computing devices lack an efficient mechanism to route queries based on carrier phrases registered by third-party applications, leading to confusion and potential misdirection of user intents in voice query processing.
Innovation Solution
Implementing a system where carrier phrases are registered by third-party applications on mobile devices, allowing the device to identify and route voice queries to the appropriate application by recognizing pre-defined phrases, enabling specific actions based on the query content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If voice queries are processed without carrier phrase registration, then the system is simpler, but query routing accuracy deteriorates
Solution Approach 1:
The system performs preliminary registration of carrier phrases with their corresponding applications before query processing. Applications register their carrier phrases with the operating system during installation or configuration, creating a lookup table in advance. This preliminary action enables rapid and accurate query routing without complex real-time analysis, resolving the contradiction between routing accuracy and system complexity.
Solution Approach 2:
The operating system introduces an intermediary carrier phrase registration mechanism between the user's voice query and the third-party applications. The OS maintains a registration database that maps carrier phrases to specific applications, acting as a mediator that routes queries accurately without requiring direct complex interactions between users and multiple applications. This intermediary layer improves routing precision while keeping the overall system architecture manageable.
2Adaptability or versatility
If multiple third-party applications can register carrier phrases, then application versatility improves, but query routing complexity increases
Solution Approach 1:
The operating system implements a universal carrier phrase registration mechanism that works across all third-party applications. Any application can register carrier phrases through a standardized interface, allowing diverse applications (messaging, media players, utilities) to participate in voice query routing. This universal approach enhances application versatility while the OS manages routing complexity through a unified registration database and standardized routing logic.
Solution Approach 2:
The system changes the parameter of carrier phrase registration from application-specific custom implementations to a standardized OS-managed parameter set. Applications register carrier phrases with the OS, which maintains a centralized registration database. This parameter standardization allows multiple applications to register carrier phrases efficiently without increasing routing complexity, as the OS handles all routing decisions based on the standardized registration data.
3Ease of operation
If carrier phrase registration is implemented, then user experience improves, but processing time increases
Solution Approach 1:
Carrier phrase registrations are performed in advance during application installation or configuration, building a ready-to-use lookup database. When voice queries are processed, the system simply looks up the carrier phrase in the pre-built registration database and routes to the corresponding application, avoiding complex real-time analysis. This preliminary action significantly reduces processing time while maintaining enhanced user experience through accurate query routing.
Data Source
AI summary
In general, the subject matter described in this specification can be embodied in methods, systems, and program products for receiving a voice query at a mobile computing device and generating data that represents content of the voice query. The data is provided to a server system. A textual query that has been determined by a speech recognizer at the server system to be a textual form of at least part of the data is received at the mobile computing device. The textual query is determined to include a carrier phrase of one or more words that is reserved by a first third-party application program installed on the computing device. The first third-party application is selected, from a group of one or more third-party applications, to receive all or a part of the textual query. All or a part of the textual query is provided to the selected first application program.