IP Library Granted Patent US 12,425,458
Granted Patent B2
US 12,425,458 · App. 18/742,301 · Granted Sep 23, 2025

Automated service enrollment in a machine-to-machine communications network

Inventors: Dale N. Seed (Allentown, PA); William Robert Flynn, IV (Schwenksville, PA); Quang Ly (North Wales, PA); Rocco Di Girolamo (Laval, CA); Zhuo Chen (Claymont, DE); Catalina Mihaela Mladin (Hatboro, PA); Shoshana Loeb (Philadelphia, PA); Mahmoud Watfa (Saint Leonard, CA); Michael F. Starsinic (Newtown, PA); Vinod Kumar Choyi (Conshohocken, PA)
Assignee: Convida Wireless, LLC
H04L65/1073H04L67/303H04W4/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 12,425,458
App. No.
18/742,301
Granted
Sep 23, 2025
Kind
B2
Abstract

IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Claims (46)

1. An apparatus comprising one or more processors and one or more memories, the apparatus further including 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 provide a service providing one or more applications with service capabilities through a set of application programming interfaces (APIs) and underlying network interfaces in a communications network and cause the service to:

receive a RESTful request to create an electronic profile comprising information associated with one or more network devices, the information comprising at least an associated identifier of each of the one or more network devices and a data control policy, for each of the one or more network devices, comprising a schema definition of data that each network device of the one or more network devices is allowed to store within one or more data storage resources of the service;

create one or more resources and store within the one or more resources the information, including the associated identifier of each of the one or more network devices, and the associated data control policy of each of the one or more network devices;

send a RESTful response indicating whether the one or more resources are successfully created to store the information;

receive, from a requesting network device connected to the communications network, an electronic request to perform an operation on the one or more data storage resources of the service, the request comprising a first identifier of the requesting network device and the one or more data storage resources;

determine, based on the information, that the first identifier of the requesting network device matches a particular associated identifier of one of the one or more network devices; and

determine that a type of data included in the request matches a schema definition of the requesting network device, and based on the determination to store the data within the one or more data storage resources.

2. The apparatus of claim 1 , wherein the data control policy further comprises a limit on the maximum age that a device can configure in the one or more data storage resources.

3. The apparatus of claim 1 , wherein the electronic profile further comprises at least one of: one or more authorized users; one or more selected service enrollment electives; one or more specified access privileges; and one or more service enrollment lifetimes.

4. The apparatus of claim 1 , wherein the computer-executable instructions further cause the service to:

determine the associated identifier of the requesting network device; and

prevent the requesting network device from performing the operation.

5. The apparatus of claim 1 , wherein the computer-executable instructions further cause the service to:

create one or more access control policies based on one or more access control privileges defined in the electronic profile; link the access control policies to resources created by the requesting network device; and determine a plurality of devices allowed to access these resources based on the privileges defined in these access control policies.

6. The apparatus of claim 1 , wherein the computer-executable instructions further cause the service to:

create one or more access control policies based on one or more access control privileges defined in the electronic profile;

link the access control policies to resources created by the requesting network device; and

determine a plurality of users allowed to access these resources based on the privileges defined in these access control policies.

7. The apparatus of claim 1 , wherein the computer-executable instructions further cause the service to:

create one or more data control policies based on one or more data control privileges defined in the electronic profile;

link the one or more data control policies to the one or more resources created by the requesting network device; and

determine at least one of a maximum rate of requests, maximum number of child resource instances or a maximum number of bytes allowed to be stored in a resource, based on the one or more data control policies.

8. The apparatus of claim 1 , wherein the computer-executable instructions further cause the service to:

create one or more data control policies based on one or more data control privileges defined in the electronic profile;

link the one or more data control policies to the one or more resources created by the requesting network device; and

determine one or more data schemas allowed to be stored in a resource based on one or more data control policies.

9. The apparatus of claim 1 , wherein the electronic profile is received from an enrollment function in the communications network.

10. The apparatus of claim 1 , wherein the service is in a service layer for IoT services.

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

12. The apparatus of claim 1 , wherein each of the one or more resources is a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods.

13. A method for a service providing one or more applications with service capabilities through a set of application programming interfaces (APIs) and underlying network interfaces in a communications network, comprising:

receiving an electronic profile comprising information associated with one or more network devices, the information comprising at least an associated identifier of each of the one or more network devices and a data control policy, for each of the one or more network devices, comprising a schema definition of data that each network device of the one or more network devices is allowed to store within one or more data storage resources of the service;

creating one or more resources and store within the one or more resources the information, including the associated identifier of each of the one or more network devices, and the associated data control policy of each of the one or more network devices;

send a RESTful response indicating whether the one or more resources are successfully created to store the information;

receiving, from a requesting network device connected to the communications network, an electronic request to perform an operation on the one or more data storage resources of the service, the request comprising a first identifier of the requesting network device and the one or more data storage resources;

determining, based on the information, that the first identifier of the requesting network device matches a particular associated identifier of one of the one or more network devices; and

determining that a type of data included in the request matches a schema definition of the requesting network device, and based on the determination store the data within the one or more data storage resources.

14. The method of claim 13 , wherein the data control policy further comprises a limit on the maximum age that a device can configure in the one or more data storage resources.

15. The method of claim 13 , wherein the electronic profile further comprises at least one of: one or more authorized users; one or more selected service enrollment electives; one or more specified access privileges; and one or more service enrollment lifetimes.

16. The method of claim 13 , wherein the method further comprising:

determining the associated identifier of the requesting network device; and

preventing the requesting network device from performing the operation.

17. The method of claim 13 , wherein the electronic profile is received from an enrollment function in the communications network.

18. The method of claim 13 , wherein the service is in a service layer for IoT services.

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

20. The method of claim 13 , wherein each of the one or more resources is a uniquely addressable element in a Resource Oriented Architecture (ROA) having representation that can be manipulated via RESTful methods.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2025
From: CONVIDA WIRELESS, LLC
To: IPLA HOLDINGS INC.
Reel/Frame 072388/0091 →
Continuity (5)
Continuation 18312616 · May 5, 2023
Continuation 17578521 · Jan 19, 2022
Continuation 16644332
Provisional Application 62556161 · Sep 8, 2017
Related Publication 20240414213A1 · Dec 12, 2024
References Cited (48)
US 10448449B2 · Aravamudhan et al. · 2019 [cited by applicant]
US 10637957B2 · Shantharam et al. · 2020 [cited by applicant]
US 10812345B2 · Seed et al. · 2020 [cited by applicant]
US 10887420B2 · Flynn et al. · 2021 [cited by applicant]
US 11265353B2 · Seed et al. · 2022 [cited by applicant]
US 11683353B2 · Seed et al. · 2023 [cited by applicant]
US 11997160B2 · Lu · 2024 [cited by examiner]
US 12041097B2 · Seed · 2024 [cited by examiner]
US 20060235973A1 · McBride et al. · 2006 [cited by applicant]
US 20110307694A1 · Broustis et al. · 2011 [cited by applicant]
US 20140289366A1 · Choi et al. · 2014 [cited by applicant]
US 20160227371A1 · Wang et al. · 2016 [cited by applicant]
US 20160277391A1 · Choyi et al. · 2016 [cited by applicant]
US 20160302069A1 · Kim et al. · 2016 [cited by applicant]
US 20170187703A1 · Enrique Salpico · 2017 [cited by applicant]
US 20180176326A1 · Shantharam et al. · 2018 [cited by applicant]
US 20190021121A1 · Aravamudhan et al. · 2019 [cited by applicant]
US 20230275956A1 · Lu · 2023 [cited by examiner]
CN 1855817A · 2006 [cited by applicant]
CN 102907068A · 2013 [cited by applicant]
CN 104104528A · 2014 [cited by applicant]
CN 107005571A · 2017 [cited by applicant]
EP 2523421A1 · 2012 [cited by applicant]
JP 2006309737A · 2006 [cited by applicant]
JP 2009003700A · 2009 [cited by applicant]
JP 2012533254A · 2012 [cited by applicant]
JP 2013537729A · 2013 [cited by applicant]
WO 2010088075A1 · 2010 [cited by applicant]
WO 2015080461A1 · 2015 [cited by applicant]
WO 2016049096A1 · 2016 [cited by applicant]
WO 2016109473A1 · 2016 [cited by applicant]
WO 2016109479A1 · 2016 [cited by applicant]
WO 2017004391A1 · 2017 [cited by applicant]
WO 2017040749A1 · 2017 [cited by applicant]
Datta et al., “Search engine based resource discovery framework for Internet of Things”, IEEE 4th Global Conference on Consumer Electronics (GCCE), Feb. 4, 2016, pp. 83-85. [cited by applicant]
ETSI 102 690 V2.0.13 Technical Specification, “Machine-to-Machine Communications (M2M); Functional Architecture”, May 2013, 328 pages. [cited by applicant]
Ian Deakin et al., “Presentation of the AppID Registry Function” REQ-2017-0044, (http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=22728), retrieved on May 7, 2017, 18 pages. [cited by applicant]
Nec et al: “Updated the CREATE procedure for Application Registration”, ARC-2014-0048-UPDATE-CREATE-Registration.DOC, ONEM2M, Jan. 21, 2014, pp. 1-8. [cited by applicant]
NEC, Cisco, Change Request, WG2, TP9, “Modification to the CREATE Procedure for Accommodating Registration”, Jan. 2014, 8 pages. [cited by applicant]
OMA Open Mobile Alliance, “Lightweight Machine to Machine Technical Specification Candidate Version 1.0”, Dec. 2013, 104 pages. [cited by applicant]
OneM2M Technical Report, TR-0048-V0.0.3, Shelby, et al., “oneM2M App-ID Registry Function”, Dec. 2017, 29 pages. [cited by applicant]
OneM2M Technical Specification TS-0001-V3.5.0, “Functional Architecture”, Apr. 2017, 461 pages. [cited by applicant]
OneM2M Technical Specification TS-0001-V3.7.0, “Function Architecture,” Aug. 16, 2017, 536 pages. [cited by applicant]
OneM2M Technical Specification TS-0003 V3.0.0, “Security Solutions”, Nov. 2016, 195 pages. [cited by applicant]
OneM2M Technical Specification, TS-0032 V0.0.4, “MAF and MEF Interface Specification”, Apr. 2017, 32 pages. [cited by applicant]
OneM2M-TS-0001 oneM2M Functional Architecture-V3.7.0, Jul. 2017. [cited by applicant]
Open Connectivity Foundation (OCF), “OIC Core Candidate Specification V1.1.0 Part 1”, Copyright 2016, 183 pages. [cited by applicant]
Shelby Kiewel et al: “Update to WI-0073/TR-0048 to move to completion”, SEC-2018-0036R02-UPDATE to WI-0073 TR-0048_TO_MOVE_TO_COMPLETION.ZIP, ONEM2M, vol. WG4—Security, Mar. 15, 2018, pp. 1-29. [cited by applicant]