Blockchain Ledger for Tamper-Evident Call Recording

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current call recording systems are vulnerable to tampering and deletion of recorded content by privileged users, leaving no trace of the incident.

Innovation Solution

Implementing a blockchain-based distributed ledger system to record conference call metadata, ensuring that multiple copies of the blockchain are stored across networks, making it difficult to alter or delete the recorded information without consensus from the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to store call recording metadata, then the system is easy to manage and access, but the system becomes vulnerable to tampering and deletion by privileged users

Engineering Contradiction:
Improveease of managementVSAvoiddata integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The centralized database is segmented into a distributed network of nodes, where each node holds a copy of the blockchain ledger. This segmentation eliminates the single point of control that allows privileged users to tamper with data, while maintaining ease of access through the distributed network architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A blockchain intermediary layer is introduced between the call recording system and the storage mechanism. This blockchain acts as a trusted mediator that records all metadata transactions immutably, preventing direct tampering by privileged users while allowing legitimate access through consensus-based validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If metadata is stored in a centralized location, then access control is simple, but the system allows unauthorized alterations without trace

Engineering Contradiction:
Improvesystem complexityVSAvoidtampering vulnerability
Core Design Contradiction:
Device complexityVSObject-affected harmful factors

Solution Approach 1:

The metadata information is copied and distributed across multiple nodes in the network, each maintaining an identical copy of the blockchain ledger. This copying mechanism ensures that no single node can alter data without detection, as changes would need to be propagated to all nodes simultaneously, which is prevented by cryptographic hashing and consensus protocols.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Cryptographic hash functions are applied preliminarily to the metadata before storage, creating a digital fingerprint that verifies data integrity. This preliminary action ensures that any subsequent alteration of the metadata would result in a mismatched hash, making tampering immediately detectable across the distributed network.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If privileged access is granted to administrators, then system management is efficient, but the system becomes susceptible to insider threats

Engineering Contradiction:
Improvemanagement efficiencyVSAvoidinsider threat risk
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The blockchain system implements continuous feedback through cryptographic verification at every transaction step. Even privileged users must have their actions validated by the network's consensus mechanism, providing immediate feedback that prevents unauthorized alterations. This feedback loop maintains management efficiency by allowing legitimate operations while blocking malicious ones.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system uses self-service cryptographic validation where each node independently verifies the authenticity and integrity of metadata transactions without requiring trust in privileged users. This self-service mechanism eliminates insider threat risks by making the system's security independent of individual user integrity, while maintaining efficient processing through parallel validation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10756912B2Distributed ledger and blockchain to confirm validity of call recordings
Publication Date: 2020.08.25 ARLINGTON TECHNOLOGIES LLC
  • US10756912B2 patent drawing
  • US10756912B2 patent drawing
  • US10756912B2 patent drawing

AI summary

A conference call is recorded. For example, a voice conference call between a group of users is recorded. Information about the recording of the conference call is identified. For example, a date, a time, a length, an agenda, and a list of participants are identified for the conference call. A block is added to a blockchain with the information about the recording of the conference call. The blockchain with the information about the recording of the conference call is sent to a distributed ledger. The distributed ledger is where copies of the blockchain are stored on multiple nodes on one or more networks. By having multiple copies distributed in one or more networks, it is much more difficult to remove all the information that the conference call actually took place.