Trigger-Driven Parameter Block Transfer for Register Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Firmware in active devices, such as implantable medical devices, faces significant overhead and synchronization challenges when changing operating parameters in registers, leading to inefficiencies in controlling components like stimulation engines.
Innovation Solution
A block moving hardware-based controller is introduced to move blocks of operating parameter data from memory to registers, utilizing trigger inputs and navigation data to manage block sizes and skipping intervals, thereby relieving firmware of data transfer responsibilities and maintaining synchronization with component operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If firmware is used to change operating parameters in registers, then the device can be controlled, but firmware overhead increases and synchronization becomes complex
Solution Approach 1:
The patent extracts the data transfer function from firmware and implements it in dedicated hardware (block moving controller). The hardware automatically moves blocks of parameter data from memory to registers when triggered, removing this burden from firmware and reducing overhead while maintaining full control capability.
Solution Approach 2:
The patent introduces a block moving controller as an intermediary component between memory and registers. This hardware mediator automatically handles data transfer and synchronization, eliminating the need for firmware to manage these operations directly, thus reducing firmware complexity while preserving control functionality.
2Manufacturing precision
If firmware synchronizes parameter changes with component operation, then timing accuracy is improved, but firmware becomes overburdened
Solution Approach 1:
The patent extracts the synchronization function from firmware and implements it in hardware. The block moving controller is triggered by component operation signals and automatically synchronizes parameter updates with component timing, maintaining precision while freeing firmware for other tasks.
Solution Approach 2:
The hardware block moving controller is self-sufficient in handling synchronization. It receives triggers from component operations and autonomously performs the data transfer and timing coordination without requiring firmware intervention, enabling firmware to focus on higher-level control functions.
3Manufacturing precision
If manual block size management is implemented, then data transfer accuracy is improved, but control complexity increases
Solution Approach 1:
The block moving controller automatically determines and manages block sizes based on pre-stored block navigation data in memory. The hardware self-manages the segmentation and transfer of parameter blocks without requiring firmware to calculate or control block boundaries, maintaining precision while reducing control complexity.
Data Source
AI summary
A hardware based block moving controller of an active device such as an implantable medical device that provides electrical stimulation reads a parameter data from a block of memory and then writes the parameter data to a designated register set of a component that performs an active function. The block of memory may include data that specifies a size of the block of memory to be moved to the register set. The block of memory may also include data that indicates a number of triggers to skip before moving a next block of memory to the register set. A trigger that causes the block moving controller to move the data from the block of memory to the register set may be generated in various ways such as through operation of the component having the register set or by a separate timer.