IP Library Granted Patent US 10,666,607
Granted Patent B1
US 10,666,607 · App. 16/457,231 · Granted May 26, 2020

Automated contact deletion based on content communications

Inventors: Madhusudhan Srinivasan (Bangalore, IN); Deviprasad Punja (Bangalore, IN)
Assignee: Rovi Guides, Inc.
H04L61/1594H04M1/2746H04M1/72547H04M1/72566
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 10,666,607
App. No.
16/457,231
Granted
May 26, 2020
Kind
B1
Abstract

Systems and methods for automated contact deletion based on content communications are disclosed herein. Based on a content item electronically communicated from a source account to a destination account, a contact deletion trigger is generated to define a criterion for deleting a contact entry that identifies the source account and is stored for the destination account in a contact database. Based on the contact deletion trigger, a determination is made as to whether the criterion for deleting the contact entry has been met. In response to determining that the criterion for deleting the contact entry has been met, the contact entry is automatically deleted from the contact database.

Claims (42)

1. A method for automated contact deletion based on content communications, the method comprising:

generating, based on a content item electronically communicated from a source account to a destination account, a contact deletion trigger defining a criterion for deleting a contact entry that identifies the source account and is stored for the destination account in a contact database, wherein the contact deletion trigger is based on an action identified based on the content item;

determining, based on the contact deletion trigger, whether the criterion for deleting the contact entry has been met by determining that the action has occurred based on a confirmation message received from a service provider; and

in response to determining that the criterion for deleting the contact entry has been met by determining that the action has occurred based on the confirmation message received from the service provider, automatically deleting the contact entry from the contact database.

2. The method of claim 1 , further comprising:

retrieving a rule from a rules database, the rule defining criteria for identifying contact deletion trigger-related data within the content item; and

identifying, based on the rule, the contact deletion trigger-related data within the content item,

wherein the contact deletion trigger is generated based on the contact deletion trigger-related data identified within the content item.

3. The method of claim 2 , wherein the rule identifies one or more fields of the content item and one or more terms or phrases that signal presence of contact deletion trigger-related data, wherein the identifying the contact deletion trigger-related data within the content item comprises searching the one or more fields of the content item for the one or more terms or phrases.

4. The method of claim 1 , further comprising matching, based on the content item, the source account to the contact entry that identifies the source account and is stored for the destination account in the contact database.

5. The method of claim 1 , further comprising:

in response to determining that the criterion for deleting the contact entry has been met, automatically causing the contact entry to be deleted from a plurality of contact databases that are stored for the destination account in at least one of a cloud storage or a local computing device storage.

6. The method of claim 1 , wherein the contact deletion trigger is a time-based trigger, and wherein the determining whether the criterion for deleting the contact entry has been met comprises determining whether a current time has reached a contact entry deletion time.

7. The method of claim 1 , further comprising:

identifying at least one of a date or a time within the content item; and

based on at least one of the date or the time, generating, as the criterion for deleting the contact entry, at least one of a day or a time for deleting the contact entry.

8. The method of claim 1 , further comprising:

identifying, based on the content item, a service to be provided by the service provider,

wherein the determining whether the criterion for deleting the contact entry has been met comprises determining, based on the confirmation message, whether the service has been provided.

9. The method of claim 1 , wherein the content item comprises at least one of a calendar event notice, a mobile application message, a text message, an email message, a chat-based message, or a social-media-based message, and wherein at least one of the source account or the destination account comprise at least one of a telephone account, an email account, a chat account, a mobile application account, or a social media account.

10. A system for automated contact deletion based on content communications, the system comprising:

a communication port configured to receive, via a communication network, a content item communicated from a source account to a destination account; and

control circuitry configured to:

generate, based on the content item, a contact deletion trigger defining a criterion for deleting a contact entry that identifies the source account and is stored for the destination account in a contact database, wherein the contact deletion trigger is based on an action identified based on the content item;

determine, based on the contact deletion trigger, whether the criterion for deleting the contact entry has been met by determining that the action has occurred based on a confirmation message received from a service provider; and

in response to determining that the criterion for deleting the contact entry has been met by determining that the action has occurred based on a confirmation message received from a service provider, automatically cause the contact entry to be deleted from the contact database.

11. The system of claim 10 , wherein the control circuitry is further configured to:

retrieve a rule from a rules database, the rule defining criteria for identifying contact deletion trigger-related data within the content item; and

identify, based on the rule, the contact deletion trigger-related data within the content item,

wherein the contact deletion trigger is generated based on the contact deletion trigger-related data identified within the content item.

12. The system of claim 11 , wherein the rule identifies one or more fields of the content item and one or more terms or phrases that signal presence of contact deletion trigger-related data, wherein the control circuitry is further configured to identify the contact deletion trigger-related data within the content item by searching the one or more fields of the content item for the one or more terms or phrases.

13. The system of claim 10 , wherein the control circuitry is further configured to match, based on the content item, the source account to the contact entry that identifies the source account and is stored for the destination account in the contact database.

14. The system of claim 10 , wherein the control circuitry is further configured to:

in response to determining that the criterion for deleting the contact entry has been met, automatically cause the contact entry to be deleted from a plurality of contact databases that are stored for the destination account in at least one of a cloud storage or a local computing device storage.

15. The system of claim 10 , wherein the contact deletion trigger is a time-based trigger, and wherein the control circuitry is further configured to determine whether the criterion for deleting the contact entry has been met by determining whether a current time has reached a contact entry deletion time.

16. The system of claim 10 , wherein the control circuitry is further configured to:

identify at least one of a date or a time within the content item; and

based on at least one of the date or the time, generate, as the criterion for deleting the contact entry, at least one of a day or a time for deleting the contact entry.

17. The system of claim 10 , wherein the control circuitry is further configured to:

identify, based on the content item, a service to be provided by the service provider,

wherein the control circuitry is further configured to determine whether the criterion for deleting the contact entry has been met by determining, based on the confirmation message, whether the service has been provided.

18. The system of claim 10 , wherein the content item comprises at least one of a calendar event notice, a mobile application message, a text message, an email message, a chat-based message, or a social-media-based message, and wherein at least one of the source account or the destination account comprise at least one of a telephone account, an email account, a chat account, a mobile application account, or a social media account.

Assignments (7)
CHANGE OF NAME Recorded Oct 3, 2024
From: ROVI GUIDES, INC.
To: ADEIA GUIDES INC.
Reel/Frame 069106/0207 →
RELEASE OF SECURITY INTEREST Recorded Jun 5, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
Reel/Frame 053481/0790 →
RELEASE OF SECURITY INTEREST Recorded Jun 5, 2020
From: HPS INVESTMENT PARTNERS, LLC
To: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
Reel/Frame 053458/0749 →
SECURITY INTEREST Recorded Jun 1, 2020
From: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS INC.; VEVEO, INC.; INVENSAS CORPORATION; INVENSAS BONDING TECHNOLOGIES, INC.; TESSERA, INC.; TESSERA ADVANCED TECHNOLOGIES, INC.; DTS, INC.; PHORUS, INC.; IBIQUITY DIGITAL CORPORATION
To: BANK OF AMERICA, N.A.
Reel/Frame 053468/0001 →
PATENT SECURITY AGREEMENT Recorded Nov 25, 2019
From: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 051110/0006 →
SECURITY INTEREST Recorded Nov 22, 2019
From: ROVI SOLUTIONS CORPORATION; ROVI TECHNOLOGIES CORPORATION; ROVI GUIDES, INC.; TIVO SOLUTIONS, INC.; VEVEO, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT
Reel/Frame 051143/0468 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 16, 2019
From: SRINIVASAN, MADHUSUDHAN; PUNJA, DEVIPRASAD
To: ROVI GUIDES, INC.
Reel/Frame 049768/0759 →