IP Library › Granted Patent US 12,739,162
Granted Patent B2
US 12,739,162 · App. 18/332,428 · Granted Sep 15, 2026

Techniques for activation triggering using time-series based event data

Inventors: Abhilash Panwar (Redmond, WA); Clemens Alden Szyperski (Bellevue, WA); James Douglas Hutton (London, GB); John Te-Jui Sheu (Bellevue, WA); Luca Colantonio (Redmond, WA); Maxim Kiryushin (London, GB); Pawel Mateusz Chodarcewicz (Redmond, WA); Phanidhar Gopavaram (Redmond, WA); William Charles Thompson (Duvall, WA)
Assignee: Microsoft Technology Licensing, LLC
H04L41/0631G06F11/0784G06F11/3058G06F11/3075G06F16/24568G06F16/2474G06F16/26H04L41/22
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,739,162
App. No.
18/332,428
Granted
Sep 15, 2026
Kind
B2
Abstract

Aspects of the present disclosure relate to detecting occurrence of triggers related to properties of objects indicated in event data in a discoverable event stream. These techniques may include identifying a namespace associated with an activation trigger, and identifying a plurality of time-series based objects of a discoverable event stream associated with the namespace. The techniques may further include determining that an activation rule is met over the plurality of time-series based objects. Additionally, the techniques may include transmitting an activation trigger event to an activation component, the activation trigger event including a generic activation identifier identifying an action to perform, and an actor identifier identifying an actor to perform the action.

Claims (82)

1 . A method comprising:

identifying a namespace associated with an activation trigger;

identifying a plurality of time-series based events of a discoverable event stream associated with the namespace, wherein the discoverable event stream includes the plurality of time-series based events, received from multiple objects, in a single stream ordered by time;

determining that an activation rule is met over the plurality of time-series based events;

publishing an activation trigger event to the discoverable event stream, the activation trigger event including a generic activation identifier identifying an action to perform, and an actor identifier identifying an actor to perform the action;

obtaining, based on monitoring the discoverable event stream, the activation trigger event via the discoverable event stream, the activation trigger event including the generic activation identifier and the actor identifier;

generating, based on the generic activation identifier and the actor identifier, an activation instruction event for causing an action associated with the generic activation identifier at an actor corresponding to the actor identifier, including mapping a field within the activation instruction event to a configuration value within the activation trigger event to which the field corresponds;

configuring, based on the activation trigger event, the activation instruction event to trigger the action at the actor; and

transmitting the activation instruction event to the actor based on the actor identifier.

2 . The method of claim 1 , wherein the generic activation identifier identifies at least one of sending a notification, sending a state change instruction to an external device, sending a state change instruction to an external system, sending an invocation instruction to an external system, sending an invocation instruction to a data processing system, or sending an analysis instruction to a data processing system.

3 . The method of claim 1 , wherein generating the activation instruction event for causing the action comprises:

identifying a collection of commands associated with the actor; and

selecting, from the collection of commands, a command for the activation instruction event.

4 . The method of claim 1 , wherein configuring the activation instruction event comprises:

detecting a presence of a parameterized value within the activation trigger event;

identifying a parameterized value field of the activation instruction event that corresponds to the parameterized value;

determining a static value for the parameterized value field based on the parameterized value; and

mapping the parameterized value field to the static value within the activation instruction event.

5 . The method of claim 4 , wherein the parameterized value is a role and/or role group, and the static value is one or more communication addresses.

6 . The method of claim 1 , wherein generating the activation instruction event comprises:

detecting a presence of the configuration value within the activation trigger event;

identifying the field of the activation instruction event that corresponds to the configuration value.

7 . The method of claim 1 , wherein activation instruction event is a first activation instruction event, the action is a first action, and further comprising:

generating a second activation instruction event for causing a second action associated with the actor;

identifying a conflict between the first action and the second action; and

determining, based on the conflict, not to send the second activation instruction event to the actor.

8 . The method of claim 1 , wherein the activation trigger event is a first activation trigger event, activation instruction event is a first activation instruction event, and further comprising:

receiving a second activation trigger event via the discoverable event stream;

identifying a conflict between the first activation trigger event and the second activation trigger event; and

determining, based on the conflict, not to generate a second activation instruction event corresponding to the second activation trigger event.

9 . The method of claim 1 , wherein the activation instruction event causes the actor to perform the action, and generate an activation event corresponding to the action within the discoverable event stream.

10 . The method of claim 1 , further comprising:

identifying the plurality of time-series based events of the discoverable event stream that triggered the activation rule;

determining explainability information based on the plurality of time-series based events, the explainability information identifying an importance value of the plurality of time-series based events; and

presenting the explainability information via a graphical user interface.

11 . The method of claim 10 , further comprising:

generating a tree structure representing one or more activation rules including the activation rule, and wherein determining the explainability information comprises determining the explainability information based on a relationship between the activation rule and other activation rules within the tree structure.

12 . An apparatus, comprising:

a memory; and

a processor coupled with the memory and configured to:

identify a namespace associated with an activation trigger;

identify a plurality of time-series based events of a discoverable event stream associated with the namespace, wherein the discoverable event stream includes the plurality of time-series based events, received from multiple objects, in a single stream ordered by time;

determine that an activation rule is met over the plurality of time-series based events;

publish an activation trigger event to the discoverable event stream, the activation trigger event including a generic activation identifier identifying an action to perform, and an actor identifier identifying an actor to perform the action;

obtain, based on monitoring the discoverable event stream, the activation trigger event via the discoverable event stream, the activation trigger event including the generic activation identifier and the actor identifier;

generate, based on the generic activation identifier and the actor identifier, an activation instruction event for causing an action associated with the generic activation identifier at an actor corresponding to the actor identifier, including mapping a field within the activation instruction event to a configuration value within the activation trigger event to which the field corresponds;

configure, based on the activation trigger event, the activation instruction event to trigger the action at the actor; and

transmit the activation instruction event to the actor based on the actor identifier.

13 . The apparatus of claim 12 , wherein the activation instruction event is a first activation instruction event, the action is a first action, and wherein the processor is further configured to:

generate a second activation instruction event for causing a second action associated with the actor;

identify a conflict between the first action and the second action; and

determine, based on the conflict, not to send the second activation instruction event to the actor.

14 . The apparatus of claim 12 , wherein the activation trigger event is a first activation trigger event, the activation instruction event is a first activation instruction event, and wherein the processor is further configured to:

receive a second activation trigger event via the discoverable event stream;

identify a conflict between the first activation trigger event and the second activation trigger event; and

determine, based on the conflict, not to generate a second activation instruction event corresponding to the second activation trigger event.

15 . The apparatus of claim 12 , wherein the processor is further configured to:

identify the plurality of time-series based events of the discoverable event stream that triggered the activation rule;

determine explainability information based on the plurality of time-series based events, the explainability information identifying an importance value of the plurality of time-series based events; and

present the explainability information via a graphical user interface.

16 . The apparatus of claim 12 , wherein the generic activation identifier identifies at least one of sending a notification, sending a state change instruction to an external device, sending a state change instruction to an external system, sending an invocation instruction to an external system, sending an invocation instruction to a data processing system, or sending an analysis instruction to a data processing system.

17 . The apparatus of claim 12 , wherein the processor is configured to generate the activation instruction event for causing the action including:

identifying a collection of commands associated with the actor; and

selecting, from the collection of commands, a command for the activation instruction event.

18 . The apparatus of claim 12 , wherein the processor is configured to configure the activation instruction event including:

detecting a presence of a parameterized value within the activation trigger event;

identifying a parameterized value field of the activation instruction event that corresponds to the parameterized value;

determining a static value for the parameterized value field based on the parameterized value; and

mapping the parameterized value field to the static value within the activation instruction event.

19 . A non-transitory computer-readable device having instructions thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

identifying a namespace associated with an activation trigger;

identifying a plurality of time-series based events of a discoverable event stream associated with the namespace, wherein the discoverable event stream includes the plurality of time-series based events, received from multiple objects, in a single stream ordered by time;

determining that an activation rule is met over the plurality of time-series based events;

publishing an activation trigger event to the discoverable event stream, the activation trigger event including a generic activation identifier identifying an action to perform, and an actor identifier identifying an actor to perform the action;

obtaining, based on monitoring the discoverable event stream, the activation trigger event via the discoverable event stream, the activation trigger event including the generic activation identifier and the actor identifier;

generating, based on the generic activation identifier and the actor identifier, an activation instruction event for causing an action associated with the generic activation identifier at an actor corresponding to the actor identifier, including mapping a field within the activation instruction event to a configuration value within the activation trigger event to which the field corresponds;

configuring, based on the activation trigger event, the activation instruction event to trigger the action at the actor; and

transmitting the activation instruction event to the actor based on the actor identifier.

20 . The non-transitory computer-readable device of claim 19 , wherein the operations further comprise:

identifying the plurality of time-series based events of the discoverable event stream that triggered the activation rule;

determining explainability information based on the plurality of time-series based events, the explainability information identifying an importance value of the plurality of time-series based events; and

presenting the explainability information via a graphical user interface.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 15, 2023
From: PANWAR, ABHILASH; SZYPERSKI, CLEMENS ALDEN; HUTTON, JAMES DOUGLAS; SHEU, JOHN TE-JUI; COLANTONIO, LUCA; KIRYUSHIN, MAXIM; CHODARCEWICZ, PAWEL MATEUSZ; GOPAVARAM, PHANIDHAR; THOMPSON, WILLIAM CHARLES
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 063965/0780 →
Continuity (2)
Provisional Application 63487609 · Feb 28, 2023
Related Publication 20240291708A1 · Aug 29, 2024
References Cited (188)
US 8560611B2 · Martinez · 2013 [cited by examiner]
US 9516053B1 · Muddu et al. · 2016 [cited by applicant]
US 9798830B2 · Imaki et al. · 2017 [cited by applicant]
US 10514966B2 · Alfred et al. · 2019 [cited by applicant]
US 10558516B2 · Leverich et al. · 2020 [cited by applicant]
US 10762097B1 · Porath · 2020 [cited by applicant]
US 10936585B1 · Echeverria et al. · 2021 [cited by applicant]
US 11042454B1 · Jain et al. · 2021 [cited by applicant]
US 11055273B1 · Meduri et al. · 2021 [cited by applicant]
US 11269808B1 · Yuan et al. · 2022 [cited by applicant]
US 11341150B1 · Ganesan · 2022 [cited by applicant]
US 11397752B1 · Goyal et al. · 2022 [cited by applicant]
US 11461347B1 · Das · 2022 [cited by applicant]
US 11487762B2 · May et al. · 2022 [cited by applicant]
US 11803562B2 · Sarma et al. · 2023 [cited by applicant]
US 11818156B1 · Parikh et al. · 2023 [cited by applicant]
US 11847038B1 · Jha et al. · 2023 [cited by applicant]
US 11853317B1 · Goyal · 2023 [cited by applicant]
US 12028208B1 · Hsiao et al. · 2024 [cited by applicant]
US 20030172151A1 · Schade · 2003 [cited by applicant]
US 20040073720A1 · Clough et al. · 2004 [cited by applicant]
US 20070203816A1 · Costache et al. · 2007 [cited by applicant]
US 20080215546A1 · Baum et al. · 2008 [cited by applicant]
US 20090018994A1 · Hajdukiewicz · 2009 [cited by applicant]
US 20090292877A1 · Piper · 2009 [cited by applicant]
US 20110131588A1 · Allam et al. · 2011 [cited by applicant]
US 20120148088A1 · Mital et al. · 2012 [cited by applicant]
US 20130262369A1 · Guanwardana et al. · 2013 [cited by applicant]
US 20140095483A1 · Toillion et al. · 2014 [cited by applicant]
US 20140095535A1 · Deshmukh · 2014 [cited by applicant]
US 20140095541A1 · Herwadkar · 2014 [cited by examiner]
US 20140149444A1 · Pompey · 2014 [cited by applicant]
US 20150149507A1 · Imaki · 2015 [cited by applicant]
US 20150186434A1 · Eichinger · 2015 [cited by applicant]
US 20150199413A1 · Brown · 2015 [cited by applicant]
US 20150293954A1 · Hsiao et al. · 2015 [cited by applicant]
US 20150295778A1 · Hsiao et al. · 2015 [cited by applicant]
US 20150295779A1 · Ching et al. · 2015 [cited by applicant]
US 20150295780A1 · Hsiao et al. · 2015 [cited by applicant]
US 20150295796A1 · Hsiao et al. · 2015 [cited by applicant]
US 20150317363A1 · Manzano Macho et al. · 2015 [cited by applicant]
US 20150324439A1 · Bhave · 2015 [cited by applicant]
US 20150341212A1 · Hsiao · 2015 [cited by applicant]
US 20150363464A1 · Alves · 2015 [cited by applicant]
US 20160019266A1 · Katsunuma · 2016 [cited by applicant]
US 20160054952A1 · Mathur · 2016 [cited by applicant]
US 20160063080A1 · Nano · 2016 [cited by examiner]
US 20160070430A1 · Kim et al. · 2016 [cited by applicant]
US 20160070451A1 · Kim et al. · 2016 [cited by applicant]
US 20160085810A1 · De Castro Alves · 2016 [cited by applicant]
US 20160127180A1 · Shcherbakov et al. · 2016 [cited by applicant]
US 20160127401A1 · Chauhan et al. · 2016 [cited by applicant]
US 20160127517A1 · Shcherbakov et al. · 2016 [cited by applicant]
US 20160210332A1 · Milton · 2016 [cited by applicant]
US 20160224899A1 · Nguyen · 2016 [cited by applicant]
US 20160359910A1 · Chen et al. · 2016 [cited by applicant]
US 20160359940A1 · Chen et al. · 2016 [cited by applicant]
US 20170060947A1 · Zhang · 2017 [cited by applicant]
US 20170083175A1 · Layman · 2017 [cited by applicant]
US 20170124151A1 · Ji et al. · 2017 [cited by applicant]
US 20170177546A1 · Heinz et al. · 2017 [cited by applicant]
US 20170201606A1 · Ding · 2017 [cited by applicant]
US 20180004812A1 · Shawver et al. · 2018 [cited by applicant]
US 20180074856A1 · Park · 2018 [cited by applicant]
US 20180075125A1 · Stiel · 2018 [cited by applicant]
US 20180089205A1 · Soora · 2018 [cited by applicant]
US 20180107530A1 · Gupta · 2018 [cited by applicant]
US 20180181537A1 · Crabtree et al. · 2018 [cited by applicant]
US 20180218046A1 · Woo · 2018 [cited by examiner]
US 20180253468A1 · Gurajada et al. · 2018 [cited by applicant]
US 20180268003A1 · Barsness · 2018 [cited by applicant]
US 20180314740A1 · Van Osten · 2018 [cited by applicant]
US 20180357267A1 · Zenger et al. · 2018 [cited by applicant]
US 20190028506A1 · Rodriguez · 2019 [cited by applicant]
US 20190095510A1 · Cruise · 2019 [cited by applicant]
US 20190102431A1 · Bishnoi et al. · 2019 [cited by applicant]
US 20190102791A1 · Park · 2019 [cited by applicant]
US 20190124105A1 · Chauhan et al. · 2019 [cited by applicant]
US 20190138641A1 · Pal · 2019 [cited by applicant]
US 20190138967A1 · Akella · 2019 [cited by applicant]
US 20190146970A1 · Chamieh · 2019 [cited by applicant]
US 20190155804A1 · Miller et al. · 2019 [cited by applicant]
US 20190155809A1 · Shankar · 2019 [cited by applicant]
US 20190171748A1 · Duffield · 2019 [cited by applicant]
US 20190294598A1 · Hsiao · 2019 [cited by examiner]
US 20190303385A1 · Ching et al. · 2019 [cited by applicant]
US 20200320005A1 · Shulman · 2020 [cited by applicant]
US 20200412810A1 · Knight · 2020 [cited by examiner]
US 20210004144A1 · Burke · 2021 [cited by applicant]
US 20210019292A1 · Kholodkov et al. · 2021 [cited by applicant]
US 20210026888A1 · Pang · 2021 [cited by applicant]
US 20210049797A1 · Cervelli et al. · 2021 [cited by applicant]
US 20210081373A1 · Tian · 2021 [cited by applicant]
US 20210117384A1 · Leite et al. · 2021 [cited by applicant]
US 20210124786A1 · Bursik · 2021 [cited by applicant]
US 20210157811A1 · Wang · 2021 [cited by applicant]
US 20210191769A1 · Eschinger · 2021 [cited by applicant]
US 20210311834A1 · Sapuntzakis · 2021 [cited by applicant]
US 20210365449A1 · Ha et al. · 2021 [cited by applicant]
US 20210397616A1 · Iranmanesh · 2021 [cited by applicant]
US 20220030066A1 · Govindaraju · 2022 [cited by applicant]
US 20220058174A1 · Lemberg et al. · 2022 [cited by applicant]
US 20220100763A1 · Sen et al. · 2022 [cited by applicant]
US 20220121689A1 · James · 2022 [cited by applicant]
US 20220147518A1 · Schindlauer et al. · 2022 [cited by applicant]
US 20220198263A1 · Guo et al. · 2022 [cited by applicant]
US 20220292021A1 · Bitincka · 2022 [cited by applicant]
US 20230048668A1 · Danilov et al. · 2023 [cited by applicant]
US 20230134030A1 · Zhou · 2023 [cited by applicant]
US 20230401466A1 · Zhao · 2023 [cited by applicant]
US 20240039954A1 · Shete et al. · 2024 [cited by applicant]
US 20240070233A1 · Blackburn · 2024 [cited by applicant]
US 20240078221A1 · Song · 2024 [cited by applicant]
US 20240289244A1 · Panwar et al. · 2024 [cited by applicant]
US 20240289336A1 · Panwar et al. · 2024 [cited by applicant]
US 20240289337A1 · Szyperski · 2024 [cited by applicant]
US 20240289347A1 · Panwar et al. · 2024 [cited by applicant]
US 20240289714A1 · Panwar et al. · 2024 [cited by applicant]
US 20250151126A1 · Yin et al. · 2025 [cited by applicant]
US 20260032013A1 · Danielson et al. · 2026 [cited by applicant]
US 20260037537A1 · Dhenia et al. · 2026 [cited by applicant]
WO 2016032986A1 · 2016 [cited by applicant]
Buddhika, et al., “Living on the Edge”, ACM Transactions on internet of things, vol. 2, Issue 3, Jul. 8, 2021, pp. 1-31. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016446, May 17, 2024, 13 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016573, Jun. 5, 2024, 15 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016580, Jun. 5, 2024, 12 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016590, Jun. 6, 2024, 13 pages. [cited by applicant]
Invitation to pay additional fees received for PCT Application No. PCT/US2024/016587 May 29, 2024, 13 pages. [cited by applicant]
Levy, Eran, “Batch, Stream, and Micro-batch Processing: A Cheat Sheet Upsolver”, Retrieved from the URL: https://web.archive.org/web/20221207202218/https://www.upsolver.com/blog/batch-stream-a-cheat-sheet, Dec. 7, 2022,… [cited by applicant]
Non-Final Office Action mailed on May 3, 2024, in U.S. Appl. No. 18/332,523, 15 pages. [cited by applicant]
Etzion, et al., “Event Processing in Action,” Retrieved from URL: https://web.archive.org/web/20190711095302if / http://www-di.inf.puc-rio.br:80/-endler/courses/RT-Analytics/transp/Books/Event%20Processing%20in%20Action… [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016455, Jul. 18, 2024, 15 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016587, mailed on Jul. 22, 2024, 22 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016789, Jul. 2, 2024, 15 pages. [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/US2024/016968, mailed on Jul. 29, 2024, 10 pages. [cited by applicant]
Non-Final Office Action mailed on Aug. 1, 2024, in U.S. Appl. No. 18/332,502, 37 pages. [cited by applicant]
Non-Final Office Action mailed on Jul. 31, 2024, in U.S. Appl. No. 18/332,316, 12 pages. [cited by applicant]
Non-Final Office Action mailed on Jun. 11, 2024, in U.S. Appl. No. 18/332,301, 18 pages. [cited by applicant]
Grund, et al., “HYRISE—A Main Memory Hybrid Storage Engine”, Proceedings of the VLDB Endowment, vol. 4, Issue No. 2, Nov. 2010, pp. 105-116. [cited by applicant]
Non-Final Office Action mailed on Oct. 9, 2024, in U.S. Appl. No. 18/332,523, 25 pages. [cited by applicant]
Non-Final Office Action mailed on Sep. 30, 2024, in U.S. Appl. No. 18/332,312, 19 pages. [cited by applicant]
Final Office Action mailed on Nov. 22, 2024, in U.S. Appl. No. 18/332,502, 39 pages. [cited by applicant]
Non-Final Office Action mailed on Oct. 23, 2024, in U.S. Appl. No. 18/332,316, 12 pages. [cited by applicant]
Final Office Action mailed on Dec. 13, 2024, in U.S. Appl. No. 18/332,301, 19 Pages. [cited by applicant]
Final Office Action mailed on Mar. 19, 2025, in U.S. Appl. No. 18/332,523, 25 pages. [cited by applicant]
Non-Final Office Action mailed on Mar. 25, 2025, in U.S. Appl. No. 18/332,466, 17 pages. [cited by applicant]
Notice of Allowance mailed on Mar. 13, 2025, in U.S. Appl. No. 18/332,502 13 pages. [cited by applicant]
Penchikala, Srini, “Big Data Processing with Apache Spark—Part 3: Spark Streaming”, Retrieved from URL: https://www.infoq.com/articles/apache-spark-streaming/, Jan. 7, 2016, 17 pages. [cited by applicant]
Final Office Action mailed on Apr. 22, 2025, in U.S. Appl. No. 18/332,316, 15 pages. [cited by applicant]
Final Office Action mailed on May 22, 2025, in U.S. Appl. No. 18/332,312, 15 pages. [cited by applicant]
Golab Lukasz, “Sliding Window Query Processing over Data Streams”, 2006, 180 pages. [cited by applicant]
Notice of Allowance mailed on Apr. 28, 2025, in U.S. Appl. No. 18/332,301, 15 pages. [cited by applicant]
Kim, et al., “A Review of Window Query Processing for Data Streams”, Journal of Computing Science and Engineering, Dec. 2013, vol. 7, No. 4, pp. 220-230. [cited by applicant]
Non-Final Office Action mailed on Jul. 29, 2025, in U.S. Appl. No. 18/332,523, 28 pages. [cited by applicant]
Notice of Allowance mailed on Aug. 4, 2025, in U.S. Appl. No. 18/332,316, 9 pages. [cited by applicant]
Notice of Allowance mailed on Jun. 24, 2025, in U.S. Appl. No. 18/332,502, 14 pages. [cited by applicant]
Armstrong, et al., “LinkBench: a database benchmark based on the Facebook social graph”, In Proceedings of the Acm Sigmod International Conference on Management of Data, Jun. 2013, pp. 1185-1196. [cited by applicant]
Final Office Action mailed on Oct. 1, 2025, in U.S. Appl. No. 18/332,466, 36 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter 1) received for PCT Application No. PCT/US2024/016580), mailed on Sep. 11, 2025, 07 Pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016455, Sep. 11, 2025, 09 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016587, Sep. 11, 2025, 15 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016590, Sep. 11, 2025, 7 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016968, Sep. 11, 2025, 7 pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016446, mailed on Sep. 11, 2025, 8 pages. [cited by applicant]
International Preliminary Report on Patentability received for PCT Application No. PCT/US2024/016789, mailed on Sep. 11, 2025, 9 pages. [cited by applicant]
Notice of Allowance mailed on Aug. 26, 2025, in U.S. Appl. No. 18/332,301, 14 pages. [cited by applicant]
Notice of Allowance mailed on Nov. 10, 2025, in U.S. Appl. No. 18/332,502, 14 Pages. [cited by applicant]
Notice of Allowance mailed on Oct. 15, 2025, in U.S. Appl. No. 18/332,483, 12 Pages. [cited by applicant]
Notice of Allowance mailed on Oct. 23, 2025, in U.S. Appl. No. 18/332,316, 10 Pages. [cited by applicant]
Tulone, et al., “PAQ: Time Series Forecasting for Approximate Query Answering in Sensor Networks”, Wireless Sensor Networks, 2006, 16 Pages. [cited by applicant]
International Preliminary Report on Patentability (Chapter I) received for PCT Application No. PCT/US2024/016573, mailed on Sep. 11, 2025, 9 Pages. [cited by applicant]
Georgiou, et al., “StreamSight: A Query-Driven Framework for Streaming Analytics in Edge Computing”, 2018, 10 pages. [cited by applicant]
Notice of Allowance mailed on Jul. 20, 2026, in U.S. Appl. No. 18/332,483, 7 pages. [cited by applicant]
Ex Parte Quayle Action mailed on Apr. 30, 2026, in U.S. Appl. No. 18/332,483, 6 pages. [cited by applicant]
Notice of Allowance mailed on Apr. 29, 2026, in U.S. Appl. No. 18/332,301, 14 Pages. [cited by applicant]
Notice of Allowance mailed on Aug. 6, 2026, in U.S. Appl. No. 18/332,312, 29 pages. [cited by applicant]
Notice of Allowance mailed on Jun. 22, 2026, in U.S. Appl. No. 18/332,523, 19 Pages. [cited by applicant]
Notice of Allowance mailed on May 13, 2026, in U.S. Appl. No. 18/332,316, 11 pages. [cited by applicant]
Notice of Allowance mailed on Aug. 4, 2026, in U.S. Appl. No. 18/332,316, 9 pages. [cited by applicant]
Notice of Allowance mailed on Jun. 9, 2026, in U.S. Appl. No. 18/332,502, 11 pages. [cited by applicant]
Non-Final Office Action mailed on Jan. 16, 2026, in U.S. Appl. No. 18/332,312, 14 pages. [cited by applicant]
Notice of Allowance mailed on Jan. 21, 2026, in U.S. Appl. No. 18/332,523, 20 Pages. [cited by applicant]
Notice of Allowance mailed on Mar. 4, 2026, in U.S. Appl. No. 18/332,316, 10 pages. [cited by applicant]
Notice of Allowance mailed on Mar. 9, 2026, in U.S. Appl. No. 18/332,502, 11 Pages. [cited by applicant]
Notice of Allowance mailed on Mar. 10, 2026, in U.S. Appl. No. 18/332,483, 07 Pages. [cited by applicant]
Notice of Allowance mailed on Mar. 13, 2026, in U.S. Appl. No. 18/332,301, 14 Pages. [cited by applicant]
Bozkurt et al., “Utilizing Flink and Kafka Technologies for Real-Time Data Processing: A Case Study”, 2023, The Eurasia Proceedings of Science, Technology, Engineering & Mathematics (EPSTEM), Vo.I 24, p. 177-183. [cited by applicant]
Non-Final Office Action mailed on Mar. 26, 2026, in U.S. Appl. No. 18/332,466, 20 pages. [cited by applicant]