Information processing system, information processing method, and non-transitory storage medium
Through the distributed ledger platform and smart contract functions, the problem of difficult to efficiently record transaction records in data transactions is solved, and the inseparable exchange of encryption keys and the reliability of transaction completion is realized, cost and labor are reduced, and security is improved. transparency.
Patent Information
- Application Number
- CN202410427459.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-04-10
- Publication Date
- 2024-11-12
AI Technical Summary
In data transactions, it is difficult for the prior art to record transaction records efficiently and reliably between data providers and data consumers, and to prevent differences between transaction records and actual data transactions, avoid unfair benefits, and reduce labor and costs. .
Through the distributed ledger platform and smart contract functions, the indivisible exchange and transaction records of encryption keys are realized, ensuring that data consumers obtain encryption keys and record transaction completion, prevent transaction records from being different, and allow transaction cancellation within the predetermined period.
The transaction record reliability between data providers and data consumers is realized, the differences between transaction records and data transactions are avoided, mediation costs and labor are reduced, and transparency and security are improved.
Smart Images

Figure CN118940284A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to an information processing system, an information processing method, and a non-transitory storage medium. Background Art
[0002] In data transactions, it is important not only to exchange the data itself, but also to keep transaction records for incentive settlement and vouching.
[0003] Japanese Unexamined Patent Application Publication No. 2021-177666 discloses a method for exchanging entities between users, and discloses generating an invitation (Tx) including an output (UTXO) associated with a hash of an encrypted and electronically transferable digital asset and a script. Here, the script includes an indication of the entity to be exchanged, the conditions of the exchange, and a public key associated with the user. Summary of the invention
[0004] The present disclosure provides a technique that enables recording transaction records in data exchanges between data providers and data consumers in a manner that is integral to the data exchange and less labor intensive.
[0005] A first aspect of the present invention relates to an information processing system that mediates a data transaction between a data provider and a data consumer. In the information processing system, a control unit indivisibly performs: making an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer available to the data consumer or causing the data consumer to actually obtain the encryption key, and recording a transaction record between the data provider and the data consumer as transaction completion.
[0006] In the first aspect, the control unit may provide the encryption key from the data provider to the data consumer via the distributed ledger platform.
[0007] In the first aspect, the control unit may be configured to record the transaction record on the distributed ledger platform.
[0008] In the first aspect, the control unit may be configured to use the smart contract function of the distributed ledger platform to indivisibly perform: 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 transaction completion.
[0009] In the first aspect, the control unit may be configured to, in response to receiving an encryption key from a data provider, use a smart contract function to indivisibly record the encryption key in a data space of the distributed ledger platform that can only be read and accessed by the data consumer, and record the completion of the transaction.
[0010] In the first aspect, the control unit can be configured to record the encryption key in a data space of the distributed ledger platform that can only be read and accessed by data consumers, and in response to receiving a request to obtain the encryption key from the data consumer, use the smart contract function to indivisibly transmit the encryption key to the data consumer and record the completion of the transaction.
[0011] In the first aspect, the control unit may be configured to obtain a hash value of the encrypted data from the data provider, and provide the encryption key to the data consumer when the hash value of the encrypted data calculated by the data consumer matches the hash value obtained from the data provider.
[0012] In the first aspect, the control unit can be configured to obtain a hash value of plaintext data corresponding to the encrypted data from a data provider, and to update the status of the data transaction to transaction cancellation when a hash value calculated based on the plaintext data obtained by the data consumer by decrypting the encrypted data using an encryption key does not match the hash value of the plaintext data obtained from the data provider.
[0013] In the first aspect, the control unit can be configured to receive a transaction cancellation request from the data consumer and update the status of the data transaction to transaction cancellation within a predetermined period after the data consumer becomes able to obtain the encryption key or after the data consumer actually obtains the encryption key, and then the control unit can be configured not to update the status of the data transaction after the predetermined period has passed.
[0014] In the first aspect, the control unit may be configured to place the encryption key in a data space of the distributed ledger platform that is not readable and accessible to anyone except the data consumer.
[0015] In the first aspect, the control unit may be configured to encrypt the encryption key using a public key shared by the data provider and the data consumer, and record the encryption key in the distributed ledger platform.
[0016] In the first aspect, the control unit may be configured to encrypt the encryption key using a public key of the data consumer and record the encryption key in the distributed ledger platform.
[0017] A second aspect of the present invention relates to an information processing method, which is performed by an information processing system that mediates a data transaction between a data provider and a data consumer. The information processing method includes: indivisibly performing: making an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer available to the data consumer or causing the data consumer to actually obtain the encryption key, and recording a transaction record between the data provider and the data consumer as transaction completion.
[0018] A third aspect of the present invention relates to a non-transitory storage medium storing instructions that are executable by one or more processors and cause the one or more processors to perform the second aspect.
[0019] A fourth aspect of the present invention relates to a non-transitory storage medium storing a first instruction, which can be executed by one or more processors and causes the one or more processors to perform a function. The function includes: controlling a distributed ledger platform to indivisibly perform: making an encryption key for encrypted data obtained by encrypting data exchanged between a data provider and a data consumer available to the data consumer via the distributed ledger platform or causing the data consumer to actually obtain the encryption key from the distributed ledger platform, and recording a transaction record between the data provider and the data consumer in the distributed ledger platform as a transaction completion.
[0020] In the fourth aspect, making the encryption key available to the data consumer via the distributed ledger platform may refer to recording the encryption key in a data space of the distributed ledger platform that can be read and accessed by the data consumer.
[0021] In the fourth aspect, causing the data consumer to actually obtain the encryption key from the distributed ledger platform may mean that the distributed ledger platform transmits the encryption key to the data consumer in response to a request from the data consumer to obtain the encryption key.
[0022] According to a fourth aspect, a non-transitory storage medium may store a second instruction that performs a function including: receiving a transaction cancellation request from a data consumer within a predetermined period after the data consumer becomes able to obtain an encryption key or after the data consumer actually obtains the encryption key, and updating the state of the data transaction between the data provider and the data consumer to a transaction cancellation state, and not updating the transaction record after the predetermined period has passed.
[0023] In a fourth aspect, the function may cause the distributed ledger platform to execute: in response to receiving an encryption key from a data provider, recording the encryption key in a data space of the distributed ledger platform that can only be read and accessed by the data provider, and in response to receiving an encryption key acquisition request from a data consumer, recording the encryption key in a data space of the distributed ledger platform that can only be read and accessed by the data consumer.
[0024] In a fourth aspect, the function may also include: causing the distributed ledger platform to execute: receiving a hash value of encrypted data calculated by the data provider from a data provider, and receiving a hash value of encrypted data calculated by the data consumer from a data consumer, and after receiving an encryption key acquisition request from the data consumer, when the hash value of the encrypted data calculated by the data provider matches the hash value of the encrypted data calculated by the data consumer, the encryption key can be recorded in a data space of the distributed ledger platform that can only be accessed by the data consumer.
[0025] According to various aspects of the present disclosure, transaction records in data exchanges between data providers and data consumers can be reliably recorded with less labor. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, wherein like numerals represent like elements, and wherein: Figure 1 is a diagram showing a schematic configuration of a data exchange system according to one embodiment; Figure 2 is a diagram showing the configuration of an information processing apparatus in this embodiment; Figure 3 is a diagram showing an overview of data exchange processing in this embodiment; Figure 4A is a timing diagram showing the data exchange process in this embodiment; Figure 4B is a timing diagram showing the data exchange process in this embodiment; Figure 4C is a timing diagram showing the data exchange process in this embodiment; and Figure 5 This is a state transition diagram of the data request ticket in this embodiment. DETAILED DESCRIPTION Overview
[0027] First, consider the case where the exchange of data (data transaction) is accompanied by incentives between different entities. In this disclosure, the entity that transmits data is called a data provider, and the entity that receives data and uses data to provide services is called a data consumer. Data providers and data consumers are also referred to as DP and DC, respectively. In addition, these terms represent not only the entity itself, but also the information processing device or information processing system managed by the entity.
[0028] In data transactions, it is important not only to exchange the data itself, but also to keep transaction records for incentive settlement and vouchers.
[0029] The interests of DP and DC can be said to be in conflict. The purpose of DP is to receive incentives while minimizing costs, while the purpose of DC is to obtain data without incurring incentive costs. Therefore, it is necessary to prevent the difference between actual data exchange and transaction records and prevent DP or DC from generating unfair benefits. On the other hand, it is desirable to avoid amplifying a large amount of workload and cost in data mediation for preventing unfair benefits.
[0030] Therefore, the embodiments of the present disclosure provide a technology that allows transaction records in data exchange between DP and DC to be reliably recorded so that there is no difference with the actual data transaction and less labor is required to record the transaction.
[0031] One embodiment of the present invention 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, while the DC is a device that obtains data from the DP and uses the data.
[0032] In one embodiment of the present disclosure, an information processing system includes a control unit that inseparably performs: making an encryption key of encrypted data obtained by encrypting data exchanged between DP and DC available to DC, or making DC actually obtain the encryption key, and recording the transaction record between DC and DP as transaction completion.
[0033] In the present disclosure, "making data available to DC" and "making DC actually obtain data" are also expressed as "providing data to DC". For example, in the present disclosure, the process of providing the encryption key to DC by the information processing system includes at least one of the process of making the encryption key available to DC or the process of actually transmitting the encryption key to DC. Therefore, one embodiment of the present disclosure can also be expressed as an embodiment of indivisibly performing the provision of the encryption key to DC and recording the transaction record between DC and DP as the completion of the transaction.
[0034] "Executing multiple processes indivisibly" means that when any one of the multiple processes is executed, the remaining processes are also executed; in other words, it is controlled so that either all of the multiple processes are executed or none of the multiple processes are executed. Processes and operations that are executed indivisibly are also called "transaction processing", "indivisible operations", "atomic operations", etc.
[0035] In one embodiment of the present disclosure, the exchange of encryption keys between DP and DC and the recording of transaction records can be performed using distributed ledger technology (blockchain technology). When distributed ledger technology is adopted, the information processing system in the present disclosure is one or more information processing devices that form at least a part of the distributed ledger platform. A peer node is an example of an information processing device that forms a part of the distributed ledger platform. In this embodiment, the activation or actual acquisition of encryption keys and the recording of transaction completion can be performed inseparably using the smart contract function of distributed ledger technology. "Smart contract" is a function that automatically executes predetermined processing (such as reading and writing records on a distributed ledger). In this embodiment, the control unit records the completion of the transaction in the transaction record under the condition that the encryption key is provided to the DC. By using the smart contract function, it can be ensured that the two processes are inseparable.
[0036] When making the cryptographic keys available to the DC and recording the completion of the transaction between the DC and the DP can be performed indivisibly, the smart contract functionality can also be used to record the completion of the transaction when the cryptographic keys are written (in an area readable and accessible by the DC). Using distributed ledger technology that requires writing data via smart contracts is an example of a method to achieve indivisible processing.
[0037] For example, in response to receiving an encryption key from a DP, the control unit uses a smart contract function to indivisibly record the encryption key in a distributed ledger and record the completion of the transaction. A distributed ledger is a data space that can be read and accessed by any participating node, and is an example of a data space that can be read and accessed by a DC. Another example of a data space that can be read and accessed by a DC is a data space that can only be read and accessed by a DC. A specific example of such a data space is a private data collection in a Hyperledger Fabric platform. By using a smart contract function that records the completion of a transaction when an encryption key is recorded in a data space that can be read and accessed by a DC in a distributed ledger platform, it is possible to indivisibly execute the encryption key available to a DC and record the completion of a transaction between a DC and a DP.
[0038] In order to indivisibly perform both the DC actually obtaining the encryption key and recording the completion of the transaction, it is expected that the DC uses the smart contract function when obtaining the encryption key. In distributed ledger technology, one method that requires a smart contract when obtaining data is to store the data in a data space that can only be accessed by authorized personnel (a private space, such as a private data collection in Hyperledger Fabric). 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 indivisibly perform the acquisition of the encryption key and record the completion of the transaction.
[0039] As an example, the control unit records the encryption key in a data space in the distributed ledger platform that can only be read and accessed by the DC in response to receiving the encryption key from the DP, and then, in response to receiving the encryption key acquisition request from the DC, the control unit uses the smart contract function to indivisibly transfer the encryption key to the DC and record the completion of the transaction. In the distributed ledger technology, it may be necessary to use the smart contract function when reading data from a data space (Private Space) that can only be accessed by the DC. Therefore, by using a smart contract function that records the completion of the transaction when receiving a request to obtain the encryption key from the DC and transmitting the encryption key to the DC, it is possible to indivisibly execute making the encryption key available to the DC and recording the completion of the transaction between the DC and the DP.
[0040] As described above, providing the encryption key to the DC and marking the transaction record as completed is performed inseparably, thereby avoiding the difference between the data transaction (data exchange) and the transaction record. Therefore, it is possible to prevent the DC from denying the completion of the transaction and refusing the incentive payment after the DC obtains the data, and it is possible to prevent the DP from claiming the completion of the transaction and receiving the incentive payment without providing the data. Another advantage of the present disclosure is that less processing is required in the mediation system, and mediation of data exchange can be performed at a low cost.
[0041] In this embodiment, a channel for data exchange and a separate channel for processing related to data exchange (such as encryption keys and transaction records) can be established. Channel separation can be logical separation or physical separation. Channels are also called planes (control plane and data plane). The "channel" here refers to a logical or physical communication path, and it is different from the concept of channels used in distributed ledger platforms.
[0042] As an example of channel separation, processing related to encryption key exchange and transaction recording can be performed via a distributed ledger platform, and the encrypted data itself can be provided from the DP to the DC without passing through the distributed ledger platform. This is because distributed ledgers are not suitable for recording large amounts of data. The target of exchange using distributed ledgers is encryption keys with a small amount of data, and the data itself is exchanged using a separate route, enabling efficient processing. In addition, the effect of encrypting and exchanging data is that even when the encrypted data itself is leaked to a third party, the content of the plaintext cannot be known, thereby protecting the secrecy of the plaintext.
[0043] This channel separation is expected to simplify implementation, and efficient processing can be expected even when distributed ledger technology is adopted. In other embodiments of the present disclosure, encrypted data can also be provided from DP to DC using a distributed ledger.
[0044] In one embodiment of the present disclosure, an information processing system for mediating data transactions between DP and DC includes peer nodes configuring a distributed ledger network, and the peer nodes have the function of executing smart contracts.
[0045] In one embodiment of the present disclosure, within a predetermined period of time after providing an encryption key to the DC, it is allowed to update the transaction record from the transaction completion state to the transaction cancellation state, and after the predetermined period of time has passed, the transaction record cannot be updated from the transaction completion state. Even when the transaction is recorded as completed within the predetermined period of time, the transaction can be canceled, so the status within and after the predetermined period of time can be respectively distinguished as "transaction temporarily completed" and "transaction completed" in a narrow sense, or "transaction completed (cancellable)" and "transaction completed (settled)". The transaction termination that occurs within the predetermined period of time can be executed in response to the distributed ledger platform identifying data transaction inconsistencies, or in response to receiving a transaction cancellation request from the DC. When the transaction is canceled in response to a request from the DC, it is expected to receive the reason for not continuing the transaction from the DC. Therefore, after the transaction is canceled, the control unit or other functional units of the information processing system can evaluate the reliability of the DC and DP by verifying whether the reason for cancellation is appropriate, or can cancel the transaction by evaluating whether the reason for cancellation is appropriate.
[0046] When a transaction is completed with an encryption key provided, there may be a problem where the encrypted data cannot be decrypted using the encryption key provided, or it can be decrypted but the decrypted data has no value (e.g., the decrypted data is different from what the DC requested). In this case, it is desirable to be able to cancel the transaction, so for appropriate data exchanges, it is advantageous to be able to cancel the transaction within a predetermined period from when the encryption key was provided through the above process.
[0047] In one embodiment of the present disclosure, the control unit of the information processing system can obtain the hash value of the encrypted data from the DP, and then 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" can be performed by the information processing system directly transmitting the encryption key to the DC, by the information processing system requesting other devices to transmit the encryption key to the DC, by the information processing system recording the encryption key in a memory (such as a distributed ledger) that the DC can read and access, and so on.
[0048] Further, the information processing system may confirm whether the hash value provided by DP matches the hash value calculated by DC, or DC may confirm and then notify the information processing system. When DC transmits a notification to the information processing system, it may take the form of, for example, an encryption key acquisition request transmitted to the information processing system on the premise that DC has confirmed the match. When the information processing system is to perform confirmation, for example, the information processing system may receive the hash value calculated by DC from DC in the form of an encryption key authenticity confirmation request, and compare the hash value calculated by DC with the hash value provided by DP.
[0049] Further, when the hash value provided by DP does not match the hash value calculated by DC, the information processing system preferably updates the transaction record to a transaction cancellation state or other error state. Specifically, the information processing system may update the transaction record to a transaction cancellation state in one of the following situations: when the information processing system receives a mismatch report from DC within a predetermined period, when the information processing system does not receive a matching report from DC within a predetermined period, or when the information processing system receives a hash value calculated by DC from DC within a predetermined period and confirms that the hash value calculated by DC does not match the hash value provided by DP.
[0050] Thus, when the hash value of the encrypted data provided by the DP does not match the hash value calculated by the DC, it is inferred that there is some defect in the encrypted data sent by the DP to the DC, for example, the encrypted data cannot be decrypted using the provided encryption key. Therefore, in this case, the benefit of being able to cancel the transaction without providing the encryption key to the DC is that it can avoid completing the transaction even if the data cannot actually be exchanged. In addition to the above viewpoints, for example, compared to also finding that the encryption cannot be decrypted after actually performing processes such as recording the encryption key in the distributed ledger by the information processing system, obtaining the encryption key by the DC, and decrypting the encryption key, it is also advantageous from the perspective of the processing efficiency of the entire system because the transaction can be canceled before performing these processes.
[0051] In one embodiment of the present disclosure, the control unit of the information processing system can obtain the hash value of the plaintext data corresponding to the encrypted data from the DP, and then when the hash value calculated by the DC from the plaintext data obtained by decrypting the encrypted data using the encryption key does not match the hash value obtained by the DC from the information processing system, the control unit can update the transaction record to a transaction cancellation state or other error state.
[0052] The information processing system may confirm whether the hash value provided by the DP matches the hash value calculated by the DC, or the DC may perform the confirmation and then 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 there is a match or a mismatch, or the DC may notify the information processing system only when there is a match or only when there is a mismatch. When the information processing system confirms whether the hash values match, the confirmation may be performed by the information processing system receiving the hash value calculated by the DC from the DC in the form of a plain text authenticity confirmation request, etc., and comparing the hash value calculated by the DC with the hash value provided by the DP.
[0053] Thus, when the hash value of the plaintext data provided by the DP does not match the hash value calculated by the DC, it is presumed that there is some defect in the encrypted data sent by the DP to the DC or in the plaintext data from which the encrypted data originated. In this case, being able to cancel a transaction that is expected to encounter problems is advantageous to the DC because it can avoid completing the transaction even though the appropriate data exchange has not occurred.
[0054] In one embodiment of the present disclosure, the control unit of the information processing system can obtain the hash value of the encryption key from the DP, and then when 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, the control unit can update the transaction record to a transaction cancellation state or other error state.
[0055] In this case, as with the comparison of hash values of plaintext data, being able to cancel a transaction that is expected to encounter problems is advantageous to the DC because it can avoid the transaction from being completed even though there was no proper data exchange.
[0056] In one embodiment of the present disclosure, the matching comparison of the hash value of the encrypted data, the matching comparison of the hash value of the encryption key, and the matching comparison of the plaintext hash value may all be performed, only some of them may be performed, or none of them may be performed. In the case of multiple executions, it is conceivable that the matching comparison of the hash value of the draft data, the matching comparison of the hash value of the encryption key, and the matching comparison of the hash value of the plaintext data are performed in sequence. This helps to minimize wasteful processing during transaction cancellation. The processing order is not limited to this and can be performed in any order.
[0057] In one aspect of the present disclosure, it is expected that the information processing system provides an encryption key to the DC in a manner that the encryption key is not disclosed to a third party. Even if the encryption key itself is leaked, as long as the corresponding encrypted data remains unknown, the security of the data can be maintained, but it is more desirable to prevent the encryption key itself from being leaked. As a form of providing to prevent the encryption key from being leaked to a third party, there are two methods: placing the encryption key in a data space that cannot be read and accessed by anyone except the DC (or a data space that can only be read and accessed by the DC), and encrypting the encryption key using a public 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 except the DC is a private data collection (PDC) in Hyperledger Fabric. For example, when obtaining an encryption key from a DP, the encryption key is first placed in the private space of the DP, and when the conditions are met, the encryption key is moved from the PDC of the DP to the private space of the DC, so that the information processing system can exchange encryption keys while protecting the secret of the encryption key. System Configuration
[0058] Figure 1 is a diagram showing a configuration of a data exchange system according to one embodiment. The data exchange system has a configuration in which a distributed ledger platform 100, a data consumer (DC) 200, and a data provider (DP) 300 are connected to each other to be able to communicate with each other.
[0059] The DC 200 is a computer managed by an entity that uses data provided from the DP 300 to, for example, provide services to end users.
[0060] DP 300 is a computer managed by an entity that provides the data it holds to DC 200 .
[0061] The distributed ledger platform 100 is configured by a plurality of peer nodes 110 and provides a distributed ledger technology. In addition to transaction records, the distributed ledger platform 100 also records encryption keys for decrypting encrypted data exchanged between DC 200 and DP 300 and various hash values for confirming the authenticity of data. In this embodiment, the encrypted data exchanged between DC 200 and DP 300 is itself exchanged between DC 200 and DP 300 without using the distributed ledger platform 100.
[0062] The distributed ledger platform 100 of this embodiment is a consortium type in which the management entities of DC 200 and DP 300 participate as managers, and the peer node 110 is an information processing device managed by the management entity of DC 200 or DP 300. The consortium type distributed ledger platform is constructed using, for example, the Hyperledger Fabric framework. A server-side program based on Hyperledger Fabric is installed on the peer node 110 to build a distributed ledger platform. In addition, a smart contract function (chain code) is deployed on the peer node 110.
[0063] Further, the distributed ledger platform 100 includes data spaces that participants can freely access and data spaces with restricted access rights. In this embodiment, data spaces that only DP 300 can read and write and data spaces that DP 300 can write and DC 200 can read are used.
[0064] In another embodiment, the distributed ledger platform 100 may take the form of a private type, including a single administrator and a limited number of participants, or a public type, in which there is no administrator and anyone is allowed to participate.
[0065] 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 functions from the DC 200 or DP 300 and from the peer node 110 described below.
[0066] The peer node 110, DC 200 and DP 300 are each configured by one or more information processing devices (computers). Figure 2 As shown in FIG. 1 , 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. In the information processing device 20, the processor 21 executes a program loaded into the main storage device 22, thereby realizing the functions described below.
[0067] In this embodiment, the distributed ledger platform 100 corresponds to an information processing system that mediates data transactions between the DC 200 and the DP 300. Further, the processor 21 of the peer node 110 corresponds to the control unit in the present invention. Overview of processing
[0068] Figure 3 FIG. 2 is a diagram showing an overview of the data transaction method in this embodiment. Figure 3As shown in , this embodiment is separated into a data plane for transmitting the data itself provided from DP 300 to DC 200 and a control plane for exchanging data related to transaction mediation. The criteria for separating the data plane and the control plane may be logical, physical or substantially different. In this embodiment, the control plane passes through the distributed ledger platform 100, while the data plane does not pass through the distributed ledger platform 100.
[0069] Will be based on Figure 3 Briefly describe data transaction processing. Figure 3 is used to illustrate the outline and will be referred to below FIG. 4A to FIG. 4C The details of the processing are described.
[0070] First, DC 200 creates a transaction record in the distributed ledger platform 100 to record the details and status of the transaction, or to make the details and status of the transaction referenceable (1). DP 300 refers to the created transaction record (2) and prepares the data (plaintext data) requested by DC 200. DP 300 encrypts the plaintext data to be transmitted to DC 200, records the hash values of the plaintext data and the encrypted data on the distributed ledger platform 100 (3), and also transmits the encrypted data to DC 200 via the data plane (4). DC 200 calculates the hash value of the encrypted data received from DP 300, determines whether it matches the hash value of the encrypted data calculated by DP 300, and confirms whether there is any inconsistency in the encrypted data sent from DP 300 (5). In this embodiment, the distributed ledger platform 100 performs the hash value matching confirmation itself. Under the condition that the hash value of the encrypted text data matches, recording the encryption key provided by DP 300 in the distributed ledger (6-1) and updating the transaction record to a completed state (6-2) are performed inseparably. Here, the encryption key is placed in a private space on the distributed ledger that can only be read and accessed by DC 200 and can only be written and accessed by DP 300. DC 200 obtains the encryption key and decrypts the encrypted data to obtain the plaintext data (7). In addition, DC 200 determines whether the hash value of the plaintext data obtained by decrypting the encrypted data received from DP 300 matches the hash value of the plaintext data calculated by DP 300, and confirms whether there is any inconsistency in the data sent from DP 300 (8). This hash value matching confirmation can be performed by the distributed ledger platform 100 or by DC200.
[0071] The indivisible execution of encryption key placement and transaction completion record (6-1 and 6-2) can be performed using the smart contract function. The smart contract function is able to prevent discrepancies between data exchange and transaction records through simple processing.
[0072] In addition, it is possible that the encrypted data cannot be decrypted using the encryption key sent from DP 300, but by sharing the hash value of the encrypted data, DC 200 can determine that it cannot be decrypted before obtaining or requesting the encryption key and cancel the transaction. In addition, although it is possible that the decrypted data has no value, DC 200 can claim that the data has no value together with the plaintext data and request cancellation of the transaction.
[0073] FIG. 4A to FIG. 4C Detailed description of the data transaction method in this embodiment. FIG. 4A to FIG. 4C Processing and Figure 3 The corresponding relationship between the processing in is as follows: Steps S11 to S14 correspond to Figure 3 In the processing (1). Steps S16 to S17 correspond to the processing (2). Steps S20 and parts of S21 and S22 correspond to the processing (3). Step S25 corresponds to the processing (4). Steps S26 to S28 correspond to the processing (5). Step S29 corresponds to the processing (6-1), and step S30 corresponds to the processing (6-2). Steps S31 to S33 and S37 correspond to the processing (7). Steps S38 to S40 correspond to the processing (8). Figure 3 In, omitted FIG. 4A to FIG. 4C Some of the processing shown in .
[0074] In the following description, the peer node 110 and the distributed ledger platform 100 are not particularly distinguished, and the data exchange between the DC 200 or DP 300 and the peer node 110 can be represented as the data exchange between the DC 200 or DP 300 and the distributed ledger platform 100. In addition, when the peer node 110 performs a certain process related to the distributed ledger platform 100, it can be represented as the distributed ledger platform 100 performing the process.
[0075] In step S11, DC 200 requests one of the peer nodes forming the distributed ledger platform 100 to create a transaction record by giving a user ID (UID). The user ID (UID) may be any identifier capable of identifying DC 200. Further, the destination of the transaction record creation request may be any peer node 110 forming the distributed ledger platform 100. Since the transaction record also represents a data request from DC 200 to DP 300, it may be referred to as a "data request ticket" or simply a "ticket".
[0076] In step S12, the distributed ledger platform 100 creates a transaction record on the distributed ledger. In this case, 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 does not reference the created transaction record.
[0077] In step S13, the distributed ledger platform 100 transmits 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 for identifying a transaction and also an identifier for identifying a transaction record.
[0078] In step S15, DC 200 transmits a data request to DP 300. The data request includes a transaction ID. Further, the data request may include a specification of data required by DC 200.
[0079] In step S16, the DP 300 transmits a transaction record reference request to the distributed ledger platform 100 (peer node 110). The transaction record reference request includes a transaction ID.
[0080] In step S17 , the distributed ledger platform 100 obtains the transaction record corresponding to the received transaction ID from the distributed ledger and transmits it to the DP 300 .
[0081] In step S18 , the DP 300 prepares the data requested by the DC 200 (plain text data).
[0082] In step S19, DP 300 encrypts the data prepared in step S18 using a predetermined encryption key. Hereinafter, when it is clear from the context, data (plain text) provided from DP 300 to DC 200 and data obtained by encrypting the plain text data will be referred to as "plain text data" and "encrypted data", respectively.
[0083] In step S20, the DP 300 calculates hash values of the plaintext data and the encrypted data, respectively. Hereinafter, the hash values of the plaintext data and the encrypted data are referred to as plaintext data hash values and encrypted data hash values.
[0084] In step S21, DP 300 transmits a data preparation completion notification to the distributed ledger platform 100. The data preparation completion 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 only be accessed by authorized personnel (for example, a private data collection (PDC) in Hyperledger Fabric). The encryption key is first stored in a private space that can only be read and accessed by DP 300. Since the peer nodes 110 that can access the private space are limited, in step S21, DP 300 transmits a data preparation completion notification to the peer nodes 110 that can access the private space of DP 300 (usually peer nodes managed by DP 300).
[0085] In step S22, the distributed ledger platform 100 records the plaintext data hash value and the encrypted data hash value received from the DP 300 in the distributed ledger.
[0086] In step S23 , the distributed ledger platform 100 stores the encryption key received from the DP 300 in a private space (also referred to as a DP-only space) that can only be read and accessed by the DP 300 .
[0087] In step S24, the distributed ledger platform 100 changes the state of the transaction record to the "encryption key preparation completed" state. Transmitting the encrypted data to the DC 200 (S25) may be performed before the processing of step S24.
[0088] Here, the processing of steps S22 to S24 in the distributed ledger platform 100 is performed indivisibly. The three processes are performed indivisibly, which means that when any one of the three processes is performed, the other two processes are also performed. In other words, it means that either all three processes are performed, or none of the three processes are performed. Processes and operations that are performed indivisibly are also called "transaction processing", "indivisible operations", "atomic operations", etc. FIG. 4A to FIG. 4C In the timing diagram of , multiple processes that are executed inseparably are surrounded by rectangles marked as "timing-critical".
[0089] In this embodiment, the processing of steps S22 to S24 is performed by using a smart contract program using distributed ledger technology. A smart contract is a program or code that defines the transaction logic. The peer node 110 that receives the data preparation completion notification from the DP 300 calls and executes the smart contract. This ensures that steps S22 to S24 are executed indivisibly.
[0090] In step S25, DP 300 transmits the encrypted data to DC 200. As described above, the encrypted data is transmitted via a communication path different from the communication path of the distributed ledger.
[0091] In step S26 , the DC 200 calculates a hash value of the encrypted data received from the data provider 300 .
[0092] In step S27, DC 200 transmits an encryption key transmission request to a peer node 110 (usually a peer node managed by DP 300) that can obtain encryption keys from the private space of DP 300. The encryption key transmission request includes the transaction ID and the hash value of the encrypted data calculated by the data consumer.
[0093] In step S28, the distributed ledger platform 100 confirms whether the encrypted data hash value received from the DC 200 matches the encrypted data hash value recorded on the distributed ledger (the encrypted data hash value calculated by the DP 300). When there is a mismatch, error handling is performed. Here, the description will continue assuming that both match.
[0094] In step S29, the distributed ledger platform 100 moves the encryption key recorded in the DP-only space that can only be read and written by the DP 300 to a private space (hereinafter also referred to as the DC-only space) that can only be written by the DP 300 and can only be read by the DC 200. Here, it is assumed that the encryption key is deleted from the DP-only space, but it is sufficient to store the encryption key at least in the DC-only space.
[0095] In step S30, the distributed ledger platform 100 changes the status of the transaction record to the "transaction completed (cancellable)" status.
[0096] The processing of steps S28 to S30 is performed inseparably using the smart contract function.
[0097] In step S31, in response to completion of the encryption key transmission request, DC 200 transmits an encryption key acquisition request to a peer node 110 (usually a peer node managing DC 200) capable of acquiring encryption keys from a private space of DC 200. The encryption key acquisition request includes a transaction ID.
[0098] In step S32, the distributed ledger platform 100 obtains the encryption key from the private space of the DC, and transmits the encryption key to the DC 200 in step S33.
[0099] In step S34, DC 200 calculates the hash value of the obtained encryption key. In step S35, DC 200 transmits an encryption key authenticity confirmation request to the distributed ledger platform 100. The encryption key authenticity confirmation request includes the transaction ID and the hash value of the encryption key calculated by DC 200.
[0100] In step S36, the distributed ledger platform 100 confirms 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). When there is a mismatch, error handling is performed. Here, the description will continue assuming that both match.
[0101] In step S37, the DC 200 decrypts the encrypted data using the encryption key to obtain the plaintext data in response to the confirmation of the authenticity of the encryption key.
[0102] In step S38, DC 200 calculates the hash value of the plaintext data. In step S39, DC 200 transmits a plaintext authenticity confirmation request to the distributed ledger platform 100. The plaintext authenticity confirmation request includes the transaction ID and the hash value of the plaintext data calculated by DC 200.
[0103] In step S40, the distributed ledger platform 100 confirms whether the hash value of the plaintext data calculated by DC 200 matches the hash value of the plaintext data recorded in the distributed ledger (the hash value of the plaintext data calculated by DP 300). When there is a mismatch, error handling is performed. Here, the description will continue assuming that both match. The hash value of the plaintext data calculated by DP 300 can be stored in an area accessible to DC 200, and DC 200 can confirm the match of the hash value.
[0104] In step S41, DC 200 evaluates the plaintext data in response to the confirmation of the authenticity of the plaintext data. The plaintext data may be evaluated based on, for example, whether the data (plaintext data) provided from DP 300 matches the request of DC 200. When DC 200 determines that the plaintext data is not appropriate, it notifies the distributed ledger platform 100 of this fact. On the other hand, when it determines that the plaintext data is appropriate, it may notify the distributed ledger platform 100 of this, or may continue processing without notification.
[0105] In step S42, DC 200 provides services to the end user using the data provided from DP 300. The services provided are not particularly limited. In addition, instead of providing services to the end user, DC 200 may also use the data for itself. Transaction status management
[0106] Figure 5 : is a diagram showing the state transition of the transaction in this embodiment.
[0107] First, when a transaction record is created (S12) in response to a transaction record creation request (S11) from DC 200, the transaction status changes to the "unreferenced" status. The unreferenced status is a status in which the transaction record is not referenced by DP 300 after the transaction record has been created.
[0108] When DP 300 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 status changes to the "encryption key preparation completed" 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 DC 200 are completed.
[0109] In the "Not Referenced" state, after the DP 300 refers to the transaction record (S16 to S17), the DP 300 may reject the transaction. In this case, the DP 300 notifies the distributed ledger platform 100 that the transaction is rejected, and the transaction state transitions to the "Data Transfer Rejected Error" state. Further, when the data preparation completion notification is not transmitted from the DP 300 even after a predetermined period of time has passed since the transaction record was created, the transaction state transitions to the "Data Transfer Rejected Error" state or a separately defined error state.
[0110] In the "Encryption key preparation completed" state, DC 200 requests the transmission of the encryption key together with the encrypted data hash value 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-only space (S28 to S29), the transaction state changes to the "Transaction completed (cancelable)" state. On the other hand, when the encrypted data hash value calculated by DC 200 does not match the encrypted data hash value calculated by DP 300, the transaction state changes to the "Encrypted data incomplete error" state. When the encrypted data hash values do not match, it is presumed that there is some defect in the encrypted data.
[0111] The "transaction completed (cancellable)" state is a state in which the data transaction has been completed, but DC 200 can request cancellation of the transaction within a certain period of time (a time when cancellation may be requested). This state can be called the "transaction temporarily completed" state.
[0112] In the "Transaction Complete (Cancellable)" state, when it is determined that the encryption key hash value calculated by the DC 200 does not match the encryption key hash value calculated by the DP 300 within the time of possible cancellation request after the state transition (S36), the transaction state transitions to the "Encryption Key Incomplete Error" state. In this state, the hash values of the encryption keys do not match, so there is some defect in the encryption key.
[0113] In the "Transaction Complete (Cancellable)" state, when DC 200 claims that the encryption key is invalid within the time when cancellation can be requested after the state transition, the transaction state changes to the "Encryption Key Invalid Error" state. For example, when DC 200 cannot decrypt encrypted data using the encryption key, DC 200 claims that the encryption key is invalid.
[0114] In the "Transaction Complete (Cancellable)" state, when it is determined that the hash value of the plaintext data calculated by the DC 200 does not match the hash value of the plaintext data calculated by the DP 300 within the time of the possible cancellation request after the state transition (S40), the transaction state transitions to the "Data Incomplete Error" state. In this state, the hash values of the plaintext data do not match, so there is some defect in the plaintext data.
[0115] In the "Transaction Complete (Cancellable)" state, when DC 200 asserts that the plaintext data is invalid within the time when cancellation can be requested after the state transition, the transaction state changes to the "Data Invalid Error" state. When DC 200 determines that the plaintext data has no value, for example because the plaintext data does not match the request of DC 200, DC 200 asserts that the plaintext data is invalid.
[0116] In the "Transaction Complete (Cancellable)" state, when DC 200 notifies acceptance of plain text data, that is, when the transaction is completed, after the time when cancellation can be requested has passed, the transaction state changes to the "Transaction Complete (Confirmed)" state. Thereafter, the transaction state cannot be changed, and the transaction is completed. Even within the time when cancellation can be requested, if DC 200 notifies completion of the transaction, the transaction state can be changed to the "Transaction Complete (Confirmed)" state.
[0117] The billing process, i.e., the payment of fees from DC 200 to DP 300, or the mediation thereof by a third party, is performed based on the transaction record in the "transaction completed (confirmed)" state. On the other hand, all error states can be regarded as transaction cancellation states. Therefore, transactions that result in a certain error do not require billing processing. For transactions that result in an error state, a third party other than DC 200 and DP 300 can determine whether the cause of the error is in DC 200 or DP 300, and perform reliability evaluation of DC 200 and DP 300, billing processing that takes the cause of the error into consideration, and the like. The beneficial effects of this embodiment
[0118] Since the smart contract function is used to indivisibly exchange data and change transaction status, there is no difference between the two. In addition, since the smart contract function is adopted, the mediation cost is low and the mediation process can be performed with high transparency.
[0119] Data exchange via the distributed ledger platform is limited to encryption keys and hash values, and the exchange of encrypted data does not need to go through the distributed ledger, so there is no problem during the exchange of large data.
[0120] Since the hash value of the encrypted data is exchanged, it is possible to detect that the data or encryption key provided from DP 300 to DC 200 is not appropriate, and there is also an advantage that the transaction can be canceled. Further, in the case where the provided data is not appropriate or the decrypted data has no value, by recording the hash value, it is possible to track that the data provided by DP 300 is not appropriate.
[0121] Furthermore, since the encryption key is exchanged via the private spaces of the DC 200 and the DP 300, it is possible to prevent the encryption key from being leaked to a third party. Deformation Examples
[0122] In the description, the transition to the "transaction completed (cancellable)" state is performed when the encryption key is recorded in the private space of DC 200 at the moment (S30), but this can also be performed when the encryption key is transmitted to DC 200 at the moment (S32 to S33). Since the smart contract function must be used when acquiring data from the private space, the acquisition of the encryption key from only the DC space, the provision to DC 200, and the transaction state transition can be performed inseparably.
[0123] Further, although the encryption key is exchanged via the private space, the encryption key may be encrypted, recorded in the distributed ledger, and then passed from DP 300 to DC 200. Encryption may be performed using a public key (symmetric key) or a public key (asymmetric key) of DC 200. When the encryption key is not stored in the private space, data may be obtained without using the smart contract function. Therefore, it is preferred to record the completion of the transaction under the condition that the encryption key is recorded in the distributed ledger, rather than recording the completion of the transaction under the condition that the encryption key is obtained.
[0124] Furthermore, the exchange of cryptographic keys and transaction records can be performed without necessarily using a distributed ledger platform. In addition to a distributed ledger platform, any system that can indivisibly provide cryptographic keys and record the completion of a transaction can be used. Other embodiments
[0125] The present embodiment is merely an example, and the present disclosure can be implemented with appropriate changes within the scope of the gist thereof.
[0126] The present disclosure can also be implemented by providing a computer program that implements the functions described in the embodiment to a computer, and causing one or more processors included in the computer to read and execute the program. Such a computer program can be provided to the computer by a non-transient computer-readable storage medium that can be connected to the system bus of the computer, or can be provided to the computer via a network. Non-transient computer-readable storage media, for example, include any type of disk, such as a disk (floppy (Floppy, registered trademark), hard disk drive (Hard Disk Drive, HDD), etc.) and optical disk (CD-ROM, DVD optical disk, Blu-ray disc, etc.), read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), EPROM, EEPROM, magnetic card, flash memory, optical card and any type of medium suitable for storing electronic instructions.
Claims
1. Information processing systems that mediate data transactions between data providers and data consumers, It is characterized in that The information processing system comprises: A control unit that inseparably performs: making an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer available to the data consumer or causing the data consumer to actually obtain the encryption key, and recording a transaction record between the data provider and the data consumer as transaction completion.
2. The information processing system according to claim 1, It is characterized in that The control unit is configured to provide the encryption key from the data provider to the data consumer via a distributed ledger platform.
3. The information processing system according to claim 1, It is characterized in that The control unit is configured to record the transaction record on a distributed ledger platform.
4. The information processing system according to claim 1, It is characterized in that The control unit is configured to use the smart contract function of the distributed ledger platform to indivisibly execute: 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 transaction completion.
5. The information processing system according to claim 4, It is characterized in that The control unit is configured as follows: In response to receiving the encryption key from the data provider, the smart contract function is used to indivisibly record the encryption key in a data space of the distributed ledger platform that can only be read and accessed by the data consumer, and record the completion of the transaction.
6. The information processing system according to claim 4, It is characterized in that The control unit is configured as follows: Recording the encryption key in a data space on the distributed ledger platform that can only be read and accessed by the data consumer; and In response to receiving a request from the data consumer to obtain the encryption key, the encryption key is transmitted indivisibly to the data consumer using the smart contract function, and the completion of the transaction is recorded.
7. The information processing system according to claim 1, It is characterized in that The control unit is configured as follows: Obtaining a hash value of the encrypted data from the data provider; and When the hash value of the encrypted data calculated by the data consumer matches the hash value obtained from the data provider, the encryption key is provided to the data consumer.
8. The information processing system according to claim 1, It is characterized in that The control unit is configured as follows: Obtaining from the data provider a hash value of the plaintext data corresponding to the encrypted data; as well as When a hash value calculated based on plaintext data obtained by the data consumer decrypting the encrypted data using the encryption key does not match a hash value of the plaintext data acquired from the data provider, the state of the data transaction is updated to transaction cancellation.
9. The information processing system according to claim 1, It is characterized in that The control unit is configured to receive a transaction cancellation request from the data consumer and update the status of the data transaction to transaction cancellation within a predetermined period after the data consumer becomes able to obtain the encryption key or after the data consumer actually obtains the encryption key, and then the control unit is configured not to update the status of the data transaction after the predetermined period has passed.
10. The information processing system according to claim 2, It is characterized in that The control unit is configured to place the encryption key in a data space of the distributed ledger platform that cannot be read and accessed by anyone except the data consumer.
11. The information processing system according to claim 2, It is characterized in that The control unit is configured to encrypt the encryption key using a public key shared by the data provider and the data consumer, and record the encryption key in the distributed ledger platform.
12. The information processing system according to claim 2, It is characterized in that The control unit is configured to encrypt the encryption key using the public key of the data consumer and record the encryption key in the distributed ledger platform.
13. An information processing method, which is performed by an information processing system, said information processing system mediating data transactions between data providers and data consumers, It is characterized in that The information processing method comprises: Inseparably performing: making an encryption key for encrypted data obtained by encrypting data exchanged between the data provider and the data consumer available to the data consumer or causing the data consumer to actually obtain the encryption key, and recording a transaction record between the data provider and the data consumer as transaction completion.
14. Non-transitory storage media, It is characterized in that The non-transitory storage medium stores instructions, which are executable by one or more processors and cause the one or more processors to perform the information processing method according to claim 13 .
15. Non-transitory storage media, It is characterized in that The non-transitory storage medium stores a first instruction, which can be executed by one or more processors and causes the one or more processors to perform functions including: Controlling a distributed ledger platform to indivisibly perform: making an encryption key for encrypted data obtained by encrypting data exchanged between a data provider and a data consumer available to the data consumer via the distributed ledger platform or causing the data consumer to actually obtain the encryption key from the distributed ledger platform, and recording a transaction between the data provider and the data consumer in the distributed ledger platform as transaction completion.
16. The non-transitory storage medium according to claim 15, It is characterized in that Making the encryption key available to the data consumer via the distributed ledger platform means recording the encryption key in a data space of the distributed ledger platform that can be read and accessed by the data consumer.
17. The non-transitory storage medium according to claim 15, It is characterized in that Causing the data consumer to actually obtain the encryption key from the distributed ledger platform means that the distributed ledger platform transmits the encryption key to the data consumer in response to a request from the data consumer to obtain the encryption key.
18. The non-transitory storage medium according to claim 15, It is characterized in that The non-transitory storage medium stores a second instruction, and the second instruction performs the following functions: After the data consumer becomes able to obtain the encryption key or within a predetermined period after the data consumer actually obtains the encryption key, a transaction cancellation request is received from the data consumer, and the status of the data transaction between the data provider and the data consumer is updated to a transaction cancellation status, and after the predetermined period has passed, the transaction record is not updated.
19. The non-transitory storage medium according to claim 15, It is characterized in that The functions include causing the distributed ledger platform to execute, In response to receiving the encryption key from the data provider, recording the encryption key in a data space on the distributed ledger platform that is readable and accessible only by the data provider, and In response to receiving an encryption key acquisition request from the data consumer, the encryption key is recorded in a data space on the distributed ledger platform that can only be read and accessed by the data consumer.
20. The non-transitory storage medium according to claim 19, It is characterized in that The functions also include causing the distributed ledger platform to execute, receiving from the data provider a hash value of the encrypted data calculated by the data provider, and receiving from the data consumer a hash value of the encrypted data calculated by the data consumer, and After receiving an encryption key acquisition request from the data consumer, when the hash value of the encrypted data calculated by the data provider matches the hash value of the encrypted data calculated by the data consumer, recording the encryption key in a data space of the distributed ledger platform that can only be accessed by the data consumer is performed.
