Push Notification Self-Notification Avoidance via GUID Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In push notification systems, endpoint devices with shared identifiers receive unnecessary updates, leading to self-notification, increased wake-ups, synchronization, radio connection time, and battery power consumption.

Innovation Solution

A method and system that utilize a server to identify globally unique identifiers within notifications, preventing the originating device with the shared identifier from receiving updates, and pushing notifications only to devices with the shared identifier but not the globally unique identifier.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If push notifications are sent to all endpoint devices with a shared identifier, then notification delivery accuracy is improved, but self-notification waste increases

Engineering Contradiction:
Improvenotification delivery accuracyVSAvoidbattery power consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the originating device from the notification distribution list by identifying its GUID in the notification payload. The server compares the GUID against device identifiers and excludes the originating device from receiving its own notification, thereby eliminating self-notification waste while maintaining accurate delivery to all other intended recipients.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The notification system incorporates feedback by including the originating device's GUID within the notification payload itself. This self-identifying information enables the server to recognize and filter out the originating device, creating a feedback mechanism that prevents energy-wasting self-notifications while preserving reliable delivery to other devices.

Inventive Principle:
Principle #23Feedback

2Reliability

If push notifications are sent to all endpoint devices with a shared identifier, then notification completeness is improved, but synchronization overhead increases

Engineering Contradiction:
Improvenotification completenessVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The server extracts and identifies the originating device using the GUID contained in the notification. By removing the originating device from the notification distribution list, the system completes notifications to all necessary devices without redundant synchronization operations, thereby reducing overall synchronization overhead and time loss.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of sending notifications to all devices with shared identifiers (excessive action), the system applies partial action by selectively excluding the originating device. This optimized approach maintains notification completeness for all affected devices while avoiding unnecessary synchronization cycles that would waste time.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If push notifications are sent to all endpoint devices with a shared identifier, then update propagation is improved, but radio connection time increases

Engineering Contradiction:
Improveupdate propagation speedVSAvoidradio connection time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The notification system extracts the originating device identifier from the GUID in the notification payload and uses it to filter out the originating device from the distribution list. This ensures rapid update propagation to all necessary devices while reducing radio connection time by eliminating redundant communication with the originating device.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial action by sending notifications only to devices that need them (all devices with the shared identifier except the originating device). This optimized approach maintains fast update propagation while avoiding excessive radio connection time that would result from notifying the originating device of its own updates.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9876872B1Method or mechanism for self notification avoidance
Publication Date: 2018.01.23 GEN DIGITAL INC
  • US9876872B1 patent drawing
  • US9876872B1 patent drawing
  • US9876872B1 patent drawing

AI summary

A method for self-notification avoidance in a push notification system is provided. The method includes receiving, at a server configured to provide a push notification service, a notification from one of a plurality of endpoint devices to be pushed to the plurality of endpoint devices, wherein the plurality of endpoint devices has a shared identifier, and wherein the one of the plurality of endpoint devices has a globally unique identifier (GUID). The method includes identifying, at the server, the globally unique identifier in the notification and pushing the notification from the server to each of the plurality of endpoint devices having the shared identifier except the one of the plurality of endpoint devices that has the globally unique identifier.