Software Multi-Ownership Account Management via Blockchain Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software distribution through cloud platforms restricts the transfer of ownership and usage authority between users, leading to issues like personal information leakage and monopolistic control by platform providers, limiting the flexibility of software utilization and resale.
Innovation Solution
A method for managing software multi-ownership accounts that allows for the registration, setting, and transfer of usage authorities using a blockchain-based system, enabling multiple users to share software through sub-access tokens and verification tokens, thereby decoupling software ownership from platform-specific accounts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If software is distributed through cloud platform with platform account management, then software distribution and authentication are simplified, but ownership transfer between users becomes impossible and platform providers gain monopolistic control
Solution Approach 1:
The patent segments the platform account into multiple user accounts, allowing the software ownership to be transferred between different user accounts while maintaining the platform's authentication system. This segmentation enables ownership transfer without compromising the simplified distribution model.
Solution Approach 2:
The patent introduces an intermediary mechanism (ownership transfer system) that mediates between the platform's account management and user-owned software. This intermediary allows ownership transfer while maintaining the platform's control over authentication and distribution.
2Adaptability or versatility
If platform account is sold to transfer software ownership, then software resale is enabled, but personal information leakage and security risks occur
Solution Approach 1:
The patent extracts the software ownership from the platform account, creating a separate ownership layer. This extraction allows software resale without transferring the entire platform account, thereby preventing personal information leakage while enabling software transfer.
Solution Approach 2:
The patent adds a new dimension to account management by separating ownership rights from account credentials. This dimensional separation allows software ownership to be transferred independently of personal information, enabling secure resale.
3Reliability
If platform provider manages all software accounts, then centralized control and security are maintained, but users cannot freely use and utilize purchased software across different environments
Solution Approach 1:
The patent introduces dynamic ownership transfer capabilities that allow software to move between different user accounts and environments. This dynamic approach maintains centralized management while enabling flexible utilization across different contexts.
Solution Approach 2:
The patent creates a universal ownership system that works across different user accounts and environments. This universal approach allows users to freely utilize purchased software in multiple contexts while maintaining centralized control through the platform.
4Reliability
If single access authority is assigned to platform account for one software, then account security is simplified, but multiple users cannot share one piece of software
Solution Approach 1:
The patent segments the single access authority into multiple user-specific authorities, allowing different users to have their own access rights to the same software. This segmentation enables software sharing while maintaining individual account security.
Solution Approach 2:
The patent merges multiple user authorities under a single software ownership, allowing multiple users to access and share the same software simultaneously. This merging enables collaboration while maintaining individual security credentials.
Data Source
AI summary
Managing a software multi-ownership account including operations of registering software, setting a usage authority, and transferring a usage authority. The operation of registering the software includes the operations of: receiving, by a reception unit of a management server, a software registration request from a software manufacturer server; checking whether an authentication unit of the management server is a pre-approved manufacturer; and generating a smart contract transaction using time information at which the authentication unit of the management server is requested to register the software and string information of a software name. An authority can be effectively transferred to use software between users to another person by using a sub-access token interworked to a system user account, and by additionally issuing a sub-access token for multiple access authorities for one piece of software, a user is able to have multiple access authorities, thereby broadening the scope of software utilization.