Event Notification Triggering via Application Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for providing notifications to users about application events often result in delays due to periodic synchronization schedules, leading to a poor user experience, especially in SaaS applications where events may not be immediately reflected in the user's activity feed.

Innovation Solution

Implementing a system that uses messages, such as email messages, sent by applications to trigger notifications and synchronization requests, allowing for real-time event notifications without relying on periodic syncing schedules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If periodic synchronization schedules are used to update user activity feeds, then system resource consumption is reduced, but notification timeliness deteriorates

Engineering Contradiction:
Improvenotification timelinessVSAvoidsystem resource consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The system uses periodic synchronization schedules to update user activity feeds at predetermined intervals. This allows system resources to be consumed in a controlled, periodic manner rather than continuously, reducing overall resource consumption while still providing timely notifications within each synchronization cycle.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system monitors application events and provides feedback by generating notifications when events occur during synchronization cycles. This feedback mechanism ensures that important events are communicated to users promptly while maintaining the efficiency benefits of periodic synchronization, balancing timeliness with resource consumption.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If periodic synchronization schedules are used, then system complexity is reduced, but user experience deteriorates due to delays

Engineering Contradiction:
Improveuser experienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

By implementing periodic synchronization schedules, the system maintains relatively simple architecture and operation patterns. The predictable periodic structure makes the system easier to manage and understand, while the timing is optimized to provide acceptable user experience without requiring overly complex real-time mechanisms.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system adjusts synchronization parameters such as interval timing and event types to optimize user experience. By changing these parameters, the system can improve responsiveness and user satisfaction without fundamentally increasing system complexity, maintaining a balance between simplicity and performance.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If real-time event notifications are implemented, then notification timeliness is improved, but system complexity increases

Engineering Contradiction:
Improvenotification delayVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer that sits between application events and user notifications. This intermediary monitors events, determines which require notification, and manages the timing of notifications within synchronization cycles. This approach enables improved notification timeliness without requiring direct complex real-time integration with all applications, as the intermediary handles the complexity centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11336606B2Triggering event notifications based on messages to application users
Publication Date: 2022.05.17 CITRIX SYSTEMS INC
  • US11336606B2 patent drawing
  • US11336606B2 patent drawing
  • US11336606B2 patent drawing

AI summary

In accordance with one disclosed method, a first computing system may receive a message from an application hosted on a second computing system, the message being indicative of an event of the application. In response to receiving the message, the first computing system may generate a notification indicative of the event and send the generated notification to a client device. The first computing system may receive a response to the notification from the client device, and may process the response so as to cause the application to take an action responsive to the event.