Inline Cryptographic Engine for Peripheral Interface Controller

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Peripheral interface data is vulnerable to observation and unauthorized access, and existing technologies lack effective encryption solutions that do not increase latency or require awareness from connected devices.

Innovation Solution

Incorporating an inline cryptographic engine within a peripheral interface controller to transparently encrypt data transmitted over peripheral interfaces and decrypt data received, while maintaining encryption keys secure within a system-on-a-chip (SOC) or attached memory, supporting both encryption and address translation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is transmitted over peripheral interfaces, then communication between components is enabled, but data becomes vulnerable to observation and unauthorized access

Engineering Contradiction:

Improvecommunication capabilityVSAvoiddata security vulnerability

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary encryption layer between the data source and peripheral interface. The encryption engine acts as a mediator that transforms readable data into encrypted form before transmission, and decrypts incoming data. This intermediary mechanism protects data security while maintaining communication functionality, as the encryption/decryption process occurs transparently within the controller without affecting the communication capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If encryption is implemented for data transmission, then data security is improved, but latency increases

Engineering Contradiction:

Improvedata securityVSAvoidencryption latency

Core Design Contradiction:

Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring the encryption engine with encryption keys and algorithms before data transmission begins. The encryption context is established in advance, allowing data to be encrypted immediately upon arrival without setup delays. This preliminary preparation minimizes latency while maintaining security.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The encryption engine operates continuously during data transmission, processing data in real-time as it flows through the peripheral interface controller. Rather than batching or pausing for encryption operations, the system maintains continuous encryption/decryption action, ensuring that the security function does not interrupt the data flow and minimizing latency.

Inventive Principle:

Principle #20Continuity of useful action

3Object-affected harmful factors

If encryption is implemented for data transmission, then data security is improved, but device complexity increases

Engineering Contradiction:

Improvedata securityVSAvoidcontroller complexity

Core Design Contradiction:

Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The peripheral interface controller is designed with multi-functionality, integrating both encryption/decryption capabilities and address translation functions within a single device. The encryption engine is embedded within the existing controller architecture, allowing it to perform multiple functions (data security and address management) rather than requiring separate dedicated hardware for each function. This reduces overall system complexity while maintaining security.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If encryption keys are stored externally, then key management flexibility is improved, but security is worsened

Engineering Contradiction:

Improvekey management flexibilityVSAvoidkey security

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements a nested structure where encryption keys are stored within the secure memory space of the peripheral interface controller, which itself is part of the broader system architecture. The keys are nested within the controller's protected memory region, accessible only through controlled interfaces. This nesting provides security by placing keys within a protected environment while maintaining flexibility through the controller's interface management capabilities.

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS9256551B2Embedded encryption/secure memory management unit for peripheral interface controller

Publication Date: 2016.02.09 APPLE INC

AI summary

In an embodiment, a peripheral interface controller may include an inline cryptographic engine which may encrypt data being sent over a peripheral interface and decrypt data received from the peripheral interface. The encryption may be transparent to the device connected to the peripheral interface that is receiving/supplying the data. In an embodiment, the peripheral interface controller is included in a system on a chip (SOC) that also includes a memory controller configured to couple to a memory. The memory may be mounted on the SOC in a chip-on-chip or package-on-package configuration. The unencrypted data may be stored in the memory for use by other parts of the SOC (e.g. processors, on-chip peripherals, etc.). The keys used for the encryption/decryption of data may remain within the SOC.