Systems and methods for updating node profile status based on automated electronic activity

• US 10,509,781 B1
• Filed: 03/21/2019
• Issued: 12/17/2019
• Est. Priority Date: 05/24/2018
• Status: Active Grant

• Current Assignee: People.ai, Inc.
• Original Assignee: People.ai, Inc.
• Inventors: Rogynskyy, Oleg, Akselrod, Andrey, Brunets, Yurii
• Primary Examiner(s): Uddin, Md I
• Application Number:
  US16/360,997
• Publication Number:
  US 20190361873A1
• Time in Patent Office: 271 Days
• Field of Search: 707705, 707769, 70799901
• CPC Class Codes: G06F 11/3024 where the computing system component is a central processing unit [CPU]
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/235 Update request formulation
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/2386 : Bulk updating operations data conversion details G06F16/258
• CPC Class Codes: G06F 16/245 : Query processing
• CPC Class Codes: G06F 16/24558 : Binary matching operations
• CPC Class Codes: G06F 16/24564 : Applying rules; Deductive queries
• CPC Class Codes: G06F 16/2457 : with adaptation to user needs
• CPC Class Codes: G06F 16/24575 : using context
• CPC Class Codes: G06F 16/24578 : using ranking
• CPC Class Codes: G06F 16/2477 : Temporal data queries
• CPC Class Codes: G06F 16/254 : Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/256 : in federated or virtual databases
• CPC Class Codes: G06F 16/26 : Visual data mining; Browsing structured data
• CPC Class Codes: G06F 16/27 : Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 : Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/28 : Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 16/285 : Clustering or classification
• CPC Class Codes: G06F 16/288 : Entity relationship models
• CPC Class Codes: G06F 16/289 : Object oriented databases
• CPC Class Codes: G06F 16/29 : Geographical information databases
• CPC Class Codes: G06F 16/313 : Selection or weighting of terms for indexing
• CPC Class Codes: G06F 16/337 : Profile generation, learning or modification
• CPC Class Codes: G06F 16/355 : Class or cluster creation or modification
• CPC Class Codes: G06F 16/901 : Indexing; Data structures therefor; Storage structures for retrieval from the web G06F16/951
• CPC Class Codes: G06F 16/9024 : Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06F 16/90344 : by using string matching techniques
• CPC Class Codes: G06F 16/9035 : Filtering based on additional data, e.g. user or group profiles
• CPC Class Codes: G06F 16/906 : Clustering; Classification
• CPC Class Codes: G06F 16/93 : Document management systems
• CPC Class Codes: G06F 16/9535 : Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 21/6218 : to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6245 : Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 40/20 : Natural language analysis semantic analysis of natural language G06F40/30
• CPC Class Codes: G06F 40/205 : Parsing
• CPC Class Codes: G06F 40/237 : Lexical tools
• CPC Class Codes: G06F 40/295 : Named entity recognition
• CPC Class Codes: G06F 40/30 : Semantic analysis
• CPC Class Codes: 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
• CPC Class Codes: G06F 9/542 : Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06N 20/00 : Machine learning
• CPC Class Codes: G06N 3/08 : Learning methods
• CPC Class Codes: G06N 5/022 : Knowledge engineering; Knowledge acquisition
• CPC Class Codes: G06N 5/025 : Extracting rules from data
• CPC Class Codes: G06N 5/04 : Inference or reasoning models
• CPC Class Codes: G06N 7/02 : using fuzzy logic computing arrangements based on biological models G06N3/00; computing arrangements using knowledge-based models G06N5/00
• CPC Class Codes: 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
• CPC Class Codes: G06Q 10/063114 : Status monitoring or status determination for a person or group
• CPC Class Codes: G06Q 10/06312 : Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/06315 : Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/06393 : Score-carding, benchmarking or key performance indicator [KPI] analysis
• CPC Class Codes: G06Q 10/06398 : Performance of employee with respect to a job function
• CPC Class Codes: G06Q 10/10 : Office automation; Time management
• CPC Class Codes: G06Q 10/107 : Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 10/109 : Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: G06Q 10/1091 : Recording time for administrative or management purposes
• CPC Class Codes: G06Q 10/1095 : Meeting or appointment
• CPC Class Codes: G06Q 30/0201 : Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 50/01 : Social networking
• CPC Class Codes: G06Q 50/22 : Social work or social welfare, e.g. community support activities or counselling services
• CPC Class Codes: G16H 15/00 : ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 50/20 : for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/30 : for calculating health indices; for individual health risk assessment
• CPC Class Codes: H04L 12/14 : Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1407 : Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 12/1831 : Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
• CPC Class Codes: H04L 2101/00 : Indexing scheme associated with group H04L61/00
• CPC Class Codes: H04L 2101/35 : containing special prefixes
• CPC Class Codes: H04L 2101/37 : E-mail addresses
• CPC Class Codes: H04L 41/082 : the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/14 : Network analysis or design
• CPC Class Codes: H04L 43/026 : using flow identification
• CPC Class Codes: H04L 43/045 : for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/062 : related to network traffic
• CPC Class Codes: H04L 43/065 : related to network devices
• CPC Class Codes: H04L 43/067 : using time frame reporting
• CPC Class Codes: H04L 43/08 : Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0876 : Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/14 : using software, i.e. software packages network security related monitoring H04L63/1408
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 51/212 : using filtering or selective blocking
• CPC Class Codes: H04L 51/234 : for tracking messages
• CPC Class Codes: H04L 51/42 : Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 61/45 : Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4594 : Address books, i.e. directories containing contact information about correspondents telephone directories in user terminals H04M1/27453
• CPC Class Codes: H04L 67/125 : involving control of end-device applications over a network
• CPC Class Codes: H04L 67/30 : Profiles
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: 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
• CPC Class Codes: H04M 15/41 : Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/50 : for cross-charging network operators
• CPC Class Codes: H04M 15/58 : based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/60 : based on actual use of network resources
• CPC Class Codes: H04M 15/66 : Policy and charging system
• CPC Class Codes: H04M 15/755 : Account identification
• CPC Class Codes: H04M 2203/556 : Statistical analysis and interpretation
• CPC Class Codes: H04M 3/2218 : Call detail recording
• CPC Class Codes: 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
• CPC Class Codes: H04M 3/5175 : Call or contact centers supervision arrangements
• CPC Class Codes: H04M 3/56 : Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04W 4/24 : Accounting or billing

Abstract

The present disclosure relates to systems and methods for updating a node profile status based on automated electronic activity. The method may include accessing electronic activities transmitted or received via electronic accounts; identifying, for an electronic activity account, a second electronic activity automatically generated and transmitted in response to a first electronic activity transmitted from the electronic activity account; determining that the second electronic activity is an automated electronic activity responsive to the first electronic activity; determining, responsive to parsing content included in a body of the second electronic activity, a context related to the second electronic activity; identifying a node profile corresponding to the recipient of the first electronic activity and identified by the second electronic activity; and updating the identified node profile corresponding to the recipient based on the context.

Claims

1. A method, comprising:

accessing, by one or more processors, data from a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers;

maintaining, by the one or more processors, a plurality of node profiles, each node profile of the plurality of node profiles corresponding to an entity, each node profile including one or more field-value pairs including values extracted from the data from the plurality of electronic activities;

identifying, by the one or more processors, for a first electronic activity account of a first data source provider, a second electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a first electronic activity of the plurality of electronic activities transmitted from the first electronic activity account, the first electronic activity transmitted to a recipient and the second electronic activity identifying the recipient;

determining, by the one or more processors, that the second electronic activity is an automated electronic activity responsive to the first electronic activity;

determining, by the one or more processors, responsive to parsing content included in a body of the second electronic activity, a context related to the second electronic activity;

matching, by the one or more processors, from the plurality of node profiles, a node profile corresponding to the recipient of the first electronic activity with the second electronic activity by comparing a contact identifier of the recipient extracted from the second electronic activity with a field-value pair of the node profile, the field-value pair identifying the contact identifier of the recipient and identifying a value data structure including at least a first entry corresponding to the first electronic activity or the second electronic activity;

updating, by the one or more processors, responsive to the second electronic activity, a status associated with the node profile corresponding to the recipient based on the context;

identifying, by the one or more processors, for a second electronic activity account of a second data source provider, a fourth electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a third electronic activity of the plurality of electronic activities transmitted from the second electronic activity account, the third electronic activity transmitted to the recipient and the fourth electronic activity identifying the recipient;

determining, by the one or more processors, that the fourth electronic activity is a second automated electronic activity responsive to the third electronic activity; and

updating, by the one or more processors, a confidence score of the status of the node profile based on the fourth electronic activity.

2. The method of claim 1, wherein determining that the second electronic activity is the automated electronic activity comprises determining a first time at which the first electronic activity was transmitted to the recipient and a second time at which the second electronic activity was received at the first electronic activity account;

and

wherein determining that the second electronic activity is the automated electronic activity comprises determining, by the one or more processors, that a difference between the first time and the second time is less than a predetermined threshold.

3. The method of claim 1, further comprising:

determining, by the one or more processors, that the automated electronic activity is an automatically generated bounceback electronic activity; and

wherein updating the status associated with the node profile corresponding to the recipient based on the context comprises updating, by the one or more processors, the node profile of the recipient to indicate that contact information corresponding to the recipient of the first electronic activity is invalid.

4. The method of claim 3, further comprising determining, by the one or more processors, that the contact information of the recipient included in the first electronic activity matches a value of a field of the node profile of the recipient prior to updating, by the one or more processors, the node profile of the recipient to indicate that the contact information corresponding to the recipient of the first electronic activity is invalid.

5. The method of claim 1, wherein

updating the status associated with the node profile corresponding to the recipient based on the context comprises updating the node profile based on the context.

6. The method of claim 5, wherein updating the node profile based on the context comprises updating a confidence score of a value of the node profile.

7. The method of claim 1, wherein updating the status associated with the node profile comprises assigning a label to one of an email address value of the node profile or the node profile, the label used to indicate that the email address value is no longer valid or the recipient has an active autoresponder.

8. The method of claim 1, wherein the contact identifier is an email address and further comprising identifying the email address included in the first electronic activity and identified by the automated electronic activity;

and

wherein matching the node profile corresponding to the recipient of the first electronic activity and identified by the second electronic activity further comprises identifying the node profile using the email address.

9. The method of claim 1, further comprising:

determining, by the one or more processors, that the automated electronic activity is an automated bounceback responsive to one of parsing the content of the body of the automated electronic activity or identifying content included in a header of the automated electronic activity.

10. The method of claim 1, further comprising:

determining, by the one or more processors, that the automated electronic activity is generated by an autoresponder set up by the recipient responsive to one of parsing the content of the body of the automated electronic activity or identifying content included in a header of the automated electronic activity; and

using the context to update a life event record corresponding to the node profile.

11. A system, comprising:

one or more hardware processors configured by machine-readable instructions to;

access data from a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers;

maintain a plurality of node profiles, each node profile of the plurality of node profiles corresponding to an entity, each node profile including one or more field-value pairs including values extracted from the data from the plurality of electronic activities;

identify, for a first electronic activity account of a first data source provider, a second electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a first electronic activity of the plurality of electronic activities transmitted from the first electronic activity account, the first electronic activity transmitted to a recipient and the second electronic activity identifying the recipient;

determine that the second electronic activity is an automated electronic activity responsive to the first electronic activity;

determine, responsive to parsing content included in a body of the second electronic activity, a context related to the second electronic activity;

match, from the plurality of node profiles, a node profile corresponding to the recipient of the first electronic activity with the second electronic activity by comparing a contact identifier of the recipient extracted from the second electronic activity with a field-value pair of the node profile, the field-value pair identifying the contact identifier of the recipient and identifying a value data structure including at least a first entry corresponding to the first electronic activity or the second electronic activity;

update, responsive to the second electronic activity, a status associated with the node profile corresponding to the recipient based on the context;

identify, for a second electronic activity account of a second data source provider, a fourth electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a third electronic activity of the plurality of electronic activities transmitted from the second electronic activity account, the third electronic activity transmitted to the recipient and the fourth electronic activity identifying the recipient;

determine that the fourth electronic activity is a second automated electronic activity responsive to the third electronic activity; and

update a confidence score of the status of the node profile based on the fourth electronic activity.

12. The system of claim 11, wherein determining that the second electronic activity is the automated electronic activity comprises determining a first time at which the first electronic activity was transmitted to the recipient and a second time at which the second electronic activity was received at the first electronic activity account;

and

wherein to determine that the second electronic activity is the automated electronic activity the one or more hardware processors are configured to determine that a difference between the first time and the second time is less than a predetermined threshold.

13. The system of claim 11, wherein the one or more hardware processors are further configured by the machine-readable instructions to:

determine that the automated electronic activity is an automatically generated bounceback electronic activity; and

wherein to update the status associated with the node profile corresponding to the recipient based on the context, the one or more hardware processors;

are further configured by the machine-readable instructions to update the node profile of the recipient to indicate that contact information corresponding to the recipient of the first electronic activity is invalid.

14. The system of claim 13, wherein the one or more hardware processors are further configured by the machine-readable instructions to determine that the contact information of the recipient included in the first electronic activity matches a value of a field of the node profile of the recipient prior to updating the node profile of the recipient to indicate that the contact information corresponding to the recipient of the first electronic activity is invalid.

15. The system of claim 11, wherein to update the status associated with the node profile corresponding to the recipient based on the context, the one or more hardware processors are further configured by the machine-readable instructions to update the node profile of the recipient based on the context.

16. The system of claim 15, wherein updating the node profile based on the context comprises updating a confidence score of a value of the node profile.

17. The system of claim 11, wherein updating the status associated with the node profile based on the context comprises assigning a label to one of an email address value of the node profile or the node profile, the label used to indicate that the email address value is no longer valid or the recipient has an active autoresponder.

18. The system of claim 11, wherein the contact identifier is an email address and wherein the one or more hardware processors are further configured by the machine-readable instructions to identify the email address included in the first electronic activity and identified by the automated electronic activity;

wherein to match the node profile corresponding to the recipient of the first electronic activity and identified by the second electronic activity further comprises identifying the node profile using the email address.

19. The system of claim 11, wherein the one or more hardware processors are further configured by the machine-readable instructions to:

determine, by the one or more hardware processors, that the automated electronic activity is an automated bounceback responsive to one of parsing the content of the body of the automated electronic activity or identifying content included in a header of the automated electronic activity.

20. A non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to:

access data from a plurality of electronic activities transmitted or received via electronic accounts associated with a plurality of data source providers;

maintain a plurality of node profiles, each node profile of the plurality of node profiles corresponding to an entity, each node profile including one or more field-value pairs including values extracted from the data from the plurality of electronic activities;

identify, for a first electronic activity account of a first data source provider, a second electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a first electronic activity of the plurality of electronic activities transmitted from the first electronic activity account, the first electronic activity transmitted to a recipient and the second electronic activity identifying the recipient;

determine that the second electronic activity is an automated electronic activity responsive to the first electronic activity;

determine, responsive to parsing content included in a body of the second electronic activity, a context related to the second electronic activity;

match, from the plurality of node profiles, a node profile corresponding to the recipient of the first electronic activity with the second electronic activity by comparing a contact identifier of the recipient extracted from the second electronic activity with a field-value pair of the node profile, the field-value pair identifying the contact identifier of the recipient and identifying a value data structure including at least a first entry corresponding to the first electronic activity or the second electronic activity;

update, responsive to the second electronic activity, a status associated with the node profile corresponding to the recipient based on the context;

identify, for a second electronic activity account of a second data source provider, a fourth electronic activity of the plurality of electronic activities automatically generated and transmitted in response to a third electronic activity of the plurality of electronic activities transmitted from the second electronic activity account, the third electronic activity transmitted to the recipient and the fourth electronic activity identifying the recipient;

determine that the fourth electronic activity is a second automated electronic activity responsive to the third electronic activity; and

update a confidence score of the status of the node profile based on the fourth electronic activity.