Interactive Voice Response Auto-Scaling with Session-Aware Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Scaling discrete customer interaction sessions in a cloud computing environment poses challenges in maintaining security and flexibility while implementing a stateless cloud environment for interactive voice response systems.

Innovation Solution

A system and method for distributing discrete events into a stateless server cloud provider architecture, involving load balancer registration of new servers, monitoring active sessions, and dynamically scaling up or down by adding or removing servers based on session thresholds, ensuring stateful operation without compromising security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If servers are dynamically added or removed in a stateless cloud environment, then system scalability and resource efficiency are improved, but session continuity and security are compromised

Engineering Contradiction:
Improvesystem scalabilityVSAvoidsession continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a load balancer as an intermediary component between the cloud infrastructure and IVR servers. The load balancer maintains session state information and manages server registration/deregistration, acting as a mediator that decouples the stateless cloud environment from the stateful IVR session requirements. This allows servers to be dynamically added or removed while the load balancer maintains session continuity by redirecting traffic appropriately.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the IVR architecture into distinct components: cloud infrastructure, load balancer, and IVR servers. This segmentation allows the stateless cloud layer to independently scale servers while the load balancer layer maintains session state, resolving the contradiction between scalability and session continuity by distributing different functions across separate layers.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a stateless cloud architecture is used for IVR systems, then security and flexibility are improved, but the ability to maintain discrete session state is worsened

Engineering Contradiction:
Improvesystem flexibilityVSAvoidsession state
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The load balancer serves as an intermediary that retains session state information in a stateless cloud environment. It maintains mapping between session identifiers and active servers, preventing loss of session state information while allowing the underlying cloud infrastructure to remain stateless and flexible.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the load balancer continuously monitors server status and session information. When servers are added or removed, the load balancer receives feedback about the changed configuration and adjusts session routing accordingly, preventing session state loss through active monitoring and dynamic adaptation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12445555B2Systems and methods for interactive voice response auto-scaling
Publication Date: 2025.10.14 HOME DEPOT PRODUCT AUTHORITY LLC
  • US12445555B2 patent drawing
  • US12445555B2 patent drawing
  • US12445555B2 patent drawing

AI summary

Systems and methods for distributing discrete events into a stateless cloud provider architecture are disclosed. Certain embodiments involve receiving, by the load balancer, a scaling up indication for the IVR system, the scaling up indication comprising an identification of a new server to be added to the plurality of servers. The method involves responsive to receiving the scaling up indication, registering the new server for IVR traffic by the load balancer. The method includes after registering the new server, receiving an IVR event. The method includes distributing the IVR event to the new server.