Request Abstraction Service for Multi-Step IoT Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT service layer operations require manual, active participation from requesting entities to perform multiple elementary operations, which is burdensome and not scalable, and there is a lack of ability to issue abstract requests that automate sequences of these operations.

Innovation Solution

A Request Abstraction Service (RAS) is introduced to automate the execution of multi-step service layer operations by interpreting higher abstraction requests and performing elementary operations autonomously, offloading the burden from the requesting entity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual active participation is required for service layer operations, then operation reliability is maintained, but operation complexity and time consumption increase

Engineering Contradiction:
Improveoperation reliabilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring service layer operations with parameters, conditions, and execution logic before they are needed. The service layer server stores operation templates that include pre-defined sequences of elementary operations, allowing automated execution without manual intervention when conditions are met, thus reducing time consumption while maintaining reliability through pre-validated operation sequences.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The service layer server performs self-service by autonomously executing service layer operations based on stored templates and current system state. The server can automatically determine when to execute operations, extract necessary parameters from context, and perform the operations without requiring active participation from requesting entities, thereby reducing time consumption while maintaining operational reliability through built-in validation and error handling.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If manual active participation is required for service layer operations, then operation control precision is maintained, but scalability deteriorates

Engineering Contradiction:
Improveoperation control precisionVSAvoidscalability
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent applies segmentation by breaking down complex service layer operations into discrete, parameterizable elementary operations that can be independently configured and executed. Each operation template is segmented into distinct components (conditions, actions, parameters) that can be individually controlled and validated, maintaining precision while enabling automated scaling across multiple operations and requesting entities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service layer server implements universality by using standardized operation templates that can serve multiple requesting entities and application scenarios. The same template framework handles diverse service layer operations through parameter configuration rather than custom implementation, enabling scalable deployment while maintaining operational precision through consistent template validation and execution logic.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Device complexity

If abstract requests are not supported, then service layer simplicity is maintained, but automation capability is lost

Engineering Contradiction:
Improveservice layer simplicityVSAvoidautomation capability
Core Design Contradiction:
Device complexityVSExtent of automation

Solution Approach 1:

The patent introduces an intermediary layer in the form of operation templates that mediate between simple request interfaces and complex service layer operations. The templates act as pre-packaged automation scripts that can be invoked through simple requests while encapsulating complex operation sequences, thus adding automation capability without significantly increasing the apparent complexity for requesting entities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service layer server uses copying by replicating operation templates across multiple execution contexts. Instead of creating complex automation logic for each requesting entity, the server copies and instantiates pre-validated operation templates with appropriate parameter substitutions, enabling automation at scale while maintaining simplicity in the template definitions themselves.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12413649B2Mechanisms for an intelligent service layer request abstraction service
Publication Date: 2025.09.09 INTERDIGITAL PATENT HOLDINGS INC
  • US12413649B2 patent drawing
  • US12413649B2 patent drawing
  • US12413649B2 patent drawing

AI summary

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.