Sessionless Reporting for Resource-Constrained DM Clients

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Device Management (DM) protocols, such as OMA-DM, are inadequate for resource-constrained Machine-to-Machine (M2M) devices with limited memory and processing capabilities, as they require session-based communication, which is inefficient for devices with restricted capabilities.

Innovation Solution

Implementing sessionless reporting mechanisms for DM Clients, allowing them to send reports to a DM Server outside the context of a DM session using a Sessionless Report Configuration Management Object (MO) that includes nodes for controlling reporting criteria and awaiting acknowledgments during subsequent sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session-based communication is used for DM Clients, then reliable management operations can be performed, but communication overhead increases and device complexity increases

Engineering Contradiction:

Improvereliability of management operationsVSAvoidcomplexity of session management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the essential reporting function from the session-based communication context. By using sessionless reporting, the DM Client can send reports to the DM Server without establishing or maintaining a DM session, thereby removing the complex session management overhead while preserving the core reliability of report delivery through acknowledgment mechanisms.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the communication into discrete report transactions rather than requiring continuous session-based interaction. Each report is sent as an independent unit with its own acknowledgment handling, separating the reporting function from the session management function and reducing overall system complexity.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If session-based communication is used for DM Clients, then complete interaction protocol can be maintained, but communication overhead increases

Engineering Contradiction:

Improvecompleteness of interaction protocolVSAvoidcommunication overhead

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential reporting functionality from the complete session-based interaction protocol. By implementing sessionless reporting, the system maintains the core adaptability of the DM protocol for reporting operations while eliminating the energy-consuming session establishment and maintenance overhead.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by implementing only the necessary reporting and acknowledgment mechanisms without requiring the full session-based interaction protocol. This partial implementation suffices for reporting operations while significantly reducing communication overhead and energy consumption.

Inventive Principle:

Principle #16Partial or excessive action

3Productivity

If sessionless reporting is implemented, then communication overhead is reduced, but acknowledgment reliability may be compromised

Engineering Contradiction:

Improveefficiency of data transmissionVSAvoidreliability of acknowledgment

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms at the report level rather than at the session level. The DM Client sends individual acknowledgments for each report received, providing reliable feedback without requiring session-based communication. This feedback approach maintains productivity benefits while ensuring acknowledgment reliability.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent segments the acknowledgment process into discrete per-report confirmations rather than relying on session-based acknowledgment. Each report receives an individual acknowledgment, ensuring reliable delivery confirmation while maintaining the efficiency of sessionless communication.

Inventive Principle:

Principle #1Segmentation

4Device complexity

If sessionless reporting is used, then device complexity is reduced, but protocol implementation complexity increases

Engineering Contradiction:

Improvecomplexity of session managementVSAvoidcomplexity of protocol implementation

Core Design Contradiction:

Device complexityVSEase of manufacture

Solution Approach 1:

The patent makes the SessionlessReportConfiguration MO universal by allowing it to be configured through standard DM Client interfaces. The MO can be set up using existing DM Client capabilities, and the sessionless reporting functionality integrates with the standard OMA-DM protocol, reducing implementation complexity while maintaining reduced device complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8924544B2Techniques for sessionless reporting by device management client

Publication Date: 2014.12.30 SAMSUNG ELECTRONICS CO LTD

AI summary

A device and method for performing sessionless reporting are provided. The device includes a memory for storing code of a Device Management (DM) Client and a Sessionless Report Configuration Management Object (MO), the Sessionless Report Configuration MO including one or more nodes, a processor for executing the code of the DM Client stored in the memory, a communications unit for sending and receiving information for the DM Client, and the DM Client for sending one or more sessionless reports to a DM server, and, while awaiting acknowledgement of the one or more sessionless reports from the DM Server in a subsequent DM Session, for controlling sessionless reporting based on criteria specified in at least one node included in the Sessionless Report Configuration MO.