Sensor Activation Circuit for Multi-Unit Device Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security sensors in processing chips are prone to false positive detection, leading to unnecessary activation of countermeasures, which can harm processes or reset devices, due to their high sensitivity and require manual software commands for activation and deactivation, increasing code size and complexity.

Innovation Solution

A method using a sensor activation circuit to determine which code execution unit is executing software code and activate only the associated sensors before execution, deactivating them after completion, ensuring sensors are active only when necessary and without modifying the software code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security sensors are kept activated continuously to detect attacks, then detection capability is improved, but false positive detection increases leading to unnecessary countermeasure activation

Engineering Contradiction:
Improveattack detection capabilityVSAvoidfalse positive detection
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies dynamics by making the sensor activation state changeable rather than fixed. Sensors are dynamically activated only when a code execution unit is executing software code, and deactivated when not executing. This dynamic adjustment resolves the contradiction by maintaining high detection capability during execution while minimizing false positives during idle periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses preliminary action by detecting code execution unit activation before actual code execution begins. The sensor activation circuit receives an indication that a code execution unit is about to execute software code, and activates the associated sensors in advance. This ensures sensors are ready to detect attacks from the moment execution starts, improving detection capability without requiring continuous activation.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If security sensors are activated manually through software commands, then sensor control is achieved, but software code size increases and readability decreases

Engineering Contradiction:
Improvesensor control capabilityVSAvoidsoftware code size
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling the sensor activation circuit to automatically activate and deactivate sensors based on the execution state of code execution units, without requiring manual software commands. The system monitors itself and manages sensor activation autonomously, eliminating the need for software engineers to insert activation/deactivation commands, thus reducing code size and maintaining readability while preserving full sensor control capability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary sensor activation circuit that mediates between the code execution units and the security sensors. This circuit receives indications of code execution unit state and automatically controls sensor activation, serving as an intermediary layer that eliminates the need for software code to directly manage sensor activation, thereby reducing software complexity while maintaining control capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If security sensors are activated without precise timing, then detection coverage is maintained, but computations may occur without required security sensors activated or sensors activated when unneeded

Engineering Contradiction:
Improvesecurity protection coverageVSAvoidcomputation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies feedback by creating a closed-loop system where the sensor activation circuit continuously monitors the execution state of code execution units and adjusts sensor activation accordingly. The circuit receives real-time indications of whether a code execution unit is executing software code and uses this feedback to activate or deactivate associated sensors. This ensures sensors are activated precisely when needed for security protection and deactivated when not needed, maintaining both security coverage and computation efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses preliminary action by activating sensors before code execution begins and deactivating them after execution completes. The sensor activation circuit detects when a code execution unit is about to execute software code and activates the associated sensors in advance, ensuring protection is in place before computations start. This timing precision ensures sensors are activated only when needed, avoiding both security gaps and unnecessary activations that would reduce computation efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11841938B2Method for activating sensors in a multi-unit device
Publication Date: 2023.12.12 THALES DIS FRANCE SA
  • US11841938B2 patent drawing

AI summary

The present invention relates to a method for activating at least one sensor among a plurality of sensors embedded in a multi-unit device, said at least one sensor being configured to detect attacks during an execution by said multi-unit device of a software code comprising computer code instructions, wherein: said multi-unit device comprises at least two code execution units and a sensor activation circuit, and each sensor is associated to one code execution unit, and said method comprising, performed by said sensor activation circuit before execution of a computer code instruction of said software code by one of said code execution units: —determining (S1) the code execution unit configured to execute said instruction, —activating (S2) only the sensors associated with the determined code execution unit.