Client-Provider Dual-Key Data Sharing for Centralized Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized collection of usage data from multiple users and different manufacturers is hindered by the risk of data accessibility to unintended parties due to data merging.

Innovation Solution

A system comprising a server, client, and database, where data generated by modules on the client is encrypted with both client and provider-specific keys, allowing secure transmission and storage on the server, accessible only to authorized parties using respective identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data from multiple users and manufacturers is merged for centralized collection, then data quantity and analysis capability are improved, but data security and access control deteriorate

Engineering Contradiction:
Improvedata quantityVSAvoiddata security
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments data into multiple encrypted versions, each protected by different keys. The original data is divided into first encrypted data (protected by client key) and second encrypted data (protected by provider key), allowing centralized collection while maintaining granular access control for different parties

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces encrypted data as an intermediary form between raw data and usable information. By storing data in encrypted states that require specific keys for decryption, the system enables centralized data collection while preventing unauthorized access, as only authorized parties with the corresponding keys can access the actual data content

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is encrypted with multiple keys for security, then data protection is improved, but system complexity and processing overhead worsen

Engineering Contradiction:
Improvedata protectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the encryption system into distinct segments: client-side encryption using the client's key, server-side encryption using the provider's key, and structured storage with clear separation between first encrypted data and second encrypted data. This segmentation makes the complex multi-key system manageable by assigning specific encryption responsibilities to different system components

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary encryption actions at the client端 before data transmission. The client encrypts data with its own key first, then the server adds another layer of encryption with the provider's key. This preliminary encryption reduces the computational burden on the server and simplifies the overall processing by distributing encryption tasks across different stages of the data flow

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3835989B1Method and system for sharing data
Publication Date: 2025.09.03 ISE INDIVIDUELLE SOFTWARE & ELEKTRONIK GMBH
  • EP3835989B1 patent drawingFigure 1
  • EP3835989B1 patent drawingFigure 2

AI summary

The invention relates to a system comprising: a server, a database, and at least one client; wherein one or more keys are stored on the database, each assigned to a respective provider of a module that processes data in or on the client; wherein the client is configured to: encrypt data generated by a module on the client with a first key assigned to the client, the module being assigned to one of the providers; access the database and read a second key assigned to the provider, and encrypt the data with the second key as the second data; and send the first and second data to the server; and wherein the server is configured to: store the first and second data, the first data being assigned to the client, and the second data being assigned to the provider of the module.