Kernel Cryptographic Interface for Asynchronous Hardware Offload

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software-based cryptographic mechanisms used in network communication can degrade application performance due to compute-intensive operations, particularly during SSL session establishment and bulk encryption/decryption, leading to slowed system throughput.

Innovation Solution

Implementing a cryptographic framework that allows kernel consumers to request cryptographic functions, with the framework determining whether requests are synchronous or asynchronous and selecting between software and hardware providers to perform these functions, thereby offloading processing overhead from the system processor.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software-based cryptographic mechanisms are used to ensure network security, then security is improved, but system throughput deteriorates due to compute-intensive operations

Engineering Contradiction:
Improvenetwork securityVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts cryptographic operations from the main application processing flow and implements them as separate kernel-level cryptographic providers. This allows cryptographic functions to be performed in the kernel context rather than blocking application-level processing, thereby maintaining security while improving system throughput by preventing cryptographic operations from becoming bottlenecks in the application layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a kernel interface as an intermediary between applications and cryptographic providers. This intermediary layer manages cryptographic operations asynchronously, allowing applications to initiate cryptographic functions without blocking on their completion. The kernel interface coordinates between multiple cryptographic providers and applications, enabling security operations to proceed without degrading overall system performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If cryptographic operations are performed synchronously in the kernel consumer context, then security is maintained, but processing time increases and system performance degrades

Engineering Contradiction:
Improvecryptographic securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements asynchronous cryptographic operations where the kernel interface prepares and queues cryptographic requests in advance without immediately executing them. Cryptographic providers process these queued requests independently, allowing the application to continue processing other tasks while cryptographic operations complete in the background. This preliminary queuing mechanism eliminates blocking delays while maintaining security requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamic scheduling of cryptographic operations through the kernel interface, which can adjust the timing and execution context of cryptographic functions based on system conditions. Instead of rigid synchronous execution, the system dynamically manages cryptographic task scheduling, allowing flexible optimization of processing time while ensuring security operations are completed when needed.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If multiple cryptographic providers are supported to enhance security capabilities, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improvecryptographic function supportVSAvoidframework complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal kernel interface that can work with multiple different cryptographic providers through a standardized abstraction layer. This single interface handles various cryptographic algorithms and providers uniformly, allowing the system to support diverse cryptographic functions without requiring separate interface implementations for each provider. The multi-functional design reduces overall complexity by consolidating interface management in one place.

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

Solution Approach 2:

The patent segments the cryptographic system into distinct modular components: the kernel interface, cryptographic providers, and application consumers. Each component has a specific responsibility and can be independently developed, tested, and maintained. This segmentation allows multiple cryptographic providers to be added without increasing the complexity of the core interface, as each provider is an independent module that interfaces through the standardized kernel interface.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7373504B1Kernel-level cryptographic kernel interface
Publication Date: 2008.05.13 ORACLE AMERICAN INC
  • US7373504B1 patent drawing
  • US7373504B1 patent drawing
  • US7373504B1 patent drawing

AI summary

A method for performing a cryptographic function including calling into an encryption framework to perform the cryptographic function, wherein calling into the encryption framework comprises sending a request to perform the cryptographic function from a kernel consumer, and processing the request and returning the result to the kernel consumer, wherein processing the request comprises determining whether the request is synchronous or asynchronous, and determining which cryptographic provider to use to perform the cryptographic function.