IP Library › Granted Patent US 12,438,973
Granted Patent B2
US 12,438,973 · App. 18/896,366 · Granted Oct 7, 2025

Voice application network platform

Inventors: Vishal Dhawan (Centreville, VA); Timothy M Price (Rockville, MD)
Assignee: Xtone, Inc.
H04M1/2478H04M1/2477H04M3/42221H04M3/4936H04M1/2535H04M1/72445H04M3/493H04M2250/74
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,438,973
App. No.
18/896,366
Granted
Oct 7, 2025
Kind
B2
Abstract

A distributed voice applications system includes a voice application rendering agent and at least one voice applications agent that is configured to provide voice applications to an individual user. A management system may control and direct the voice applications rendering agent to create voice applications that are personalized for individual users based on user characteristics, information about the environment in which the voice applications will be performed, prior user interactions and other information. The voice applications agent and components of customized voice applications may be resident on a local user device which includes a voice browser and speech recognition capabilities. The local device, voice applications rendering agent and management system may be interconnected via a communications network.

Claims (38)

1. A method performed by one or more servers of a voice services provider (VSP) to enable a distributed voice application execution system (DVAES)-enabled local device to perform a voice application, comprising:

receiving, from a DVAES-enabled local device, one or more messages that include information regarding an event, setting, state and/or variable value associated with at least one component of the DVAES-enabled local device;

generating one or more voice application (VA) components based on at least some of the information that is included in the one or more received messages; and

sending the one or more VA components to the DVAES-enabled local device to enable the DVAES-enabled device to perform the voice application.

2. The method of claim 1 , wherein the one or more messages are received from a voice applications agent (VAA) software client that is running on the DVAES-enabled local device.

3. The method of claim 1 , wherein the one or more messages received from the DVAES-enabled local device include a credential associated with the DVAES-enabled local device, wherein the method further comprises determining whether the DVAES-enabled local device is authorized to communicate with the VSP based on the credential, and wherein the generating and sending steps are only performed if the DVAES-enabled local device is determined to be authorized to communicate with the VSP.

4. The method of claim 1 , wherein the one or more messages include information regarding an event, setting, state and/or variable value associated with a voice applications agent (VAA) software client running on the DVAES-enabled local device.

5. The method of claim 1 , wherein the one or more messages include information regarding an event, setting, state and/or variable value associated with at least one runtime environment (RTE) that is running on the DVAES-enabled local device.

6. The method of claim 1 , wherein the one or more messages include information regarding an event, setting, state and/or variable value associated with at least one process or thread that is running on the DVAES-enabled local device.

7. The method of claim 1 , wherein the one or more messages include information regarding an event, setting, state and/or variable value associated with a VA component that was previously sent by the one or more servers to the DVAES-enabled device.

8. The method of claim 1 , wherein the one or more messages include audio content that includes a spoken command, wherein the method further comprises analyzing the audio content to determine a meaning of the spoken command, and wherein the generating step comprises generating one or more voice application (VA) components that are responsive to the spoken command.

9. The method of claim 8 , wherein the generating step comprises generating one or more voice application (VA) components that, when performed by a voice applications agent (VAA) software client that is running on the DVAES-enabled local device, will result in the DVAES-enabled local device responding to the spoken command.

10. The method of claim 8 , wherein the generating step comprises generating one or more voice application (VA) components that, when performed by a voice applications agent (VAA) software client that is running on the DVAES-enabled local device, will result in the DVAES-enabled local device providing information in response to the spoken command.

11. The method of claim 8 , wherein the generating step comprises generating one or more voice application (VA) components that, when performed by a voice applications agent (VAA) software client that is running on the DVAES-enabled local device, result in the DVAES-enabled local device playing music in response to the spoken command.

12. The method of claim 8 , wherein the generating step further comprises generating one or more voice application (VA) components that, when performed by a voice applications agent (VAA) software client that is running on the DVAES-enabled local device, result in the DVAES-enabled local device changing a setting of the DVAES-enabled device in response to the spoken command.

13. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured to be run by a runtime environment, a process and/or a thread running on the DVAES-enabled local device.

14. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured to provide instructions to a runtime environment, process and/or a thread running on the DVAES-enabled local device.

15. The method of claim 1 , wherein the generating step comprises generating one or more VA components that include audio data that can be used to play audio to a user of the DVAES-enabled local device.

16. The method of claim 1 , wherein the generating step comprises generating one or more VA components that include information indicating where audio data is stored, wherein the audio data at the stored location can be retrieved and used by the DVAES-enabled local device to play audio to a user of the DVAES-enabled local device.

17. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured based on a capability or characteristic of the DVAES-enabled local device.

18. The method of claim 1 , wherein the method further comprises determining an identity of an account associated with the DVAES enabled device based on information contained in the one or more messages received from the DVAES-enabled local device, and wherein the generating step comprises generating one or more VA components that are configured based on one or more characteristics of an individual associated with the determined account.

19. The method of claim 1 , wherein the method further comprises determining an identity of an account associated with the DVAES enabled device based on information contained in the one or more messages received from the DVAES-enabled local device, and wherein the generating step comprises generating one or more VA components that are configured based on one or more characteristics of an electronic device associated with the determined account.

20. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured based on an identity of a user of the DVAES-enabled local device.

21. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured based on one or more characteristics of a first user of the DVAES-enabled local device and also generating one or more VA components that are configured based on one or more characteristics of a second user of the DVAES-enabled local device, and wherein the sending step comprises sending both the one or more VA components configured based on one or more characteristics of the first user and the one or more VA components configured based on one or more characteristics of the second user to the DVAES-enabled local device.

22. The method of claim 1 , wherein the generating step comprises generating one or more VA components that are configured based on a capability or characteristic of a data network connection of the DVAES-enabled local device.

23. The method of claim 1 , wherein the generating step comprises generating one or more VA components for a first voice application and also generating one or more VA components for a second voice application, and wherein the sending step comprises sending the one or more VA components for the first voice application and the one or more VA components for the second voice application to the DVAES-enabled local device.

24. The method of claim 23 , wherein the one or more VA components for the first voice application and the one or more VA components for the second voice application are sent to the DVAES-enabled local device in a manner that enables the DVAES-enabled local device to perform the first and second voice applications concurrently.

25. The method of claim 1 , further comprising:

generating one or more control messages that include information that will cause the DVAES-enabled local device to adjust a setting, state or variable value of a component of the DVAES-enabled device; and

sending the one or more control messages to the DVAES-enabled local device.

26. The method of claim 25 , wherein the received one or more messages include information about a first setting, state and/or variable value of a first component of the DVAES-enabled local device, and wherein the generated one or more control messages include information that will cause the DVAES-enabled local device to adjust the first setting, state or variable value of the first component of the DVAES-enabled device.

27. The method of claim 1 , wherein the one or more messages include a credential that identifies the DVAES-enabled device or a voice applications agent (VAA) software application running on the DVAES-enabled device, wherein the method further comprises:

verifying that the DVAES-enabled device is authorized to communicate with the VSP based on the credential; and

registering the DVAES-enabled device or a voice applications agent (VAA) software application running on the DVAES-enabled device with the VSP.

28. The method of claim 27 , wherein the generating step comprises generating one or more voice application (VA) components that include information that will facilitate future communications between the DVAES-enabled device and the VSP.

29. The method of claim 27 , wherein the registering step comprises associating the DVAES-enabled device or a VAA software application running on the DVAES-enabled device with a pre-existing account with the VSP.

30. The method of claim 29 , wherein the generating step comprises generating one or more voice application (VA) components that are configured based on information associated with the pre-existing account with the VSP.

31. The method of claim 29 , wherein the generating step comprises generating one or more voice application (VA) components that are configured based on characteristics of an individual associated with the pre-existing account with the VSP.

Assignments (2)
CHANGE OF NAME Recorded Sep 26, 2024
From: XTONE NETWORKS, INC.
To: XTONE, INC.
Reel/Frame 069050/0409 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: DHAWAN, VISHAL; PRICE, TIMOTHY M
To: XTONE NETWORKS, INC.
Reel/Frame 068703/0527 →
Continuity (9)
Continuation 18412940 · Jan 15, 2024
Continuation 18115562 · Feb 28, 2023
Continuation 17965616 · Oct 13, 2022
Continuation 17410683 · Aug 24, 2021
Continuation 12717893 · Mar 4, 2010
Continuation In Part 11514116 · Sep 1, 2006
Provisional Application 61157337 · Mar 4, 2009
Provisional Application 60712808 · Sep 1, 2005
Related Publication 20250016260A1 · Jan 9, 2025
References Cited (204)
US 5073923A · Offers et al. · 1991 [cited by applicant]
US 5323444A · Ertz et al. · 1994 [cited by applicant]
US 5802526A · Fawcett · 1998 [cited by examiner]
US 5918014A · Robinson · 1999 [cited by applicant]
US 6035018A · Kaufman · 2000 [cited by applicant]
US 6072482A · Moon et al. · 2000 [cited by applicant]
US 6088428A · Trandal et al. · 2000 [cited by applicant]
US 6212408B1 · Son et al. · 2001 [cited by applicant]
US 6285984B1 · Speicher · 2001 [cited by applicant]
US 6334103B1 · Surace et al. · 2001 [cited by applicant]
US 6408272B1 · White et al. · 2002 [cited by applicant]
US 6636504B1 · Albers et al. · 2003 [cited by applicant]
US 6636831B1 · Profit, Jr. et al. · 2003 [cited by applicant]
US 6658388B1 · Kleindienst et al. · 2003 [cited by applicant]
US 6738743B2 · Sharma et al. · 2004 [cited by applicant]
US 6744881B1 · Price · 2004 [cited by applicant]
US 6757781B2 · Williams et al. · 2004 [cited by applicant]
US 6829334B1 · Zirngibl et al. · 2004 [cited by applicant]
US 6882974B2 · James et al. · 2005 [cited by applicant]
US 6901431B1 · Dodrill et al. · 2005 [cited by applicant]
US 6977992B2 · Zirngibl et al. · 2005 [cited by applicant]
US 6988070B2 · Kawasaki et al. · 2006 [cited by applicant]
US 7016847B1 · Tessel et al. · 2006 [cited by applicant]
US 7020609B2 · Thrift et al. · 2006 [cited by applicant]
US 7024363B1 · Comerford et al. · 2006 [cited by applicant]
US 7043232B2 · Pelaez et al. · 2006 [cited by applicant]
US 7062709B2 · Cheung · 2006 [cited by applicant]
US 7069221B2 · Crane et al. · 2006 [cited by applicant]
US 7174005B1 · Rodkey et al. · 2007 [cited by applicant]
US 7174297B2 · Guerra et al. · 2007 [cited by applicant]
US 7263712B2 · Spencer · 2007 [cited by examiner]
US 7334050B2 · Zondervan et al. · 2008 [cited by applicant]
US 7376222B2 · Lin · 2008 [cited by applicant]
US 7415442B1 · Battaglini · 2008 [cited by applicant]
US 7466810B1 · Quon · 2008 [cited by applicant]
US 7483833B2 · Peters · 2009 [cited by applicant]
US 7552055B2 · Lecoeuche · 2009 [cited by applicant]
US 7599838B2 · Gong et al. · 2009 [cited by applicant]
US 7657005B2 · Chang · 2010 [cited by applicant]
US 7689426B2 · Matula · 2010 [cited by applicant]
US 7702084B2 · Wolmuth · 2010 [cited by applicant]
US 7801283B2 · Harwood et al. · 2010 [cited by applicant]
US 7801306B2 · Reitmeier et al. · 2010 [cited by applicant]
US 7809376B2 · Letourneau et al. · 2010 [cited by applicant]
US 7844215B2 · Vance · 2010 [cited by examiner]
US 7885817B2 · Paek et al. · 2011 [cited by applicant]
US 7889853B2 · Sutcliffe · 2011 [cited by applicant]
US 7948892B2 · Morinaga et al. · 2011 [cited by applicant]
US 8064588B2 · Brahm et al. · 2011 [cited by applicant]
US 8085909B2 · Tischer · 2011 [cited by examiner]
US 8140340B2 · Bhogal et al. · 2012 [cited by applicant]
US 8223931B1 · Lavian et al. · 2012 [cited by applicant]
US 8483853B1 · Lambourne · 2013 [cited by examiner]
US 20020001370A1 · Walker et al. · 2002 [cited by applicant]
US 20020022453A1 · Balog et al. · 2002 [cited by applicant]
US 20020059073A1 · Zondervan et al. · 2002 [cited by applicant]
US 20020065944A1 · Hickey et al. · 2002 [cited by applicant]
US 20020073034A1 · Wagner et al. · 2002 [cited by applicant]
US 20020108125A1 · Joao · 2002 [cited by examiner]
US 20020161646A1 · Gailey et al. · 2002 [cited by applicant]
US 20020169604A1 · Damiba et al. · 2002 [cited by applicant]
US 20020169615A1 · Kruger et al. · 2002 [cited by applicant]
US 20020188451A1 · Guerra et al. · 2002 [cited by applicant]
US 20030007609A1 · Yuen et al. · 2003 [cited by applicant]
US 20030068999A1 · Casali et al. · 2003 [cited by applicant]
US 20030114202A1 · Suh et al. · 2003 [cited by applicant]
US 20030119487A1 · Silvester · 2003 [cited by applicant]
US 20030125944A1 · Wohlsen et al. · 2003 [cited by applicant]
US 20030144005A1 · Videtich · 2003 [cited by applicant]
US 20030191816A1 · Landress et al. · 2003 [cited by applicant]
US 20030233238A1 · Creamer et al. · 2003 [cited by applicant]
US 20040006471A1 · Chiu · 2004 [cited by applicant]
US 20040006476A1 · Chiu · 2004 [cited by applicant]
US 20040010412A1 · Chiu · 2004 [cited by applicant]
US 20040068364A1 · Zhao et al. · 2004 [cited by applicant]
US 20040093218A1 · Bezar · 2004 [cited by examiner]
US 20040151285A1 · Sychta · 2004 [cited by applicant]
US 20040163073A1 · Krzyzanowski et al. · 2004 [cited by applicant]
US 20040174983A1 · Olschwang et al. · 2004 [cited by applicant]
US 20040210637A1 · Loveland · 2004 [cited by applicant]
US 20040230689A1 · Loveland · 2004 [cited by applicant]
US 20050091057A1 · Phillips et al. · 2005 [cited by applicant]
US 20050135338A1 · Chiu et al. · 2005 [cited by applicant]
US 20050141679A1 · Zirngibl et al. · 2005 [cited by applicant]
US 20050163136A1 · Chiu et al. · 2005 [cited by applicant]
US 20050234720A1 · Paillet et al. · 2005 [cited by applicant]
US 20050234727A1 · Chiu · 2005 [cited by applicant]
US 20050283367A1 · Ativanichayaphong et al. · 2005 [cited by applicant]
US 20060047511A1 · Hussain · 2006 [cited by applicant]
US 20060069701A1 · O'Rourke, III · 2006 [cited by applicant]
US 20060122840A1 · Anderson et al. · 2006 [cited by applicant]
US 20060159246A1 · Abrahamson et al. · 2006 [cited by applicant]
US 20060182247A1 · Batni et al. · 2006 [cited by applicant]
US 20060206340A1 · Silvera et al. · 2006 [cited by applicant]
US 20060293897A1 · White et al. · 2006 [cited by applicant]
US 20070078706A1 · Datta et al. · 2007 [cited by applicant]
US 20070135101A1 · Ramati et al. · 2007 [cited by applicant]
US 20070143113A1 · Nanavati et al. · 2007 [cited by applicant]
US 20070156747A1 · Samuelson · 2007 [cited by examiner]
US 20070206758A1 · Barak · 2007 [cited by applicant]
US 20070263838A1 · Wiseman et al. · 2007 [cited by applicant]
US 20070283268A1 · Berger et al. · 2007 [cited by applicant]
US 20080104630A1 · Bruce et al. · 2008 [cited by applicant]
US 20080165937A1 · Moore · 2008 [cited by applicant]
US 20090007171A1 · Casey et al. · 2009 [cited by applicant]
US 20090022283A1 · Pollitt · 2009 [cited by applicant]
US 20100036717A1 · Trest · 2010 [cited by applicant]
US 20100054432A1 · Brahm et al. · 2010 [cited by applicant]
US 20100086107A1 · Tzruya · 2010 [cited by applicant]
US 20130045778A1 · Sundaresan et al. · 2013 [cited by applicant]
GB 2362540 · 2001 [cited by applicant]
WO 9620448 · 1996 [cited by applicant]
WO WO0145086 · 2001 [cited by applicant]
U.S. Appl. No. 11/514,116, filed Sep. 1, 2006. [cited by applicant]
Office Action for U.S. Appl. No. 11/514,116 issued Feb. 26, 2010. [cited by applicant]
U.S. Appl. No. 12/717,826, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,826 issued Nov. 28, 2011. [cited by applicant]
U.S. Appl. No. 12/717,839, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,839 issued Dec. 29, 2011. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,839 issued Sep. 21, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,839 issued May 2, 2014. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,839 issued Mar. 17, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,839 issued Nov. 20, 2015. [cited by applicant]
U.S. Appl. No. 12/717,854, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,854 issued Dec. 29, 2011. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,854 issued Oct. 16, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,854 issued Feb. 3, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,854 issued Jan. 4, 2016. [cited by applicant]
U.S. Appl. No. 12/717,858, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,858 issued Nov. 25, 2011. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,858 issued Sep. 27, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,858 issued Mar. 27, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,858 issued Apr. 22, 2016. [cited by applicant]
U.S. Appl. No. 12/717,865, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,865 issued Mar. 13, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,865 issued Aug. 15, 2013. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,865 issued Apr. 10, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,865 issued May 9, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,865 issued Jun. 21, 2021. [cited by applicant]
U.S. Appl. No. 12/717,875, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,875 issued Dec. 29, 2011. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,875 issued Nov. 26, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,875 issued May 5, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,875 issued Jan. 4, 2016. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,875 issued Jun. 27, 2017. [cited by applicant]
U.S. Appl. No. 12/717,881, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,881 issued Nov. 22, 2011. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,881 issued Aug. 15, 2013. [cited by applicant]
U.S. Appl. No. 12/717,888, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,888 issued Jan. 25, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,888 issued Sep. 27, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,888 issued Apr. 1, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,888 issued Jun. 3, 2016. [cited by applicant]
U.S. Appl. No. 12/717,893, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Mar. 1, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Sep. 27, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Oct. 15, 2013. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Aug. 1, 2014. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Apr. 9, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,893 issued Apr. 26, 2021. [cited by applicant]
U.S. Appl. No. 12/717,897, filed Mar. 4, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,897 issued Feb. 3, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,897 issued Sep. 21, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,897 issued Jul. 19, 2013. [cited by applicant]
Office Action for U.S. Appl. No. 12/717,897 issued Dec. 9, 2014. [cited by applicant]
U.S. Appl. No. 12/943,510, filed Jul. 10, 2010. [cited by applicant]
Office Action for U.S. Appl. No. 12/943,510 issued Apr. 10, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 12/943,510 issued Nov. 21, 2012. [cited by applicant]
U.S. Appl. No. 13/355,840, filed Jan. 23, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 13/355,840 issued Apr. 5, 2012. [cited by applicant]
U.S. Appl. No. 13/595,482, filed Aug. 27, 2012. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Sep. 9, 2014. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Jul. 8, 2015. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Mar. 10, 2016. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Jan. 5, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Oct. 10, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 13/595,482 issued Sep. 20, 2019. [cited by applicant]
U.S. Appl. No. 15/216,752, filed Jul. 22, 2016. [cited by applicant]
Office Action for U.S. Appl. No. 15/216,752 issued Mar. 24, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 15/216,752 issued Jan. 12, 2018. [cited by applicant]
Office Action for U.S. Appl. No. 15/216,752 issued Aug. 29, 2018. [cited by applicant]
U.S. Appl. No. 15/246,770, filed Aug. 25, 2016. [cited by applicant]
Office Action for U.S. Appl. No. 15/246,770 issued Jan. 26, 2018. [cited by applicant]
U.S. Appl. No. 15/784,423, filed Oct. 16, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 15/784,423 issued Nov. 16, 2018. [cited by applicant]
Office Action for U.S. Appl. No. 15/784,423 issued Aug. 22, 2019. [cited by applicant]
U.S. Appl. No. 15/982,701, filed May 17, 2018. [cited by applicant]
Office Action for U.S. Appl. No. 15/982,701 issued Mar. 19, 2019. [cited by applicant]
U.S. Appl. No. 16/773,444, filed Jan. 27, 2020. [cited by applicant]
Office Action for U.S. Appl. No. 16/773,444 issued May 29, 2020. [cited by applicant]
Office Action for U.S. Appl. No. 16/773,444 issued Mar. 3, 2021. [cited by applicant]
Office Action for U.S. Appl. No. 16/773,444 issued Sep. 15, 2021. [cited by applicant]
U.S. Appl. No. 16/799,033, filed Feb. 24, 2020. [cited by applicant]
Office Action for U.S. Appl. No. 16/799,033 issued Mar. 2, 2021. [cited by applicant]
Office Action for U.S. Appl. No. 16/799,033 issued Sep. 15, 2021. [cited by applicant]
U.S. Appl. No. 17/410,683, filed Aug. 24, 2021. [cited by applicant]
Office Action for U.S. Appl. No. 17/410,583 issued Aug. 17, 2022. [cited by applicant]
U.S. Appl. No. 17/582,479 filed Jan. 24, 2022. [cited by applicant]
Office Action for U.S. Appl. No. 17/582,479 issued Sep. 27, 2022. [cited by applicant]
U.S. Appl. No. 17/582,555, filed Jan. 24, 2022. [cited by applicant]
Office Action for U.S. Appl. No. 17/582,555 issued Sep. 26, 2022. [cited by applicant]
Supplementary European Search Report issued in 06802900.8 on Apr. 13, 2010. [cited by applicant]
U.S. Appl. No. 18/412,940, filed Jan. 15, 2024. [cited by applicant]
Office Action for U.S. Appl. No. 18/412,940 issued Aug. 13, 2024. [cited by applicant]