Mechanisms for an intelligent service layer request abstraction service

Patent metadata

Field	Value
Publication number	US-12413649-B2
Application number	US-202418758951-A
Country	US
Kind code	B2
Filing date	Jun 28, 2024
Priority date	May 7, 2018
Publication date	Sep 9, 2025
Grant date	Sep 9, 2025

Abstract

Systems and methods are described herein to automate managing of service layer operations comprised of multiple elementary operations and offloading the burden of performing such multi-step operations from a requesting entity to the service layer. A Request Abstraction Service (RAS) is described herein for the autonomous execution of such multi-step operations. Methods and apparatuses are also described herein for a service layer framework for integrating generic and functional user interfaces as services managed by the SL on behalf of requesting entities.

First claim

The invention claimed is:

1. An apparatus comprising circuitry configured to:
receive, from a requesting entity, an abstract request targeting a URI of the apparatus and comprising a command predicate, one or more command objects, and one or more command contexts, wherein the one or more command contexts comprise context information referring to at least one of a type of resource to be operated on, a time duration applicable to the abstract request and a desired location applicable to the abstract request;
classify a word of the abstract request as a noun;
based on the noun classification, determine a service associated with the word;
determine, based on the abstract request, a sequence of one or more operations, associated with a service supporting service capabilities through a set of commands, to execute;
execute the sequence of one or more operations at the service, wherein the execution of the sequence of one or more operations comprises sending one or more requests addressed to resources of the service; and
send, to the requesting entity, one or more statuses of the executed one or more operations.

2. The apparatus of claim 1 , wherein the abstract request comprises a request message associated with the service.

3. The apparatus of claim 1 , wherein the circuitry is configured to infer, and wherein the inferring comprises:
analyzing the abstract request to determine the command predicate, the one or more command objects, and the one or more command contexts before determining the sequence of one or more operations.

4. The apparatus of claim 1 , computer-executable instructions stored in a memory of the apparatus which, when executed by a processor of the apparatus, further cause the apparatus to:
determine a keyword is present in the abstract request;
determine an operation is associated with the keyword; and
add the operation to the sequence of one or more operations to execute.

5. The apparatus of claim 1 , computer-executable instructions stored in a memory of the apparatus which, when executed by a processor of the apparatus, further cause the apparatus to:
classify a word of the abstract request as a noun; and
based on the noun classification, determine an entity associated with the word.

6. The apparatus of claim 1 , wherein the circuitry is configured to infer, and wherein the inferring comprises:
classifying a word of the abstract request as a verb; and
based on the verb classification, determining an operation associated with the word.

7. The apparatus of claim 1 , comprising computer-executable instructions stored in a memory of the apparatus, which when executed by a processor of the apparatus, further cause an entity associated with the service to:
create a resource representing the abstract request, wherein the resource comprises a command predicate, one or more command objects, and context information.

8. The apparatus of claim 7 , comprising computer-executable instructions stored in a memory of the apparatus, which when executed by a processor of the apparatus, further cause an entity associated with the service to:
receive a second abstract request targeting the resource, wherein the second abstract request comprises second context information to replace the context information; and
process the abstract request using the second context information.

9. The apparatus of claim 1 , wherein the abstract request comprises a text string.

10. The apparatus of claim 1 , wherein the one or more command contexts comprise context information for use in future abstract requests.

11. The apparatus of claim 10 , wherein the context information comprises a term and a definition associated with the term.

12. The apparatus of claim 10 , wherein the context information comprises a term and an operation associated with the term.

13. A method comprising:
receiving, from a requesting entity, an abstract request targeting a URI of an apparatus and comprising a command predicate, one or more command objects, and one or more command contexts, wherein the one or more command contexts comprise context information referring to at least one of a type of resource to be operated on, a time duration applicable to the abstract request and a desired location applicable to the abstract request;
classifying a word of the abstract request as a noun;
based on the noun classification, determining a service associated with the word;
determining, based on the abstract request, a sequence of one or more operations, associated with a service supporting service capabilities through a set of commands, to execute;
generating a set of command based on the command predicate, the one or more command objects, and the one or more command contexts, wherein the set of commands make calls to the sequence of the one or more operations;
executing the generated set of commands, wherein the execution of commands comprises sending one or more requests addressed to resources of the service; and
returning, to the requesting entity, a status indicating completion of the abstract request.

14. The method of claim 13 , further comprising:
determining a first command context of the one or more command contexts is not recognized; and
prompting the requesting entity for a definition of the command context.

15. The method of claim 13 , further comprising:
creating a resource of the abstract request to store the command predicate, the one or more command objects, and the one or more command contexts.

16. The method of claim 15 , further comprising:
receiving a request targeting the resource; and
executing the generated set of commands.

17. The method of claim 15 , further comprising:
receiving a second abstract request, wherein the second abstract request targets the resource and comprises one or more changes to be made to the abstract request; and
based on the one or more changes, modifying the resource of the abstract request.

18. The method of claim 13 , further comprising:
before executing the generated set of commands, sequencing the generated set of commands.

19. The method of claim 13 , wherein the generated set of commands are sequenced such that retrieve and discovery operations are performed before create or update operations.

20. A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by a processor of a computing device, cause the computing device to:
receive, from a requesting entity, an abstract request targeting a URI of the computing device and comprising a command predicate, one or more command objects, and one or more command contexts;
classify a word of the abstract request as a noun;
based on the noun classification, determine a service associated with the word;
determine a set of operations based of the command predicate, the one or more command objects, and the one or more command contexts, wherein the one or more command contexts comprise context information referring to at least one of a type of resource to be operated on, a time duration applicable to the abstract request and a desired location applicable to the abstract request;
execute the set of operations at a service supporting service capabilities through a set of commands, wherein the set of operations comprise sending one or more requests addressed to resources of the service; and
return, to the requesting entity, a statuses of the executed operations.

Assignees

• Interdigital Patent Holdings Inc

Inventors

• Mladin Catalina Mihaela
• Seed Dale N
• Ly Quang
• Flynn Iv William Robert
• Chen Zhuo
• Li Hongkun
• Liu Lu
• Wang Chonggang
• Ninglekhu Jiwan L

Classifications

• H04L67/565 Primary

  Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04W4/70

  Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

• H04L67/62 Primary

  Establishing a time schedule for servicing the requests · CPC title