M2M Cross-Resource Subscription for Unified Time-Window Notifications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional M2M service layers, such as oneM2M, lack support for cross-resource subscription, requiring separate subscriptions and notifications for multiple resources, leading to extra processing and overhead at the subscriber.

Innovation Solution

Implementing cross-resource subscription mechanisms where a subscriber can request subscription to multiple resources with defined notification criteria and time windows, allowing the resource host to generate unified notifications based on these criteria within a specified time frame.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If separate subscriptions are implemented for multiple resources, then each resource can be monitored individually, but processing overhead and notification quantity increase significantly

Engineering Contradiction:

Improveresource monitoring precisionVSAvoidsubscription management complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent combines multiple separate resource subscriptions into a single unified subscription mechanism. Instead of requiring individual subscriptions for each resource, the system allows subscribers to monitor multiple resources through one subscription, which reduces processing overhead and simplifies subscription management while maintaining the ability to detect changes in each individual resource.

Inventive Principle:

Principle #5Merging (Combining)

2Speed

If individual notifications are sent for each resource change, then real-time monitoring is achieved, but communication channel load increases

Engineering Contradiction:

Improvenotification response speedVSAvoidcommunication channel load

Core Design Contradiction:

SpeedVSLoss of energy

Solution Approach 1:

The patent merges multiple individual resource notifications into a single unified notification mechanism. When any of the subscribed resources undergo a change, the system sends one consolidated notification instead of multiple separate notifications, thereby reducing communication channel load and energy consumption while still providing real-time monitoring capabilities.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system creates a unified notification template that can be reused across multiple resource types. Instead of generating separate notification structures for each resource, a single notification format is used that can carry information about multiple resource changes, reducing the overall communication overhead.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If multiple separate subscriptions are maintained, then comprehensive resource coverage is achieved, but processing overhead at subscriber increases

Engineering Contradiction:

Improveresource coverage scopeVSAvoidsubscriber processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent combines multiple subscription processing tasks into a single unified subscription handler at the subscriber side. This unified mechanism can monitor and process changes across multiple resources simultaneously, maintaining comprehensive resource coverage while significantly reducing the processing overhead that would otherwise be required to manage multiple separate subscriptions.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS12382264B2Cross-resource subscription for M2M service layer

Publication Date: 2025.08.05 INTERDIGITAL PATENT HOLDINGS INC

AI summary

A subscriber issues a message to a resource host to request subscription to multiple resources. This message may indicate identifiers of these resources, event notification criteria for each individual resource and define cross-resource notification criteria such as time window type and time window size. The resource host issues cross-resource notifications to the subscriber or its designated notification targets when expected changes on the target resources occur within a time window.