Bidirectional Crypto IO Engine for Secure DMA Transactions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing system architectures lack a comprehensive, cost-effective solution for secure device input/output (IO) operations that ensure confidentiality, integrity, and anti-replay protection for memory transactions across multiple entities, particularly in bi-directional data streams.

Innovation Solution

A bi-directional cryptographically secure IO protocol using a specialized IO crypto engine (ICE) and trusted execution environment (TEE) ensures secure DMA transactions by employing metadata with replay counters and globally unique identifiers, enabling stateless encryption and decryption of data streams while maintaining integrity and confidentiality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If comprehensive security measures are implemented for all IO operations, then security strength is improved, but device complexity and cost increase

Engineering Contradiction:
Improvesecurity strengthVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal security protocol that handles both read and write operations through the same cryptographic mechanism. The bi-directional secure IO protocol enables a single security framework to protect multiple types of IO operations (read, write, DMA) without requiring separate security subsystems for each operation type, thereby reducing overall system complexity while maintaining comprehensive security coverage

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent establishes security parameters, cryptographic keys, and protocol configurations in advance before actual IO operations occur. By pre-configuring security measures including replay protection mechanisms and entity authentication frameworks, the system avoids the need for complex runtime security decision-making, reducing operational complexity while ensuring consistent security enforcement across all devices

Inventive Principle:
Principle #10Preliminary action

2Reliability

If strong cryptographic security is applied to all devices, then confidentiality and integrity are improved, but cost effectiveness deteriorates

Engineering Contradiction:
Improveconfidentiality and integrityVSAvoidcost effectiveness
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent employs a universal security protocol that provides strong cryptographic protection (confidentiality via encryption, integrity via authentication) through a single standardized mechanism applicable to all devices. This eliminates the need for device-specific security implementations, reducing development and manufacturing costs while maintaining uniform high-security standards across the entire system

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses configurable security parameters including selectable cryptographic algorithms, key lengths, and protocol options that can be adjusted based on specific device requirements and threat models. This flexibility allows the system to apply appropriate security strength for each use case without over-engineering, optimizing the balance between security strength and implementation cost across different device types

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple entities are granted access to IO streams, then system versatility is improved, but security management complexity increases

Engineering Contradiction:
Improvemulti-entity access capabilityVSAvoidsecurity management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides IO streams into distinct secured channels, each with its own security context, authentication credentials, and access control policies. This segmentation allows multiple entities to access different portions of the IO stream simultaneously with appropriate security measures applied to each segment, preventing cross-contamination of security contexts and simplifying the management of multi-entity access through clear spatial separation of security domains

Inventive Principle:
Principle #1Segmentation

4Reliability

If replay protection mechanisms are implemented, then anti-replay security is improved, but processing overhead increases

Engineering Contradiction:
Improveanti-replay protectionVSAvoidprocessing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent pre-generates and caches replay protection tokens, sequence numbers, and cryptographic nonces before actual IO operations. By having these replay protection parameters ready in advance, the system can perform rapid token comparison and validation during operations without requiring complex real-time cryptographic computations, thereby maintaining strong anti-replay protection while minimizing processing overhead and preserving throughput

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10225247B2Bidirectional cryptographic IO for data streams
Publication Date: 2019.03.05 TAHOE RES LTD
  • US10225247B2 patent drawing
  • US10225247B2 patent drawing
  • US10225247B2 patent drawing

AI summary

Various configurations and techniques for enabling bidirectional cryptographic input output (IO) operations with an IO device of a computing system are disclosed herein. In an example, electronic operations of a computing system to enable a secure direct memory access (DMA) transaction including writing information to enable the secure DMA transaction to memory, reading and verifying the information from memory, performing encryption of data from the IO device using the information from memory, and writing encrypted secure data for the secure DMA transaction to the memory. In a further example, the information to enable the secure DMA transaction may include a counter value written by authorized software, and encrypting the secure data using the counter value, to prevent replay of the secure encrypted data by software other than the authorized software.