Proxy-Injected Messaging Handler for On-Demand Push Notifications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current push notification mechanisms are limited in allowing third-party devices to initiate notifications across multiple web resources, require user registration and installation of agents, and are not transparent or seamless, particularly in cloud computing environments where uninterrupted service is crucial.

Innovation Solution

A proxy device modifies server responses to include a messaging handler, establishing a communication channel with a notification server to push real-time notifications to client devices, enabling on-demand notifications across different web resources without user registration or agent installation, using protocols like WebSocket for secure communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current push notification mechanisms are used, then notifications can be delivered from servers to clients, but third-party devices cannot initiate notifications across multiple web resources

Engineering Contradiction:
Improvenotification initiation capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a notification handler as an intermediary component that is injected into web pages by a proxy device. This handler enables third-party devices to initiate notifications across multiple web resources without requiring direct server-client communication, thereby resolving the contradiction between versatility and complexity by adding a mediating layer rather than fundamentally redesigning the entire system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The notification system is segmented into distinct components: the proxy device that intercepts responses, the notification handler injected into web pages, and the notification server that delivers notifications. This segmentation allows each component to have a specific function, enabling third-party notification initiation while maintaining manageable system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

2Reliability

If user registration and agent installation are required, then push notifications can be delivered reliably, but the process is not transparent or seamless to users

Engineering Contradiction:
Improvenotification deliveryVSAvoiduser setup process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The notification handler is automatically injected into web pages through the proxy device without requiring user action for installation or configuration. The system serves itself by automatically establishing the notification mechanism, thereby maintaining reliable notification delivery while eliminating the need for manual user setup, making the process transparent and seamless.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The proxy device performs preliminary action by automatically injecting the notification handler into web pages before the user interacts with the application. This preliminary setup ensures reliable notification delivery is already in place without requiring the user to go through registration or installation steps, thereby achieving both reliability and ease of operation.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If traditional push mechanisms are used, then notifications can be delivered, but cloud computing services cannot ensure uninterrupted service after browser or application updates

Engineering Contradiction:
Improveservice continuityVSAvoidbrowser compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The notification handler is designed to be universally compatible across different browsers and application versions by being injected as a standard script into web pages. This universal design allows cloud computing services to maintain uninterrupted service after updates, as the notification mechanism does not depend on specific browser or application implementations, thereby achieving both reliability and adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If a proxy device monitors and regulates traffic, then security and control are improved, but the proxy cannot push notifications on-demand to clients

Engineering Contradiction:
Improvetraffic controlVSAvoidnotification responsiveness
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The notification handler acts as an intermediary that enables the proxy device to push notifications on-demand to clients. The handler receives notification commands from the proxy device and delivers them to the client's browser, thereby maintaining the proxy's traffic control capabilities while adding the productivity of responsive, on-demand notification delivery without requiring fundamental changes to the proxy's architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11233867B2On-demand push notification mechanism
Publication Date: 2022.01.25 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11233867B2 patent drawing
  • US11233867B2 patent drawing
  • US11233867B2 patent drawing

AI summary

A method, a non-transitory computer readable medium, and a proxy device. The method includes receiving, by a proxy device, a request to access a first web resource of a plurality of web resources; modifying a received response to include at least a messaging handler, wherein the response corresponds to the received request; returning the modified response with the messaging handler to a client device, wherein the messaging handler causes establishment of a communication channel between the client device and a notification server; and providing the notification server with at least one notification, wherein the notification server immediately pushes the at least one notification to the client device over the communication channel, wherein the at least one notification is related to at least the first web resource.