IP Library Granted Patent US 12,267,339
Granted Patent B1
US 12,267,339 · App. 18/309,624 · Granted Apr 1, 2025

Executing modular alerts and associated security actions

Inventors: Banipal Shahbaz (Santa Clara, CA); Sri Atma Oaklander de Licori (San Francisco, CA); John Robert Coates (San Francisco, CA); David Hazekamp (Tinley Park, IL); Devendra Badhani (Santa Clara, CA); Luke Murphey (Wadsworth, IL); Patrick Schulz (San Francisco, CA)
Assignee: Splunk Inc.
H04L63/1416G06F21/53G06F21/554H04L63/145H04L63/1458H04L63/1475G06F16/248G06F16/26G06F2221/2151H04L2463/121H04L2463/141
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,267,339
App. No.
18/309,624
Granted
Apr 1, 2025
Kind
B1
Abstract

Techniques and mechanisms are disclosed for configuring actions to be performed by a network security application in response to the detection of potential security incidents, and for causing a network security application to report on the performance of those actions. For example, users may use such a network security application to configure one or more “modular alerts.” As used herein, a modular alert generally represents a component of a network security application which enables users to specify security modular alert actions to be performed in response to the detection of defined triggering conditions, and which further enables tracking information related to the performance of modular alert actions and reporting on the performance of those actions.

Claims (51)

1. A computer-implemented method comprising:

receiving input defining a custom response action to be executed by a network security application in response to a detection of a potential security incident in an information technology (IT) environment, wherein the input specifies a command to be sent to a device or service related to the network security application in response to the detection of the potential security incident in the IT environment, and wherein the input defining the custom response action further comprises a script file that includes code for performing the custom response action;

generating a package containing executable logic for the custom response action;

sending the package to an application programming interface (API) or other component;

receiving a determination that the package conforms to one or more standards for executing actions within the network security application;

based on receiving the determination that the package conforms to one or more standards for executing actions within the network security application, applying the package to an instance of the network security application;

receiving input defining an adaptive response, wherein the input identifies:

a correlation search used to identify notable events from event data stored by a data intake and query system, wherein the data intake and query system includes event data from a plurality of input data sources in the IT environment, and

the custom response action to be executed by the network security application in response to the detection of the potential security incident in the IT environment;

executing, by the data intake and query system, the correlation search against the event data stored by the data intake and query system;

identifying a notable event based on executing the correlation search against the event data stored by the data intake and query system; and

executing the custom response action based on identifying the notable event, wherein executing the custom response action comprises running the script file.

2. The computer-implemented method of claim 1 , wherein the code for performing the custom response action includes code for interacting with an external application.

3. The computer-implemented method of claim 1 , wherein the input defining the adaptive response further includes a configuration for parameters of the custom response action.

4. The computer-implemented method of claim 1 , wherein the input defining the custom response action is received via an editing panel of a graphical user interface.

5. The computer-implemented method of claim 4 , further comprising displaying, via the editing panel of the graphical user interface, output generated based on testing of the custom response action.

6. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause performance of operations comprising:

receiving input defining a custom response action to be executed by a network security application in response to a detection of a potential security incident in an information technology (IT) environment, wherein the input specifies a command to be sent to a device or service related to the network security application in response to the detection of the potential security incident in the IT environment, and wherein the input defining the custom response action further comprises a script file that includes code for performing the custom response action;

generating a package containing executable logic for the custom response action;

sending the package to an application programming interface (API) or other component;

receiving a determination that the package conforms to one or more standards for executing actions within the network security application;

based on receiving the determination that the package conforms to one or more standards for executing actions within the network security application, applying the package to an instance of the network security application;

receiving input defining an adaptive response, wherein the input identifies:

a correlation search used to identify notable events from event data stored by a data intake and query system, wherein the data intake and query system includes event data from a plurality of input data sources in the IT environment, and

the custom response action to be executed by the network security application in response to the detection of the potential security incident in the IT environment;

executing, by the data intake and query system, the correlation search against the event data stored by the data intake and query system;

identifying a notable event based on executing the correlation search against the event data stored by the data intake and query system; and

executing the custom response action based on identifying the notable event, wherein executing the custom response action comprises running the script file.

7. The non-transitory computer-readable storage medium of claim 6 ,

wherein the code for performing the custom response action includes code for interacting with an external application.

8. The non-transitory computer-readable storage medium of claim 6 , wherein the input defining the adaptive response further includes a configuration for parameters of the custom response action.

9. The non-transitory computer-readable storage medium of claim 6 , wherein the input defining the custom response action is received via an editing panel of a graphical user interface.

10. The non-transitory computer-readable storage medium of claim 9 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause performance of further operations comprising displaying, via the editing panel of the graphical user interface, output generated based on testing of the custom response action.

11. An apparatus, comprising:

one or more processors; and

a non-transitory computer-readable storage medium coupled to the one or more processors, the non-transitory computer-readable storage medium storing instructions that, when executed by the one or more processors, cause the apparatus to:

receive input defining a custom response action to be executed by a network security application in response to a detection of a potential security incident in an information technology (IT) environment, wherein the input specifies a command to be sent to a device or service related to the network security application in response to the detection of the potential security incident in the IT environment, and wherein the input defining the custom response action further comprises a script file that includes code for performing the custom response action;

generate a package containing executable logic for the custom response action;

send the package to an application programming interface (API) or other component;

receive a determination that the package conforms to one or more standards for executing actions within the network security application;

based on receiving the determination that the package conforms to one or more standards for executing actions within the network security application, apply the package to an instance of the network security application;

receive input defining an adaptive response, wherein the input identifies:

a correlation search used to identify notable events from event data stored by a data intake and query system, wherein the data intake and query system includes event data from a plurality of input data sources in the IT environment, and

the custom response action to be executed by the network security application in response to the detection of the potential security incident in the IT environment;

execute, by the data intake and query system, the correlation search against the event data stored by the data intake and query system;

identify a notable event based on executing the correlation search against the event data stored by the data intake and query system; and

execute the custom response action based on identifying the notable event, wherein executing the custom response action comprises running the script file.

12. The apparatus of claim 11 , wherein the code for performing the custom response action includes code for interacting with an external application.

13. The apparatus of claim 11 , wherein the input defining the adaptive response further includes a configuration for parameters of the custom response action.

14. The apparatus of claim 11 , wherein the input defining the custom response action is received via an editing panel of a graphical user interface.

15. The apparatus of claim 14 , wherein the instructions comprise further instructions that, when executed by the one or more processors, cause performance of further operations comprising displaying, via the editing panel of the graphical user interface, output generated based on testing of the custom response action.

Assignments (4)
CHANGE OF NAME Recorded Jul 22, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 072170/0599 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2025
From: SPLUNK LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 072173/0058 →
CHANGE OF NAME Recorded Jan 6, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 069826/0060 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 13, 2023
From: SHAHBAZ, BANIPAL; OAKLANDER DE LICORI, SRI ATMA; COATES, JOHN ROBERT; HAZEKAMP, DAVID; BADHANI, DEVENDRA; MURPHEY, LUKE; SCHULZ, PATRICK
To: SPLUNK INC.
Reel/Frame 064246/0522 →
Continuity (2)
Continuation 16944433 · Jul 31, 2020
Continuation 15276756 · Sep 26, 2016
References Cited (207)
US 4445177A · Bratt · 1984 [cited by examiner]
US 5787253A · McCreery et al. · 1998 [cited by applicant]
US 5796942A · Esbensen · 1998 [cited by applicant]
US 6044401A · Harvey · 2000 [cited by applicant]
US 6418471B1 · Shelton et al. · 2002 [cited by applicant]
US 6587969B1 · Weinberg et al. · 2003 [cited by applicant]
US 6792460B2 · Oulu et al. · 2004 [cited by applicant]
US 6810494B2 · Weinberg et al. · 2004 [cited by applicant]
US 6892167B2 · Polan et al. · 2005 [cited by applicant]
US 6898556B2 · Smocha et al. · 2005 [cited by applicant]
US 6915308B1 · Evans et al. · 2005 [cited by applicant]
US 6973489B1 · Levy · 2005 [cited by applicant]
US 6985944B2 · Aggarwal · 2006 [cited by applicant]
US 7177441B2 · Condon et al. · 2007 [cited by applicant]
US 7197559B2 · Goldstein et al. · 2007 [cited by applicant]
US 7219138B2 · Straut et al. · 2007 [cited by applicant]
US 7246101B2 · Fu et al. · 2007 [cited by applicant]
US 7257719B2 · Pandit et al. · 2007 [cited by applicant]
US 7260846B2 · Day · 2007 [cited by applicant]
US 7277957B2 · Rowley et al. · 2007 [cited by applicant]
US 7293238B1 · Brook et al. · 2007 [cited by applicant]
US 7376896B2 · Ullmann et al. · 2008 [cited by applicant]
US 7380272B2 · Sharp et al. · 2008 [cited by applicant]
US 7444263B2 · White et al. · 2008 [cited by applicant]
US 7543051B2 · Greifeneder et al. · 2009 [cited by applicant]
US 7577623B2 · Genty et al. · 2009 [cited by applicant]
US 7594011B2 · Chandra · 2009 [cited by applicant]
US 7594269B2 · Durham et al. · 2009 [cited by applicant]
US 7607170B2 · Chesla · 2009 [cited by applicant]
US 7610344B2 · Mehr et al. · 2009 [cited by applicant]
US 7623463B2 · Chavda · 2009 [cited by applicant]
US 7702806B2 · Gil et al. · 2010 [cited by applicant]
US 7729240B1 · Crane et al. · 2010 [cited by applicant]
US 7738396B1 · Turner et al. · 2010 [cited by applicant]
US 7751393B2 · Chaskar et al. · 2010 [cited by applicant]
US 7761918B2 · Gula et al. · 2010 [cited by applicant]
US 7797443B1 · Pettigrew et al. · 2010 [cited by applicant]
US RE41903E · Wenig et al. · 2010 [cited by applicant]
US 7836498B2 · Poletto et al. · 2010 [cited by applicant]
US 7869352B1 · Turner et al. · 2011 [cited by applicant]
US 7948889B2 · Lalonde et al. · 2011 [cited by applicant]
US 7962616B2 · Kupferman et al. · 2011 [cited by applicant]
US 7979555B2 · Rothstein et al. · 2011 [cited by applicant]
US 8019064B2 · Bedingfield et al. · 2011 [cited by applicant]
US 8020211B2 · Keanini et al. · 2011 [cited by applicant]
US 8032564B2 · Muret et al. · 2011 [cited by applicant]
US 8037175B1 · Apte et al. · 2011 [cited by applicant]
US 8042055B2 · Wenig et al. · 2011 [cited by applicant]
US 8056130B1 · Njemanze et al. · 2011 [cited by applicant]
US 8064350B2 · Peterman et al. · 2011 [cited by applicant]
US 8068986B1 · Shahbazi et al. · 2011 [cited by applicant]
US 8095640B2 · Guingo et al. · 2012 [cited by applicant]
US 8103765B2 · Greifeneder et al. · 2012 [cited by applicant]
US 8125908B2 · Rothstein et al. · 2012 [cited by applicant]
US 8127000B2 · Wenig et al. · 2012 [cited by applicant]
US 8140665B2 · Malloy et al. · 2012 [cited by applicant]
US 8144609B2 · Rao · 2012 [cited by applicant]
US 8185953B2 · Rothstein et al. · 2012 [cited by applicant]
US 8191136B2 · Dudfield et al. · 2012 [cited by applicant]
US 8195661B2 · Kalavade · 2012 [cited by applicant]
US 8248958B1 · Tulasi et al. · 2012 [cited by applicant]
US 8255511B1 · Moore et al. · 2012 [cited by applicant]
US 8301745B1 · Wohlgemuth et al. · 2012 [cited by applicant]
US 8335848B2 · Wenig et al. · 2012 [cited by applicant]
US 8364509B1 · Marr · 2013 [cited by applicant]
US 8385532B1 · Geist et al. · 2013 [cited by applicant]
US 8386371B2 · Kittelsen et al. · 2013 [cited by applicant]
US 8386598B2 · Robinson · 2013 [cited by applicant]
US 8473620B2 · Demmer et al. · 2013 [cited by applicant]
US 8522219B2 · Schwarzbauer et al. · 2013 [cited by applicant]
US 8533532B2 · Wenig et al. · 2013 [cited by applicant]
US 8549650B2 · Hanson · 2013 [cited by applicant]
US 8583772B2 · Wenig et al. · 2013 [cited by applicant]
US 8589375B2 · Zhang et al. · 2013 [cited by applicant]
US 8806361B1 · Noel et al. · 2014 [cited by applicant]
US 8806629B1 · Cherepov et al. · 2014 [cited by applicant]
US 8918430B2 · Fischer · 2014 [cited by applicant]
US 8997230B1 · McCauley et al. · 2015 [cited by applicant]
US 9137258B2 · Haugsnes · 2015 [cited by applicant]
US 9715675B2 · Chakravarty et al. · 2017 [cited by applicant]
US 20020015387A1 · Houh · 2002 [cited by applicant]
US 20030120619A1 · Osborn · 2003 [cited by applicant]
US 20030221000A1 · Cherkasova et al. · 2003 [cited by applicant]
US 20040030796A1 · Cooper et al. · 2004 [cited by applicant]
US 20040044912A1 · Connary et al. · 2004 [cited by applicant]
US 20040152444A1 · Lialiamou et al. · 2004 [cited by applicant]
US 20040193892A1 · Tamura et al. · 2004 [cited by applicant]
US 20040199361A1 · Lu et al. · 2004 [cited by applicant]
US 20050120160A1 · Plouffe et al. · 2005 [cited by applicant]
US 20050138013A1 · Walker et al. · 2005 [cited by applicant]
US 20050138426A1 · Styslinger · 2005 [cited by applicant]
US 20050273593A1 · Seminaro et al. · 2005 [cited by applicant]
US 20050278731A1 · Cameron et al. · 2005 [cited by applicant]
US 20060047721A1 · Narang et al. · 2006 [cited by applicant]
US 20060198318A1 · Schondelmayer et al. · 2006 [cited by applicant]
US 20060259967A1 · Thomas et al. · 2006 [cited by applicant]
US 20070033408A1 · Morten · 2007 [cited by applicant]
US 20070043861A1 · Baron et al. · 2007 [cited by applicant]
US 20070106692A1 · Klein · 2007 [cited by applicant]
US 20070150584A1 · Srinivasan · 2007 [cited by applicant]
US 20070156916A1 · Schiefer · 2007 [cited by applicant]
US 20070169194A1 · Church et al. · 2007 [cited by applicant]
US 20070208852A1 · Wexler et al. · 2007 [cited by applicant]
US 20080040191A1 · Chakravarty · 2008 [cited by examiner]
US 20080056139A1 · Liaqat · 2008 [cited by applicant]
US 20080229418A1 · Chen et al. · 2008 [cited by applicant]
US 20080244741A1 · Gustafson et al. · 2008 [cited by applicant]
US 20080281963A1 · Fletcher et al. · 2008 [cited by applicant]
US 20080301175A1 · Applebaum et al. · 2008 [cited by applicant]
US 20090129316A1 · Ramanathan et al. · 2009 [cited by applicant]
US 20090228474A1 · Chiu et al. · 2009 [cited by applicant]
US 20090238088A1 · Tan · 2009 [cited by applicant]
US 20090271504A1 · Ginter et al. · 2009 [cited by applicant]
US 20100031274A1 · Sim-Tang · 2010 [cited by applicant]
US 20100064307A1 · Malhotra et al. · 2010 [cited by applicant]
US 20100070929A1 · Behl et al. · 2010 [cited by applicant]
US 20100136943A1 · Hirvela et al. · 2010 [cited by applicant]
US 20100153316A1 · Duffield et al. · 2010 [cited by applicant]
US 20100318836A1 · Ness et al. · 2010 [cited by applicant]
US 20110106935A1 · Srinivasan · 2011 [cited by applicant]
US 20110166982A1 · Cole et al. · 2011 [cited by applicant]
US 20110231935A1 · Gula et al. · 2011 [cited by applicant]
US 20110238723A1 · Weintraub et al. · 2011 [cited by applicant]
US 20110296015A1 · Chakravarty et al. · 2011 [cited by applicant]
US 20110302305A1 · Morimura et al. · 2011 [cited by applicant]
US 20120017270A1 · Bartholomay et al. · 2012 [cited by applicant]
US 20120084437A1 · Wenig et al. · 2012 [cited by applicant]
US 20120089964A1 · Sawano · 2012 [cited by examiner]
US 20120158987A1 · Greifeneder et al. · 2012 [cited by applicant]
US 20120173966A1 · Powell et al. · 2012 [cited by applicant]
US 20120198047A1 · Steuer et al. · 2012 [cited by applicant]
US 20120239681A1 · Zhang et al. · 2012 [cited by applicant]
US 20130024431A1 · Parthasarathy et al. · 2013 [cited by applicant]
US 20130067034A1 · Degioanni et al. · 2013 [cited by applicant]
US 20130070622A1 · Degioanni et al. · 2013 [cited by applicant]
US 20130080620A1 · Cook · 2013 [cited by applicant]
US 20130091278A1 · Ludwig et al. · 2013 [cited by applicant]
US 20130111011A1 · Moulhaud et al. · 2013 [cited by applicant]
US 20130114456A1 · Dahod · 2013 [cited by applicant]
US 20130128742A1 · Yu · 2013 [cited by applicant]
US 20130132833A1 · White et al. · 2013 [cited by applicant]
US 20130136253A1 · Liberman et al. · 2013 [cited by applicant]
US 20130173782A1 · Ragutski et al. · 2013 [cited by applicant]
US 20130198391A1 · Weissblum · 2013 [cited by applicant]
US 20130212689A1 · Ben-Natan et al. · 2013 [cited by applicant]
US 20130227689A1 · Pietrowicz et al. · 2013 [cited by applicant]
US 20130232137A1 · Knott · 2013 [cited by applicant]
US 20130246925A1 · Ahuja et al. · 2013 [cited by applicant]
US 20130258995A1 · Skov et al. · 2013 [cited by applicant]
US 20140230062A1 · Kumaran · 2014 [cited by applicant]
US 20140317684A1 · Porras et al. · 2014 [cited by applicant]
US 20150013006A1 · Shulman et al. · 2015 [cited by applicant]
US 20150033333A1 · Merza · 2015 [cited by applicant]
US 20150163234A1 · Tal et al. · 2015 [cited by applicant]
US 20150172300A1 · Cochenour · 2015 [cited by applicant]
US 20150180891A1 · Seward et al. · 2015 [cited by applicant]
US 20160028758A1 · Ellis et al. · 2016 [cited by applicant]
US 20160034361A1 · Block · 2016 [cited by examiner]
US 20160078236A1 · Chesla · 2016 [cited by applicant]
US 20160119405A1 · Karpoor · 2016 [cited by examiner]
US 20160173446A1 · Nantel · 2016 [cited by applicant]
US 20160275190A1 · Seed et al. · 2016 [cited by applicant]
US 20170048260A1 · Peddemors et al. · 2017 [cited by applicant]
US 20170063920A1 · Thomas et al. · 2017 [cited by applicant]
US 20170223039A1 · Mont et al. · 2017 [cited by applicant]
US 20170230412A1 · Thomas et al. · 2017 [cited by applicant]
US 20170289178A1 · Roundy et al. · 2017 [cited by applicant]
US 20170339174A1 · Mounaguruswamy · 2017 [cited by applicant]
US 20180027006A1 · Zimmermann et al. · 2018 [cited by applicant]
US 20180034835A1 · Iwanir et al. · 2018 [cited by applicant]
CN 105302727A · 2016 [cited by examiner]
“API of a package in python. In _init_.py?”, 2010, obtained online from <https://stackoverflow.com/questions/3271794/api-of-a-package-in-python-in-init-py>, retrieved on Dec. 16, 2023 (Year: 2010). [cited by examiner]
Microsoft, the definition of script, Microsoft Computer Dictionary, Fifth Edition, p. 467 (Year: 2002). [cited by examiner]
“Basic Incident Response Script for Linux”, Jun. 19, 2016, obtained online from <https://github.com/puffyCid/linuxLiveResponse>, retrieved on Jun. 25, 2024 (Year: 2016). [cited by examiner]
Advisory Action from U.S. Appl. No. 14/253,753, Apr. 29, 2016, 2 pages. [cited by applicant]
Advisory Action from U.S. Appl. No. 14/253,753, May 7, 2015, 2 pages. [cited by applicant]
Advisory Action from U.S. Appl. No. 14/253,767, Mar. 1, 2016, 3 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,713, Feb. 10, 2015, 15 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,713, Feb. 12, 2016, 17 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,744, Jan. 9, 2015, 29 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,744, Oct. 23, 2015, 51 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,753, Feb. 4, 2016, 17 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,753, Mar. 2, 2015, 19 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,767, Dec. 16, 2015, 21 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/253,767, Jan. 7, 2015, 14 pages. [cited by applicant]
Final Office Action from U.S. Appl. No. 14/528,898, Jun. 29, 2016, 18 pages. [cited by applicant]
Final Office Action received for U.S. Appl. No. 15/276,756, Feb. 21, 2019, 28 pages. [cited by applicant]
JD Lenaeus, “How to Implement Security Controls for an Information Security Program at CBRN Facilities”, 2015, obtained online from <https://www.pnnl.gov/main/publications/external/technical_reports/PNNL-25112.pdf>, ret… [cited by applicant]
Non-Final Office Acion, U.S. Appl. No. 16/944,433, Jul. 22, 2022, 27 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,713, Aug. 12, 2015, 17 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,713, Sep. 3, 2014, 26 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,744, Jul. 5, 2016, 31 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,744, Jun. 10, 2015, 50 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,744, Oct. 6, 2014, 34 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,753, Jul. 1, 2016, 21 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,753, Jul. 28, 2015, 14 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,753, Sep. 5, 2014, 16 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,767, Jul. 15, 2015, 17 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,767, Jun. 19, 2014, 13 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/253,767, Sep. 19, 2016, 21 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/528,898, Mar. 31, 2016, 17 pages. [cited by applicant]
Non-Final Office Action from U.S. Appl. No. 14/528,918, Feb. 17, 2016, 17 pages. [cited by applicant]
Non-Final Office Action received for U.S. Appl. No. 15/276,756, Jul. 30, 2018, 25 pages. [cited by applicant]
Non-Final Office Action received for U.S. Appl. No. 15/276,756, Sep. 3, 2019, 27 pages. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 14/528,918, Aug. 18, 2016, 5 pages. [cited by applicant]
Notice of Allowance, U.S. Appl. No. 16/944,433, Jan. 31, 2023, 23 pages. [cited by applicant]
Notice of Allowance, U.S. Appl. No. 15/276,756, May 7, 2020, 17 pages. [cited by applicant]