Granted Patent B1

US 12,477,601 · App. 18/212,563 · Granted Nov 18, 2025

Inventors: Kent V Lam (Diamond Bar, CA); Samer A. Sarhan Hussein (Rancho Santa Margarita, CA); Apoorv Naik (Carlsbad, CA); Jnana Prasanna Panuganti (Oakville, CA)

Assignee: Amazon Technologies, Inc.

H04W76/14G06Q50/12H04M1/72409H04W12/50H04W12/63

Abstract

Claims (105)

1 . A system, comprising:

one or more processors; and

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

receiving, prior to a user entering an environment with a voice interface device located therein and from an enterprise device associated with an enterprise system, a first request for an accessory device to be associated with the voice interface device, the first request including a first identifier of the accessory device;

generating a second request for the voice interface device to be associated with the accessory device:

sending the second request to the enterprise system associated with the environment, the second request causing the enterprise system to identify a second identifier of the voice interface device based on an association, as maintained by the enterprise system, between the user and the environment;

receiving, from the enterprise system, the second identifier of the voice interface device:

authorizing the first identifier of the accessory device to be associated with the second identifier of the voice interface device for pairing purposes;

receiving, from the voice interface device, a notification that the accessory device is within a threshold range of the voice interface device in the environment;

based on the notification:

sending a first command to the accessory device, the first command configured to cause the accessory device to enter a pairing mode and send a pairing request; and

sending a second command to the voice interface device, the second command configured to cause the voice interface device to enter the pairing mode and accept the pairing request associated with the first identifier of the accessory device; and

receiving, from the voice interface device, an indication that the voice interface device has been successfully paired to the accessory device.

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

receiving, from the enterprise system, an indication that the user is to be dissociated from the environment;

causing, based on receiving the indication that the user is to be dissociated from the environment, the first identifier to be removed from a database of device identifiers that are associated with the enterprise system;

sending a third command to the voice interface device, the third command causing the voice interface device to remove the first identifier of the accessory device from a list of paired devices with the voice interface device; and

sending a fourth command to the accessory device, the fourth command causing the accessory device to reset to a state that the accessory device was in prior to receiving the first request.

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

based on receiving the indication that the voice interface device has been successfully paired to the accessory device, sending authorization data to the enterprise system, the authorization data enabling the enterprise system to communicate with the accessory device;

receiving, from the enterprise system, an indication that the enterprise system has caused a state change to occur with respect to the accessory device utilizing the authorization data; and

causing a state database to indicate the state change.

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

determining that an application has been developed in association with the enterprise system, the application configured to at least perform pairing operations; and

sending the second request to the application, the application configured to communicate the second request to the enterprise system, and wherein receiving the second identifier of the voice interface device comprises receiving the second identifier of the voice interface device from the enterprise system utilizing the application.

5 . A method, comprising:

receiving, from an enterprise device associated with an enterprise system, first data requesting that a first device be associated with a second device, the first data including a first identifier of the first device;

generating second data requesting a second identifier of the second device to be associated with the first device;

sending the second data to the enterprise system, the second data causing the enterprise system to identify the second identifier based at least in part on an association between user account data and the first identifier as maintained by the enterprise system;

receiving, from the enterprise system, third data that includes the second identifier;

generating fourth data that authorizes the first identifier to be associated with the second identifier for pairing purposes;

receiving, from the second device, fifth data indicating that the first device is within a threshold range of the second device; and

based at least in part on the fifth data:

sending a first command to the first device, the first command configured to cause the first device to enter a pairing mode and send a pairing request; and

sending a second command to the second device, the second command configured to cause the second device to enter the pairing mode and accept the pairing request associated with the first identifier.

6 . The method of claim 5 , further comprising:

receiving, from the enterprise system, sixth data indicating that the user account data is to be dissociated from the enterprise system;

causing, based at least in part on receiving the sixth data, the first identifier to be removed from a database of device identifiers;

sending a third command to the second device, the third command causing the second device to remove the first identifier from a list of paired devices with the second device; and

sending a fourth command to the first device, the fourth command causing the first device to reset to a state that the first device was in prior to receiving the first data.

7 . The method of claim 5 , further comprising:

receiving, from the second device, sixth data indicating that the second device has been successfully paired to the first device;

based at least in part on the sixth data, sending authorization data to the enterprise system, the authorization data enabling the enterprise system to communicate with the first device;

receiving, from the enterprise system, seventh data indicating that the enterprise system has caused a state change to occur with respect to the first device; and

causing a state database to indicate the state change.

8 . The method of claim 5 , further comprising:

determining that an application has been developed in association with the enterprise system; and

sending the second data to the application, the application configured to communicate the second data to the enterprise system, and wherein receiving the second identifier of the second device comprises receiving the second identifier from the enterprise system utilizing the application.

9 . The method of claim 5 , further comprising:

determining that a third device is associated with an environment of the second device;

determining that the first device has been successfully paired with the second device; and

based at least in part on the third device being associated with the environment and the first device successfully being paired with the second device, sending a third command to the third device, the third command causing the third device to enter the pairing mode and accept the pairing request associated with the first identifier.

10 . The method of claim 5 , further comprising:

receiving, from the enterprise system, sixth data indicating that a third device having a device type of the first device has been associated with the user account data; and

based at least in part on the third device having the device type and being associated with the user account data, causing the second device to pair with the third device when the third device is within the threshold range of the second device.

11 . The method of claim 5 , wherein:

the first device is a wearable device;

the second device is a voice interface device situated in a hotel room;

the enterprise system is associated with a hotel; and

receiving the first data from the enterprise device is based at least in part on an indication that a user has checked in to the hotel room.

12 . The method of claim 5 , wherein:

the first device is a phone;

the second device is a vehicle; and

receiving the first data from the enterprise device is based at least in part on an indication that a user has rented the vehicle.

13 . A system, comprising:

one or more processors; and

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

receiving, from an enterprise device associated with an enterprise system and based at least in part on a trigger event occurring, first data requesting that a first device be associated with a second device, the first data including a first identifier of the first device;

generating second data requesting a second identifier of the second device to be associated with the first device:

sending the second data to the enterprise system, the second data causing the enterprise system to identify the second identifier based at least in part on an association between user account data and the first identifier as maintained by the enterprise system;

receiving, from the enterprise system, third data that includes the second identifier:

generating fourth data that authorizes the first identifier to be associated with the second identifier for pairing purposes;

receiving, from the second device, fifth data indicating that the first device has moved within a threshold range of the second device; and

based at least in part on the fifth data:

sending a first command to the first device, the first command configured to cause the first device to enter a pairing mode and send a pairing request; and

sending a second command to the second device, the second command configured to cause the second device to enter the pairing mode and accept the pairing request associated with the first identifier.

14 . The system of claim 13 , the operations further comprising:

receiving, from the enterprise system, sixth data indicating that the user account data is to be dissociated from the enterprise system;

causing, based at least in part on receiving the sixth data, the first identifier to be removed from a database of device identifiers that are associated with the enterprise system;

sending a third command to the second device, the third command causing the second device to remove the first identifier from a list of paired devices with the second device; and

sending a fourth command to the first device, the fourth command causing the first device to reset to a state that the first device was in prior to receiving the first data.

15 . The system of claim 13 , the operations further comprising:

receiving, from the second device, sixth data indicating that the second device has been successfully paired to the first device;

based at least in part on the sixth data, sending authorization data to the enterprise system, the authorization data enabling the enterprise system to communicate with the first device;

receiving, from the enterprise system, seventh data indicating that the enterprise system has caused a state change to occur with respect to the first device; and

causing a state database to indicate the state change.

16 . The system of claim 13 , the operations further comprising:

determining that an application has been developed in association with the enterprise system; and

sending the second data to the application, the application configured to communicate the second data to the enterprise system, and wherein receiving the second identifier of the second device comprises receiving the second identifier from the enterprise system utilizing the application.

17 . The system of claim 13 , the operations further comprising:

determining that a third device is associated with an environment of the second device;

determining that the first device has been successfully paired with the second device; and

based at least in part on the third device being associated with the environment and the first device successfully being paired with the second device, sending a third command to the third device, the third command causing the third device to enter the pairing mode and accept the pairing request associated with the first identifier.

18 . The system of claim 13 , the operations further comprising:

receiving, from the enterprise system, sixth data indicating that a third device having a device type of the first device has been associated with the user account data; and

based at least in part on the third device having the device type and being associated with the user account data, causing the second device to pair with the third device when the third device moves to within the threshold range of the second device.

19 . The system of claim 13 , wherein:

the first device is a wearable device;

the second device is a voice interface device situated in a hotel room;

the enterprise system is associated with a hotel; and

the trigger event is an indication that a user has checked in to the hotel room.

20 . The system of claim 13 , wherein:

the first device is a phone;

the second device is a vehicle; and

the trigger event is an indication that a user has rented the vehicle.

Assignments (1)

References Cited (13)

Cited By (1)

US 12,739,904