Asynchronous Widget Micro Payments via Ajax and Cookies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The request/response paradigm used in internet transactions for making purchases or donations is inefficient, requiring multiple web page loads and high bandwidth usage, failing to capture the real-time experience and wasting resources.

Innovation Solution

Implementing an asynchronous payment system using AJAX technology and widgets that allow for micro payments without loading entire web pages, using cookies to store transaction data and updating only the relevant screen objects or widgets, enabling partial screen updates and efficient data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the request/response paradigm is used for internet transactions, then business transactions can be completed, but bandwidth and computing resources are wasted due to loading entire web pages for each transaction step

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidbandwidth and computing resource usage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the web page into multiple independent objects (widgets, screens, components) that can be updated individually. Instead of loading entire web pages for each transaction step, only the specific screen objects involved in the transaction are loaded or updated. This segmentation allows the system to reduce bandwidth usage by transmitting only the necessary data for specific transaction elements rather than entire pages.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the essential transaction functionality from the traditional web page framework. By using asynchronous JavaScript and XML (Ajax) technology, the transaction processing is separated from the full web page loading process. Only the necessary transaction data and specific screen objects are transmitted and updated, extracting the core transaction function from the overhead of complete page loads.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If the request/response paradigm is used for internet transactions, then purchases and donations can be processed, but the real-time experience is not captured due to multiple web page loads

Engineering Contradiction:
Improveuser experience qualityVSAvoidtime for multiple page loads
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements continuous transaction processing through asynchronous updates. Instead of interrupting the user experience with sequential page loads, the system continuously processes transactions in the background and updates only the relevant screen objects. This maintains the continuity of the user experience, allowing users to interact with the page while transactions are processed asynchronously.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent uses cookies to store transaction data preliminarily before final processing. Transaction information is captured and stored in cookies during user interaction, allowing the transaction to be prepared in advance. This preliminary action enables faster processing by having transaction data ready before the actual transaction completion step, reducing the perceived time for transaction processing.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If entire web pages are loaded for each transaction step, then transaction data can be transmitted, but bandwidth usage increases significantly

Engineering Contradiction:
Improvedata transmission completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by transmitting only the necessary portion of transaction data rather than complete web pages. Using Ajax technology, the system sends and receives only the specific data elements required for transaction processing (such as transaction amounts, item identifiers, and user information) instead of transmitting entire web pages. This partial data transmission maintains reliability by including all essential transaction information while dramatically reducing bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

4Loss of information

If new web pages are generated for each transaction step, then transaction progress can be tracked, but computing resources are wasted

Engineering Contradiction:
Improvetransaction status trackingVSAvoidcomputing resource requirements
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent uses cookies as lightweight copies to store and track transaction information. Instead of generating new web pages to track transaction progress, the system creates simplified data copies in cookies that contain essential transaction status information. These cookie copies are much less resource-intensive than full web pages while still providing adequate transaction tracking functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent segments transaction tracking into independent screen object updates rather than full page generations. Each screen object can be updated independently to reflect transaction progress, allowing the system to track transaction status by modifying only the relevant visual elements on the page. This segmentation reduces computing resources by avoiding the overhead of generating complete new web pages for each status update.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9524496B2Micro payments
Publication Date: 2016.12.20 PAYPAL INC
  • US9524496B2 patent drawing
  • US9524496B2 patent drawing
  • US9524496B2 patent drawing

AI summary

In one example embodiment, a system and method is shown that includes receiving financial data generated by a widget residing on a web page, the financial data including at least one of donation, or purchase data. The system and method may further include transmitting a display update to update the widget, the updating based upon the financial data. Some example embodiments may include, selecting a widget using an input device to generate data including at least one of donation or purchase data. Moreover, the system and method may include transmitting the at least one of donation or purchase data. Further, the system and method may include storing the at least one of donation or purchase data to a cookie.