IP Library Granted Patent US 12,204,580
Granted Patent B2
US 12,204,580 · App. 16/457,225 · Granted Jan 21, 2025

Automated contact creation based on content communications

Inventors: Madhusudhan Srinivasan (Bangalore, IN); Deviprasad Punja (Bangalore, IN)
Assignee: Adeia Guides Inc.
G06F16/383G06F16/2358
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,204,580
App. No.
16/457,225
Granted
Jan 21, 2025
Kind
B2
Abstract

Systems and methods for automated contact generation based on content communications are disclosed herein. A rule is retrieved from a rules database, the rule defining criteria for identifying contact-related data within a content item electronically communicated from a source account to a destination account. Based on the rule, the contact-related data within the content item is identified. In response to identifying the contact-related data within the content item, the contact-related data is automatically extracted from the content item, a contact entry corresponding to the source account is automatically generated based on the extracted contact-related data, and the contact entry is automatically stored for the destination account in a contact database.

Claims (61)

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

receiving a content item electronically communicated from a source account to a destination account;

determining a content item type identifier of the content item electronically communicated from the source account to the destination account;

retrieving a rule from a rules database, wherein the rule is based on the content item type identifier of the content item electronically communicated from the source account to the destination account and defines criteria for identifying contact-related data within the content item electronically communicated from the source account to the destination account;

identifying, based on the rule, a content item field within the content item, wherein a field type of the content item field matches a contact-related data type; and

in response to identifying the content item field within the content item, automatically:

extracting the contact-related data from the content item field of the content item;

generating, based on the extracted contact-related data, a contact entry corresponding to the source account; and

storing, for the destination account, the contact entry in a contact database.

2. The method of claim 1 , further comprising:

identifying, based on the rule, contextual information in the content item; and

adding a context identifier to the contact entry based on the contextual information.

3. The method of claim 2 , wherein the contextual information comprises an identifier of a service provider scheduled to provide a service, and wherein the context identifier comprises an identifier of the service provider or of a type of the service.

4. The method of claim 1 , further comprising:

identifying, based on the rule, contextual information in the content item;

based on the contextual information, searching a second source for additional contact-related data corresponding to the source account; and

storing the additional contact-related data in the contact entry.

5. The method of claim 4 , wherein the contextual information comprises an identifier of a service provider, and wherein the searching the second source comprises searching a website of the service provider.

6. The method of claim 1 , wherein the rule identifies one or more fields of the content item and one or more terms or phrases that signal presence of contact-related data, wherein the analyzing the content item comprises searching the one or more fields of the content item for the one or more terms or phrases.

7. The method of claim 1 , further comprising:

storing, in the rules database, content item type identifiers, content item fields for each of the content item type identifiers, and keywords or phrases for each of the content item fields,

wherein the retrieving of the rule from the rules database is performed based on matching the content item to at least one of the content item type identifiers stored in the rules database, matching a field of the content item to at least one of the content item fields stored in the rules database, or matching a keyword or phrase in the content item to at least one of the keywords or phrases stored in the rules database.

8. The method of claim 1 , further comprising:

selecting one of a plurality of independently executable plugins that corresponds to the content item type identifier of the content item; and

activating the selected plugin to perform at least one of the retrieving of the rule, the identifying of the contact-related data, the extracting of the contact-related data, the generating the contact entry, or the storing the contact entry.

9. The method of claim 1 , further comprising:

receiving, at a computing device after the content item has been electronically communicated from the source account to the destination account, a message from the source account to the destination account, wherein the message comprises at least one of an email message, a text message, a chat message, or a telephone call; and

generating, for display via the computing device, the contact entry as an identifier of the source account.

10. 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.

11. A system for automated contact generation 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

determine a content item type identifier of the content item electronically communicated from the source account to the destination account;

a rules database configured to store a rule based on the content item type identifier of the content item electronically communicated from the source account to the destination account and defining criteria for identifying contact-related data within the content item electronically communicated from the source account to the destination account;

a contact database; and

control circuitry configured to:

retrieve the rule from the rules database;

identify, based on the rule, a content item field within the content item, wherein a field type of the content item field matches a contact-related data type; and

in response to identifying the content item field within the content item, automatically:

extract the contact-related data from the content item field of the content item;

generate, based on the extracted contact-related data, a contact entry corresponding to the source account; and

store, for the destination account, the contact entry in the contact database.

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

identify, based on the rule, contextual information in the content item; and

add a context identifier to the contact entry based on the contextual information.

13. The system of claim 12 , wherein the contextual information comprises an identifier of a service provider scheduled to provide a service, and wherein the context identifier comprises an identifier of the service provider or of a type of the service.

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

identify, based on the rule, contextual information in the content item;

based on the contextual information, search a second source for additional contact-related data corresponding to the source account; and

store the additional contact-related data in the contact entry.

15. The system of claim 14 , wherein the contextual information comprises an identifier of a service provider, and wherein the control circuitry is further configured to search the second source by searching a website of the service provider.

16. 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-related data, wherein the control circuitry is further configured to analyze the content item by searching the one or more fields of the content item for the one or more terms or phrases.

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

store, in the rules database, content item type identifiers, content item fields for each of the content item type identifiers, and keywords or phrases for each of the content item fields,

wherein the control circuitry is further configured to retrieve of the rule from the rules database based on matching the content item to at least one of the content item type identifiers stored in the rules database, matching a field of the content item to at least one of the content item fields stored in the rules database, or matching a keyword or phrase in the content item to at least one of the keywords or phrases stored in the rules database.

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

select one of a plurality of independently executable plugins that corresponds to the content item type identifier of the content item; and

activate the selected plugin to perform at least one of the retrieving of the rule, the identifying of the contact-related data, the extracting of the contact-related data, the generating the contact entry, or the storing the contact entry.

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

receive, at a computing device after the content item has been electronically communicated from the source account to the destination account, a message from the source account to the destination account, wherein the message comprises at least one of an email message, a text message, a chat message, or a telephone call; and

generate, for display via the computing device, the contact entry as an identifier of the source 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 049771/0851 →
Continuity (1)
Related Publication 20200409926A1 · Dec 31, 2020
References Cited (25)
US 10489387B1 · Rogynskyy · 2019 [cited by examiner]
US 20040093317A1 · Swan · 2004 [cited by applicant]
US 20060259551A1 · Caldwell · 2006 [cited by applicant]
US 20100216442A1 · Kim · 2010 [cited by applicant]
US 20120004015A1 · Le Thierry D'Ennequin · 2012 [cited by applicant]
US 20120226704A1 · Boland · 2012 [cited by examiner]
US 20140006970A1 · Casey · 2014 [cited by examiner]
US 20140214895A1 · Higgins et al. · 2014 [cited by applicant]
US 20150081697A1 · Ng · 2015 [cited by examiner]
US 20150089354A1 · Abrahami · 2015 [cited by examiner]
US 20150100356A1 · Bessler · 2015 [cited by examiner]
US 20150134389A1 · Punera · 2015 [cited by examiner]
US 20150287099A1 · Soundararajan · 2015 [cited by examiner]
US 20150358447A1 · Horling · 2015 [cited by examiner]
US 20160099903A1 · Dabney et al. · 2016 [cited by applicant]
US 20160099904A1 · Agathangelos · 2016 [cited by examiner]
US 20170005954A1 · Shaltiel et al. · 2017 [cited by applicant]
US 20170124034A1 · Upadhyay et al. · 2017 [cited by applicant]
US 20170169013A1 · Sarikaya · 2017 [cited by examiner]
US 20180131644A1 · Bueker et al. · 2018 [cited by applicant]
US 20200125669A1 · Subedi · 2020 [cited by examiner]
US 20200211077A1 · He · 2020 [cited by examiner]
Amit Agarwal, “How to Extract Email Addresses from your Gmail Messages in Gmail,” Internet article, May 26, 2016 retrieved from the Internet: URL:https://www.labnol.org/internet/extrac t-gmail-addresses/28037/ [retrieve… [cited by applicant]
Mapilab: “How to create Outlook contacts automatically when sending or replying to email”, Internet article, Aug. 10, 2015, Retrieved from the Internet: URL:https://www.mapilab.com/blog/create-ou tlook-contacts-automati… [cited by applicant]
International Search Report and Written Opinion of PCT/US2020/039958 dated Aug. 25, 2020. [cited by applicant]