Application Subsystem Routing With Dynamic Connection Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems inefficiently utilize computing resources such as memory and network bandwidth due to predefined and constantly active connections between application sub-systems, even when some connections are not in use during data transfer processes.

Innovation Solution

Implementing an artificial intelligence/machine learning module to determine and manage interactions between application sub-systems by dynamically opening and closing connections based on a sequence of instructions generated by a control sub-system, optimizing the connection path and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connections between application sub-systems remain active all or most of the time, then reliability of data transfer is improved, but computing resources (memory and network bandwidth) are wasted

Engineering Contradiction:
Improvereliability of data transferVSAvoidcomputing resources (memory and network bandwidth)
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system dynamically manages connection states by transitioning connections between active and inactive states based on real-time data transfer requirements. The control sub-system monitors interaction patterns and activates connections only when needed for data transfer, then deactivates them to release resources, making the connection management adaptive rather than static.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system employs periodic activation and deactivation of connections based on scheduled interactions between application sub-systems. Connections are activated periodically when data transfer is required and deactivated between transfer periods, creating a rhythmic pattern of resource allocation that matches the periodic nature of data transfer operations.

Inventive Principle:
Principle #19Periodic action

2Ease of operation

If predefined connection paths are used between application sub-systems, then ease of operation is improved, but adaptability to different data transfer scenarios deteriorates

Engineering Contradiction:
Improveease of data transfer operationVSAvoidadaptability to different data transfer scenarios
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system dynamically determines connection paths based on the specific data transfer requirements of each interaction. Rather than using fixed predefined paths, the control sub-system evaluates the source and destination application sub-systems and selects optimal connection routes in real-time, allowing the system to adapt to different scenarios while maintaining operational simplicity through automated path selection.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system autonomously manages connection path selection and configuration without requiring manual intervention. The control sub-system automatically identifies the appropriate connection path between application sub-systems based on interaction requirements, configures the necessary connections, and manages the data transfer process, making the system self-adapting to different scenarios.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12468584B2Determining and managing interactions between application sub-systems using machine learning
Publication Date: 2025.11.11 BANK OF AMERICA CORP
  • US12468584B2 patent drawing
  • US12468584B2 patent drawing
  • US12468584B2 patent drawing

AI summary

A system and method for determining and managing interactions between application sub-systems. The method includes receiving plan identification information from a source application sub-system. One or more rule sets are applied to the plan identification information to determine: source and destination application sub-systems, a set of intermediate application sub-systems, and a sequence of connections determining a connection path from the source application sub-system to the destination application sub-system via the set of intermediate application sub-systems. A sequence of instructions is generated based on one or more of the source application sub-system, the destination application sub-system, the set of intermediate application sub-systems, and the sequence of connections. A first instruction is sent to the source application sub-system, which instructs the source application sub-system to: open a first connection between the source application sub-system and a first intermediate application sub-system, transfer first data via the first connection, and close the first connection.