Push Notification Framework Optimizing Channel Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing push notification systems often send redundant notifications to users across multiple channels, wasting resources and failing to efficiently deliver notifications that require no action, as users are not always active on all channels.

Innovation Solution

A framework that determines the most efficient channel for push notifications based on user history and trend analysis, selecting channels with the lowest receive time duration for notifications that do not require user action, thereby reducing redundancy and improving delivery efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notifications are sent via multiple channels to ensure delivery, then notification coverage is improved, but resource waste and redundancy increase

Engineering Contradiction:
Improvenotification delivery coverageVSAvoidresource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system applies different notification strategies to different users based on their individual channel activity patterns. Each user receives notifications only through channels they are currently active on, rather than uniformly across all channels. This localized adaptation eliminates redundant notifications while maintaining reliable delivery for each user.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically changes the notification channel parameters based on user behavior. By monitoring user activity across different channels over time, the system adjusts which channels are selected for notification delivery, optimizing the balance between coverage and resource efficiency for each user.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If notifications are sent through all available channels, then notification reach is improved, but receive time duration increases

Engineering Contradiction:
Improvenotification reachVSAvoidreceive time duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts and removes redundant notification channels from the delivery process. By identifying channels where users are not active, the system eliminates unnecessary notification attempts, reducing the overall time required for notification delivery while maintaining reach through active channels only.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary analysis of user channel activity patterns before sending notifications. By pre-identifying which channels are currently active for each user, the system prepares an optimized notification delivery plan that minimizes receive time duration while ensuring the notification reaches the user through an active channel.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If redundant notifications are sent to ensure user awareness, then notification reliability is improved, but user engagement decreases

Engineering Contradiction:
Improvenotification reliabilityVSAvoiduser engagement
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies partial action by sending notifications through only the necessary subset of channels rather than all channels. By sending notifications through a single optimized channel based on user activity, the system achieves sufficient reliability without the excessive redundancy that harms user engagement.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9967223B2System for push service notification based on user history
Publication Date: 2018.05.08 SAP SE
  • US9967223B2 patent drawing
  • US9967223B2 patent drawing
  • US9967223B2 patent drawing

AI summary

Disclosed herein is a framework for pushing service notifications to users via selected channels that are chosen based on user history. In accordance with one aspect, the framework determines if a notification is to be sent to a particular user. The framework may further determine if the notification requires an action. If the notification requires no action, the framework may choose, from multiple channels, a channel with lowest receive time duration. The framework may then send the notification via the chosen channel.