Data trading system

Abstract

An object of the present invention is to implement a mechanism for smoothly circulating IoT data. The data trading system of the present invention includes: a data transmission unit that can send data to a specified object destination through a channel of control setting data from the outside; a data processing unit that executes a data trading contract; an acquisition unit that issues a seller's offer of data to the data processing unit for a provider who provides data; and a data agency unit that issues a buyer's offer of data to the data processing unit for a service provider who uses data. The data processing unit matches the conditions of the seller's offer and the buyer's offer, and in the case of a match, enables the service provider to set a channel for sending data from the provider to the service provider.

Description

Technical Field

[0001] The present invention relates to a data trading system for conducting data trading. In particular, it relates to a data trading system that can smoothly conduct data trading from contract to data trading. Background Art

[0002] (1) Development in the IoT Field

[0003] In recent years, the Internet of Things, i.e., IoT (Internet of Things), has been widely used. In order for ordinary users on the Internet to utilize the data obtained from sensors and the like on this IoT, the following mechanism is mostly used: the data is stored in a server at one time, and users on the Internet utilize the data by accessing this server.

[0004] Figure 25 The schematic diagram of the prior art IoT platform is shown. This platform is called a data storage type platform (hereinafter, the platform will be referred to as PF). As Figure 25 shown, the device 14 that acquires data supplies data to the PF 10 via a gateway (hereinafter, the gateway will be referred to as GW) 12. This prior art PF 10 has a memory (storage device) and can store data. After the data is temporarily stored, it is provided to various objects. The GW 12 is used to bridge the network of the device 14 and the Internet. Figure 25 The data storage type PF is also called a data silo type (warehouse type), and this data storage type is mostly used for the utilization of the prior art IoT.

[0005] The data storage type IoT platform has the following characteristics:

[0006] ・Retain data (make it available)

[0007] ・Possessive (inventory type)

[0008] ・Single domain architecture

[0009] However, in recent years, the amount of data processed using IoT has become huge. There are cases where the amount of data is very small, such as the air temperature data every hour, but there are also many IoT such as surveillance cameras that require a large amount of data. An effective mechanism for sending such a large amount of data in large quantities and in real time has been unknown in the past.

[0010] (2) Automatic Execution of Transaction Contracts (Smart Contracts)

[0011] In addition, in recent years, a framework of smart contracts that automatically executes various transactions has been in use. In this framework, the following technologies are widely advocated: ensuring reliability by using technologies such as distributed ledgers, and automatically executing contracts.

[0012] Most of the frameworks of the existing smart contracts use the so-called blockchain technology and are difficult to be used for data contracts of IoT that process huge amounts of data as described above.

[0013] For example, Patent Document 1 below discloses a mechanism for starting a blockchain application using an IoT gateway or the like. Here, the blockchain application further starts a distributed file sharing application and performs registration of information files in a distributed file sharing network. According to such a mechanism, since a blockchain application is used, the uniqueness of the file content can be ensured.

[0014] Prior Art Documents

[0015] Patent Documents

[0016] Patent Document 1: Japanese Unexamined Patent Application Publication No. 2018-81464. Summary of the Invention

[0017] Problems to be Solved by the Invention

[0018] As described in (1) above, in order to cope with a large amount of IoT data, there is a limit to the existing data storage type PF, and an effective mechanism in the means for solving this problem is not known. Therefore, a mechanism for efficiently transmitting a large amount of IoT data is desired.

[0019] In addition, as described in (2), in recent years, a mechanism for managing transactions using a distributed ledger has been widely used. However, since the mechanism of the distributed ledger is based on the mechanism of constructing a so-called blockchain, it is difficult to process a large amount of data in principle. Therefore, it can be considered that it is actually difficult to apply the mechanism of the distributed ledger to transactions in the IoT field. An effective mechanism in the means for solving this problem is not known. Therefore, a mechanism for managing transactions of a large amount of IoT data using a distributed ledger is desired.

[0020] In view of such a situation, an object of the present invention is to realize a mechanism that enables IoT data to flow smoothly. In addition, an object of the present invention is to realize a mechanism that manages the transaction of the IoT data using a distributed ledger while adopting the circulation mechanism.

[0021] Solutions to the Problems

[0022] The data trading system (such as PtDX116 described later) involved in the present invention includes: a data transmission unit (such as DEXPF106 described later), which can set a data channel through external control and send data to a specified object destination; a data processing unit (such as PTPF118 described later), which executes a data trading contract; an acquisition unit (such as AC104 described later), which makes a seller's offer of data from a provider (such as DO102 described later) that provides data to the data processing unit; and a data agency unit (such as DB110 described later), which makes a buyer's offer of data from a service provider (such as SP108 described later) that uses data to the data processing unit. The data processing unit matches the conditions of the seller's offer and the buyer's offer. In the case of a match, it enables the service provider to set the channel for sending data from the provider to the service provider.

[0023] The data transmission unit may be a data circulation type platform that does not aim to store data (such as the Figure 1 data circulation type PF shown later).

[0024] The data processing unit may use a distributed ledger to preserve and manage the trading contract.

[0025] The distributed ledger may use a blockchain (such as blockchain 200 described later).

[0026] The distributed ledger may use a public blockchain (such as blockchain 200 described later).

[0027] A public key associated with a device (such as device 10 described later) for obtaining the data provided by the provider may be stored on the blockchain.

[0028] The data processing unit may be constituted by using an Ethereum system.

[0029] It may have a subroutine unit (such as subroutines 202n to 202m described later), which processes the output data of the data transmission unit and supplies the processed output data to the input of the data transmission unit.

[0030] The acquisition unit and the data agency unit may use cryptocurrency for settlement in the data processing unit.

[0031] The data may be IoT data, and the provider may provide IoT data.

[0032] It may also have: other data processing units connected to two or more of the above-mentioned data trading systems and the data processing units within the two or more data trading systems. The other data processing transaction unit is the main data processing unit (such as the main PTPF network 118m described later) above the two or more data processing units.

[0033] Advantages of the Invention

[0034] According to the present invention, the circulation of IoT data can be made smooth. In addition, so-called smart contracts can be implemented on IoT. Description of the Drawings

[0035] Figure 1 It is a schematic diagram of PtDX of this embodiment.

[0036] Figure 2 It is an explanatory diagram showing the services provided by the IoT platform including PtDX of this embodiment and a diagram showing the connection with other platforms.

[0037] Figure 3 It is an explanatory diagram showing the structure of PtDX of this embodiment and its peripheral structure.

[0038] Figure 4 It is an explanatory diagram showing the specific trading work of this embodiment.

[0039] Figure 5 It is a schematic diagram of the processing of PTPF118 of this embodiment.

[0040] Figure 6 It is shown by a double-dashed line Figure 5 the data processing part and the data transmission part is shown by a dashed line.

[0041] Figure 7 It is on the basis of Figure 6 with the addition of the consideration flow.

[0042] Figure 8 It is an explanatory diagram of the situation of performing netting.

[0043] Figure 9 It is an explanatory diagram showing the situation of executing transactions between AC104, DB110 and B120 within PTPF118.

[0044] Figure 10 It is an explanatory diagram showing that the distributed ledger can be implemented by private DLT or public DLT in the case of constructing PTPF118.

[0045] Figure 11It is an explanatory diagram of the case where there are three AC104s.

[0046] Figure 12 It is in Figure 11 An explanatory diagram of the structure in which the token 130 (XPT) and the public chain PF132 are added to the figure.

[0047] Figure 13 It is an explanatory diagram of only extracting the part connected to DEXPF106.

[0048] Figure 14 It is a diagram showing the structure of PtDX where there are two DO102s and two SP108s.

[0049] Figure 15 It is an explanatory diagram showing the case where PTPF118 performs condition matching.

[0050] Figure 16 It is an explanatory diagram showing the case where PTPF118 issues a channel ID.

[0051] Figure 17 It is an explanatory diagram showing the case where DEXPF106 with a set channel ID starts data circulation.

[0052] Figure 18 It is an explanatory diagram showing the case of settlement between AC104 and DB110.

[0053] Figure 19 It is a schematic diagram showing the separation of the data plane (high-speed path) for transmitting IoT data from the control plane (low-speed path) containing transaction metadata.

[0054] Figure 20 It is a schematic diagram showing the case of constructing metadata for the control plane on the public domain of the blockchain.

[0055] Figure 21 It is a schematic diagram in which the data outlet is added to the subroutine for processing, and then the processed data is used as the input data of DEXPF106 to enable recursive processing.

[0056] Figure 22 It is an explanatory diagram showing the case where multiple brand domains are configured under the main PTPF network 118m.

[0057] Figure 23 It is a schematic diagram showing the case of placing the public key associated with DeID (device ID) on the blockchain.

[0058] Figure 24 It is a structural diagram of PD Exchange400.

[0059] Figure 25 It is a schematic diagram of a general IoT platform in the prior art, namely, the data silo type (warehouse type). Detailed implementation manners

[0060] Hereinafter, embodiments of the present invention will be described based on the accompanying drawings.

[0061] 1. IoT platform adopted

[0062] Figure 1 It is a schematic diagram showing the principle of the characteristic IoT platform, namely, the IoT platform of PtDX116, described in this embodiment. This figure is a figure for comparison with the IoT platform in the prior art, namely Figure 25 for comparison.

[0063] As shown in this figure, the data of device 24 flows into the network of PtDX116 via gateway 22. This is called the data circulation type PF (platform).

[0064] This data circulation type PF has the following characteristics:

[0065] - Does not hold data

[0066] - Shared type (flow type)

[0067] - Cross-domain architecture

[0068] In Figure 25 the characteristics of the data storage type PF described are:

[0069] - Holds data (makes it available)

[0070] - Exclusive type (inventory type)

[0071] - Single-domain architecture

[0072] In these aspects, there are great differences between the two.

[0073] 2. Function of PtDX

[0074] In this embodiment, a mechanism with the following characteristics will be described.

[0075] (1) In terms of data circulation, a new IoT PF proposed in this embodiment, namely DEXPF, is used.

[0076] (2) In terms of data transaction and service layer provision, a processing (transaction) platform called PTPF is used.

[0077] Such a mechanism is called PtDX116. PtDX is short for Pt Data Exchange. The inventor of the present invention calls this mechanism PtDX.

[0078] Briefly speaking, the role of PtDX116 is to provide an API / service layer for IoT. PtDX116 provides API access services for the IoT device layer to each PF and service platform. As a result, each IoT device can be flexibly connected to various PFs and services.

[0079] In Figure 2 The schematic diagram of such PtDX116 is shown. As shown in this figure, the data of device 14 is supplied to the network of PtDX116 via GW12. Each PF10 can receive IoT data via the network of this PtDX116.

[0080] That is, PtDX116 is a platform that provides an API / service layer for IoT.

[0081] PtDX116 is an IoT data transmission and processing platform, which is a general / information service foundation that can securely and quickly perform transmission and transactions for IoT data.

[0082] PtDX116 corresponds to a preferred example of the data trading system in the scope of the patent claim.

[0083] For users, PtDX116 has the following characteristics.

[0084] It has the characteristic of cross-domain.

[0085] That is, it is a platform that can perform transaction processing in all domains, all regions, and all tiers (cloud, edge, Things) of IoT.

[0086] Characteristics in terms of business

[0087] It has the characteristic of being able to perform business on the platform. That is to say, it is a platform that can perform the following businesses: (a) signing, implementation management, and settlement of contracts; (b) data exchange; (c) management of data ownership.

[0088] 3. Technical characteristics of PtDX

[0089] PtDX is an information foundation that provides IoT data exchange, trading, and settlement, and has the following technical characteristics.

[0090] (1) Distributed ledger technology: It utilizes distributed ledger technology (DLT: Distributed Ledger Technology). By issuing tokens for using PFs, data circulation transactions can be carried out.

[0091] (2) Ultra-high speed: Since DEXPF is used in data communication, communication can be carried out at ultra-high speed. By assigning channel IDs, PTPF enables data trading, settlement, and right control. In addition, it can handle an extremely large amount of traffic.

[0092] (3) Scale: It can handle all of Global, cloud, edge, and Things.

[0093] (4) Security: It can ensure end-to-end and center-to-end security and management.

[0094] (5) Integrity: It can perform the preservation of transaction records. It can perform the complete preservation and management of data records / IoT transactions (Data of Record / IoT Transaction).

[0095] (6) Ownership control: It can manage the permissions for data utilization (DLT / smart contract) based on the rights at each stage of each data stream according to the data origin.

[0096] (7) Cross-domain: It can handle cross-platforms in heterogeneous domains. It can also function as a platform of platforms. This is the so-called Intel Platform.

[0097] 4. The role of PtDX

[0098] PtDX plays an important role in the industries after the information industry revolution. Its role is explained by comparing it with the previous industrial forms.

[0099] In the previous economic system, the main objects were materials and energy, but PtDX takes information as the object. In addition, the currencies used in the previous economic system were money (shells, gold / silver), paper money (banknotes), but in PtDX, tokens (Crypto Currency, cryptocurrency) are used as currency. In addition, the ledgers used in the previous economic system were account books and DBs (databases), but in PtDX, distributed ledgers (DLT: Distributed Ledger Technology) are used as ledgers.

[0100] 5. The structure of PtDX

[0101] In Figure 3 shows the structure of PtDX116 of this embodiment and its peripheral structure. PtDX116 corresponds to a preferred example of the data trading system in the claims.

[0102] AsFigure 3 As shown, PtDX116 is composed of PTPF118 and DEXPF106.

[0103] Device 100 is a device that inputs and outputs IoT data. In this embodiment, it is described as a device for acquiring data, and the situation of trading the data acquired by device 100 is described.

[0104] DO102 is a Device Operator, meaning a person (device) who controls device 100. DO102 is a preferred example of the provider in the claims.

[0105] AC104 is an Acquirer, which is a person's (account) who executes the seller's offer of data, etc.

[0106] Regarding the account

[0107] For example, in the case of using Ethereum, two types of accounts can be used on Ethereum. One is an Externally Owned Account (hereinafter referred to as EOA), and the other is a Contract account. An EOA is an account generated and controlled by a user. A contract account is an account generated by processing an EOA. In addition, a contract account is an automatic agent that takes the processing sent by the EOA as a trigger and executes contract code. In addition, simply put, a contract account is like a collection of variables and functions. In addition, the functions in this embodiment are independently constructed by the inventor. That is to say, the contract code is like a function executed on Ethereum. AC104 in this embodiment is, for example, the above contract account that executes functions.

[0108] In this embodiment, AC104, DB110, and PTPF118 are all implemented using, for example, contract accounts on Ethereum. In addition, the functions of this embodiment can also be implemented using the above contract code on Ethereum.

[0109] AC104 issues a seller's offer of data for DO102. In addition, AC104 is a preferred example of the acquisition unit in the claims.

[0110] DEXPF106 is a Transfer PF, which is a switching device for transferring data.

[0111] PTPF118 is a Transaction (Processing) PF that executes transactions (processing) rather than data.

[0112] DB110 is the Data Broker, which executes the buyer's offer for data and conducts data transactions. DB110 issues a buyer's offer for data to SP108 described later. In addition, DB110 corresponds to a preferred example of the data broker in the claims. Similarly to AC104, DB110 can be implemented using, for example, the contract account on the Ethereum mentioned above, and can also execute a prescribed function.

[0113] B114 is the Brand.

[0114] SP108 is the Service Provider, which is the account of the person who uses data to provide services. SP108 corresponds to a preferred example of the service provider in the claims.

[0115] Bnf112 is the account of the person who conducts business using data. "Bnf" in Bnf112 means "Beneficiary", indicating the recipient or beneficiary.

[0116] In addition, in Figure 3 the double dashed line shows the Business Data Flow. Moreover, the dashed line represents the IoT Data Flow.

[0117] Figure 4 The working situation in the case of a specific transaction is shown.

[0118] (1) First, AC104 accepts the entrustment of DO102 and issues a seller's offer for data on PTPF118. The seller's offer for data in this embodiment is specifically as follows.

[0119] (a) Description of metadata (data profile itself)

[0120] (b) Receiving address (classification)

[0121] (c) Right information

[0122] (d) Others

[0123] Such a seller's offer is issued.

[0124] Then, on PTPF118 (smart contract basis), the buying and selling of data can be executed. If the conditions are met, the agreement is automatically executed, and the contract is executed based on the contract conditions. Here, executing the contract means executing the following two processes: granting a channel corresponding to the contract to enable the use of data; and settling accounts based on the conditions. Here, the processed data can be permanently stored in PTPF118 without being tampered with.

[0125] In addition, PTPF118 can be regarded as the basis for IoT data processing. In this embodiment, for example, it can be constituted by using, for example, distributed ledger technology (DLT: Distributed ledger Technology) (Enterprise Ethereum, enterprise Ethereum) PF (platform). Ethereum is a trademark.

[0126] (2) Next, DB110 accepts the entrustment of SP108 and issues a buyer's offer on PTPF118. The buyer's offer of the data in this embodiment can be specifically described as follows.

[0127] (a) ID for processing, account information, price

[0128] (b) Credit (certification) that DB110 can trust

[0129] If the conditions of these seller's offers and buyer's offers match, PTPF118 automatically executes the contract.

[0130] In addition, in Figure 4 , the ID of DO102 is managed by an unillustrated management system. In addition, SP108 is also managed by an unillustrated management system for its ID.

[0131] 6. Processing operations of PTPF

[0132] Figure 5 A schematic diagram of the processing of PTPF118 is shown. PTPF118 is a data processing platform (transaction) and is responsible for the processing part of data transactions. In contrast, DEXPF106 is a data transmission platform (transmission) and is responsible for the transmission part of data transactions.

[0133] As Figure 5 shows, B (Brand) 120 is drawn, and this B accepts the seller's offer from AC104 and the buyer's offer from DB110 in PTPF118.

[0134] Figure 6 is a diagram that shows the data processing part in Figure 5 with a double-dashed line and the data transmission part in Figure 5 with a dashed line. In this way, one of the features of this embodiment is to separate the processing part from the data transmission part. The distributed ledger of the prior art can process seller's offers and buyer's offers, but it is difficult to process a large amount of data like transmitting data. In this embodiment, the processing that exploits the characteristics of the two platforms respectively is carried out to obtain the so-called division of labor effect.

[0135] Figure 7 is the same figure as Figure 6 but shows the flow of consideration.

[0136] As Figure 7 shown, the consideration for the data transaction is delivered from SP108 to DB110. Next, it is transferred from DB110 to B120 within PTPF118. If the conditions of the contract are met, B120 transfers the consideration to AC104. AC104 delivers the consideration to DO102. In this way, the processing part of the contract is carried out within the data processing platform (transaction), that is, PTPF118.

[0137] DO102 provides data, for example, by receiving consideration.

[0138] In addition, so-called netting can also be executed within PTPF118. As Figure 8 shown, netting can be directly carried out between AC104 and DB110. In addition, netting means calculating the difference between the payment amount and the received amount between the parties and settling this difference between the parties to offset the claims and debts.

[0139] In addition, the settlement, consideration payment, consideration receipt, etc. within PTPF118 can be executed in various ways. For example, it can be executed using cryptocurrencies, etc.

[0140] In this way, in this embodiment, transactions other than data transfer, contract signing, settlement, etc. can be executed within PTPF118. As a result, as Figure 9 shown, transactions between AC104, DB110, and B120 can be smoothly carried out within PTPF118. The feature of this embodiment is that the platform related to the contract is separately set from the data transfer platform. As a result, technologies such as distributed ledgers can be utilized, so transactions that are difficult to tamper with can be securely realized.

[0141] That is to say, a distributed ledger can be used to execute any one or more of the processes of preservation, management, and storage of contract content (contract documents), various transaction documents, settlement records, etc.

[0142] In addition, PTPF118 can use various methods to implement the distributed ledger it adopts. For example, it can be implemented using a private DLT (Private DLT), or it can be implemented using a public DLT (Public DLT). In addition, various other blockchains (consortium type, etc.) can also be utilized. In Figure 10 its explanatory diagram is shown. As Figure 10As shown, the distributed ledger in the case of constructing PTPF118 can be implemented using a private DLT or a public DLT according to the purpose. Here, DLT means Distributed Ledger Technology. PTPF118 can be constituted by, for example, the Ethereum (Ethereum is a trademark) system.

[0143] 7. Actual method

[0144] So far, the case where there is one AC104 and one DB110 has been taken as an example for explanation, but there can also be multiple of each of them. Figure 11 The explanatory diagram showing such an example is shown. In Figure 11 For example, an example where there are three AC104s is shown. These three AC104s can be, for example, the Tokyo branch, Kyoto branch, Osaka branch, etc. of a data providing company.

[0145] The Tokyo branch manages multiple temperature sensors in Tokyo under its control, absorbs the data of these temperature sensors, and supplies it to DEXPF106.

[0146] The Kyoto branch manages multiple temperature sensors in Kyoto under its control, absorbs the data of these temperature sensors, and supplies it to DEXPF106.

[0147] The Osaka branch manages multiple temperature sensors in Osaka under its control, absorbs the data of these temperature sensors, and supplies it to DEXPF106.

[0148] In addition, Figure 11 For example, an example where there are three DB110s and three SP108s is shown. These three SP108s can be, for example, the Musashino City Government, Kyoto City Government, Osaka City Government, etc.

[0149] The Musashino City Government wants to obtain the temperature data of Musashino City in Tokyo and is about to use this data to make judgments such as for heatstroke. Therefore, it applies for the specified temperature data through DB110. Then, it obtains the actual data via DEXPF106.

[0150] The Kyoto City Government wants to obtain the temperature data of Kyoto City and is about to use this data to make judgments such as for photochemical smog. Therefore, it applies for the specified temperature data through DB110. Then, it obtains the actual data via DEXPF106.

[0151] The Osaka City Government wants to obtain the temperature data of Osaka City and is about to use this data to make a prediction judgment for electricity consumption. Therefore, it applies for the specified temperature data through DB110. Then, it obtains the actual data via DEXPF106.

[0152] Like this, there can also be multiple DO102s and AC104s, and there can also be multiple DB110s and SP108s. However, in any case, data exchange is carried out as appropriate in DEXPF, so data can be automatically allocated for each channel.

[0153] Figure 12 It shows that on the basis of the Figure 11 structure, there is also a structure with a token 130 (XPT) and a public blockchain PF132. As shown in this figure, various blockchains can also be included in the platform of PTPF118. For example, it can be a public blockchain. In addition, various tokens can be used as consideration. The cryptocurrency called XPT can also be used.

[0154] 8. Structure of DEXPF

[0155] Figure 13 It is an explanatory diagram that only extracts the part connected to DEXPF106. As shown in this figure, DEXPF106 (IoT data transmission / exchange platform) plays the role of a switch, and by using the API from the outside, channels can be appropriately formed in the desired route. Therefore, a large amount of IoT data can be transmitted / exchanged. DEXPF106 is a preferred example of the data transmission part in the patent claim scope.

[0156] Like this, in this embodiment, since a platform different from the one for receiving and sending contract documents and consideration is separately provided with an IoT data transmission / exchange platform, a large amount of data transmission can be carried out. In contrast, when using PTPF118 to execute a smart contract and data is also to be transmitted on PTPF, it is difficult to handle a large data volume. It can be anticipated that, for example, when using a blockchain to manage within PTPF118, it is very difficult to accommodate a large amount of data in each block of the blockchain.

[0157] Regarding this point, according to this embodiment, since a data circulation type platform without accompanying data storage is used for data transmission as Figure 1 shown, a large amount of data can be transmitted while using a smart contract.

[0158] 9. Working example

[0159] The working example of the case of using a blockchain will be described based on the drawings.

[0160] Different from what has been described so far Figure 3 , Figure 4 etc., in Figures 14 to 18 a figure showing the structure with two DO102s and two SP108s is shown. Hereinafter, the working example will be described using such a figure.

[0161] In Figure 14 , AC104 issues a seller's offer. In addition, DB110 issues a buyer's offer.

[0162] In Figure 15 , PTPF118 performs condition matching.

[0163] In Figure 16 , since the conditions are matched, PTPF118 issues a channel ID and supplies it to DEXPF106. Specifically, for DEXPF106, the application program for setting the channel is started, and the API for issuing the channel ID to DEXPF106 is operated using this application program.

[0164] In Figure 17 , since DEXPF106 has set the channel, data circulation starts.

[0165] In Figure 18 , settlement is performed between AC104 and DB110. Settlement can be carried out using cryptocurrency or other methods.

[0166] In this way, by using PTPF118 and DEXPF106 to separately execute the parts of data communication and parts such as contracts and settlements, efficient business can be carried out.

[0167] 10. Technical Feature Matters

[0168] As described above, in this embodiment, there are various technical feature matters, and these technical feature matters will be described here.

[0169] (1) Two - layer structure

[0170] As described above, PtDX116 of this embodiment separates the data plane (high - speed path) for transmitting IoT data from the control plane (low - speed path) including metadata of transactions. In Figure 19 shows its schematic diagram. A two - layer structure of PTPF118 for communicating metadata such as transactions and DEXPF106 for communicating IoT data, which have been described so far, is formed. That is, PTPF118 is the control plane and DEXPF106 is the data plane.

[0171] Therefore, both high - speed, intermittent, batch, unconventional, etc. data communication and low - speed on - demand data transmission are achieved.

[0172] (2) Separation of the public plane and the non - public plane.

[0173] By constructing the metadata of the control plane on the public domain based on the blockchain, the uniqueness of viewing and permission from third parties is achieved.Figure 20 The schematic diagram thereof is shown. By configuring metadata on a public blockchain, a state is created where although all participants can refer to it, it cannot be tampered with and only legitimate authorized persons can change it, thus enabling a situation where anyone can only use the data under such conditions.

[0174] That is to say, in PTPF118, a public blockchain is used to make various right information public (in a state where anyone can view it). Public means a state where anyone among the members participating in the blockchain can view it. In addition, the metadata here refers to the type of information, the definition of permissions, right information, etc.

[0175] (3) Overlapping data processing based on subroutines

[0176] By adding the output of data to a subroutine for processing and then using the processed data as the input data of DEXPF106, recursive processing can be performed.

[0177] That is, the output data of DEXPF106 is provided to subroutines 202n to 202m connected to the output of DEXPF106. The output data of subroutines 202n to 202m becomes the input data of DEXPF106. That is, subroutines 202n to 202m supply the processed data to the input of DEXPF106.

[0178] Therefore, recursive processing can be performed. Figure 21 The figure showing these subroutines 202n to 202m is shown. Here, n and m are natural numbers. Therefore, data transformation and data multiplexing processing can be realized. Data format transformation, intelligent processing, etc. can be performed.

[0179] In addition, subroutines 202n to 202m are equivalent to a preferred example of the subroutine part in the claims of the patent.

[0180] (4) Major brand agreement

[0181] The main PTPF network 118m implements cross - domain agreements among brands within the same brand (under the major brand). Figure 22 This situation is shown. As Figure 22 shown, a plurality of brand domains are configured under the main PTPF network 118m. In each domain, a data trading system (brand B1) based on PTPF118 and DEXPF106 described above is formed. In Figure 22 the example, three brands are configured, and any number can also exist. In addition, the DEX when viewed from the perspective of DEX (Data Exchange) under the domain is called the main DEX.

[0182] That is to say, the PTPF118m above the PTPF118 described in the above embodiment can perform transactions between multiple PTPF118s (via the upper PTPF118m).

[0183] In addition, the main PTPF network 118m corresponds to a preferred example of the main data processing unit in the claims.

[0184] (5) Place the public key of DeID on the blockchain

[0185] By placing the public key associated with DeID (device ID) on the blockchain, no matter at which stage DeID is embedded in the device, the private key of Dev (device) is hidden. In this state, DEX (data exchange) can utilize the information that can be referred to but cannot be tampered with. Figure 23 The explanatory diagram thereof is shown. The device ID is written in the shaded part.

[0186] Figure 23 Case 1 shows an example where DP302 writes DeID into the device and delivers it to DO102. That is, DM (Device Manufacture) 300 creates a device and delivers it to DP (Device Provider) 302. After DP302 writes DeID into the device, it delivers it to DO102.

[0187] Figure 23 Case 2 shows an example where DM300 writes DeID into the device and delivers it to DP302 or DO102. That is, DM (device manufacturer) 300 writes DeID into the device and then delivers it to DP (device provider) 302 or DO (device manager) 102.

[0188] In Figure 23 In case 3, after DO102 writes DeID into the device, it deploys the device.

[0189] In this embodiment, the public key can be placed (stored) on the blockchain in any way.

[0190] 11. "PD Exchange" as one of the specific examples of DEXPF106

[0191] DEXPF106, as one of the characteristic structures in this embodiment, can utilize various transmission systems, but can also directly use, for example, the product of the applicant of this application, namely "PD Exchange", as DEXPF106.

[0192] Hereinafter, this PD Exchange will be described.

[0193] PD Exchange is data exchange server software and cloud services, which are specifically used for the common functions "collection of data from IoT devices" and "sending instructions to IoT devices" in IoT application development.

[0194] Functions of PD Exchange

[0195] PD Exchange has a flexible distribution function. For example, it can distribute the simultaneously sent "temperature" and "humidity" data to different applications respectively, or distribute only "temperature" to one application and both "temperature" and "humidity" to another application. That is, it can also perform data allocation.

[0196] Product Structure of PD Exchange

[0197] API Connect (Open Platform)

[0198] PD Exchange can be operated using REST APIs. It can quickly develop applications with good affinity for existing networks. In addition to request and response type APIs, it can also utilize real-time APIs for instant distribution.

[0199] Two-way Channel (Two-way Communication)

[0200] Simply sending data sometimes cannot fully utilize the value of IoT data. However, if PD Exchange is used, two-way communication can be carried out to send instructions from applications to IoT devices.

[0201] Security (Robust Security)

[0202] PD Exchange encrypts the data sending and receiving paths based on SSL / TSS to prevent eavesdropping. In addition, it also supports using message digest to prevent data tampering. Data exchange is carried out on PD Exchange, and data is completely discarded within a certain period. That is, PD Exchange is not aimed at data storage.

[0203] Analysis (Recording and Analysis)

[0204] Users can obtain usage reports immediately after starting to use the services of PD Exchange. The data included in the usage reports and the usage reports themselves can be downloaded in traditional formats such as CSV. Furthermore, data can also be obtained using the management system API.

[0205] Cost saving (pursuing valuable development)

[0206] It can reduce the time until the start of using PD Exchange, the development man-hours of applications, the costs of equipment, the operation resources after providing services, etc., and can realize the value and benefit creation of IoT services.

[0207] Anywhere (can be applied to the cloud and on-premises)

[0208] It can be installed and used in public cloud services, local systems, etc. of IaaS (Infrastructure as a Service). In addition, PD Exchange can also be provided as an infrastructure system.

[0209] Architecture

[0210] Next, based on the attached drawings, the architecture (structure) of PD Exchange 400 will be described. Figure 24 The structure diagram of PD Exchange 400 is shown. As shown in this figure, PD Exchange 400 has: a Channel Mapper 402 that allocates channels for data transmission; an API for IoT Devices 404 that is an API for IoT devices; an API for IoT Applications 406 that is an API for IoT applications; and an API for IoT Management 408 that is an API for controlling this PD Exchange 400.

[0211] As described above, the Channel Mapper 402 performs the following tasks: setting the channel of IoT data through external control and sending specified IoT data to the designated recipient address.

[0212] The API for IoT Devices 404 is an API that receives IoT data sent from the IoT device 410. The IoT device 410 can also be an IoT gateway.

[0213] The API for IoT Applications 406 is an API corresponding to the IoT application 412, and the IoT application 412 uses this API for IoT applications 406 to receive IoT data.

[0214] The API 408 for IoT management is an API for externally controlling the PD Exchange 400. Figure 24 An example is shown in which the Management Toolbelt 414 uses the API 408 for IoT management to control the PD Exchange 400.

[0215] Characteristic technologies of the PD Exchange 400

[0216] DeID

[0217] As one of the characteristic matters of the PD Exchange 400, DeID can be cited. DeID is a unit for identifying IoT devices on the PD Exchange 400. The format is unique to the PD Exchange 400, but it has compatibility with UUIDv4 and can maintain high affinity with other IoT systems.

[0218] In addition, DeID is divided into a prefix part and a suffix part, and the prefix part is managed by the PD Exchange 400. In contrast, the suffix part is independent of the PD Exchange 400, can be set separately, and can be managed like an IP address (network part and host part).

[0219] Channel

[0220] In the PD Exchange 400, the concept of channels is used to control IoT data streams. Therefore, compared with the prior art, the time until utilization, the development man-hours of applications, the costs of devices, and the operation resources after starting services can be reduced. As a result, the effect of creating IoT business value and benefits is obtained.

[0221] Anonymization of DeID

[0222] It can be accessed from the application side only through the channel ID, and DeID is not directly exposed on the application side. Although it may seem inconvenient, with such a structure, the possibility of device ID leakage on the application side can be reduced.

[0223] In this way, on an anonymized system, the possibility of device ID leakage in the application can be reduced. Determining the ID is equivalent to permitting device operation. In addition, anonymizing DeID can also achieve the effect of reducing the custody cost of sensitive information on the application side.

[0224] Specialty of data exchange

[0225] PD Exchange400 is not for data storage. It temporarily stores data while waiting for data acquisition, but does not provide permanent storage function. In addition, different from the so-called "queue", data is deleted only when the temporary storage period expires. With such a structure, subscription management (management of the position to continue reading) needs to be carried out on the data acquisition side, but instead it can be read independently from multiple applications, so the miniaturization of applications can be implemented.

[0226] Docker

[0227] PD Exchange400 works through Docker. By containerizing the working environment, the system application can be carried out in the same environment from physical servers to IaaS. It can also be applied to the situation where it starts on the remaining physical servers at startup and gradually migrates to IaaS. Even in such a case, it can be migrated without changing the code related to the working environment. In addition, the upgrade can be more comprehensively controlled by updating the Docker image with the docker pull instruction.

[0228] Import types of PD Exchange400

[0229] As the import types of PD Exchange400, there are two types. That is, a more suitable PD Exchange400 can be selected from the two types of cloud (SaaS) type and on-premises type according to the purpose and use of the system and solution that PD Exchange400 is intended to build.

[0230] The embodiments of the present invention have been described above, but the present invention is not limited to the above embodiments. In addition, the effects described in this embodiment are only the best effects produced by the present invention, and the effects of the present invention are not limited to the effects described in this embodiment.

[0231] Description of reference numerals

[0232] 10: PF

[0233] 12: GW

[0234] 14: Device

[0235] 20: R

[0236] 22: GW

[0237] 24: Device

[0238] 100: Device

[0239] 102: DO

[0240] 104: AC

[0241] 106: DEXPF

[0242] 108: SP

[0243] 110: DB

[0244] 112: Bnf

[0245] 114: B

[0246] 116: PtDX

[0247] 118: PTPF

[0248] 120: B

[0249] 130: Token (XPT)

[0250] 132: Public Chain PF

[0251] 200: Blockchain

[0252] 300: DM

[0253] 302: DP

[0254] 400: PD Exchange

[0255] 402: Channel Mapper

[0256] 404: API for IoT Devices

[0257] 406: API for IoT Applications

[0258] 408: API for IoT Management

[0259] 410: IoT Devices

[0260] 412: IoT Applications

[0261] 414: Management Tools

Claims

1. A data trading system that automatically conducts data trading between a provider who provides data and a service provider who utilizes the data, comprising: A data processing unit that matches the conditions of the seller's offer and the buyer's offer, and in the case of a match, automatically executes the transaction contract for the data and does not perform the transmission of the data. The data processing unit uses a distributed ledger to preserve and manage the transaction contract. The execution of the transaction contract for the data includes: The data processing unit assigns a channel corresponding to the contract based on the contract conditions and conducts settlement based on the contract conditions; A data transmission unit for data transmission. The data transmission unit is a data circulation type platform that does not aim to store data and can, through control from the data processing unit, set a data channel so that data from the provider is sent to the specified service provider via the data transmission unit; An acquisition unit that makes a seller's offer of data from the provider to the data processing unit; And A data agency unit that makes a buyer's offer of data from the service provider to the data processing unit. When the seller's offer and the buyer's offer match, the data processing unit causes the data transmission unit to set the channel for sending data from the provider to the service provider via the data transmission unit.

2. The data trading system according to claim 1, wherein The distributed ledger utilizes blockchain.

3. The data trading system according to claim 1, wherein The distributed ledger utilizes a public blockchain.

4. The data trading system according to claim 2, wherein A public key associated with the device used to obtain the data provided by the provider is stored on the blockchain.

5. The data trading system according to claim 1, wherein The data processing unit is constituted by using the Ethereum system.

6. The data trading system according to claim 1, wherein It has a subroutine unit that processes the output data of the data transmission unit and supplies the processed output data to the input of the data transmission unit.

7. The data trading system according to claim 1, wherein The data is IoT data and the provider provides IoT data.

8. The data trading system according to claim 1, wherein The acquisition unit and the data agency unit conduct settlement using cryptocurrency in the data processing unit.

9. A data trading system, comprising: Two or more data trading systems according to any one of claims 1 to 8; and Another data processing unit connected to the data processing units within the two or more data trading systems. The other data processing unit is a main data processing unit at a higher level than the two or more data processing units.

Images