Database Archiving Flow Management via Segmented Queues

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for recording and archiving interactions, such as those in contact centers, face bottlenecks due to multiple archiving servers competing for limited resources, leading to performance degradation and scalability issues as they update and access the same database tables concurrently.

Innovation Solution

A system utilizing a plurality of action queues and archiving information queues, where a rule engine directs recorders to select appropriate queues for archiving operations, allowing for distributed archiving and updating of a global table with completed operations, thereby managing resource competition and improving scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple archiving servers compete for limited resources to update the same database tables, then archiving functionality is provided, but system performance degrades and scalability is limited

Engineering Contradiction:
Improvearchiving throughputVSAvoidsystem performance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the archiving process into distinct phases: data extraction from the database, transformation/archiving processing, and result insertion back to the database. This segmentation allows multiple recorders to operate in parallel without interfering with each other's database access patterns, thereby improving throughput while maintaining performance stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary archiving server that acts as a mediator between recorders and the database. This intermediary handles all database operations centrally, allowing multiple recorders to extract data independently while a single archiving server manages the transformation and insertion processes, eliminating direct competition for database resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple archiving servers update the same database tables concurrently, then archiving operations are performed, but resource competition causes bottlenecks

Engineering Contradiction:
Improvearchiving operation speedVSAvoidresource management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides the archiving operation into independent extraction phases and centralized transformation phases. Each recorder can extract data independently without interfering with others, while the archiving server centrally manages transformation and database insertion, simplifying resource management despite concurrent operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the operational parameters by introducing a single intermediary archiving server that consolidates all database write operations. This parameter change from distributed write access to centralized write access through a single intermediary simplifies resource management while maintaining high archiving operation speed through parallel data extraction.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If a single archiving server handles all archiving operations, then resource competition is reduced, but system scalability is limited

Engineering Contradiction:
Improvesystem stabilityVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the archiving function into distributed data extraction (one function per recorder) and centralized transformation (one archiving server). This segmentation allows the system to scale by adding more recorders without increasing the complexity of the archiving server, as each recorder operates independently with its own extraction logic.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent makes the intermediary archiving server universal by designing it to handle all archiving operations regardless of the number or identity of recorders. The archiving server uses a single thread pool that dynamically manages all extraction and transformation tasks, allowing the system to scale horizontally by adding recorders without proportionally increasing server complexity.

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

Data Source

PatentUS9405786B2System and method for database flow management
Publication Date: 2016.08.02 NICE LTD
  • US9405786B2 patent drawing
  • US9405786B2 patent drawing
  • US9405786B2 patent drawing

AI summary

A system and method for database flow management may include a rule engine which may examine information related to an interaction; select an action queue from the plurality of action queues; and store, in the selected action queue, archiving information related to the interaction. A recorder may select an action queue from the plurality of action queues; extract archiving information from the selected action queue and perform an archiving operation based on the extracted archiving information. The recorder may update an archiving information queue according to a result of the archiving operation. A unit may examine the plurality of archiving information queues to identify completed archiving operations and update a global table to include completed archiving operations. Other embodiments are described and claimed.