Information processing device, information processing method, and information processing program

Abstract

This information processing device comprises: an acquisition unit that acquires encrypted apparatus data from an apparatus used by a user and acquires, from a first provider, an encrypted first conversion rule by which the apparatus data is encrypted according to a first rule; a generation unit that generates encrypted first converted data on the basis of the acquired apparatus data and first conversion rule; and a management unit that associates the generated first converted data with the user and the first provider, and manages the use of and a reward for the first converted data.

Description

Information processing device, information processing method, and information processing program

[0001] The present disclosure relates to an information processing device, an information processing method, and an information processing program.

[0002] Patent Literature 1 describes that a data provider can send and deposit data that he or she owns or that is related to him or her to a data processing device of an information bank / information safe. Patent Literature 1 also describes that the data provider can determine the status and provision level of data to be provided to a data user from among the deposited data, as well as whether or not to provide the data, and can receive incentives in accordance with the data provided to the data user.

[0003] Japanese Patent Application Laid-Open No. 2020-190797

[0004] However, in the above-mentioned conventional technology, data acquisition and conversion are not performed in a manner that keeps the data and conversion rules secret, making it difficult to combine a user's device data and conversion rules in a confidential state and utilize them as personal information assets.

[0005] Therefore, the present disclosure proposes an information processing device, an information processing method, and an information processing program that can combine a user's device data and conversion rules in a confidential state and utilize them as personal information assets.

[0006] An information processing device according to one aspect of the present disclosure includes an acquisition unit that acquires encrypted device data of a device used by a user and an encrypted first conversion rule that converts the device data in accordance with a first rule from a first provider, a generation unit that generates encrypted first conversion data based on the acquired device data and the first conversion rule, and a management unit that associates the generated first conversion data with the user and the first provider and manages the use and compensation of the first conversion data.

[0007] 1 is a diagram illustrating an example of a configuration of an information processing system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating an example of a data flow according to an embodiment of the present disclosure. FIG. 2 is a flowchart illustrating an example of a rights management process according to an embodiment of the present disclosure. FIG. 3 is a block diagram illustrating an example of a functional configuration of a management device according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of rights allocation to generation contributors. FIG. 5 is a diagram illustrating an example of management of a change history of a rights certificate. FIG. 6 is a sequence diagram illustrating an example of a process of combining conversion rules according to an embodiment of the present disclosure. FIG. 7 is a sequence diagram illustrating an example of a process of generating service data and a rights certificate according to an embodiment of the present disclosure. FIG. 8 is a sequence diagram illustrating an example of a distribution process when service data is used according to an embodiment of the present disclosure. FIG. 9 is a sequence diagram illustrating an example of a deletion process when device data is returned or deleted according to an embodiment of the present disclosure. FIG. 10 is a diagram illustrating an example of a data flow in use case UC11. FIG. 11 is a diagram illustrating an example of a data flow in use case UC12. FIG. 12 is a diagram illustrating an example of a data flow in use case UC13. FIG. 13 is a diagram illustrating an example of a data flow in use case UC21. FIG. 14 is a diagram illustrating an example of a data flow in use case UC22. FIG. 15 is a diagram illustrating an example of a data flow in use case UC23. FIG. 16 is a diagram illustrating an example of a data flow in use case UC24. FIG. 17 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of an information processing device.

[0008] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the following embodiments, the same components are designated by the same reference numerals, and redundant description will be omitted.

[0009] The present disclosure will be described in the following order: 1. System configuration according to embodiment 2. Rights management processing flow according to embodiment 3. Management device configuration according to embodiment 4. Information processing procedure according to embodiment 5. Use cases 6. Modified example of embodiment 7. Hardware configuration 8. Effects

[0010] (Embodiment) <<1. System Configuration According to Embodiment>> Fig. 1 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment of the present disclosure. As shown in Fig. 1, the information processing system 1 includes an equipment data providing device 10, a conversion rule providing device 20, a user device 30, and a management device 100. The equipment data providing device 10, the conversion rule providing device 20, the user device 30, and the management device 100 are connected to each other via a network N, for example, in a wired or wireless manner so as to be able to communicate with each other.

[0011] The device data providing device 10 is an information processing device that collects and manages device data, which is data related to the use of devices used by users (device users) in a device data providing organization. The device data providing device 10 also includes in-vehicle devices such as in-vehicle MPUs (Micro Processing Units). The device data providing device 10 may collect and manage device data from multiple users. The device data providing device 10 provides the collected device data to the management device 100 in a confidential (encrypted) state. The device data providing device 10 receives a device data right certificate for each user from the management device 100. Furthermore, the device data providing device 10 distributes the compensation distributed from the management device 100 to each user based on the device data right certificate for each user.

[0012] The conversion rule providing device 20 is an information processing device at a conversion rule providing organization that provides the management device 100 with conversion rules in a concealed (encrypted) state for converting equipment data in accordance with specific rules. The conversion rule providing organization is an example of a first provider, and the multiple conversion rule providing organizations are examples of a first provider and a second provider. The specific rule is an example of a first rule and a second rule. The conversion rule providing device 20 receives a certificate of right for the conversion rule from the management device 100. The conversion rule providing device 20 also receives a consideration distributed from the management device 100.

[0013] The utilization device 30 is an information processing device in a service data utilization organization that utilizes service data, which is confidential converted data generated by the management device 100 based on the equipment data and the conversion rule. The first user and the second user are examples of a service data utilization organization. The utilization device 30 pays, for example, to the management device 100, a fee corresponding to the service data used.

[0014] The management device 100 is an information processing device that manages equipment data, conversion rules, service data, and consideration information in the information processing system 1. The management device 100 also performs secure computation together with the equipment data providing device 10 and the conversion rule providing device 20. The management device 100 also issues and manages various certificates, such as equipment data right certificates, conversion rule right certificates, service data right certificates, and verification certificates assigned to service data. The number of equipment data providing devices 10, conversion rule providing devices 20, and utilization devices 30 is not limited, and the information processing system 1 may include any number of equipment data providing devices 10, conversion rule providing devices 20, and utilization devices 30. The management device 100 will be described in detail later.

[0015] 2 is a diagram illustrating an example of a data flow according to an embodiment of the present disclosure. As shown in FIG. 2, when the management device 100 receives an instruction to start creating service data, the management device 100 acquires a concealed conversion rule 21 from the conversion rule providing device 20. The management device 100 issues a right certificate for the conversion rule 21 (included in right certificate 14 in FIG. 2) to the conversion rule providing device 20. The management device 100 acquires concealed device data 11 of a data type corresponding to the conversion rule 21 from the device data providing device 10. The management device 100 issues a right certificate for the device data 11 (included in right certificate 13 in FIG. 2) to the device data providing device 10.

[0016] Management device 100 generates service data 12 based on conversion rule 21 while keeping equipment data 11 confidential. Management device 100 also issues service data right certificates (included in right certificates 13 and 14, respectively, in FIG. 2 ) corresponding to service data 12 to equipment data providing device 10 and conversion rule providing device 20, respectively. Management device 100 transmits the service data with the verification certificate to usage device 30 of the data using organization. Usage device 30 pays data usage fees 15 and 16 to management device 100. Management device 100 pays data usage fees 15 and 16 to equipment data providing device 10 and conversion rule providing device 20, respectively, in accordance with the service data right certificates included in right certificates 13 and 14, respectively. 2, the data usage fees 15 and 16 are shown separately, but it is assumed that the using device 30 pays the data usage fees 15 and 16 together to the management device 100 and distributes them to the equipment data providing device 10 and the conversion rule providing device 20 in accordance with the rights allocation. The equipment data providing device 10 further distributes the data usage fee 15 paid to the equipment data providing organization to multiple users in accordance with the shares of the multiple users who provided the equipment data.

[0017] <<2. Flow of Rights Management Processing According to an Embodiment>> FIG. 3 is a flowchart showing an example of rights management processing according to an embodiment of the present disclosure. Note that the description of encryption is omitted in the description of FIG. 3 . As shown in FIG. 3 , in the information processing system 1, the management device 100 acquires a conversion rule from the conversion rule providing device 20 and issues a right certificate for the conversion rule to the conversion rule providing organization (step S1). At this time, the right certificate for the conversion rule may be configured to comply with the management method of the conversion rule management organization. The management device 100 analyzes the device data required by the conversion rule acquired from the conversion rule providing device 20 (step S2). The management device 100 issues a right certificate for the device data to the user who is the provider of the device data (step S3). At this time, the right certificate for the device data may be configured to comply with the management method of the device data management organization.

[0018] The management device 100 generates service data based on the analysis results of the device data required by the conversion rules (step S4). The management device 100 allocates rights to contributors to the generation of the service data, such as the conversion rule provider organization and the device data provider organization including the user, according to the degree of their contribution to the generation of the service data (step S5). The management device 100 also issues a service data rights certificate corresponding to the rights allocation.

[0019] When a service data user organization, i.e., a user, uses service data, the user device 30 pays a predetermined fee to the management device 100 (step S6). Payment of the fee can be made using various payment methods, including, but not limited to, electronic money, cryptocurrency, tokens, and points. The management device 100 distributes the paid fee to the contributors to the creation of the service data based on the rights allocation (step S7). Furthermore, if the user requests the return or deletion of the device data provided by the management device 100, the management device 100 returns or deletes the device data and deletes the corresponding rights certificate and rights allocation. That is, if there is a change in the rights allocation of the service data, the management device 100 updates each rights certificate (step S8). In this way, the management device 100 can execute various rights-related processes as a credential infrastructure.

[0020] 4 is a block diagram showing an example of the functional configuration of a management device according to an embodiment of the present disclosure. As shown in Fig. 4, the management device 100 includes a display unit 101, an operation unit 102, a communication unit 110, a storage unit 120, and a control unit 130. Examples of the management device 100 include a server and a personal computer.

[0021] The display unit 101 is a display device for displaying various types of information. The display unit 101 is realized, for example, by a liquid crystal display, an organic EL (Electro Luminescence) display, etc. The display unit 101 displays various screens, such as management screens for device data, conversion rules, service data, and various rights certificates.

[0022] The operation unit 102 is an input device that accepts various operations from an administrator who operates the management device 100. The operation unit 102 is realized, for example, by input devices such as a keyboard, a mouse, and a touch panel. The operation unit 102 accepts, for example, input of various setting information. Note that the display device of the display unit 101 and the input device of the operation unit 102 may be integrated, such as a display with a touch panel.

[0023] The communication unit 110 is realized, for example, by a network interface card (NIC) or a wireless local area network (LAN) such as Wi-Fi (registered trademark). The communication unit 110 is connected to the equipment data providing device 10, the conversion rule providing device 20, and the utilization device 30 via the network N, either wired or wirelessly, and is a communication interface that controls the communication of information among the equipment data providing device 10, the conversion rule providing device 20, and the utilization device 30. The communication unit 110 receives, for example, encrypted equipment data from the equipment data providing device 10. The communication unit 110 receives, for example, encrypted conversion rules from the conversion rule providing device 20. The communication unit 110 receives, for example, a data usage request and information on the data usage fee from the utilization device 30. The communication unit 110 also transmits, for example, a certificate of right for equipment data and information on the data usage fee to the equipment data providing device 10. The communication unit 110 transmits, for example, an analysis request, a right certificate for the conversion rule, information on the data usage fee, etc. to the conversion rule providing device 20. The communication unit 110 transmits, for example, a verification certificate, target data corresponding to the data usage request, billing information, etc. to the usage device 30.

[0024] The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM), a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 120 has a device data storage unit 121, a conversion rule storage unit 122, a service data storage unit 123, and a management information storage unit 124. The storage unit 120 also stores information (programs and data) used for processing by the control unit 130.

[0025] The device data storage unit 121 stores encrypted device data acquired from the device data providing device 10. The encrypted device data is data processed for secure computation (confidential computation) by, for example, secret sharing type multi-party computation (MPC) or the like together with the device data providing device 10 and the conversion rule providing device 20. In other words, the device data storage unit 121 shares a portion of the distributed device data with the device data providing device 10. In the following description, encryption may be referred to as distribution. Note that homomorphic encryption may be used for the secure computation.

[0026] The conversion rule storage unit 122 stores encrypted conversion rules acquired from the conversion rule providing device 20. The conversion rule storage unit 122 stores encrypted conversion rules in association with each of a plurality of conversion rule providing organizations. The encrypted conversion rules are data processed for secure computation (concealed computation) by, for example, a secret sharing MPC or the like together with the equipment data providing device 10 and the conversion rule providing device 20. In other words, the conversion rule storage unit 122 shares some of the distributed conversion rules with the conversion rule providing device 20. Note that homomorphic encryption may be used for the secure computation.

[0027] The service data storage unit 123 stores the generated service data. The service data is encrypted service data generated based on the encrypted (distributed) device data and the conversion rule.

[0028] The management information storage unit 124 stores management information for various certificates, such as issued device data right certificates, conversion rule right certificates, service data right certificates, and verification certificates assigned to service data, as well as compensation information and the results of distribution of compensation. The management information also includes an update history.

[0029] The control unit 130 is realized by, for example, a central processing unit (CPU) or a micro processing unit (MPU) executing a program stored in an internal storage device using a RAM as a work area. The control unit 130 may also be realized by, for example, an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0030] The control unit 130 has an acquisition unit 131, a generation unit 132, a management unit 133, and a distribution unit 134, and realizes or executes the functions and actions of the information processing described below. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in Fig. 4, and may be any other configuration that performs the information processing described below.

[0031] The acquisition unit 131 receives a request from the administrator to start creating service data or to change the conversion rules. Upon receiving this request, the acquisition unit 131 transmits a conversion rule analysis request to the conversion rule providing device 20 via the network N and the communication unit 110, and receives and acquires information on data types that require rule conversion from the conversion rule providing device 20. The acquisition unit 131 also transmits information on data types that require rule conversion to the equipment data providing device 10 via the network N and the communication unit 110, and receives and acquires a notification of completion of data provision preparation indicating that matching of data types has been completed.

[0032] Upon receiving the completion notification, the acquisition unit 131 accepts a selection of service data to be permitted to be created from the user. The acquisition unit 131 may accept the selection directly from the user or via the device data providing organization (device data providing device 10). The acquisition unit 131 may also acquire selection information from the user regarding whether or not to provide personally identifiable information. Upon accepting the selection of the service data, the acquisition unit 131 instructs the management unit 133 to start managing the service data and right certificate including the user's device data.

[0033] The acquisition unit 131 transmits a distribution request for the conversion rules to the conversion rule providing device 20 via the network N and the communication unit 110, and receives and acquires the rights related to the conversion rules of the conversion rule providing organization and the distributed conversion rules from the conversion rule providing device 20. The acquisition unit 131 stores the acquired rights related to the conversion rules of the conversion rule providing organization in the management information storage unit 124, and stores the distributed conversion rules in the conversion rule storage unit 122. The acquisition unit 131 also transmits a distribution request for the equipment data to the equipment data providing device 10 via the network N and the communication unit 110, and receives and acquires the rights related to the equipment data of the user who is the equipment user and the distributed equipment data from the equipment data providing device 10. The acquisition unit 131 stores the acquired rights related to the equipment data of the user in the management information storage unit 124, stores the distributed equipment data in the equipment data storage unit 121, and transmits it to the equipment data providing device 10.

[0034] When the acquisition unit 131 makes a request to distribute the equipment data and the conversion rules, the generation unit 132 performs secure computation (confidential computation) together with the equipment data providing device 10 and the conversion rule providing device 20 using a secret sharing MPC or the like. That is, the generation unit 132 generates some of the distributed equipment data and conversion rules. The generation unit 132 stores the data to be shared with the equipment data providing device 10 and the conversion rule providing device 20, respectively, in the equipment data storage unit 121 and the conversion rule storage unit 122.

[0035] When a generation instruction is input from management unit 133, generation unit 132 refers to device data storage unit 121 and conversion rule storage unit 122, and generates encrypted service data based on the distributed device data and the conversion rule. Generation unit 132 stores the generated service data in service data storage unit 123. After generating the service data, generation unit 132 outputs the amount of data provided by each user and used to generate the service data, and the data type, to management unit 133. Furthermore, when there are multiple service data using organizations, i.e., multiple user devices 30, generation unit 132 generates encrypted service data corresponding to the data usage requests received from each user device 30.

[0036] The management unit 133 generates and manages each right certificate. When the distributed device data is stored in the device data storage unit 121, the management unit 133 allocates the rights of the device data to the device data right certificate and the conversion rule right certificate. The management unit 133 stores each right certificate in the management information storage unit 124. Note that the device data right certificate includes the allocation of each user and the allocation of the device data provider organization. Furthermore, when the device data right certificate and the conversion rule right certificate are changed, the management unit 133 stores the change history (update history) in the management information storage unit 124. When the allocation of rights is completed, the management unit 133 outputs a generation instruction to the generation unit 132.

[0037] When the management unit 133 receives the data amount and data type provided by each user from the generation unit 132, it determines a rights allocation ratio based on the input data amount and data type provided by each user. That is, the management unit 133 determines the rights allocation of the fee for the use of the service data among each user, the device data provider organization, and the conversion rule provider organization. After determining the rights allocation ratio, the management unit 133 generates a service data rights certificate that can be verified by a third party and that identifies the device data provided by each user and the rights allocation. For example, a ZKP (Zero Knowledge Proof) can be used as the service data rights certificate. The management unit 133 stores the generated service data rights certificate in the management information storage unit 124. The service data rights certificate includes the rights allocation of the fee for the use of the service data among each user, the device data provider organization, and the conversion rule provider organization. The management unit 133 also stores and manages the change history (update history) of the service data rights certificate in the management information storage unit 124. The management unit 133 also generates a verification certificate to be attached to the service data. For example, ZKP or the like can be used for the verification certificate.

[0038] Here, rights allocation will be described using FIG. 5 . FIG. 5 is a diagram showing an example of rights allocation to generation contributors. As shown in FIG. 5 , generation contributors who contributed to the generation of service data include, for example, a conversion rule provider organization, a device data provider organization, and a device user (user). An example of rights allocation is a fixed allocation of 50% to the conversion rule provider organization, a fixed value of 10% to the device data provider organization, and a variable value of 40% to the device user. The variable value for the device user indicates that the rights allocation to each user varies depending on the number of users. For example, if there are two users, 40% is further allocated to two users, for example, 20% each. For example, if there are four users, 40% is further allocated to four users, for example, 10% each. The rights allocation among users may vary depending on the amount of data contributed. If there are no more service data rights allocators as a result of the change, the service data and rights certificate may be invalidated.

[0039] Next, the storage of change history will be described with reference to FIG. 6 . FIG. 6 is a diagram illustrating an example of management of change history of a right certificate of device data. As shown in FIG. 6 , the right certificate of device data is associated with a personal identifier (e.g., ID=xyz) of the user who provided the data. For example, if the conversion rule is changed and the data type used for the device data provided by the user is changed, the rights share of the right certificate of the device data is also changed, and the change history (update history) of the right certificate of the device data is stored in the device data storage unit 121. In this case, the change history may be managed using, for example, a blockchain (BC) to provide tamper resistance. Furthermore, the right certificate of device data may use a standard specification such as verifiable credential (VC). Furthermore, the identifier of the user, organization, etc. used in each right certificate may be, for example, a decentralized ID (DID) or a so-called digital wallet.

[0040] For each rights certificate, the change history is stored in the management information storage unit 124 as a change history (update history) using a blockchain each time a rights management event such as new creation (acquisition), deletion (waiver), update, addition, or use is detected. For each rights certificate, the change history of rights processing from the rights holder's perspective is managed in addition to the change history of the rights certificate itself by VC, etc., so that the rights certificate as an information asset is securely managed. The change history of rights processing may be stored in the rights certificate and managed in association with the rights certificate itself. Examples of rights management events include the acquisition of rights for service data, the update of service data, the loss or waiver of rights by a rights holder, updates to allocations between rights holders, and an increase or decrease in the number of rights holders.

[0041] An example of a rights management event is when a user requests the return or deletion of device data. In this case, the management unit 133 requests the device data providing device 10 to return or delete the device data based on the user's device data rights certificate. The device data providing device 10 returns or deletes the device data and notifies the management device 100 that the return or deletion of the device data has been completed. Upon receiving the notification that the return or deletion of the device data has been completed, the management unit 133 of the management device 100 deletes the user's service data rights certificate stored in the management information storage unit 124 and notifies the device data providing device 10 that the deletion of the user's service data rights certificate has been completed.

[0042] Returning to the explanation of FIG. 4 , the management unit 133 accepts a selection of service data that the service data user organization, i.e., the user's user device 30, desires to use. The management unit 133 does not disclose all of the service data, but instead proves to the user device 30 that it owns the target data by using, for example, a service data right certificate. When the management unit 133 accepts a data usage request from the user device 30, it provides the target service data corresponding to the data usage request to the user device 30. Note that, if the management unit 133 has acquired selection information from the user indicating whether or not to provide personally identifiable information, it may provide information about users whose selection information indicates that provision is permitted to the user device 30 along with the target service data.

[0043] The management unit 133 determines the price according to the service data right certificate and the usage history of the usage device 30. The management unit 133 bills the usage device 30 for the determined price for the target data. When the price is paid from the usage device 30, the management unit 133 associates the price information with the service data right certificate and stores it in the management information storage unit 124. When the management unit 133 stores the price information in the management information storage unit 124, it outputs a distribution instruction to the distribution unit 134.

[0044] When a distribution instruction is input from the management unit 133, the distribution unit 134 refers to the management information storage unit 124 and distributes a consideration (incentive) to the equipment data providing device 10 of the equipment data user organization based on the service data right certificate and the consideration information. The distribution unit 134 also distributes a consideration to the conversion rule providing device 20 of the conversion rule providing organization based on the service data right certificate and the consideration information. Note that when a distribution instruction is input from the management unit 133, the distribution unit 134 may automatically distribute these considerations using a smart contract. The distribution unit 134 stores the result of the distribution of the consideration in the management information storage unit 124.

[0045] <<4. Procedure of Information Processing According to the Embodiment>> Next, information processing according to the embodiment will be described with reference to Fig. 7 to Fig. 10. Fig. 7 is a sequence diagram showing an example of a process of combining conversion rules according to an embodiment of the present disclosure.

[0046] The acquisition unit 131 of the management device 100 receives from the administrator a request to start creating service data or a request to change a conversion rule (step S101). Upon receiving this request, the acquisition unit 131 transmits a request to the conversion rule providing device 20 to analyze the conversion rule (step S102).

[0047] When the conversion rule providing device 20 receives the analysis request from the management device 100, it analyzes the data types that require rule conversion, generates information on the data types that require rule conversion, and transmits it to the management device 100 (step S103).

[0048] The acquisition unit 131 of the management device 100 receives and acquires information on data types that require rule conversion from the conversion rule providing device 20, thereby sharing the information on data types that require rule conversion (step S104). The acquisition unit 131 transmits the information on data types that require rule conversion to the equipment data providing device 10, and performs matching between the data types that require rule conversion and the data types held by the equipment data providing organization (step S105).

[0049] The device data providing device 10 extracts data requiring rule-based conversion from the device data based on the received information on the data type requiring rule-based conversion (step S106). That is, the device data providing device 10 performs data type matching. The device data providing device 10 transmits a data provision preparation completion notification to the management device 100, indicating that the data type matching has been completed (step S107). The acquisition unit 131 of the management device 100 receives and acquires the data provision preparation completion notification from the device data providing device 10. The management device 100 may generate correlation data between the data type of the device data and the conversion rule based on the data type matching result. For example, if the data format of the device data is changed, the management device 100 may change (update) the association between the data type of the device data used for service data and the conversion rule based on the correlation data. This allows the management device 100 to associate the data type of the device data used for service data with the conversion rule.

[0050] FIG. 8 is a sequence diagram showing an example of a process for generating service data and a certificate of right according to an embodiment of the present disclosure.

[0051] The acquisition unit 131 of the management device 100 accepts a selection of service data that the user is permitted to create. Upon accepting the selection of the service data, the acquisition unit 131 instructs the management unit 133 to start managing the user's service data and right certificate. The management unit 133 starts managing the user's service data and right certificate (step S111). The acquisition unit 131 transmits a request to distribute the conversion rules to the conversion rule providing device 20 (step S112).

[0052] When the conversion rule providing device 20 receives a request to distribute the conversion rules, it notifies the management device 100 of the conversion rule providing organization's rights regarding the conversion rules (step S113), distributes the conversion rules, and transmits the distributed conversion rules to the management device 100 (step S114).

[0053] The acquisition unit 131 of the management device 100 receives and acquires the rights related to the conversion rules of the conversion rule provider organization and the decentralized conversion rules from the conversion rule providing device 20, thereby sharing the rights related to the conversion rules of the conversion rule provider organization and the decentralized conversion rules (step S115). After sharing the rights related to the conversion rules of the conversion rule provider organization and the decentralized conversion rules, the acquisition unit 131 transmits a distribution request for the equipment data to the equipment data providing device 10 (step S116).

[0054] The device data providing device 10 starts acquiring device data from the user through device use at any timing (step S117). When the device data providing device 10 receives a device data distribution request, it notifies the management device 100 of the user's rights to the device data (step S118), distributes the device data, and transmits the distributed device data to the management device 100 (step S119).

[0055] The acquisition unit 131 of the management device 100 shares the rights to the device data of the user who is the device user by receiving and acquiring the rights to the device data of the user who is the device user from the device data providing device 10. The acquisition unit 131 also shares the distributed device data by receiving and acquiring the distributed device data from the device data providing device 10 (step S120).

[0056] When the distributed device data is shared, the management unit 133 allocates the rights of the device data to each right certificate (step S121). Note that the device data distribution process of the device data providing device 10 and the device data right allocation process of the management unit 133 of the management device 100 to each right certificate may be performed simultaneously. When the allocation of rights is completed, the management unit 133 outputs a generation instruction to the generation unit 132.

[0057] When the generation instruction is input from the management unit 133, the generation unit 132 refers to the device data storage unit 121 and the conversion rule storage unit 122, and generates encrypted service data based on the distributed device data and the conversion rule (step S122). After generating the service data, the generation unit 132 outputs to the management unit 133 the amount of data provided by each user and used in generating the service data, and the data type.

[0058] When the management unit 133 receives the data amount and data type provided by each user from the generation unit 132, it determines the ratio of rights allocation based on the input data amount and data type provided by each user (step S123). After determining the ratio of rights allocation, the management unit 133 generates a service data right certificate that can be verified by a third party and that identifies the device data and rights allocation provided by each user (step S124). The management unit 133 also stores and manages the change history (update history) of the service data right certificate in the management information storage unit 124 (step S125). This allows the management device 100 to generate and manage service data and each right certificate.

[0059] FIG. 9 is a sequence diagram illustrating an example of a distribution process when service data is used according to an embodiment of the present disclosure.

[0060] The management unit 133 of the management device 100 accepts a selection of service data that the user device 30 of the service data user organization wishes to use (step S131). The management unit 133 certifies to the user device 30 that it owns the target data, for example, by using a service data right certificate, without disclosing all of the service data (step S132).

[0061] The use device 30 transmits a data usage request for data it wishes to use from among the service data to the management device 100. When the management unit 133 of the management device 100 receives the data usage request from the use device 30, it provides the use device 30 with target data corresponding to the data usage request (step S133). A verification certificate (a verification certificate attached to the service data) is attached to the target data.

[0062] The management unit 133 determines a price based on the service data right certificate and the usage history of the use device 30 (step S134). The management unit 133 bills the use device 30 for the determined price for the target data (step S135).

[0063] The utilization device 30 makes payment of the consideration to the management device 100 (step S136). Note that the utilization device 30 may make payment of the consideration to wallets (not shown) of the equipment data provider and the conversion rule provider.

[0064] When the consideration is paid from the use device 30, the management unit 133 of the management device 100 associates the consideration information with the service data right certificate and stores the associated information in the management information storage unit 124. After storing the consideration information in the management information storage unit 124, the management unit 133 outputs a distribution instruction to the distribution unit 134.

[0065] When the distribution instruction is input from the management unit 133, the distribution unit 134 refers to the management information storage unit 124 and distributes the consideration to the equipment data providing device 10 of the equipment data user organization based on the service data right certificate and the consideration information (step S137). The distribution unit 134 also distributes the consideration to the conversion rule providing device 20 of the conversion rule providing organization based on the service data right certificate and the consideration information (step S138). The distribution unit 134 stores the result of the distribution of the consideration in the management information storage unit 124. This allows the management device 100 to distribute the consideration according to the usage of the service data to the equipment data user organization and the conversion rule providing organization.

[0066] FIG. 10 is a sequence diagram illustrating an example of a deletion process when returning or deleting device data according to an embodiment of the present disclosure.

[0067] The management unit 133 of the management device 100 receives a request to return or delete device data from the user (step S141). Upon receiving the request to return or delete device data, the management unit 133 requests the device data providing device 10 to return or delete the device data based on the user's device data right certificate (step S142).

[0068] When the equipment data providing device 10 receives the request, it returns or deletes the equipment data of the user (step S143), and notifies the management device 100 of the completion of the return or deletion of the equipment data (step S144).

[0069] When the management unit 133 of the management device 100 is notified of the completion of the return or deletion of the equipment data, it deletes the service data right certificate of the user stored in the management information storage unit 124. The management unit 133 also notifies the equipment data providing device 10 of the completion of the deletion of the service data right certificate of the user (step S145). This allows the management device 100 to return or delete equipment data from any user.

[0070] <<5. Use Cases>> Next, use cases using the information processing system according to the embodiment of the present disclosure will be described with reference to Fig. 11 to Fig. 17. Note that the description of Fig. 11 to Fig. 17 omits the flow of payment of consideration.

[0071] FIG. 11 is a diagram illustrating an example of data flow in use case UC11. In use case UC11 illustrated in FIG. 11, the management device 100 acquires, as equipment data, data on a vehicle driver and vehicle as encrypted driving history. The management device 100 also acquires encrypted accident data conversion rules from an insurance company. The management device 100 generates encrypted service data, personal driving risk data, based on the encrypted driving history and the encrypted accident data conversion rules. The management device 100 accepts selections of service data that each wishes to use from, for example, a vehicle insurance company or a rental car insurance company, which are service data user organizations in the financial industry. The management device 100 provides certified data (personal driving risk data) as service data to the vehicle insurance company. The management device 100 also provides certified data (personal driving risk data) as service data to the rental car insurance company. The service data user organizations that receive the service data may be from different business types or industries.

[0072] Conventionally, depending on the recipient of service data, prior agreements on confidentiality and data management methods were required between the driver and the insurance company, making it difficult to capitalize driving history data. In contrast, in use case UC11, the management device 100 can manage personal driving risk data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the accident data conversion rules. Furthermore, even if the data format of the confidential driving history data is changed, the management device 100 can match data types using the accident data conversion rules, thereby generating personal driving risk data. The management device 100 may also acquire selection information from users regarding whether or not to provide personally identifiable information, and provide information on users who select "yes" to provide information along with service data to the service data user organization. In this case, the management device 100 can realize a single process, from providing the driver's driving history to receiving compensation, such as a reduction in automobile insurance premiums.

[0073] FIG. 12 is a diagram illustrating an example of data flow in use case UC12. In use case UC12 illustrated in FIG. 12, the management device 100 acquires, as equipment data, data on a vehicle driver and vehicle as encrypted driving history. The management device 100 also acquires encrypted driving skill conversion rules from an automobile company. The management device 100 generates encrypted service data, personal driving skill data, based on the encrypted driving history and the encrypted driving skill conversion rules. The management device 100 accepts selections of service data that each wishes to use from, for example, a taxi company or a delivery company, which are service data user organizations in the transportation industry. The management device 100 provides certified data (personal driving skill data) as service data to the taxi company. The management device 100 also provides certified data (personal driving skill data) as service data to the delivery company. The service data user organizations receiving the service data may be from different business types or industries.

[0074] Conventionally, depending on the recipient of service data, prior agreements on confidentiality and data management methods were required between the driver and the automobile company, making it difficult to capitalize driving history data. In contrast, in use case UC12, the management device 100 can manage personal driving skill data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the driving skill conversion rules. Furthermore, even if the data format of the confidential driving history data is changed, the management device 100 can match data types using the driving skill conversion rules, thereby generating personal driving skill data. The management device 100 may also acquire selection information from users regarding whether or not to provide personally identifiable information, and provide information on users whose selection information indicates that they are willing to provide information to the service data user organization along with the service data. In this case, the management device 100 can realize a single process, from providing the driver's driving history to receiving compensation, such as a usage fee.

[0075] FIG. 13 is a diagram illustrating an example of data flow in use case UC13. In use case UC13 illustrated in FIG. 13, the management device 100 acquires, as device data, the user's biometric information and data from the biometric information acquisition device as encrypted biometric information. The management device 100 also acquires an encrypted disease data conversion rule from a medical examination institution. The management device 100 generates encrypted service data, personal healthcare data, based on the encrypted biometric information and the encrypted disease data conversion rule. The management device 100 accepts selections of service data that each wishes to use from, for example, a medical institution or a healthcare product sales company, which are service data user organizations in the healthcare industry. The management device 100 provides certified data (personal healthcare data) as service data to the medical institution. The management device 100 also provides certified data (personal healthcare data) as service data to the healthcare product sales company. The service data user organizations that receive the service data may be from different business types or industries.

[0076] Conventionally, depending on the recipient of service data, prior agreement on confidentiality and data management methods was required between the user and the medical examination institution, making it difficult to capitalize biometric information. In contrast, in use case UC13, the management device 100 can manage personal healthcare data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the disease data conversion rules. Furthermore, even if the data format of confidential biometric information is changed, the management device 100 can match data types using the disease data conversion rules, thereby generating personal healthcare data. The management device 100 may also acquire selection information from the user indicating whether or not to provide personally identifiable information, and provide information on users who select "yes" to provide information to the service data user organization along with service data. In this case, the management device 100 can realize a single process, from providing the user's biometric information to receiving compensation, such as a discount on the test fee.

[0077] FIG. 14 illustrates an example of data flow in use case UC21. In use case UC21 illustrated in FIG. 14, the management device 100 acquires device data, such as driver and vehicle data for multiple automobiles, as encrypted wiper data. The management device 100 also acquires encrypted weather forecast conversion rules from a weather forecasting company. The management device 100 generates specific location / time weather data as encrypted service data based on the encrypted wiper data and the encrypted weather forecast conversion rules. The management device 100 accepts selections of service data that each wishes to use from service data users in the weather forecasting industry, such as local governments, road management companies, and weather forecasting companies. The management device 100 provides certified data (specific location / time weather data) as service data to local governments and road management companies. The management device 100 also provides certified data (specific location / time weather data) as service data to weather forecasting companies. The service data users receiving the service data may be from different business types or industries.

[0078] In the past, depending on the recipient of the service data, prior agreements on confidentiality and data management methods were required between the driver and the weather forecast company, making it difficult to capitalize wiper data. In contrast, in use case UC21, the management device 100 can manage specific location / time weather data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the weather forecast conversion rules. Furthermore, even if the data format of the confidential wiper data is changed, the management device 100 can match data types using the weather forecast conversion rules, thereby generating specific location / time weather data.

[0079] FIG. 15 illustrates an example of data flow in use case UC22. In use case UC22 illustrated in FIG. 15, the management device 100 acquires encrypted vehicle image data representing the drivers and vehicles of multiple automobiles as equipment data. The vehicle image data may be, for example, still or moving images captured by an imaging device installed in each vehicle. The management device 100 also acquires encrypted matching rules from the automobile manufacturer. The management device 100 generates specific location video data as encrypted service data based on the encrypted vehicle image data and the encrypted matching rules. The management device 100 receives selections of service data from automobile owners α and β, who are service data user organizations in the automobile industry. The management device 100 provides certified data (specific location video data) as service data for automobile owner α. The management device 100 also provides certified data (specific location video data) as service data for automobile owner β. The service data user organizations receiving the service data may be from different business types or industries.

[0080] In the past, depending on the recipient of the service data, prior agreements on confidentiality and data management methods were required between the driver and the automobile company, making it difficult to capitalize vehicle image data. In contrast, in use case UC22, the management device 100 can manage specific location image data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the matching rules. Furthermore, even if the data format of the confidential vehicle image data is changed, the management device 100 can match data types using the matching rules, thereby generating specific location image data.

[0081] FIG. 16 illustrates an example of data flow in use case UC23. In use case UC23 illustrated in FIG. 16, the management device 100 acquires device data, including data on multiple users and image capture devices, as encrypted location information and image capture data. The image capture data may be, for example, still images or video captured by each image capture device. The management device 100 also acquires encrypted people flow data conversion rules from government ministries and agencies or local governments. The management device 100 generates person analysis data as encrypted service data based on the encrypted location information and image capture data and the encrypted people flow data conversion rules. The management device 100 accepts selections of service data that each of stores A and B, which are service data users in the retail industry, wants to use. Store A uses service data related to product lineups, and store B uses service data related to advertising. The management device 100 provides certified data (person analysis data) as service data to store A. Furthermore, the management device 100 provides the certificate-attached data (person analysis data) as service data to the store B. The service data using organizations that receive the service data may be in different business types or industries.

[0082] In the past, depending on the destination of service data, prior agreements on confidentiality and data management methods were required between users and government ministries and local governments, making it difficult to capitalize location information and photography data. In contrast, in use case UC23, the management device 100 can manage person analysis data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to people flow data conversion rules. Furthermore, even if the data format of confidential location information and photography data is changed, the management device 100 can match data types using the people flow data conversion rules, thereby generating person analysis data.

[0083] FIG. 17 is a diagram illustrating an example of data flow in use case UC24. In use case UC24 illustrated in FIG. 17 , the management device 100 acquires encrypted power data representing the power consumption of multiple users and their homes as device data. The power data may represent, for example, hourly power consumption. The management device 100 also acquires encrypted presence-at-home information conversion rules from a power company. The management device 100 generates encrypted service data, called home analysis data, based on the encrypted power data and the encrypted presence-at-home information conversion rules. The management device 100 accepts selections of service data from service data users in different industries, such as a transportation company and a hospital. The transportation company uses service data related to delivery, while the hospital uses service data related to emergency care in a certain area and service data related to monitoring of home medical patients. The management device 100 provides certified data (home analysis data) as service data to the transportation company. The management device 100 also provides the certified data (home analysis data) as service data to the hospital. The service data user organizations that receive the service data may be in different industries.

[0084] In the past, depending on the recipient of the service data, prior agreement on confidentiality and data management methods was required between the user and the electric power company, making it difficult to capitalize power data. In contrast, in use case UC24, the management device 100 can manage home analysis data as an asset. Furthermore, the management device 100 can dynamically allocate rights in response to updates to the presence-at-home information conversion rules. Furthermore, even if the data format of the confidential power data is changed, the management device 100 can match data types using the presence-at-home information conversion rules, thereby generating home analysis data.

[0085] <<6. Modifications of the Embodiment>> The processing according to the embodiment described above may be implemented in various different forms other than the above embodiment.

[0086] In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0087] Furthermore, the components of each device shown in the figure are conceptual functional units and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of the devices can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc. For example, in the management device 100, the functions of the management unit 133 for accepting data use requests, providing target data, and determining the allocation of fees may be distributed.

[0088] Furthermore, the above-described embodiments and modifications can be combined as appropriate within the scope of not causing any contradiction in the processing content.

[0089] <<7. Hardware Configuration>> Information devices such as the management device 100 according to each of the above-described embodiments are realized by a computer 1000 having a configuration such as that shown in FIG. 18, for example. The following description will be given using the management device 100, which is an information processing device according to the embodiments, as an example. FIG. 18 is a hardware configuration diagram showing an example of a computer that realizes the functions of the information processing device. The computer 1000 has a CPU 1100, a RAM 1200, a ROM (Read Only Memory) 1300, a HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input / output interface 1600. The components of the computer 1000 are connected by a bus 1050.

[0090] The CPU 1100 operates and controls each component based on programs stored in the ROM 1300 or the HDD 1400. For example, the CPU 1100 loads the programs stored in the ROM 1300 or the HDD 1400 into the RAM 1200 and executes processing corresponding to the various programs.

[0091] The ROM 1300 stores boot programs such as a Basic Input Output System (BIOS) that is executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000 .

[0092] HDD 1400 is a computer-readable recording medium that non-temporarily records programs executed by CPU 1100 and data used by such programs. Specifically, HDD 1400 is a recording medium that records an information processing program according to the present disclosure, which is an example of program data 1450.

[0093] The communication interface 1500 is an interface for connecting the computer 1000 to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data generated by the CPU 1100 to other devices via the communication interface 1500.

[0094] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the CPU 1100 receives data from an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 also transmits data to an output device such as a display, a speaker, or a printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs and the like recorded on a predetermined recording medium. Examples of media include optical recording media such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), magneto-optical recording media such as an MO (Magneto-Optical Disk), tape media, magnetic recording media, and semiconductor memories.

[0095] For example, when the computer 1000 functions as the management device 100 according to the embodiment, the CPU 1100 of the computer 1000 executes an information processing program loaded onto the RAM 1200 to realize functions such as the acquisition unit 131. The information processing program according to the present disclosure and data such as the device data storage unit 121 are stored in the HDD 1400. The CPU 1100 reads and executes the program data 1450 from the HDD 1400, but as another example, the CPU 1100 may acquire these programs from another device via an external network 1550.

[0096] <<8. Effects>> The information processing device (management device 100) includes an acquisition unit 131, a generation unit 132, and a management unit 133. The acquisition unit 131 acquires encrypted device data of a device used by a user and an encrypted first conversion rule for converting the device data in accordance with the first rule from a first provider. The generation unit 132 generates encrypted first conversion data based on the acquired device data and first conversion rule. The management unit 133 associates the generated first conversion data with the user and the first provider, and manages the use and compensation of the first conversion data. As a result, the user's device data and the conversion rule can be combined in a confidential state and utilized as personal information assets.

[0097] When the management unit 133 receives a data usage request from the first user, it provides the first user with target data corresponding to the data usage request from the first converted data, thereby enabling the first user, who is a service using organization, to be provided with the data that he or she desires to use.

[0098] The management unit 133 determines the allocation of the fee received from the first user to the user and the first provider based on the provided target data. As a result, it is possible to determine the allocation of the fee according to the use of the target data to be distributed to the device data provider organization and the first provider, which is the conversion rule provider organization related to the user.

[0099] The management unit 133 manages the compensation allocation history in association with the user and the first provider, thereby recording the compensation allocation history for each of the user and the first provider.

[0100] The acquisition unit 131 acquires, from a second provider, an encrypted second conversion rule for converting device data in accordance with the second rule. As a result, multiple conversion rules acquired from multiple conversion rule providers can be used. Furthermore, device data and conversion rules can be dynamically combined.

[0101] The generating unit 132 generates encrypted second conversion data based on the device data and the second conversion rule, thereby providing target data corresponding to a plurality of conversion rules obtained from a plurality of conversion rule providers.

[0102] The management unit 133 associates the generated second conversion data with the user and the second provider, and manages the use and value of the second conversion data. As a result, the user's device data can be combined with multiple conversion rules in a confidential state and utilized as personal information assets.

[0103] When the management unit 133 receives a data usage request from the second user, it provides the second user with the target data corresponding to the data usage request from the second converted data. As a result, it is possible to provide each of the data that a plurality of service user organizations desire to use.

[0104] The management unit 133 determines the allocation of the fee received from the second user to the user and the second provider based on the provided target data. As a result, the fee for the use of the service data received from the plurality of service user organizations can be distributed to the device data user organizations and the plurality of conversion rule provider organizations related to the user.

[0105] The generating unit 132 generates at least one of the first converted data and the second converted data in response to a data usage request received from at least one of the first user and the second user, thereby providing data that one or more service user organizations want to use.

[0106] The device data is acquired from a device used by one user, and as a result, target data corresponding to the device data of the user can be provided.

[0107] The device data is acquired from a plurality of devices used by a plurality of users, respectively, and as a result, target data that reflects the device data of each of the plurality of users can be provided.

[0108] The first user and the second user are in different industries, and as a result, data can be provided to a wider range of users.

[0109] The information processing device further includes a distribution unit 134 that distributes the compensation to the user and the first provider according to the determined distribution. As a result, the compensation according to the use of the target data can be distributed to the first provider, which is the device data provider organization and the conversion rule provider organization associated with the user.

[0110] The acquisition unit 131 acquires selection information from the user indicating whether or not to provide personally identifiable information. The management unit 133 provides the information of the user whose selection information indicates that the information is available to the first user together with the target data. As a result, a series of processes can be realized, from the provision of the user's device data to the receipt of compensation that benefits the user at the service user organization.

[0111] The effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0112] The present disclosure may also be configured as follows. (1) An information processing device having: an acquisition unit that acquires encrypted device data of a device used by a user and an encrypted first conversion rule for converting the device data in accordance with a first rule from a first provider; a generation unit that generates encrypted first converted data based on the acquired device data and the first conversion rule; and a management unit that associates the generated first converted data with the user and the first provider and manages the use and compensation of the first converted data. (2) The information processing device described in (1), in which, upon receiving a data usage request from a first user, the management unit provides the first user with target data from the first converted data that corresponds to the data usage request. (3) The information processing device described in (2), in which the management unit determines an allocation of compensation received from the first user to the user and the first provider based on the provided target data. (4) The information processing device according to (3), wherein the management unit manages the distribution history of the consideration in association with the user and the first provider. (5) The information processing device according to any one of (2) to (4), wherein the acquisition unit acquires, from a second provider, an encrypted second conversion rule for converting the equipment data in accordance with a second rule. (6) The information processing device according to (5), wherein the generation unit generates encrypted second converted data based on the equipment data and the second conversion rule. (7) The information processing device according to (6), wherein the management unit associates the generated second converted data with the user and the second provider and manages the use and consideration of the second converted data. (8) The information processing device according to (6) or (7), wherein, upon receiving a data usage request from a second user, the management unit provides target data of the second converted data corresponding to the data usage request to the second user. (9) The information processing device according to (8), wherein the management unit determines an allocation of a fee obtained from the second user to the user and the second provider based on the provided target data.(10) The information processing device according to (8), wherein the generation unit generates at least one of the corresponding first converted data and the second converted data in response to the data use request received from at least one of the first user and the second user. (11) The information processing device according to any one of (1) to (10), wherein the device data is acquired from the device used by one of the users. (12) The information processing device according to any one of (1) to (10), wherein the device data is acquired from a plurality of the devices used by a plurality of the users respectively. (13) The information processing device according to any one of (8) to (10), wherein the first user and the second user are users in different industries. (14) The information processing device according to (3) or (4), further comprising a distribution unit that distributes the consideration to the user and the first provider in accordance with the determined distribution. (15) The information processing device according to any one of (2) to (4), wherein the acquisition unit acquires selection information indicating whether or not to provide personally identifiable information from the user, and the management unit provides information of the user for whom the selection information indicates that provision is permitted to the first user together with the target data. (16) An information processing method in which a computer executes processes of: acquiring encrypted device data of a device used by a user and an encrypted first conversion rule for converting the device data in accordance with a first rule from a first provider, generating encrypted first converted data based on the acquired device data and the first conversion rule, and associating the generated first converted data with the user and the first provider to manage use and compensation of the first converted data. (17) An information processing program that causes a computer to execute the following process: acquiring encrypted device data of a device used by a user and an encrypted first conversion rule that converts the device data in accordance with a first rule from a first provider; generating encrypted first conversion data based on the acquired device data and the first conversion rule; associating the generated first conversion data with the user and the first provider, and managing the use and compensation of the first conversion data.

[0113] REFERENCE SIGNS LIST 1 Information processing system 10 Equipment data providing device 20 Conversion rule providing device 30 Use device 100 Management device 101 Display unit 102 Operation unit 110 Communication unit 120 Storage unit 121 Equipment data storage unit 122 Conversion rule storage unit 123 Service data storage unit 124 Management information storage unit 130 Control unit 131 Acquisition unit 132 Generation unit 133 Management unit 134 Distribution unit N Network

Claims

1. An information processing device having: an acquisition unit that acquires encrypted device data of a device used by a user and an encrypted first conversion rule that converts the device data in accordance with a first rule from a first provider; a generation unit that generates encrypted first conversion data based on the acquired device data and the first conversion rule; and a management unit that associates the generated first conversion data with the user and the first provider, and manages the use and compensation of the first conversion data.

2. The information processing device according to claim 1, wherein, when the management unit receives a data usage request from a first user, it provides the first user with target data from the first converted data that corresponds to the data usage request.

3. The information processing device according to claim 2, wherein the management unit determines an allocation of the compensation obtained from the first user to the user and the first provider based on the provided target data.

4. The information processing device according to claim 3, wherein the management unit manages the distribution history of the consideration in association with the user and the first provider.

5. The information processing device according to claim 2, wherein the acquisition unit acquires, from a second provider, an encrypted second conversion rule for converting the device data in accordance with the second rule.

6. The information processing device according to claim 5, wherein the generation unit generates encrypted second converted data based on the device data and the second conversion rule.

7. The information processing device according to claim 6, wherein the management unit associates the generated second converted data with the user and the second provider, and manages the use and compensation of the second converted data.

8. The information processing device according to claim 6, wherein, when the management unit receives a data usage request from a second user, the management unit provides the second user with target data from the second converted data that corresponds to the data usage request.

9. The information processing device according to claim 8, wherein the management unit determines an allocation of the compensation obtained from the second user to the user and the second provider based on the provided target data.

10. The information processing device according to claim 8, wherein the generation unit generates at least one of the corresponding first converted data and the second converted data in response to the data usage request received from at least one of the first user and the second user.

11. The information processing device according to claim 1, wherein the device data is acquired from the device used by one of the users.

12. The information processing device according to claim 1, wherein the device data is acquired from a plurality of the devices used by a plurality of the users, respectively.

13. The information processing device according to claim 8, wherein the first user and the second user are users in different industries.

14. The information processing device according to claim 3, further comprising a distribution unit that distributes the compensation to the user and the first provider in accordance with the determined allocation.

15. The information processing device of claim 2, wherein the acquisition unit acquires selection information from the user regarding whether or not to provide personally identifiable information, and the management unit provides information of the user for which the selection information is yes to provide information to the first user together with the target data.

16. An information processing method in which a computer executes the following processes: acquiring encrypted device data of a device used by a user and an encrypted first conversion rule for converting the device data in accordance with a first rule from a first provider; generating encrypted first conversion data based on the acquired device data and the first conversion rule; and associating the generated first conversion data with the user and the first provider, and managing the use and compensation of the first conversion data.

17. An information processing program that causes a computer to execute the following process: acquiring encrypted device data of a device used by a user and an encrypted first conversion rule that converts the device data in accordance with a first rule from a first provider; generating encrypted first conversion data based on the acquired device data and the first conversion rule; and associating the generated first conversion data with the user and the first provider, and managing the use and compensation of the first conversion data.

Images