Private Blockchain Storage for Verifiable Contact Center Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing contact center engagement data storage solutions lack trust and verification, as they rely on a single entity that may modify or delete data, which is undesirable for multi-party access and compliance with legal mandates.
Innovation Solution
Storing engagement recordings and metadata in a private blockchain that ensures data integrity through cryptographic hashing and digital signatures, allowing only authorized parties to access and modify data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If engagement data is stored in a centralized database, then data accessibility and ease of operation are improved, but data integrity and trust deteriorate because a single entity can modify or delete data
Solution Approach 1:
The system segments data storage from centralized database to distributed blockchain network, where data is stored across multiple nodes. This segmentation eliminates single point of failure and prevents unauthorized modification while maintaining accessibility through decentralized access mechanisms.
Solution Approach 2:
The patent introduces blockchain as an intermediary layer between data storage and access mechanisms. The blockchain acts as a trusted mediator that ensures data integrity through cryptographic hashing and consensus mechanisms while maintaining operational accessibility for authorized parties.
2Ease of operation
If data is stored in a centralized database, then ease of operation is improved, but trust and verification capabilities deteriorate as multiple parties cannot verify data authenticity
Solution Approach 1:
The system implements feedback mechanisms through cryptographic verification where each block contains a hash of the previous block, creating a chain of verification. This feedback loop allows multiple parties to verify data authenticity independently while maintaining ease of access through the distributed network.
Solution Approach 2:
Blockchain serves as a trusted intermediary that enables verification without requiring direct trust between parties. The decentralized ledger provides a common reference point that all authorized parties can verify, eliminating information loss while maintaining operational ease.
3Reliability
If a private blockchain is used for data storage, then data integrity and trust are improved, but device complexity increases
Solution Approach 1:
The patent applies local quality by implementing selective accessibility control where different users have different levels of access to blockchain data. This allows the system to maintain high data integrity through the blockchain while reducing complexity by only requiring cryptographic verification capabilities where needed, rather than full blockchain participation.
Solution Approach 2:
The system uses cryptographic copying mechanisms where data is replicated across multiple blockchain nodes. This copying approach maintains data integrity through distribution while managing complexity by using efficient cryptographic hashing that can be verified without requiring full data replication at every node.
4Ease of manufacture
If centralized storage is used, then ease of manufacture and implementation are improved, but adaptability for multi-party access and compliance deteriorates
Solution Approach 1:
The patent implements dynamics by enabling flexible access control mechanisms on the blockchain where permissions can be dynamically adjusted for different users and parties. This dynamic access control maintains implementation simplicity through standardized blockchain protocols while providing high adaptability for various multi-party scenarios and compliance requirements.
Data Source
AI summary
A server of a contact center generates an engagement recording and engagement metadata associated with a contact center engagement. The engagement metadata identifies one or more user devices and one or more business servers. The server stores the engagement recording and the engagement metadata in a block of a private blockchain. The block includes a cryptographic hash of a previous block in the private blockchain, the engagement recording, and the engagement metadata. The server provides access to the block to the one or more user devices and the one or more business servers.