Hardware Identifier Filtering to Reduce Controller Processor Load
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing controller node networks experience increased processor load due to unnecessary interrupt requests caused by irrelevant identifiers, which are typically handled by software, leading to inefficiencies.
Innovation Solution
Implementing a hardware-based identifier filter within controller nodes to determine relevance of identifiers and perform tasks only for relevant identifiers, thereby reducing processor load and simplifying software architecture.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software-based identifier evaluation is used in interrupt request handlers, then controller nodes can process all incoming identifiers, but processor load increases due to handling irrelevant identifiers
Solution Approach 1:
The patent replaces the software-based identifier evaluation mechanism with a hardware-based identifier filter. This hardware filter automatically compares incoming identifiers against allocated identifiers for the controller node and generates interrupt requests only for relevant identifiers, eliminating the need for software to process irrelevant identifiers and thereby reducing processor load.
2Reliability
If all identifiers are processed by software interrupt handlers, then no identifiers are lost, but software complexity and processing time increase
Solution Approach 1:
The patent replaces the software interrupt handler mechanism with a hardware-based identifier filter that performs automatic identifier comparison and selective interrupt generation. This hardware mechanism ensures reliable handling of relevant identifiers while simplifying the software architecture by eliminating the need for software to evaluate all incoming identifiers.
Solution Approach 2:
The hardware identifier filter acts as an intermediary component between the communication interface and the controller node processor. It receives all incoming identifiers, filters them against allocated identifiers, and only passes relevant identifiers to the processor via interrupt requests, thereby reducing both complexity and processing requirements.
3Measurement precision
If software processes every incoming identifier, then accurate relevance determination is achieved, but response time decreases due to increased computation work
Solution Approach 1:
The patent replaces software-based identifier evaluation with a hardware-based identifier filter that performs parallel comparison of incoming identifiers against allocated identifiers. This hardware implementation achieves accurate relevance determination through simultaneous bit-wise comparison while dramatically reducing processing time compared to sequential software evaluation.
Solution Approach 2:
The controller node is pre-configured with allocated identifiers stored in the hardware filter before operation begins. This preliminary configuration enables the hardware filter to immediately compare incoming identifiers against the pre-loaded allocated identifiers without requiring real-time software intervention, thus achieving fast and accurate relevance determination.
Data Source
AI summary
A controller node (112) is presented. The controller node (112) is configured for being connected to at least one further controller node (112) via a communication interface (114) transferring signals between a plurality of controller nodes (112). The signals comprise identifiers. The controller node (112) comprises an identifier filter (120). The identifier filter (120) is a hardware filter device. The identifier filter (120) is configured for receiving an identifier sent by a further controller node (112), deciding if the identifier is relevant for the controller node (112) and, if the identifier is relevant for the controller node (112), performing a task relating to the identifier. Further, a method for filtering identifiers, a controller node network (110) and a use of the controller node (112), the method for filtering identifiers or the controller node network (110) are presented.


