Notification Manager Scheduling With Interaction-Based Cancellation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing notification systems lack efficient mechanisms for scheduling and canceling notifications based on specific interaction patterns, leading to redundant or irrelevant notifications.

Innovation Solution

A notification manager system that schedules notifications with a defined set of interactions and expiration times, periodically checks for expiration, and cancels notifications upon matching interaction patterns, ensuring only relevant notifications are sent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If notifications are scheduled without interaction-based cancellation, then notification delivery is simple, but redundant or irrelevant notifications are sent

Engineering Contradiction:
Improvenotification relevanceVSAvoidnotification scheduling system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by defining interaction patterns and scheduling notifications in advance with expiration times. The notification manager stores these predefined interaction patterns and uses them to automatically cancel notifications when matching interactions occur, ensuring only relevant notifications are sent without requiring complex real-time evaluation during notification delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring user interactions and using this feedback to determine whether to send scheduled notifications. When an interaction matching the predefined pattern occurs, the system receives feedback and cancels the notification accordingly, creating a closed-loop system that adapts to user behavior to eliminate redundant notifications.

Inventive Principle:
Principle #23Feedback

2Loss of time

If notifications are periodically checked for expiration, then time-based control is achieved, but system resources are consumed continuously

Engineering Contradiction:
Improvenotification timing accuracyVSAvoidsystem processing energy
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The system applies periodic action by having the notification manager check for expired notifications at regular intervals rather than continuously. This periodic checking mechanism ensures time-based control accuracy while minimizing system resource consumption, as the system only activates the expiration check function when needed based on the scheduled timing rather than maintaining constant monitoring.

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If multiple notifications are scheduled with different interaction conditions, then notification flexibility increases, but queue management complexity increases

Engineering Contradiction:
Improvenotification scheduling flexibilityVSAvoidqueue management system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the notification management task by separating notification scheduling from interaction monitoring and cancellation. The notification manager handles scheduling and expiration, while a separate mechanism handles interaction pattern matching and cancellation decisions. This segmentation allows multiple notifications with different conditions to be managed independently, increasing flexibility without proportionally increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10938949B2Notifications based on queues
Publication Date: 2021.03.02 SAP SE
  • US10938949B2 patent drawing
  • US10938949B2 patent drawing
  • US10938949B2 patent drawing

AI summary

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives, from an application, a request to schedule a notification. The program further generates a pending notification. The program also stores the pending notification in a queue. The program further periodically iterates through the queue to check whether an expiration time of the pending notification has elapsed. Upon determining that the expiration time of the pending notification has elapsed, the program also deletes the pending notification from the queue without processing the pending notification. Upon receiving from the application a second set of interactions performed on the application that matches the defined set of interactions specified in the pending notification, the program further processes the pending notification by sending the recipient specified in the pending notification a notification comprising the message specified in the pending notification.