IP Library Granted Patent US 11,985,195
Granted Patent B2
US 11,985,195 · App. 16/756,154 · Granted May 14, 2024

Methods to enable data continuity service

Inventors: Rocco Di Girolamo (Laval, CA); Quang Ly (North Wales, PA); Dale N. Seed (Allentown, PA); Catalina Mihaela Mladin (Hatboro, PA); William Robert Flynn, IV (Schwenksville, PA); Shoshana Loeb (Philadelphia, PA); Zhuo Chen (Claymont, DE); Michael F. Starsinic (Newtown, PA)
Assignee: Convida Wireless, LLC
H04L67/125G06F9/5011H04L67/563H04W4/70
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 11,985,195
App. No.
16/756,154
Granted
May 14, 2024
Kind
B2
Abstract

A Data Producer may be configured to negotiate and initiate a Data Continuity service with an M2M/IoT system. This service may be for specific data sets or all data sets generated by the Data Producer. The M2M/IoT system may be configured to autonomously decide to start a Data Continuity Service for a data set of a Data Producer. The Data Producer may interact directly with an Aggregator SL to store its aggregated data set, and may also be configured to update and delete entries in this data set and start a data service on this aggregated data set. A Local SL may be configured to manage all interactions with an Aggregator SL, and the Local SL may be configured to retarget requests from the Data Producer to the Aggregator SL, including a request to start a data service on the aggregated data set.

Claims (34)

1. A method performed in a machine-to-machine/internet of things (M2M/IoT) system by a first service layer entity implemented on an apparatus of a communications network, the method comprising:

receiving a data continuity service request, wherein the data continuity service request comprises information associated with a computing device;

determining, based on the data continuity service request, to configure a second service layer entity implemented on another apparatus of the communications network for performing one or more data operations on data associated with the computing device;

configuring the second service layer entity for performing the one or more data operations on the data associated with the computing device;

receiving, from the computing device, a request to perform, by the first service layer entity, at least one data operation, wherein the request to perform the at least one data operation identifies a resource associated with the first service layer entity; and

retargeting, to the second service layer entity, the request to perform the at least one data operation on at least a portion of the data.

2. The method of claim 1 , further comprising:

sending, to the computing device, an indication that at least a portion of the data is stored at the second service layer entity.

3. The method of claim 2 , wherein the indication that at least a portion of the data is stored at the second service layer entity comprises an identifier of the second service layer entity.

4. The method of claim 1 , further comprising:

receiving, from the second service layer entity, a response indicating that the at least one data operation on the at least the portion of the data has been performed; and

sending, to the computing device, the indication that the at least one data operation on the at least the portion of the data has been performed.

5. The method of claim 1 , wherein the computing device is pre-configured with information associated with the resource.

6. The method of claim 1 , further comprising sending, based on configuring the second service layer entity for performing the one or more data operations on the data associated with the computing device, information associated with the resource.

7. The method of claim 1 , wherein the request to perform the at least one data operation comprises a request to perform one or more of a create, update, retrieve, or delete operation associated with the data.

8. An apparatus in a machine-to-machine/internet of things (M2M/IoT) system comprising a processor and a memory, the memory storing computer-executable instructions which, when executed by the processor, implement a first service layer entity of a communications network and cause the first service layer entity to perform operations comprising:

receiving a data continuity service request, wherein the data continuity service request comprises information associated with a computing device;

determining, based on the data continuity service request, to configure a second service layer entity implemented on another apparatus of the communications network for performing one or more data operations on the data associated with the computing device;

configuring the second service layer entity for performing the one or more data operations on the data associated with the computing device;

receiving, from the computing device, a request to perform, by the first service layer entity, at least one data operation, wherein the request to perform the at least one data operation identifies a virtual resource associated with the first service layer entity; and

retargeting, to the second service layer entity, the request to perform the at least one data operation on at least a portion of the data.

9. The apparatus of claim 8 , wherein the instructions when executed further cause the first service layer entity to perform operations comprising:

sending, to the computing device, an indication that at least a portion of the data is stored at the second service layer entity.

10. The apparatus of claim 9 , wherein the indication that at least a portion of the data is stored at the second service layer entity comprises an identifier of the second service layer entity.

11. The apparatus of claim 8 , wherein the instructions when executed further cause the first service layer entity to perform operations comprising:

receiving, from the second service layer entity, a response indicating that the at least one data operation on the at least the portion of the data has been performed; and

sending, to the computing device, the indication that the at least one data operation on the at least the portion of the data has been performed.

12. The apparatus of claim 8 , wherein the computing device is pre-configured with information associated with the resource.

13. The apparatus of claim 8 , wherein the instructions when executed further cause the first service layer entity to perform operations comprising sending, based on configuring the second service layer entity for performing the one or more data operations on the data associated with the computing device, information associated with the resource.

14. The apparatus of claim 8 , wherein the request to perform the at least one data operation comprises a request to perform one or more of a create, update, retrieve, or delete operation associated with the data.

15. The method of claim 1 , wherein the service layer entity supports service capabilities through a set of Application Programming Interfaces (APIs).

16. The method of claim 15 , wherein functions of the service layer entity are defined according to the European Telecommunications Standards Institute (ETSIs)/OneM2M.

17. The apparatus of claim 8 , wherein the service layer entity supports service capabilities through a set of Application Programming Interfaces (APIs).

18. The apparatus of claim 17 , wherein functions of the service layer entity are defined according to the European Telecommunications Standards Institute (ETSI)/OneM2M.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2025
From: CONVIDA WIRELESS, LLC
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 071773/0735 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 15, 2020
From: DI GIROLAMO, ROCCO; LY, QUANG; SEED, DALE N; MLADIN, CATALINA MIHAELA; FLYNN, WILLIAM ROBERT, IV; LOEB, SHOSHANA; CHEN, ZHUO; STARSINIC, MICHAEL F.
To: CONVIDA WIRELESS, LLC
Reel/Frame 052400/0653 →
Continuity (2)
Provisional Application 62575990 · Oct 23, 2017
Related Publication 20200244741A1 · Jul 30, 2020