WO2019189954A1

WO2019189954A1 - Multiple blockchain-based data sharing method

Info

Publication number: WO2019189954A1
Application number: PCT/KR2018/003632
Authority: WO
Inventors: 양성우; 전재경; 최익정; 박현민; 박지은; 서정선; 김창훈; 서한솔; 김남희
Original assignee: 주식회사 마크로젠; 마크로젠 코퍼레이션
Priority date: 2018-03-28
Filing date: 2018-03-28
Publication date: 2019-10-03

Abstract

A multiple blockchain-based data sharing method comprises the steps of: registering, in a user information blockchain, user block data including user information and a hash key for each of multiple users, by a management server; receiving, from a storage server, storage information for data provided by a first user, by the management server; and receiving a request for specific data from a second user and transmitting storage information for the specific data to the second user, by the management server.

Description

Data sharing method based on multiple blockchains

The technique described below relates to a technique for data sharing. The technology described below relates to a platform for data trading relaying and data sharing based on the sharing economy. More specifically, it serves as an integrated management role as a kind of transaction brokerage platform, which is made by sharing the data owned by the individual in the ownership of the individual between the trading entities and the provider who provided the data and the user who uses the data.

As the paradigm shifts from current ownership to sharing, digital information is increasing along with the integration of existing information and communication technologies. For example, a sharing economy in which peer-to-peer (P2P), which is a trade between individuals through collaborative consumption, is activated.

The sharing economy is an economic system based on collaborative consumption, which is shared among several trading partners, and which is not owned by individuals. In the sharing economy platform, users pay for resources and use as many resources as necessary, resource providers receive rewards through the provision of idle resources, and the brokered platform earns commission revenue.

When blockchain technology is introduced into this sharing economy, all participants jointly register, store and share idle resources, solve security problems for hacking and manipulation of idle resources, and further secure transaction record reliability through verification. can do.

The data may consist of various information. For example, the data may include specific genomic information, medical information, and life information of various organisms including humans. Data on humans predict the likelihood of disease, enabling tailored precision medicine to prescribe the most appropriate treatment for each patient. Among the various data that are essential for precision medicine, in particular genomic information and medical information, it is very difficult to collect data for a specific population due to various regulations and system problems, cost and time. In addition, life information is a unique life record with a degree of difference between individuals, such as living habits and the environment, which is difficult to collect unless the individual provides it. These problems can be solved through a blockchain-based data integration management platform that enables researchers and institutions that require such information to be securely shared after personal data owned by individuals are securely shared after de-identification of personal information. I can solve it.

In other words, by providing and renting personal information and personal data, which are idle resources owned by individuals, data users can secure the necessary data by paying the use fee to form a win-win economic system. . Based on these idle resources, researchers and institutions can create high-value added value by strengthening public health care by developing new medicines and reducing social burdens by reducing medical costs by developing customized treatments and programs through various research results.

Therefore, the technology described below can promote data sharing and utilization by incorporating blockchain technology into a sharing economy based platform, and improve user data accessibility and management efficiency through the ease of use of open software sources. In addition, the technology described below can guarantee security, reliability and speed through a systematic security system that can transparently and flexibly cope with hacking risk, data capacity increase and sharing in managing big data, which is integrated large data. . In addition, the technology described below can be expected to reduce costs and time by increasing the participation rate of users by building an economic incentive system through the compensation and payment method.

The technology described below introduces blockchain technology to securely register, store, and share data, which is an idle resource jointly owned by all participants, and solves security problems for hacking and manipulation of data. It is intended to provide a trading system and method.

In addition, the technology described below is to provide a data sharing transaction system and method for each other by obtaining a reward for providing and renting data that is owned idle resources, and data users secure the necessary data through payment of usage fees. .

In addition, the technology described below is intended to provide a blockchain system and method that implements a function through a blockchain that allows the data owner to store, register or delete data, which is an idle resource, on a shared storage server directly or through another organization. do.

In addition, the technology described below is to provide an integrated management system and method for blockchain-based shared data that provides data transfer and provide data that can be retrieved from the storage, and retrieves the information that the lender needs the data required .

Meanwhile, the technical problem to be described below is not limited to the technical problem mentioned above, and various technical problems may be included within the scope apparent to those skilled in the art from the following description.

Integrated management system and method for blockchain-based data sharing according to an embodiment may be configured as follows.

Integrated management methods for data sharing include: a) a user (including data owners / providers and data lenders / users) entering basic information and registering in the personal information blockchain, b) the data provider storing personal data on the data storage server Storing data in the data storage server and registering and deleting in the data information and data blockchain, c) retrieving the personal data of the provider required by the data user from the data storage server, d) paying the fee for the personal data of the provider required by the data user. And receiving the corresponding data from the data storage server, and e) delivering a fee for sharing the genome / medical information data to the data provider.

The step a) includes receiving identification information such as a user's name, date of birth, and e-mail as basic information, registering the user information in the user information blockchain, performing user authentication through the user information blockchain, and making a deposit and withdrawal of a user fee. It may include a virtual account creation step.

The step b) includes the data provider registering meta information about the data in the metadata blockchain, the data provider directly transmitting the data to the data storage server, and the data provider deleting personal data and information. can do. Meanwhile, step b) may include a step in which the data provider requests a separate data producer to transmit data to the storage server.

Step c) may include searching for meta information on the registered data through a query on the metadata blockchain for data required by the data user.

In step d), the data user converts the data usage fee into virtual currency (points, membership mileage, actual cash, etc.), registering the virtual currency into the virtual account through the information and data blockchain, and the data user It may include the step of requesting and receiving data required for the data storage server.

The step e) may include transmitting a virtual currency to a virtual account registered in the genome / medical information data blockchain to a data provider, and converting the transmitted virtual currency into a data fee.

The technology described below ensures security for data sharing, which is an idle resource based on the blockchain. In addition, the technology described below smoothly compensates for data sharing by introducing a blockchain technique.

1 is an example of a data sharing model.

2 is an example of a data sharing system.

3 is an example of a flowchart for a data sharing process.

4 is an example of a user information registration and authentication process.

5 is an example of a point trading process.

6 is an example of a metadata management process for data.

7 is an example of a data storage and deletion process.

8 is an example of a data retrieval and transmission process.

9 is an example of a process of identifying data based on metadata.

10 is an example of a process of sharing data including an encryption process.

11 is another example of a process of sharing data including an encryption process.

The following description may be made in various ways and have a variety of embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the technology described below to specific embodiments, it should be understood to include all changes, equivalents, and substitutes included in the spirit and scope of the technology described below.

The techniques described below relate to data provision or shared services. Although the following describes the life information data, the technology described below may be applied to various data providing services regardless of the type of data.

The terms used in the following description will be described.

Genomic data refers to data obtained from samples (samples) and organisms (humans, animals, microorganisms, etc.) of a particular user. For example, genomic data may include nucleotide sequences obtained from deoxyribonucleic acid (DNA), ribonucleic acid (RNA), or protein (Protein), cells, tissues, etc., genetic variation data, genetic variation with standard genomic data, and DNA methylation. ) May be included. Generally, genomic data includes sequence information obtained by analyzing a particular sample. Dielectric data is generally represented as digital data. This includes the sequence data obtained through the NGS analysis device.

Genomic analysis data or simply analysis data refers to information obtained by analyzing genomic data. For example, the analysis data includes a diagnosis result obtained by analyzing the genomic data, a disease prediction result, a disease risk, paternity results, a disease treatment means, a drug candidate, and the like.

Medical data refers to data that can be used to determine the health of a particular user (eg, a patient). For example, medical data may include electronic medical record (EMR) data in a hospital. That is, the medical data may include a test result (clinical information) using a medical device or a diagnosis result by a medical staff. Also, for example, the medical data may include medical image data measured or photographed by a medical device. Also, for example, the medical data may include biosignal data obtained by a mobile terminal (eg, a healthcare device) capable of measuring the biosignal.

The following data refers to digital data having various information regardless of data format or type. The data may include personal information, information produced by the individual, information analyzed by the personal data, experimental data about the individual, and the like. For example, the data may include at least one of the above-described genomic data, analysis data and medical data. Data may be data produced by individual objects (people, businesses, research institutions, schools, hospitals, etc.) that are biological or social subjects.

Metadata is identification data derived from data production or processing. The metadata corresponds to data for identification or further explanation of the data. Metadata can be a criterion for retrieving specific data. For example, the metadata may include data format and production methodology for genomic data, sequencing machine information, sample information, definition of molecular biology techniques, yield, quality analysis and statistics on data, date of production, and the like. For example, the metadata may include a production date of the medical data, a production organization, patient information (identifier, etc.), disease information, a test technique, a type of a test apparatus, a format of data, and the like.

Provider means a user who produces or processes and provides data. A provider is a user who provides data to be shared. Providers can provide data produced by themselves or data produced by others.

The receiver refers to a user who shares data provided by the provider. Recipients can use the data to conduct research and analysis.

The user includes a specific subject such as a person or an institution. The user terminal or terminal is a computer device, and means a client device used by the user. In the system, a user is specified as a user terminal.

The computer device refers to a device that analyzes input source data using a computing device such as a CPU or an AP. Computer devices generally include computing devices, memory, input / output devices, communication interface devices, and the like. The computer device may be implemented as a device such as a server, a PC, a tablet PC, a smartphone, or the like.

A hash key is a value used to identify a user on a blockchain network. Hashkeys can be generated in a variety of ways. Representative hash key generation algorithms include MD5 and SHA-256. The hash key is the only value present for a particular user. Hash keys are keys that consist of strings of varying lengths.

Public keys and encryption keys are keys for encrypting and transmitting data on a blockchain network. Public and cryptographic keys are keys used for so-called public key cryptography. The public key range is a key for encrypting data, and the encryption key is a key for decrypting encrypted data. The public and encryption keys can be paired with one another and randomly produced using various public key encryption methods (eg, RSA, elliptic curve cryptography, etc.).

Blockchain refers to a chain-based distributed data storage environment in which small pieces of data called 'blocks' are managed based on P2P methods. Blockchain network refers to the network components constituting the blockchain.

1 is an example of a data sharing model. 1 shows a user terminal 10 used by a provider A side, a user terminal 20 used by a receiver B side, a management server 30 and a blockchain set 40. For convenience of description, the user terminal used by the provider A is called the first terminal 10 and the user terminal used by the receiver B is called the second terminal 20.

The first terminal 10 receives data. Alternatively, the first terminal 10 may generate data. Alternatively, the first terminal 10 may receive data from another object. The first terminal 10 transmits data to the management server 30.

The management server 30 manages the overall process for data sharing. The management server 30 may be managed by a provider that provides a data sharing service. It can be seen that the management server 30 and the blockchain set 40 constitute a system for data sharing.

Data sharing is done through the blockchain. Data sharing uses a plurality of blockchains (blockchain sets). Individual blockchains belonging to a blockchain set are involved in different processes or functions for sharing data. The blockchain set 40 includes a user information blockchain, a point information blockchain, a metadata blockchain, and a data storage blockchain. Details will be described later.

The management server 30 registers the information about the user in the user information blockchain in advance. The management server 30 may perform authentication for a specific user using the user information blockchain. The management server 30 registers metadata about data received from the first terminal 10 in the metadata blockchain. The management server 30 stores the data received from the first terminal 10 in the storage server to configure a data storage blockchain. In addition, the management server 30 manages the user's point information (point generation, point use, point transfer, point extinction, etc.) using the point information blockchain.

The management server 30 receives a request for data from the second terminal 20. The management server 30 may inquire about the requested data based on the metadata. Alternatively, in some cases, the management server 30 may inquire about data stored in the storage server. If the requested data exists, the management server 30 transmits the storage information for the data to the second terminal 20. Thereafter, the second terminal 20 may receive data from the storage server based on the storage information.

Blockchain networks have two main components. One is a blockchain node and the other is a client. From the user's point of view, a blockchain node acts as a backend for a typical service and a blockchain client acts as a client. When a client initiates a new transaction, the nodes share the transaction through the process of distributing and executing the transaction. The client can check the outcome of the transaction. In FIG. 1,

user terminals

10 and 20 correspond to clients. In FIG. 1, a blockchain node corresponds to a separate node (terminal, server, etc.) connected to a network.

2 is an example of a data sharing system 100. The data sharing system 100 includes a management server 110 and a plurality of

blockchains

120, 130, 140, and 150. The management server 110 corresponds to the management server 30 of FIG.

The user terminal 110 includes a first terminal 10 on the provider side and a second terminal 20 on the receiver side.

2 shows all four blockchains 120-150. One blockchain is composed of a plurality of blockchain nodes. The four blockchains are shown below. As will be described later, in some cases, the system 100 may further include a blockchain for other items.

The user information blockchain 120 holds user information. The user information blockchain stores hash keys and user information about users. For example, the user information may include information such as an identifier of the user, a user ID, a user contact number, an e-mail, a name, a gender, an institution, a date of birth, and the like. The user information blockchain 120 may hold user information encrypted with a public key.

The point information blockchain 130 holds point information. The point is the incentive to share data. In addition, points correspond to the fee for using data. Furthermore, the points may be a fee for the operators who broker the data. The point may be a so-called blockchain-based virtual currency. Alternatively, the point may be a currency unique to the shared service (cyber money, cash, mileage, etc.) that is not based on the blockchain. Points may be converted into currency used in the real world through a separate system or service. The point information blockchain 130 holds information such as point balance information and point transaction details of individual users.

The metadata blockchain 140 holds metadata about the data. The metadata blockchain 140 can hold metadata encrypted with a specific public key.

The data storage blockchain 150 holds storage information for data stored in the storage server. The storage information may include an identifier of a storage server, a file name, a location where data is stored in a storage medium of the storage server, a file size, file split information, a verification key, and the like.

The storage server 155 stores the data. The storage server may be one single server. Alternatively, as shown in FIG. 2, the storage server may include n servers (storage server 1, ... storage server n). When there are a plurality of storage servers, data may be distributed and stored. Furthermore, when there are a plurality of storage servers, one server (main storage server) may store the generated data as it is, and the other server (sub storage server) may distribute (segment) and store the data. When a plurality of servers are used, the plurality of storage servers or the plurality of sub-storage servers may be nodes constituting the block chain, and the plurality of storage servers may configure the data storage block chain. The data storage blockchain 150 holds storage information for the entire data held.

The management server 110 stores user information, point transaction information, metadata, and data received from the first terminal 10 in a blockchain network. The management server 110 transmits data to the second terminal 20 requesting data.

The management server 110 may include a user management function. In other words, the user information can be received and stored in the user information blockchain network, and user authentication can be performed based on the stored user information.

The management server 110 may include a point management function. That is, a point purchase, a point sale, or a point transaction that occurs from a user-to-user transaction. The user's balance points can be stored and retrieved through the blockchain network.

The management server 110 may include a metadata management function. The management server 110 stores the metadata received from the data provider in the blockchain network. In addition, the management server 110 may search for data based on the receiver, and group the data corresponding to the search results into groups.

The management server 110 may include a data storage management function. The management server 110 may receive the data from the provider, store the data in the storage server, collect the data, and group the data to the receiver.

3 is an example of a flow chart for a data sharing process 200. 3 shows a schematic process for data sharing. The users (providers and recipients) perform user registration in advance (210). The management server 110 registers the user information and the hash key in the user information blockchain. In addition, after user registration, the management server 110 may perform authentication for a user who performs or requests a corresponding process before starting data provision, data sharing, point processing, or the like. The management server 110 may perform user authentication by using a user information blockchain.

The provider provides data to the management server 110, and the management server 110 configures the data storage blockchain 150 while storing the data in the storage server 155 (220). Although not shown in FIG. 3, the management server 110 may register metadata about data in a metadata block chain.

The receiver requests the management server 30 for necessary data. The management server 30 performs a data search for the requested data and, if present, transmits the stored information of the data to the receiver (230). The management server 30 may search for data based on the metadata.

The management server 110 performs 240 processing points related to the use of data before providing data to the recipient. The management server 110 registers the details of the point transaction details (point change, point transfer, point charging, etc.) in the point information blockchain 130. For example, the recipient point can be delivered to the provider through this process.

Finally, the management server 110 provides the storage information of the requested data to the receiver. The receiver may receive data from the storage server 155 based on the stored information.

Meanwhile, data used in the process of registering user information, storing data, registering metadata, and processing points may be encrypted using a public key method.

4 is an example of a user information registration and authentication process 300. 4 shows both a user registration process and a user authentication process.

The user registration process will be described. In FIG. 9, the user terminal refers to the first terminal 10 and / or the second terminal 20. The provider must register the user in advance to provide the data or the receiver to request the data.

The user terminal 10/20 inputs user information PI (301). The user terminal 10/20 transmits the user information PI to the management server 110 (302).

The management server 110 may generate a hash key. The management server 110 generates a hash key H _k for the user who requested to generate the hash based on the user information PI (311). The hash key H _k is used as an identifier for the user (terminal) who has requested the current hash key. Thus, the hash key H _k corresponds to user-specific unique information. The management server 110 generates the hash key H _k by inputting the input user information PI into a predetermined hash function. The algorithm or hash function for generating the hash key may vary.

The management server 110 may encrypt (generated PI ') the received user information PI (312). The management server 110 may encrypt the user information using the public key transmitted by the user terminal 10/20. Meanwhile, the user information PI 'encrypted by the public terminal 10/20 may be transmitted to the management server 110.

The management server 110 transmits the generated hash key H _k to the user terminal 10/20 that requested the hash key (321). The user terminal 10/20 stores the hash key H _k in the storage medium (322).

The management server 110 transmits user block data including the encrypted user information PI ′ and the hash key H _k to the user information blockchain 120 (331). The user information blockchain 120 registers the received encrypted user information PI 'and the hash key H _k (332). In this case, the management server 110 may further transmit the public key used for encryption to the user information blockchain 120. In this case, the user information blockchain 120 may further register up to the public key. Steps 301 to 332 described above correspond to a user information registration process.

Describes the user authentication process. User authentication may be required at certain stages or at each stage of the data sharing service. Only users who have been authenticated through user authentication can proceed to the next step.

For authentication, the user terminal 10/20 inputs user information PI (351). The user terminal 10/20 transmits the user information PI or its stored hash key H _k to the management server 110 (352). The management server 110 may generate the PI 'by encrypting the received user information with the public key. The management server 110 inquires the user information based on the received user information PI (or PI ') or the hash key (H _k ) (361). The management server 110 queries the user information delivered to the user information blockchain 120 based on the received information. The management server 110 transmits the inquired user information or hash key H _k to the user information blockchain 120.

The user information blockchain 120 may identify user information based on the received information (371). For example, the user information blockchain 120 may identify user information based on the hash key H _k . The user information blockchain 120 transmits the identified user information to the management server 110 (372).

The management server 110 may perform user authentication by comparing the user information PI ′ received from the user information blockchain 120 and the user information PI ′ received from the user terminal 10/20. In addition, the management server 110 may generate an authentication token (381). At this time, the management server 110 may encrypt the authentication token with a public key. The management server 110 transmits a user authentication token to the user terminal 10/20 (382).

The user terminal 10/20 stores a user authentication token (383). The user terminal 10/20 may decrypt and store the encrypted authentication token. Thereafter, the user terminal 10/20 may use an authentication token in the process of communicating with the management server 110. The management server 110 that requires authentication may provide specific data only for the user terminal that delivers a valid authentication token.

In the user registration process, a virtual account generation step for an individual user may be performed. The virtual account generation includes creating an account (wallet) for the user in the point information blockchain 130. Virtual account creation may be a method commonly used in a virtual money service based on blockchain. The description related to FIG. 5 described below assumes a state where a virtual account is created for each user.

5 is an example of a point trading process 400. 5 is an example of a process of processing and managing points for a user.

The user terminal 10/20 inputs user point transaction information (401). The point trading information includes information necessary for point trading. For example, the point transaction information includes transaction subject information (user information or hash key), point charging information, point deposit and withdrawal information, point balance information, transaction amount information, and the like. The user terminal 10/20 transmits point transaction information to the management server 110 (411). The user terminal 10/20 may encrypt the point transaction information with the public key and transmit the encrypted information.

The management server 110 may perform an authentication on the user who transmitted the point transaction information (420). The subsequent process may be performed only for the user whose authentication is successful. The management server 110 may perform authentication for the corresponding user by using the authentication token transmitted by the user terminal 10/20. The authentication token has been described with reference to FIG. 4.

The management server 110 can inquire the requested point transaction history (421). For example, a specific block corresponding to a book in which transaction details are listed may be inquired. The management server 110 transmits the point transaction information to the confirmed point information blockchain 130 (422).

The point information blockchain 130 inquires information about the point transaction, and registers the content of the requested transaction (431). For example, points may be reduced in the books of a specific user (recipient) and added to the books of another user (provider). The point information blockchain 130 writes information related to the transaction details in the block. The point information blockchain 130 transmits the changed point transaction information to the management server 110 (432).

The management server 110 may verify whether the transaction details received from the point information blockchain 130 and the transaction details requested from the user terminal 10/20 match (441). If the verification is successful, the management server 110 transmits the point transaction information to the user terminal 10/20 (442). The user terminal 10/20 stores user point transaction information (451).

6 is an example of a metadata management process 500 for data. 6 includes a process of registering and deleting metadata.

First, the process of registering metadata is described. The first terminal 10 inputs data (511). Alternatively, the user terminal 10/20 inputs metadata about data. The first terminal 10 transmits the input or acquired data or metadata to the management server 110 (512).

The management server 110 may perform authentication on the user who transmitted the data or metadata (520). The subsequent process may be performed only for the user whose authentication is successful. The management server 110 may perform authentication for the corresponding user by using the authentication token transmitted by the user terminal 10/20. The authentication token has been described with reference to FIG. 4.

When the management server 110 receives the data, the management server 110 may identify metadata from the data (521). The management server 110 may verify whether the data meets a predetermined format or standard upon receiving the data. Alternatively, the management server 110 may verify data with a specific verification key. The verification key refers to information for verifying an electronic signature. In this case, the data must include an electronic signature in advance. The provider sends the data with the electronic signature.

The data may include information about the metadata in a particular format. In this case, the management server 110 may extract metadata from the data. If the management server 110 receives the metadata directly from the first terminal 10, no separate identification process is required. The management server 110 transmits the metadata to the metadata blockchain 140. The metadata blockchain 140 registers metadata related to specific data as block data (531). The metadata registered in the metadata blockchain 140 may be used for checking whether data corresponding to the request exists when the receiver requests data.

Describe the process of deleting metadata. The first terminal 10 requests deletion of metadata (551). The first terminal 10 transmits the metadata deletion message to the management server 110 (552). The deletion message may include an identifier of data to be deleted, an identifier of metadata, a metadata generation time point, and the like. Alternatively, the deletion message may include all metadata. The management server 110 verifies the received metadata deletion message (561). The management server 110 may verify the deletion message with a specific verification key. Separately, the management server 110 may perform authentication on the user who delivered the deletion message. Authentication may be performed by whether the authentication token delivered by the first terminal 10 is valid. The management server 110 transmits a deletion message to the metadata blockchain 140 (562). The metadata blockchain 140 deletes the requested metadata based on the information included in the deletion message (571). Thereafter, the metadata blockchain 140 transmits a delete confirmation message to the management server 110 (581). The management server may transmit a deletion confirmation message to the first terminal 10 (582).

7 is an example of a data storage and deletion process 600.

First, the data storage process is explained. The first terminal 10 inputs data (601). The first terminal 10 may directly generate data or input information generated by a third party. The first terminal 10 may encrypt the generated data with the public key (602). In some cases, the management server 110 may encrypt data with the public key of the first terminal 10.

The first terminal 10 transmits data to the management server 110 (611). The management server 110 may verify the received data on a predetermined basis (612). For example, when the data has a specific format, the management server 110 may verify whether the data satisfies the standard of the format. Alternatively, the verification may be performed using a separate verification key for the data.

The management server 110 may perform authentication on the user who transmitted the data (620). The subsequent process may be performed only for the user whose authentication is successful. The management server 110 may perform authentication for the corresponding user by using the authentication token transmitted by the user terminal 10/20. The authentication token has been described with reference to FIG. 4.

The management server 110 transmits the encrypted data to the storage server 155 (621). The storage server 155 stores the received data (622). As described above, the storage server 155 may be configured of a plurality of servers. In this case, data may be distributed or divided in a plurality of servers and stored. One server or a plurality of servers transmits the information in which the data is stored to the data storage blockchain 150 (631). The data storage blockchain 150 registers the storage information for the data held by the storage server 155 collectively (632). Each storage server 155 has only its own information, but the data storage blockchain 150 holds the storage information of the entire data. As described above, the storage information may include an identifier of a storage server, a file name, a location where data is stored in a storage medium of the storage server, a file size, file split information, a verification key, and the like. The data storage blockchain 150 transmits data storage information to the management server 110 (641). The management server 110 registers 642 storage information for the data. That is, the management server 110 retains the storage information for the entire data.

Describe the data deletion process. The first terminal 10 requests data deletion (651). The first terminal 10 transmits a data deletion message to the management server 110 (652). The management server 110 verifies the deletion message (661). The deletion message may include a name, an identifier, and the like of data to be deleted. The management server 110 may verify the deletion message by using a separate verification key. In addition, the user (first terminal) that transmits the deletion message may be authenticated through a separate process.

The management server 110 may perform authentication on the user who sent the deletion message (670). The subsequent process may be performed only for the user whose authentication is successful. The management server 110 may perform authentication for the corresponding user by using the authentication token transmitted by the user terminal 10/20. The authentication token has been described with reference to FIG. 4.

The management server 110 transmits a data deletion message to the storage server 155 (671). Since the management server 110 holds the storage information, the management server 110 may transmit a deletion message to the storage server 155 storing the deletion target (671). The storage server 155 deletes the data requested for deletion (681). Although not shown in FIG. 7, the storage server 155 deletes the data and registers the changed information in the data storage blockchain 150. The data storage blockchain 150 updates the storage information. The storage server 155 transmits a deletion confirmation message to the management server 110 (691). The management server 110 may transmit a deletion confirmation message to the first terminal 10 (692).

On the other hand, when the first terminal 10 deletes the data, it is preferable to also delete the metadata for the data to be deleted. Therefore, the deletion message transmitted by the first terminal 10 may include deletion information about data and metadata about the data.

8 is an example of a data retrieval and transmission process 700. 8 corresponds to a process in which a receiver receives data. The second terminal 20 inputs a data search word (711). The data search word may be composed of various information. For example, the data search word may include an identifier of a specific subject, an identifier of a specific genome, an identifier for a specific disease, an identifier for a specific organ, a data generation time, a data update time, and the like. The data search term may include metadata about the data. The second terminal 20 transmits the data search word to the management server 110 (712).

The management server 110 may perform an authentication on the user who transmitted the search word (720). The subsequent process may be performed only for the user whose authentication is successful. The management server 110 may perform authentication for the corresponding user by using the authentication token transmitted by the user terminal 10/20. The authentication token has been described with reference to FIG. 4.

The management server 110 must first search whether the requested data exists in the storage server 155 (721). The management server 110 may search whether the storage server 155 has the corresponding data by using the information included in the search word. For example, the management server 110 may know whether the corresponding data exists in the storage server 155 based on the identifier of the data. This is because the management server 110 holds the storage information for the data. Furthermore, the management server 110 may check that there is information corresponding to the metadata blockchain 140 by using metadata included in a search word. The management server 110 may search for information held by the metadata blockchain 140 based on information such as a data generation technique, a generation time, a specific disease type, and the like to determine whether there is data that meets a corresponding condition.

If there is the requested data, the management server 110 performs point inquiry and point processing (731). Point trading is as described in FIG. The management server 110 checks whether the recipient has a point in the point information blockchain 130. If there is a point balance corresponding to the price of data sharing, the management server 110 decrements the point of the receiver and increases the point of the provider of the data. In addition, the management server 110 may bring the recipient's points to some manager account as a fee for the data brokerage service.

The management server 110 identifies the storage information of the requested data (741). Meanwhile, the management server 110 may identify a plurality of data that meets the corresponding criteria based on the search expression included in the search word and configure the data into one group. In this case, the management server 110 identifies the entire storage information for the data belonging to the group. The management server 110 transmits the stored storage information to the second terminal 20 (742).

The second terminal 20 stores the received storage information and generates a transmission request message for requesting transmission to the corresponding storage server (751). The transmission request message may include an identifier (address) of the storage server, an identifier of the data, a storage location of the data, and the like. The second terminal 20 transmits a transmission request message to the corresponding storage server 155 (752).

The storage server 155 identifies the requested data based on the information included in the transmission request message, and identifies the data stored in the specific location (761). The storage server 155 transmits the identified data to the second terminal 20 (762). The second terminal 20 receives the data and decodes the data using the encryption key (771). Therefore, the second terminal 20 must obtain an encryption key to decrypt data previously encrypted with the public key. To this end, the user information blockchain 120 may hold an encryption key for a specific user. The second terminal 20 may obtain an encryption key for a specific user in advance through the management server 110.

9 is an example of a process of identifying data based on metadata. The receiver who wants to receive the data shared by the provider requests the management server 110 for data meeting the conditions. The second terminal 20 receives a search word (811). The second terminal 20 transmits the search word to the management server 110 (812). The search term includes information that can identify the particular type of data desired by the recipient. For example, the search term may include at least some of the metadata about the data.

As described above, the management server 110 may authenticate the user who transmitted the search word (820). In addition, the management server 110 may verify the received search word using a separate verification key (821). Alternatively, the management server 110 may simply verify whether the search word is composed of a valid search word for a specific format. If authentication or verification is successful, the management server 110 transmits a search word to the metadata blockchain 140 (822).

The metadata blockchain 140 extracts metadata associated with the received search word (831). The metadata blockchain 140 may extract all metadata including specific metadata. The metadata blockchain 140 transmits the retrieved metadata to the management server 110. The metadata may include an identifier for the data.

The management server 110 may identify specific data in the transmitted metadata. In addition, when there are a large number of data related to a search word, the management server 110 may process the corresponding data into one group (841). The management server 110 extracts storage information for the identified one or more data (842). As described above, the management server 110 retains storage information for data stored in the storage server 155. Or, in some cases, a separate server or blockchain may manage the storage information.

The management server 110 transmits the identified stored information to the second terminal 20 (851).

10 is an example of a process of sharing data including an encryption process. 10 corresponds to a process in which the first terminal 10 provides data and the second terminal 20 receives the provided data.

The management server 110 transmits its public key P _s to the first terminal 10 (901). The first terminal 10 encrypts the data using the public key P _s (911). The first terminal 10 transmits the encrypted data to the management server 110 (912).

Unlike the process illustrated in FIG. 10, the management server 110 may encrypt data transmitted by the first terminal 10 using its public key and then proceed with the subsequent process.

The management server 110 may verify data using the verification key (921). The management server 110 transmits the encrypted data to the storage server 155 (922). One or more storage servers 155 store the encrypted data (931). As described above, the plurality of storage servers 155 may configure the data storage blockchain 150. The storage server 155 transmits storage information about the stored data to the management server 110 (932).

Thereafter, the second terminal 20 requests specific data from the management server 110 (941). In this case, the second terminal 20 may transmit its public key _Pue2 (941).

The management server 110 retrieves data through the above-described process (951). The management server 110 may request the identified data from the storage server 155 (952). The storage server 155 transmits the requested data to the management server 110 (953).

The management server 110 may decrypt the data received with the encryption key corresponding to its public key (P _s ), and may now encrypt the data again with the public key (P _{ue 2} ) of the second terminal (961). The management server 110 transmits the encrypted data to the second terminal 20 (971). The second terminal 20 decrypts the received data with its encryption key (981).

11 is another example of a process of sharing data including an encryption process. 11 corresponds to a process in which the first terminal 10 provides data and the second terminal 20 receives the provided data.

The management server 110 transmits its public key P _s to the first terminal 10 (1001). The first terminal 10 encrypts the data using the public key P _s (1011). The first terminal 10 transmits the encrypted data to the management server 110 (1012).

The management server 110 may decrypt the received data with its encryption key (1021). The management server 110 transmits the decoded data to the storage server 155 (1022). One or more storage servers 155 store the decoded data (1031). As described above, the plurality of storage servers 155 may configure the data storage blockchain 150. The storage server 155 transmits storage information about the stored data to the management server 110 (1032).

Thereafter, the second terminal 20 requests specific data from the management server 110 (1041). The management server 110 retrieves data through the above-described process (1051). The management server 110 transmits the storage information for the identified data to the second terminal 20 (1052).

The second terminal 20 may request specific data from the storage server 155 using the storage information (1061). In this case, the second terminal 20 may transmit its public key _Pue2 to the storage server 155 (1061).

The storage server 155 may retrieve the requested data and encrypt the data using the public key _Pue2 (1062). The storage server 155 transmits the encrypted data to the second terminal 20 (1063). The second terminal 20 may decrypt the received data with its own encryption key (1071).

In addition, the data sharing method as described above may be implemented as a program (or application) including an executable algorithm that can be executed on a computer. The program may be stored and provided in a non-transitory computer readable medium.

The non-transitory readable medium refers to a medium that stores data semi-permanently and is readable by a device, not a medium storing data for a short time such as a register, a cache, a memory, and the like. Specifically, the various applications or programs described above may be stored and provided in a non-transitory readable medium such as a CD, a DVD, a hard disk, a Blu-ray disk, a USB, a memory card, a ROM, or the like.

The embodiments and the drawings attached to this specification are merely to clearly show a part of the technical idea included in the above-described technology, and those skilled in the art can easily make it within the scope of the technical idea included in the description and the drawings of the above-described technology. It will be apparent that both the inferred modifications and the specific embodiments are included in the scope of the above-described technology.

Claims

Registering, by the management server, the user block data including the user information and the hash key for each of the plurality of users in the user information blockchain;

Receiving, by the management server, storage information for data provided from a first user from a storage server; And

And receiving, by the management server, a request for specific data from a second user, and transmitting the storage information for the specific data to the second user.
The method of claim 1,

The management server further comprises the step of registering the metadata of the data in a metadata blockchain.
The method of claim 2,

And the management server transfers at least one of the information included in the request to the metadata blockchain to identify the specific data.
The method of claim 1,

And the management server registers the point transaction details according to the sharing of the specific data in the point information convex chain managing the points of the second user and the points of the first user.
The method of claim 1,

And the storage information comprises at least one of an identifier of the storage server, an identifier of the data, a location where the data is stored in a storage medium, a verification key, a file size, and file partition information.
The method of claim 1,

And a plurality of storage servers, wherein a plurality of storage servers constitute a data storage blockchain holding the storage information.
The method of claim 1,

The management server identifies a corresponding user in the user information blockchain based on user information about the first user or the second user, authenticates the user, and transmits an authentication token to the first user or the second user. The data sharing method based on a plurality of blockchains further comprising the step of.
Receiving, by the management server, identification information about specific data from the user;

Identifying, by the management server, whether the specific data exists among data stored in a storage server using the identification information; And

And extracting the storage information for the specific data from the storage information previously held by the management server and transmitting the stored information to the user.
The method of claim 8,

Receiving, by the management server, user information from the user, generating a hash key based on the received user information, and registering the user information and the hash key in a user information blockchain. Based on data sharing.
The method of claim 9,

The management server further comprises the step of performing a user authentication by comparing the information stored in the user information blockchain and the user information transmitted by the user.
The method of claim 8,

The management server further comprises the step of registering the metadata of the specific data in a metadata blockchain.
The method of claim 11,

And the management server transfers the information included in the identification information to the metadata blockchain to identify the specific data.
The method of claim 8,

The management server is a data sharing method based on a plurality of block chains to register the point transaction details according to the sharing of the specific data in the point information convex chain for managing the user's points.
The method of claim 8,

The management server receives and stores storage information for data stored in a data storage blockchain configured by a plurality of storage servers,

And transmitting the information included in the identification information to a metadata blockchain storing the metadata of the specific data, thereby identifying the specific data based on the identified metadata.
The method of claim 14,

The management server further comprises the step of extracting the storage information for the identified specific data and transmitting to the user.
The method of claim 8,

And the user receiving the specific data from the storage server using the storage information.
The method of claim 8,

And the storage information comprises at least one of an identifier of the storage server, an identifier of the data, a location where the data is stored in a storage medium, a verification key, a file size, and file partition information.