IP Library Granted Patent US 11,677,812
Granted Patent B2
US 11,677,812 · App. 17/747,020 · Granted Jun 13, 2023

Lightweight IoT information model

Inventors: Guang Lu (Thornhill, CA); Dale N. Seed (Allentown, PA); Lijun Dong (San Diego, CA); Quang Ly (North Wales, PA); Shamim Akbar Rahman (Cote St. Luc, CA); Chonggang Wang (Princeton, NJ)
Assignee: Convida Wireless, LLC
H04L67/10H04W4/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,677,812
App. No.
17/747,020
Granted
Jun 13, 2023
Kind
B2
Abstract

A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Claims (36)

1. A first network apparatus in a RESTful architecture, the first network apparatus comprising:

a memory comprising executable instructions; and

a processor that, when executing the executable instructions, effectuates operations comprising:

receiving, from a second network apparatus, a RESTful request to create at least one application-specific instance of an information model object in the RESTful architecture, wherein the request comprises:

at least one information model object description in the RESTful architecture, wherein the at least one information model object description is application-specific and is provided by a first entity executing on the second network apparatus; and

wherein the at least one information model object description comprises a description of a uniquely addressable resource; and

wherein the description comprises one or more characteristics, states, statuses, or other attributes of the information model object;

creating the at least one application-specific instance of the information model object based on the at least one information model object description received from the second network apparatus; and

transmitting a response to the second network apparatus comprising an identifier for the at least one application-specific instance of the information model object,

wherein the at least one application-specific instance of the information model object is accessible via RESTful requests issued by other entities implemented on other network apparatuses.

2. The first network apparatus of claim 1 , wherein the operations further comprise restricting use of the at least one application-specific instance of the information model object by only the first entity executing on the second network apparatus.

3. The first network apparatus of claim 1 , wherein the operations further comprise transmitting a response to the second network apparatus via the communication network, wherein the response comprises a confirmation of the creation of the at least one application specific instance of the information model object.

4. The first network apparatus of claim 1 , wherein the request to create the application-specific instance of the information model object further comprises one or more object creation rules, and wherein creating the at least one application-specific instance of the information model object comprises creating the at least one application-specific instance of the information model object in accordance with the one or more object creation rules.

5. The first network apparatus of claim 1 , wherein the operations further comprise transmitting a response to the second network apparatus comprising an attribute that identifies a type of the at least one application-specific instance of the information model object.

6. The first network apparatus of claim 1 , wherein the operations further comprise advertising the at least one application-specific instance of the information model object to another network apparatus.

7. The first network apparatus of claim 6 , wherein the operations further comprise sending to the another network apparatus the at least one application-specific instance of the information model object in response to a retrieve message received from the another network apparatus.

8. The first network apparatus of claim 1 , wherein the information model object is defined in a service layer of the network.

9. The first network apparatus of claim 8 , wherein the service layer comprises common service layer functions for M2M service.

10. The first network apparatus of claim 9 , wherein the common service layer functions are defined according to ETSI or oneM2M standards.

11. A method for a first entity in a network, the method comprising:

receiving, from a second network apparatus, a RESTful request to create at least one application-specific instance of an information model object in a RESTful architecture, wherein the request comprises:

at least one information model object description in the RESTful architecture, wherein the at least one information model object description is application-specific and is provided by a first entity executing on the second network apparatus; and

wherein the at least one information model object description comprises a description of a uniquely addressable resource; and

wherein the description comprises one or more characteristics, states, statuses, or other attributes of the information object;

creating the at least one application-specific instance of the information model object based on the at least one information model object description received from the second network apparatus; and

transmitting a response to the second network apparatus comprising an identifier for the at least one application-specific instance of the information model object,

wherein the at least one application-specific instance of the information model object is accessible via RESTful requests issued by other entities implemented on other network apparatuses.

12. The method of claim 11 , further comprising restricting use of the at least one application-specific instance of the information model object by only the first entity executing on the second network apparatus.

13. The method of claim 11 , further comprising transmitting a response to the second network apparatus via the communication network, wherein the response comprises a confirmation of the creation of the at least one application-specific object instance of the information model object.

14. The method of claim 11 , further comprising transmitting a response to the second network apparatus comprising an identifier for the at least one application-specific instance of the information model object.

15. The method of claim 11 , wherein the request to create the application-specific instance of the information model object further comprises one or more object creation rules, and wherein creating the at least one application-specific instance of the information model object comprises creating the at least one application-specific instance of the information model object in accordance with the one or more object creation rules.

16. The method of claim 11 , further comprising advertising the at least one application-specific instance of the information model object to another network apparatus.

17. The method of claim 16 , further comprising sending to the another network apparatus the at least one application-specific instance of the information model object in response to a retrieve message received from the another network apparatus.

18. The method of claim 11 , wherein the information model object is defined in a service layer of the network.

19. The method of claim 18 , wherein the service layer comprises common service layer functions for M2M service.

20. The method of claim 19 , wherein the common service layer functions are defined according to ETSI or oneM2M standards.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2025
From: CONVIDA WIRELESS,LLC
To: IPLA HOLDINGS INC.
Reel/Frame 073903/0733 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 27, 2022
From: LU, GUANG; SEED, DALE N.; DONG, LIJUN; LY, QUANG; RAHMAN, SHAMIM AKBAR; WANG, CHONGGANG
To: CONVIDA WIRELESS, LLC
Reel/Frame 060039/0029 →
Continuity (5)
Continuation 17469078 · Sep 8, 2021
Continuation 16875245 · May 15, 2020
Continuation 14283905 · May 21, 2014
Provisional Application 61825640 · May 21, 2013
Related Publication 20220279039A1 · Sep 1, 2022
Cited By (1)
US 12,267,386