Web Notification Platform Channel Hierarchy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web notification systems face challenges in achieving low per notification and per browser session overhead, particularly in cloud-based solutions where sensitive information may be exposed, and in self-hosted solutions where additional components are required for horizontal scalability, complicating server-side deployment.
Innovation Solution
A web notification management platform creates a notification channel based on user-specific dimensional hierarchies, supporting both websocket and long poll mechanisms to manage web notifications efficiently, allowing for scalable and versatile delivery of notifications without requiring computationally intensive operations from cloud applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If web notification systems use traditional polling or event-driven architectures in cloud-based solutions, then notifications can be delivered to clients, but sensitive information may be exposed and system complexity increases
Solution Approach 1:
The patent introduces a service broker as an intermediary component that sits between cloud applications and client devices. The service broker receives notification requests from applications, manages the notification channels, and delivers notifications to clients. This intermediary architecture protects sensitive information by preventing direct exposure between applications and clients, while also simplifying the overall system by centralizing notification management logic in the broker rather than requiring complex implementations in each application or client.
2Productivity
If self-hosted solutions implement web notification systems with additional components for horizontal scalability, then scalability is improved, but deployment complexity and overhead increase
Solution Approach 1:
The service broker is designed as a universal platform that can serve multiple functions: managing notification channels, routing notifications to appropriate clients, handling both websocket and long-polling protocols, and supporting horizontal scalability. By making the broker multi-functional, the system achieves scalability without requiring separate specialized components for each function, thereby reducing deployment complexity while maintaining the ability to scale horizontally across multiple broker instances.
3Productivity
If servers process high volumes of notifications (1,000 messages per second), then notification throughput is improved, but processing time per message decreases to roughly 1ms requiring effective diff aggregation and batch delivering
Solution Approach 1:
The service broker performs preliminary actions by pre-aggregating notification diffs and preparing batch deliveries before clients request notifications. Instead of processing individual notifications in real-time under tight time constraints, the broker collects multiple notification changes, aggregates them into efficient batch operations, and prepares them for delivery in advance. This preliminary aggregation reduces the processing time per message when high throughput is required, as the broker can efficiently transmit multiple notifications in a single batch operation rather than handling each message individually within 1ms constraints.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Technologies for managing web notifications between a web browser and an application integration in a client- server system include a web notification management platform configured to manage web notifications to a hierarchy of users (i.e., via the web browser) about operation state change events of the application integration. To do so, the web notification management platform is configured to create a notification channel and identify a message selector to be associated with the notification channel based on a dimensional channel hierarchy determined as a function of a user for which the notification channel is being created. Accordingly, the message selector can be used to rout web notifications to the appropriate notification channel and to the applicable web browser(s) via a long poll topic subscription or a websocket connection. Additional embodiments are described herein.