IP Library › Granted Patent US 12,314,672
Granted Patent B1
US 12,314,672 · App. 18/238,375 · Granted May 27, 2025

Routing data communications between client-specific servers and data-center communications servers

Inventors: Ali Arsanjani (Campbell, CA); Bryan R. Martin (Campbell, CA); Manu Mukerji (Campbell, CA); Venkat Nagaswamy (Campbell, CA); Marshall Lincoln (Campbell, CA)
Assignee: 8x8, Inc.
G06F40/30G06F9/54G06F16/90332G06Q30/016H04L51/046H04L67/535
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,314,672
App. No.
18/238,375
Granted
May 27, 2025
Kind
B1
Abstract

Certain aspects of the disclosure are directed to context aggregation in a data communications network. According to a specific example, user-data communications between a client-specific endpoint device and the other participating endpoint device during a first time period can be retrieved from a plurality of interconnected data communications systems. The client station can be configured and arranged to interface with a data communications server providing data communications services on a subscription basis. Context information for each respective user-data communication between the client station and the participating station during the first time period can be aggregated, such that subsequent user-data communications received from the participating station and intended for the client entity, can be routed based on the aggregated context information.

Claims (35)

1. A method for use in a system including a cloud-based configuration of a set of one or more servers (“the server set”), to client-specific endpoint devices associated with a client entity, from among a plurality of different client entities, receiving data communications services from the server set, the method comprising:

organizing communications-related information, including context information and at least one communications-specific characteristic, according to an event-based timeline indicative of events which correspond to user-based data communications sessions that involve a client-specific endpoint, associated with the client entity, and another participating endpoint and that are facilitated by the server set;

for a plurality of time periods of the event-based timeline including a first time period and for one or more later time periods, aggregating and storing the communications-related information, including the context information, in a unified data and events circuit that is to store communication-related event data corresponding to the client entity;

correlating aspects of the communications-related information with the context information, via data-processing computer circuitry, in response to the steps of aggregating and storing the communications-related information; and

processing the correlated aspects via execution of a machine-learning algorithm in the data-processing computer circuitry and, in response, providing to the server set predictive data to indicate a destination to which a user-data communication of a subsequent one of the user-based data communications sessions involving at least one of the client-specific endpoint and the other participating endpoint, should be routed.

2. The method of claim 1 , further including routing, in response to the predictive data, the user-data communication involving the other participating endpoint.

3. The method of claim 1 , further including facilitating and monitoring, via the server set, each of the user-based data communications sessions.

4. The method of claim 1 , further including associating the communications-related information, including the context information, as respectively pertaining to at least one communications-specific characteristic of the user-based data communications sessions.

5. The method of claim 1 , wherein certain aspects of the communications-related information are selected from among recognizable speech or tone features, including one or more of: key words, phrases, tone, and other recognizable features.

6. The method of claim 1 , wherein said correlating aspects of the communications-related information with the context information includes correlating one or more recognizable speech or tone features with an overall context pertaining to one or more of the user-based data communications sessions.

7. An apparatus comprising:

a set of one or more servers (“the server set”) in a cloud-based configuration to provide data communications services to client-specific endpoint devices associated with a client entity from among a plurality of different client entities authorized to receive the data communications services;

data-processing computer circuitry to:

organize communications-related information, including context information and at least one communications-specific characteristic, according to an event-based timeline indicative of events which correspond to user-based data communications sessions that involve a client-specific endpoint, associated with the client entity, and another participating endpoint and that are facilitated by the server set;

aggregate and store, for a plurality of time periods of the event-based timeline including a first time period and for one or more later time periods, the communications-related information, including the context information, in a unified data and events circuit that is to store communication-related event data corresponding to the client entity;

correlate aspects of the communications-related information with the context information, via data-processing computer circuitry, in response to aggregation and storage of the communications-related information; and

process the correlated aspects via execution of a machine-learning algorithm in the data-processing computer circuitry and, in response, provide to the server set predictive data to indicate a destination to which a user-data communication of a subsequent one of the user-based data communications sessions, involving at least one of the client-specific endpoint and the other participating endpoint, should be routed.

8. The apparatus of claim 7 , wherein the data-processing computer circuitry is to generate one or more machine-learning models to predict context information for future data communications.

9. The apparatus of claim 7 , wherein the context information is to be stored by the server set in the unified data and events circuit and to be associated with a client-specific endpoint associated with the client entity.

10. The apparatus of claim 7 , wherein the unified data and events circuit is to store data and events involving the client entity, including content from a plurality of communications from at least one of the following sources: emails, phone calls, and chat messages.

11. The apparatus of claim 7 , wherein the server set is to identify speech characteristic parameters of the user-data communication and determine a sentiment, a criticality, and a topic for the user-data communication.

12. The apparatus of claim 7 , wherein the server set is to monitor the user-based data communications sessions.

13. The apparatus of claim 7 , wherein the server set is to monitor the user-based data communications sessions and, in response, the data-processing computer circuitry is to identify speech characteristic parameters of the user-data communication and determine a sentiment, a criticality, and a topic for the user-data communication.

14. The apparatus of claim 7 , wherein the data-processing computer circuitry is to determine a context for each respective one of the user-based data communications sessions involving the at least one of the client-specific endpoint and the other participating endpoint during the first time period.

15. The apparatus of claim 7 , wherein the data-processing computer circuitry is to develop a client specific database based on certain of the context information.

16. In a system including a set of one or more servers (“the server set”) in a cloud-based configuration to provide data communications services to client-specific endpoint devices associated with a client entity from among a plurality of different client entities authorized to receive the data communications services, an apparatus comprising:

data-processing computer circuitry to

organize communications-related information, including context information and at least one communications-specific characteristic, according to an event-based timeline indicative of events which correspond to user-based data communications sessions that involve a client-specific endpoint, associated with the client entity, and another participating endpoint and that are facilitated by the server set;

aggregate and store, for a plurality of time periods of the event-based timeline including a first time period and for one or more later time periods, the communications-related information, including the context information, in a unified data and events circuit that is to store communication-related event data corresponding to the client entity;

correlate aspects of the communications-related information with the context information, via data-processing computer circuitry, in response to aggregation and storage of the communications-related information; and

process the correlated aspects via execution of a machine-learning algorithm in the data-processing computer circuitry and, in response, predict a destination to which a user-data communication of a subsequent one of the user-based data communications sessions, involving at least one of the client-specific endpoint and the other participating endpoint, should be routed.

17. The apparatus of claim 16 , wherein the data-processing computer circuitry is to develop a client specific database based on certain of the context information, and to use the client specific database to configure the machine-learning algorithm to assign a context to one or more subsequent user-data communications.

18. The apparatus of claim 16 , wherein, for each previous data communication involving the client entity and the other participating endpoint, the event-based timeline is to indicate a plurality of events that transpired and to indicate the context information.

19. The apparatus of claim 16 , wherein the data-processing computer circuitry is to access communication-related event data corresponding to the client entity stored in the unified data and events circuit and to access product usage records related to the accessed communication-related event data to determine an overall context.

20. The apparatus of claim 16 , wherein the server set is to route the subsequent one of the user-based data communications sessions to a representative of the client entity based on an access to the context information and on at least one of a sentiment, a criticality, and a topic.

Assignments (2)
SECURITY INTEREST Recorded Aug 5, 2024
From: 8X8, INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
Reel/Frame 068327/0819 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2023
From: MUKERJI, MANU; NAGASWAMY, VENKAT; LINCOLN, MARSHALL; MARTIN, BRYAN R.; ARSANJANI, ALI
To: 8X8, INC.
Reel/Frame 064710/0628 →
Continuity (2)
Continuation 17203592 · Mar 16, 2021
Continuation 16235972 · Dec 28, 2018
References Cited (168)
US 6061433A · Polcyn et al. · 2000 [cited by applicant]
US 6651058B1 · Sundaresan et al. · 2003 [cited by applicant]
US 7065188B1 · Mei et al. · 2006 [cited by applicant]
US 7369653B2 · Dezonno et al. · 2008 [cited by applicant]
US 7457404B1 · Hession et al. · 2008 [cited by applicant]
US 7602900B1 · Croak et al. · 2009 [cited by applicant]
US 7979840B2 · Zhang et al. · 2011 [cited by applicant]
US 7983401B1 · Krinsky · 2011 [cited by applicant]
US 8316347B2 · Arsanjani et al. · 2012 [cited by applicant]
US 8332813B2 · Arasanjani et al. · 2012 [cited by applicant]
US 8468244B2 · Redlich · 2013 [cited by applicant]
US 8600034B2 · Teitelman et al. · 2013 [cited by applicant]
US 8605878B2 · Claudatos et al. · 2013 [cited by applicant]
US 8739111B2 · Allam et al. · 2014 [cited by applicant]
US 8750123B1 · Alisawi et al. · 2014 [cited by applicant]
US 8874755B1 · Deklich et al. · 2014 [cited by applicant]
US 9031222B2 · Wolfeld · 2015 [cited by applicant]
US 9053211B2 · Goldfarb · 2015 [cited by applicant]
US 9077746B2 · Chandrshekhar · 2015 [cited by applicant]
US 9112974B1 · Wilsie et al. · 2015 [cited by applicant]
US 9160853B1 · Daddi · 2015 [cited by applicant]
US 9160854B1 · Daddi et al. · 2015 [cited by applicant]
US 9171319B2 · Qu et al. · 2015 [cited by applicant]
US 9178999B1 · Hegde et al. · 2015 [cited by applicant]
US 9213564B1 · Klein et al. · 2015 [cited by applicant]
US 9392049B2 · Ennis et al. · 2016 [cited by applicant]
US 9542832B1 · Fu et al. · 2017 [cited by applicant]
US 9552512B2 · Guo et al. · 2017 [cited by applicant]
US 9602666B2 · Ponting et al. · 2017 [cited by applicant]
US 9717017B2 · Backholm et al. · 2017 [cited by applicant]
US 9824145B1 · Rohrweck · 2017 [cited by applicant]
US 9848082B1 · Lillard et al. · 2017 [cited by applicant]
US 9936066B1 · Mammen et al. · 2018 [cited by applicant]
US 10021590B2 · Backholm et al. · 2018 [cited by applicant]
US 10027803B2 · Krinsky et al. · 2018 [cited by applicant]
US 10096063B2 · Dahlwadkar · 2018 [cited by applicant]
US 10194027B1 · Daddi et al. · 2019 [cited by applicant]
US 10198427B2 · Yishay · 2019 [cited by applicant]
US 10282791B2 · O'Neil · 2019 [cited by applicant]
US 10394975B2 · Kim et al. · 2019 [cited by applicant]
US 10419609B1 · Harris · 2019 [cited by applicant]
US 10433243B2 · Lopes et al. · 2019 [cited by applicant]
US 10546008B2 · Yishay · 2020 [cited by applicant]
US 10573312B1 · Thomson · 2020 [cited by applicant]
US 10574822B1 · Sheshaiahgari et al. · 2020 [cited by applicant]
US 10608929B2 · Zaslow et al. · 2020 [cited by applicant]
US 10614107B2 · Yishay · 2020 [cited by applicant]
US 10642889B2 · Reshef et al. · 2020 [cited by applicant]
US 10666799B2 · Kazerani et al. · 2020 [cited by applicant]
US 10855849B1 · Liu et al. · 2020 [cited by applicant]
US 10944800B1 · Arsanjani et al. · 2021 [cited by applicant]
US 10949619B1 · Arsanjani · 2021 [cited by examiner]
US 11025488B1 · Arsanjani · 2021 [cited by examiner]
US 11044338B1 · Arsanjani · 2021 [cited by examiner]
US 11070640B1 · Arsanjani · 2021 [cited by examiner]
US 11140110B2 · Kasireddy et al. · 2021 [cited by applicant]
US 11196866B1 · Samat · 2021 [cited by examiner]
US 11368551B1 · Arsanjani · 2022 [cited by examiner]
US 11445063B1 · Driemeyer · 2022 [cited by examiner]
US 11551005B1 · Arsanjani et al. · 2023 [cited by applicant]
US 11575755B1 · Arsanjani et al. · 2023 [cited by applicant]
US 11790178B1 · Arsanjani · 2023 [cited by examiner]
US 20030078972A1 · Tapissier et al. · 2003 [cited by applicant]
US 20030187868A1 · Igarashi · 2003 [cited by applicant]
US 20040064517A1 · Uenoyama et al. · 2004 [cited by applicant]
US 20040098274A1 · Dezonno et al. · 2004 [cited by applicant]
US 20040122245A1 · Franks · 2004 [cited by examiner]
US 20050152511A1 · Stubley · 2005 [cited by applicant]
US 20050246211A1 · Kaiser · 2005 [cited by applicant]
US 20060233347A1 · Tong et al. · 2006 [cited by applicant]
US 20060285670A1 · Chin · 2006 [cited by applicant]
US 20070025537A1 · Claudatos · 2007 [cited by applicant]
US 20070025539A1 · Claudatos · 2007 [cited by applicant]
US 20070168447A1 · Chen et al. · 2007 [cited by applicant]
US 20080027784A1 · Ang · 2008 [cited by examiner]
US 20080082341A1 · Blair · 2008 [cited by applicant]
US 20080130842A1 · Johri · 2008 [cited by applicant]
US 20080140348A1 · Frank · 2008 [cited by applicant]
US 20080214219A1 · Matsushima · 2008 [cited by applicant]
US 20080219429A1 · Mandalia · 2008 [cited by applicant]
US 20090083768A1 · Hatalkar et al. · 2009 [cited by applicant]
US 20090216734A1 · Aghajanyan et al. · 2009 [cited by applicant]
US 20090254404A1 · Eggenberger · 2009 [cited by applicant]
US 20090254572A1 · Redlich · 2009 [cited by examiner]
US 20090292583A1 · Eilam et al. · 2009 [cited by applicant]
US 20090306984A1 · Mark et al. · 2009 [cited by applicant]
US 20090327172A1 · Liu · 2009 [cited by examiner]
US 20100114954A1 · Sareen et al. · 2010 [cited by applicant]
US 20100197329A1 · Claudatos et al. · 2010 [cited by applicant]
US 20100226490A1 · Schultz et al. · 2010 [cited by applicant]
US 20100250497A1 · Redlich · 2010 [cited by examiner]
US 20110305331A1 · Hughes et al. · 2011 [cited by applicant]
US 20130124463A1 · Lee · 2013 [cited by examiner]
US 20130311511A1 · Peng · 2013 [cited by applicant]
US 20130339436A1 · Gray · 2013 [cited by applicant]
US 20140012826A1 · Wisman et al. · 2014 [cited by applicant]
US 20140064072A1 · Ludwig · 2014 [cited by applicant]
US 20140064202A1 · Norstrom et al. · 2014 [cited by applicant]
US 20140120981A1 · King · 2014 [cited by examiner]
US 20140172444A1 · Moore et al. · 2014 [cited by applicant]
US 20140244652A1 · O'Neil · 2014 [cited by examiner]
US 20140304365A1 · Khanna · 2014 [cited by applicant]
US 20140324420A1 · Sorensen et al. · 2014 [cited by applicant]
US 20150046514A1 · Madan et al. · 2015 [cited by applicant]
US 20150169538A1 · Reynolds et al. · 2015 [cited by applicant]
US 20150170674A1 · Ishibashi · 2015 [cited by applicant]
US 20150242513A1 · Sanghavi et al. · 2015 [cited by applicant]
US 20150243155A1 · Kiong et al. · 2015 [cited by applicant]
US 20150294377A1 · Chow · 2015 [cited by examiner]
US 20150363563A1 · Hallwachs · 2015 [cited by examiner]
US 20150373196A1 · Scott et al. · 2015 [cited by applicant]
US 20160036869A1 · Logan et al. · 2016 [cited by applicant]
US 20160036972A1 · Ristock et al. · 2016 [cited by applicant]
US 20160080428A1 · Fan et al. · 2016 [cited by applicant]
US 20160127553A1 · McCormack et al. · 2016 [cited by applicant]
US 20160182718A1 · Yoakum et al. · 2016 [cited by applicant]
US 20160188960A1 · Guo et al. · 2016 [cited by applicant]
US 20160227431A1 · Alisawi · 2016 [cited by examiner]
US 20160350674A1 · Midboe · 2016 [cited by applicant]
US 20160360039A1 · Sanghavi et al. · 2016 [cited by applicant]
US 20160364368A1 · Chen et al. · 2016 [cited by applicant]
US 20160364488A1 · Shen et al. · 2016 [cited by applicant]
US 20170011740A1 · Gauci · 2017 [cited by applicant]
US 20170019529A1 · Bostick et al. · 2017 [cited by applicant]
US 20170104876A1 · Hibbard et al. · 2017 [cited by applicant]
US 20170214779A1 · Moran et al. · 2017 [cited by applicant]
US 20170236148A1 · James et al. · 2017 [cited by applicant]
US 20170257303A1 · Boyapalle et al. · 2017 [cited by applicant]
US 20170262164A1 · Jain et al. · 2017 [cited by applicant]
US 20170346777A1 · Kim et al. · 2017 [cited by applicant]
US 20180018371A1 · Miller et al. · 2018 [cited by applicant]
US 20180032576A1 · Romero · 2018 [cited by applicant]
US 20180041378A1 · Yan et al. · 2018 [cited by applicant]
US 20180047072A1 · Chow · 2018 [cited by examiner]
US 20180054524A1 · Dahan et al. · 2018 [cited by applicant]
US 20180082112A1 · Keller · 2018 [cited by applicant]
US 20180109574A1 · Vigoda et al. · 2018 [cited by applicant]
US 20180176281A1 · Arunachalam et al. · 2018 [cited by applicant]
US 20180184140A1 · Danker · 2018 [cited by examiner]
US 20180184171A1 · Danker · 2018 [cited by examiner]
US 20180285750A1 · Purushothaman et al. · 2018 [cited by applicant]
US 20180309708A1 · Potvin · 2018 [cited by applicant]
US 20180324041A1 · Deklich · 2018 [cited by examiner]
US 20180351901A1 · Snider et al. · 2018 [cited by applicant]
US 20190012251A1 · Khosrowpour et al. · 2019 [cited by applicant]
US 20190042988A1 · Brown et al. · 2019 [cited by applicant]
US 20190052926A1 · Waterman et al. · 2019 [cited by applicant]
US 20190182200A1 · Jobanputra et al. · 2019 [cited by applicant]
US 20190243836A1 · Nanda et al. · 2019 [cited by applicant]
US 20190253520A1 · Maharana et al. · 2019 [cited by applicant]
US 20190327130A1 · Huang et al. · 2019 [cited by applicant]
US 20190342718A1 · Pylappan et al. · 2019 [cited by applicant]
US 20190349426A1 · Smith · 2019 [cited by examiner]
US 20200004561A1 · Kottler et al. · 2020 [cited by applicant]
US 20200092293A1 · Liu · 2020 [cited by examiner]
US 20200133629A1 · Pratt et al. · 2020 [cited by applicant]
US 20200220741A1 · Sai et al. · 2020 [cited by applicant]
US 20220263783A1 · Jang · 2022 [cited by applicant]
EP 2779538A1 · 2014 [cited by applicant]
GB 2546433A · 2017 [cited by applicant]
WO 2010069567A1 · 2010 [cited by applicant]
USPTO. Final Office Action dated Mar. 20, 2024, received for U.S. Appl. No. 18/086,495 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Sep. 1, 2023, received for U.S. Appl. No. 17/380,412 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Aug. 2, 2024, received for U.S. Appl. No. 17/380,412 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Dec. 4, 2023, received for U.S. Appl. No. 18/086,486 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Mar. 28, 2024, received for U.S. Appl. No. 18/086,486 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Mar. 28, 2024, received for U.S. Appl. No. 18/238,419 of the instant Applicant/Assignee. [cited by applicant]
USPTO. Office Action dated Aug. 15, 2024, received for U.S. Appl. No. 18/089,961 of the instant Applicant/Assignee. [cited by applicant]