Application-Specific Device Identification via Segmented ID Modules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for authenticating electronic devices to applications do not adequately protect user privacy, as they often rely on global identifiers that can be compromised, leading to potential access to personal data.

Innovation Solution

Implementing an ID module within computing devices that generates and manages application-specific IDs and keypairs, ensuring that only the intended application can access its unique identifier and encryption keys, preventing access by other applications or devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If global identifiers are used to uniquely identify devices to applications, then device identification and authentication functionality is achieved, but user privacy is compromised and security vulnerabilities arise

Engineering Contradiction:
Improvedevice identification reliabilityVSAvoidprivacy vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the identification system by creating application-specific identifiers instead of using a single global identifier. Each application receives a unique identifier that is specific to that application-context, preventing the compromise of one application from affecting others. This is achieved through generating multiple pseudonymous identifiers that are mathematically linked to the device but cannot be traced back to reveal global device identity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer between the device and applications through the use of pseudonymous identifiers. These identifiers act as mediators that enable authentication and device recognition without exposing the actual global device identifier. The system uses cryptographic techniques to create these intermediary identifiers that preserve privacy while maintaining functional reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If application-specific identifiers are implemented, then user privacy is protected, but device identification complexity increases

Engineering Contradiction:
Improveprivacy protectionVSAvoididentification system complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where the system automatically generates and manages application-specific identifiers without requiring complex manual configuration. The device itself performs the generation of pseudonymous identifiers using built-in cryptographic functions, and the operating system automatically handles the distribution of these identifiers to applications, reducing the perceived complexity for users while maintaining strong privacy protection.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the parameters of identification from static global identifiers to dynamic application-specific identifiers. This involves changing the scope, granularity, and mathematical properties of identifiers. The system uses cryptographic parameter transformations to generate identifiers with specific properties (uniqueness per application, unlinkability across applications, verifiability) without requiring complex external infrastructure.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2864927B1Systems, methods and apparatuses for the application-specific identification of devices
Publication Date: 2025.01.15 OLOGN TECH AG
  • EP2864927B1 patent drawingFigure 1
  • EP2864927B1 patent drawingFigure 2
  • EP2864927B1 patent drawingFigure 3A

AI summary

The systems, methods and apparatuses described herein provide a computing environment that manages application specific identification of devices. An apparatus according to the present disclosure may comprise a non- volatile storage storing identifier (ID) base data and a processor. The processor may be configured to validate a certificate of an application being executed on the apparatus. The certificate may contain a code signer ID for a code signer of the application. The processor may further be configured to receive a request for a unique ID of the application, generate the unique ID from the code signer ID and the ID base data and return the generated unique ID.