M2M Service Layer Session Management Across Multiple Hops

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional M2M service layer architectures lack support for end-to-end sessions, leading to overhead and complexity in managing sessions, preventing network services from providing value-added functionalities such as data aggregation and analytics, and are unsuitable for unmanned devices.

Innovation Solution

Implement mechanisms to support end-to-end M2M service layer sessions that span multiple service layer hops, enabling the M2M service layer to participate in end-to-end security, quality of service, and negotiation of settings, with session management functions that encrypt and compress data, and provide data analytics and aggregation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional M2M service layer architectures are used, then application sessions can be established between applications, but extra overhead and complexity are added to applications

Engineering Contradiction:
Improvesession establishment capabilityVSAvoidapplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a service layer as an intermediary between applications and the underlying communication infrastructure. This service layer session manager handles session establishment, maintenance, and termination, freeing applications from direct session management complexity while maintaining session establishment capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts session management functionality from applications and places it in the service layer. By taking out the session management burden from applications, the system reduces application complexity while preserving the ability to establish and manage sessions.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If application sessions are managed by applications themselves, then sessions can be established, but overhead and complexity increase

Engineering Contradiction:
Improvesession management capabilityVSAvoidcomputational overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The service layer acts as a mediator that assumes the burden of session management from applications. This intermediary handles session state tracking, message routing, and session lifecycle management, making session management easier for applications while reducing their computational overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service layer provides self-service session management capabilities, automatically handling session establishment, maintenance, and termination without requiring application intervention. This reduces the operational burden on applications and decreases their energy consumption related to session management.

Inventive Principle:
Principle #25Self-service

3Productivity

If conventional service layers are used, then basic communication is supported, but network services cannot provide value-added functionalities such as data aggregation and analytics

Engineering Contradiction:
Improvedata processing capabilityVSAvoidservice layer architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges session management with service layer functionality, creating an integrated architecture where the service layer simultaneously handles session control and provides value-added services such as data aggregation, analytics, and security. This combining approach enables productivity enhancement without proportionally increasing complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The service layer is designed with multi-functionality, serving both as a session management infrastructure and as a platform for value-added services. This universal approach allows the same service layer to provide basic communication support while simultaneously enabling data aggregation, analytics, and other productivity-enhancing functionalities.

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

4Reliability

If end-to-end encryption is implemented at application level, then security is provided, but network services cannot process data securely

Engineering Contradiction:
ImprovesecurityVSAvoiddata processing by network services
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The service layer introduces an intermediary encryption approach where data is encrypted at the service layer rather than at the application level. This allows network services to access and process encrypted data securely for value-added functionalities like analytics and aggregation, while still maintaining security throughout the transmission and processing pipeline.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies different encryption strategies at different layers of the architecture. The service layer implements encryption that is tailored to its specific needs, allowing network services to process data with appropriate security measures in place, rather than applying uniform end-to-end encryption that would prevent intermediate processing.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20260075112A1End-to-end m2m service layer sessions
Publication Date: 2026.03.12 INTERDIGITAL PATENT HOLDINGS INC
  • US20260075112A1 patent drawing
  • US20260075112A1 patent drawing
  • US20260075112A1 patent drawing

AI summary

Mechanisms support machine-to-machine service layer sessions that can span multiple service layer hops where a machine-to-machine service layer hop is a direct machine-to-machine service layer communication session between two machine-to-machine service layer instances or between a machine-to-machine service layer instance and a machine-to-machine application. Mechanisms are also disclosed that illustrate machine-to-machine session establishment procedures for oneM2M Session Management Service supporting multiple resources.