IP Library Granted Patent US 12,541,527
Granted Patent B2
US 12,541,527 · App. 18/669,309 · Granted Feb 3, 2026

Methods for enabling data analytics service at service layer

Inventors: Xu Li (Plainsboro, NJ); Qing Li (Princeton Junction, NJ); Sneha Aman Singh (Issaquah, WA); Rocco Di Girolamo (Laval, CA); Catalina Mihaela Mladin (Hatboro, PA); Hongkun Li (Malvern, PA); Chonggang Wang (Princeton, NJ)
Assignee: IPLA HOLDINGS INC.
G06F16/2465G06F9/541G06F9/547G06F16/86G06F16/955G06F16/958G06Q30/0201H04L67/63G06F2216/03
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,541,527
App. No.
18/669,309
Granted
Feb 3, 2026
Kind
B2
Abstract

A common Data Analytics Service (DAS) at service layer is designed to use underlying existing/future data analytics technologies or tools and provide them to service layer entities that need those data analytics operations with uniform access approach. A general operation framework/interface design is used for enabling DAS and the operation details within DAS. Related procedures for interacting with DAS, including the new parameters in service layer request/response messages can be used.

Claims (28)

1 . A method performed by a service entity for a service supporting service capabilities through a set of application programming interfaces (APIs) in a network, the method comprising:

receiving, from an application entity via the network, a request to perform a data analytics operation on data, the request identifying a type of data analytics capability capable of performing the requested data analytics operation, the request further comprising one or more parameters required by the identified type of data analytics capability, the required parameters being specified in a profile defined for the identified type of data analytics capability, wherein the profile defined for the identified type of data analytics capability further comprises a mapping to an interface of a data analytics capability of the identified type;

determining a first data host entity of a plurality of data host entities in the service storing the data on which the requested data analytics operation is to be performed, wherein each of the plurality of data host entities is a uniquely addressable element in resource oriented architecture via RESTful methods using uniform resource identifiers (URIs);

transmitting a message corresponding to the received request to a second service entity for the service in the network, the second service entity for the service having a closer proximity to the first data host entity, and wherein the second service entity is configured to request the data from the first data host entity; and

receiving, from the second service entity, a response to the requested data analytics operation on the data, wherein results of the requested data analytics operation are available for the application entity via the set of APIs.

2 . The method of claim 1 , wherein the received request further comprises the data on which the data analytics operation is to be performed.

3 . The method of claim 1 , further comprising retrieving, based on the URIs, the data on which the data analytics operation is to be performed.

4 . The method of claim 1 , wherein the method is performed by a data analytics service of the service.

5 . The method of claim 4 , wherein the data analytics service interfaces with a plurality of different types of analytics capabilities.

6 . The method of claim 5 , further comprising converting, based on the profile of the identified type of data analytics capability, the received request into a request that conforms to an application programming interface of a data analytics capability of the identified type, wherein the converting is performed by an interface converter of the data analytics service that interfaces with the data analytics capability of the identified type.

7 . The method of claim 1 , wherein the requested data analytics operation is performed by the identified type of data analytics capability in accordance with a subscription associated with the requested data analytics operation.

8 . The method of claim 1 , wherein the service is provided as a middleware service for IoT services.

9 . The method of claim 8 , wherein the middleware service is a service layer located on top of network protocol stacks.

10 . The method of claim 9 , wherein the service layer is defined according to ETSI/oneM2M standards.

11 . An apparatus comprising one or more processors and one or more memories, the apparatus further comprising computer-executable instructions stored in the one or more memories of the apparatus which, when executed by the one or more processors of the apparatus, cause the apparatus to perform, at a service supporting service capabilities through a set of application programming interfaces (APIs) in a network, operations comprising:

receiving, from an application entity via the network, a request to perform a data analytics operation on data, the request identifying a type of data analytics capability capable of performing the requested data analytics operation, the request further comprising one or more parameters required by the identified type of data analytics capability, the required parameters being specified in a profile defined for the identified type of data analytics capability, wherein the profile defined for the identified type of data analytics capability further comprises a mapping to an interface of a data analytics capability of the identified type;

determining a first data host entity of a plurality of data host entities in the service storing the data on which the requested data analytics operation is to be performed, wherein each of the plurality of data host entities is a uniquely addressable element in resource oriented architecture via RESTful methods using uniform resource identifiers (URIs);

transmitting a message corresponding to the received request to a second service entity for the service in the network, the second service entity for the service having a closer proximity to the first data host entity, and wherein the second service entity is configured to request the data from the first data host entity; and

receiving, from the second service entity, a response to the requested data analytics operation on the data, wherein results of the requested data analytics operation are available for the application entity via the set of APIs.

12 . The apparatus of claim 11 , wherein the received request further comprises the data on which the data analytics operation is to be performed.

13 . The apparatus of claim 11 , wherein the computer-executable instructions further cause the apparatus to retrieve, based on the URIs, the data on which the data analytics operation is to be performed.

14 . The apparatus of claim 11 , wherein the computer-executable instructions further cause the apparatus to implement a data analytics service of the service of the network, which data analytics service performs said operations.

15 . The apparatus of claim 14 , wherein the data analytics service interfaces with a plurality of different types of analytics capabilities.

16 . The apparatus of claim 15 , wherein the computer-executable instructions further cause the apparatus to convert, based on the profile of the identified type of data analytics capability, the received request into a request that conforms to an application programming interface of a data analytics capability of the identified type, wherein the converting is performed by an interface converter of the data analytics service that interfaces with the data analytics capability of the identified type.

17 . The apparatus of claim 11 , wherein the requested data analytics operation is performed at the second service entity for the service by the identified type of data analytics capability in accordance with a subscription associated with the requested data analytics operation.

18 . The apparatus of claim 11 , wherein the service is provided as a middleware service for IoT services.

19 . The apparatus of claim 18 , wherein the middleware service is a service layer located on top of network protocol stacks.

20 . The apparatus of claim 19 , wherein the service layer is defined according to ETSI/oneM2M standards.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2025
From: CONVIDA WIRELESS, LLC
To: IPLA HOLDINGS INC.
Reel/Frame 072388/0091 →
Continuity (3)
Continuation 16096498
Provisional Application 62326881 · Apr 25, 2016
Related Publication 20240394270A1 · Nov 28, 2024
References Cited (22)
US 20120029710A1 · Dodderi · 2012 [cited by examiner]
US 20150370872A1 · Raghavan · 2015 [cited by examiner]
US 20160112487A1 · Wang et al. · 2016 [cited by applicant]
US 20230401588A1 · Levin · 2023 [cited by examiner]
CN 102187328A · 2011 [cited by applicant]
CN 102523246A · 2012 [cited by applicant]
CN 104937552A · 2015 [cited by applicant]
CN 105430494A · 2016 [cited by applicant]
CN 105493525A · 2016 [cited by applicant]
KR 1020150066474A · 2015 [cited by applicant]
KR 101696101B1 · 2017 [cited by applicant]
KR 101812398B1 · 2017 [cited by applicant]
WO 2014190186A1 · 2014 [cited by applicant]
WO 2015196177A1 · 2015 [cited by applicant]
WO 2016044581A1 · 2016 [cited by applicant]
“https://www.quora.com/What-is-the-architecture-of-Google-Analytics”, Downloaded on Apr. 8, 2020, 3 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-0001 V2.8.0, “Functional Architecture”, Mar. 2016, 430 pages. [cited by applicant]
OneM2M Technical Specification TS-0007 V0.3.0, “Service Component Architecture”, Jun. 2014, 105 pages. [cited by applicant]
SAP HANA Blog, “Big Data for Enterprise Customers Leveraging Hadoop Distributed File System and SAP Real Time Data Platform”, Aug. 29, 2012, 5 pages. [cited by applicant]
Sultan R.A et al., “A spatial incremental relaying-based user transparent ARQ protocol,” 2013 IEEE 14th Workshop on Signal Processing Advances in Wireless Communications (SPAWC), 2013, pp. 550-554. [cited by applicant]
Yingjie Hong et al., “TS0001-V2.8.0—Functional Architecture”, ARC-2016-0215-TS-000I_FUNCTIONAL_ARCHITECT URE-V2_8_0.ZIP, ONEM2M, vol. WG2—Architecture, ARC, no. conference = ARC 22.1, Mar. 31, 2016-Mar. 31, 2016 Mar. 29… [cited by applicant]