Server device
The server device uses dual ledgers to manage authority information, enabling secure data sharing between specific nodes in a distributed ledger network, enhancing data integrity and reducing verification redundancy.
Patent Information
- Application Number
- JP2021153996
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-09-22
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-09-22
AI Technical Summary
Existing distributed ledger technologies do not allow for data sharing between specific nodes while maintaining data integrity and preventing falsification.
A server device with a first and second distributed ledger is used to manage authority information, enabling data sharing only between authorized nodes by storing and updating this information in the first ledger and transmitting data via the second ledger based on authority information.
This approach enhances data sharing security by improving tampering resistance and reducing the need for redundant identity verification processes, ensuring data is shared only between authorized nodes.
Smart Images

Figure 0007589662000001 
Figure 0007589662000002 
Figure 0007589662000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a server device that forms a network using distributed ledger technology. [Background technology]
[0002] Japanese Patent No. 6587370 (Patent Document 1) discloses a document management system that uses block chain technology to prevent tampering of documents shared among multiple PCs (Personal Computers). In this document management system, multiple PCs are connected via a network to form a PC cluster. When a document is recorded in a PC, this document management system has a means for reflecting the document in the records of other PCs belonging to the PC cluster. This document management system also has a means for generating a hash value of the document and including it in a block. This allows documents to be shared within the PC cluster while preventing document tampering. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 6587370 Summary of the Invention [Problem to be solved by the invention]
[0004] Data stored in a distributed ledger such as a blockchain can be accessed by all nodes participating in the distributed ledger network. Depending on the content of the data, there may be cases where data needs to be shared only among specific nodes participating in the distributed ledger network. Previously, such cases could not be handled.
[0005] The present disclosure has been made to solve the above-mentioned problems, and the purpose of the present disclosure is to enable data sharing only among specific nodes participating in a distributed ledger network, while suppressing data tampering using distributed ledger technology. [Means for solving the problem]
[0006] (1) A server device according to an aspect of the present disclosure is a server device used in a data sharing system using distributed ledger technology. The data sharing system includes a plurality of other server devices. The server device includes a first distributed ledger configured to share authority information regarding data sharing with the plurality of other server devices. The authority information includes information for limiting other server devices with which the data is shared among the plurality of other server devices. Furthermore, the server device includes a second distributed ledger configured to share the data with the other server devices based on the authority information.
[0007] According to the above configuration, authority information, which is information for limiting other server devices with which data is shared, is managed in the first distributed ledger, and the data can be shared only with other server devices based on the authority information in the second distributed ledger. By managing the authority information in the first distributed ledger, the authority information is shared among devices included in the data sharing system (the server device and multiple other server devices). Therefore, the authority information is monitored in all devices, so that the tamper resistance of the authority information can be improved. Then, data can be shared only with other server devices based on the authority information.
[0008] (2) In one embodiment, the server device further includes a control device that updates the first distributed ledger and the second distributed ledger, and transmits data stored in the second distributed ledger to other server devices based on the authority information.
[0009] According to the above configuration, data stored in the second distributed ledger can be transmitted to other server devices and shared with the other server devices.
[0010] (3) In one embodiment, when the authority information is updated, the control device stores the updated authority information in the first distributed ledger.
[0011] According to the above configuration, since the updated authority information is stored in the first distributed ledger, the updated authority information can be shared with the other server devices included in the data sharing system. As a result, the authority information is monitored by all devices (the server device and the other server devices) included in the data sharing system, so that the tamper-resistance of the authority information can be improved.
[0012] (4) In an embodiment, the server device provides a first application for providing a predetermined service. The first application is installed in a terminal device of a user. The terminal device provides user information about the user, which is input when the first application is installed, to the server device. Upon acquiring the user information, the control device sets the server device in authority information for the user information and stores the authority information in the first distributed ledger.
[0013] A user of the terminal device provides user information to a server device that provides a first application. According to the above configuration, since the authority information set by the server device is stored in the first distributed ledger, it is possible to share with a plurality of other server devices that the server device has been given the authority to obtain the user information.
[0014] (5) In an embodiment, the predetermined service includes an identity verification service. The user information includes personal information of the user. Upon acquiring the user information, the control device performs the identity verification service on the user information and stores the verified user information in the second distributed ledger.
[0015] According to the above configuration, since user information whose identity has been verified is stored in the second distributed ledger, it is possible to prevent the user information from being shared with other server devices that do not have the authority to obtain the user information.
[0016] (6) In one embodiment, the control device stores information indicating the results of the identity verification service in the first distributed ledger.
[0017] According to the above configuration, since the information indicating the implementation result of the identity verification service is stored in the first distributed ledger, the updated authority information can be shared with a plurality of other server devices. As a result, the information indicating the implementation result of the identity verification service is monitored by all devices included in the data sharing system, so that the tamper resistance of the information indicating the implementation result of the identity verification service can be improved.
[0018] (7) In an embodiment, the first application includes a second application. The second application is an application provided by a specific server device among a plurality of other server devices. When the user registers to use the second application, the first application requests the terminal device to consent to sharing user information with the second application. If consent is obtained, the control device adds the specific server device to the authority information.
[0019] According to the above configuration, when consent to sharing user information is obtained from the second application, a specific server device is added to the authority information. This authority information is stored in the first distributed ledger. Therefore, the authority information to which the specific server device has been added can be shared with a plurality of other server devices.
[0020] (8) In one embodiment, the control device shares the user information stored in the second distributed ledger with a specified server device based on the authority information added by the specified server device.
[0021] According to the above configuration, when a specific server device is added to the authority information, the user information can be shared with the specific server device.
[0022] (9) In one embodiment, when an application for withdrawal from registration of the second application is made, the control device deletes the specified server device from the authority information.
[0023] According to the above configuration, in response to an application for withdrawal registration of the second application, a predetermined server device that provides the second application is deleted from the authority information. Since this updated authority information is stored in the first distributed ledger, the updated authority information can be shared with a plurality of other server devices.
[0024] (10) In one embodiment, the system further includes a control device that updates the first distributed ledger and the second distributed ledger. When a server device is added to the authority information, the control device obtains data from other server devices that have the data and stores the data in the second distributed ledger.
[0025] According to the above configuration, when the server device itself is added to the authority information, the server device can obtain data corresponding to the authority information from another server device that has the data.
[0026] (11) In one embodiment, when the server device is deleted from the authority information, the control device deletes data corresponding to the authority information from the second distributed ledger.
[0027] According to the above configuration, when the authority to hold data of oneself (the server device) is lost, the data can be appropriately deleted from the second distributed ledger.
[0028] (12) In one embodiment, the server device provides a second application included in a first application provided by a specific server device, which is one of multiple other server devices. The first application is an application that provides an identity verification service. The first distributed ledger stores information indicating the results of the identity verification service provided by the specific server device. When registration for use of the second application is made, the control device omits the implementation of identity verification by referring to the information indicating the results of the identity verification service.
[0029] According to the above configuration, the implementation result of the identity verification service implemented by the predetermined server device providing the first application is shared by the first distributed ledger, thereby omitting the implementation of identity verification, thereby reducing the man-hours required for implementing identity verification. Effect of the Invention
[0030] According to the present disclosure, distributed ledger technology can be used to suppress data tampering while enabling data sharing only among specific nodes participating in the distributed ledger network. [Brief description of the drawings]
[0031] [Figure 1] 1 is a diagram showing a schematic configuration of a data sharing system according to an embodiment; [Diagram 2] 2 is a diagram illustrating a hardware configuration of a management server. FIG. [Diagram 3] 2 is a diagram illustrating a hardware configuration of a service server. FIG. [Figure 4] FIG. 2 is a diagram illustrating a hardware configuration of a client device. [Diagram 5] FIG. 1 is a diagram illustrating an outline of a system configuration of a data sharing system. [Figure 6] FIG. 2 is a diagram showing a schematic diagram of the flow of information in the process executed when a wallet application is installed on a client device. [Figure 7] FIG. 13 is a diagram showing a schematic diagram of the flow of information in the process executed when a first application is registered for use within a wallet application. [Figure 8] FIG. 13 is a diagram showing a schematic diagram of an information flow in a process executed when registering withdrawal from a first application. [Figure 9] 11 is a flowchart showing a procedure of a process executed when a wallet application is installed in a client device. [Figure 10] 13 is a flowchart showing a procedure of a process executed when registration for use of a first application is performed. [Figure 11] 13 is a flowchart showing a procedure of a process executed when registering withdrawal from a first application (first service). [Figure 12] FIG. 13 is a diagram illustrating a flow of information in a process executed when a wallet application is installed on a client device in a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0032] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference characters, and the description thereof will not be repeated.
[0033] [Embodiment Mode] <Overall configuration of data sharing system> 1 is a diagram showing a schematic configuration of a data sharing system 1 according to the present embodiment. The data sharing system 1 according to the present embodiment is a system for forming a consortium network (hereinafter also simply referred to as a "network") NW among a plurality of companies and sharing data using distributed ledger technology.
[0034] The data sharing system 1 includes a management server 2, four service servers 3-1 to 3-4, a client device 4, and an application providing server 5. Each of the four service servers 3-1 to 3-4 belongs to a different company (for example, company A, company B, company C, and company D). For example, the service server 3-1 belongs to company A, the service server 3-2 belongs to company B, the service server 3-3 belongs to company C, and the service server 3-4 belongs to company D. Hereinafter, when there is no particular distinction between the service servers 3-1 to 3-4, they are collectively referred to simply as "service servers 3."
[0035] The management server 2 is a server belonging to a management company that operates the network NW. The management server 2 manages the network NW. The management server 2 accepts applications for participation in the network NW from each service server 3. The management server 2 permits the service server 3 to participate in the network NW based on an operation by the administrator of the management server 2 to permit participation or based on the result of judging a predetermined condition (a function of the doorman node described later). In this embodiment, four service servers 3 belonging to companies A, B, C, and D are permitted to participate in the network NW.
[0036] The management server 2 also manages an application providing server 5. The application providing server 5 is a so-called marketplace that provides applications. The management server 2 provides a wallet application 50 in the application providing server 5.
[0037] The application providing server 5 is configured to be able to communicate with the client device 4. The application providing server 5 provides applications to the client device 4. The client device 4 can access the application providing server 5 and install applications provided by the application providing server 5. In this embodiment, the application providing server 5 provides a wallet application 50. The client device 4 can install the wallet application 50 from the application providing server 5. Note that, in this embodiment, an example will be described in which the application providing server 5 provides one application (wallet application 50), but the application providing server 5 may provide a plurality of applications.
[0038] The wallet application 50 is an application that provides a Know Your Customer (KYC) service. The wallet application 50 may be an application that provides various services in addition to the KYC service.
[0039] The wallet application 50 is a so-called super application, and includes a first application 51, a second application 52, a third application 53, and a fourth application 54 as so-called mini applications. The first application 51 is an application for using a first service provided by a company A that manages a service server 3-1. The service server 3-1 of the company A registers the first application 51 as a mini application in the wallet application 50. The second application 52 is an application for using a second service provided by a company B that manages a service server 3-2. The service server 3-2 of the company B registers the second application 52 as a mini application in the wallet application 50. The third application 53 is an application for using a third service provided by a company C that manages a service server 3-3. The service server 3-3 of the company C registers the third application 53 as a mini application in the wallet application 50. The fourth application 54 is an application for using a fourth service provided by a company D that manages a service server 3-4. The service server 3-4 of Company D registers the fourth application 54 as a mini application in the wallet application 50.
[0040] Each of the first application 51 to the fourth application 54 is developed by utilizing the framework of the wallet application 50. Each of the first application 51 to the fourth application 54 may, for example, run on a browser in the wallet application 50 and provide services (first service to fourth service) provided by each of the service servers 3-1 to 3-4 in cooperation with the API (Application Program Interface) 210 of the management server 2 and the APIs 310-1 to 310-4 of each of the service servers 3-1 to 3-4. Each of the first service to fourth service may be any service such as a rental car service, a car sharing service, an insurance service, an administrative service, a car dealership service, a maintenance business service, etc.
[0041] The client device 4 is, for example, a smartphone, a tablet terminal, a desktop PC (Personal Computer), a notebook PC, or other information processing terminal having a communication function. The client device 4 can use the services provided by each company (service servers 3-1 to 3-4) by launching the first application 51, the second application 52, the third application 53, and the fourth application 54 from within the installed wallet application 50. As will be described in detail later, when each mini application is launched for the first time (when registering for use), consent is requested to provide user information including personal information of the user of the client device 4 to the service server 3, which is the provider of the application.
[0042] Two distributed ledger platform software programs are installed in each of the management server 2 and the service server 3. The first distributed ledger platform software program (hereinafter also referred to as "first software") includes a smart contract for functioning as a node that constructs a broadcast-type main chain. The second distributed ledger platform software program (hereinafter also referred to as "second software") includes a smart contract for functioning as a node that constructs a P2P (Peer to Peer)-type subchain. For example, CORDA (registered trademark) may be adopted as the second distributed ledger platform. By the functioning of the installed first software, the control device 21 (FIG. 2) included in the management server 2 and the control device 31 (FIG. 3) included in the service server 3 function as the main chain node 200A (FIG. 2) and the main chain node 300A (FIG. 3), respectively. By the functioning of the introduced second software, the control device 21 (Figure 2) included in the management server 2 and the control device 31 (Figure 3) included in the service server 3 function as sub-chain node 200B (Figure 2) and sub-chain node 300B (Figure 3), respectively.
[0043] Furthermore, the control device 21 (FIG. 2) included in the management server 2 and the control device 31 (FIG. 3) included in the service server 3 also function as an off-chain node 200C (FIG. 2) and an off-chain node 300C (FIG. 3) that execute processes outside the network NW, respectively. In FIG. 1, the main chain node 200A, the sub-chain node 200B, and the off-chain node 200C are collectively referred to as "node 200", and the main chain node 300A, the sub-chain node 300B, and the off-chain node 300C are collectively referred to as "node 300".
[0044] The management server 2 has a distributed ledger set 270. The service server 3 has a distributed ledger set 370. The distributed ledger set 270 and the distributed ledger set 370 have similar data structures. Therefore, the following description will be given of the distributed ledger set 270 as a representative example.
[0045] The distributed ledger set 270 includes a distributed ledger 271 (Figure 2) that stores transaction data shared in the main chain, and a distributed ledger 272 (Figure 2) that stores transaction data shared in the subchain.
[0046] The distributed ledger 271 is a distributed ledger that stores transaction data shared in a broadcast-type main chain, and is made public to all main chain nodes participating in the network NW. That is, the distributed ledger 271 held by the management server 2, the distributed ledger 371-1 held by the service server 3-1 (FIG. 3), the distributed ledger 371-2 held by the service server 3-2 (FIG. 3), the distributed ledger 371-3 held by the service server 3-3 (FIG. 3), and the distributed ledger 371-4 held by the service server 3-4 (FIG. 3) hold the same transaction data.
[0047] The distributed ledger 272 is a distributed ledger that stores transaction data shared in a P2P sub-chain, and the disclosure range is limited to the parties involved. Although details will be described later, the disclosure range of the distributed ledger 272 is limited based on the authority information (consent information) stored in the main chain (distributed ledger 271). Therefore, the distributed ledger 271 held by the management server 2, the distributed ledger 371-1 held by the service server 3-1 (FIG. 3), the distributed ledger 371-2 held by the service server 3-2 (FIG. 3), the distributed ledger 371-3 held by the service server 3-3 (FIG. 3), and the distributed ledger 371-4 held by the service server 3-4 (FIG. 3) may hold different transaction data.
[0048] Furthermore, the control device (FIG. 2) included in the management server 2 functions as a platform provider 60 by the function of software stored in a ROM (Read Only Memory). The platform provider 60 has a function of managing the network NW. The platform provider 60 includes a doorman node 61, a network map node 63, and a notary node 65.
[0049] The doorman node 61 approves a participation application from a node 300 that wishes to participate in the network NW. The doorman node 61 also issues a certificate to the node 300. A node 300 that has joined the network NW creates a pair of a private key and a public key when joining, and transmits a request for certificate issuance to the doorman node 61. The doorman node 61 verifies predetermined conditions and issues a certificate to the node 300 that has requested certificate issuance.
[0050] The network map node 63 is the node that has been issued a certificate by the doorman node 61 (i.e., the network ParticipationThe network map node 63 stores information (e.g., IP address) of the node 300 that is authorized to transmit transaction data. The network map node 63 functions as a Domain Name System (DNS) in the network NW. The nodes 200 and 300 recognize the destination of the transaction data based on the information provided by the network map node 63, for example.
[0051] The notary node 65 provides finality to transaction data in the sub-chain. When node 200 (sub-chain node 200B) and node 300 (sub-chain node 300B) generate transaction data, they send data including a hash value of the transaction data and an index of the output of the transaction data to the notary node 65. The notary node 65 holds the above data received from node 200 or node 300 in order, thereby guaranteeing the order of the transaction data in the sub-chain.
[0052] 2 is a diagram for explaining the hardware configuration of the management server 2. The management server 2 includes a control device 21, a ROM 22, a RAM (Random Access Memory) 23, a communication device 24, an input device 25, a display device 26, and a storage device 27. The control device 21, the ROM 22, the RAM 23, the communication device 24, the input device 25, the display device 26, and the storage device 27 are connected to a bus 29.
[0053] The control device 21 is configured, for example, by an integrated circuit including a CPU (Central Processing Unit). The control device 21 deploys various programs stored in the ROM 22 in the RAM 23 and executes them. The various programs include an operating system and the like. The RAM 23 functions as a working memory and temporarily stores various data required for the execution of the various programs. As will be described in detail later, the control device 21 includes a main chain node 200A that functions in the main chain, a sub-chain node 200B that functions in the sub-chain, and an off-chain node 200C that functions off-chain (outside the network NW). The control device 21 also includes the above-mentioned platform provider 60 that functions in the network NW.
[0054] The communication device 24 is configured to be capable of communicating with external devices. The external devices include, for example, the service server 3, the client device 4, and the application providing server 5. The communication between the communication device 24 and the external devices is performed using the Internet, a wide area network (WAN), a local area network (LAN), an Ethernet (registered trademark) network, a public network, a private network, a wired network, a wireless network, or the like, or a combination of these.
[0055] The input device 25 includes an input device, such as a mouse, a keyboard, a touch panel, and / or other device capable of receiving a user's operation.
[0056] The display device 26 includes a display. The display device 26 displays various images on the display according to a control signal from the control device 21. The display is, for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or other display device.
[0057] The storage device 27 includes a storage medium such as a hard disk or a flash memory. The storage device 27 stores a distributed ledger set 270, a private key 275, and a plurality of public keys 277. Details of the distributed ledger set 270 and the distributed ledger set 370 described below will be described later.
[0058] The private key 275 is a private key of the management company that manages the management server 2. For example, when the management server 2 first forms a network, the control device 21 generates a private key and a public key. Then, the control device 21 transmits the generated public key to a certification authority (not shown) and is authenticated. The certification authority is a certification organization that issues electronic certificates. The certification authority issues an electronic certificate including information on the public key. The control device 21 stores the private key 275 corresponding to the authenticated public key in the storage device 27. The control device 21 also transmits the authenticated public key (electronic certificate) to the service servers 3-1 to 3-4 participating in the network NW.
[0059] The multiple public keys 277 include a public key of company A, a public key of company B, a public key of company C, and a public key of company D. The control device 21 stores the public keys received from the service server 3 in the storage device 27. The storage device 27 may also store its own (managing company's) public key.
[0060] When generating transaction data, the control device 21 creates a digital signature using the private key 275 and includes the digital signature in the transaction data. When the control device 21 receives transaction data from the service server 3, the control device 21 verifies the validity of the digital signature using the public key of the sender of the transaction data, out of the multiple public keys 277.
[0061] Fig. 3 is a diagram for explaining the hardware configuration of the service server 3. The service servers 3-1 to 3-4 basically have the same hardware configuration. In the explanation of Fig. 3, when specifying which company the service server 3 belongs to, the service server 3-1 of company A will be explained as an example.
[0062] The service server 3 includes a control device 31, a ROM 32, a RAM 33, a communication device 34, an input device 35, a display device 36, and a storage device 37. The control device 31, the ROM 32, the RAM 33, the communication device 34, the input device 35, the display device 36, and the storage device 37 are connected to a bus 39.
[0063] The control device 31 is configured, for example, by an integrated circuit including a CPU. The control device 31 deploys various programs stored in the ROM 32 in the RAM 33 and executes them. The various programs include an operating system and the like. The RAM 33 functions as a working memory and temporarily stores various data required for executing the various programs. The control device 31 includes a main chain node 300A that functions in the main chain, a sub-chain node 300B that functions in the sub-chain, and an off-chain node 300C that functions off-chain (outside the network NW).
[0064] The communication device 34, the input device 35 and the display device 36 basically have the same configurations as the communication device 24, the input device 25 and the display device 26 of the management server 2, respectively, and therefore their description will not be repeated.
[0065] The storage device 37 includes a storage medium such as a hard disk or a flash memory. The storage device 37 stores a distributed ledger set 370, a private key 375, and a plurality of public keys 377.
[0066] The private key 375-1 is a private key of the A company that manages the service server 3-1. For example, when the service server 3-1 of the A company first joins the network NW, the control device 31-1 generates a private key and a public key. Then, the control device 31-1 transmits the generated public key to a certification authority (not shown) and receives authentication. The control device 31-1 stores the private key 375-1 corresponding to the authenticated public key in the storage device 37-1. The control device 31-1 also transmits the authenticated public key (electronic certificate) to the doorman node 61 and receives the certificate. This certificate is included in the transaction data issued by the service server 3-1. The control device 31-1 also transmits the authenticated public key (electronic certificate) to the management server 2 and the service servers 3-2 to 3-4 that form the network NW.
[0067] The multiple public keys 377-1 include a public key of a management company, a public key of a company B, a public key of a company C, and a public key of a company D. The control device 31-1 stores the public keys received from the management server 2 and the service servers 3-2 to 3-4 in the storage device 37-1. The storage device 37-1 may also store its own (company A's) public key.
[0068] When generating transaction data, the control device 31-1 creates an electronic signature using the private key 375-1 and includes the electronic signature in the transaction data. When the control device 31-1 receives transaction data from the management server 2 or the service servers 3-2 to 3-4, the control device 31-1 verifies the validity of the electronic signature using the public key of the sender of the transaction data, out of the multiple public keys 377-1.
[0069] 4 is a diagram for explaining the hardware configuration of the client device 4. The client device 4 includes a control device 41, a ROM 42, a RAM 43, a communication device 44, an input device 45, a display device 46, and a storage device 47. The control device 41, the ROM 42, the RAM 43, the communication device 44, the input device 45, the display device 46, and the storage device 47 are connected to a bus 49.
[0070] The control device 41 is configured, for example, by an integrated circuit including a CPU. The control device 41 loads various programs stored in the ROM 42 into the RAM 43 and executes them. The various programs include an operating system and the like. The RAM 43 functions as a working memory and temporarily stores various data required for executing the various programs. The control device 41 has a function of installing applications from the application providing server 5 via the communication device 44 and executing the installed applications.
[0071] The communication device 44 and the display device 46 have basically the same configuration as the communication device 24 and the display device 26 of the management server 2, respectively, and therefore their description will not be repeated.
[0072] The input device 45 includes an input device such as a mouse, a keyboard, a touch panel, and / or other device capable of receiving a user's operation. The input device 45 further includes an information acquisition device such as a camera or a scanner.
[0073] The storage device 47 includes a storage medium such as a hard disk or a flash memory. The storage device 47 stores applications installed from the application providing server 5. In this embodiment, the storage device 47 stores a wallet application 50.
[0074] <Using the Wallet App and Mini App> In the data sharing system 1 having the above configuration, the wallet application 50 (super application) installed in the client device 4 can be used after user information is registered and the user is verified (KYC). Furthermore, in order to use the mini-applications (first application 51 to fourth application 54) of the wallet application 50, the user is required to provide user information to a company that provides the mini-applications to be used (for example, company A for the first application 51) and undergo KYC by the company. For example, when a user registers to use the first application 51, the user is required to provide user information to the service server 3-1 (company A), but is not required to provide user information to the service servers 3-2 to 3-4 (company B, company C, and company D). In general, in a distributed ledger technology such as a blockchain, data is shared among all nodes participating in the network, so data cannot be shared only between specific nodes. There is a demand for a method of sharing data only between specific nodes while improving the resistance of data to tampering by using a distributed ledger technology. Also, regarding KYC, conducting it for each service server 3 (each company) that provides a mini-app is troublesome for both companies and users, and measures are being called for.
[0075] Therefore, in the data sharing system 1 according to the present embodiment, the KYC results performed by the management company (management server 2) providing the super app are stored in the main chain and shared with participants in the network NW. When an application for use of a mini app is made, each company providing a mini app can omit carrying out KYC by checking the KYC results on the main chain and assuming that the company has performed identity verification of the user.
[0076] Furthermore, a company that receives an application to use a mini app needs to obtain user information in order to provide the service. In the data sharing system 1 according to this embodiment, the user information entered when registering the user information in the wallet app 50 is stored in the distributed ledger 272 (sub-chain) of the management server 2 after the KYC service is implemented. When the user of the client device 4 agrees to provide his / her user information to the mini app, the user information stored in the distributed ledger 272 is shared by the sub-chain with the distributed ledger 372 of the service server 3 that provides the mini app.
[0077] Fig. 5 is a diagram showing an outline of the system configuration of the data sharing system 1. A series of processes from registration of use of the wallet application and mini application to registration of withdrawal will be described with reference to Fig. 5 and Figs. 6 to 8 described later.
[0078] <<Wallet App Installation: KYC>> FIG. 6 is a diagram showing a schematic flow of information in a process executed when the wallet application 50 is installed in the client device 4. With reference to FIGS. 5 and 6, when the wallet application 50 is installed in the client device 4, the wallet application 50 (application providing server 5) requests the client device 4 to register an account. In response to the request for account registration, the control device 41 of the client device 4 generates a private key and a public key. The control device 41 may transmit the generated public key to a certification authority (not shown) for authentication. The control device 41 stores the private key corresponding to the authenticated public key in the storage device 47. The authenticated public key is also used as an ID of the client device 4 (user) in the main chain, as will be described later.
[0079] Next, the wallet application 50 requests the client device 4 to register user information. The control device 41 of the client device 4 causes, for example, a display screen of the display device 46 to display an input field for user information. The user information includes, for example, information such as name, date of birth, address, and age. The user inputs information such as name, date of birth, address, and age via the input device 45. Furthermore, the user information further includes information for identity verification. The information for identity verification may be, for example, a driver's license, a My Number card, or a health insurance card. For example, the user photographs the driver's license using a camera or the like included in the input device 45, and registers the information as user information.
[0080] The registered user information is sent to the application providing server 5 via the communication device 44 of the client device 4. The application providing server 5 accesses the API 210 of the management server 2 that implements the KYC service, and transmits a KYC implementation request together with the user information to the management server 2. In addition, information on the public key of the client device 4 is also sent from the client device 4 to the management server 2 via the application providing server 5. Note that the application providing server 5 may check whether there are any omissions in the user information and / or whether the capacity of the image data of the photographed driver's license or the like is within the range of standards established for implementing the KYC service.
[0081] Upon receiving a request to implement KYC, the management server 2 implements the KYC service. Then, the management server 2 stores KYC-completed user information in the distributed ledger 272 to update the sub-chain, issues an ID of the user of the client device 4 (hereinafter also referred to as a "user ID") to the main chain, stores the KYC result in the distributed ledger 271 in a format linked to the user ID, and updates the main chain.
[0082] Specifically, when a request to implement KYC is received, the off-chain node 200C of the control device 21 functions. The off-chain node 200C implements KYC using the acquired user information. The implementation of KYC may involve the work of an administrator of the management server 2 or an employee of the company that operates the management server 2. If it is determined that there is no problem with identity verification as a result of implementing KYC, the off-chain node 200C outputs information indicating the completion of KYC to the sub-chain node 200B.
[0083] When the information indicating the completion of KYC is acquired, the sub-chain node 200B of the control device 21 functions. The sub-chain node 200B generates transaction data for updating the sub-chain. At this point, the user of the client device 4 has agreed to provide user information to the wallet application 50, but has not agreed to provide user information to the mini-application in the wallet application 50. Therefore, at this point, the user information is stored only in the distributed ledger 272 of the management server 2, and is not stored in the distributed ledgers 372-1 to 372-4 of the service servers 3-1 to 3-4. Therefore, the transaction data includes the user information, and the sub-chain node 200B (the management server 2) is specified as the destination of the transaction data. Furthermore, the transaction data includes a hash value of the user information (hereinafter also referred to as a "data hash"). The sub-chain node 200B processes this transaction data and stores the user information and the data hash in the distributed ledger 272. The reason for storing the data hash in the distributed ledger 272 is to reduce the amount of work required to generate a hash value of user information each time an update check is performed on the consent information (authority information) described later. In Fig. 5, the user information and data hash are represented as "DataA". As described above, at this point in time, DataA is stored only in the distributed ledger 272 of the management server 2.
[0084] When the sub-chain is updated, the main chain node 200A of the control device 21 functions. The main chain node 200A generates transaction data for updating the main chain. Specifically, the main chain node 200A generates transaction data including a data hash, consent information, and information indicating a KYC confirmation result. All nodes forming the main chain (the main chain node 200A and the main chain nodes 300A-1 to 300A-4) are specified as the destination of the transaction data. In addition, the information indicating the owner of the transaction data includes a hash value of the public key of the client device 4. This transaction data is broadcast to the network NW and processed by the main chain node 200A of the management server 2 and the main chain node 300A of the service server 3, and the hash value of the public key of the client device 4 is issued to the main chain as the ID of the client device 4 (hereinafter also referred to as "user ID"). Then, the data hash, consent information, and information indicating a KYC confirmation result are stored in the main chain (the distributed ledger 271 and the distributed ledger 371) in a format linked to the user ID.
[0085] The consent information (authority information) is information for determining the sharing range of user information, and includes information on "who (From)", "to whom (To)", and "what data (Hash) consented to". Specifically, the consent information includes information (From) indicating the consent source, information (To) indicating the consent recipient, and information (Hash) indicating the target data. In the above example, the information indicating the consent source is, for example, a user ID (hash value of the public key of the client device 4). The information indicating the consent recipient is, for example, the ID of the management server 2 (for example, a hash value or address of the public key of the management server 2), which is information for identifying the management server 2. The information indicating the target data is, for example, a hash value (data hash) of the user information.
[0086] The information on the KYC confirmation result is information indicating the implementation result of KYC, and includes information on "who (From)", "who (To)", and "what data (Hash) was confirmed". Specifically, the information on the KYC confirmation result includes information (From) indicating the person who implemented KYC, information (To) indicating the person who is the subject of KYC, and information (Hash) indicating the data that is the subject of KYC. In the above example, the information indicating the person who implemented KYC is, for example, the ID of the management server 2 (for example, the hash value or address of the public key of the management server 2), which is information for identifying the management server 2. The information indicating the person who is the subject of KYC is, for example, a user ID (the hash value of the public key of the client device 4). The information indicating the data that is the subject of KYC is, for example, a hash value (data hash) of the user information.
[0087] As described above, when the wallet application 50 is installed in the client device 4, KYC of the user is performed by the management server 2 (management company) that provides the wallet application 50. Then, the user information is stored in the distributed ledger 272 of the management server 2. Furthermore, a user ID is issued to the main chain, and the KYC result, a hash value (data hash) of the user information, and consent information are stored in the main chain (the distributed ledger 271 and the distributed ledgers 371-1 to 371-4) in a format linked to the user ID.
[0088] <<Mini App Registration: KYC Omission>> Fig. 7 is a diagram showing a schematic diagram of the flow of information in the process executed when the first application 51 is registered for use (first use) in the wallet application 50. In Fig. 7, the first application 51 is taken as an example of a mini application. With reference to Figs. 5 and 7, it is assumed that company A providing the first service has decided to provide (distribute) the first application 51 as a mini application of the wallet application 50. Therefore, the first application 51 is provided as a mini application of the wallet application 50.
[0089] For example, the user of the client device 4 launches the wallet application 50 and selects and operates the first application 51 displayed on the display screen of the display device 46. When the first application 51 is used (started) for the first time, the wallet application 50 (application providing server 5) requests the user of the client device 4 to register for use of the first application 51. Specifically, the wallet application 50 requests the user of the client device 4 to provide user information to the first application 51 (service server 3-1 providing the first service). In response to this request, the control device 41 of the client device 4 causes the display device 46 to display a consent screen requesting the user to provide user information to the first application 51 (service server 3-1 providing the first service). The user of the client device 4 operates the input device 45 to consent to providing user information to the first application 51.
[0090] The control device 41 of the client device 4 transmits information indicating that the user has consented to the provision of the user information (information indicating consent) to the application providing server 5 via the communication device 44. The application providing server 5 transmits the information indicating consent to the management server 2.
[0091] When the management server 2 receives the information indicating consent, it updates the consent information in the main chain, and then transmits the user information to the service server 3-1 in the sub-chain based on the updated consent information.
[0092] Specifically, when information indicating consent is received, the off-chain node 200C of the control device 21 functions, and the off-chain node 200C notifies the main chain node 200A that information indicating consent has been received.
[0093] Upon receiving the notification, the main chain node 200A updates the consent information. Specifically, transaction data is generated including consent information in which the ID of the service server 3-1 (for example, the hash value or address of the public key of the service server 3-1) is added to the information indicating the consent recipient. That is, the information indicating the consent recipient included in this consent information includes the ID of the management server 2 and the ID of the service server 3-1. The main chain node 200A broadcasts the generated transaction data to the network NW. The transaction data is processed by the main chain nodes 200A and 300A, thereby updating the distributed ledgers 271 and 371. As a result, the consent information stored in the main chain is updated.
[0094] When the consent information in the distributed ledger 271 (main chain) is updated, the sub-chain node 200B checks the contents of the updated consent information. Through this check, the sub-chain node 200B recognizes that the service server 3-1 has the authority to obtain user information. As described above, a hash value is stored in the information (Hash) indicating the data that is the subject of the consent information. In this embodiment, since the data hash is stored in addition to the user information in the distributed ledger 272, when performing the above check, the sub-chain node 200B can identify the user information to be shared with the sub-chain node 300B of the service server 3-1 without hashing the user information again.
[0095] The sub-chain node 200B generates transaction data that stores user information and a data hash. The destination of this transaction data is specified as the sub-chain node 300B-1 of the service server 3-1.
[0096] When the sub-chain node 200B generates transaction data to be sent to the sub-chain node 300B-1 of the service server 3-1, it sends data including a hash value of the transaction data and an index of the output of the transaction data to the notary node 65. This gives finality to the transaction data.
[0097] The sub-chain node 300B-1 of the service server 3-1 processes the transaction data received from the sub-chain node 200B of the management server 2 and stores the user information in the distributed ledger 372-1. As a result, the user information is synchronized (shared) and the sub-chain is updated. At this time, the transaction data is not transmitted to the sub-chain nodes 300B-2 to 300B-4 of the service servers 3-2 to 3-4. As shown in FIG. 5, DataA is also stored in the distributed ledger 372-1 of the service server 3-1, and DataA is held in the distributed ledger 272 of the management server 2 and the distributed ledger 372-1 of the service server 3-1.
[0098] When the user information is synchronized to the distributed ledger 372-1, the main chain node 300A-1 of the service server 3-1 refers to the main chain (distributed ledger 371-1) to confirm the hash value (data hash) of the synchronized user information and the KYC result. Specifically, the main chain node 300A-1 queries the distributed ledger 371-1 for the hash value of the synchronized user information. The hash value of the user information may be generated by the main chain node 300A-1, or the data hash stored in the distributed ledger 372-1 may be used. Through the above query, the main chain node 300A-1 identifies the user ID to which the data hash is linked. Then, the main chain node 300A-1 can confirm that the user information synchronized to the distributed ledger 372-1 is permitted to be provided to the management server 2 and the service server 3-1 by referring to the consent information linked to the identified user ID. This allows the main chain node 300A-1 to recognize that the user information provided to itself is appropriate. In addition, the main chain node 300A-1 can confirm that the management server 2 (management company) has completed KYC for the user of the identified user ID by referring to the KYC result linked to the identified user ID.
[0099] When the main chain node 300A-1 confirms that KYC has been completed, the off-chain node 300C-1 completes the registration for use of the first service. This allows the user of the client device 4 to use the first application 51 to use the first service.
[0100] Although the above description has been given taking the example of the registration of the first application 51, the same applies to the registration of the second application 52 to the fourth application 54.
[0101] <<Mini app cancellation registration>> FIG. 8 is a diagram showing a schematic diagram of the flow of information in the process executed when registering withdrawal from first application 51. As shown in FIG.
[0102] 5 and 8, the user of the client device 4 applies for withdrawal from the first application (first service) through the wallet application 50. The withdrawal application includes a request (deletion request) to delete user information from the first application 51 (service server 3-1). The user of the client device 4 can apply for withdrawal by, for example, selecting a withdrawal button displayed on the display device 46 when using the first application 51. The withdrawal application is transmitted to the application providing server 5 via the communication device 44 of the client device 4.
[0103] The application providing server 5 decides to stop providing the first application 51 to the client device 4. Then, the application providing server 5 transmits a notification indicating the stop of provision to the management server 2.
[0104] When the management server 2 receives a notification indicating the suspension of provision, it updates the consent information of the main chain (distributed ledger 271). Specifically, when the off-chain node 200C receives a notification indicating the suspension of provision from the application providing server 5, it outputs the notification to the main chain node 200A. The main chain node 200A deletes the ID of the service server 3-1 from the information (To) indicating the consent destination included in the consent information, and generates transaction data including this consent information. That is, the information indicating the consent destination included in the updated consent information includes only the ID of the management server 2. The main chain node 200A broadcasts the generated transaction data to the network NW. The main chain node 200A and the main chain node 300A process this transaction data, thereby updating the consent information of the main chain (distributed ledger 271, 371).
[0105] When the sub-chain node 300B-1 of the service server 3-1 recognizes that the consent information has been updated and that it no longer has the authority to hold its own user information, it deletes the user information (Data A) from the distributed ledger 372-1. In addition, if the usage information associated with the user's use of the first service is stored in the distributed ledger 372-1, the sub-chain node 300B-1 also deletes the usage information.
[0106] When the off-chain node 200C receives a notification indicating the suspension of provision from the application providing server 5, the off-chain node 200C may notify the service server 3-1 of the notification via the communication device 24. In response to this, the service server 3-1 may accept the withdrawal registration.
[0107] <Flowchart> Fig. 9 is a flowchart showing the procedure of processing executed when the wallet application 50 is installed in the client device 4. The processing of the flowchart shown in Fig. 9 is started when the client device 4 accesses the application providing server 5. Note that, although each step (hereinafter, steps are abbreviated as "S") of the flowchart shown in Fig. 9 will be described as being realized by software processing by the control device 41 of the client device 4, the application providing server 5, and the control device 21 of the management server 2, a part or all of the steps may be realized by hardware (electronic circuits) created in the control device 41, the application providing server 5, and the control device 21.
[0108] In S10, a user operation for installing the wallet application 50 is performed on the client device 4. In response to the user operation, the control device 41 of the client device 4 installs the wallet application 50 from the application providing server 5.
[0109] In S12, the control device 41 of the client device 4 is requested to register an account by the wallet application 50 (application providing server 5). In response to the request for account registration, the control device 41 of the client device 4 generates a private key and a public key. Control device 41 may send the generated public key to a certification authority (not shown) to have it authenticated.
[0110] In S14, the control device 41 of the client device 4 is requested by the wallet application 50 to register user information. In response to the request to register user information, the control device 41 of the client device 4 displays an input field for user information on the display screen of the display device 46. When the user inputs information into the input field, the control device 41 of the client device 4 registers the input information as user information.
[0111] In S16, the control device 41 of the client device 4 transmits the user information and the public key information to the application providing server 5.
[0112] In S20, the application providing server 5 acquires user information and public key information from the client device 4.
[0113] In S22, in order to cooperate with the KYC service, the application providing server 5 transmits the user information acquired in S20 and a request for implementing KYC to the management server 2 that implements the KYC service. In addition, the application providing server 5 also transmits information on the public key of the client device 4 to the management server 2.
[0114] In S30, the control device 21 of the management server 2 implements the KYC service in response to the KYC implementation request. The implementation of the KYC service may involve the work of an administrator of the management server 2 or an employee of the company that operates the management server 2. If the control device 21 of the management server 2 determines that there is no problem with the identity verification as a result of implementing the KYC, it advances the process to S32.
[0115] In S32, the control device 21 of the management server 2 generates transaction data for updating the sub-chain. The control device 21 of the management server 2 includes user information and a data hash in the transaction data. The control device 21 of the management server 2 also specifies itself (sub-chain node 200B) as the destination of the transaction data. The control device 21 of the management server 2 processes the transaction data, stores the user information and the data hash in the distributed ledger 272, and updates the sub-chain.
[0116] In S34 and S36, the control device 21 of the management server 2 generates transaction data for updating the main chain. The control device 21 of the management server 2 includes in the transaction data the data hash, the consent information, and information indicating the KYC confirmation result. In addition, the control device 21 of the management server 2 specifies all nodes forming the main chain (the main chain node 200A and the main chain nodes 300A-1 to 300A-4) as the destination of the transaction data. In addition, the control device 21 of the management server 2 includes in the transaction data the hash value of the public key of the client device 4 as information indicating the owner of the transaction data. This transaction data is broadcast to the network NW and processed by the main chain node 200A of the management server 2 and the main chain node 300A of the service server 3, whereby the user ID is issued on the main chain, and the data hash, the consent information, and information indicating the KYC confirmation result are stored in the main chain (the distributed ledger 271 and the distributed ledger 371) in a format linked to the user ID.
[0117] Fig. 10 is a flowchart showing the procedure of processing executed when registration for use of first application 51 is performed. The processing of the flowchart shown in Fig. 10 is started by a user operation for starting up first application 51 in wallet application 50 for the first time. Note that, although each step of the flowchart shown in Fig. 10 and Fig. 11 described later will be described as being realized by software processing by control device 41 of client device 4, application providing server 5, control device 21 of management server 2, and control device 31-1 of service server 3-1, a part or all of the steps may be realized by hardware (electronic circuitry) created in control device 41, application providing server 5, control device 21, and control device 31-1.
[0118] In S40, the control device 41 of the client device 4 launches the first application 51 in the wallet application 50 for the first time in response to a user operation.
[0119] In S50, the application providing server 5 (wallet application 50) returns an instruction to the client device 4 to display a confirmation screen requesting consent to providing user information to the service server 3-1 that provides the first application 51 (first service). The user information here is user information (e.g., DataA in the example of FIG. 5) that was provided to the management server 2 when the wallet application 50 was installed.
[0120] In S42, the control device 41 of the client device 4 displays a confirmation screen in accordance with an instruction from the application providing server 5 (wallet application 50).
[0121] In S44, the user of the client device 4 performs an agreement operation on the confirmation screen to indicate agreement. The control device 41 of the client device 4 transmits information indicating agreement to the application providing server 5.
[0122] In S52, upon confirming that the information indicating consent has been acquired, the application providing server 5 transmits the information indicating consent to the management server 2.
[0123] In S60, when the control device 21 of the management server 2 receives the information indicating consent, it updates the consent information of the main chain. Specifically, the control device 21 of the management server 2 (main chain node 200A) generates transaction data including consent information in which the ID of the service server 3-1 is added to the information indicating the consent destination. The control device 21 of the management server 2 broadcasts the generated transaction data to the network NW.
[0124] In S70, the control device 31-1 (main chain node 300A-1) of the service server 3-1 processes the transaction data acquired from the management server 2. This updates the distributed ledger 371-1. Similarly, the transaction data sent in S60 is processed by the service servers 3-2 to 3-4 (main chain nodes 300A-2 to 300A-4), thereby updating the distributed ledgers 371-2 to 371-4. This updates the consent information stored in the main chain. The updated consent information indicates that the user of the client device 4 has agreed to provide user information to the management server 2 (management company) and the service server 3-1 (company A).
[0125] In S62, the control device 21 of the management server 2 recognizes that the service server 3-1 has gained the authority to obtain user information due to the update of the consent information of the main chain (distributed ledger 271). The control device 21 (sub-chain node 200B) of the management server 2 generates transaction data that stores the user information and data hash. The control device 21 (sub-chain node 200B) of the management server 2 specifies the sub-chain node 300B-1 of the service server 3-1 as the destination of this transaction data. The control device 21 (sub-chain node 200B) of the management server 2 also transmits data including the hash value of the transaction data and an index of the output of the transaction data to the notary node 65.
[0126] In S72, the control device 31-1 (sub-chain node 300B-1) of the service server 3-1 processes the transaction data received from the management server 2 and stores the user information in the distributed ledger 372-1. As a result, the user information is synchronized and the sub-chain is updated.
[0127] In S74, when the user information is synchronized with the distributed ledger 372-1, the control device 31-1 (main chain node 300A-1) of the service server 3-1 refers to the main chain (distributed ledger 371-1) to confirm the hash value (data hash) of the synchronized user information and the KYC result. Specifically, the control device 31-1 of the service server 3-1 queries the distributed ledger 371-1 for the hash value of the synchronized user information. Through the query, the control device 31-1 of the service server 3-1 identifies the user ID to which the data hash is linked. Then, the control device 31-1 of the service server 3-1 can confirm that the user information synchronized with the distributed ledger 372-1 is permitted to be provided to the management server 2 and the service server 3-1 by referring to the consent information linked to the identified user ID. This allows the control device 31-1 of the service server 3-1 to recognize that the user information provided to itself is appropriate. In addition, the control device 31-1 of the service server 3-1 can confirm that the management server 2 (management company) has completed KYC for the user of the identified user ID by referring to the KYC result linked to the identified user ID.
[0128] When the control device 31-1 of the service server 3-1 confirms that KYC has been completed, it completes the registration for use of the first service.
[0129] 11 is a flowchart showing a procedure of a process executed when registering for withdrawal from the first application 51 (first service). The process of the flowchart shown in FIG. 11 is started by a user operation for requesting withdrawal from the first application 51.
[0130] In S80, the control device 41 of the client device 4 transmits an application for withdrawal registration of the first application 51 (first service) to the application providing server 5 in response to a user operation.
[0131] In S90, when the application providing server 5 receives the application for withdrawal registration from the client device 4, the application providing server 5 accepts the application for withdrawal registration.
[0132] In S92, the application providing server 5 decides to stop providing the first application 51 to the client device 4. Then, the application providing server 5 transmits a notification indicating the stop of provision to the management server 2.
[0133] In S100, when the control device 21 (main chain node 200A) of the management server 2 receives a notification indicating the suspension of service, it updates the consent information of the main chain (distributed ledger 271). Specifically, the control device 21 of the management server 2 deletes the ID of the service server 3-1 from the information indicating the consent destination (To) included in the consent information, generates transaction data including this consent information, and broadcasts it to the network NW.
[0134] In S110, the control device 31-1 (main chain node 300A-1) of the service server 3-1 processes the transaction data acquired from the management server 2. This updates the distributed ledger 371-1. Similarly, the transaction data sent in S110 is processed by the service servers 3-2 to 3-4 (main chain nodes 300A-2 to 300A-4), thereby updating the distributed ledgers 371-2 to 371-4. This updates the consent information stored in the main chain. The updated consent information indicates that the user of the client device 4 has authorized only the management server 2 (management company) to provide user information.
[0135] In S112, when the control device 31-1 (sub-chain node 300B-1) of the service server 3-1 recognizes that the consent information has been updated and that it no longer has the authority to hold its own user information, it deletes the user information from the distributed ledger 372-1. In addition, if usage information associated with the user's use of the first service is stored in the distributed ledger 372-1, the control device 31-1 of the service server 3-1 also deletes that usage information.
[0136] In S114, the control device 31-1 of the service server 3-1 completes the withdrawal registration of the user.
[0137] In addition, in S102, the control device 21 of the management server 2 may notify the service server 3-1 that a notification indicating suspension of provision has been received from the application providing server 5. In response to this, the control device 31-1 of the service server 3-1 may accept a withdrawal registration.
[0138] As described above, in the data sharing system 1 according to the present embodiment, when the wallet application 50 is installed in the client device 4, the management server 2 (management company) implements the KYC service. Information indicating the KYC result is stored in the main chain in which data is shared by all main chain nodes participating in the network NW. As a result, the information indicating the KYC result is monitored by all main chain nodes participating in the network NW, improving tamper resistance.
[0139] Furthermore, when registration for use of a mini app (for example, first app 51) of wallet app 50 is made, the service server 3 (company) providing the mini app refers to the main chain and confirms the KYC result performed by management server 2 without performing KYC on the user. With this confirmation process, the service server 3 (company) completes KYC. In this way, by referring to the KYC result by management server 2, it is possible to omit the implementation of KYC.
[0140] The service server 3 (company) that receives the application for use of the mini app needs to obtain user information in order to provide the service. In the data sharing system 1 according to the present embodiment, the user information is synchronized to the service server 3 that has obtained the authority to obtain the user information from the management server 2 using a P2P type subchain based on the user's consent. By managing the consent information in a broadcast type main chain, the consent information is monitored by the entire main chain, so that the tamper resistance of the consent information can be improved. Then, based on the consent information shared in the main chain, the P2P type subchain can enable data synchronization only between specific subchain nodes. In this way, by combining the broadcast type main chain with the P2P type subchain, it is possible to increase the tamper resistance of the consent information while enabling data synchronization only between specific subchain nodes based on the consent information.
[0141] Furthermore, by combining a broadcast-type main chain with a P2P-type sub-chain, it is possible to increase the tamper-resistance of consent information while making it possible to delete only data that has been synchronized to a specific sub-chain node based on the consent information shared on the main chain.
[0142] [Variation 1] In the embodiment, for example, as shown in Figure 6, at the timing when KYC results etc. are stored in the main chain, M A user ID is issued to the in-chain. However, the timing of when the user ID is issued to the main chain may be different.
[0143] FIG. 12 is a diagram showing a schematic flow of information in the process executed when the wallet application 50 is installed in the client device 4 in the modified example.
[0144] 12, when the wallet application 50 is installed in the client device 4, the wallet application 50 (application providing server 5) requests the client device 4 to register an account, similarly to the embodiment. In response to the request for account registration, the control device 41 of the client device 4 generates a private key and a public key. The control device 21 may transmit the generated public key to a certification authority (not shown) for authentication. The control device 41 stores the private key corresponding to the authenticated public key in the storage device 47.
[0145] The control device 41 of the client device 4 transmits the authenticated public key and a hash value of the public key to the application providing server 5.
[0146] The application providing server 5 registers the user's ID using the public key and a hash value of the public key as the ID.
[0147] When the application providing server 5 completes the user ID registration, the application providing server 5 transmits the hash value of the public key and an ID issuance request to the management server 2.
[0148] When the management server 2 receives the hash value of the public key and the ID issuance request, it issues a user ID to the main chain using the hash value as the ID. Specifically, when the management server 2 receives the hash value of the public key and the ID issuance request from the application providing server 5, the off-chain node 200C functions and outputs the hash value of the public key to the main chain node 200A.
[0149] The main chain node 200A generates transaction data for issuing a user ID and broadcasts the generated transaction data to the network NW. By processing this transaction data, a user ID is issued to the main chain.
[0150] The processing after the registration of the user information is the same as in the embodiment. After the KYC service is implemented, when the user information is stored in the sub-chain (distributed ledger 272), the main chain node 200A generates transaction data including a data hash, consent information, and information indicating the KYC confirmation result. In this transaction data, a user ID is specified as information indicating the owner. By processing this transaction data, the data hash, consent information, and information indicating the KYC confirmation result are stored in the main chain (distributed ledger 271 and distributed ledger 371) in a format linked to the user ID.
[0151] Even if a configuration is adopted in which a user ID is issued to the main chain at the timing described above, the same effects as those of the embodiment can be achieved.
[0152] [Variation 2] In the embodiment and the first modification, an example has been described in which the first application 51 to the fourth application 54 are provided as mini applications of the wallet application 50. However, the first application 51 to the fourth application 54 may be provided to the application providing server 5 as standalone applications rather than as mini applications. Furthermore, in this case, companies A to D (service servers 3-1 to 3-4) may each provide a server equivalent to the application providing server 5 for providing the first application 51 to the fourth application 54.
[0153] Even with the above configuration, when each application (first application 51 to fourth application 54) is installed in the client device 4, each service server 3 (service servers 3-1 to 3-4) can omit implementation of KYC by referring to the KYC result by the management server 2 stored in the main chain based on the user ID. By sharing the public key used by the client device 4 to register accounts for the wallet application 50 and the first application 51 to the fourth application 54, the user ID (hash value of the public key) issued to the main chain is shared, so that it becomes possible to refer to the KYC result based on the user ID. Therefore, even with the above configuration, it is possible to achieve the same effects as those of the embodiment.
[0154] [Variation 3] In the embodiment and the first and second modifications, the management server 2 has a function of managing the network NW and a function of implementing the KYC service. However, the function of managing the network NW and the function of implementing the KYC service may be provided in different servers. In this case, the wallet application 50 is provided by a service server that provides the KYC service.
[0155] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]
[0156] 1 Data sharing system, 2 Management server, 3 Service server, 4 Client device, 5 Application providing server, 21 Control device, 22 ROM, 23 RAM, 24 Communication device, 25 Input device, 26 Display device, 27 Storage device, 29 Bus, 31 Control device, 32 ROM, 33 RAM, 34 Communication device, 35 Input device, 36 Display device, 37 Storage device, 39 Bus, 41 Control device, 42 ROM, 43 RAM, 44 Communication device, 45 Input device, 46 Display device, 47 Storage device, 49 Bus, 50 Wallet application, 51 First application, 52 Second application, 53 Third application, 54 Fourth application, 60 Platform provider, 61 Doorman node, 63 Network map node, 65 Notary node, 200 Node, 200A Main chain node, 200B Sub-chain node, 200C Off-chain node, 270 distributed ledger set, 271,272 distributed ledger, 275 private key, 277 multiple public keys, 300 nodes, 300A main chain node, 300B sub-chain node, 300C off-chain node, 370 distributed ledger set, 371,372 distributed ledger, 375 private key, 377 multiple public keys, NW network.
Claims
1. A server device for use in a data sharing system using distributed ledger technology, comprising: the data sharing system includes a plurality of other server devices; The server device includes: a storage device that stores the first distributed ledger and the second distributed ledger; a control device that updates the first distributed ledger and the second distributed ledger; The first distributed ledger is configured to share authority information regarding data sharing with the plurality of other server devices; the authority information includes information for limiting other server devices with which the data is shared among the plurality of other server devices, The second distributed ledger is configured to share the data with the other server device based on the authority information; The control device transmits the data stored in the second distributed ledger to the other server device based on the authority information; and the server device provides a first application for providing a predetermined service; the first application is installed on a terminal device of a user; the terminal device provides the server device with user information regarding the user, the user information having been input at the time of installation of the first application; When the control device acquires the user information, the control device sets the server device as the authority information for the user information and stores the authority information in the first distributed ledger; the first application includes a second application; the second application is an application provided by a predetermined server device among the plurality of other server devices, When the user registration for the second application is performed, the first application requests the terminal device to consent to sharing the user information with the second application; If the consent is obtained, the control device adds the specified server device to the authority information.
2. The server device according to claim 1 , wherein when the authority information is updated, the control device stores the updated authority information in the first distributed ledger.
3. The predetermined service includes an identity verification service, The user information includes personal information of the user, When the control device acquires the user information, performing the identity verification service on the user information; The server device according to claim 1 or 2, further comprising: storing the user information, which has been authenticated, in the second distributed ledger.
4. The server device according to claim 3 , wherein the control device stores information indicating a result of implementation of the identity verification service in the first distributed ledger.
5. 5. The server device according to claim 1, wherein the control device shares the user information stored in the second distributed ledger with the specified server device based on the authority information to which the specified server device has been added.
6. The server device according to claim 1 , wherein when an application for withdrawal registration of the second application is made, the control device deletes the predetermined server device from the authority information.
7. A server device for use in a data sharing system using distributed ledger technology, comprising: the data sharing system includes a plurality of other server devices; The server device includes: a storage device that stores the first distributed ledger and the second distributed ledger; a control device that updates the first distributed ledger and the second distributed ledger; The first distributed ledger is configured to share authority information regarding data sharing with the plurality of other server devices; the authority information includes information for limiting other server devices with which the data is shared among the plurality of other server devices, The second distributed ledger is configured to share the data with the other server device based on the authority information; When the server device is added to the authority information, the control device acquires the data from the other server device having the data and stores the data in the second distributed ledger; the server device provides a second application included in a first application provided by a predetermined server device that is any one of the plurality of other server devices, the first application is an application that provides an identity verification service; The first distributed ledger stores information indicating a result of implementation of the identity verification service by the predetermined server device, The control device, when registration for use of the second application is made, omits the implementation of identity verification by referring to information indicating a result of implementation of the identity verification service.
8. The server device according to claim 7 , wherein the control device deletes the data from the second distributed ledger when the server device is deleted from the authority information.
Citation Information
Patent Citations
Article information management apparatus, system, method and program
JP2018173692A
Individual identification assisting device and individual identification assisting method
JP2020064483A
Document Management System
JP6587370B1
