IP Library › Granted Patent US 12,567,407
Granted Patent B2
US 12,567,407 · App. 18/467,083 · Granted Mar 3, 2026

User profile linking

Inventors: Fabien Hertschuh (Seattle, WA); Mohit Mittal (Vancouver, CA); John Montague Howard (Seattle, WA); Akshit Proothi (Seattle, WA); Rahul Manne (Lynwood, WA)
Assignee: Amazon Technologies, Inc.
G10L15/1822G10L15/07G10L15/1815G10L15/22G10L17/00G10L2015/223G10L2015/227G10L2015/228G10L17/04G10L17/26
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,567,407
App. No.
18/467,083
Granted
Mar 3, 2026
Kind
B2
Abstract

Described are techniques for linking generating a skill-stored user profile, and linking same with a natural language processing (NLP) system-stored user profile. In at least some examples, a user may provide a natural language input to a NLP system. The NLP system may determine a skill is to process to perform an action responsive to the natural language input. To perform the action, the skill may require the user have a user profile stored by the skill, but the user may not have such a user profile. However, the NLP system may store a user profile for the user. The NLP system may determine the user profile stored thereby and may send, with user permission, information in the user profile to the skill. The skill may use the received information to generate and store a user profile for the user. Thereafter, the skill may provide the NLP system with a user profile identifier that the skill may use to identify the user's profile stored thereby. The NLP system may store the received user profile identifier in the user's profile stored by the NLP system, thereby linking the user profiles and enabling the skill to thereafter personalize processing with respect to natural language inputs of the user.

Claims (54)

1 . A computer-implemented method, comprising:

receiving, from a first device associated with a first user profile, a request corresponding to generation of a second user profile for a website;

determining a first type of information is to be used to generate the second user profile;

determining user permission to use first information to generate the second user profile, the first information corresponding to the first type of information;

based on the user permission, sending the first information to a component corresponding to the website, wherein sending of the first information enables the component to generate the second user profile using the first information;

after sending the first information, receiving, from the component corresponding to the website, first data corresponding to a token associated with the second user profile as generated by the component corresponding to the website, wherein the token is an identifier of the second user profile stored by the website, the token being unique to a system that generated the token;

storing an association between the first data and the first user profile, wherein the first user profile is associated with the first device and is different from the second user profile associated with the website;

receiving, from the first device, a second request relating to the website;

based at least in part on the second request relating to the website and the second request being received from the first device, selecting the first data associated with the first user profile; and

causing the component corresponding to the website to perform an action response to the second request based on the first data.

2 . The computer-implemented method of claim 1 , wherein the first user profile and the second user profile are associated with a same user.

3 . The computer-implemented method of claim 1 , further comprising:

receiving user input data from the first device, the user input data representing a natural language input; and

processing the user input data to determine the request.

4 . The computer-implemented method of claim 1 , further comprising:

retrieving, using the first user profile, the first information.

5 . The computer-implemented method of claim 1 , wherein the first user profile corresponds to a first system, and the website is different from the first system.

6 . The computer-implemented method of claim 1 , wherein the first information is specific to a user associated with the first user profile.

7 . The computer-implemented method of claim 1 , further comprising:

associating the second user profile with the first device.

8 . The computer-implemented method of claim 1 , wherein the second user profile corresponds to an application to be operated in conjunction with the first device.

9 . The computer-implemented method of claim 1 , further comprising:

determining that a user associated with the first user profile has been recognized using a user recognition technique; and

sending the first information based on determining that the user has been recognized.

10 . The computer-implemented method of claim 1 , wherein the first data is the token that, when decoded by the component corresponding to the website, identifies the second user profile.

11 . The computer-implemented method of claim 1 , further comprising:

determining an identifier that supports an association between the first user profile and the website; and

determining, based at least in part on the identifier, the first type of information.

12 . A system comprising:

at least one processor; and

at least one memory comprising instructions that, when executed by the at least one processor, cause the system to:

receive, from a first device associated with a first user profile, a request corresponding to generation of a second user profile for an application;

determine a first type of information is to be used to generate the second user profile;

determine user permission to use first information to generate the second user profile, the first information corresponding to the first type of information;

based on the user permission, send the first information to a component corresponding to the application, wherein sending of the first information enables the component to generate the second user profile using the first information;

after sending the first information, receive, from the component corresponding to the application, first data corresponding to a token associated with the second user profile as generated by the component corresponding to the application, wherein the token is an identifier of the second user profile stored by the application;

store an association between the first data and the first user profile, wherein the first user profile is associated with the first device and is different from the second user profile associated with the application;

receive, from the first device, a second request relating to the application;

based at least in part on the second request relating to the application and the second request being received from the first device, selecting the first data associated with the first user profile; and

causing the component corresponding to the application to perform an action response to the second request based on the first data.

13 . The system of claim 12 , wherein the first user profile and the second user profile are associated with a same user.

14 . The system of claim 12 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the system to:

receive user input data from the first device, the user input data representing a natural language input; and

process the user input data to determine the request.

15 . The system of claim 12 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the system to:

retrieve, using the first user profile, the first information.

16 . The system of claim 12 , wherein the first user profile corresponds to a first system, and the application is different from the first system.

17 . The system of claim 12 , wherein the first information is specific to a user associated with the first user profile.

18 . The system of claim 12 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the system to:

associate the second user profile with the first device.

19 . The system of claim 12 , wherein the second user profile corresponds to a website.

20 . The system of claim 12 , wherein the at least one memory further comprises instructions that, when executed by the at least one processor, further cause the system to:

determine that a user associated with the first user profile has been recognized using a user recognition technique; and

send the first information based on determining that the user has been recognized.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2023
From: HERTSCHUH, FABIEN; MITTAL, MOHIT; HOWARD, JOHN MONTAGUE; PROOTHI, AKSHIT; MANNE, RAHUL
To: AMAZON TECHNOLOGIES, INC.
Reel/Frame 064903/0510 →
Continuity (3)
Continuation 17405120 · Aug 18, 2021
Continuation 16455496 · Jun 27, 2019
Related Publication 20230419957A1 · Dec 28, 2023
References Cited (23)
US 7188252B1 · Dunn · 2007 [cited by examiner]
US 8340974B2 · Zurek · 2012 [cited by examiner]
US 8682667B2 · Haughay · 2014 [cited by examiner]
US 9858927B2 · Williams · 2018 [cited by examiner]
US 9922642B2 · Pitschel · 2018 [cited by examiner]
US 10074369B2 · Devaraj · 2018 [cited by examiner]
US 10580405B1 · Wang · 2020 [cited by examiner]
US 10621988B2 · Raichelgauz · 2020 [cited by examiner]
US 10832684B2 · Sarikaya · 2020 [cited by examiner]
US 11516213B2 · Ding · 2022 [cited by examiner]
US 11516221B2 · Alsina · 2022 [cited by examiner]
US 11528274B1 · Krishnamoorthy · 2022 [cited by examiner]
US 11580973B2 · Sundaram · 2023 [cited by examiner]
US 20100169091A1 · Zurek · 2010 [cited by examiner]
US 20120095834A1 · Doig · 2012 [cited by examiner]
US 20120265528A1 · Gruber · 2012 [cited by examiner]
US 20170242657A1 · Jarvis · 2017 [cited by examiner]
US 20180061421A1 · Sarikaya · 2018 [cited by examiner]
US 20200160856A1 · Kline · 2020 [cited by examiner]
US 20200194004A1 · Bates · 2020 [cited by examiner]
US 20200342877A1 · Kartoun · 2020 [cited by examiner]
US 20200382517A1 · Alsina · 2020 [cited by examiner]
US 20210084032A1 · Ding · 2021 [cited by examiner]