Push Notification Server Replaces Open Browser Connections

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional HTTP connections often remain open for extended periods, especially when data is not instantaneously available or for periodic updates, leading to inefficient utilization and increased resource usage.

Innovation Solution

Implementing push notifications to replace HTTP requests and responses, allowing computing devices to convert HTTP requests or XHRs into push notifications, thereby reducing the need for open browser connections by using a push server to deliver data updates periodically or upon status changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HTTP connections are kept open for data requests, then real-time data delivery is enabled, but resource usage increases and connection efficiency decreases

Engineering Contradiction:

Improvereal-time data deliveryVSAvoidresource usage

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

A push server is introduced as an intermediary component between the web server and the web browser. The push server receives data from the web server and actively pushes it to the browser through notification mechanisms, eliminating the need for the browser to maintain persistent open connections while ensuring real-time data delivery. This intermediary resolves the contradiction by decoupling the data production (web server) from data consumption (browser) without requiring continuous connection state.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Duration of action of moving object

If HTTP connections remain open for extended periods, then periodic updates can be delivered, but connection utilization becomes inefficient

Engineering Contradiction:

Improveconnection durationVSAvoidconnection utilization

Core Design Contradiction:

Duration of action of moving objectVSProductivity

Solution Approach 1:

The system implements periodic action through push notifications delivered at specific intervals or events rather than maintaining continuous connection state. The push server periodically pushes data to the browser when updates are available, allowing the HTTP connection to be closed between updates. This enables periodic data delivery while improving connection utilization by keeping connections closed during idle periods.

Inventive Principle:

Principle #19Periodic action

3Productivity

If push notifications replace HTTP requests, then open browser connections are reduced, but system complexity increases

Engineering Contradiction:

Improveconnection efficiencyVSAvoidsystem architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The push server is designed as a universal multi-functional component that handles multiple tasks: receiving data from web servers, managing notification queues, determining optimal push timing, and delivering notifications to browsers. By consolidating these functions into a single multi-purpose system, the overall system complexity is managed more effectively than if each function were implemented separately in the browser or web server.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9009283B2Using push notifications to reduce open browser connections

Publication Date: 2015.04.14 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A browser request is received at a computing device. A determination is made as to whether to replace the browser request with a push notification based upon characteristics of the browser request. The browser request is replaced with the push notification in response to determining, based upon the characteristics of the browser request, to replace the browser request with the push notification.