Middleware Buffering for Push Data Reception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communication systems, data loss occurs when an application is not active or ready to receive data, as incoming data cannot be handled immediately due to delays in launching the application, especially if user approval is needed, leading to situations where connecting parties start sending data before the receiving application is running.

Innovation Solution

Implementing a buffering mechanism between the application and the operating system, where incoming data is stored in buffers even when the application is not active, allowing the application to recover data later, even if the connection is lost, and enabling immediate data transmission from the connecting party once the application is launched.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the application waits to be manually activated or auto-launched before receiving data, then the application can process data when ready, but data loss occurs when the connecting party sends data before the application is running

Engineering Contradiction:
Improvedata reception reliabilityVSAvoidapplication launch delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by setting up the communication channel and preparing the application environment before actual data transmission begins. The application is pre-configured with connection parameters and can be rapidly activated when data arrives, reducing the effective delay between data arrival and processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism that bridges the connecting party and the application. This intermediary handles data buffering, connection management, and application activation coordination, ensuring data is not lost during the transition period when the application is not yet running.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the application is auto-launched immediately upon incoming connection, then data can be received without delay, but user approval requirements cause significant delays in launching

Engineering Contradiction:
Improvedata reception speedVSAvoiduser approval delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

User approval permissions are pre-configured and stored in the system before actual data reception occurs. When data arrives, the system checks pre-stored approval settings and can automatically activate the application without waiting for real-time user confirmation, thus maintaining productivity while respecting user control preferences.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides self-service functionality by automatically managing application activation based on pre-configured user preferences. The approval mechanism serves itself by using stored permission settings to make automatic decisions about application launch, eliminating the need for repeated user interventions while maintaining user control over the system behavior.

Inventive Principle:
Principle #25Self-service

3Speed

If the application monitors inbound connections itself, then communication can be immediate, but the application must be continuously running which consumes resources

Engineering Contradiction:
Improveconnection response speedVSAvoidapplication runtime energy consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system introduces an intermediary layer that handles connection monitoring and data buffering independently of the application's runtime state. This intermediary can detect incoming connections, buffer data, and trigger application activation only when necessary, allowing the application to remain inactive and conserve energy while maintaining fast response capability through the always-active monitoring layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7707291B2Handling incoming data
Publication Date: 2010.04.27 NOKIA TECHNOLOGIES OY
  • US7707291B2 patent drawing
  • US7707291B2 patent drawing
  • US7707291B2 patent drawing

AI summary

So-called push technology enables reception of new contents automatically, i.e. without user initiation. In order to enable a connecting party to send data when a receiving application is not even running, and thus cannot receive the data, middleware simulating the application to a connecting party, and an active connection to the application by utilizing buffers is provided. More precisely, the middleware is arranged to buffer incoming data on behalf of the application, if the application is not receiving the data, and to allow the application to receive the buffered data when the application is again willing to receive the data.