IP Library Granted Patent US 12,192,295
Granted Patent B2
US 12,192,295 · App. 18/455,239 · Granted Jan 7, 2025

Enhanced restful operations

Inventors: Catalina Mihaela Mladin (Hatboro, PA); Qing Li (Princeton Junction, NJ); Rocco Di Girolamo (Laval, CA); Chonggang Wang (Princeton, NJ); William Robert Flynn, IV (Schwenksville, PA); Hongkun Li (Malvern, PA); Xu Li (Plainsboro, NJ)
Assignee: Convida Wireless, LLC
H04L67/51H04L67/02H04L67/133H04L67/566H04L67/60H04W4/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,192,295
App. No.
18/455,239
Granted
Jan 7, 2025
Kind
B2
Abstract

A batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.

Claims (28)

1. An apparatus for a service providing service capabilities to a plurality of applications via a set of application programming interfaces (APIs), the service being supported as a middleware above an application protocol layer, the apparatus comprising circuitry configured to:

receive a representational state transfer (RESTful) request that comprises a filter criteria and uniform resource identifier (URI) of a target resource hosted at the service;

check whether an originator of the RESTful request has a discovery right for the RESTful request;

query to discover one or more child resources of the target resource that matches the filter criteria, wherein each of the one or more child resources comprise the URI of the target resource and an additional path of the child resource relative to the target resource;

create a group of discovered resources that match the filter criteria, wherein the discovered resources of the group match the filter criteria;

assign a group identifier to the group; and

send a RESTful response comprising information indicative of the group.

2. The apparatus recited in claim 1 , wherein the circuitry is further configured to:

receive a request indicating a RESTful operation to be performed on the target resource, the RESTful operation being one of a CREATE request, a RETRIEVE request, an UPDATE request, or a DELETE request.

3. The apparatus recited in claim 2 , wherein the circuitry is further configured to:

perform the RESTful operation on at least one of the one or more child resources based on the group identifier.

4. The apparatus recited in claim 1 , wherein the filter criteria comprises a criteria to identify one or more resources having a matching resource attribute.

5. The apparatus recited in claim 1 , wherein the filter criteria comprises a criteria to identify one or more child resources with an attribute matching a given value.

6. The apparatus recited in claim 1 , wherein the filter criteria comprises a criteria to identify one or more resources with an attribute matching a given value as its parent resource.

7. A method for a service providing service capabilities to a plurality of applications via a set of application programming interfaces (APIs), the service being supported as a middleware above an application protocol layer, the method comprising:

receiving a representational state transfer (RESTful) request that comprises a filter criteria and uniform resource identifier (URI) of a target resource hosted at the service;

checking whether an originator of the RESTful request has a discovery right for the RESTful request;

querying to discover one or more child resources of the target resource that match the filter criteria, wherein each of the one or more child resources comprise the URI of the target resource and an additional path of the child resource relative to the target resource;

creating a group of discovered resources that match the filter criteria, wherein the discovered resources of the group match the filter criteria;

assigning a group identifier to the group; and

sending a RESTful response comprising information indicative of the group.

8. The method recited in claim 7 , wherein the method further comprising:

receiving a request indicating a RESTful operation to be performed on the target resource, the RESTful operation being one of a CREATE request, a RETRIEVE request, an UPDATE request, or a DELETE request.

9. The method recited in claim 8 , wherein the method further comprising:

performing the RESTful operation on at least one of the one or more child resources based on the group identifier.

10. The method recited in claim 7 , wherein the filter criteria comprises a criteria to identify one or more resources having a matching resource attribute.

11. The method recited in claim 7 , wherein the filter criteria comprises a criteria to identify one or more child resources with an attribute matching a given value.

12. The method recited in claim 7 , wherein the filter criteria comprises a criteria to identify one or more resources with an attribute matching a given value as its parent resource.

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 17643484 · Dec 9, 2021
Continuation 17245246 · Apr 30, 2021
Continuation 15762263
Provisional Application 62222536 · Sep 23, 2015
Related Publication 20230403334A1 · Dec 14, 2023
References Cited (35)
US 11019155B2 · Mladin et al. · 2021 [cited by applicant]
US 20020161883A1 · Matheny et al. · 2002 [cited by applicant]
US 20080201338A1 · Castro et al. · 2008 [cited by applicant]
US 20130203394A1 · Dong et al. · 2013 [cited by applicant]
US 20140215043A1 · Ryu et al. · 2014 [cited by applicant]
US 20150029894A1 · Lu · 2015 [cited by examiner]
US 20150055557A1 · Dong et al. · 2015 [cited by applicant]
US 20150055640A1 · Wang · 2015 [cited by examiner]
US 20150143472A1 · Kim · 2015 [cited by examiner]
US 20150205834A1 · Keeton et al. · 2015 [cited by applicant]
US 20150373127A1 · Ly · 2015 [cited by examiner]
US 20160085862A1 · Baldwin et al. · 2016 [cited by applicant]
US 20170099562A1 · Bhalla · 2017 [cited by applicant]
US 20170134427A1 · Hutchins · 2017 [cited by examiner]
US 20180234908A1 · Di et al. · 2018 [cited by applicant]
US 20230114953A1 · Arumugam · 2023 [cited by examiner]
CN 101957847A · 2011 [cited by applicant]
CN 102255969A · 2011 [cited by applicant]
CN 103200209A · 2013 [cited by applicant]
CN 103279573A · 2013 [cited by applicant]
CN 108141468A · 2018 [cited by applicant]
GB 2530499A · 2016 [cited by applicant]
JP 2015119901A · 2015 [cited by applicant]
TW 201404098A · 2014 [cited by applicant]
WO 2014185754A1 · 2014 [cited by applicant]
WO 2015119901A1 · 2015 [cited by applicant]
U.S. Appl. No. 17/643,484, filed Dec. 9, 2021. [cited by applicant]
U.S. Appl. No. 17/245,246, filed Apr. 30, 2021. [cited by applicant]
U.S. Appl. No. 15/762,263, filed Mar. 22, 2018. [cited by applicant]
Co-Rapporteurs et al., “OneM2M Service Layer Protocol Core Specification”, Draft TS-0004 v0.5.6, pro-2014-0402R01-draft _ Ts-0004_ V0_5_6.zip, ONEM2M, vol. WG3—Protocols, PRO, No. conference = PRO 12, Jul. 28, 2014-Aug.… [cited by applicant]
OneM2M TS-0001 V2.3.0, “Functional Architecture” Aug. 7, 2015, 352 pages. [cited by applicant]
OneM2M TS-0004 V1.0.0, “Service Layer Core Protocol Specification”, Jan. 30, 2015. [cited by applicant]
OneM2M TS-0007 V0.3.0, “Service Component Architecture”, Jun. 27, 2014, 105 pages. [cited by applicant]
OneM2M White Paper, “The Interoperability Enabler for the Entire M2M and IoT Ecosystem”, Jan. 2015, 14 pages. [cited by applicant]
Yong. C. et al., One Network Resource Sharing Architecture of Traditional Chinese Medicine Industry, World Science and Technology—Modernization of Traditional Chinese Medicine and Materia Medica, vol. 15, Issue 8, 1853-… [cited by applicant]