| CPC H04L 9/3239 (2013.01) [H04L 9/3213 (2013.01); H04L 9/50 (2022.05)] | 2 Claims |
|
1. A method for managing a software multi-ownership account, wherein:
the method is divided into an operation of registering software, an operation of setting a usage authority, and an operation of transferring a usage authority; and
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,
wherein the operation of transferring the usage authority includes the operations of:
selecting, by a user terminal, software that is desired to be transferred and delivering the same to a management server;
matching, by a usage authority transfer unit of the management server, the software with user information that is desired to be received and delivering the same to the user terminal;
executing, by the user terminal, an account that is desired to be transferred and delivering the same to the management server;
searching, by the usage authority transfer unit of the management server, a transaction ID of the usage authority and requesting a blockchain system for state information;
checking, by a reception unit of the management server, block information of the corresponding transaction ID of the blockchain system and receiving the state information;
updating, by the usage authority transfer unit of the management server, an authority to use software from a transferor to a transferee in a database;
cancelling, by the usage authority transfer unit of the management server, a previously accessed user connection; and
disconnecting, by the usage authority transfer unit, all accesses, wherein the software of an existing owner is disconnected by interworking with the authentication unit,
wherein the operation of setting the usage authority includes the operations of:
downloading, by a user terminal, software interworked to a dedicated application;
requesting, by an interworked software server, for a usage authority from the manager server when the user terminal executes the downloaded software for the first time;
extracting, by an authentication unit of the management server, a transaction ID from a database;
extracting by the authentication unit of the management server, a top level account of a user;
using, by the authentication unit of the management server, the transaction ID and a blockchain CA to generate ownership information of the user, wherein the top level account of the user is the blockchain CA;
generating, by a usage authority generation unit of the management server, an access token and a verification token, wherein the access token is for ownership and the verification token for verifying the account;
storing, by the usage authority generation unit, a hex value of an account address on the blockchain system of the user and a transaction ID value of a registered software, the hex value is referred and stored, by the usage authority generation unit, in one structure; and
transmitting, by a transmission unit of the management server, the access token and the verification token to the interworked software server,
wherein the access token is generated by encrypting the ownership information using AES 128 encryption, and
wherein the usage authority generation unit of the management server repeatedly generates the access token and the verification token so that multiple users share the software through a plurality of access tokens and verification tokens for one piece of software.
|