IP Library Granted Patent US 12,499,112
Granted Patent B2
US 12,499,112 · App. 18/675,784 · Granted Dec 16, 2025

Methods, systems, and media for interpreting voice queries

Inventor: Yongsung Kim (Mountain View, CA)
Assignee: GOOGLE LLC
G06F16/2454G06F16/2282G06F16/23G06F16/2365G06F16/24549G06F16/24575G06F16/29G06F16/3322G06F16/9535G06F16/9538H04N21/278H04N21/47202
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,499,112
App. No.
18/675,784
Granted
Dec 16, 2025
Kind
B2
Abstract

Methods, systems, and media for interpreting queries are described herein. For example, an illustrative method may include: determining, based on a voice query received in a search domain, a first voice recognition term and a second voice recognition term; determining that at least a portion of the first voice recognition term corresponds to an entity name associated with the search domain; determining, based on the entity name, a feasibility score for the first voice recognition term; ranking, based on the feasibility score, the first voice recognition term over the second voice recognition term; and executing the voice query in the search domain using the first voice recognition term, the first voice recognition term being selected for use over the second voice recognition term based on the ranking. Corresponding systems, devices, and other implementations are also described.

Claims (72)

1 . A method comprising:

determining, based on a voice query received in a search domain, a first voice recognition term and a second voice recognition term;

determining that at least a portion of the first voice recognition term corresponds to an entity name associated with the search domain;

determining, based on the entity name, a feasibility score for the first voice recognition term;

ranking, based on the feasibility score, the first voice recognition term relative to the second voice recognition term; and

based on a determination that a first portion of the voice query does not correspond to an action command term, executing the voice query in the search domain in accordance with a default action command and using the first voice recognition term, the first voice recognition term being selected for use over the second voice recognition term based on the ranking.

2 . The method of claim 1 , wherein the determining the first voice recognition term and the second voice recognition term includes segmenting the voice query to generate:

the first voice recognition term as the first portion of the voice query; and

the second voice recognition term as a second portion of the voice query.

3 . The method of claim 1 , wherein:

the determining the first voice recognition term and the second voice recognition term includes segmenting an entirety of the voice query to generate the first voice recognition term; and

the determining that at least the portion of the first voice recognition term corresponds to the entity name includes determining that the entirety of the voice query corresponds to the entity name.

4 . The method of claim 1 , further comprising:

determining, based on an additional voice query received in the search domain, a third voice recognition term and a fourth voice recognition term, the determining the third voice recognition term and the fourth voice recognition term includes:

determining that a first portion of the additional voice query corresponds to an additional action command term, and

generating a set of terms, including the third voice recognition term and the fourth voice recognition term, based on the first portion of the additional voice query; and

determining that at least a portion of the third voice recognition term corresponds to an additional entity name associated with the search domain by comparing the set of terms with entities in an entity table associated with action command terms.

5 . The method of claim 4 , the entity table includes curated entity information for a plurality of action command terms.

6 . The method of claim 1 , wherein the default action command is based on the search domain.

7 . The method of claim 1 , wherein:

the entity name to which at least the portion of the first voice recognition term corresponds is of an entity type; and

the default action command is based on the entity type.

8 . The method of claim 1 , wherein:

the entity name to which at least the portion of the first voice recognition term corresponds is of a first entity type;

the method further comprises determining that at least a portion of the second voice recognition term corresponds to an additional entity name of a second entity type different from the first entity type; and

the default action command is determined based on:

a first entity score for the entity name,

a second entity score for the additional entity name, and

at least one of the first entity type or the second entity type.

9 . The method of claim 1 , wherein the determining the feasibility score for the first voice recognition term includes applying a penalty score to the feasibility score, the penalty score based on how many terms associated with the first voice recognition term are recognized as entities in an entity table.

10 . The method of claim 1 , wherein the determining the feasibility score for the first voice recognition term includes weighting an average entity score for a plurality of terms that are associated with the first voice recognition term and recognized as entities in an entity table.

11 . The method of claim 1 , wherein the voice query is received from at least one of:

a media playback device having audio input capabilities; or

an audio input device included within a mobile device.

12 . The method of claim 1 , further comprising detecting a language in which the voice query is spoken;

wherein the determining the first voice recognition term and the second voice recognition term includes interpreting the voice query based on the detected language.

13 . A system comprising:

a memory storing instructions; and

a processor communicatively coupled to the memory and configured to execute the instructions to perform a process comprising:

determining, based on a voice query received in a search domain, a first voice recognition term and a second voice recognition term;

determining that at least a portion of the first voice recognition term corresponds to an entity name associated with the search domain;

determining, based on the entity name, a feasibility score for the first voice recognition term;

ranking, based on the feasibility score, the first voice recognition term relative to the second voice recognition term; and

based on a determination that a first portion of the voice query does not correspond to an action command term, executing the voice query in the search domain in accordance with a default action command and using the first voice recognition term, the first voice recognition term being selected for use over the second voice recognition term based on the ranking.

14 . The system of claim 13 , wherein the determining the first voice recognition term and the second voice recognition term includes segmenting the voice query to generate:

the first voice recognition term as the first portion of the voice query; and

the second voice recognition term as a second portion of the voice query.

15 . The system of claim 13 , wherein the process further comprises:

determining, based on an additional voice query received in the search domain, a third voice recognition term and a fourth voice recognition term, the determining the third voice recognition term and the fourth voice recognition term includes:

determining that a first portion of the additional voice query corresponds to an additional action command term, and

generating a set of terms, including the third voice recognition term and the fourth voice recognition term, based on the first portion of the additional voice query; and

determining that at least a portion of the third voice recognition term corresponds to an additional entity name associated with the search domain by comparing the set of terms with entities in an entity table associated with action command terms.

16 . The system of claim 13 , wherein the default action command is based on the search domain.

17 . The system of claim 13 , wherein:

the entity name to which at least the portion of the first voice recognition term corresponds is of an entity type; and

the default action command is based on the entity type.

18 . The system of claim 13 , wherein:

the entity name to which at least the portion of the first voice recognition term corresponds is of a first entity type;

the process further comprises determining that at least a portion of the second voice recognition term corresponds to an additional entity name of a second entity type different from the first entity type; and

the default action command is determined based on:

a first entity score for the entity name,

a second entity score for the additional entity name, and

at least one of the first entity type or the second entity type.

19 . A non-transitory computer-readable medium storing instructions that, when executed, cause a processor of a computing device to perform a process comprising:

determining, based on a voice query received in a search domain, a first voice recognition term and a second voice recognition term;

determining that at least a portion of the first voice recognition term corresponds to an entity name associated with the search domain;

determining, based on the entity name, a feasibility score for the first voice recognition term;

ranking, based on the feasibility score, the first voice recognition term relative to the second voice recognition term; and

based on a determination that a first portion of the voice query does not correspond to an action command term, executing the voice query in the search domain in accordance with a default action command and using the first voice recognition term, the first voice recognition term being selected for use over the second voice recognition term based on the ranking.

20 . The non-transitory computer-readable medium of claim 19 , wherein the determining the first voice recognition term and the second voice recognition term includes segmenting the voice query to generate:

the first voice recognition term as the first portion of the voice query; and

the second voice recognition term as a second portion of the voice query.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2024
From: KIM, YONGSUNG
To: GOOGLE INC.
Reel/Frame 067553/0734 →
ENTITY CONVERSION Recorded May 29, 2024
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 067564/0681 →
Continuity (5)
Continuation 17560693 · Dec 23, 2021
Continuation 15587915 · May 5, 2017
Continuation 14816802 · Aug 3, 2015
Continuation 13677020 · Nov 14, 2012
Related Publication 20240311374A1 · Sep 19, 2024
References Cited (58)
US 7523099B1 · Egnor et al. · 2009 [cited by applicant]
US 7526425B2 · Marchisio et al. · 2009 [cited by applicant]
US 7636714B1 · Lamping et al. · 2009 [cited by applicant]
US 7792837B1 · Zhao · 2010 [cited by applicant]
US 7831632B2 · Djugash et al. · 2010 [cited by applicant]
US 8027988B1 · Egnor et al. · 2011 [cited by applicant]
US 8112432B2 · Zhou et al. · 2012 [cited by applicant]
US 8117206B2 · Sibley et al. · 2012 [cited by applicant]
US 8214210B1 · Woods · 2012 [cited by examiner]
US 8356029B2 · Djugash et al. · 2013 [cited by applicant]
US 8364692B1 · Allen et al. · 2013 [cited by applicant]
US 8463774B1 · Buron · 2013 [cited by examiner]
US 8527520B2 · Morton et al. · 2013 [cited by applicant]
US 8533223B2 · Houghton · 2013 [cited by applicant]
US 8595250B1 · Egnor et al. · 2013 [cited by applicant]
US 8752001B2 · Sureka · 2014 [cited by examiner]
US 9639874B2 · Psota · 2017 [cited by examiner]
US 12400656B2 · Chao · 2025 [cited by examiner]
US 20040243407A1 · Yu et al. · 2004 [cited by applicant]
US 20050222976A1 · Pfleger · 2005 [cited by applicant]
US 20050222977A1 · Zhou et al. · 2005 [cited by applicant]
US 20070198511A1 · Kim et al. · 2007 [cited by applicant]
US 20080005090A1 · Khan et al. · 2008 [cited by applicant]
US 20090125534A1 · Morton et al. · 2009 [cited by applicant]
US 20090204596A1 · Brun et al. · 2009 [cited by applicant]
US 20090244592A1 · Grams · 2009 [cited by applicant]
US 20090307208A1 · Peng · 2009 [cited by examiner]
US 20090326923A1 · Yan et al. · 2009 [cited by applicant]
US 20100114944A1 · Adler · 2010 [cited by examiner]
US 20100223292A1 · Bhagwan et al. · 2010 [cited by applicant]
US 20100293195A1 · Houghton · 2010 [cited by applicant]
US 20100312782A1 · Li · 2010 [cited by examiner]
US 20110004618A1 · Chaudhary · 2011 [cited by applicant]
US 20110119243A1 · Diamond et al. · 2011 [cited by applicant]
US 20110231347A1 · Xu et al. · 2011 [cited by applicant]
US 20110307432A1 · Yao et al. · 2011 [cited by applicant]
US 20110320458A1 · Karana · 2011 [cited by applicant]
US 20120059838A1 · Berntson et al. · 2012 [cited by applicant]
US 20120109966A1 · Liang et al. · 2012 [cited by applicant]
US 20120232897A1 · Pettyjohn · 2012 [cited by examiner]
US 20130144854A1 · Pantel · 2013 [cited by examiner]
US 20130173639A1 · Chandra · 2013 [cited by examiner]
US 20130238594A1 · Hong · 2013 [cited by examiner]
US 20130238631A1 · Carmel · 2013 [cited by examiner]
US 20130262107A1 · Bernard · 2013 [cited by examiner]
US 20130308840A1 · Tallapragada · 2013 [cited by examiner]
US 20130339340A1 · Pfitzner · 2013 [cited by examiner]
US 20140006393A1 · Soshin · 2014 [cited by examiner]
US 20140129220A1 · Zhang · 2014 [cited by examiner]
US 20140136197A1 · Mamou · 2014 [cited by examiner]
US 20140288932A1 · Yeracaris · 2014 [cited by examiner]
US 20220148591A1 · Chao · 2022 [cited by examiner]
US 20240362282A1 · Malhotra · 2024 [cited by examiner]
U.S. Appl. No. 17/560,693, filed Dec. 23, 2021, Allowed. [cited by applicant]
U.S. Appl. No. 15/587,915, filed May 5, 2017, Issued. [cited by applicant]
U.S. Appl. No. 14/816,802, filed Aug. 3, 2015, Issued. [cited by applicant]
U.S. Appl. No. 13/677,020, filed Nov. 14, 2012, Issued. [cited by applicant]
Guo , et al., “Names Entity Recognition in Query”, Proc. 32nd Int'l ACM SIGIR Conference on Research and Development in Information Retrieval, SIGIR '09, Jan. 2009, pp. 267-274. [cited by applicant]