IP Library Granted Patent US 12,574,416
Granted Patent B2
US 12,574,416 · App. 17/989,093 · Granted Mar 10, 2026

Monitoring overlay networks

Inventors: Nicholas Anthony Marrone (Seattle, WA); Bryan David Skene (Seattle, WA); Ludwin Fuchs (Seattle, WA); Jeffrey Scott Hussey (Seattle, WA)
Assignee: TYCO FIRE & SECURITY GMBH
H04L63/20H04L12/66H04L41/06H04L41/0894H04L43/08H04L43/0876H04L45/64H04L65/102H04L67/1001H04L43/16
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,574,416
App. No.
17/989,093
Granted
Mar 10, 2026
Kind
B2
Abstract

Embodiments are directed to managing communication over one or more networks. A monitoring engine may be instantiated to perform actions including receiving network traffic from a physical network that may be associated with network addresses of the physical network. The monitoring engine may analyze the network traffic to associate activity with gateway identifiers (GIDs) associated with gateway computers in an overlay network such that the GIDs are separate from the network addresses. The monitoring engine may be arranged to monitor the network traffic based on monitoring rules. The monitoring engine may provide metrics associated with the gateway computers based on the monitoring of the network traffic. The monitoring engine may compare the metrics to event rules. The monitoring engine may generate events based on affirmative results of the comparison. The events may be mapped to actions based on characteristics of the events and executed.

Claims (49)

1 . A method for managing communication over one or more networks using one or more network computers, wherein execution of configured instructions by the one or more network computers causes the one or more network computers to perform the method comprising:

monitoring, according to one or more monitoring rules, one or more metrics of network traffic associated with one or more network addresses of one or more private networks, the network traffic further associated with one or more gateway identifiers (GIDs) for one or more gateway computers which communicably couple the one or more private networks to an overlay network, the overlay network providing an abstraction layer which obscures activity associated with the network traffic of the one or more private networks from members of the overlay network;

generating one or more events, based on the one or more metrics of the network traffic of the one or more gateway computers compared to one or more event rules, the one or more event rules including corresponding one or more actions based on the one or more events, the one or more events being generated upon satisfaction of at least one event rule by the one or more metrics; and

executing the one or more actions based on the one or more events, wherein the one or more actions comprise modifying an operational parameter of at least one of the overlay network, a gateway computer, or a network computer in response to the event.

2 . The method of claim 1 , further comprising:

locally interpreting the one or more events to determine the one or more actions, wherein the interpretation is performed local to the one or more gateway computers.

3 . The method of claim 2 , wherein the local interpretation further comprises: performing the interpretation with a computer that is unassociated with the one or more events and local to the one or more gateway computers.

4 . The method of claim 1 , wherein monitoring the network traffic further comprises: locally monitoring the one or more metrics associated with one or more of a gateway computer or a node computer.

5 . The method of claim 1 , further comprising:

generating one or more policies for the one or more gateway computers, wherein the one or more gateway computers employ the one or more policies to route network traffic to one or more node computers.

6 . The method of claim 1 , further comprising:

employing a management platform to configure and distribute one or more polices to the one or more gateway computers, wherein the one or more policies are configured for routing of network traffic between the one or more gateway computers and one or more node computers.

7 . The method of claim 1 , further comprising:

employing one or more relay computers to establish communication between two or more gateway computers; and

routing network traffic between the two or more gateway computers and one or more node computers based on one or more policies provided by the one or more relay computers to the two or more gateway computers.

8 . A network computer for managing communication over one or more networks, comprising:

memory for storing instructions; and

one or more processors, wherein execution of the instructions is configured to cause actions, comprising:

monitoring, according to one or more monitoring rules, one or more metrics of network traffic associated with one or more network addresses of one or more private networks, the network traffic further associated with one or more gateway identifiers (GIDs) for one or more gateway computers which communicably couple the one or more private networks to an overlay network, the overlay network providing an abstraction layer which obscures activity associated with the network traffic of the one or more private networks from members of the overlay network;

generating one or more events based on the one or more metrics of the network traffic of the one or more gateway computers compared to one or more event rules the one or more event rules including corresponding one or more actions based on the one or more events, the one or more events being generated upon satisfaction of at least one event rule by the one or more metrics; and

executing the one or more actions based on the one or more events, wherein the one or more actions comprise modifying an operational parameter of at least one of the overlay network, a gateway computer, or a network computer in response to the event.

9 . The network computer of claim 8 , further comprising:

locally interpreting the one or more events to determine the one or more actions, wherein the interpretation is performed local to the one or more gateway computers.

10 . The network computer of claim 8 , wherein the local interpretation further comprises:

performing the interpretation with a computer that is unassociated with the one or more events and local to the one or more gateway computers.

11 . The network computer of claim 8 , wherein monitoring the network traffic further comprises:

locally monitoring the one or more metrics associated with one or more of a gateway computer or a node computer.

12 . The network computer of claim 8 , further comprising:

generating one or more policies for the one or more gateway computers, wherein the one or more gateway computers employ the one or more policies to route network traffic to one or more node computers.

13 . The network computer of claim 8 , further comprising:

employing a management platform to configure and distribute one or more polices to the one or more gateway computers, wherein the one or more policies are configured for routing of network traffic between the one or more gateway computers and one or more node computers.

14 . The network computer of claim 8 , further comprising:

employing one or more relay computers to establish communication between two or more gateway computers; and

routing network traffic between the two or more gateway computers and one or more node computers based on one or more policies provided by the one or more relay computers to the two or more gateway computers.

15 . A management platform for managing communication over one or more networks with one or more network computers, wherein execution of code by the one or more network computers is configured to cause actions, comprising:

monitoring, according to one or more monitoring rules, one or more metrics of network traffic associated with one or more network addresses of one or more private networks, the network traffic further associated with one or more gateway identifiers (GIDs) for one or more gateway computers which communicably couple the one or more private networks to an overlay network, the overlay network providing an abstraction layer which obscures activity associated with the network traffic of the one or more private networks from members of the overlay network;

generating one or more events based on the one or more metrics of the network traffic of the one or more gateway computers compared to one or more event rules, the one or more event rules including corresponding one or more actions based on the one or more events, the one or more events being generated upon satisfaction of at least one event rule by the one or more metrics; and

executing one or more actions based on the one or more events, wherein the one or more actions comprise modifying an operational parameter of at least one of the overlay network, a gateway computer, or a network computer in response to the event.

16 . The management platform of claim 15 , further comprising:

locally interpreting the one or more events to determine the one or more actions, wherein the interpretation is performed local to the one or more gateway computers.

17 . The management platform of claim 15 , wherein the local interpretation further comprises:

performing the interpretation with a computer that is unassociated with the one or more events and local to the one or more gateway computers.

18 . The management platform of claim 15 , further comprises:

locally monitoring the one or more metrics associated with one or more of a gateway computer or a node computer.

19 . The management platform of claim 15 , further comprising:

generating one or more policies for the one or more gateway computers, wherein the one or more gateway computers employ the one or more policies to route network traffic to one or more node computers.

20 . The management platform of claim 15 , further comprising:

employing one or more relay computers to establish communication between two or more gateway computers; and

routing network traffic between the two or more gateway computers and one or more node computers based on one or more policies provided by the one or more relay computers to the two or more gateway computers.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 9, 2024
From: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
To: TYCO FIRE & SECURITY GMBH
Reel/Frame 067056/0552 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 31, 2023
From: TEMPERED NETWORKS, INC.
To: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
Reel/Frame 065406/0415 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2022
From: MARRONE, NICHOLAS ANTHONY; SKENE, BRYAN DAVID; FUCHS, LUDWIN; HUSSEY, JEFFREY SCOTT
To: TEMPERED NETWORKS, INC.
Reel/Frame 061961/0439 →
Continuity (4)
Continuation 16562258 · Sep 5, 2019
Continuation 16221145 · Dec 14, 2018
Continuation 15994760 · May 31, 2018
Related Publication 20230188446A1 · Jun 15, 2023
References Cited (212)
US 5835727A · Wong et al. · 1998 [cited by applicant]
US 6158010A · Moriconi · 2000 [cited by examiner]
US 6981156B1 · Stern et al. · 2005 [cited by applicant]
US 7209956B2 · Mache · 2007 [cited by applicant]
US 7324533B1 · DeLiberato et al. · 2008 [cited by applicant]
US 7373660B1 · Guichard et al. · 2008 [cited by applicant]
US 7395349B1 · Szabo et al. · 2008 [cited by applicant]
US 7796593B1 · Ghosh et al. · 2010 [cited by applicant]
US 7881199B2 · Krstulich · 2011 [cited by applicant]
US 7996894B1 · Chen et al. · 2011 [cited by applicant]
US 8224971B1 · Miller et al. · 2012 [cited by applicant]
US 8429400B2 · Khalid et al. · 2013 [cited by applicant]
US 8489701B2 · Manion et al. · 2013 [cited by applicant]
US 8607301B2 · Carrasco · 2013 [cited by applicant]
US 8630183B2 · Miyata · 2014 [cited by applicant]
US 8756344B2 · Waldrop · 2014 [cited by examiner]
US 8832211B1 · Lebedev et al. · 2014 [cited by applicant]
US 8886827B2 · Goel et al. · 2014 [cited by applicant]
US 8959513B1 · Swaminathan · 2015 [cited by examiner]
US 9264522B1 · Reeves et al. · 2016 [cited by applicant]
US 9344403B2 · Mattes · 2016 [cited by examiner]
US 9729580B2 · Mattes · 2017 [cited by examiner]
US 9774586B1 · Roche et al. · 2017 [cited by applicant]
US 10038725B2 · Mattes · 2018 [cited by examiner]
US 10158545B1 · Marrone · 2018 [cited by examiner]
US 10178133B2 · Mattes · 2019 [cited by examiner]
US 10911418B1 · Fuchs et al. · 2021 [cited by applicant]
US 10999154B1 · Ahrenholz et al. · 2021 [cited by applicant]
US 11310341B2 · Shribman · 2022 [cited by examiner]
US 11509559B2 · Marrone · 2022 [cited by examiner]
US 11582129B2 · Marrone · 2023 [cited by examiner]
US 20020026532A1 · Maeda et al. · 2002 [cited by applicant]
US 20020073182A1 · Zakurdaev et al. · 2002 [cited by applicant]
US 20020143855A1 · Traversat et al. · 2002 [cited by applicant]
US 20030061479A1 · Kimura · 2003 [cited by applicant]
US 20030081620A1 · Danner et al. · 2003 [cited by applicant]
US 20030123436A1 · Joseph et al. · 2003 [cited by applicant]
US 20040024905A1 · Liao et al. · 2004 [cited by applicant]
US 20040143628A1 · Bradford et al. · 2004 [cited by applicant]
US 20040268121A1 · Shelest et al. · 2004 [cited by applicant]
US 20050014500A1 · Muhonen et al. · 2005 [cited by applicant]
US 20050052999A1 · Oliver et al. · 2005 [cited by applicant]
US 20050265355A1 · Havala et al. · 2005 [cited by applicant]
US 20060190458A1 · Mishina et al. · 2006 [cited by applicant]
US 20060233166A1 · Bou-Diab et al. · 2006 [cited by applicant]
US 20070019641A1 · Pai et al. · 2007 [cited by applicant]
US 20070081530A1 · Nomura et al. · 2007 [cited by applicant]
US 20070226781A1 · Chen et al. · 2007 [cited by applicant]
US 20070230352A1 · Kokku et al. · 2007 [cited by applicant]
US 20070258440A1 · Watanabe · 2007 [cited by applicant]
US 20080072282A1 · Willis et al. · 2008 [cited by applicant]
US 20080082823A1 · Starrett et al. · 2008 [cited by applicant]
US 20080151916A1 · Jetcheva et al. · 2008 [cited by applicant]
US 20080232360A1 · Mihaly et al. · 2008 [cited by applicant]
US 20080288614A1 · Gil et al. · 2008 [cited by applicant]
US 20080307519A1 · Curcio et al. · 2008 [cited by applicant]
US 20090010168A1 · Yurchenko et al. · 2009 [cited by applicant]
US 20090034738A1 · Starrett · 2009 [cited by applicant]
US 20090059906A1 · Cullen · 2009 [cited by applicant]
US 20090129374A1 · Yurchenko et al. · 2009 [cited by applicant]
US 20090210518A1 · Verma et al. · 2009 [cited by applicant]
US 20090210541A1 · Chandolu et al. · 2009 [cited by applicant]
US 20090310518A1 · Jayaram et al. · 2009 [cited by applicant]
US 20100014533A1 · Hirano et al. · 2010 [cited by applicant]
US 20100024026A1 · Ylonen et al. · 2010 [cited by applicant]
US 20100027442A1 · Chockler et al. · 2010 [cited by applicant]
US 20100042747A1 · Hascalovici · 2010 [cited by examiner]
US 20100214959A1 · Kuehnel et al. · 2010 [cited by applicant]
US 20100218235A1 · Ganot · 2010 [cited by applicant]
US 20100254395A1 · Smith et al. · 2010 [cited by applicant]
US 20110016509A1 · Huang et al. · 2011 [cited by applicant]
US 20110035466A1 · Panigrahi · 2011 [cited by applicant]
US 20110090892A1 · Cooke · 2011 [cited by applicant]
US 20110103393A1 · Meier et al. · 2011 [cited by applicant]
US 20110141881A1 · Joshi et al. · 2011 [cited by applicant]
US 20120110203A1 · Ozawa · 2012 [cited by applicant]
US 20120163196A1 · Jansen et al. · 2012 [cited by applicant]
US 20120304243A1 · Li et al. · 2012 [cited by applicant]
US 20130010621A1 · Yoshiuchi et al. · 2013 [cited by applicant]
US 20130018993A1 · Hui et al. · 2013 [cited by applicant]
US 20130046414A1 · Ree · 2013 [cited by applicant]
US 20130083725A1 · Mallya et al. · 2013 [cited by applicant]
US 20130198830A1 · Nemoto et al. · 2013 [cited by applicant]
US 20130254264A1 · Hankinson et al. · 2013 [cited by applicant]
US 20130283364A1 · Chang et al. · 2013 [cited by applicant]
US 20140026207A1 · Wang et al. · 2014 [cited by applicant]
US 20140133354A1 · Scharf et al. · 2014 [cited by applicant]
US 20140150070A1 · Peterson · 2014 [cited by examiner]
US 20140223507A1 · Xu · 2014 [cited by applicant]
US 20140282817A1 · Singer et al. · 2014 [cited by applicant]
US 20140282850A1 · Mattes · 2014 [cited by examiner]
US 20140307744A1 · Dunbar et al. · 2014 [cited by applicant]
US 20140348131A1 · Duan et al. · 2014 [cited by applicant]
US 20150024677A1 · Gopal et al. · 2015 [cited by applicant]
US 20150046997A1 · Gupta · 2015 [cited by examiner]
US 20150057766A1 · Ejiri et al. · 2015 [cited by applicant]
US 20150067033A1 · Martinsen et al. · 2015 [cited by applicant]
US 20150124823A1 · Pani et al. · 2015 [cited by applicant]
US 20150135259A1 · Ilyadis · 2015 [cited by examiner]
US 20150281074A1 · Kubota · 2015 [cited by applicant]
US 20150365316A1 · Liao et al. · 2015 [cited by applicant]
US 20150372828A1 · Hao et al. · 2015 [cited by applicant]
US 20160028624A1 · Song et al. · 2016 [cited by applicant]
US 20160036861A1 · Mattes · 2016 [cited by examiner]
US 20160149804A1 · Mirza · 2016 [cited by applicant]
US 20160182378A1 · Basavaraja et al. · 2016 [cited by applicant]
US 20160188527A1 · Cherian et al. · 2016 [cited by applicant]
US 20160255542A1 · Hughes et al. · 2016 [cited by applicant]
US 20160261641A1 · Mattes · 2016 [cited by examiner]
US 20170019430A1 · Cohn · 2017 [cited by applicant]
US 20170126623A1 · Lindteigen · 2017 [cited by examiner]
US 20170134261A1 · Seo · 2017 [cited by examiner]
US 20170142208A1 · Hammer · 2017 [cited by examiner]
US 20170222973A1 · Bangma · 2017 [cited by examiner]
US 20170238215A1 · Jin · 2017 [cited by applicant]
US 20170288948A1 · Singh · 2017 [cited by examiner]
US 20170373936A1 · Hooda et al. · 2017 [cited by applicant]
US 20180083968A1 · Xu et al. · 2018 [cited by applicant]
US 20180084060A1 · Xie et al. · 2018 [cited by applicant]
US 20180124183A1 · Kozat · 2018 [cited by examiner]
US 20180183834A1 · Mattes · 2018 [cited by examiner]
US 20180234459A1 · Kung et al. · 2018 [cited by applicant]
US 20180262466A1 · Atad · 2018 [cited by examiner]
US 20190068592A1 · Mattela et al. · 2019 [cited by applicant]
US 20190132152A1 · Wang · 2019 [cited by examiner]
US 20190149401A1 · Ramachandran et al. · 2019 [cited by applicant]
US 20190158397A1 · Liu · 2019 [cited by applicant]
US 20190313318A1 · Pawar · 2019 [cited by examiner]
US 20190372876A1 · Marrone · 2019 [cited by examiner]
US 20190394107A1 · Marrone · 2019 [cited by examiner]
US 20200067341A1 · Glover et al. · 2020 [cited by applicant]
US 20200107226A1 · Raleigh · 2020 [cited by examiner]
US 20200177311A1 · Ho · 2020 [cited by examiner]
US 20200177503A1 · Hooda et al. · 2020 [cited by applicant]
US 20200336562A1 · Luft · 2020 [cited by examiner]
US 20210084048A1 · Kannan et al. · 2021 [cited by applicant]
US 20210111998A1 · Saavedra · 2021 [cited by examiner]
US 20230188446A1 · Marrone · 2023 [cited by examiner]
WO 2007038872A1 · 2007 [cited by applicant]
WO 2008039506A2 · 2008 [cited by applicant]
WO 2011159842A2 · 2011 [cited by applicant]
WO 2019246331A1 · 2019 [cited by applicant]
Office Communication for U.S. Appl. No. 17/246,520 mailed Jun. 23, 2023, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 17/378,535 mailed Jul. 6, 2023, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 17/164,488 mailed Mar. 27, 2023, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 17/246,520 mailed Mar. 31, 2023, pp. 1-10. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/US2014/023632 mailed Jun. 23, 2014, pp. 1-15. [cited by applicant]
Asguard Networks, Inc., “SimpleConnectTM Product Information,” Retrieved on Nov. 9, 2012, from http://www.asguardnetworks.com/product/, p. 1. [cited by applicant]
Asguard Networks, Inc., “Welcome to Asguard Networks,” Retrieved on Oct. 23, 2012, from http://www.asguardnetworks.com/, p. 1. [cited by applicant]
Asguard Networks, Inc., “SimpleConnectTM Quick Start Documentation Guide,” Revision 1, Dec. 13, 2012, pp. 1-18. [cited by applicant]
Henderson, T. et al., “HIP-based Virtual Private LAN Service (HIPLS),” Network Working Group, Internet-Draft, The Boeing Company, Nov. 6, 2012, pp. 1-16. [cited by applicant]
Asguard Networks, Inc., “Gray Matter Systems Announces Asguard Networks Partnership at 2012 Gray Matter Systems Training and User Group Meeting,” Aug. 9, 2012, retrieved on Oct. 23, 2012, from http://www.asguardnetworks… [cited by applicant]
Trusted Computing Group, Incorporated, “TCG Trusted Network Connect: IF-MAP Metadata for ICS Security,” Specification Version 1.0, Revision 44, May 8, 2014, pp. 1-64. [cited by applicant]
Office Communication for U.S. Appl. No. 14/204,907 mailed Jul. 10, 2015, pp. 1-20. [cited by applicant]
Aoyagi, S. et al., “ELA: A Fully Distributed VPN System Over Peer-to-Peer Network,” Proceedings of the 2005 Symposium on Applications and the Internet, 2005, IEEE, Computer Society, pp. 1-4. [cited by applicant]
Benyamina, D. et al., “Wireless Mesh Networks Design—A Survey,” IEEE Communications Survey & Tutorials, vol. 14, No. 2, Second Quarter 2012, pp. 299-310. [cited by applicant]
Office Communication for U.S. Appl. No. 14/740,053 mailed Jul. 29, 2015, pp. 1-10. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/US2015/042993 mailed Nov. 11, 2015, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 14/814,283 mailed Nov. 30, 2015, pp. 1-8. [cited by applicant]
Office Communication for U.S. Appl. No. 14/204,907 mailed Dec. 2, 2015, pp. 1-14. [cited by applicant]
Office Communication for U.S. Appl. No. 14/740,053 mailed Jan. 21, 2016, pp. 1-18. [cited by applicant]
Office Communication for U.S. Appl. No. 14/204,907 mailed Feb. 24, 2016, pp. 1-14. [cited by applicant]
Office Communication for U.S. Appl. No. 14/814,283 mailed Jun. 3, 2016, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/083,214 mailed Jul. 7, 2016, pp. 1-11. [cited by applicant]
Trusted Computing Group Architects Guide; ICS Security Using TNC Technology, Oct. 2013, pp. 1-6. [cited by applicant]
Office Communication for U.S. Appl. No. 15/156,254 mailed Aug. 3, 2016, pp. 1-13. [cited by applicant]
Office Communication for U.S. Appl. No. 15/083,214 mailed Oct. 25, 2016, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 15/201,063 mailed Nov. 2, 2016, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 14/814,283 mailed Nov. 21, 2016, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/156,254 mailed Dec. 30, 2016, pp. 1-13. [cited by applicant]
Office Communication for U.S. Appl. No. 15/083,214 mailed Jan. 9, 2017, pp. 1-6. [cited by applicant]
Office Communication for U.S. Appl. No. 15/083,214 mailed Feb. 9, 2017, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/201,063 mailed Apr. 21, 2017, pp. 1-14. [cited by applicant]
Office Communication for U.S. Appl. No. 15/156,254 mailed May 5, 2017, pp. 1-13. [cited by applicant]
Office Communication for U.S. Appl. No. 14/814,283 mailed Jun. 9, 2017, pp. 1-18. [cited by applicant]
Office Communication for U.S. Appl. No. 15/156,254 mailed Oct. 19, 2017, pp. 1-13. [cited by applicant]
Lawton, G., “Machine-to-Machine Technology gears up for growth”, 2004, IEEE Computer Society, pp. 12-15. [cited by applicant]
Office Communication for U.S. Appl. No. 15/670,925 mailed Apr. 5, 2018, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/156,254 mailed May 14, 2018, pp. 1-19. [cited by applicant]
Office Communication for U.S. Appl. No. 15/670,859 mailed Jun. 29, 2018, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/924,148 mailed Jun. 5, 2018, pp. 1-13. [cited by applicant]
Office Communication for U.S. Appl. No. 15/987,762 mailed Sep. 12, 2018, pp. 1-13. [cited by applicant]
Office Communication for U.S. Appl. No. 15/994,760 mailed Oct. 1, 2018, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 15/670,859 mailed Nov. 26, 2018, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 14/814,283 mailed Aug. 23, 2016, pp. 1-8. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Oct. 22, 2019, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 16/267,166 mailed Jan. 14, 2020, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 16/172,621 mailed Mar. 17, 2020, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Apr. 13, 2020, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Apr. 7, 2020, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 16/172,621 mailed Jul. 15, 2020, pp. 1-15. [cited by applicant]
Office Communication for U.S. Appl. No. 16/267,166 mailed Jul. 22, 2020, pp. 1-8. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Sep. 8, 2020, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Sep. 10, 2020, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/913,114 mailed Oct. 1, 2020, pp. 1-21. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Nov. 20, 2020, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Nov. 23, 2020, pp. 1-4. [cited by applicant]
Office Communication for U.S. Appl. No. 17/084,557 mailed Dec. 16, 2020, pp. 1-23. [cited by applicant]
Office Communication for U.S. Appl. No. 17/079,248 mailed Jan. 7, 2021, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 17/079,248 mailed Feb. 17, 2021, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Mar. 19, 2021, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Mar. 24, 2021, pp. 1-9. [cited by applicant]
Office Communication for U.S. Appl. No. 17/084,557 mailed Apr. 1, 2021, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Aug. 20, 2021, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Aug. 24, 2021, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Apr. 22, 2022, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Apr. 26, 2022, pp. 1-11. [cited by applicant]
Office Communication for U.S. Appl. No. 16/562,258 mailed Jul. 20, 2022, pp. 1-9. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Jul. 25, 2022, pp. 1-9. [cited by applicant]
Office Communication for U.S. Appl. No. 17/246,520 mailed Aug. 18, 2022, pp. 1-8. [cited by applicant]
Office Communication for U.S. Appl. No. 17/164,488 mailed Sep. 19, 2022, pp. 1-6. [cited by applicant]
Office Communication for U.S. Appl. No. 16/221,145 mailed Oct. 14, 2022, pp. 1-7. [cited by applicant]