Multi-tiered Protection Platform Intermediate Layer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional approaches to securing computer systems, such as implementing a demilitarized zone (DMZ), often expose networks to security vulnerabilities due to redirects between service providers, which can compromise compliance and introduce additional security concerns.

Innovation Solution

A multi-tier platform with an intermediate layer that interacts between the web and application layers, acting as an aggregate layer to store or access data sets, thereby reducing the need for redirects and enhancing security by managing data requests and interactions between different service providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional DMZ approach is implemented, then network security perimeter is established, but security vulnerabilities are introduced due to redirects between service providers

Engineering Contradiction:
Improvenetwork securityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediate layer as a mediator between the web layer and application layer. This intermediate layer consolidates service provider interactions, eliminating the need for multiple redirects between different service providers that create security vulnerabilities. The intermediate layer acts as a single point of control that maintains security while enabling necessary communications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into four distinct layers: web layer, intermediate layer, application layer, and database layer. This segmentation isolates security-critical functions in the intermediate layer, allowing it to manage service provider redirects securely while keeping the web layer simple and the application layer protected from direct external interactions.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple service provider redirects are implemented, then different front end components can be accessed, but compliance failures and security concerns arise

Engineering Contradiction:
Improveservice provider integrationVSAvoidcompliance security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The intermediate layer serves as a mediator that consolidates all service provider interactions through a single controlled interface. This eliminates the need for multiple redirects between different service providers, thereby maintaining compliance security while still enabling integration with various service providers through the unified intermediate layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The intermediate layer is designed with universal functionality to handle diverse service provider interactions through a single interface. It can manage multiple service providers and different types of data requests (static and dynamic) without requiring separate redirect mechanisms, thus maintaining compliance while providing versatile service provider integration.

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

3Device complexity

If web layer handles all data requests directly, then system complexity is reduced, but security exposure increases due to direct interaction with multiple service providers

Engineering Contradiction:
Improvesystem architectureVSAvoidperimeter security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the system architecture into four layers, placing security-critical service provider interaction management in the intermediate layer. This segmentation allows the web layer to remain relatively simple while the intermediate layer handles the complexity of secure service provider communications, thus maintaining both simplicity and security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The intermediate layer acts as an intermediary that absorbs the security management complexity of interacting with multiple service providers. This protects the web layer from direct exposure to service provider protocols and security requirements, maintaining perimeter security while enabling necessary integrations.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If dynamic data is accessed from authoritative applications, then data accuracy is improved, but system response time increases due to additional queries

Engineering Contradiction:
Improvedata accuracyVSAvoiddata retrieval time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The intermediate layer performs preliminary actions by determining whether requested data sets have static or dynamic values before executing data retrieval. For static data, it serves the data directly from cached values, avoiding unnecessary queries to authoritative applications. For dynamic data, it then queries the appropriate authoritative application, thus optimizing response time while maintaining data accuracy.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10263955B2Multi-tiered protection platform
Publication Date: 2019.04.16 BANK OF AMERICA CORP
  • US10263955B2 patent drawing
  • US10263955B2 patent drawing
  • US10263955B2 patent drawing

AI summary

A multi-tier platform provides security at a perimeter of a computer system, where an intermediate layer interacts between a web layer and an application layer. A data request that is associated with a data set is received at the web layer and passed to the intermediate layer. The intermediate layer determines the authoritative source for the data set and whether the data set has a static or dynamic value. If the value is static, the intermediate layer accesses the value stored at the intermediate layer. However, if the value is dynamic, the intermediate layer queries the source registered to the data set, obtains the value from the authoritative source, and returns the dynamic value via the web layer, where the registered source may be internal or external to the computer system. Consequently, the intermediate layer may function as an aggregate layer that supports both database and messaging services.