Information processing system, information processing method, and program
The information processing system addresses the challenge of reliably recording transaction records in data exchanges by using smart contracts and channel separation in distributed ledger technology, ensuring seamless and cost-effective transaction recording.
Patent Information
- Application Number
- JP2023079572
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2043-05-12
AI Technical Summary
Existing data exchange systems face challenges in reliably recording transaction records inseparably from data exchange between data providers and consumers while minimizing effort and cost, leading to potential discrepancies and unfair profits.
An information processing system that mediates data transactions using encrypted data, ensuring the encryption key is made available to the data consumer and recording the transaction as completed, utilizing distributed ledger technology with smart contracts to perform these processes inseparably, thereby preventing discrepancies and reducing intermediary costs.
Ensures reliable and efficient recording of transaction records with minimal effort, preventing discrepancies between data exchange and transaction records, and reducing intermediary costs through the use of smart contracts and channel separation in distributed ledger technology.
Smart Images

Figure 2024163723000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information processing system, an information processing method, and a program. [Background technology]
[0002] In data transactions, it is important not only to transfer the data itself, but also to keep records of transactions for incentive settlement and evidence purposes.
[0003] Patent Document 1 discloses a method for exchanging entities between users, and generates an invitation (Tx) including an output (UTXO) associated with an encrypted, electronically transferable digital asset and a hash of a script, where the script includes an indication of the entities to be exchanged, the conditions for the exchange, and a public key associated with the user. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2021-177666 [Patent Document 2] JP 2021-127246 A Summary of the Invention [Problem to be solved by the invention]
[0005] One aspect of the present disclosure aims to provide a technology that enables a transaction record in a data exchange between a data provider and a data consumer to be recorded inseparably from the data exchange with minimal effort. [Means for solving the problem]
[0006] One aspect of the present disclosure is an information processing system that mediates data transactions between a data provider and a data consumer, and includes a control unit that inseparably performs the following operations: making available to the data consumer an encryption key for encrypted data that encrypts data exchanged between the data provider and the data consumer, or having the data consumer actually obtain the encryption key; and recording the completion of the transaction between the data provider and the data consumer.
[0007] Another aspect of the present disclosure is an information processing method performed by an information processing system that mediates data transactions between a data provider and a data consumer, characterized in that the information processing method includes inseparably executing the steps of making available to the data consumer an encryption key for encrypted data that encrypts data exchanged between the data provider and the data consumer, or the data consumer actually obtaining the encryption key, and recording the completion of the transaction between the data provider and the data consumer. Effect of the Invention
[0008] According to an aspect of the present disclosure, transaction records in data exchange between a data provider and a data consumer can be recorded reliably and with minimal effort. [Brief description of the drawings]
[0009] [Figure 1] 1 is a diagram showing a schematic configuration of a data exchange system according to an embodiment; [Diagram 2] FIG. 1 is a diagram illustrating a configuration of an information processing device according to an embodiment. [Diagram 3] FIG. 1 is a diagram illustrating an overview of a data exchange process according to an embodiment. [Figure 4A] FIG. 11 is a sequence diagram illustrating a data exchange process according to an embodiment. [Figure 4B] FIG. 11 is a sequence diagram illustrating a data exchange process according to an embodiment. [Figure 4C] FIG. 11 is a sequence diagram illustrating a data exchange process according to an embodiment. [Diagram 5] FIG. 13 is a state transition diagram of a data request ticket in one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] (overview) Consider data exchange (data trading) with incentives between different entities. In this disclosure, the entity that transmits data is called a data provider, The entity that receives the data and uses it to provide services is called a Data Consumer. The data provider and data consumer are also referred to as DP and DC, respectively. These terms refer to the subject itself as well as the information processing device or information processing system that the subject manages.
[0011] In data transactions, it is important not only to transfer the data itself, but also to keep records of transactions for incentive settlement and evidence.
[0012] It can be said that the interests of DP and DC are in conflict. DP wants to receive incentives while keeping costs down, while DC wants to obtain data without paying incentives. Therefore, it is necessary to prevent discrepancies between the actual data transfer and the transaction records, and to prevent unfair profits by DP or DC. On the other hand, it is also necessary to avoid the huge effort and cost involved in mediating to prevent unfair profits.
[0013] Therefore, one embodiment of the present disclosure provides a technology that enables reliable recording of transaction records in data exchange between a DP and a DC so as not to cause any deviation from the actual data transaction, and enables recording with little effort.
[0014] One embodiment of the present disclosure is an information processing system that mediates data transactions between a data provider (DP) and a data consumer (DC). The DP is a device that provides data to the DC, and the DC is a device that obtains and uses data from the DP.
[0015] In one embodiment of the present disclosure, the information processing system includes a control unit that inseparably performs the following operations: making available to the DC an encryption key for encrypted data obtained by encrypting data exchanged between the DP and DC, or actually obtaining this encryption key by the DC; and recording a transaction record between the DC and the DP as a completed transaction.
[0016] In the present disclosure, "making data available to the DC" and "actually acquiring data by the DC" are collectively expressed as "provision of data to the DC." For example, in the present disclosure, a process in which an information processing system provides an encryption key to a DC includes at least one of a process of making the encryption key available to the DC and a process of actually transmitting the encryption key to the DC. Therefore, one embodiment of the present disclosure can also be expressed as inseparably executing the provision of the encryption key to the DC and the recording of the transaction between the DC and the DP as transaction completion.
[0017] "Atomic execution" of multiple processes means that when any one of the processes is executed, the remaining processes are also executed, or in other words, the multiple processes are controlled so that either all of them are executed or none of them are executed. Processes and operations executed atomically are also called "transaction processing", "atomic operations", "atomic operations", etc.
[0018] In one embodiment of the present disclosure, the exchange of encryption keys between the DP and the DC and the recording of the transaction record may be performed using distributed ledger technology (blockchain technology). When the distributed ledger technology is adopted, the information processing system in the present disclosure is one or more information processing devices constituting at least a part of the distributed ledger infrastructure. An example of an information processing device constituting a part of the distributed ledger infrastructure is a peer node. In this embodiment, the inseparable execution of making the encryption key available or actually acquiring it and the recording of the transaction completion may be performed using a smart contract function of the distributed ledger technology. A "smart contract" is a function that automatically executes a process that is determined to read and write records on the distributed ledger. In this embodiment, the control unit records the completion of the transaction in the transaction record on the condition that the encryption key is provided to the DC. By using the smart contract function, the inseparability of these two processes can be guaranteed.
[0019] If making the encryption key available to the DC and recording the transaction as completed are executed inseparably, the completion of the transaction can be recorded by using a smart contract function when writing the encryption key (to an area that the DC can read and access). The use of distributed ledger technology, which requires data to be written via a smart contract, is one example of a method for achieving the above-mentioned inseparable processing.
[0020] As an example, in response to receiving the encryption key from the DP, the control unit inseparably records the encryption key in the distributed ledger and records the completion of the transaction using a smart contract function. The distributed ledger is a data space that is readable and accessible by any participating node, and is an example of a data space that is readable and accessible by the DC. Another example of a data space that is readable and accessible by the DC is a data space that is readable and accessible only by the DC. A specific example of such a data space is the Private Data Collection. The encryption key is readable and accessible by the DC in the distributed ledger infrastructure. By using a smart contract function that also records the completion of the transaction when recording in space, it is possible for the DC to inseparably make the encryption key available to the DC and record the completion of the transaction between the DC and the DP.
[0021] In order to inseparably record that the DC actually obtained the encryption key and that the transaction was completed, it is desirable for the DC to use a smart contract function when obtaining the encryption key. In distributed ledger technology, one method of making it mandatory to go through a smart contract when obtaining data is to store the data in a data space (private space, for example, Private Data Collection in Hyperledger Fabric) that is accessible only to authorized individuals. Therefore, by placing the encryption key in the private space of the DC, when the DC obtains the encryption key, the smart contract function can inseparably execute the acquisition of the encryption key and the recording of the completion of the transaction.
[0022] As an example, in response to receiving the encryption key from the DP, the control unit records the encryption key in a data space of the distributed ledger infrastructure that can be read and accessed only by the DC, and in response to receiving a request to obtain the encryption key from the DC, the control unit inseparably executes the transmission of the encryption key to the DC and the recording of the completion of the transaction using a smart contract function. In distributed ledger technology, reading of data from a data space (private space) that can be accessed only by the DC can be made mandatory via a smart contract function. Therefore, by using a smart contract function that also records the completion of the transaction when accepting a request to obtain the encryption key from the DC and transmitting the encryption key to the DC, it is possible to inseparably execute making the encryption key available to the DC and recording the completion of the transaction between the DC and the DP.
[0023] As mentioned above, providing the encryption key to the DC and completing the transaction record are performed inseparably, which may cause a discrepancy between the data transaction (data transfer) and the transaction record. This can prevent the DC from acquiring data but denying the transaction and refusing to pay the incentive, or the DP from claiming the transaction has been completed and receiving the incentive without providing the data. Another advantage of the present disclosure is that the intermediary system requires fewer processes and can mediate data exchange at low cost.
[0024] In this embodiment, a channel for exchanging data itself may be separated from a channel for performing processes associated with data exchange, such as encryption keys and transaction records. The separation of channels may be logical or physical. Channels are also called planes (control plane and data plane). Note that "channel" here refers to a logical or physical communication path, and is different from the concept of a channel used in a distributed ledger platform.
[0025] As an example of channel separation, processing related to encryption key exchange and transaction recording may be performed via a distributed ledger infrastructure, and the encrypted data itself may be provided from the DP to the DC without going through the distributed ledger infrastructure. This is because a distributed ledger is not suitable for recording large-sized data. Exchanges using a distributed ledger are targeted at encryption keys, which have a small data size, and the data itself is exchanged using a separate route, making it possible to execute efficient processing. In addition, encrypting and exchanging the data itself has the effect of protecting the secrecy of the plaintext, since the contents of the plaintext cannot be known even if the encrypted data itself is leaked to a third party.
[0026] Such separation of channels is expected to facilitate implementation and to provide efficient processing even when using distributed ledger technology. In another embodiment of the present disclosure, encrypted data may also be provided from the DP to the DC using a distributed ledger.
[0027] In one embodiment of the present disclosure, an information processing system that mediates data transactions between a DP and a DC includes peer nodes that constitute a distributed ledger network, and the peer nodes have the function of executing the above-mentioned smart contract.
[0028] In one embodiment of the present disclosure, the transaction record may be permitted to be updated from a transaction completion state to a transaction cancellation state for a predetermined period after the encryption key is provided to the DC, and the transaction record may not be updated from the transaction completion state after the predetermined period has elapsed. Since the transaction can be cancelled even if it is recorded as completed within the predetermined period, the state within the predetermined period and the state after the period may be distinguished as "transaction provisional completion" and "transaction completion" in the narrow sense, or "transaction completion (cancellable)" and "transaction completion (confirmed)", respectively. The transaction may be cancelled within the predetermined period in response to the distributed ledger infrastructure detecting an inconsistency in the data transaction, or in response to receiving a transaction cancellation request from the DC. When canceling a transaction in response to a request from the DC, it is preferable to receive the reason for the transaction cancellation from the DC, and the control unit or other functional unit of the information processing system may verify whether the reason for cancellation is appropriate after the transaction cancellation and evaluate the reliability of the DC and DP, or may cancel the transaction after evaluating whether the reason for cancellation is appropriate.
[0029] If the transaction is considered complete with the provision of the encryption key, problems may occur, such as the encrypted data not being decrypted with the provided encryption key, or the data being decrypted but having no value (for example, different from what the DC is requesting). In such cases, it is desirable to be able to cancel the transaction, and it is advantageous for appropriate data exchange to be able to cancel the transaction within a specified period from the provision of the encryption key by the above-mentioned process.
[0030] In one embodiment of the present disclosure, the control unit of the information processing system may obtain a hash value of the encrypted data from the DP, and provide the encryption key to the DC when the hash value of the encrypted data calculated by the DC itself matches the hash value calculated by the DP. Here, "providing the encryption key to the DC" refers to the information processing system directly transmitting the encryption key to the DC, and the information processing system This may be done by the DC requesting another device to send the encryption key to the DC, by the information processing system recording the encryption key in storage (e.g., a distributed ledger) that can be read and accessed by the DC, etc.
[0031] Furthermore, the match between the DP provided hash value and the DC calculated hash value may be confirmed by the information processing system, or the DC may confirm and notify the information processing system. When the DC notifies the information processing system, the format may be, for example, an encryption key acquisition request that is sent to the information processing system on the premise that the DC has confirmed the match. When the information processing system confirms, for example, the information processing system may receive the DC calculated hash value from the DC in the format of an encryption key authenticity confirmation request or the like, and compare it with the DP provided hash value.
[0032] Furthermore, it is desirable for the information processing system to update the transaction record to a transaction aborted state or other error state when the DP-provided hash value and the DC-calculated hash value do not match. Specifically, the information processing system may update the transaction record to a transaction aborted state in any of the following cases: when the information processing system receives a report of mismatch from the DC within a predetermined period of time, when the information processing system does not receive a report of match from the DC within a predetermined period of time, or when the information processing system receives a DC-calculated hash value from the DC within a predetermined period of time and confirms a mismatch with the DP-provided hash value.
[0033] In this way, when the DP-provided hash value of the encrypted data does not match the DC-calculated hash value, it is assumed that there is some defect in the encrypted data sent from the DP to the DC, for example, that the data cannot be decrypted using the provided encryption key. Therefore, in such a case, being able to cancel the transaction without providing the encryption key to the DC is advantageous for the DC in that it is possible to avoid the transaction being concluded even when data cannot be exchanged. In addition to the above viewpoint, it is also advantageous from the viewpoint of the processing efficiency of the entire system, since the transaction can be canceled before performing processes such as recording the encryption key in the distributed ledger by the information processing system and obtaining and decrypting the encryption key by the DC, rather than finding out that the data cannot be decrypted after actually performing these processes.
[0034] In one embodiment of the present disclosure, a control unit of the information processing system may obtain a hash value of plaintext data corresponding to the encrypted data from the DP, and if the hash value calculated from the plaintext data obtained by the DC decrypting the encrypted data using the encryption key does not match the hash value obtained by the DC from the information processing system, update the transaction record to a transaction aborted state or other error state.
[0035] The confirmation of whether the hash value provided by the DP and the hash value calculated by the DC match may be performed by the information processing system, or the DC may confirm and notify the information processing system. When notifying the information processing system from the DC, the DC may notify the information processing system regardless of whether they match or not, or the DC may notify the information processing system only if they match or only if they do not match. When the information processing system confirms, the confirmation of whether the hash values match or not may be performed by the information processing system receiving the hash value calculated by the DC from the DC in the form of a plaintext authenticity confirmation request or the like and comparing it with the hash value provided by the DP.
[0036] In this way, if the hash value of the plaintext data provided by the DP does not match the hash value calculated by the DC, it is assumed that there is some defect in the encrypted data sent from the DP to the DC or the plaintext data on which it is based. In such a case, being able to cancel a transaction that is assumed to have a defect is advantageous for the DC in that it can avoid a transaction being concluded even if the appropriate data exchange has not been performed.
[0037] In one embodiment of the present disclosure, the control unit of the information processing system may obtain a hash value of the encryption key from the DP, and if the hash value calculated by the DC based on the obtained encryption key does not match the hash value obtained by the DC from the information processing system, update the transaction record to a transaction aborted state or other error state.
[0038] In this case, as in the case of comparing hash values of plaintext data, being able to cancel a transaction that is suspected to be defective is advantageous for the DC in that it can avoid a transaction being completed despite the lack of proper data exchange.
[0039] In one embodiment of the present disclosure, the above-mentioned comparison of hash values of encrypted data, comparison of hash values of encryption keys, and comparison of hash values of plaintext may all be performed, only some of them may be performed, or none of them may be performed. When performing multiple comparisons, it is possible to perform the comparisons in the order of the comparison of hash values of the draft data, the comparison of hash values of the encryption keys, and the comparison of hash values of plaintext data. This is because it is possible to minimize the amount of processing that is wasted when a transaction is canceled. Of course, the order of the processing is not limited to this, and may be performed in any order.
[0040] In one aspect of the present disclosure, it is desirable for the information processing system to provide the encryption key to the DC in such a way that the encryption key is not leaked to a third party. Even if the encryption key itself is leaked, the security of the data is maintained if the corresponding encrypted data is unknown, but it is more desirable to prevent the encryption key itself from being leaked. As a form of provision that prevents the encryption key from being leaked to a third party, there is a method of placing the encryption key in a data space that cannot be read and accessed by anyone other than the DC (or a data space that can be read and accessed only by the DC), and a method of encrypting the encryption key using a common key (symmetric key) or a public key (asymmetric key). An example of a data space on a distributed ledger that cannot be read and accessed by anyone other than the DC is Private Data Collection (PDC) in Hyperledger Fabric. For example, when an information processing system obtains an encryption key from a DP, it first places the encryption key in the private space of the DP, and then when the conditions are met, moves the encryption key from the PDC of the DP to the private space of the DC, thereby making it possible to transfer the encryption key while protecting its secrecy.
[0041] (System Configuration) 1 is a diagram showing the configuration of a data exchange system according to an embodiment. The data exchange system has a configuration in which a distributed ledger infrastructure 100, a data consumer (DC) 200, and a data provider (DP) 300 are connected to each other so that they can communicate with each other.
[0042] The DC 200 is a computer managed by an entity that uses data provided by the DP 300 and provides services to end users, for example.
[0043] The DP 300 is a computer managed by an entity that provides the data it holds to the DC 200 .
[0044] The distributed ledger infrastructure 100 is composed of multiple peer nodes 110 and provides distributed ledger technology. In addition to transaction records, the distributed ledger infrastructure 100 also records encryption keys for decrypting encrypted data exchanged between the DC200 and the DP300 and various hash values for verifying the authenticity of the data. In this embodiment, the encrypted data itself exchanged between the DC200 and the DP300 is exchanged between the DC200 and the DP300 without using the distributed ledger infrastructure 100.
[0045] The distributed ledger infrastructure 100 in this embodiment is a consortium type in which the management entities of the DC 200 and the DP 300 participate as administrators, and the peer node 110 is a It is an information processing device managed by the management entity of P300. The consortium-type distributed ledger infrastructure is constructed using, for example, the Hyperledger Fabric framework. A server-side program of the Hyperledger Fabric infrastructure is installed in the peer node 110, and the distributed ledger infrastructure is constructed. In addition, a smart contract function (chain code) is deployed in the peer node 110.
[0046] In addition, the distributed ledger infrastructure 100 has a data space that participants can freely access and a data space with limited access rights. In this embodiment, a data space that only the DP 300 can read and write, and a data space that the DP 300 can write and that the DC 200 can read are used.
[0047] In another embodiment, the distributed ledger infrastructure 100 may be a private type in which only limited participants such as an administrator can participate, or a public type in which anyone can participate without the administrator.
[0048] In this embodiment, the DC 200 and the peer node 110, or the DP 300 and the peer node 110 may be the same device. That is, one information processing device may include both the functions of the DC 200 or the DP 300 described below and the function as the peer node 110.
[0049] Each of the peer node 110, the DC 200, and the DP 300 is configured with one or more information processing devices (computers). As shown in Fig. 2, the information processing device 20 includes a processor 21, a main storage device 22, an auxiliary storage device 23, an input / output device 24, and a communication device 25. The processor 21 executes a program loaded in the main storage device 22 to realize functions described below.
[0050] In this embodiment, the distributed ledger infrastructure 100 corresponds to an information processing system that mediates data transactions between the DC 200 and the DP 300. Moreover, the processor 21 of the peer node 110 corresponds to the control unit in the present invention.
[0051] (Processing Overview) 3 is a diagram for explaining an outline of the data transaction method in this embodiment. As shown in FIG. 3, in this embodiment, a data plane in which the data itself provided from the DP 300 to the DC 200 is transmitted is separated from a control plane in which data related to the mediation of transactions is exchanged. The difference between the data plane and the control plane may be logical, or may be physically or substantially different. In this embodiment, the control plane passes through the distributed ledger infrastructure 100, and the data plane does not pass through the distributed ledger infrastructure 100.
[0052] The data transaction process will be roughly explained based on Fig. 3. Note that Fig. 3 is merely for explaining the overview, and the details of the process will be explained later with reference to Figs. 4A to 4C.
[0053] First, the DC200 creates a transaction record in the distributed ledger infrastructure 100 to record the contents and status of a transaction or to enable reference to the contents and status of a transaction (1). The DP300 references the created transaction record (2) and prepares the data (plaintext data) requested by the DC200. The DP300 encrypts the plaintext data to be sent to the DC200, records the hash value of this plaintext data and the encrypted data in the distributed ledger infrastructure 100 (3), and also transmits the encrypted data to the DC200 on the data plane (4). The DC200 calculates the hash value of the encrypted data received from the DP300, and checks whether it matches the encrypted data hash value calculated by the DP300, and confirms whether there is any inconsistency in the encrypted data sent from the DP300 (5). Note that in this embodiment, the match check of the hash value itself is performed by the distributed ledger infrastructure 100. The encrypted data hash On the condition that the hash values match, the encryption key provided by the DP300 is recorded in the distributed ledger (6-1) and the transaction record is updated to a completed state (6-2) inseparably executed. Here, the encryption key is placed in a private space on the distributed ledger that is readable and writable only by the DC200. The DC200 obtains the encryption key and decrypts the encrypted data to obtain plaintext data (7). The DC200 also checks whether the hash value of the plaintext data obtained by decrypting the encrypted data received from the DP300 matches the plaintext data hash value calculated by the DP300, and confirms whether there is any inconsistency in the data sent from the DP300 (8). This check to confirm the match of the hash values may be performed by the distributed ledger infrastructure 100 or by the DC200.
[0054] The above-mentioned placement of the encryption key and recording of the transaction completion (6-1 and 6-2) can be performed indivisibly using the smart contract function. By using the smart contract function, it is possible to prevent discrepancies between data transfer and transaction recording with simple processing.
[0055] In addition, it is possible that the encrypted data cannot be decrypted using the encryption key sent from DP300, but by sharing the encrypted data hash value, DC200 can determine that it cannot be decrypted before obtaining or requesting the encryption key and cancel the transaction. In addition, it is possible that the decrypted data has no value, but DC200 can request cancellation of the transaction by asserting that the data is worthless along with the plaintext data.
[0056] 4A to 4C are sequence diagrams showing details of the data transaction method in this embodiment. The correspondence between the processes in FIGS. 4A to 4C and those in FIG. 3 is as follows: Steps S11 to S14 correspond to process (1) in FIG. 3. Steps S16 to S17 correspond to process (2). Steps S20 and part of S21 and S22 correspond to process (3). Step S25 corresponds to process (4). Steps S26 to S28 correspond to process (5). Step S29 corresponds to process (6-1) and step S30 corresponds to process (6-2). Steps S31 to S33 and S37 correspond to process (7). Steps S38 to S40 correspond to process (8). Note that some of the processes shown in FIGS. 4A to 4C are omitted in FIG. 3.
[0057] In the following description, there is no particular distinction between the peer node 110 and the distributed ledger infrastructure 100, and data exchange between the DC200 or DP300 and the peer node 110 may be expressed as data exchange between the DC200 or DP300 and the distributed ledger infrastructure 100. In addition, when the peer node 110 performs some processing related to the distributed ledger infrastructure 100, it may be expressed as the distributed ledger infrastructure 100 performing this processing.
[0058] In step S11, DC200 requests the creation of a transaction record by passing a user ID (UID) to one of the peer nodes constituting the distributed ledger infrastructure 100. The user ID (UD) may be any identifier that can identify DC200. Furthermore, the destination of the transaction record creation request may be any peer node 110 constituting the distributed ledger infrastructure 100. The transaction record may be referred to as a "data request ticket" or simply a "ticket" since it also represents a request for data from DC200 to DP300.
[0059] In step S12, the distributed ledger infrastructure 100 creates a transaction record on the distributed ledger. At this time, the state of the transaction record (transaction state) is set to the "unreferenced" state. The "unreferenced" state is a state in which the DP 300 has not referenced the created transaction record.
[0060] In step S13, the distributed ledger infrastructure 100 sends a transaction record creation completion notification to the DC 200. The transaction creation completion notification includes a transaction ID. The transaction ID is an identifier that identifies a transaction and also an identifier that identifies a transaction record.
[0061] In step S15, the DC 200 transmits a data request to the DP 300. The data request includes a transaction ID. The data request may also include a specification of data required by the DC 200.
[0062] In step S16, the DP 300 sends a request to reference a transaction record to the distributed ledger infrastructure 100 (peer node 110). The transaction record reference request includes a transaction ID.
[0063] In step S17, the distributed ledger infrastructure 100 retrieves the transaction record corresponding to the received transaction ID from the distributed ledger and transmits it to the DP 300.
[0064] In step S18, the DP 300 prepares the data requested by the DC 200 (plaintext data).
[0065] In step S19, the DP300 encrypts the data prepared in step S18 using a predetermined encryption key. In the following, if it is clear from the context, the data (plaintext) provided from the DP300 to the DC200 and the data obtained by encrypting this plaintext data will be simply referred to as "plaintext data" and "encrypted data", respectively.
[0066] In step S20, the DP 300 calculates hash values of the plaintext data and the encrypted data, respectively. The hash values of the plaintext data and the encrypted data are hereinafter referred to as the plaintext data hash value and the encrypted data hash value.
[0067] In step S21, the DP300 transmits a data preparation notification to the distributed ledger infrastructure 400. The data preparation notification includes a plaintext data hash value, an encrypted data hash value, and an encryption key. In this embodiment, the encryption key is stored in a private space that can be accessed only by those with authority (for example, a Private Data Collection (PDC) in Hyperledger Fabric). The encryption key is first stored in a private space that can be read and accessed only by the DP300. Since the peer nodes 110 that can access the private space are limited, in step S21, the DP300 transmits a data preparation notification to the peer nodes 110 that can access the private space of the DP300 (typically, peer nodes managed by the DP300).
[0068] In step S22, the distributed ledger infrastructure 100 records the plaintext data hash value and the encrypted data hash value received from the DP 300 in the distributed ledger.
[0069] In step S23, the distributed ledger infrastructure 100 stores the encryption key received from the DP 300 in a private space (also referred to as a DP-only space) that can be read and accessed only by the DP 300.
[0070] In step S24, the distributed ledger infrastructure 100 transitions the state of the transaction record to the “encryption key prepared” state. Note that the encrypted data may be transmitted to the DC 200 (S25) prior to the processing of step S24.
[0071] Here, the processes of steps S22 to S24 in the distributed ledger infrastructure 100 are executed indivisibly. Executing these three processes indivisibly means that when any one of the three processes is executed, the other two are also executed; in other words, control is exercised so that all three processes are executed or none of them are executed. Processes and operations executed indivisibly are also called "transaction processing," "indivisible operations," "atomic operations," etc. In the sequence diagrams of Figures 4A to 4C, multiple processes executed indivisibly are labeled "Seq Critical." It is surrounded by a rectangle with a bell.
[0072] In this embodiment, the processes of steps S22 to S24 are executed using a smart contract program based on distributed ledger technology. A smart contract is a program or code that defines the logic of a transaction. Upon receiving a data preparation notification from the data provider 300, the peer node 110 calls and executes this smart contract. This ensures that steps S22 to S24 are executed indivisibly.
[0073] In step S25, the data provider 300 transmits the encrypted data to the data consumer 200. As described above, the encrypted data is transmitted via a communication path different from the distributed ledger.
[0074] In step S 26 , the data consumer 200 calculates a hash value of the encrypted data received from the data provider 300 .
[0075] In step S27, the data consumer 200 transmits an encryption key transfer request to a peer node 110 (typically a peer node managed by the DP 300) that can obtain an encryption key from the private space of the DP 300. The encryption key transfer request includes the transaction ID and the hash value of the encrypted data calculated by the data consumer.
[0076] In step S28, the distributed ledger infrastructure 100 checks whether the encrypted data hash value received from the data consumer 200 matches the encrypted data hash value recorded on the distributed ledger (the encrypted data hash value calculated by the data provider 300). If they do not match, error processing is performed. Here, we will proceed with the explanation assuming that the two match.
[0077] In step S29, the distributed ledger infrastructure 100 moves the encryption key recorded in the DP dedicated space that only the DP 300 has read / write access to, to a private space (hereinafter also referred to as the DC dedicated space) that only the DP 300 has write access to and only the DC 200 has read access to. Here, it is assumed that the encryption key is deleted from the DP dedicated space, but it is sufficient that the encryption key is stored at least in the DC dedicated space.
[0078] In step S30, the distributed ledger infrastructure 100 transitions the state of the transaction record to the “Transaction completed (cancellable)” state.
[0079] The processing of steps S28 to S30 is executed indivisibly using a smart contract function.
[0080] In step S31, in response to the completion of the encryption key transfer request, the DC 200 transmits an encryption key acquisition request to a peer node 110 (typically, a peer node that manages the DC 200) that can acquire an encryption key from the private space of the DC 200. The encryption key acquisition request includes a transaction ID.
[0081] In step S32, the distributed ledger infrastructure 100 obtains the encryption key from the private space of the DC, and in step S33, sends the encryption key to the DC 200.
[0082] In step S34, the DC200 calculates a hash value of the obtained encryption key. In step S35, the DC200 sends an encryption key authenticity confirmation request to the distributed ledger infrastructure 100. The encryption key authenticity confirmation request includes the transaction ID and the hash value of the encryption key calculated by the DC200.
[0083] In step S36, the distributed ledger infrastructure 100 checks whether the hash value of the encryption key calculated by the DC 200 matches the hash value of the encryption key recorded in the distributed ledger (the hash value of the encryption key calculated by the DP 300). If they do not match, error processing is performed. Here, we will proceed with the explanation assuming that the two match.
[0084] In step S37, in response to the authenticity of the encryption key being confirmed, the DC 200 decrypts the encrypted data using the encryption key to obtain plaintext data.
[0085] In step S38, the DC200 calculates a hash value of the plaintext data. In step S39, the DC200 transmits a plaintext authenticity verification request to the distributed ledger infrastructure 100. The plaintext authenticity verification request includes the transaction ID and the hash value of the plaintext data calculated by the DC200.
[0086] In step S40, the distributed ledger infrastructure 100 checks whether the hash value of the plaintext data calculated by DC200 matches the hash value of the plaintext data recorded in the distributed ledger (the hash value of the plaintext data calculated by DP300). If they do not match, error processing is performed. Here, the explanation will proceed assuming that the two match. Note that the hash value of the plaintext data calculated by DP300 may be stored in an area accessible by DC200, and DC200 may check whether the hash values match.
[0087] In step S37, in response to the confirmation of the authenticity of the plaintext data, the DC200 evaluates the plaintext data. The evaluation of the plaintext data may be determined, for example, based on a criterion such as whether the data (plaintext data) provided by the DP300 matches the request of the DC200. If the DC200 determines that the plaintext data is inappropriate, it notifies the distributed ledger infrastructure 100 of that effect. On the other hand, if the DC200 determines that the plaintext data is appropriate, it may notify the distributed ledger infrastructure 100 of that effect, or it may proceed with the processing without notifying the distributed ledger infrastructure 100.
[0088] In step S42, the DC 200 provides a service to the end user using the data provided by the DP 300. The service to be provided is not particularly limited. Instead of providing a service to the end user, the DC 200 may use the data for its own purposes.
[0089] (Transaction status management) FIG. 5 is a diagram showing the state transition of a transaction in this embodiment.
[0090] First, when a transaction record is created (S12) in response to a transaction record creation request (S11) from the DC 200, the transaction state transitions to the "unreferenced" state. The unreferenced state is a state after the transaction record is created, in which the DP 300 has not yet referenced the transaction record.
[0091] When the DP300 refers to the transaction record (S16 to S17) and records the encryption key, the plaintext data hash value, and the encrypted data hash value in the distributed ledger (S18 to S23), the transaction state transitions to the "encryption key prepared" state. The encrypted data is in a state where the recording of the encryption key in the distributed ledger and the transmission of the encrypted data to the DC200 have been completed.
[0092] In the "unreferenced" state, after the DP300 references the transaction record (S16 to S17), the DP300 may reject the transaction. In this case, the DP300 notifies the distributed ledger infrastructure 100 that the transaction is rejected, and the transaction state transitions to the "data transmission refusal error" state. In addition, if the DP300 does not send a data preparation notification even after a predetermined time has passed since the creation of the transaction record, the transaction state transitions to the "data transmission refusal error" state or a separately defined error state.
[0093] In the "encryption key prepared" state, DC200 requests the transfer of the encryption key together with the encrypted data hash calculated by itself (S27), and when the match of the encrypted data hash value is confirmed and the encryption key is placed in the DC dedicated space (S28-S29), the transaction state transitions to the "transaction completed (cancellable)" state. On the other hand, if the encrypted data hash value calculated by DC200 does not match the encrypted data hash value calculated by DP300, the transaction state transitions to the "encryption data incomplete error" state. If the encrypted data hash values do not match, it is assumed that there is some defect in the encrypted data.
[0094] The "transaction completed (cancellable)" state is a state in which the data transaction is tentatively completed, but the transaction can be cancelled within a certain period of time (cancellation request possible time) from the DC 200. This state may be called a "transaction provisionally completed" state.
[0095] In the "transaction completed (cancellable)" state, if it is determined that the encryption key hash value calculated by the DC200 and the encryption key hash value calculated by the DP300 do not match (S36) at the cancellation request possible time from the state transition, the transaction state transitions to the "encryption key incomplete error" state. This state is a state in which there is some defect in the encryption key because the hash values of the encryption keys do not match.
[0096] In the "Transaction Completed (Cancelable)" state, if DC200 asserts that the encryption key is invalid within the cancellation requestable time from the state transition, the transaction state transitions to the "Encryption Key Invalid Error" state. DC200 asserts that the encryption key is invalid when, for example, DC200 cannot decrypt encrypted data using the encryption key.
[0097] In the "Transaction Completed (Cancelable)" state, if it is determined that the plaintext data hash value calculated by the DC200 and the plaintext data hash value calculated by the DP300 do not match (S40) within the cancellation requestable time from the state transition, the transaction state transitions to the "Data Incomplete Error" state. This state indicates that there is some defect in the plaintext data because the hash values of the plaintext data do not match.
[0098] In the "Transaction Completed (Cancelable)" state, if DC200 asserts the invalidity of plaintext data within the cancellation request possible time from the state transition, the transaction state transitions to the "Data Invalid Error" state. DC200 asserts the invalidity of plaintext data when DC200 judges that the plaintext data has no value, for example, because the plaintext data does not match the request of DC200.
[0099] In the "Transaction Completed (Cancelable)" state, if DC200 notifies acceptance of plaintext data, i.e., completion of the transaction, after the cancellation request time has elapsed, the transaction state transitions to the "Transaction Completed (Confirmed)" state. After this, the transaction state cannot be changed and the completion of the transaction is confirmed. Note that even if it is within the cancellation request time, if DC200 notifies completion of the transaction, the transaction state may transition to "Transaction Completed (Confirmed)".
[0100] Billing, i.e., payment of fees from DC200 to DP300, or mediation by a third party, is performed based on transaction records in the "transaction completed (confirmed)" state. On the other hand, all error states are considered to be transaction aborted states. Therefore, transactions that have encountered some kind of error state do not need to be subject to billing. Here, for transactions that have encountered an error state, a third party other than DC200 and DP300 may determine whether the cause of the error is DC200 or DP300, and may perform a reliability evaluation of DC200 and DP300 and billing processing that takes into account the cause of the error.
[0101] (Advantageous Effects of the Present Embodiment) Using the smart contract function, data transfer and changes to transaction status are inseparably performed, so there is no separation between them. In addition, the use of the smart contract function keeps intermediation costs low and enables highly transparent intermediation processing.
[0102] The data exchanged via the distributed ledger board is limited to encryption keys and hash values, and encrypted data is exchanged without going through the distributed ledger, so there are no problems even when exchanging large amounts of data.
[0103] Since hash values of encrypted data are exchanged, it is possible to detect if the data or encryption key provided from DP300 to DC200 is inappropriate, and it has the advantage of being able to stop the transaction. In addition, if inappropriate data is provided or if the decrypted data is worthless, it is possible to track down the DP300 for providing inappropriate data by recording the hash value.
[0104] Furthermore, since the encryption key is exchanged via the private space of the DC 200 and the DP 300, the encryption key can be prevented from being leaked to a third party.
[0105] (Modification) In the above description, the transition to the "transaction completed (cancellable)" state is performed when the encryption key is recorded in the private space of DC200 (S30), but it may be performed when the encryption key is sent to DC200 (S32 to S33). Since data acquisition from the private space must be via the smart contract function, the acquisition of the encryption key from the DC dedicated space and its provision to DC200 can be executed inseparably from the transition of the transaction state.
[0106] In addition, although the encryption key is exchanged via a private space, the encryption key may be encrypted and recorded in a distributed ledger and passed from the DP300 to the DC200. The encryption may be performed using a common key (symmetric key) or a public key (asymmetric key) of the DC200. If the encryption key is not stored in a private space, data can be acquired without using a smart contract function. Therefore, it is preferable to record the completion of the transaction on the condition that the encryption key is recorded in the distributed ledger, rather than on the condition that the encryption key is acquired.
[0107] In addition, the exchange of encryption keys and the recording of transactions do not necessarily have to be performed using a distributed ledger platform. Any system other than a distributed ledger platform can be used as long as it is capable of inseparably providing encryption keys and recording the completion of transactions.
[0108] (Other embodiments) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate without departing from the spirit and scope of the present disclosure.
[0109] The present disclosure can also be realized by supplying a computer program that implements the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium that can be connected to the system bus of the computer, or may be provided to the computer via a network. The non-transitory computer-readable storage medium may be, for example, any type of disk, such as a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic This includes cards, flash memory, optical cards, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]
[0110] 100: Distributed ledger platform 110: Peer node 200: Data Consumer (DC) 300: Data Provider (DP)
Claims
1. An information processing system that mediates data transactions between a data provider and a data consumer, comprising: An information processing system comprising a control unit that inseparably executes the following: making available to the data consumer an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer; or, the data consumer actually obtaining the encryption key; and recording a transaction record between the data provider and the data consumer as a completed transaction.
2. The control unit provides the encryption key from the data provider to the data consumer via a distributed ledger infrastructure.
2. The information processing system according to claim 1 .
3. The control unit records the transaction record in a distributed ledger infrastructure.
2. The information processing system according to claim 1 .
4. The control unit inseparably executes making the encryption key available to the data consumer, or causing the data consumer to actually obtain the encryption key, and recording the transaction record as a transaction completion, using a smart contract function of a distributed ledger infrastructure.
2. The information processing system according to claim 1 .
5. The control unit is In response to receiving the encryption key from the data provider, inseparably recording the encryption key in a data space of the distributed ledger infrastructure that is readable and accessible only to the data consumer, and recording the completion of the transaction, using the smart contract function.
5. The information processing system according to claim 4.
6. The control unit is Recording the encryption key in a data space of the distributed ledger infrastructure that is readable and accessible only to the data consumer; In response to receiving a request to obtain the encryption key from the data consumer, transmitting the encryption key to the data consumer and recording the completion of the transaction are performed in an atomic manner using the smart contract function.
5. The information processing system according to claim 4.
7. The control unit is obtaining a hash value of the encrypted data from the data provider; providing the encryption key to the data consumer when a hash value of the encrypted data calculated by the data consumer itself matches the hash value obtained from the data provider; The information processing system according to claim 1 , further comprising:
8. The control unit is obtaining a hash value of plaintext data corresponding to the encrypted data from the data provider; The data consumer calculates a hash value from the plaintext data obtained by decrypting the encrypted data using the encryption key, and calculates a hash value of the plaintext data obtained from the data provider. updating a state of the data transaction to a transaction aborted if the hash values do not match; The information processing system according to claim 1 , further comprising:
9. The information processing system of claim 1, characterized in that the control unit accepts a request to cancel the transaction from the data consumer for a predetermined period of time after the encryption key becomes available for the data consumer to acquire or has actually acquired it, and updates the status of the data transaction to canceled, and does not update the status of the data transaction after the predetermined period has elapsed.
10. 3. The information processing system according to claim 2, wherein the control unit places the encryption key in a data space of the distributed ledger infrastructure that cannot be read and accessed by anyone other than the data consumer.
11. 3. The information processing system according to claim 2, wherein the control unit encrypts the encryption key using a common key shared by the data provider and the data consumer, and then records the encryption key in the distributed ledger infrastructure.
12. 3. The information processing system according to claim 2, wherein the control unit encrypts the encryption key using a public key of the data consumer and records the encryption key in the distributed ledger infrastructure.
13. An information processing method performed by an information processing system that mediates data transactions between a data provider and a data consumer, comprising the steps of: An information processing method comprising the steps of inseparably executing the steps of making available to the data consumer an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer, or the data consumer actually obtaining the encryption key, and recording a transaction record between the data provider and the data consumer as a completed transaction.
14. A program for causing a computer to execute the information processing method according to claim 13.
15. A smart contract program executed on a distributed ledger platform that mediates data transactions between a data provider and a data consumer, Controlling the distributed ledger infrastructure to inseparably execute the following: making an encryption key for encrypted data, which is used to encrypt data exchanged between the data provider and the data consumer, available to the data consumer via the distributed ledger infrastructure; or, the data consumer actually obtaining the encryption key from the distributed ledger infrastructure; and recording a transaction record between the data provider and the data consumer as a transaction completion in the distributed ledger infrastructure. Smart contract program.
16. 16. The smart contract program of claim 15, wherein making the cryptographic key available to the data consumer via the distributed ledger infrastructure comprises recording the cryptographic key in a data space of the distributed ledger infrastructure that is readable and accessible by the data consumer.
17. 16. The smart contract program of claim 15, wherein the data consumer actually obtaining the encryption key from the distributed ledger infrastructure means that the distributed ledger infrastructure sends the encryption key to the data consumer in response to a request for obtaining the encryption key from the data consumer.
18. 16. The smart contract program of claim 15, wherein after the encryption key becomes available for the data consumer to acquire or for a predetermined period of time after the data consumer actually acquires the encryption key, a request to cancel the transaction is accepted from the data consumer and the state of the data transaction is updated to a transaction canceled state, and the transaction record is not updated after the predetermined period has elapsed.
19. In response to receiving the encryption key from the data provider, recording the encryption key in a data space of the distributed ledger infrastructure that is readable and accessible only to the data provider; In response to receiving an encryption key acquisition request from the data consumer, recording the encryption key in a data space of the distributed ledger infrastructure that is readable and accessible only to the data consumer; The smart contract program according to claim 15, which causes the distributed ledger platform to execute the following:
20. receiving from the data provider a hash value of the encrypted data calculated by the data provider; receiving from the data consumer a hash value of the encrypted data calculated by the data consumer; and causing the distributed ledger platform to further execute the above. recording the encryption key in a data space of the distributed ledger infrastructure that is accessible only to the data consumer, when a hash value of the encrypted data calculated by the data provider matches a hash value of the encrypted data calculated by the data consumer after receiving an encryption key acquisition request from the data consumer; 20. The smart contract program of claim 19.
Citation Information
Patent Citations
Data transaction system and program
JP2018022346A
Transaction Processing
JP2021521544A
Sharing data via blockchain transactions
JP2022548583A
Belt conveyor with ejector
JP2021127246A
Blockchain-based exchange with tokenization
JP2021177666A
