Request Abstraction Service for Multi-Step IoT Operation Automation

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 automatically execute 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

1Measurement precision

If manual active participation is required for each elementary operation, then control precision is improved, but productivity deteriorates and operation complexity increases

Engineering Contradiction:
Improvecontrol precisionVSAvoidoperation efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent segments service layer operations into two categories: elementary operations (individual API calls) and abstract operations (compositional workflows). The RAS service segmentes the automation task by identifying sequences of elementary operations that can be grouped into abstract operations, allowing selective automation while maintaining manual control where needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Request Abstraction Service acts as an intermediary between the requesting entity and the service layer. It receives abstract requests, automatically executes sequences of elementary operations, and returns results to the requester. This mediator pattern enables batch processing and automation without requiring manual intervention for each operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual active participation is required for each elementary operation, then operation reliability is improved, but device complexity increases

Engineering Contradiction:
Improveoperation reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The RAS service enables self-service automation by automatically executing sequences of elementary operations without requiring manual intervention. The service monitors its own execution state, handles errors, and manages transaction commits or rollbacks autonomously, reducing the need for complex error handling logic in requesting entities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The RAS service as an intermediary centralizes the complexity of coordinating multiple elementary operations. It manages the execution flow, error handling, and transaction management internally, presenting a simplified abstract interface to requesters while maintaining operational reliability through structured error handling and rollback mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If abstract requests with automatic execution are implemented, then productivity is improved and operation complexity is reduced, but control precision deteriorates

Engineering Contradiction:
Improvebatch processing capabilityVSAvoidcontrol precision
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system provides dynamic control by allowing requesting entities to choose between issuing individual elementary operations (manual control) or abstract operations (automatic execution). The RAS service dynamically adapts its behavior based on the request type, executing sequences automatically for abstract operations while maintaining the option for manual intervention when needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments operations into elementary and abstract levels, allowing selective automation. Requesting entities can issue abstract requests for routine batch operations while maintaining the ability to issue individual elementary operations when precise manual control is needed, enabling a hybrid approach that balances automation benefits with control precision.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If abstract requests with automatic execution are implemented, then scalability is improved, but system complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidservice layer complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The RAS service provides universal functionality by handling multiple types of abstract requests and coordinating various elementary operations through a unified interface. It serves as a multi-functional component that can process different kinds of batch operations, error scenarios, and transaction types, reducing the need for separate specialized services for each operation type.

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

Data Source

PatentUS20250379921A1Mechanisms for an intelligent service layer request abstraction service
Publication Date: 2025.12.11 INTERDIGITAL PATENT HOLDINGS INC
  • US20250379921A1 patent drawing
  • US20250379921A1 patent drawing
  • US20250379921A1 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.