# US 10,504,050 B1 · Systems and methods for managing electronic activity driven targets

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

- Number: US 10,504,050 B1
- Document ID: US10504050B1
- Status: Granted
- Kind: B1
- Application number: 16/421,298
- Filed: 2019-05-23
- Published: 2019-11-28
- Granted: 2019-12-10
- Earliest claimed: 2018-05-24
- Assignees: People.ai, Inc.
- Applicants: People.ai, Inc.
- Inventors: Oleg Rogynskyy; Wei Hai; Kavita Shah
- Web page: https://patentgrep.com/patent/US10504050B1

## 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

Methods, systems, and storage media for managing electronic activity driven targets are disclosed. Example implementations may: maintain a plurality of node profiles; select, for a first node profile, using one or more field-value pairs of the first node profile, an endpoint profile generated using electronic activities of second node profiles including one or more field-value pairs that match the one or more field-value pairs of the first node profile, the endpoint profile specifying electronic activity driven targets that can be tracked by parsing electronic activities corresponding to the first node profile; store in one or more data structures, an association between the first node profile and the endpoint profile specifying the electronic activity driven targets; parse a plurality of electronic activities corresponding to the first node profile; and update a metric relating to the electronic activity driven targets responsive to parsing the second plurality of electronic activities.

## Claims

### Claim 1

A method comprising:
maintaining, by one or more processors, a plurality of node profiles respectively corresponding to a plurality of entities, each node profile including a plurality of field-value pairs;
accessing, by the one or more processors, data from a first 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 data from the first plurality of electronic activities;
generating, by the one or more processors, for a first node profile of the plurality of node profiles, an endpoint profile using data from electronic activities of at least one second node profile, the at least one second node profile including one or more field-value pairs that match one or more field-value pairs of the first node profile, the endpoint profile specifying targets that can be tracked based on electronic activities corresponding to the first node profile, the first node profile different from the at least one second node profile, wherein generating the endpoint profile comprises
generating, by the one or more processors, for each second node profile of the at least one second node profile, a respective electronic activity pattern based on a second plurality of electronic activities transmitted or received via electronic accounts of the second node profile, and
setting, by the one or more processors, one or more target values for the endpoint profile based on each respective electronic activity pattern;
storing, by the one or more processors, in one or more data structures, an association between the first node profile and the endpoint profile specifying the targets;
parsing, by the one or more processors, data from a third plurality of electronic activities corresponding to the first node profile;
updating, by the one or more processors, a metric relating to the targets responsive to parsing the data from the third plurality of electronic activities;
determining, by the one or more processors, that the updated metric does not satisfy a threshold value; and
transmitting, by the one or more processors, responsive to determining that the updated metric does not satisfy the threshold value, a notification to a contact identifier corresponding to a third node profile, the notification referencing at least one of the targets.

### Claim 2 (depends on 1)

The method of claim 1, wherein generating the respective electronic activity pattern for the second node profile comprises:
parsing, by the one or more processors, data from each electronic activity of the second plurality of electronic activities;
generating, by the one or more processors, for each electronic activity of the second plurality of electronic activities, one or more activity field-value pairs corresponding to respective node field-value pairs of node profiles of participants of the electronic activity; and
using, by the one or more processors, the one or more activity field-value pairs to generate the respective electronic activity pattern.

### Claim 3 (depends on 2)

The method of claim 2, wherein using the one or more activity-field value pairs to generate the respective electronic activity pattern comprises using a volume of electronic activities that identify participants corresponding to node profiles including node field value pairs that specify a predetermined value of a predetermined field.

### Claim 4 (depends on 1)

The method of claim 1, wherein updating the metric comprises generating an updated metric and further comprising:
determining, by the one or more processors, that the updated metric is below a threshold value; and
transmitting, by the one or more processors responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier specified by the first node profile, the notification referencing at least one of the targets.

### Claim 5 (depends on 1)

The method of claim 1, wherein:
the metric is a count of a number of record objects associated with the first node profile and having a stage status indicating that a last stage of an ordered set of stages has been completed, and
one of the targets requires meeting at least a threshold value for the metric.

### Claim 6 (depends on 1)

The method of claim 1, wherein each second node profile of the second node profiles is associated with at least a threshold number of record objects having a stage status indicating that a specified stage of an ordered set of stages has been completed.

### Claim 7 (depends on 1)

The method of claim 1, wherein the electronic activities corresponding to one of the second node profiles used to generate the endpoint profile correspond to a predetermined time period from a trigger time of the second node profile, and a current time is within the predetermined time period of a trigger time of the first node profile.

### Claim 8

A system comprising:
one or more hardware processors configured by machine-readable instructions to:
maintain a plurality of node profiles respectively corresponding to a plurality of entities, each node profile including a plurality of field-value pairs;
access a first 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 first plurality of electronic activities;
generate, for a first node profile of the plurality of node profiles, an endpoint profile using data from electronic activities of at least one second node profile, the at least one second node profile including one or more field-value pairs that match one or more field-value pairs of the first node profile, the endpoint profile specifying targets that can be tracked based on electronic activities corresponding to the first node profile, the first node profile different from the at least one second node profile, wherein to generate the endpoint profile, the one or more hardware processors are configured to
generate, for each second node profile of the at least one second node profile, a respective electronic activity pattern based on a second plurality of electronic activities transmitted or received via electronic accounts of the second node profile, and
set one or more target values for the endpoint profile based on each respective electronic activity pattern;
store in one or more data structures, an association between the first node profile and the endpoint profile specifying the targets;
parse data from a third plurality of electronic activities corresponding to the first node profile;
update a metric relating to the targets responsive to parsing the data from the third plurality of electronic activities;
determine that the updated metric does not satisfy a threshold value; and
transmit, responsive to determining that the updated metric does not satisfy the threshold value, a notification to a contact identifier corresponding to a third node profile, the notification referencing the at least one of the targets.

### Claim 9 (depends on 1)

The system of claim 1, wherein generating the respective electronic activity pattern for the second node profile comprises: parsing data from each electronic activity of the second plurality of electronic activities; generating, for each electronic activity of the second plurality of electronic activities, one or more activity field-value pairs corresponding to respective node field-value pairs of node profiles of participants of the electronic activity; and using the one or more activity field-value pairs to generate the respective electronic activity pattern.

### Claim 10 (depends on 9)

The system of claim 9, wherein using the one or more activity-field value pairs to generate the respective electronic activity pattern comprises using a volume of electronic activities that identify participants corresponding to node profiles including node field value pairs that specify a predetermined value of a predetermined field.

### Claim 11 (depends on 8)

The system of claim 8, wherein updating the metric comprises generating an updated metric, and the one or more hardware processors are further configured by machine-readable instructions to:
determine that the updated metric is below a threshold value; and
transmit, responsive to determining that the updated metric is below the threshold value, a notification to a contact identifier specified by the first node profile, the notification referencing at least one of the targets.

### Claim 12 (depends on 8)

The system of claim 8, wherein:
the metric is a count of a number of record objects associated with the first node profile and having a stage status indicating that a last stage of an ordered set of stages has been completed, and
one of the electronic activity driven targets requires meeting at least a threshold value for the metric.

### Claim 13 (depends on 8)

The system of claim 8, wherein each second node profile of the second node profiles is associated with at least a threshold number of record objects having a stage status indicating that a specified stage of an ordered set of stages has been completed.

### Claim 14 (depends on 8)

The system of claim 8, wherein the electronic activities corresponding to one of the second node profiles used to generate the endpoint profile correspond to a predetermined time period from a trigger time of the second node profile, and a current time is within the predetermined time period of a trigger time of the first node profile.

### Claim 15

A non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method comprising:
maintaining a plurality of node profiles respectively corresponding to a plurality of entities, each node profile including a plurality of field-value pairs;
accessing a first 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 first plurality of electronic activities;
generating, for a first node profile of the plurality of node profiles, an endpoint profile using data from electronic activities of at least one second node profile, the at least one second node profile including one or more field-value pairs that match one or more field-value pairs of the first node profile, the endpoint profile specifying targets that can be tracked based on electronic activities corresponding to the first node profile, the first node profile different from the at least one second node profile, wherein generating the endpoint profile comprises
generating, for each second node profile of the at least one second node profile, a respective electronic activity pattern based on a second plurality of electronic activities transmitted or received via electronic accounts of the second node profile, and
setting, one or more target values for the endpoint profile based on each respective electronic activity pattern;
storing, in one or more data structures, an association between the first node profile and the endpoint profile specifying the targets;
parsing data from a third plurality of electronic activities corresponding to the first node profile;
updating a metric relating to the targets responsive to parsing the data from the third plurality of electronic activities;
determining that the updated metric does not satisfy a threshold value; and
transmitting, responsive to determining that the updated metric does not satisfy the threshold value, a notification to a contact identifier corresponding to a third node profile, the notification referencing the at least one of the targets.