Object Detection Robustness Certification Using Cross Lipschitz Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for quantifying the robustness of object detection models are computationally intensive and lack a clear, sample-by-sample definition of local robustness, particularly for models producing bounding boxes with probability distributions, and do not account for adversarial attacks effectively.

Innovation Solution

A method using cross Lipschitz-ness functions integrated into the CLEVER framework to quantify robustness by defining specific requirements for object detection models, reducing computational complexity and providing reliable certification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If heuristic search approach is used to quantify robustness, then robustness can be measured, but computation resource requirement becomes very large

Engineering Contradiction:
Improverobustness measurementVSAvoidcomputation resource
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent extracts and focuses computation only on the bounding box coordinates output by the object detection model, rather than performing exhaustive heuristic searches on the entire input space. By taking out only the critical output parameters (bounding box coordinates) and analyzing their sensitivity to input perturbations, the method achieves robustness measurement with significantly reduced computational resources.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the measurement parameters from global metrics (like mAP) to local parameters by computing the Jacobian matrix of the neural network output with respect to input at specific test samples. This parameter transformation enables sample-by-sample robustness quantification and reduces the need for large-scale heuristic searches.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If batch-wise mAP metric is used, then global robustness can be assessed, but sample-by-sample robustness cannot be quantified

Engineering Contradiction:
Improveglobal robustnessVSAvoidlocal robustness information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent segments the robustness assessment into individual sample-level evaluations by computing the Jacobian matrix for each test sample independently. This segmentation allows the method to quantify robustness for each sample separately, preserving local robustness information that would be lost in batch-wise aggregation. The overall robustness can then be aggregated from individual sample measurements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent replaces the mechanical batch-wise evaluation process with a differential calculus approach, using Jacobian matrices to capture local sensitivity. This substitution enables continuous, fine-grained robustness measurement at the sample level, providing both local and global robustness information without requiring large batches.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If arbitrary mAP threshold is used for certification, then simple decision can be made, but theoretical guarantees are lacking

Engineering Contradiction:
Improvecertification decisionVSAvoidtheoretical guarantee
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces feedback by using the computed Jacobian matrix to determine an adaptive perturbation magnitude based on the actual sensitivity of the model output. Instead of using arbitrary fixed thresholds, the method adjusts the perturbation scale according to the measured sensitivity, providing theoretically grounded certification decisions that adapt to the specific model and test sample.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary computation of the Jacobian matrix and sensitivity analysis before making the certification decision. By pre-computing the local sensitivity characteristics, the method establishes theoretical bounds on robustness that inform the certification threshold, replacing arbitrary decisions with theoretically justified ones.

Inventive Principle:
Principle #10Preliminary action

4Measurement precision

If deep neural networks are used for object detection, then detection accuracy is improved, but robustness certification becomes computationally intensive

Engineering Contradiction:
Improvedetection accuracyVSAvoidcertification complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the essential output parameters (bounding box coordinates) from the deep neural network and focuses the certification analysis on these extracted parameters. By taking out only the critical coordinates and ignoring redundant internal computations, the method simplifies the certification process while maintaining accuracy for deep network models.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the certification parameters from global performance metrics to local sensitivity parameters (Jacobian matrix elements) that can be efficiently computed even for deep networks. This parameter transformation reduces certification complexity from requiring thousands of forward passes to a single forward pass with gradient computation, making it feasible for deep architectures.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260112153A1Automatically quantifying a robustness of an object detection model applied for a controlling task and/or a monitoring task
Publication Date: 2026.04.23 SIEMENS AG
  • US20260112153A1 patent drawing
  • US20260112153A1 patent drawing
  • US20260112153A1 patent drawing

AI summary

A method for automatically quantifying a robustness of an object detection model applied for a controlling task and/or a monitoring task is provided, including—receiving the object detection model which is trained to output a predicted object in terms of a location in an image data and of an object class out of a set of object classes when the image data is input into the object detection model, —applying a set of robustness requirements to the object detection model, —deriving from each robustness requirement a cross Lipschitz-ness function, —determining a robustness value of the object detection model deviating from the un-perturbed image data of the image data, —comparing the determined robustness value with a predefined robustness threshold value, and—outputting a positive certification for applying the object detection model in the controlling task and/or the monitoring task if the robustness value is below the predefined robustness threshold value.