Ecommerce Translation Architecture for Banking System Decoupling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current electronic banking systems are complex and inefficient, with each bank back office having its own methods and processes, leading to increased complexity, processing costs, and longer release cycles due to tight coupling of layers and products, resulting in slower market time, higher change costs, and increased customer interactions.

Innovation Solution

A financial transaction system with an ecommerce translation system architecture that decouples users from their bank back office systems by creating a session profile, merging it with a banking and online profile, and using a translation service to assemble and submit transactions, providing a consistent view and application, and separating the presentation layer from code and content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each bank back office has its own method and process for transactions, then each bank can process transactions according to its specific requirements, but the system complexity increases and processing efficiency decreases

Engineering Contradiction:

Improvebank-specific transaction processing capabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into distinct layers: presentation layer, translation layer, and back office layer. Each layer has specific responsibilities and communicates through standardized interfaces, reducing overall system complexity while maintaining bank-specific processing capabilities.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A translation service acts as an intermediary between the presentation layer and various bank back offices. It translates generic financial transactions into bank-specific formats and vice versa, allowing each bank to process transactions according to its requirements without increasing overall system complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If layers are tightly coupled for each banking application, then transaction processing follows a clear path, but processing time increases and market response speed decreases

Engineering Contradiction:

Improvetransaction processing reliabilityVSAvoidprocessing speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The architecture segments the system into independent layers that can operate asynchronously. The translation layer buffers and manages communication between presentation and back office layers, reducing processing time while maintaining reliability through structured error handling and transaction management.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Session profiles are pre-configured with user authentication and account information before transactions are initiated. This preliminary preparation reduces processing time during actual transaction execution while maintaining security and reliability through pre-validated session management.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If each banking system is independently configured, then customization is possible, but integration with new bank entities becomes difficult and costly

Engineering Contradiction:

Improvecustomization capabilityVSAvoidintegration ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The translation service provides universal functionality by supporting multiple bank back offices through a common interface. New bank entities can be integrated by configuring translation rules in the translation layer without modifying the overall system architecture, making integration easier while maintaining customization capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Bank-specific processing logic is extracted from the presentation layer and placed in the translation layer. This separation allows new bank entities to be integrated by adding translation configurations rather than modifying core system code, reducing integration costs while preserving customization.

Inventive Principle:

Principle #2Taking out (Extraction)

4Device complexity

If the presentation layer is coupled with code and content, then system structure is simple, but system flexibility and ease of maintenance decrease

Engineering Contradiction:

Improvesystem structure simplicityVSAvoidsystem flexibility

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

Code and content are extracted from the presentation layer and placed in separate translation and configuration layers. This separation increases system flexibility and ease of maintenance while keeping the overall structure manageable through clear layer boundaries and standardized interfaces.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS8185460B1Electronic financial translation system architecture

Publication Date: 2012.05.22 BANK OF AMERICA CORP

AI summary

Aspects of the invention include methods and systems for an electronic financial transaction system with a translation system architecture. Aspects of the invention provide translation methods such that the front-end functions (e.g., authentication, presentation, content library, data library, and banking functions) are all performed under one system. These front-end functions are decoupled from their respective bank back office systems. The information from these front-end functions are merged together to form a session profile information. The translation service or module receives this session profile information and translates the session profile information of the transactions in order to complete the transaction for the user.