Recording Device Audit Tagging for Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current recording devices for security agencies lack efficient mechanisms for real-time data auditing and metadata management, particularly in identifying and prioritizing critical events, which can lead to data loss or corruption during storage and transfer.

Innovation Solution

The implementation of a system where recording devices generate and transmit metadata as audit tags, categorized as urgent or non-urgent, to a server for immediate notification and data prioritization, ensuring the integrity and timely retrieval of critical event data through cryptographic protection and real-time data transfer protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If recording devices store all recorded data locally without auditing mechanisms, then data storage capacity is maximized, but data integrity and reliability deteriorate due to potential loss or corruption

Engineering Contradiction:
Improvedata integrityVSAvoidauditing mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the auditing function from the main recording device by implementing a separate server system that receives and verifies audit tags. This separation allows the recording device to maintain data integrity through auditing without bearing the full complexity of the auditing infrastructure, thus improving reliability while managing device complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces audit tags as intermediary elements that mediate between the recording device and the server. These metadata tags carry verification information without requiring complex direct communication protocols, simplifying the auditing mechanism while ensuring data integrity through cryptographic verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If real-time auditing and verification mechanisms are implemented, then data integrity is improved, but processing time and system complexity increase

Engineering Contradiction:
Improvedata verification accuracyVSAvoiddata transfer and verification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by generating and attaching cryptographic audit tags to data packets before transmission. This pre-verification approach allows the server to quickly validate data integrity without performing complex verification operations after receipt, thus improving verification accuracy while minimizing time loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter of verification from post-transmission complex checking to pre-transmission cryptographic tagging. By transforming the verification mechanism into compact cryptographic parameters embedded in audit tags, the system achieves high verification accuracy with minimal processing time.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If cryptographic protection is applied to all data, then security and data integrity are improved, but processing speed and energy consumption increase

Engineering Contradiction:
Improvedata securityVSAvoidenergy consumption for cryptographic operations
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies local quality by implementing cryptographic protection selectively rather than uniformly. Audit tags containing cryptographic verification data are applied only to specific data packets that require verification, rather than encrypting all data. This localized approach maintains data security for critical information while reducing overall energy consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses disposable cryptographic hash values in audit tags instead of complex ongoing encryption. These lightweight cryptographic parameters provide sufficient security verification without the high energy cost of continuous cryptographic operations, making security maintenance more energy-efficient.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

4Reliability

If all recorded data is transferred to server immediately, then data centralization and management are improved, but network bandwidth consumption and transfer time increase

Engineering Contradiction:
Improvedata centralizationVSAvoiddata transfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential verification information (audit tags) from the full data packets for immediate server processing. This selective extraction allows the server to begin verification and centralization processes without waiting for complete data transfers, improving data centralization while reducing transfer time requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by transferring audit tags before the corresponding full data packets. This allows the server to prepare verification processes and begin data centralization in advance, reducing the overall time required for complete data transfer and centralization while maintaining data integrity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11995734B2Auditing recorded data from a recording device
Publication Date: 2024.05.28 AXON ENTERPRISE INC
  • US11995734B2 patent drawing
  • US11995734B2 patent drawing
  • US11995734B2 patent drawing

AI summary

A recording device may record information continuously. Particular events which occur during recording may be of interest for review (e.g., audit, inspection). Events may be audited to ensure that the data gathered is not tampered with or corrupted and to provably establish an evidence chain of custody. Metadata may mark recorded data of an event, in whole or in part, for later review. Metadata may be identified as an audit tag which may identify particular occurrences during an event. An audit tag may be urgent or non-urgent. Notice of an urgent audit tag may be sent to a server prior to sending the recorded data associated with the audit tag. Recorded data may be cryptographically signed to protect the recorded data from tampering.