Adaptive Access Control for Hardware Blocks via Dynamic Key Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed computing systems face complexity in configuring access control mechanisms, often requiring centralized supervision and static resource allocation, which limits dynamic resource management and increases synchronization complexities.

Innovation Solution

Implementing adaptive access control by determining the current access owner and processing memory access commands based on domain masks associated with the master side entity, invalidating existing keys when ownership changes, and updating the current access owner, allowing for dynamic resource allocation and reduced synchronization complexities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized supervisor or administrator is used to manage access control, then security and access control are improved, but device complexity and configuration difficulty increase

Engineering Contradiction:
Improveaccess control securityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hardware block automatically determines the current access owner by examining the entity ID in incoming commands and autonomously selects appropriate keys from storage based on the domain mask, eliminating the need for centralized supervisor management and reducing configuration complexity while maintaining security

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The access control mechanism dynamically adapts to different master side entities by changing the current access owner based on the entity ID, allowing the system to automatically adjust which keys are used for encryption/decryption without manual reconfiguration, thereby reducing configuration difficulty while maintaining security

Inventive Principle:
Principle #15Dynamics

2Device complexity

If static resource allocation is used, then device complexity is reduced, but adaptability and dynamic resource management capability are worsened

Engineering Contradiction:
Improveresource allocation simplicityVSAvoiddynamic resource allocation capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system dynamically allocates hardware block access to different master side entities by determining the current access owner based on the entity ID in incoming commands and selecting appropriate keys from storage, enabling flexible resource allocation without increasing device complexity

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The hardware block can serve multiple master side entities by storing multiple keys in the key storage unit and selectively using them based on the domain mask and current access owner, making the hardware block universal and adaptable to different entities without requiring separate dedicated blocks for each

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

Data Source

PatentUS10176139B2Adaptive access control for hardware blocks
Publication Date: 2019.01.08 QUALCOMM INC
  • US10176139B2 patent drawing
  • US10176139B2 patent drawing
  • US10176139B2 patent drawing

AI summary

System and method for providing adaptive access to a hardware block on a computer system. In one embodiment, a method includes receiving a first access request and a second access request with an access controller, wherein the second access request is received sequentially after the first access request, and the first access request includes a first master identification and the second access request includes a second master identification, determining if the second master identification is equal to the first master identification, providing access to the second access request if the second master identification is equal to the first master identification, wherein the first master identification is associated with one or more hardware block interface values, invalidating the one or more hardware block interface values associated with the first master identification if the second master identification is not equal to the first master identification, and associating the one or more hardware block interface values with the second master identification and a corresponding privilege.