IP Library › Granted Patent US 12,200,166
Granted Patent B2
US 12,200,166 · App. 17/891,101 · Granted Jan 14, 2025

Simultaneous voice and data content driven commercial data platform

Inventors: Trysit Nitidharmatut (Bangkok, TH); Timothy Maslyn (Cupertino, CA); Vira Intanate (Samutprakarn, TH)
H04M3/42068H04L51/02H04M1/72469H04M2201/42H04M2203/256
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,200,166
App. No.
17/891,101
Granted
Jan 14, 2025
Kind
B2
Abstract

One disclosed system comprises a server; a receiver device with a receiver identifier; a dialer device with a dialer identifier; a dialer programmed to initiate a voice call, over a voice channel, with the receiver device using the receiver identifier; a database; and a data channel connecting the dialer device, the receiver device, and the server. The database stores interaction data in association with both the receiver identifier and the dialer identifier. The system is programmed to: obtain a voice sample from the voice call; process the voice sample to obtain a search cue; obtain one or more interaction data from the database using the search cue; obtain a response data from the one or more interaction data; and surface, during the voice call, the response data to one of the dialer device and the receiver device.

Claims (101)

1. A system comprising:

a server;

a receiver device with a receiver identifier;

a dialer device with a dialer identifier;

a dialer programmed to initiate a voice call, over a voice channel, with the receiver device using the receiver identifier;

a database; and

a data channel connecting the dialer device, the receiver device, and the server;

wherein the database stores interaction data in association with both the receiver identifier and the dialer identifier;

wherein the system is programmed to:

obtain a voice sample from the voice call;

process the voice sample to obtain a search cue;

obtain one or more interaction data from the database using the search cue;

obtain a response data from the one or more interaction data; and

surface, during the voice call, the response data to one of the dialer device and the receiver device.

2. The system of claim 1 , wherein the server stores, in the database, the response data in association with both the receiver identifier and the dialer identifier.

3. The system of claim 1 , further comprising:

a display manager: (i) stored on the dialer device; and (ii) programmed to generate display content for a display of the dialer device using the response data.

4. The system of claim 1 , further comprising:

a display manager: (i) stored on the receiver device; and (ii) programmed to generate display content for a display of the receiver device using the response data.

5. The system of claim 1 , further comprising:

a first interaction manager: (i) stored on the dialer device; and (ii) programmed to transmit, over the data channel, a first set of interaction data to the server during the voice call; and

a second interaction manager: (i) stored on the receiver device; and (ii) programmed to transmit, over the data channel, a second set of interaction data to the server during the voice call;

wherein the server is programmed to store data from both the first set of interaction data and the second set of interaction data in the database in association with both the receiver identifier and the dialer identifier.

6. The system of claim 1 , further comprising:

a non-transitory computer-readable medium storing executable instructions to:

obtain the voice sample from the voice call;

process the voice sample to obtain the search cue;

obtain, using the search cue, the one or more interaction data from the database;

obtain the response data using the one or more interaction data; and

surface, during the voice call, the response data to one of the dialer device and the receiver device.

7. The system of claim 1 , wherein:

the dialer device is programmed to obtain the voice sample from the voice call and transmit, over the data channel, the voice sample to the server; and

the server is programmed to:

receive the voice sample from the voice call;

process the voice sample to obtain the search cue;

obtain, using the search cue, the one or more interaction data from the database;

obtain the response data using the one or more interaction data; and

surface, during the voice call, the response data to one of the dialer device and the receiver device.

8. The system of claim 1 , wherein:

the receiver device is programmed to obtain the voice sample from the voice call and transmit, over a data channel connecting the receiver device and the server, the voice sample to the server; and

the server is programmed to:

receive the voice sample from the voice call;

process the voice sample to obtain the search cue;

obtain, using the search cue, the one or more interaction data from the database;

obtain the response data using the one or more interaction data; and

surface, during the voice call, the response data to one of the dialer device and the receiver device.

9. The system of claim 1 , wherein the dialer device is programmed to:

obtain the voice sample from the voice call;

process the voice sample to obtain the search cue;

obtain, over the data channel, the one or more interaction data from the database using the search cue;

obtain the response data using the one or more interaction data; and

display, during the voice call, the response data on a display of the dialer device.

10. The system of claim 1 , wherein the receiver device is programmed to:

obtain the voice sample from the voice call;

process the voice sample to obtain the search cue;

obtain, over the data channel, the one or more interaction data from the database using the search cue; and

display, during the voice call, the response data on a display of the receiver device.

11. The system of claim 1 , wherein:

the interaction data comprises a dialer profile in association with the dialer identifier; and

the response data comprises at least a portion of the dialer profile.

12. The system of claim 1 , wherein:

the interaction data comprises a work profile in association with the dialer identifier; and

the response data comprises at least a portion of the work profile.

13. The system of claim 1 , wherein:

the interaction data comprises a ranking associated with the dialer identifier; and

the response data comprises the ranking.

14. The system of claim 1 , wherein:

the interaction data comprises a receiver profile in association with the receiver identifier; and

the response data comprises at least a portion of the receiver profile.

15. The system of claim 1 , wherein:

the interaction data comprises a business profile in association with the receiver identifier; and

the response data comprises at least a portion of the business profile.

16. The system of claim 1 , wherein:

the interaction data comprises a ranking associated with the receiver identifier; and

the response data comprises the ranking.

17. The system of claim 1 , wherein:

the interaction data comprises a menu of products or services offered in association with the receiver identifier; and

the response data comprises at least a portion of the menu.

18. The system of claim 1 , wherein:

the interaction data comprises a menu of products or services offered in association with the receiver identifier; and

the response data comprises at least a portion of the menu.

19. A method, in which each step is conducted by a system comprising a dialer device with a dialer identifier, a receiver device with a receiver identifier, a dialer programmed to initiate a voice call, over a voice channel, with the receiver device using the receiver identifier, and a database for storing interaction data in association with both the receiver identifier and the dialer identifier, the method comprising:

initiating a voice call, over the voice channel, with the receiver device using the receiver identifier;

obtaining a voice sample from the voice call;

processing the voice sample to obtain a search cue;

obtaining, using the search cue, one or more interaction data from the database;

obtaining a response data using the one or more interaction data; and

surfacing, during the voice call, the response data to one of the dialer device and the receiver device.

20. A system comprising:

a server;

a chatbot receiver device with a receiver identifier;

a dialer device with a dialer identifier;

a dialer programmed to initiate a voice call, over a voice channel, with the chatbot receiver device using the receiver identifier;

a database; and

a data channel connecting the dialer device and the server;

wherein the server is programmed to store, in the database, interaction data in association with one of the receiver identifier and the dialer identifier;

wherein the voice channel is a voice connection over a packet-switched network; and

wherein the system is programmed to:

obtain a voice sample from the voice call;

process the voice sample to obtain a response data from the voice sample; and

store, in the database, the response data in association with one of the receiver identifier and the dialer identifier.

Continuity (6)
Continuation In Part 17340600 · Jun 7, 2021
Continuation In Part 15931447 · May 13, 2020
Continuation In Part 16730882 · Dec 30, 2019
Continuation In Part 16176113 · Oct 31, 2018
Provisional Application 62611690 · Dec 29, 2017
Related Publication 20220394126A1 · Dec 8, 2022
References Cited (64)
US 5544231A · Cho · 1996 [cited by applicant]
US 6327343B1 · Epstein et al. · 2001 [cited by applicant]
US 6987841B1 · Byers et al. · 2006 [cited by applicant]
US 7277445B2 · Bartfeld et al. · 2007 [cited by applicant]
US 7379881B2 · Smithies et al. · 2008 [cited by applicant]
US 7418090B2 · Reding et al. · 2008 [cited by applicant]
US 8036355B2 · Velarde · 2011 [cited by applicant]
US 8107613B2 · Gumbula · 2012 [cited by applicant]
US 8320536B2 · Portman et al. · 2012 [cited by applicant]
US 8335299B1 · Crandall et al. · 2012 [cited by applicant]
US 8428559B2 · Silva · 2013 [cited by applicant]
US 8510116B1 · Moy et al. · 2013 [cited by applicant]
US 8675638B2 · Croak et al. · 2014 [cited by applicant]
US 8687786B2 · Chiczewski et al. · 2014 [cited by applicant]
US 8761353B1 · Apple et al. · 2014 [cited by applicant]
US 8897428B2 · Walker et al. · 2014 [cited by applicant]
US 10431209B2 · Bhaya · 2019 [cited by examiner]
US 20020152142A1 · Schellmann et al. · 2002 [cited by applicant]
US 20020167936A1 · Goodman · 2002 [cited by examiner]
US 20020168967A1 · Clapper · 2002 [cited by applicant]
US 20030097438A1 · Bearden et al. · 2003 [cited by applicant]
US 20030220835A1 · Barnes · 2003 [cited by applicant]
US 20050125342A1 · Schiff · 2005 [cited by applicant]
US 20050286708A1 · Slosberg et al. · 2005 [cited by applicant]
US 20060056599A1 · Cragun · 2006 [cited by applicant]
US 20060285662A1 · Yin · 2006 [cited by applicant]
US 20070135101A1 · Ramati · 2007 [cited by applicant]
US 20070269025A1 · Shieh · 2007 [cited by applicant]
US 20090086010A1 · Tiphane · 2009 [cited by applicant]
US 20120257002A1 · Stocker · 2012 [cited by applicant]
US 20130035054A1 · Ashton · 2013 [cited by applicant]
US 20140254437A1 · Koch · 2014 [cited by applicant]
US 20150149290A1 · Ashton · 2015 [cited by applicant]
US 20160119477A1 · Sharpe et al. · 2016 [cited by applicant]
US 20170013129A1 · Rotsztein · 2017 [cited by applicant]
US 20170192735A1 · Faran · 2017 [cited by applicant]
US 20220407961A1 · Willshire · 2022 [cited by examiner]
JP 2008236323A · 2008 [cited by applicant]
JP 2016092620A · 2016 [cited by applicant]
JP 2016530818A · 2016 [cited by applicant]
WO 2016085258A1 · 2016 [cited by applicant]
WO 2016189350A1 · 2016 [cited by applicant]
WO 2017079214A1 · 2017 [cited by applicant]
First Office Action from Japanese Patent Application No. 2020-531725 dated Jan. 10, 2023, 2 pages. [cited by applicant]
C. Franky, “Skype For Business Server—Where is Conversation History Stored”, Sep. 9, 2016, XP055913850, Retrieved from the Internet: URL:https://answers.microsoft.com/en-us/skype/forum/all/skype-for-business-server-wher… [cited by applicant]
Extended European Search Report dated Jun. 21, 2021 from European Application No. 18895105.7, 10 pages. [cited by applicant]
Final Office Action dated Oct. 1, 2020 from U.S. Appl. No. 16/730,882, 9 pages. [cited by applicant]
First Examination Report dated Apr. 13, 2022 from Indian Application No. 202027016266, 5 pages. [cited by applicant]
First Examination Report dated Apr. 26, 2022 from European Application No. 18895105.7, 9 pages. [cited by applicant]
First Office Action from Chinese Application No. 201880082706.3 dated May 25, 2021, 22 pages. [cited by applicant]
International Search Report and Written Opinion from International Application No. PCT/2020/065705, 6 pages. [cited by applicant]
International Search Report and Written Opinion from International Application No. PCT/US2018/061450 mailed Feb. 7, 2019, 11 pages. [cited by applicant]
Nonfinal Office Action dated Aug. 5, 2020 from U.S. Appl. No. 16/730,882. [cited by applicant]
Nonfinal Office Action dated Mar. 19, 2020 from U.S. Appl. No. 16/730,882. [cited by applicant]
Non-Final Office Action dated May 26, 2022 from U.S. Appl. No. 17/340,600, 42 pages. [cited by applicant]
Nonfinal Office Action dated Oct. 6, 2020 from U.S. Appl. No. 15/931,447, 21 pages. [cited by applicant]
Nonfinal Office Action dated Sep. 18, 2019 from U.S. Appl. No. 16/176,113, 27 pages. [cited by applicant]
Notice of Allowance dated Feb. 4, 2021 from U.S. Appl. No. 15/931,447, 20 pages. [cited by applicant]
Notice of Allowance dated Jan. 11, 2022 from Chinese Patent Application No. 201880082706.3, 2 pages. [cited by applicant]
Notice of Allowance dated Mar. 20, 2020 from U.S. Appl. No. 16/176,113, 12 pages. [cited by applicant]
Notice of Allowance dated Oct. 20, 2020 from U.S. Appl. No. 16/730,882, 16 pages. [cited by applicant]
Spasovski et al., “Proof of Stake Blockchain: Performance and Scalability for Groupware Communications”, Proceedings of the 9th International Conference on Management of Digital Ecosystems, Nov. 7, 2017, pp. 251-258, re… [cited by applicant]
Second examination report from European Application No. 18895105.7 dated Mar. 15, 2023, 11 pages. [cited by applicant]
Communication under Rule 71(3) dated Jun. 6, 2024 from European Application No. 18895105.7, 8 pages. [cited by applicant]
Cited By (1)
US 12,381,979