Service Layer Message Templates for Low-Overhead IoT Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing service layer request and response messages in M2M/IoT networks, particularly in low-power wide-area networks, are inefficient due to redundant parameters, leading to increased communication overhead and limited network capacity issues.

Innovation Solution

Implementing message templates at the service layer to store common request and response parameters, allowing applications to send optimized messages using template identifiers, thereby reducing redundant parameter inclusion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If request and response messages include all necessary parameters, then completeness of information is improved, but message size increases and communication efficiency deteriorates

Engineering Contradiction:
Improvecompleteness of informationVSAvoidmessage size
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts commonly repeated parameters from request and response messages and stores them in a parameter cache. Instead of including all parameters in every message, only template identifiers are transmitted, with full parameter values retrieved from the cache, thereby reducing message size while preserving information completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates parameter templates that store standard parameter sets. These templates are copied and referenced multiple times across different messages, allowing the system to avoid retransmitting identical parameter values while maintaining data integrity and completeness.

Inventive Principle:
Principle #26Copying

2Loss of information

If all parameters are transmitted in each message, then information accuracy is improved, but communication overhead increases

Engineering Contradiction:
Improveinformation accuracyVSAvoidcommunication overhead
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts and caches frequently used parameter values, allowing the system to reference them by identifier rather than retransmitting full parameter data. This extraction approach maintains information accuracy while significantly reducing communication overhead and energy consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary action by pre-storing parameter templates and their values in a cache before they are needed in message transmissions. This advance preparation allows the system to quickly reference cached parameters during communication, reducing the need to transmit redundant data and lowering communication overhead.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If message templates are implemented, then communication efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal parameter template system that serves multiple functions: storing parameters, generating message identifiers, and enabling efficient retrieval. This multi-functional approach consolidates what could be separate complex systems into a unified template mechanism, improving communication efficiency while managing system complexity through consolidation.

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

Data Source

PatentUS12495099B2Service layer message templates in a communications network
Publication Date: 2025.12.09 IPLA HLDG INC
  • US12495099B2 patent drawing
  • US12495099B2 patent drawing
  • US12495099B2 patent drawing

AI summary

The concept of a service layer message template is introduced, which may be a request template or a response template. Message templates may be created and stored at the service layer. Each message template may contain a set of request or response parameters and their values. Once in place, an application can send a request to the service layer that does not include the request parameters contained in the message template (i.e. request template); instead, a message template identifier may be sent. Since request parameters are included in the message template and stored at the service layer, communication overhead between the service layer and the application (or another service layer) may be reduced.