IP Library Granted Patent US 12,206,741
Granted Patent B2
US 12,206,741 · App. 18/487,164 · Granted Jan 21, 2025

Profile based content and services

Inventors: William Robert Flynn, IV (Schwenksville, PA); Dale N. Seed (Allentown, PA); Quang Ly (North Wales, PA); Catalina Mihaela Mladin (Hatboro, PA); Zhuo Chen (Claymont, DE); Rocco Di Girolamo (Laval, CA); Shamim Akbar Rahman (Cote St. Luc, CA)
Assignee: Convida Wireless, LLC
H04L67/30H04L67/12H04L67/51H04L69/08H04W4/50H04W4/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,206,741
App. No.
18/487,164
Granted
Jan 21, 2025
Kind
B2
Abstract

Profile based services and content can assist with the backward and forward compatibility of conventional service layers or the like. Using a profile to manage content and access to services offered may reduce the overhead or processing associated with providing those value added services by service layers.

Claims (33)

1. An apparatus for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the apparatus comprising circuitry configured to:

receive a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes;

store the profile in a resource that can be identified by uniform resource identifier (URI) in the service;

receive a second message from a client application for a target application;

determine a list of applicable profiles stored in one or more resources of the service for modifying the second message; and

apply the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.

2. The apparatus of claim 1 , wherein creator of each of the profiles in the list of applicable profiles is checked for permission to modify the second message before the profile is applied to the second message.

3. The apparatus of claim 1 , further comprising circuitry configured to perform a consistency check to ensure the profiles do not conflict with each other if more than one applicable profile is identified.

4. The apparatus of claim 1 , further comprising circuitry configured to revert operations if an error occurs when processing the updated or new message that is compatible.

5. The apparatus of claim 1 , wherein the one or more modification actions indicated by the profile comprise at least one of updating, adding, or removing of one or more attributes.

6. The apparatus of claim 5 , wherein the service is defined as a service layer according to ETSI/oneM2M standards, and the profile is defined as part of the service layer according to the ETSI/oneM2M standards.

7. A method for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the method comprising:

receiving a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes;

storing the profile in a resource that can be identified by uniform resource identifier (URI) in the service;

receiving a second message from a client application for a target application;

determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and

applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.

8. The method of claim 7 , wherein creator of each of the profiles in the list of applicable profiles is checked for permission to modify the second message before the profile is applied to the second message.

9. The method of claim 7 , further comprising performing a consistency check to ensure the profiles do not conflict with each other if more than one applicable profile is identified.

10. The method of claim 7 , further comprising reverting steps if an error occurs when processing the updated or the new message that is compatible.

11. The method of claim 7 , wherein the one or more modification actions indicated by the profile comprise at least one of updating, adding, or removing of one or more attributes.

12. The method of claim 11 , wherein the service is defined as a service layer according to ETSI/oneM2M standards, and the profile is defined as part of the service layer according to the ETSI/oneM2M standards.

13. A computer readable storage medium for a service supporting service capabilities through a set of Application Programming Interfaces (APIs), the service being provided as middleware between application protocols and a plurality of applications, the computer readable storage medium storing computer executable instructions that when executed by one or more computing devices cause said one or more computing devices to effectuate operations comprising:

receiving a first RESTful message comprising a profile for modifying messages in the service, wherein the profile indicates which types of messages the profile applies to, one or more names of attributes to be modified, and one or more modification actions to be performed on the attributes;

storing the profile in a resource that can be identified by uniform resource identifier (URI) in the service;

receiving a second message from a client application for a target application;

determining a list of applicable profiles stored in one or more resources of the service for modifying the second message; and

applying the list of applicable profiles to the second message to perform the one or more modification actions on attributes of the second message and create an updated or a new message that is compatible with the target application.

14. The computer readable storage medium of claim 13 , wherein creator of each of the profiles in the list of applicable profiles is checked for permission to modify the second message before the profile is applied to the second message.

15. The computer readable storage medium of claim 13 , wherein a consistency check is performed to ensure the profiles do not conflict with each other if more than one applicable profile is identified.

16. The computer readable storage medium of claim 13 , wherein the operations are reverted if an error occurs when processing the updated or the new message that is compatible.

17. The computer readable storage medium of claim 13 , wherein the one or more modification actions specified by the profile comprise at least one of updating, adding, or removing of one or more attributes.

18. The computer readable storage medium of claim 13 , wherein the service is defined as a service layer according to ETSI/oneM2M standards, and the profile is defined as part of the service layer according to the ETSI/oneM2M standards.

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 (5)
Continuation 18069422 · Dec 21, 2022
Continuation 17103025 · Nov 24, 2020
Continuation 16339390
Provisional Application 62405018 · Oct 6, 2016
Related Publication 20240129373A1 · Apr 18, 2024
References Cited (22)
US 10021549B2 · Lu et al. · 2018 [cited by applicant]
US 10887420B2 · Flynn et al. · 2021 [cited by applicant]
US 20130103842A1 · Seed et al. · 2013 [cited by applicant]
US 20140007076A1 · Kim et al. · 2014 [cited by applicant]
US 20140215043A1 · Ryu et al. · 2014 [cited by applicant]
US 20140330952A1 · Starsinic et al. · 2014 [cited by applicant]
US 20140359131A1 · Seed et al. · 2014 [cited by applicant]
US 20150019717A1 · Li et al. · 2015 [cited by applicant]
US 20150055557A1 · Dong et al. · 2015 [cited by applicant]
US 20150193223A1 · Cardamore · 2015 [cited by applicant]
US 20160007138A1 · Palanisamy et al. · 2016 [cited by applicant]
US 20160127312A1 · Foti · 2016 [cited by applicant]
US 20160277391A1 · Choyi et al. · 2016 [cited by applicant]
US 20180018363A1 · Lin et al. · 2018 [cited by applicant]
US 20180109453A1 · Dong · 2018 [cited by examiner]
US 20180225354A1 · Li · 2018 [cited by examiner]
US 20180288098A1 · Wang · 2018 [cited by examiner]
WO 2015191965A2 · 2015 [cited by applicant]
OneM2M TS-0001 V1.13.1, Technical Specification, “Functional Architecture” Feb. 29, 2016, 310 pages. [cited by applicant]
OneM2M TS-0001 V2.3.0, Technical Specification, “Functional Architecture”, Aug. 2015, 352 pages. [cited by applicant]
OneM2M TS-0004 V-2014-08, Technical Specification, “oneM2M Service Layer Protocol Core Specification”, Aug. 2014, 176 pages. [cited by applicant]
OneM2M TS-0009 V1.0.1 Technical Specification, “HTTP Protocol Binding TS”, Jan. 2015, 13 pages. [cited by applicant]