Notification Relay Service Using Connectivity Descriptors
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The proliferation of notifications leads to GUI clutter, increased bandwidth usage, and higher costs due to the need for direct client-publisher connections and separate notifier applications, which also require complex configuration for managing notifications.
Innovation Solution
A notification relay service infrastructure that uses a connectivity descriptor to manage publisher-subscriber relationships and delivery, allowing clients to receive notifications from multiple publishers via a single connection, separating relationship management from delivery tasks and supporting various delivery models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If direct client-publisher connections are used for notification delivery, then notification reliability is improved, but device complexity and bandwidth usage increase
Solution Approach 1:
The patent introduces a notification relay service as an intermediary component between publishers and clients. This relay service manages the connection infrastructure and routing logic, allowing publishers to push notifications to the relay service which then distributes them to appropriate clients. This eliminates the need for clients to maintain direct connections to multiple publishers, reducing connection management complexity while preserving reliable notification delivery through the relay service's coordinated distribution mechanism.
2Reliability
If separate notifier applications are used for each publisher, then notification specificity is improved, but device complexity and cost increase
Solution Approach 1:
The patent implements a universal notification relay service that handles notifications from multiple different publishers through a single service infrastructure. Instead of requiring separate dedicated applications for each publisher, the relay service provides a unified interface that can route notifications from any publisher to appropriate clients based on subscription relationships. This multi-functional approach maintains reliable publisher-specific notification delivery while significantly reducing the number of separate applications needed on client devices.
Solution Approach 2:
The relay service acts as an intermediary layer that abstracts the complexity of multiple publisher connections from individual clients. Publishers continue to maintain their own notification systems, but the relay service mediates the distribution to clients, allowing a single client application to receive notifications from multiple publishers through one connection rather than requiring separate notifier applications for each publisher.
3Loss of information
If multiple notifier icons are displayed in GUI, then notification visibility is improved, but GUI clutter increases
Solution Approach 1:
The patent consolidates multiple notification sources into a single unified notification interface. Instead of displaying separate icons for each publisher's notifier application, the relay service merges all notifications into a single stream that can be displayed through one interface element. This combining approach maintains comprehensive notification visibility while eliminating the clutter of multiple separate GUI icons, as all notifications from multiple publishers are aggregated and presented through the single relay service connection.
4Speed
If direct publisher-client connections are maintained, then notification speed is improved, but bandwidth availability decreases
Solution Approach 1:
The notification relay service serves as an intermediary that efficiently routes notifications from publishers to clients. Rather than requiring multiple simultaneous direct connections from clients to different publishers, the relay service maintains optimized connection paths and can batch or prioritize notifications, maintaining fast delivery speeds while reducing the total bandwidth consumed by consolidating connection management and enabling more efficient data transmission through the relay infrastructure.
Data Source
AI summary
A notification relay service architecture can utilize one or more computing platforms that are configured to rely on a connectivity descriptor. The connectivity descriptor can express permissions of various users of the notification relay service to publish to and/or listen to notifications from one or more “exchange points.” The notification relay service can receive notifications from publishers intended for various exchange points and push notifications at exchange points to users without need for the notification relay service components to manage or even understand the underlying relationship(s) between publishers and subscribers. Server-based and/or client-based evaluations of a client's current context can be used to control whether and how notifications are relayed to/from the client.