Control Data Initialization Using Local or Memory-Based Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data processing systems face inefficiencies in handling control data, as existing methods require software to determine whether control data is stored in memory or local storage, leading to complexities and performance issues depending on data volume, especially for devices like memory management units that need to manage varying amounts of control data across different contexts or devices.

Innovation Solution

A method where an identification value determines whether to allocate memory space for control data or use a preset address for local storage, allowing transparent access and optimizing storage based on data requirements, with the identification value set during manufacture or initialization, ensuring consistent programming interfaces regardless of storage location.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If control data is stored in memory, then storage capacity is sufficient for large data volumes, but access speed decreases and system complexity increases

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The patent segments control data into two categories: small control data stored in fast local storage within the device, and large control data stored in slower memory. The identification value determines which category applies, allowing the system to optimize between speed and capacity based on data size requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different storage solutions for different types of control data. Small control data gets priority placement in local storage for fast access, while large control data is accommodated in memory. This creates localized optimization where each storage location is used for the type of data it handles most efficiently.

Inventive Principle:
Principle #3Local quality

2Speed

If control data is stored in local storage, then access speed improves, but storage capacity is limited for large data volumes

Engineering Contradiction:
Improveaccess speedVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments control data into two categories: small control data stored in fast local storage within the device, and large control data stored in slower memory. The identification value determines which category applies, allowing the system to optimize between speed and capacity based on data size requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different storage solutions for different types of control data. Small control data gets priority placement in local storage for fast access, while large control data is accommodated in memory. This creates localized optimization where each storage location is used for the type of data it handles most efficiently.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If software determines storage location, then flexibility is improved, but system complexity and processing overhead increase

Engineering Contradiction:
ImproveflexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring the identification value during device initialization or manufacture to indicate the storage location of control data. This eliminates the need for software to determine storage location at runtime, as the information is already encoded in the identification value, thereby reducing system complexity while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If memory allocation is performed, then storage flexibility is improved, but processing time and system overhead increase

Engineering Contradiction:
Improvestorage flexibilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring the identification value during device initialization or manufacture to indicate the storage location of control data. This eliminates the need for software to determine storage location at runtime, as the information is already encoded in the identification value, thereby reducing system complexity while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11009841B2Initialising control data for a device
Publication Date: 2021.05.18 ARM LTD
  • US11009841B2 patent drawing
  • US11009841B2 patent drawing
  • US11009841B2 patent drawing

AI summary

A method for initialising control data for a device comprises determining whether an identification value stored in a control storage location of the device has a first value or second value. When the identification value has the first value, space is allocated in the memory for storing the control data and an address of the allocated space in memory is written to a control data pointer storage location of the device. When the identification value has the second value, the allocation of space in memory is omitted and the control data pointer storage location comprises a preset address indicative of a location for storing the control data in local storage provided within the device.