Resource Domain Controller for Secure Peripheral Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data processing systems lack a dynamic and secure method to configure access permissions for peripheral devices, as generic data processors often require flexible control over accessing various peripherals, necessitating a solution to prevent unauthorized access.

Innovation Solution

Implementing a resource domain controller that groups data processors and peripherals into logical domains, where access requests are authorized only if the requesting data processor and target peripheral belong to the same resource domain, using interconnects and access controllers to enforce domain membership and restrict access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data processors are designed to be generic for use across multiple applications, then adaptability is improved, but security control over peripheral access deteriorates

Engineering Contradiction:
ImproveadaptabilityVSAvoidsecurity control
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the monolithic access control function into hierarchical levels: application-level policies define which data processors can access which peripherals, while the interconnect enforces these policies by segmenting access paths. This allows generic data processors to maintain adaptability while security is enforced through segmented policy enforcement points throughout the access path.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control mechanism between data processors and peripherals. The interconnect acts as a mediator that intercepts access requests, evaluates them against stored policies, and either permits or blocks access. This intermediary layer enables security control without restricting the generic nature of data processors.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If dynamic configuration of access permissions is implemented, then ease of operation is improved, but device complexity increases

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements dynamic access control policies that can be configured and modified without hardware changes. Policies are stored in reconfigurable memory structures within the interconnect, allowing runtime modification of access permissions. This dynamic configuration capability improves ease of operation while the modular policy storage structure manages complexity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent utilizes parameter changes in the form of configurable policy attributes stored in the interconnect. Access policies are defined by parameters such as data processor identifiers, peripheral identifiers, and access permissions. These parameters can be dynamically modified to change access behavior without altering the underlying hardware architecture, balancing ease of operation with manageable complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9830295B2Resource domain partioning in a data processing system
Publication Date: 2017.11.28 NXP USA INC
  • US9830295B2 patent drawing
  • US9830295B2 patent drawing
  • US9830295B2 patent drawing

AI summary

A resource domain controller in a data processing system stores information that is used to group various resources, such as bus masters and peripherals, into common domains. Each group can be referred to as a resource domain and can include one or more data processor and peripheral devices. The resource domain information is then used to determine whether a particular access request from a data processor is authorized to access its intended target, e.g., one of the peripheral devices, by determining whether the access request and the intended target each belong to a common resource domain. If so, the access request is allowed, otherwise the access request is prevented from being successfully completed.