Multi-Party Computation Environments With Consensus-Based Setup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Collaborative computing environments face challenges in ensuring secure and trustworthy setup and management when multiple entities contribute sensitive digital assets, as reliance on a single administrative entity can lead to potential misuse or security threats.

Innovation Solution

Implementing a consensus-driven management interface (CMMI) that requires all contributing entities to agree on management operations, using trusted execution environments (TEEs) and remote attestation to establish a multi-owned computing environment (MOCE) with sandboxing and tamper-proof auditing, eliminating the need for a trusted third party.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single administrative entity operates the computing environment, then ease of operation is improved, but security and trustworthiness deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidsecurity and trustworthiness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The administrative control is segmented from a single entity to multiple participating parties. Each party holds equal administrative power and must consensus on management operations. The controller software module segments the coordination function, managing setup and operations only when all parties agree, thus distributing trust while maintaining operational efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controller software module acts as an intermediary that coordinates between multiple participating parties. It receives requests from any party, obtains consensus from all parties, and executes management operations only when consensus is reached. This intermediary mechanism enables secure multi-party control without sacrificing operational ease.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple entities contribute sensitive digital assets, then adaptability and collaboration are improved, but security risks and complexity increase

Engineering Contradiction:
Improvecollaboration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the collaborative environment into isolated confidential computing systems, each contributing sensitive digital assets. The controller software module segments the management function, handling setup and coordination separately from the actual computing operations. This segmentation allows multiple entities to collaborate on complex tasks while maintaining security boundaries and reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controller software module serves as an intermediary that manages the complexity of multi-entity collaboration. It handles the coordination overhead, consensus management, and setup processes, allowing participating parties to focus on their respective computing tasks without directly managing the complexity of inter-party coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If a trusted third party is used to manage the environment, then security is improved, but loss of control and autonomy by participating parties increases

Engineering Contradiction:
ImprovesecurityVSAvoidparty autonomy
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent extracts the trusted third party concept and replaces it with a distributed trust model among participating parties. Instead of relying on an external trusted entity, each party maintains autonomy while the controller software module enables them to collectively manage the environment. This extraction eliminates the loss of autonomy while maintaining security through cryptographic verification and consensus mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The participating parties serve themselves by directly managing the computing environment through the controller software module. Each party has equal administrative power and can initiate setup requests, propose management operations, and participate in consensus decisions. This self-service model eliminates the need for a trusted third party while maintaining security and party autonomy.

Inventive Principle:
Principle #25Self-service

4Reliability

If consensus-driven management is implemented, then security and trustworthiness are improved, but ease of operation and decision-making speed deteriorate

Engineering Contradiction:
Improvesecurity and trustworthinessVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The controller software module enables participating parties to self-serve in the consensus process. When a management operation is needed, any party can initiate a request, and the controller automatically coordinates with other parties to obtain consensus. This automated self-service approach maintains security through consensus while improving operational efficiency by eliminating manual coordination overhead.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The controller software module implements feedback mechanisms that track the consensus status of management operations. It automatically communicates with participating parties, updates their knowledge of pending and approved operations, and notifies them when consensus is reached. This feedback system streamlines the consensus process, making it more efficient while maintaining security and trustworthiness.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4614371A1Systems and methods for setting up and maintaining multi-party computation environments
Publication Date: 2025.09.10 ROBERT BOSCH GMBH
  • EP4614371A1 patent drawingFigure 1~2
  • EP4614371A1 patent drawingFigure 3
  • EP4614371A1 patent drawingFigure 4

AI summary

A method for implementing a cooperative computing environment includes, using one or more computing devices, establishing a first confidential computing system, executing, on the first confidential computing system, a controller software module, executing, using the controller software module, an interface configured to provide, to a plurality of participating parties, access to the computing environment, receiving, via the interface from a requesting participating party of the plurality of participating parties, a request to initiate a setup process for the computing environment on a second confidential computing system, and, in response to a determination that non-requesting participating parties of the plurality of participating parties approved the request, completing the setup process for the computing environment in accordance with one or more criteria defined by the request.