Notification Queue System for Shared Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Collaboration notification systems in productivity applications often overwhelm users with excessive notifications, consuming bandwidth and resources, while timely notifications are essential for effective collaboration.

Innovation Solution

A notification queue system that periodically analyzes internal editing events in shared documents, sending individual notifications for single events and group notifications for multiple events, conserving resources and improving user experience by reducing notification frequency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual notifications are sent for every editing event, then users receive timely information about document changes, but users are overwhelmed with excessive notifications and communication resources are consumed

Engineering Contradiction:
Improvetimeliness of notificationVSAvoidnotification overload
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system implements periodic polling of the notification queue at scheduled intervals rather than immediate notification for every editing event. This periodic action allows the system to accumulate multiple editing events and send consolidated notifications, reducing notification frequency while maintaining timely awareness of document changes.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

Multiple individual editing event notifications are merged into a single consolidated notification that summarizes multiple changes. This merging approach combines multiple notification events into one unified notification, reducing the total number of notifications sent to users while preserving information about all editing events.

Inventive Principle:
Principle #5Merging (Combining)

2Loss of information

If notifications are sent for every editing event, then users stay informed about collaboration activities, but bandwidth and power resources are consumed

Engineering Contradiction:
Improvecollaboration information completenessVSAvoidbandwidth and power consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

Multiple notification events are merged into a single consolidated notification that preserves information about all editing events while reducing the total communication overhead. This approach maintains collaboration information completeness by including details of multiple edits in one notification message.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system uses periodic polling intervals to determine when to send notifications, consolidating multiple editing events that occur within each polling interval into a single notification. This reduces the frequency of communication events, thereby conserving bandwidth and power resources.

Inventive Principle:
Principle #19Periodic action

3Loss of energy

If notification frequency is reduced to conserve resources, then bandwidth and power are conserved, but users may miss timely information about document changes

Engineering Contradiction:
Improveresource conservationVSAvoidinformation timeliness
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system employs periodic polling at optimized intervals that balance resource conservation with information timeliness. By adjusting the polling frequency, the system can conserve resources through less frequent notifications while ensuring that users are still notified of document changes within an acceptable time frame.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The notification system monitors user engagement and document activity patterns to dynamically adjust notification timing and consolidation. This feedback mechanism ensures that resource conservation does not compromise information timeliness by adapting notification behavior based on actual usage patterns and urgency of changes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10552234B2Enhanced notification of editing events in shared documents
Publication Date: 2020.02.04 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10552234B2 patent drawing
  • US10552234B2 patent drawing
  • US10552234B2 patent drawing

AI summary

Technology is disclosed herein that enhances collaboration notifications. In various implementations, a notification queue is maintained for internal notifications that are generated as editing events that occur in relation to a shared document. The notification queue is periodically queried to determine which of the notifications qualify at a given time to be communicated externally to a group of users. An individual notification is communicated when only a single internal notification qualifies. But when multiple internal notifications are present that qualify, then a group notification is sent. Thus, users are presented with fewer notifications than otherwise, improving the user experience and conserving communication and computing resources.