Safety Controller Firmware Update With Device-Specific Activation Codes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Firmware updates for safety controllers in automation technology are complex and costly, especially for installed devices, as they require manufacturer intervention to ensure safety compliance, limiting user flexibility and increasing logistical complexity.

Innovation Solution

A method involving a device-specific authorization check and activation code system, where a manufacturer-provided enabling device generates a signed device file and activation code, allowing secure and controlled firmware updates through a user-side updating device, ensuring trackability and reducing logistical complexity and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware updates are performed by the device manufacturer in compliance with safety requirements, then safety and security are ensured, but logistical complexity and costs increase significantly

Engineering Contradiction:
Improvesafety complianceVSAvoidlogistical complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the firmware update process into distinct functional segments: the enabling device on the manufacturer's side handles authorization and code generation, while the updating device on the user's side performs the actual update execution. This segmentation allows safety-critical functions to remain centralized while distributing the operational burden, thereby reducing logistical complexity without compromising safety compliance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary activation code as a mediator between the manufacturer's enabling device and the user's updating device. This code serves as a secure token that carries authorization information, enabling the user-side device to perform firmware updates without direct manufacturer involvement in each update operation. The intermediary mechanism maintains security and traceability while eliminating the need for complex manufacturer-logistics infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If firmware updates require manufacturer intervention, then safety requirements are met, but user flexibility and operational ease deteriorate

Engineering Contradiction:
Improvesafety complianceVSAvoiduser flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The manufacturer performs preliminary actions by generating the activation code in advance through the enabling device. This code encapsulates all necessary authorization and device-specific information, allowing the user's updating device to execute firmware updates independently without requiring real-time manufacturer intervention. The preliminary generation of the activation code maintains safety compliance while significantly improving user flexibility and operational ease.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If device-specific authorization checks are performed on the manufacturer's side, then trackability and security improve, but system complexity increases

Engineering Contradiction:
ImprovetrackabilityVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent extracts the complex authorization check logic and device-specific verification functions from the user-side updating device and concentrates them in the manufacturer's enabling device. The enabling device performs comprehensive authorization checks using device data and generates the activation code that encapsulates the results. This extraction reduces the complexity burden on the user's system while maintaining full trackability and security through centralized verification.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11429720B2Method and system for firmware-updating a control device for process control
Publication Date: 2022.08.30 PHOENIX CONTACT GMBH & CO KG
  • US11429720B2 patent drawing
  • US11429720B2 patent drawing
  • US11429720B2 patent drawing

AI summary

For simplifying and/or improving the updating of firmware of a control device, in particular of a safety controller, the invention provides a method and a system for updating firmware, in which a device-specific authorization check for performing a firmware update is performed by the manufacturer, and in case of a successful authorization check a device-specific activation code for performing the firmware update is provided, and for this purpose an enabling device is provided on the manufacturer's side and an updating device connectable to a control device on the user's side. The improvement is that the safe and secure firmware update proceeds under the control and long-term archiving of the manufacturer.The invention furthermore relates to a digital storage medium having instructions stored thereon for use when performing the method according to the invention.