Multi-command single utterance input method
US-2015348551-A1 · Dec 3, 2015 · US
US11567788B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11567788-B1 |
| Application number | US-202017035253-A |
| Country | US |
| Kind code | B1 |
| Filing date | Sep 28, 2020 |
| Priority date | Oct 18, 2019 |
| Publication date | Jan 31, 2023 |
| Grant date | Jan 31, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one embodiment, a method includes receiving a user request to create a reminder from a client system associated with a user, wherein the user request does not specify an activation-condition for the reminder, determining one or more proactive activation-conditions for the reminder, storing the reminder in a reminder store, receiving one or more inputs associated with the user, determining a user context associated with the user based on the one or more inputs, determining the one or more proactive activation-conditions for the reminder are satisfied based on the user context, and sending instructions for presenting the reminder to the user to the client system responsive to determining the one or more proactive activation-conditions are satisfied.
Opening claim text (preview).
What is claimed is: 1. A method comprising, by one or more computing systems: receiving, from a client system associated with a user, a user request to create a reminder, wherein the user request does not specify an activation-condition for the reminder; determining one or more proactive activation-conditions for the reminder; storing the reminder in a reminder store; receiving one or more inputs associated with the user; determining, based on the one or more inputs, a user context associated with the user; determining, based on the user context, whether the one or more proactive activation-conditions for the reminder are satisfied; and sending, to the client system, instructions for presenting the reminder to the user responsive to determining the one or more proactive activation-conditions are satisfied. 2. The method of claim 1 , wherein the user context comprises one or more events comprising one or more of a time event, a social event, a world event, or a language-intent event. 3. The method of claim 2 , further comprising: determining the one or more events based on one or more multimodal signals, wherein the one or more multimodal signals comprise one or more of a date, a time, a location, a visual signal, a sound signal, or an entity update. 4. The method of claim 1 , further comprising: creating a prospective memory entry in a user memory associated with the user, wherein the prospective memory entry is associated with the reminder. 5. The method of claim 4 , further comprising: querying the user memory to identify the prospective memory entry upon receiving the one or more inputs; and determining, based on the prospective memory entry, the user context is associated with the reminder. 6. The method of claim 1 , wherein determining the one or more proactive activation-conditions for the reminder is based on one or more of a user task history or a user memory associated with the user. 7. The method of claim 1 , wherein determining that the triggering signals satisfy the delivery condition is further based on one or more proactive policies. 8. The method of claim 1 , further comprising: determining a priority of the reminder; determining one or more priorities of one or more current tasks associated with the user, respectively; comparing the priority of the reminder with the one or more priorities of the one or more current tasks, respectively; and determining, based on the comparison, the reminder has a higher priority than the one or more current tasks; wherein sending instructions for presenting the reminder to the user is further responsive to determining the reminder has a higher priority than the one or more current tasks. 9. The method of claim 1 , wherein the one or more proactive activation-conditions are based on one or more of a time, a location, or an entity. 10. The method of claim 1 , further comprising: receiving, from the client system, an indication the reminder was not successfully presented to the user; and rescheduling the reminder for the user. 11. The method of claim 10 , wherein rescheduling the reminder comprises updating one or more of the proactive activation-conditions for the reminder. 12. The method of claim 11 , wherein updating the one or more of the activation-conditions is based on the user context associated with the user. 13. The method of claim 11 , further comprising: determining whether the updated proactive activation-conditions associated with the reminder is satisfied; and sending, to the client system, instructions for presenting the reminder to the user responsive to determining the updated proactive activation-conditions are satisfied. 14. The method of claim 1 , wherein determining the user context associated with the user is further based on a dialog state associated with the user. 15. The method of claim 1 , wherein the reminder store is located in a data store associated with the one or more computing systems. 16. The method of claim 1 , wherein the reminder store is located in a data store associated with the client system. 17. One or more computer-readable non-transitory storage media embodying software that is operable when executed to: receive, from a client system associated with a user, a user request to create a reminder, wherein the user request does not specify an activation-condition for the reminder; determine one or more proactive activation-conditions for the reminder; store the reminder in a reminder store; receive one or more inputs associated with the user; determine, based on the one or more inputs, a user context associated with the user; determine, based on the user context, whether the one or more proactive activation-conditions for the reminder are satisfied; and send, to the client system, instructions for presenting the reminder to the user responsive to determining the one or more proactive activation-conditions are satisfied. 18. A system comprising: one or more processors; and a non-transitory memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to: receive, from a client system associated with a user, a user request to create a reminder, wherein the user request does not specify an activation-condition for the reminder; determine one or more proactive activation-conditions for the reminder; store the reminder in a reminder store; receive one or more inputs associated with the user; determine, based on the one or more inputs, a user context associated with the user; determine, based on the user context, whether the one or more proactive activation-conditions for the reminder are satisfied; and send, to the client system, instructions for presenting the reminder to the user responsive to determining the one or more proactive activation-conditions are satisfied.
Machine learning · CPC title
Push-based network services · CPC title
Audio in a user interface, e.g. using voice commands for navigating, audio feedback · CPC title
using third party service providers · CPC title
User profiles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.