Interprogram Communication via Event Handling and Tagging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing applications are limited in communicating with other applications using different data conventions, requiring significant development effort and memory resources, and modifying source code to change functionality, which is impractical for case-by-case configurations.

Innovation Solution

Implementing interprogram communication with event handling allows multiple applications to exchange information and interact without large, configuration-specific applications, using subscription tagging, overlays, and online enhancements to dynamically provide information without modifying source code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are coded with predetermined features and functionalities, then application stability is improved, but adaptability to communicate with other applications using different data conventions deteriorates

Engineering Contradiction:
Improveapplication stabilityVSAvoidinterapplication communication capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary layer (web service tagging tool and event handling system) that sits between applications with predetermined functionality and external data sources. This intermediary enables flexible data collection and communication without requiring modifications to the core application code, thus maintaining stability while enabling adaptability through subscription tags and event-driven architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the application functionality into modular components: the core application remains unchanged with predetermined features, while separate modules (web service tagging tool, data collector engine, online enhancement engine) handle communication and data processing. This segmentation allows the core application to maintain stability while peripheral modules provide adaptability for interapplication communication.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If source code is modified to change application functionality, then adaptability is improved, but development time and effort increase

Engineering Contradiction:
Improvefunctionality change capabilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic functionality changes through event handling and subscription tags that can be configured and modified at runtime without recompiling or redeploying the application. The web service tagging tool dynamically adds, removes, or modifies event subscriptions based on user needs, enabling rapid adaptation of application behavior without the time-consuming process of source code modification.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary actions by pre-configuring event handlers, subscription tags, and data collection mechanisms that can be easily activated or deactivated. This preliminary setup allows functionality to be changed by simply switching configurations rather than modifying source code, significantly reducing development time while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If large applications are created to support numerous configurations, then adaptability is improved, but memory resources increase

Engineering Contradiction:
Improveconfiguration support capabilityVSAvoidmemory resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements a universal event handling system and web service tagging tool that can serve multiple configurations and purposes through a single lightweight application. Rather than creating separate large applications for different configurations, this universal system adapts to various needs through configurable subscription tags and event handlers, maintaining low memory usage while supporting diverse functionalities.

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

Solution Approach 2:

The patent uses lightweight copies of event handling mechanisms and subscription tag structures that can be replicated and configured for different purposes without duplicating entire application modules. This approach allows multiple configurations to be supported using minimal memory resources, as the same core infrastructure is reused across different scenarios rather than creating separate large applications.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10949605B2Interprogram communication with event handling for online enhancements
Publication Date: 2021.03.16 BANK OF AMERICA CORP
  • US10949605B2 patent drawing
  • US10949605B2 patent drawing
  • US10949605B2 patent drawing

AI summary

A web service tagging tool including a web service application that includes a tagging engine configured to identify one or more hyperlinks on a user interface of a user application, to assign user-defined labels to the one or more hyperlinks on the user interface of the user application, and to send data content comprising the one or more hyperlinks to the user interface of the user application. The web service tagging tool further includes a data collector engine configured to receive data in response to a user selecting one or more hyperlinks from the plurality of hyperlinks on the user interface where the data identifies the selected one or more hyperlinks. The web service tagging tool further includes an online enhancement engine configured to parse the received data by the user-defined labels and compile a report comprising the received data organized by the user-defined labels.