IP Library Granted Patent US 12,095,719
Granted Patent B2
US 12,095,719 · App. 17/525,434 · Granted Sep 17, 2024

Method and system for the analysis of user content and interactions to define a call to action

Inventors: Mohit Goenka (Santa Clara, CA); Hafeez Shaik (Milpitas, CA); Luis Alves (Sunnyvale, CA); Deepesh Mittal (Santa Clara, CA)
Assignee: YAHOO ASSETS LLC
H04L51/226H04L51/224H04L67/535
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,095,719
App. No.
17/525,434
Granted
Sep 17, 2024
Kind
B2
Abstract

The disclosed embodiments relate to processing of notifications displayed on computing devices. In one embodiment, a method is disclosed comprising receiving a notification and querying at least one activity database that records historical interactions of a user. The method then receives a priority indicator in response to the querying and determines whether the priority indicator indicates a high priority. If so, the method generates, and in some embodiments displays, a second notification.

Claims (106)

1. A method comprising:

receiving, by a processor, a notification addressed to a user, the notification comprising a push notification generated by a messaging service and associated with a mobile application;

querying, by the processor, a call to action activity database to identify similar call to action responses based on a property of the notification, the call to action activity database storing a mapping of user actions and templates to properties of previously received notifications;

loading, by the processor, a call to action template in response to querying the call to action activity database, the call to action template including a plurality of placeholders;

populating, by the processor, the plurality of placeholders with data extracted from the notification to generate a second notification;

displaying, by the processor, the second notification by temporarily displaying a banner including the second notification; and

recording, by the processor, an interaction with the second notification in the call to action activity database.

2. The method of claim 1 , wherein before querying the call to action activity database the method further comprises:

extracting, by the processor, one or more query parameters from the notification;

querying, by the processor, at least one activity database using the one or more query parameters, the at least one activity database comprising data regarding historical interactions of the user;

generating, by the processor, a priority indicator in response to the one or more query parameters by aggregating priority levels of results of querying of the at least one activity database; and

determining, by the processor, that the priority indicator indicates a high priority before querying the call to action activity database.

3. The method of claim 2 , further comprising:

determining, by the processor, that the priority indicator indicates a low priority; and

ignoring, by the processor, the notification when the priority indicator indicates the low priority.

4. The method of claim 2 , wherein querying the at least one activity database comprises:

querying multiple activity databases; and

combining query results of querying the multiple activity databases to generate the priority indicator.

5. The method of claim 4 , wherein the multiple activity databases include a notification activity database and the method further comprises building the notification activity database by:

receiving, by the processor, a third notification;

building, by the processor, a record based on data of the third notification;

marking, by the processor, the record as high priority if the user interacted with the third notification;

marking, by the processor, the record as low priority if the user did not interact with the third notification; and

storing, by the processor, the record in the notification activity database.

6. The method of claim 4 , wherein the multiple activity databases include a message activity database and the method further comprises building the message activity database by:

receiving, by the processor, a message;

building, by the processor, a record based on data of the message;

marking, by the processor, the record as high priority if a positive action was received for the message, the positive action comprising an interaction with a messaging application selected from the group consisting of a read, star, and reply interaction;

marking, by the processor, the record as low priority if a negative action was received for the message, the negative action comprising an interaction with a messaging application selected from the group consisting of a delete and triage interaction; and

storing, by the processor, the record in the message activity database.

7. The method of claim 4 , wherein the multiple activity databases include a contact activity database, and the method further comprises building the contact activity database by:

monitoring, by the processor, messaging activity of a messaging application;

recording, by the processor, positive and negative interactions undertaken with contacts associated with the messaging activity;

classifying, by the processor, a contact as a high priority contact if a number of positive interactions exceeds a first threshold;

classifying, by the processor, the contact as a low priority contact if a number of negative interactions exceeds a second threshold; and

storing, by the processor, the contact in the contact activity database.

8. The method of claim 4 , wherein the multiple activity databases include the call to action activity database and the method further comprises building the call to action activity database by:

selecting, by the processor, a message in a messaging application;

loading, by the processor, a template associated with the message;

detecting, by the processor, an action undertaken by the user with the message;

building, by the processor, a record based on metadata of the message, the template, and the action; and

storing, by the processor, the record in the call to action activity database.

9. A non-transitory computer-readable storage medium for tangibly storing computer program instructions capable of being executed by a computer processor, the computer program instructions defining steps of:

receiving, by a processor, a notification addressed to a user, the notification comprising a push notification generated by a messaging service and associated with a mobile application;

querying, by the processor, a call to action activity database to identify similar call to action responses based on a property of the notification, the call to action activity database storing a mapping of user actions and templates to properties of previously received notifications;

loading, by the processor, a call to action template in response to querying the call to action activity database, the call to action template including a plurality of placeholders;

populating, by the processor, the plurality of placeholders with data extracted from the notification to generate a second notification;

displaying, by the processor, the second notification by temporarily displaying a banner including the second notification; and

recording, by the processor, an interaction with the second notification in the call to action activity database.

10. The non-transitory computer-readable storage medium of claim 9 , wherein before querying the call to action activity database the steps further comprise:

extracting, by the processor, one or more query parameters from the notification;

querying, by the processor, at least one activity database using the one or more query parameters, the at least one activity database comprising data regarding historical interactions of the user;

generating, by the processor, a priority indicator in response to the querying of the at least one activity database by aggregating priority levels of results of the querying; and

determining, by the processor, that the priority indicator indicates a high priority before querying the call to action activity database.

11. The non-transitory computer-readable storage medium of claim 10 , wherein querying the at least one activity database comprises:

querying multiple activity databases; and

combining query results of querying the multiple activity databases to generate the priority indicator.

12. The non-transitory computer-readable storage medium of claim 11 , wherein the multiple activity databases include a notification activity database and the steps further comprise building the notification activity database by:

receiving, by the processor, a third notification;

building, by the processor, a record based on data of the third notification;

marking, by the processor, the record as high priority if the user interacted with the third notification;

marking, by the processor, the record as low priority if the user did not interact with the third notification; and

storing, by the processor, the record in the notification activity database.

13. The non-transitory computer-readable storage medium of claim 11 , wherein the multiple activity databases include a message activity database and the steps further comprise building the message activity database by:

receiving, by the processor, a message;

building, by the processor, a record based on data of the message;

marking, by the processor, the record as high priority if a positive action was received for the message, the positive action comprising an interaction with a messaging application selected from the group consisting of a read, star, and reply interaction;

marking, by the processor, the record as low priority if a negative action was received for the message, the negative action comprising an interaction with a messaging application selected from the group consisting of a delete and triage interaction; and

storing, by the processor, the record in the message activity database.

14. The non-transitory computer-readable storage medium of claim 11 , wherein the multiple activity databases include a contact activity database and the steps further comprise building the contact activity database by:

monitoring, by the processor, messaging activity of a messaging application;

recording, by the processor, positive and negative interactions undertaken with contacts associated with the messaging activity;

classifying, by the processor, a contact as a high priority contact if a number of positive interactions exceeds a first threshold;

classifying, by the processor, the contact as a low priority contact if a number of negative interactions exceeds a second threshold; and

storing, by the processor, the contact in the contact activity database.

15. The non-transitory computer-readable storage medium of claim 11 , the steps further comprising building the call to action activity database by:

selecting, by the processor, a message in a messaging application;

loading, by the processor, a template associated with the message;

detecting, by the processor, an action undertaken by the user with the message;

building, by the processor, a record based on metadata of the message, the template, and the action; and

storing, by the processor, the record in the call to action activity database.

16. A device comprising:

a processor configured to:

receive a notification addressed to a user, the notification comprising a push notification generated by a messaging service and associated with a mobile application;

query a call to action activity database to identify similar call to action responses based on a property of the notification, the call to action activity database storing a mapping of user actions and templates to properties of previously received notifications;

load a call to action template in response to querying the call to action activity database, the call to action template including a plurality of placeholders;

populate the plurality of placeholders with data extracted from the notification to generate a second notification;

display the second notification by temporarily displaying a banner including the second notification; and

record an interaction with the second notification in the call to action activity database.

17. The device of claim 16 , wherein before querying the call to action activity database the processor is further configured to:

extract one or more query parameters from the notification;

query at least one activity database using the one or more query parameters, the at least one activity database comprising data regarding historical interactions of the user;

generate a priority indicator in response to the querying of the at least one activity database by aggregating priority levels of results of the querying; and

determine that the priority indicator indicates a high priority before querying the call to action activity database.

18. The device of claim 17 , the processor further configured to:

determine that the priority indicator indicates a low priority; and

ignore the notification when the priority indicator indicates the low priority.

19. The device of claim 18 , wherein querying the at least one activity database comprises:

querying multiple activity databases; and

combining query results of querying the multiple activity databases to generate the priority indicator.

20. The device of claim 16 , the processor further configured to build the call to action activity database by:

selecting, by the processor, a message in a messaging application;

loading, by the processor, a template associated with the message;

detecting, by the processor, an action undertaken by the user with the message;

building, by the processor, a record based on metadata of the message, the template, and the action; and

storing, by the processor, the record in the call to action activity database.

Assignments (5)
SUPPLEMENTAL PATENT SECURITY AGREEMENT Recorded Sep 17, 2025
From: YAHOO ASSETS LLC
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 072915/0540 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2024
From: YAHOO AD TECH LLC (FORMERLY VERIZON MEDIA INC.)
To: YAHOO ASSETS LLC
Reel/Frame 068277/0154 →
CHANGE OF NAME Recorded Mar 22, 2022
From: VERIZON MEDIA INC.
To: YAHOO AD TECH LLC
Reel/Frame 059472/0328 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2021
From: GOENKA, MOHITA; SHAIK, HAFEEZ; ALVES, LUIS; MITTAL, DEEPESH
To: OATH INC.
Reel/Frame 058100/0675 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2021
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 058896/0281 →