IP Library Granted Patent US 9,117,447
Granted Patent B2
US 9,117,447 · App. 13/725,761 · Granted Aug 25, 2015

Using event alert text as input to an automated assistant

Inventors: Thomas Robert Gruber (Emerald Hills, CA); Adam John Cheyer (Oakland, CA); Didier Rene Guzzoni (Monte-sur-Rolle, CH)
Assignee: Apple Inc.
G10L15/1815G06F3/167G06F9/54G06F17/28G06F17/3087G10L15/22G10L15/26G10L21/06
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 9,117,447
App. No.
13/725,761
Granted
Aug 25, 2015
Kind
B2
Abstract

Methods, systems, and computer readable storage medium related to operating an intelligent digital assistant are disclosed. An event alert is detected, where the event alert includes context data. A representation of an intent is derived based at least in part on the context data. At least one domain, at least one task, and at least one parameter for the task are identified based at least in part on the representation of the intent. The identified task is performed using the at least one parameter. An output is provided to the user, where the output is related to the performance of the first task.

Claims (65)

1. A method for operating an automated assistant, comprising:

at an electronic device comprising a processor and memory storing instructions for execution by the processor:

detecting, by the automated assistant, an event alert issued by an application or a web-based service, wherein the event alert comprises context data;

in response to detecting the event alert, prompting a user for input based at least in part on the context data of the event alert;

identifying at least one task based at least in part on the context data of the event alert;

performing the identified task using the user input; and

providing an output to the user, wherein the output is related to the performance of the identified task.

2. The method of claim 1 , wherein the event alert is issued by a calendar application, and the context data is a text string associated with a previously created calendar event stored by the calendar application.

3. The method of claim 2 , wherein the context data includes a name of a person associated with the calendar event.

4. The method of claim 3 , further comprising:

identifying at least one parameter for the task; and

selecting the name of the person as one of the at least one parameters for the task.

5. The method of claim 2 , wherein the text string was supplied by a user during creation of the calendar event stored by the calendar application.

6. The method of claim 2 , wherein the context data includes a location associated with the calendar event.

7. The method of claim 6 , further comprising:

identifying at least one parameter for the task; and

selecting the location as one of the at least one parameters for the task.

8. The method of claim 1 , further comprising:

detecting a second event alert;

determining a relevance for the event alert and the second event alert; and

presenting the event alert and the second event alert to the user in order based on the determined relevance.

9. The method of claim 1 , wherein the event alert is a flight status alert.

10. A system for operating an intelligent automated assistant, comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the processors to perform operations comprising:

detecting, by the intelligent automated assistant, an event alert issued by an application or a web-based service, wherein the event alert comprises context data;

in response to detecting the event alert, prompting a user for input based at least in part on the context data of the event alert;

identifying at least one task based at least in part on the context data of the event alert;

performing the identified task using the user input; and

providing an output to the user, wherein the output is related to the performance of the identified task.

11. The system of claim 10 , wherein the event alert is issued by a calendar application, and the context data is a text string associated with a previously created calendar event stored by the calendar application.

12. The system of claim 11 , wherein the context data includes a name of a person associated with the calendar event.

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

identifying at least one parameter for the task; and

selecting the name of the person as one of the at least one parameters for the task.

14. The system of claim 11 , wherein the text string was supplied by a user during creation of the calendar event stored by the calendar application.

15. The system of claim 11 , wherein the context data includes a location associated with the calendar event.

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

identifying at least one parameter for the task; and

selecting the location as one of the at least one parameters for the task.

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

detecting a second event alert;

determining a relevance for the event alert and the second event alert; and presenting the event alert and the second event alert to the user in order based on the determined relevance.

18. The system of claim 10 , wherein the event alert is a flight status alert.

19. A non-transitory computer readable storage medium storing instructions that, when executed by an electronic device with one or more processors, cause the processors to perform operations comprising:

detecting, by an automated assistant, an event alert issued by an application or a web-based service, wherein the event alert comprises context data;

in response to detecting the event alert, prompting a user for input based at least in part on the context data of the event alert;

identifying at least one task based at least in part on the context data of the event alert;

performing the identified task using the user input; and

providing an output to the user, wherein the output is related to the performance of the identified task.

20. The computer readable storage medium of claim 19 , wherein the event alert is issued by a calendar application, and the context data is a text string associated with a previously created calendar event stored by the calendar application.

21. The computer readable storage medium of claim 20 , wherein the context data includes a name of a person associated with the calendar event.

22. The computer readable storage medium of claim 21 , the operations further comprising:

identifying at least one parameter for the task; and

selecting the name of the person as one of the at least one parameters for the task.

23. The computer readable storage medium of claim 20 , wherein the text string was supplied by a user during creation of the calendar event stored by the calendar application.

24. The computer readable storage medium of claim 20 , wherein the context data includes a location associated with the calendar event.

25. The computer readable storage medium of claim 24 , the operations further comprising:

identifying at least one parameter for the task; and

selecting the location as one of the at least one parameters for the task.

26. The computer readable storage medium of claim 19 , the operations further comprising:

detecting a second event alert;

determining a relevance for the event alert and the second event alert; and

presenting the event alert and the second event alert to the user in order based on the determined relevance.

27. The computer readable storage medium of claim 19 , wherein the event alert is a flight status alert.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 27, 2013
From: GRUBER, THOMAS ROBERT; CHEYER, ADAM JOHN; GUZZONI, DIDIER RENE
To: APPLE INC.
Reel/Frame 030100/0250 →
Continuity (3)
Continuation 12987982 · Jan 10, 2011
Provisional Application 61295774 · Jan 18, 2010
Related Publication 20130110505A1 · May 2, 2013