# US 12,010,190 B2 · Systems and methods for generating node profiles using electronic activity information

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,010,190 B2
- Document ID: US12010190B2
- Status: Granted
- Kind: B2
- Application number: 17/361,094
- Filed: 2021-06-28
- Published: 2021-10-21
- Granted: 2024-06-11
- Earliest claimed: 2018-05-24
- Assignees: People.ai, Inc.
- Applicants: People.ai, Inc.
- Inventors: Oleg Rogynskyy; Rajit Kurien Joseph; Heorhiy Kozlov; Andrey Akselrod
- Web page: https://patentgrep.com/patent/US12010190B2

## CPC

- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- G06F 7/14: Merging, i.e. combining at least two sets of record carriers each arranged in the same ordered sequence to produce a single set having the same ordered sequence
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 11/3024: {where the computing system component is a central processing unit [CPU]}
- G06F 11/3452: {Performance evaluation by statistical analysis}
- G06F 11/3495: {for systems}
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/182: Distributed file systems
- G06F 16/212: {with details for data modelling support}
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/22: Indexing; Data structures therefor; Storage structures
- G06F 16/221: {Column-oriented storage; Management thereof}
- G06F 16/2228: {Indexing structures}
- G06F 16/2264: {Multidimensional index structures}
- G06F 16/2272: {Management thereof}
- G06F 16/23: Updating
- G06F 16/235: {Update request formulation}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/2386: {Bulk updating operations (data conversion details G06F16/258)}
- G06F 16/245: Query processing
- G06F 16/24558: {Binary matching operations}
- G06F 16/24564: {Applying rules; Deductive queries}
- G06F 16/2457: with adaptation to user needs
- G06F 16/24575: {using context}
- G06F 16/24578: {using ranking}
- G06F 16/2477: {Temporal data queries}
- G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses}
- G06F 16/256: {in federated or virtual databases}
- G06F 16/26: Visual data mining; Browsing structured data
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/273: {Asynchronous replication or reconciliation}
- G06F 16/28: Databases characterised by their database models, e.g. relational or object models
- G06F 16/285: {Clustering or classification}
- G06F 16/288: {Entity relationship models}
- G06F 16/289: {Object oriented databases}
- G06F 16/29: Geographical information databases
- G06F 16/313: {Selection or weighting of terms for indexing}
- G06F 16/337: {Profile generation, learning or modification}
- G06F 16/355: Creation or modification of classes or clusters
- G06F 16/901: Indexing; Data structures therefor; Storage structures (for retrieval from the web G06F16/951)
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06F 16/90344: {by using string matching techniques}
- G06F 16/9035: Filtering based on additional data, e.g. user or group profiles
- G06F 16/906: Clustering; Classification
- G06F 16/93: Document management systems
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 40/20: Natural language analysis (semantic analysis of natural language G06F40/30)
- G06F 40/237: Lexical tools
- G06F 40/295: Named entity recognition
- G06F 40/30: Semantic analysis
- G06N 3/08: Learning methods
- G06N 3/09: Supervised learning
- G06N 5/022: Knowledge engineering; Knowledge acquisition
- G06N 5/025: Extracting rules from data
- G06N 5/04: Inference or reasoning models
- G06N 7/02: using fuzzy logic (computing arrangements based on biological models G06N3/00; computing arrangements using knowledge-based models G06N5/00)
- G06Q 10/04: Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" (market predictions or forecasting for commercial activities G06Q30/0202)
- G06Q 10/063114: {Status monitoring or status determination for a person or group}
- G06Q 10/06312: {Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling}
- G06Q 10/06315: {Needs-based resource requirements planning or analysis}
- G06Q 10/06393: {Score-carding, benchmarking or key performance indicator [KPI] analysis}
- G06Q 10/06398: {Performance of employee with respect to a job function}
- G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q 10/1091: Recording time for administrative or management purposes
- G06Q 10/1093: Calendar-based scheduling for persons or groups
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06Q 50/22: Social work or social welfare, e.g. community support activities or counselling services
- G16H 50/20: for computer-aided diagnosis, e.g. based on medical expert systems
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1831: {Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status}
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 41/14: Network analysis or design
- H04L 43/026: using flow identification
- H04L 43/045: for graphical visualisation of monitoring data
- H04L 43/062: related to network traffic
- H04L 43/065: related to network devices
- H04L 43/067: using time frame reporting
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 43/14: {using software, i.e. software packages (network security related monitoring H04L63/1408)}
- H04L 51/046: Interoperability with other network applications or services
- H04L 51/212: using filtering or selective blocking
- H04L 51/234: for tracking messages
- H04L 51/42: Mailbox-related aspects, e.g. synchronisation of mailboxes
- H04L 61/45: Network directories; Name-to-address mapping
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/30: Profiles
- H04L 67/303: Terminal profiles
- H04L 67/306: User profiles
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04M 3/436: Arrangements for screening incoming calls {, i.e. evaluating the characteristics of a call before deciding whether to answer it (based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54)}
- H04M 3/5175: {Call or contact centers supervision arrangements}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/60: {based on actual use of network resources}
- H04M 15/66: {Policy and charging system}
- H04M 15/755: {Account identification}
- H04W 4/24: Accounting or billing
- G06F 40/205: Parsing
- G06N 20/00: Machine learning
- G06Q 10/10: Office automation; Time management
- G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof
- G16H 50/30: for calculating health indices; for individual health risk assessment
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L 61/4594: Address books, i.e. directories containing contact information about correspondents (telephone directories in user terminals H04M1/27453)
- H04L 2101/00: Indexing scheme associated with group H04L61/00
- H04L 2101/35: containing special prefixes
- H04L 2101/37: E-mail addresses
- H04M 3/2218: {Call detail recording}
- H04M 3/56: Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities (video conference systems H04N7/15)
- H04M 15/50: {for cross-charging network operators}
- H04M 2203/556: Statistical analysis and interpretation
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure relates to systems and methods for generating new node profiles using information from electronic activities. The system is configured to maintain node profiles corresponding to unique entities; access electronic activities transmitted or received via electronic accounts associated with data source providers; identify a first email address of a sender and second email addresses of respective recipients of an electronic activity; identify that the first email address matches a value of a field of a first node profile; link the electronic activity to the first node profile; determine that a second email address of a respective recipient of the electronic activity cannot be matched to any node profile associated with the respective participant; and generate, responsive to determining that the electronic activity cannot be matched to any node profile of the plurality of node profiles, a new node profile including the second email address of the respective recipient.

## Claims

### Claim 1

A method comprising:
maintaining, by one or more processors, a plurality of node profiles corresponding to a plurality of unique entities, each node profile including a plurality of fields, each field of the plurality of fields including one or more value data structures, each value data structure of the one or more value data structures including a value and one or more entries corresponding to respective one or more data points that include the value of the value data structure;
accessing, by the one or more processors, a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic activities;
identifying, by the one or more processors, a first email address of a sender and one or more second email addresses of respective recipients of an electronic activity of the plurality of electronic activities;
identifying, by the one or more processors, that the first email address matches a value of a field of a first node profile of the plurality of node profiles;
linking, by the one or more processors, the electronic activity to the first node profile;
determining, by the one or more processors, that a second email address of a respective recipient of the electronic activity does not match any value of a particular field of any of the plurality of node profiles;
determining, by the one or more processors, using one or more additional values identified from the electronic activity, that the electronic activity cannot be matched to any node profile associated with the respective recipient based on a matching policy; and
generating, by the one or more processors, responsive to determining that the electronic activity cannot be matched to any node profile associated with the respective recipient, a new node profile including the second email address of the respective recipient as a value of the particular field of the new node profile.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining, by the one or more processors, that the one or more additional values identifies at least one candidate node profile of the plurality of node profiles to which the second email address can be assigned as a value; and
assigning, by the one or more processors, responsive to determining that the one or more additional values identifies at least one candidate node profile of the plurality of node profiles to which the second email address can be assigned as a value, the second email address as a new value to a particular field of the candidate node profile.

### Claim 3 (depends on 2)

The method of claim 2, further comprising adding an entry identifying the electronic activity in a value data structure corresponding to the new value.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
identifying, by the one or more processors, for a first field of the new node profile, a first value identified from the electronic activity to assign to the first field; and
generating, by the one or more processors, a first value data structure corresponding to the value, the first value data structure including a first entry identifying the electronic activity.

### Claim 5 (depends on 4)

The method of claim 4, wherein the first entry includes a timestamp associated with the electronic activity.

### Claim 6 (depends on 4)

The method of claim 4, further comprising:
identifying, by the one or more processors, for one or more second fields of the new node profile, a respective value derived from the electronic activity to assign to the second field; and
generating, by the one or more processors, a second value data structure corresponding to the respective value, the second value data structure including a second entry identifying the electronic activity.

### Claim 7 (depends on 1)

The method of claim 1, further comprising extracting the additional values from the second email address of the recipient.

### Claim 8 (depends on 1)

The method of claim 1, further comprising applying a value detection policy to the electronic activity, the value detection policy including one or more rules used to detect, from the electronic activity, one or more values of candidate fields of a node profile.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
determining, by the one or more processors, a plurality of values using the value detection policy;
identifying, by the one or more processors, for each value of the plurality of values, a field to which the value corresponds;
generating, by the one or more processors, for each field-value pair including the value and the field to which the value corresponds, a value data structure including an entry identifying the electronic activity; and
generating, by the one or more processors, a confidence score for each value corresponding to a field indicating a likelihood that the value of the field is accurate.

### Claim 10 (depends on 8)

The method of claim 8, wherein applying the value detection policy includes determining a first value for a first field of the node profile based on parsing a first email address.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
comparing, by the one or more processors, field-value pairs of the new node profile to respective field-value pairs of a candidate node profile with which to merge the new node profile;
determining, by the one or more processors, that a number of field-value pairs of the new node profile that match respective field-value pairs of the candidate node profile satisfy a node merge policy; and
merging, by the one or more processors, responsive to the determination, the new node profile with the candidate node profile, wherein merging includes
adding, for each field of the new node profile that includes a value that does not match a corresponding value of the candidate node profile, one or more values and their corresponding value data structures to the respective field of the candidate node profile; and
adding, for each field of the new node profile that includes a value that matches a corresponding value of the candidate node profile, entries of the value data structure of the new node profile to a corresponding value data structure of the candidate node profile.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
identifying, by the one or more processors, a response to the electronic activity;
parsing, by the one more processors, a signature included in the response; and
updating, by the one or more processors, the new node profile to include values from the signature.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
identifying, by the one or more processors, a response to the electronic activity;
parsing, by the one more processors, a signature included in the response;
determining, by the one or more processors, using values derived from the signature, that the sender of the response matches a previously generated node profile of the plurality of node profiles maintained by the one or more processors;
linking, by one or more processors, the electronic activity and the response to the electronic activity to the previously generated node profile.

### Claim 14 (depends on 13)

The method of claim 13, further comprising merging, by the one or more processors, the new node profile with the previously generated node profile such that the second email address is added as a value to a field of the previously generated node profile.

### Claim 15 (depends on 1)

The method of claim 1, further comprising:
executing, by the one or more processors, a deduplication process to merge new node profiles with previously generated node profiles, wherein the deduplication process comprises:
determining, by the one or more processors, that the new node profile belongs to a user for which a previously generated node profile of the plurality of node profiles maintained by the one or more processors already exists; and
merging, by the one or more processors, the new node profile with the previously generated node profile such that the second email address is added as a value to a field of the previously generated node profile.

### Claim 16 (depends on 15)

The method of claim 15, wherein the deduplication process is executed responsive to a trigger condition, wherein the trigger condition is based on one or more of i) a length of time since a previous deduplication process was executed, ii) generation of a predetermined number of new nodes; iii) a number of new electronic activities processed by the one or more processors; or iv) ingestion of electronic activities or record objects from a new data source.

### Claim 17

A system comprising:
one or more hardware processors configured by machine-readable instructions to:
maintain a plurality of node profiles corresponding to a plurality of unique entities, each node profile including a plurality of fields, each field of the plurality of fields including one or more value data structures, each value data structure of the one or more value data structures including a value and one or more entries corresponding to respective one or more data points that include the value of the value data structure;
access a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic activities;
identify a first email address of a sender and one or more second email addresses of respective recipients of an electronic activity of the plurality of electronic activities;
identify that the first email address matches a value of a field of a first node profile of the plurality of node profiles;
link the electronic activity to the first node profile;
determine that a second email address of a respective recipient of the electronic activity does not match any value of a particular field of any of the plurality of node profiles;
determine, using one or more additional values identified from the electronic activity, that the electronic activity cannot be matched to any node profile associated with the respective recipient based on a matching policy; and
generate, responsive to determining that the electronic activity cannot be matched to any node profile associated with the respective recipient, a new node profile including the second email address of the respective recipient as a value of the particular field of the new node profile.

### Claim 18 (depends on 17)

The system of claim 17, wherein the one or more hardware processors are further configured to:
determine that the one or more additional values identifies at least one candidate node profile of the plurality of node profiles to which the second email address can be assigned as a value; and
assign, responsive to determining that the one or more additional values identifies at least one candidate node profile of the plurality of node profiles to which the second email address can be assigned as a value, the second email address as a new value to a particular field of the candidate node profile.

### Claim 19 (depends on 18)

The system of claim 18, wherein the one or more hardware processors are further configured to add an entry identifying the electronic activity in a value data structure corresponding to the new value.

### Claim 20

A non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to cause the one or more processors to:
maintain a plurality of node profiles corresponding to a plurality of unique entities, each node profile of the plurality of node profiles including one or more node field-value pairs, each node field-value pair of the node profile associated with a corresponding field and a node field value;
access a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic activities;
identify a first email address of a sender and one or more second email addresses of respective recipients of an electronic activity of the plurality of electronic activities;
identify that the first email address matches a value of a field of a first node profile of the plurality of node profiles;
link the electronic activity to the first node profile;
determine that a second email address of a respective recipient of the electronic activity does not match any value of a particular field of any of the plurality of node profiles;
determine, using one or more additional values identified from the electronic activity, that the electronic activity cannot be matched to any node profile associated with the respective recipient based on a matching policy; and
generate, responsive to determining that the electronic activity cannot be matched to any node profile associated with the respective recipient, a new node profile including the second email address of the respective recipient as a value of the particular field of the new node profile.