IP Library Granted Patent US 12,536,178
Granted Patent B2
US 12,536,178 · App. 18/338,053 · Granted Jan 27, 2026

Data stream analytics at service layer

Inventors: Sneha Aman Singh (Issaquah, WA); Xu Li (Plainsboro, NJ); Quang Ly (North Wales, PA); Gregory S. Sternberg (Mt. Laurel, NJ); Shamim Akbar Rahman (Cote St. Luc, CA); Chonggang Wang (Princeton, NJ)
Assignee: InterDigital Patent Holdings, Inc.
G06F16/24568G06F16/00H04L12/28H04L12/2823H04L43/04H04L43/18H04L67/12H04W4/70H04W12/08H04L63/10H04L63/1425
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,536,178
App. No.
18/338,053
Granted
Jan 27, 2026
Kind
B2
Abstract

A modular and distributed architecture for data stream processing and analysis is described to incorporate data stream analytics capabilities, called Data Stream Analytics Service (DSAS) in the IoT/M2M service layer. Each service layer node hosting DSAS can be split into two independent modules, Stream Forwarder and Stream Analytics Engine. Stream Forwarder is a light weight processing modules that can be responsible for data preprocessing and routing. Stream Analytics Engine is responsible for performing actual analytics on the data stream. Separating the two functionalities enables the service layer nodes to efficiently distribute stream analytics tasks across multiple nodes.

Claims (35)

1 . An apparatus for a service supporting service capabilities in a Resource-Oriented Architecture (ROA) through a set of Application Programming Interfaces (APIs), the apparatus comprising circuitry configured to:

receive, from a first client entity, a first request for creating a data stream query resource in the ROA via RESTful methods;

authorize, based on the first request, the first client entity by referring to one or more access control policies;

create, based on authorizing the first client entity, the data stream query resource having a plurality of attributes, the data stream query resource comprising one or more data stream IDs;

send, based on the first request and to the first client entity, a query response;

receive, from a second client entity, a second request to access the data stream query resource;

authorize, based on the second request, the second client entity to access the data stream query resource by referring to one or more access control policies;

generate, based on authorizing the second client entity, a query output from the data stream query resource based on one or more query parameters; and

send, to the second client entity, the query output.

2 . The apparatus of claim 1 , wherein the service is provided as a middleware service between network protocol stacks and applications.

3 . The apparatus of claim 2 , wherein the service is a oneM2M service layer.

4 . The apparatus of claim 1 , wherein the data stream query resource further comprises a query output format and a query switch for enabling/disabling.

5 . The apparatus of claim 1 , wherein the one or more query parameters further indicate output format.

6 . The apparatus of claim 1 , wherein the one or more query parameters further indicate maximum error tolerance.

7 . The apparatus of claim 1 , wherein the apparatus comprises a service layer component.

8 . The apparatus of claim 1 , wherein the first client entity comprises an Internet of Things (IoT) device.

9 . The apparatus of claim 1 , wherein the first client entity and the second client entity are different.

10 . The apparatus of claim 1 , wherein the second request to access the data stream query resource comprises raw data, and wherein the circuitry is configured to generate the query output based on the raw data.

11 . A method for a service supporting service capabilities in a Resource-Oriented Architecture (ROA) through a set of Application Programming Interfaces (APIs), the method comprising:

receiving, from a first client entity, a first request for creating a data stream query resource in the ROA via RESTful methods;

authorizing, based on the first request, the first client entity by referring to one or more access control policies;

creating, based on authorizing the first client entity, the data stream query resource having a plurality of attributes, the data stream query resource comprising one or more data stream IDs;

sending, based on the first request and to the first client entity, a query response;

receiving, from a second client entity, a second request to access the data stream query resource;

authorizing, based on the second request, the second client entity to access the data stream query resource by referring to one or more access control policies;

generating, based on authorizing the second client entity, a query output from the data stream query resource based on one or more query parameters; and

sending, to the second client entity, the query output.

12 . The method of claim 11 , wherein the service is provided as a middleware service between network protocol stacks and applications.

13 . The method of claim 12 , wherein the service is a oneM2M service layer.

14 . The method of claim 11 , wherein the first client entity comprises an Internet of Things (IoT) device.

15 . The method of claim 11 , wherein the data stream query resource further comprises a query output format and a query switch for enabling/disabling.

16 . The method of claim 11 , wherein the one or more query parameters further indicate output format.

17 . The method of claim 11 , wherein the one or more query parameters further indicate maximum error tolerance.

18 . The method of claim 11 , wherein the first client entity and the second client entity are different.

19 . The method of claim 11 , wherein the second request to access the data stream query resource comprises raw data, and wherein the method comprises generating the query output based on the raw data.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2025
From: CONVIDA WIRELESS, LLC
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 071773/0735 →
Continuity (4)
Continuation 17175100 · Feb 12, 2021
Continuation 16096510
Provisional Application 62326894 · Apr 25, 2016
Related Publication 20230334051A1 · Oct 19, 2023
References Cited (60)
US 7480660B1 · Black · 2009 [cited by examiner]
US 8301645B1 · Crook et al. · 2012 [cited by applicant]
US 8606825B1 · Matthews · 2013 [cited by examiner]
US 8935751B1 · Cardente · 2015 [cited by examiner]
US 9026644B2 · Parker · 2015 [cited by examiner]
US 9251215B2 · Chen · 2016 [cited by examiner]
US 9497198B2 · Mullick · 2016 [cited by examiner]
US 9710518B2 · Cheng · 2017 [cited by examiner]
US 10601958B2 · Wada · 2020 [cited by examiner]
US 10853359B1 · Waugh · 2020 [cited by examiner]
US 11431785B2 · Spaven et al. · 2022 [cited by applicant]
US 20040004631A1 · Debique et al. · 2004 [cited by applicant]
US 20040117157A1 · Bantz et al. · 2004 [cited by applicant]
US 20050175029A1 · Cheung et al. · 2005 [cited by applicant]
US 20050249221A1 · Remi et al. · 2005 [cited by applicant]
US 20070005576A1 · Cutrell et al. · 2007 [cited by applicant]
US 20070143386A1 · Nguyen · 2007 [cited by applicant]
US 20100288157A1 · LeFebvre et al. · 2010 [cited by applicant]
US 20120151345A1 · McClements, IV · 2012 [cited by applicant]
US 20130029599A1 · Santori et al. · 2013 [cited by applicant]
US 20130042327A1 · Chow · 2013 [cited by applicant]
US 20130121282A1 · Liu · 2013 [cited by applicant]
US 20130124484A1 · Hoffman · 2013 [cited by applicant]
US 20140194657A1 · Wadhwa et al. · 2014 [cited by applicant]
US 20140280338A1 · Metz et al. · 2014 [cited by applicant]
US 20140304006A1 · Korpman et al. · 2014 [cited by applicant]
US 20140330926A1 · Nano et al. · 2014 [cited by applicant]
US 20140359035A1 · Wang et al. · 2014 [cited by applicant]
US 20150033311A1 · Seed · 2015 [cited by examiner]
US 20150199225A1 · Chen · 2015 [cited by examiner]
US 20150200919A1 · Czajkowski · 2015 [cited by examiner]
US 20150271033A1 · Srivastava et al. · 2015 [cited by applicant]
US 20150317363A1 · Manzano et al. · 2015 [cited by applicant]
US 20160070761A1 · Viel · 2016 [cited by examiner]
US 20160085594A1 · Wang · 2016 [cited by examiner]
US 20160191591A1 · Rider et al. · 2016 [cited by applicant]
US 20160234022A1 · Motika et al. · 2016 [cited by applicant]
US 20160357806A1 · Andleman · 2016 [cited by examiner]
US 20170039245A1 · Wholey, III · 2017 [cited by examiner]
US 20170109266A1 · Chee · 2017 [cited by examiner]
US 20170171165A1 · Britt et al. · 2017 [cited by applicant]
US 20170177546A1 · Heinz et al. · 2017 [cited by applicant]
US 20170230402A1 · Greenspan et al. · 2017 [cited by applicant]
US 20180046671A1 · Baba · 2018 [cited by examiner]
US 20190065683A9 · Korpman et al. · 2019 [cited by applicant]
EP 2674876A1 · 2013 [cited by applicant]
EP 2801935A1 · 2014 [cited by applicant]
WO 9843178A1 · 1998 [cited by applicant]
“Http://storm.apache.org/”, Retrieved Jan. 7, 2020, 3 pages. [cited by applicant]
“http://www.enterprisetech.com/2014/12/10/intel-rolls-iot-platform/”, Dec. 10, 2014, 3 pages. [cited by applicant]
“https://docs.microsoft.com/en-us/azure/iot-fundamentals/iot-introduction”, downloaded Apr. 8, 2020, 37 pages. [cited by applicant]
“https://opensource.com/business/15/4/guide-to-apache-spark-streaming”, Apr. 23, 2015, 7 pages. [cited by applicant]
“https://www.IBM.com/support/knowledgecenter/SSCRJU_4.0.0/com.ibm.streams.welcome.doc/doc/kc-homepage. html” Retrieved Apr. 8, 2020, 3 pages. [cited by applicant]
Aazam et al., “Fog Computing and Smart Gateway Based Communication for Cloud of Things”, 2014 International Conference on Future Internet of Things and Cloud, Retrieved on Jun. 29, 2016, 7 pages. [cited by applicant]
AIM Autonomous Intersection Management, University of Texas at Austin, http://www.cs.utexas.edu/˜aim/, retrieved Apr. 8, 2020, 6 pages. [cited by applicant]
Campbell, “How to Process Google Data in Real Time with Azure Stream Analytics”, BlueGranite business Insights, Feb. 26, 2015, 1 pages. [cited by applicant]
Guillaume Leduc, JRC Technical Notes, “Road Traffic Data: Collection Methods and Applications”, JRC 47967-2008, 55 pages. [cited by applicant]
OneM2M Technical Specification TS-0001 V2.3.0, “Functional Architecture”, Aug. 2015, 352 pages. [cited by applicant]
OneM2M Technical Specification, TS-0007 V0.3.0, Service Component Architecture, Jun. 2014, 105 pages. [cited by applicant]
Satyanarayanan, et al., “Edge Analytics in the Internet of Things”, Apr.-Jun. 2015, 8 pages. [cited by applicant]