IP Library › Granted Patent US 12,237,940
Granted Patent B1
US 12,237,940 · App. 18/375,192 · Granted Feb 25, 2025

Usage-based device naming and grouping

Inventors: Aniruddha Basak (Seattle, WA); Yu Liu (Seattle, WA); George Strajan (Seattle, WA); Hersh Sridhar Iyer (Redmond, WA); Sara Parker Hillenmeyer (Seattle, WA); William Evan Welbourne (Seattle, WA)
Assignee: Amazon Technologies, Inc.
H04L12/2812H04L12/2816H04L12/2829H04L12/2832
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,237,940
App. No.
18/375,192
Granted
Feb 25, 2025
Kind
B1
Abstract

Systems and methods for usage-based device naming and grouping are disclosed. For example, trigger events that indicate when a device should be renamed, added to a device group, and/or added to a routine may be determined. Usage data representing usage of the device may be received and utilized to determine if a trigger event occurs. When a trigger event occurs, a recommendation for renaming, grouping, etc. may be determined and sent to a user device. Upon acceptance of the recommendation, the device may be renamed, grouped, and/or added to a routine.

Claims (48)

1. A system comprising:

one or more processors; and

non-transitory computer-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

determining that a trigger event associated with a device has occurred;

causing, based at least in part on the trigger event, output of a request for user input associated with the device;

receiving user input data corresponding to the user input;

generating, based at least in part on user input data, first data indicating a naming identifier for the device; and

storing the first data in association with user account data.

2. The system of claim 1 , wherein:

the trigger event comprises detection of a wake word from first audio data;

causing output of the request comprises causing output of audio representing the request; and

the user input comprises second audio data responsive to the audio representing the request.

3. The system of claim 2 , the operations further comprising:

performing automatic speech recognition on the second audio data such that text data representing the user input is generated;

identifying a portion of the text data predefined as being associated with device naming; and

wherein generating the first data comprises generating the first data utilizing the portion of the text data predefined as being associated with device naming.

4. The system of claim 1 , the operations further comprising:

generating, based at least in part on the user input data, second data indicating a device group to associate with the device; and

storing the second data in association with the user account data.

5. The system of claim 1 , the operations further comprising receiving a request to operate the device, and wherein determining that the trigger event associated with the device has occurred is based at least in part on receiving the request to operate the device.

6. The system of claim 1 , wherein the trigger event includes detecting a degree of change in a usage pattern of the device that satisfies a threshold degree of change in the usage pattern.

7. The system of claim 1 , wherein the trigger event includes determining that a device name of the device includes a word predefined to be associated with seasonal usage of the device.

8. The system of claim 1 , the operations further comprising receiving feedback data indicating that improper targeting of the device using voice commands has occurred, and wherein the trigger event comprises receiving the feedback data.

9. The system of claim 1 , the operations further comprising determining a device type of the device, and wherein the trigger event comprises determining that the device type corresponds to a predefined device type associated with temporary use of the device.

10. The system of claim 1 , the operations further comprising causing the device to transition from a first device state to a second device state, and wherein the trigger event comprises causing the device to transition from the first device state to the second device state.

11. A method comprising:

determining that a trigger event associated with a device has occurred;

causing, based at least in part on the trigger event, output of a request for user input associated with the device;

receiving user input data corresponding to the user input;

generating, based at least in part on user input data, first data indicating a naming identifier for the device; and

storing the first data in association with user account data.

12. The method of claim 11 , wherein:

the trigger event comprises detection of a wake word from first audio data;

causing output of the request comprises causing output of audio representing the request; and

the user input comprises second audio data responsive to the audio representing the request.

13. The method of claim 12 , further comprising:

performing automatic speech recognition on the second audio data such that text data representing the user input is generated;

identifying a portion of the text data predefined as being associated with device naming; and

wherein generating the first data comprises generating the first data utilizing the portion of the text data predefined as being associated with device naming.

14. The method of claim 11 , further comprising:

generating, based at least in part on the user input data, second data indicating a device group to associate with the device; and

storing the second data in association with the user account data.

15. The method of claim 11 , further comprising receiving a request to operate the device, and wherein determining that the trigger event associated with the device has occurred is based at least in part on receiving the request to operate the device.

16. The method of claim 11 , wherein the trigger event includes detecting a degree of change in a usage pattern of the device that satisfies a threshold degree of change in the usage pattern.

17. The method of claim 11 , wherein the trigger event includes determining that a device name of the device includes a word predefined to be associated with seasonal usage of the device.

18. The method of claim 11 , further comprising receiving feedback data indicating that improper targeting of the device using voice commands has occurred, and wherein the trigger event comprises receiving the feedback data.

19. The method of claim 11 , further comprising determining a device type of the device, and wherein the trigger event comprises determining that the device type corresponds to a predefined device type associated with temporary use of the device.

20. The method of claim 11 , further comprising causing the device to transition from a first device state to a second device state, and wherein the trigger event comprises causing the device to transition from the first device state to the second device state.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 19, 2023
From: BASAK, ANIRUDDHA; LIU, YU; STRAJAN, GEORGE; IYER, HERSH SRIDHAR; HILLENMEYER, SARA PARKER; WELBOURNE, WILLIAM EVAN
To: AMAZON TECHNOLOGIES, INC.
Reel/Frame 065910/0100 →
Continuity (3)
Continuation 17847485 · Jun 23, 2022
Continuation 17156875 · Jan 25, 2021
Continuation 16835954 · Mar 31, 2020
References Cited (32)
US 5581760A · Atkinson et al. · 1996 [cited by applicant]
US 8291046B2 · Farber et al. · 2012 [cited by applicant]
US 8880793B2 · Nagineni · 2014 [cited by applicant]
US 9113286B1 · Adams et al. · 2015 [cited by applicant]
US 9553841B1 · Skinner et al. · 2017 [cited by applicant]
US 10674001B1 · Rao et al. · 2020 [cited by applicant]
US 10747894B1 · Cline et al. · 2020 [cited by applicant]
US 10855483B1 · Ramesh et al. · 2020 [cited by applicant]
US 10904027B1 · Basak · 2021 [cited by examiner]
US 11132172B1 · Naik et al. · 2021 [cited by applicant]
US 11374780B1 · Basak · 2022 [cited by examiner]
US 11784843B1 · Basak · 2023 [cited by examiner]
US 20080235358A1 · Moribe et al. · 2008 [cited by applicant]
US 20090119274A1 · Tsuzuki et al. · 2009 [cited by applicant]
US 20100198724A1 · Thomas · 2010 [cited by examiner]
US 20100299260A1 · Thomas · 2010 [cited by examiner]
US 20120268770A1 · Fukuda · 2012 [cited by applicant]
US 20130179500A1 · Kacin et al. · 2013 [cited by applicant]
US 20130232195A1 · Ruan · 2013 [cited by examiner]
US 20140173687A1 · Dimitrakos · 2014 [cited by examiner]
US 20160149716A1 · Raj · 2016 [cited by applicant]
US 20170063948A1 · Shroff et al. · 2017 [cited by applicant]
US 20170223128A1 · Shuvaev et al. · 2017 [cited by applicant]
US 20180337686A1 · Diegmann · 2018 [cited by examiner]
US 20190281878A1 · Tang · 2019 [cited by examiner]
US 20200265530A1 · Lee et al. · 2020 [cited by applicant]
US 20200265531A1 · Lee et al. · 2020 [cited by applicant]
US 20200265532A1 · Lee et al. · 2020 [cited by applicant]
US 20200265533A1 · Lee et al. · 2020 [cited by applicant]
US 20200265534A1 · Lee et al. · 2020 [cited by applicant]
US 20210090578A1 · Trapp et al. · 2021 [cited by applicant]
Office Action for U.S. Appl. No. 17/847,485, mailed on Jan. 20, 2023, Aniruddha Basak, “Usage-Based Device Naming and Grouping”, 5 pages. [cited by applicant]