IP Library Granted Patent US 12,231,739
Granted Patent B2
US 12,231,739 · App. 18/414,604 · Granted Feb 18, 2025

Generating notifications that provide context for predicted content interruptions

Inventors: Cliff Kuang (San Francisco, CA); Jesse Kaczmarek (New York, NY); Andy Gugel (Eden Prairie, MN); Jonathan Lee (Brooklyn, NY)
Assignee: GOOGLE LLC
H04N21/4882H04N21/4131H04N21/4312
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,231,739
App. No.
18/414,604
Granted
Feb 18, 2025
Kind
B2
Abstract

Implementations set forth herein relate to providing notifications regarding events that may interrupt content being rendered at an interface. The notifications can be preemptive and/or can indicate a predicted time and/or source for the events. The event can be, for example, a person attempting to contact a user who is viewing content at a display interface. The person can be associated with a food delivery that has been ordered by the user via a delivery application. An application, such an automated assistant application, can predict when the person is expected to arrive with the food delivery, and generate a notification ahead of the person arriving. In some implementations, the notification can be rendered at a scrubber user interface (UI) at a location corresponding to the time that the food delivery is expected to arrive, thereby putting the user on notice of when the streaming content may be interrupted.

Claims (47)

1. A system, comprising:

memory storing instructions;

one or more processors operable to execute the instructions to:

determine, based on a prior user interaction with an application, a predicted time for an application event to occur, wherein the application event corresponds to the prior user interaction with the application;

receive, from an internet of things (IoT) device and during rendering of streaming content at a display interface of a computing device, an indication that an IoT event has occurred;

determine that the IoT event corresponds to the application event, wherein in determining that the IoT event corresponds to the application event one or more of the processors are to determine that the IoT event corresponds to the application event based on determining that the indication, that the IoT event has occurred, corresponds to the predicted time;

in response to determining that the IoT event corresponds to the application event:

cause a notification to be rendered, at the computing device and during the rendering of the streaming content, that includes application content that is based on the prior user interaction with the application.

2. The system of claim 1 , wherein the IoT device is a smart doorbell.

3. The system of claim 2 , wherein the application is a food delivery application.

4. The system of claim 2 , wherein in determining the predicted time one or more of the processors are to determine the predicted time based on application data that is provided by the application and that is based on the prior user interaction.

5. The system of claim 2 , wherein in causing the notification to be rendered during the rendering of the streaming content one or more of the processors are to cause the notification to be rendered in a scrubber user interrace of the streaming application.

6. The system of claim 2 , wherein in causing the notification to be rendered during the rendering of the streaming content one or more of the processors are to cause the notification to be rendered along with an image captured by the smart doorbell.

7. The system of claim 2 , wherein the application content includes an icon that corresponds to the application.

8. The system of claim 2 , wherein the application event is a delivery and wherein the application content includes product content characterizing a product to be delivered.

9. The system of claim 1 , wherein one or more processors are further operable to execute the instructions to:

cause, prior to causing the notification to be rendered and prior to receiving the indication that the IoT event has occurred, a predictive notification to be rendered at the computing device during the rendering of the streaming content;

wherein the predictive notification includes the application content and is rendered, within a scrubber user interface of the streaming application, at a relative time, within the scrubber user interface, that corresponds to the predicted time.

10. The system of claim 1 , wherein one or more processors are further operable to execute the instructions to:

determine that the application event satisfies a priority threshold;

wherein causing the notification to be rendered at the computing device and during the rendering of the streaming content is further in response to determining that the application event satisfies the priority threshold.

11. The system of claim 1 , wherein the predicted time is a range of time during which the application event is predicted to occur and wherein in determining that the indication, that the IoT event has occurred, corresponds to the predicted time, one or more of the processors are to determine that the indication that the IoT event has occurred was received within the range of time.

12. The system of claim 11 , wherein one or more processors are further operable to execute the instructions to determine the range of time based on a type classification of the application event.

13. A system, comprising:

memory storing instructions;

one or more processors operable to execute the instructions to:

determine, based on data from an application that is in addition to an active application rendering streaming content at a computing device, that a future event is predicted to occur during a subsequent duration of time;

determine, based on the data, whether the future event satisfies a priority threshold for rendering a notification, for the future event, during the subsequent duration of time; and

in response to determining that the future event satisfies the priority threshold for rendering the notification:

cause a notification of the future event to be rendered, at the computing device and during rendering the streaming content at the computing device, but before actual occurrence of the future event,

wherein the notification characterizes the application based on which the future event is determined.

14. The system of claim 13 , wherein the priority threshold is based on contextual data that is available via one or more additional computing devices and indicates a relative importance of the event.

15. The system of claim 14 , wherein the contextual data includes an identifier for the user that is viewing the streaming content at the computing device.

16. The system of claim 14 , wherein the contextual data characterizes a type classification for the future event.

17. The system of claim 13 , wherein in determining that the future event is predicted to occur one or more of the processors are to determine that the future event is predicted to occur when prior content is being rendered by the application at the interface of the computing device.

18. The system of claim 13 , wherein in causing the notification of the future event to be rendered one or more of the processors are to:

cause the notification to be rendered simultaneous to a scrubber user interface being rendered by the active application at the interface of the computing device.

19. The system of claim 18 , wherein in causing the notification of the future event to be rendered one or more of the processors are to:

cause the notification to be rendered within the scrubber user interface at a relative time, within the scrubber user interface, that corresponds to the subsequent duration of time of the future event.

20. A system, comprising:

memory storing instructions;

one or more processors operable to execute the instructions to:

determine, based on a prior user interaction with an application, a predicted time for an application event to occur, wherein the application event corresponds to the prior user interaction with the application;

receive, from an internet of things (IoT) device and during rendering of streaming content at a display interface of a computing device, an indication that an IoT event has occurred;

determine that the IoT event corresponds to the application event, wherein in determining that the IoT event corresponds to the application event one or more of the processors are to determine that the IoT event corresponds to the application event based on determining that the indication, that the IoT event has occurred, corresponds to the predicted time;

in response to determining that the IoT event corresponds to the application event:

cause a notification to be rendered, at the computing device and during the rendering of the streaming content, that includes application content that is based on the prior user interaction with the application.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2024
From: KUANG, CLIFF; KACZMAREK, JESSE; GUGEL, ANDY; LEE, JONATHAN
To: GOOGLE LLC
Reel/Frame 066310/0693 →
Continuity (4)
Continuation 17985713 · Nov 11, 2022
Continuation 17572433 · Jan 10, 2022
Provisional Application 63290723 · Dec 17, 2021
Related Publication 20240155204A1 · May 9, 2024
References Cited (32)
US 8634533B2 · Strasters · 2014 [cited by applicant]
US 9749701B2 · Mozell et al. · 2017 [cited by applicant]
US 9824578B2 · Burton et al. · 2017 [cited by applicant]
US 9838736B2 · Smith et al. · 2017 [cited by applicant]
US 9967614B2 · McCarthy · 2018 [cited by applicant]
US 10051600B1 · Zhong et al. · 2018 [cited by applicant]
US 10060644B2 · Bruhn et al. · 2018 [cited by applicant]
US 10073428B2 · Bruhn et al. · 2018 [cited by applicant]
US 10091017B2 · Landow et al. · 2018 [cited by applicant]
US 10294600B2 · Beals · 2019 [cited by applicant]
US 10453030B2 · Park et al. · 2019 [cited by applicant]
US 10885917B2 · Schairer et al. · 2021 [cited by applicant]
US 10958953B2 · Lewis et al. · 2021 [cited by applicant]
US 11061543B1 · Blatz et al. · 2021 [cited by applicant]
US 11153147B2 · Wu et al. · 2021 [cited by applicant]
US 11523190B1 · Kuang et al. · 2022 [cited by applicant]
US 20010030667A1 · Kelts · 2001 [cited by applicant]
US 20080092199A1 · McCarthy et al. · 2008 [cited by applicant]
US 20140267911A1 · Grant et al. · 2014 [cited by applicant]
US 20150134761A1 · Sharma et al. · 2015 [cited by applicant]
US 20160127765A1 · Robinson · 2016 [cited by applicant]
US 20180310045A1 · Panchaksharaiah · 2018 [cited by applicant]
US 20190235936A1 · Murdock et al. · 2019 [cited by applicant]
US 20200037038A1 · Shoop · 2020 [cited by applicant]
US 20200092687A1 · Devaraj et al. · 2020 [cited by applicant]
US 20210150381A1 · Alkan et al. · 2021 [cited by applicant]
US 20210174795A1 · Robert Jose et al. · 2021 [cited by applicant]
US 20210374579A1 · Dotan-Cohen et al. · 2021 [cited by applicant]
US 20220094657A1 · Brooks Powell et al. · 2022 [cited by applicant]
US 20230199263A1 · Kuang et al. · 2023 [cited by applicant]
European Patent Office; International Search Report and Written Opinion issued in Application No. PCT/US2022/049444; 20 pages; dated Apr. 25, 2023. [cited by applicant]
European Patent Office; Invitation to Pay Additional Fees issued in Application No. PCT/US2022/049444; 13 pages; dated Mar. 3, 2023. [cited by applicant]