Splitting Engine for Parallel Request Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems face inefficiencies in processing data requests due to sequential retrieval of data elements from multiple repositories, leading to increased processing time and resource consumption, and lack adequate network security, making them vulnerable to malicious attacks.

Innovation Solution

The system splits data requests into sub-requests encapsulated in sub-wrappers, groups them based on attributes, and sends them to relevant repositories, while using wrappers to ensure data integrity and security during transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential requests are sent to multiple data repositories to fetch different types of data elements, then data security and integrity are maintained, but request processing time increases and throughput decreases

Engineering Contradiction:

Improvedata securityVSAvoidrequest processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent divides a single data request into multiple sub-requests, each targeting specific data repositories. The request is split into sub-requests that can be processed in parallel, with each sub-request containing only the necessary credentials and parameters for its target repository. This segmentation enables concurrent processing while maintaining security through minimal credential exposure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-processing the original request to identify required data repositories and their access credentials before splitting. Credentials are prepared and attached to appropriate sub-requests in advance, enabling immediate parallel execution without sequential authentication delays.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If duplicative requests are sent to multiple data repositories to fetch data elements simultaneously, then request processing time is reduced, but computing resources such as memory and bandwidth are consumed

Engineering Contradiction:

Improverequest processing throughputVSAvoidcomputing resources

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The original request is segmented into non-overlapping sub-requests, each targeting a specific data repository with only the necessary data elements. This eliminates duplicative transmissions by ensuring each sub-request fetches unique data portions, reducing overall network bandwidth consumption and memory usage while maintaining parallel processing benefits.

Inventive Principle:

Principle #1Segmentation

3Loss of energy

If sequential request processing is used to conserve computing resources, then resource consumption is reduced, but processing time increases and throughput decreases

Engineering Contradiction:

Improvecomputing resourcesVSAvoidrequest processing throughput

Core Design Contradiction:

Loss of energyVSProductivity

Solution Approach 1:

The request processing workload is segmented into independent sub-requests that can execute in parallel. Each sub-request is self-contained with necessary credentials and parameters, allowing simultaneous processing across multiple data repositories. This segmentation increases throughput by utilizing parallel computing resources efficiently without causing resource conflicts.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs partial actions by creating only the necessary sub-requests for required data repositories rather than processing all possible requests. This selective parallel processing optimizes resource utilization by activating only the computing resources needed for the specific data elements requested, avoiding excessive resource consumption.

Inventive Principle:

Principle #16Partial or excessive action

4Adaptability or versatility

If data requests are sent to multiple data repositories located in different geographic locations, then data availability is improved, but network traffic increases and overall throughput is reduced

Engineering Contradiction:

Improvedata availabilityVSAvoidnetwork bandwidth

Core Design Contradiction:

Adaptability or versatilityVSLoss of substance

Solution Approach 1:

The request is segmented to send only necessary data element queries to each geographically distributed data repository. By dividing the original request into targeted sub-requests with specific query parameters, the system minimizes network traffic to each location while ensuring data availability from multiple sources. This prevents redundant data transmission across the network.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10425456B2Request processing system using a splitting engine

Publication Date: 2019.09.24 BANK OF AMERICA CORP

AI summary

A system includes a request processing system which enables the system to reduce request processing time, increase overall throughput of the system, while conserving computing resources and increasing data security associated with the storage and transmission of requests and requested information over a network. The system is configured to gather a plurality of requests, encapsulate each of the requests in a wrapper, split each of the encapsulated requests into sub-requests that are encapsulated in sub-wrappers, divide the encapsulated sub-requests into multiple groups based on some attributes, and send the multiple groups of encapsulated sub-requests relevant data repositories.