Event Handling Subscription Tagging for Interprogram Communication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing applications are limited in communicating with each other due to different data conventions, requiring significant development effort and memory resources, making it impractical for multiple applications to work cooperatively without modifying their source code.

Innovation Solution

Implementing interprogram communication with event handling using a web service tagging tool that generates subscription tags linking user data fields, data location information, and triggering events, allowing applications to exchange information and interact without modifying their source code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are coded with predetermined features and data conventions, then application stability is improved, but the ability 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 event handling system as an intermediary layer between applications. This system uses standardized event types (e.g., form submission, button click) that act as a universal language, allowing applications with different internal data conventions to communicate through common event interfaces without requiring source code modification.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The event handling system provides universal functionality by implementing a standardized set of event types that can be used across multiple applications. The system can handle various data formats and conventions through a unified event processing mechanism, enabling one application to serve multiple communication purposes without losing its own stability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If source code is modified to enable application communication, then interapplication cooperation is improved, but development time and effort increase significantly

Engineering Contradiction:

Improveapplication cooperation capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The event handling system is pre-configured with standardized event types and data structures during system design. This preliminary setup allows applications to communicate using these pre-defined interfaces without requiring developers to modify source code or create custom communication protocols for each interaction scenario.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables applications to self-configure for communication by automatically mapping their internal data structures to the standardized event formats. The event handling system provides self-service capabilities through automatic data transformation and routing, eliminating the need for manual source code modification and reducing development time.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If custom applications are created for different configurations, then communication specificity is improved, but device memory resources are consumed

Engineering Contradiction:

Improvecommunication specificityVSAvoidmemory resources

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Instead of creating separate custom applications for different communication configurations, the patent implements a universal event handling system that can adapt to various communication needs through configuration. This single multi-functional system reduces memory consumption by eliminating the need to load multiple specialized applications while maintaining the ability to handle specific communication requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The event handling system is designed to be dynamic and configurable, allowing it to adapt its behavior based on the specific communication needs of different applications. This dynamic configuration capability enables the system to provide communication specificity when needed without requiring separate hard-coded applications for each scenario, thereby optimizing memory resource usage.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20180074869A1Interprogram Communication With Event Handling For Subscription Tagging

Publication Date: 2018.03.15 BANK OF AMERICA CORP

AI summary

A web service tagging tool that includes a memory operable to store subscription tags and a web service application. The web service application includes a tagging engine configure to generate a subscription tag linking target data fields, target data location information, and a triggering event. The tagging engine is further configured to send data content comprising the subscription tag to the user application. The web service application further includes a data collection engine configured to receive data from the target data fields in response to the triggering event. The web service application further includes a data feed engine operably coupled to the data collection engine. The data feed engine is configured to generate one or more data feeds comprising at least a portion of the user data and to forward the one or more data feeds based on routing instructions.