Secure Processor Software Download via Device-Specific Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge lies in securely downloading software to multiple devices while preventing unauthorized code loading and exploiting known bugs, especially given the complexity of managing different content and services across numerous devices.

Innovation Solution

A system where a server generates encryption keys based on personalized unit data for secure processors, allowing for secure software downloads by encrypting and decrypting code images using unique keys, ensuring only intended devices can execute the software, and limiting the number of downloads to prevent malicious use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software code images are downloaded to multiple devices, then software updates and new services can be provided, but the risk of unauthorized code loading and exploitation of bugs increases

Engineering Contradiction:
Improvesoftware update efficiencyVSAvoidsoftware security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the software distribution process by creating device-specific encrypted code images. Each device receives a uniquely encrypted version of the software, segmented by device identifier. This prevents unauthorized loading because code encrypted for one device cannot be decrypted or executed on another device, thus maintaining security while enabling widespread software updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary encryption mechanism using device-specific keys as mediators between the central software source and individual devices. The encryption key acts as an intermediary that ensures only the intended device can access and execute the software, preventing malicious users from loading unauthorized code on other devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If encryption keys are generated for each device, then unauthorized code loading is prevented, but the complexity of key management increases

Engineering Contradiction:
Improvesoftware securityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by having each device generate its own encryption key based on its unique device identifier. The device uses its own identifier to encrypt the software code image, and the same identifier is used to decrypt and execute the code. This eliminates the need for complex centralized key management, as each device autonomously manages its own security credentials.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The device identifier serves multiple functions simultaneously: it uniquely identifies the device, generates the encryption key, and enables both encryption and decryption operations. This multi-functionality reduces key management complexity by consolidating multiple security functions into a single identifier-based mechanism.

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

3Adaptability or versatility

If previous application code images can be loaded, then compatibility is maintained, but known bugs can be exploited

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidbug exploitation risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by encrypting software code images with device-specific keys before distribution. This pre-encryption ensures that even if previous code images are available, they cannot be loaded on devices for which they were not specifically encrypted. The encryption is established in advance, preventing retrospective exploitation of bugs in older versions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11115201B2Downloading of data to secure devices
Publication Date: 2021.09.07 COMBINED CONDITIONAL ACCESS DEV & SUPPORT
  • US11115201B2 patent drawing
  • US11115201B2 patent drawing
  • US11115201B2 patent drawing

AI summary

An encryption key may be generated based on personalized unit data associated with a software download recipient, for example, a secure processor. In some aspects, the secure processor may generate a decryption key based on its personalized unit data, and a software download may be performed between the software provider and the secure processor using the generated encryption keys. The secure processor may then decrypt and load the software for execution. The encryption and decryption key generation may also be based on a sequence number or other data indicating one or more previous software downloads at the secure processor. Using the sequence number or other data, sequences of multiple encryption and/or decryption keys may be generated to support multiple software downloads to a secure processor.