Subscription Grouping Mechanism for M2M Service Layer Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing oneM2M subscription mechanism is inefficient as it requires multiple identical subscription requests and notifications for multiple subscribers interested in the same resource, leading to overhead and inefficiency, especially when dealing with high-frequency resource attribute changes in M2M applications.
Innovation Solution
A subscription analyzing and grouping mechanism is proposed, where the hosting node analyzes and groups similar subscription requests, sending aggregated notifications to a transit node for distribution to subscribers, reducing the number of subscription and notification messages and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple identical subscription requests are sent for multiple subscribers interested in the same resource, then each subscriber receives individual notifications, but the number of messages and processing overhead increases significantly
Solution Approach 1:
The patent combines multiple identical subscription requests into a single aggregated subscription request. The hosting node identifies subscriptions with matching criteria (same resource, same event type, same notification policy) and merges them into one request that includes multiple subscriber identifiers. This reduces the number of messages exchanged between hosting nodes and transit nodes, directly improving subscription efficiency while maintaining reliable notification delivery to all individual subscribers.
Solution Approach 2:
The aggregated subscription request serves multiple subscribers simultaneously, making a single subscription mechanism universal for multiple identical subscriptions. The notification message structure is designed to carry information applicable to all subscribed resources and events, allowing one notification to satisfy multiple individual subscription requirements without losing subscriber-specific delivery capability.
2Reliability
If multiple identical notification messages are sent to multiple subscribers, then each subscriber receives their notification, but the network overhead and processing load increase
Solution Approach 1:
The patent merges multiple identical notification messages into a single aggregated notification message that contains the event information once, along with references to multiple subscribed resources and events. The transit node receives this single aggregated message and distributes the notification to all relevant subscribers. This approach maintains reliable delivery to each subscriber while significantly reducing network overhead and processing load compared to sending separate identical notifications to each subscriber.
Solution Approach 2:
Instead of transmitting identical notification content multiple times, the system transmits the notification content once in the aggregated message and uses references/identifiers to indicate which subscribers should receive it. The transit node creates logical copies of the notification delivery instruction for each subscriber without duplicating the actual notification payload, reducing energy consumption while ensuring reliable delivery.
3Measurement precision
If the subscription mechanism processes each subscription request individually, then subscription accuracy is maintained, but the complexity and time consumption increase
Solution Approach 1:
The hosting node performs preliminary analysis of incoming subscription requests to identify potential aggregations before processing them individually. By pre-grouping subscriptions with matching criteria (same resource, event type, and notification policy), the system reduces the number of individual processing steps required. This preliminary action maintains subscription matching accuracy while significantly reducing overall processing time and complexity.
Solution Approach 2:
The patent merges the processing of multiple identical subscription requests into a single aggregation operation. Instead of processing each subscription request separately through the complete matching and validation workflow, the system combines them into one aggregated request that is processed once, maintaining the same matching accuracy while reducing time consumption and operational complexity.
4Ease of operation
If multiple subscription requests are handled separately, then individual subscription management is precise, but the system scalability is limited
Solution Approach 1:
The patent segments the subscription management system into two functional layers: aggregation at the hosting node and distribution at the transit node. This segmentation allows individual subscription management precision to be maintained through the aggregation logic, while the system gains scalability by reducing the overall number of messages and processing operations required as the number of subscribers increases.
Solution Approach 2:
The aggregated subscription request mechanism provides a universal solution that handles multiple subscribers simultaneously while maintaining individual subscription management precision. The system becomes more adaptable and scalable because the same aggregation mechanism can handle any number of identical subscriptions without proportionally increasing processing complexity, allowing the system to grow efficiently.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A subscription analyzing and grouping mechanism can group similar subscription requests from different subscribers and generates an aggregated notification for them. The subscription analyzing and grouping mechanism reduces the number of subscription request messages and notification messages and in turn improves subscription efficiency and makes M2M/IoT service layer more efficient and scalable.