Centralized Call Routing System for Reducing Vendor Billing Fees

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise systems face inefficiencies due to redundant calls to vendors, leading to higher billing fees and increased system latency, as each group within the system uses its own platform for vendor calls, resulting in unnecessary data requests and network traffic.

Innovation Solution

A system architecture that includes a first I/O platform, processing engine, second I/O platform, vendor source broker, and vendor data intelligence engine, which leverages calling source data, vendor data, and internal data to augment and route calls, manage vendors centrally, and cache high-frequency information to reduce redundant requests and optimize response times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If each group within the system uses its own platform for vendor calls, then each group can independently manage its data requests, but redundant calls are generated leading to higher billing fees and increased system latency

Engineering Contradiction:
ImproveIndependent vendor call managementVSAvoidBilling fees
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent implements a centralized call management platform that merges and consolidates vendor calls from multiple groups. The system receives calls from various calling sources, identifies redundant requests, and consolidates them into single vendor calls, thereby reducing the total number of calls and associated billing fees while maintaining independent access for each group.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized call management platform acts as an intermediary between calling sources and vendors. It receives data requests from multiple groups, processes them through a unified system, and forwards consolidated requests to vendors, eliminating redundant calls and reducing billing costs while preserving the operational independence of individual groups.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If each group uses its own platform for vendor calls, then call management is decentralized, but multiple data requests to the vendor result in system latency and longer response times

Engineering Contradiction:
ImproveDecentralized call managementVSAvoidSystem latency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system merges multiple data requests from different groups into a single consolidated vendor call. By combining redundant requests before they reach the vendor, the system reduces the total number of round trips, thereby decreasing system latency and improving response times while maintaining decentralized access patterns.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The call management platform performs preliminary processing of data requests before they are forwarded to vendors. It identifies and consolidates redundant requests in advance, so that when vendor calls are made, they contain aggregated data requirements rather than multiple separate requests, reducing latency by eliminating redundant network round trips.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If redundant calls are made to vendors, then each group can access vendor data independently, but network traffic increases and response efficiency decreases

Engineering Contradiction:
ImproveIndependent data accessVSAvoidResponse efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system merges redundant data requests from multiple groups into single consolidated vendor calls. This consolidation maintains the adaptability and versatility of independent data access for each group while significantly improving response efficiency by reducing the total number of network requests and vendor interactions required.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized call management platform serves as an intermediary that preserves independent data access capabilities while optimizing network traffic. It processes and consolidates requests before they reach vendors, thereby maintaining the versatility of individual group access but improving overall response efficiency by eliminating redundant network communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If multiple data requests are made to vendors, then comprehensive data can be obtained, but billing fees increase and network traffic increases

Engineering Contradiction:
ImproveData completenessVSAvoidNetwork traffic
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system merges multiple data requests into consolidated vendor calls while preserving data completeness. By aggregating redundant requests before they reach vendors, the system ensures all necessary data is obtained through fewer, more efficient calls, thereby reducing network traffic and billing fees without compromising information completeness.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized call management platform provides universal access to vendor data for all groups while optimizing network utilization. It handles diverse data requests from multiple sources through a unified processing mechanism, ensuring comprehensive data retrieval with reduced network traffic by consolidating redundant requests.

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

Data Source

PatentUS11290505B1Data processing systems for data request routing
Publication Date: 2022.03.29 BANK OF AMERICA CORP
  • US11290505B1 patent drawing
  • US11290505B1 patent drawing
  • US11290505B1 patent drawing

AI summary

Apparatus and methods for call management is provided. The apparatus may include system architecture comprising a first I/O platform, a processing engine and a second I/O platform. The first I/O platform may receive a call from a calling source and augment the call by pulling data from a calling sources database. The call may then be routed to the processing engine for a determination of whether cached data can satisfy a data request stored in the call. If the cached data cannot respond to the data request in the call, the processing engine may transmit the call to the second I/O platform. The second I/O platform may leverage a vendor data intelligence engine for selecting an appropriate data source to receive the call. The second I/O platform may subsequently format the call for transmission to the appropriate data source and, after the formatting, route the call.