Secure Software Update Transmission via Device-Specific Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for managing software updates on remote devices lack effective protection of proprietary know-how, leading to risks of unauthorized access, software interception, and overproduction for parallel markets, as encryption keys and unique identification parameters are vulnerable to misuse.

Innovation Solution

A system that assigns unique identification parameters and encryption keys to each device, storing them in a protected database, allowing only authorized devices to receive encrypted software updates, preventing unauthorized decryption and ensuring secure transmission and installation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If encryption keys and unique identification parameters are stored on remote devices for software updates, then device autonomy and update speed are improved, but security vulnerabilities increase due to key exposure and unauthorized access risks

Engineering Contradiction:
Improveupdate speedVSAvoidsecurity
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent extracts the encryption keys from the remote devices and stores them exclusively in the protected database on the server. The devices retain only unique identification parameters. This separation eliminates the security vulnerability of storing keys on devices while maintaining the ability to perform fast, autonomous updates by having devices request software using their ID parameters, which the server then encrypts and sends.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The server acts as an intermediary between the protected database (containing encryption keys) and the remote devices. The server receives update requests from devices using their ID parameters, retrieves the appropriate encryption keys from the protected database, encrypts the software updates, and sends them to the devices. This intermediary role ensures keys never leave the protected database while enabling secure updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If software updates are made available for download to multiple devices, then service coverage and user satisfaction are improved, but the risk of overproduction for parallel markets increases

Engineering Contradiction:
Improveservice coverageVSAvoidoverproduction risk
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The patent implements local quality by encrypting software updates specifically for each individual device using that device's unique encryption key from the protected database. Each device receives software encrypted with its own key, making it unusable on any other device. This enables broad service coverage while preventing overproduction for parallel markets, as each unit of software is locally adapted to a specific device.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the software update distribution system into device-specific encrypted versions. Instead of distributing one generic software version that could be copied and used on multiple devices, the system creates segmented, device-specific encrypted versions. Each segment (encrypted software) is tied to a specific device through its unique encryption key, preventing unauthorized replication and parallel market distribution.

Inventive Principle:
Principle #1Segmentation

3Reliability

If a protected database stores encryption keys for multiple devices, then security is improved, but system complexity increases due to key management requirements

Engineering Contradiction:
ImprovesecurityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling devices to autonomously request software updates using their unique identification parameters. The server automatically retrieves the corresponding encryption key from the protected database, encrypts the software, and sends it to the device. This automated process eliminates the need for manual key management operations, reducing system complexity despite the presence of a protected database with multiple keys.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The server is designed with multi-functionality to handle multiple devices and their unique key management requirements through a single unified system. The protected database stores multiple encryption keys, each associated with a unique device ID, and the server can automatically match any device request with the correct key. This universal approach manages complexity by consolidating key management operations into a single multi-functional server rather than requiring separate management systems for each device.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP2742453B1Method and system for protected transmission of files
Publication Date: 2020.01.08 ABB (SCHWEIZ) AG
  • EP2742453B1 patent drawingFigure 1
  • EP2742453B1 patent drawingFigure 2
  • EP2742453B1 patent drawingFigure 3~4

AI summary

To protect a software to be transferred to programmable electronic devices, a management system for programmable electronic devices is provided, comprising: a plurality of electronic devices (57), each identified by at least one unique identification parameter (ID) and containing at least one encryption key (Key); - at least one protected site (41) in which a protected database (45) resides, in which the unique identification parameter (ID) and the encryption key (Key) are stored for each electronic device (57); - a server (49) programmed to receive a request for transmission of a software from a device (57) and to generate an encrypted version of said software, using the encryption key (Key) associated in the database (45) with the unique identification parameter (ID) of the device (57) that has requested the transmission of said software.