Group Server Notification Aggregation for M2M Traffic Reduction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Machine-to-Machine (M2M) communication systems experience heavy communication traffic due to numerous notification messages exchanged between group member devices and subscription devices when group member devices send notifications.

Innovation Solution

Implementing a group communication method where group member devices send notification messages to a group server only if a resource meets a subscription condition, allowing the server to aggregate and send a consolidated notification message to the subscription device, reducing the number of messages exchanged.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If group member devices send notification messages directly to subscription devices for each resource change, then real-time notification reliability is improved, but communication traffic volume increases significantly

Engineering Contradiction:

Improvenotification delivery reliabilityVSAvoidcommunication traffic volume

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

A group server is introduced as an intermediary between group member devices and subscription devices. The group server receives notification messages from multiple group member devices, aggregates them, and then sends consolidated notification messages to subscription devices. This mediator approach maintains reliable notification delivery while significantly reducing communication traffic volume by preventing direct one-to-one message exchanges between all group members and subscribers.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies merging by consolidating multiple notification messages into a single aggregated message. The group server collects notification messages from multiple group member devices and combines them into one unified notification message that is then sent to the subscription device. This merging operation reduces the number of messages exchanged while preserving all necessary notification information, thereby reducing communication traffic volume without sacrificing reliability.

Inventive Principle:

Principle #5Merging (Combining)

2Reliability

If every group member device sends individual notification messages to the subscription device, then notification completeness is improved, but system complexity increases

Engineering Contradiction:

Improvenotification completenessVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The group server serves as a centralized intermediary that manages the complexity of collecting, aggregating, and distributing notification messages. By introducing this mediator, individual group member devices do not need to directly manage multiple subscription devices, and the system avoids the complexity of managing numerous one-to-one communication channels between all group members and subscribers while maintaining complete notification delivery.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The group server performs multiple functions: receiving notifications from any group member device, aggregating messages from multiple sources, determining which subscription devices should receive the aggregated notifications, and sending consolidated messages to appropriate subscribers. This multi-functional design simplifies the overall system architecture by centralizing complex operations in a single universal component rather than requiring distributed complexity across multiple devices.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If the system uses RESTful group resource methodology, then ease of operation is improved, but communication traffic increases due to multiple message exchanges

Engineering Contradiction:

Improveoperation simplicityVSAvoidcommunication traffic

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The group server acts as an intermediary that preserves the ease of operation benefits of RESTful group resource methodology while mitigating the communication traffic problem. The server receives resource change notifications from group members using standard RESTful patterns, processes these notifications, and sends aggregated results to subscription devices. This approach maintains the simplicity and standardization of RESTful operations while reducing the number of messages exchanged through intelligent aggregation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The group server performs preliminary aggregation of notification messages before sending them to subscription devices. By collecting and processing multiple notification messages in advance and consolidating them into a single message, the system reduces the number of communication exchanges required. This preliminary action maintains the ease of operation through standardized processing while significantly reducing communication traffic volume.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11805441B2Method and system for group communication, group server, and group member device

Publication Date: 2023.10.31 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD

AI summary

Embodiments of the present invention provide a group communication method, system, group server, and group member device. A group server receives notification messages sent by a group member device, aggregates, according to an address of a subscription device, the notification messages destined for the same subscription device, and sends a notification message obtained after aggregation to the subscription device.