Coordinator-Based Secure Transaction Registration Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing systems face difficulties in securely allowing a third-party computing entity to participate in a message transaction that it was not involved in creating, lacking effective mechanisms for secure registration and authorization.
Innovation Solution
A mechanism involving a coordinator computing entity that manages transactions, uses a secure key for registration, and employs role-based authorization to ensure legitimate participation by participant computing entities, preventing unauthorized access and ensuring actions align with assigned relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a third-party computing entity is allowed to participate in a message transaction it was not involved in creating, then the adaptability and versatility of the transaction system is improved, but the security and authorization control deteriorate
Solution Approach 1:
The patent introduces a coordinator computing entity as an intermediary that manages the transaction and controls participant registration. The coordinator receives transaction initiation requests, generates coordination contexts with secure keys, and validates registration requests. This intermediary structure enables third-party participation while maintaining security through centralized authorization control.
Solution Approach 2:
The coordinator generates a coordination context containing a secure key before any participant registration occurs. This preliminary action establishes the security framework in advance, allowing subsequent participants to be authorized through the pre-established key rather than requiring ad-hoc security arrangements.
2Reliability
If secure key-based registration is implemented for participant authorization, then the security and reliability of the transaction is improved, but the device complexity and operational overhead increase
Solution Approach 1:
The coordination context serves multiple functions: it contains the secure key for authentication, identifies the transaction, and provides the basis for authorization. This multi-functional structure reduces overall system complexity by consolidating security and transaction management into a single mechanism rather than requiring separate systems for each function.
3Reliability
If role-based authorization is used to ensure legitimate participation, then the security against unauthorized access and spoofing is improved, but the operational complexity and processing time increase
Solution Approach 1:
Roles and authorization rules are established in advance by the coordinator before participants need to act. The coordination context is prepared with the secure key beforehand, so when a participant registers, the verification process is streamlined to checking against pre-established criteria rather than creating authorization rules in real-time.
Data Source
AI summary
Mechanisms for securely allowing a participant computing entity to engage in a transaction initiated by an initiator computing entity and managed by a coordinator computing entity. The initiator provides a transaction initiation request to the coordinator. Upon receipt, the coordinator accessing a transaction coordination context that includes information such as a secure key that may be used by a participant to register in the transaction. The coordinator then provides the coordination context to the initiator, which provides the coordination context to the participant(s) that are also to engage in the transaction. Each participant then generates a registration request that is based on the coordination context, and that is secured using the secure key provided in the coordination context.