Database Server Storing Call Session Data for Telephony Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telephony systems, call session information is typically discarded after a call session, leading to redundant IVR applications and processes, which results in inefficiencies and frustration for callers who must re-enter authentication information across multiple call sessions.
Innovation Solution
Implementing a database server to store call session information, generating a unique identifier for each session, and replicating this information across sessions, allowing for centralized management and reuse of call data, thereby reducing redundant IVR applications and processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If call session information is discarded after each call session, then system memory usage is reduced and security is improved, but callers must re-enter authentication information across multiple call sessions causing frustration and inefficiency
Solution Approach 1:
The system performs preliminary action by storing authentication information and call session data in a database server during the first call session. This pre-stored information is then retrieved and used in subsequent call sessions, eliminating the need for callers to re-enter authentication details and resolving the contradiction between security/memory management and operational ease.
2Productivity
If call session information is stored in a database server for reuse across sessions, then operational efficiency is improved and redundant IVR processes are reduced, but system complexity and data security risks increase
Solution Approach 1:
The patent introduces a database server as an intermediary component between IVR servers and call session data. This mediator enables centralized storage and retrieval of authentication information across multiple IVR servers without requiring complex point-to-point communication protocols, thus improving productivity while managing system complexity through a standardized interface.
3Reliability
If multiple IVR servers are deployed to handle different call sessions, then system reliability and scalability are improved, but redundant IVR applications and processes increase operational overhead
Solution Approach 1:
The database server implements universality by serving as a shared resource for multiple IVR servers. Instead of each IVR server maintaining separate authentication data, the universal database stores call session information that can be accessed by any IVR server, enabling reliable call session continuity across multiple servers while eliminating redundant storage and processing of the same authentication information.
Data Source
AI summary
In an example of this disclosure, a method may include receiving, by a database server, a data write request. The data write request may include authentication information corresponding to a first call session and first additional information. The method may include generating, by the database server, a first unique identifier based on the first additional information. The authentication information may correspond to the first unique identifier. The method may include storing the first unique identifier and the authentication information in a data structure in a memory of the database server.