Service Layer Device Management Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current device management within service layer architectures is inefficient due to the need for multiple protocol translations, data models, and access control logic, leading to complex designs and increased resource requirements, especially for constrained devices.

Innovation Solution

Enhancements include streamlined application registration procedures, automated request notification, and lightweight transport protocol bindings, such as CoAP header options, to simplify device management commands and reduce message exchanges.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple protocol translations and data models are used for device management, then device management functionality is comprehensive, but system complexity increases

Engineering Contradiction:

Improvedevice management functionalityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a service layer as an intermediary between the device management server and the target devices. This service layer handles protocol translations and data model conversions, preventing direct complex interactions between the DM server and diverse devices. The service layer acts as a mediator that standardizes communications while supporting multiple protocols and device types.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the device management system into distinct functional layers: the service layer with automated notification procedures, the transport layer with lightweight bindings, and the application layer. This segmentation allows each layer to handle specific tasks independently, reducing overall system complexity while maintaining comprehensive management capabilities.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If multiple protocol translations are performed, then device compatibility is improved, but message exchange overhead increases

Engineering Contradiction:

Improvedevice compatibilityVSAvoidmessage exchange overhead

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements automated request notification procedures where the service layer pre-configures notification mechanisms and establishes binding relationships before actual device management operations occur. This preliminary setup eliminates the need for repeated protocol translations and handshakes during runtime, reducing message exchange overhead while maintaining device compatibility.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If comprehensive device management commands are supported, then management capability is enhanced, but resource consumption on constrained devices increases

Engineering Contradiction:

Improvemanagement capabilityVSAvoidresource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts complex protocol translation and command processing logic from the constrained devices and relocates it to the service layer. The service layer handles comprehensive device management commands and translates them into appropriate protocols, allowing constrained devices to execute simpler commands with reduced resource consumption while still supporting full management capabilities.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11671306B2Enhancing native service layer device management functionality

Publication Date: 2023.06.06 INTERDIGITAL PATENT HOLDINGS INC

AI summary

Enhancements to the device management functionality within service layer architecture of a Gateway node are described. The SL application registration procedure can be enhanced for devices in support of device management. Functionality can be added to the service layer to initiate automated request notification for DM purposes. Lightweight SL Transport Protocol bindings can support sending multiple DM commands called DM Action Scripts with a specific focus on the Constrained Application Protocol (CoAP) Protocol.