Patent Description:
Patent document <NUM> discloses an attribute-based key management system wherein a data encryption key used to encrypt data is encrypted using a first asymmetric key and a policy. The policy includes rules that correspond to attributes. A second asymmetric key is associated with the attributes. To decrypt the encrypted data encryption key, the attributes are used to identify the second asymmetric key. The attributes are also used to pass the rules in the policy included in the encrypted data encryption key. If the attributes pass the rules in the policy, the encrypted data encryption key is decrypted. The decrypted data encryption key can then decrypt the encrypted data.

In an electronic commerce service provided on the Internet, there is a technology of statistically analyzing personal information of a user such as a gender, an address and transaction information by a service provider for the purpose of the marketing and the like not only using the data possessed by the company but also utilizing data outside the company. For example, Patent document <NUM> discloses an electronic commerce system wherein a service provider can obtain analysis of transaction histories without obtaining personal information of users.

However, in the system described in Patent document <NUM>, a service providing server which wants to perform the statistical analysis transmits an encryption key to all other service providing servers so that the other service providing servers encrypt the data by using the transmitted encryption key and transmit the encrypted data to the server of a third party organization which performs the statistical analysis. Since the data possessed by the other service providing servers is encrypted by the encryption key of the others, the other service providing servers should fear the possibility of the occurrence of problems in information security such as information leakage and illegal use.

Accordingly, the present disclosure is made for solving the above described problems and the purpose of the present disclosure is to provide a data sharing system capable of utilizing the data possessed by various companies safely without disclosing the details of the data to the other companies.

In order to achieve the above described purpose, according to a first aspect of the present invention there is provided a data sharing system according to claim <NUM>.

In order to achieve the above described purpose, according to a second aspect of the present invention there is provided a data sharing method according to claim <NUM>.

Furthermore, in order to achieve the above described purpose, according to a third aspect of the present invention there is provided a data sharing program according to claim <NUM>.

By using the present disclosure, in the data sharing system, the data possessed by various companies can be utilized safely without disclosing the details of the data to the other companies.

Hereafter, the embodiments of the present disclosure will be explained with reference to the drawings. In all drawings explaining the embodiments, the same reference signs are assigned to the common component to omit the repeated explanation. Note that the following embodiments do not unreasonably limit the content of the present disclosure described in the claims. In addition, all components disclosed in the embodiments are not necessarily essential components of the present disclosure. The scope of the invention is defined by the independent claims.

In recent years, the number of the organizations who possess a large amount of sensitive data such as customer information has been increased. Because of this, it has been spread that the cloud service for performing statistical analysis processing and the like using not only the sensitive data possessed by own organization but also the sensitive data possessed by the other organizations to find new knowledge on business and connect it to new service. However, when using the sensitive data, security should be considered, privacy should be protected and extreme care should be paid when treating the data. Thus, it is required to execute the data processing such as retrieval (search), tabulation analysis and statistics while preventing the information leakage of the sensitive data possessed by own organization.

Accordingly, in the data sharing system of the present invention, the sensitive data provided from the organization or the like joined in the system is encrypted by a predetermined encryption scheme (the encryption scheme where the calculation including retrieval, analysis and the like can be performed in the encrypted state) and the data processing is executed while the key used for encryption and decryption is managed in each organization which provides the sensitive data. Consequently, the sensitive data possessed by own organization and the decryption processing of the execution result of the data processing related to the sensitive data can be managed in own organization. Thus, the sensitive data can be utilized safely without unintentionally disclosing the detailed content of the sensitive data to the other organizations.

<FIG> is a drawing showing a configuration of a data sharing system <NUM> of the present embodiment. With reference to <FIG>, the configuration of the data sharing system <NUM> of the embodiment <NUM> will be explained.

The data sharing system <NUM> includes data providing servers <NUM>-<NUM>, <NUM>-<NUM>, ---, <NUM>-N (N is natural number), a management server <NUM>, a common database <NUM> and a terminal device <NUM> and they are communicatively connected with each other via a network NW. The network NW is, for example, WAN (Wide Area Network), LAN (Local Area Network), optical line network, intranet or the like. The network NW can be comprised of arbitrary network. The data sharing system <NUM> is a platform that enables each of the organizations joined in the system to use the data possessed by each of the organizations without disclosing the detailed contents of the data to the other organizations. Note that the organization is not limited to a company and a party. The organization can be a department, a division, a group, a team and the like divided according to the role.

In the following explanation, the data providing servers <NUM>-<NUM>, <NUM>-<NUM>, ---, <NUM>-N are referred to as a data providing server <NUM> unless it is necessary to distinguish them with each other. In the present embodiment, the common database <NUM> is connected with the management server <NUM> via the network NW. However, the configuration is not limited to this. The common database <NUM> can be locally connected with the management server <NUM>.

The data providing server <NUM> is associated with the organization joined in the platform. The data providing server <NUM> encrypts the sensitive data possessed by the organization and transmits the encrypted data to the management server <NUM>. In <FIG>, the data providing server <NUM>-<NUM> is associated with "company A," the data providing server <NUM>-<NUM> is associated with "company B" and the data providing server <NUM>-N is associated with "company X," for example.

The sensitive data includes attribute values of each attribute item (column). The data providing server <NUM> transmits the sensitive data in which at least a part of the attribute values is encrypted to the management server <NUM>. The data structure of the sensitive data will be described later. Furthermore, the data providing server <NUM> can store and manage an encryption key and a decryption key in own server (data providing server <NUM>). Otherwise, the data providing server <NUM> can store and manage them in another information processing device (e.g., the management can be entrusted to KSM: Key Management Service).

The management server <NUM> generates an integrated data by integrating the encrypted sensitive data obtained from each of the data providing servers <NUM> based on an identifier which is included in the sensitive data as one of the attribute items and stores the integrated data in the common database <NUM>. Furthermore, the management server <NUM> executes the data processing of the integrated data in the encrypted state according to a processing request of the data processing processed to the integrated data stored in the common database. Then, the management server <NUM> transmits a processing request of a decryption processing to the data providing server <NUM> from which the sensitive data including the attribute item of the data processing is provided for requesting the data providing server <NUM> to decrypt the encrypted execution result.

As described above, the common database <NUM> stores the integrated data generated in the management server <NUM>. Although the management server <NUM> generates the integrated data in the present embodiment, it is also possible to generate the integrated data in another information processing device or the like instead of the management server <NUM>.

The terminal device <NUM> is an information processing device used by a user of the data sharing system <NUM>. For example, the terminal device <NUM> is a PC (Personal Computer), a smartphone or a tablet terminal. In addition, the terminal device <NUM> can be wearable terminals such as a head mount display and the like or AR (Augmented Reality)/VR (Virtual Reality)/MR (Mixed Reality) devices. Note that the user can be an employee of the organization (e.g., company A) that joins the platform and provides the sensitive data, for example. In this case, the terminal device <NUM> can be configured to be linked with the data providing server <NUM> of the organization to which the user belongs.

The terminal device <NUM> transmits the processing request of the data processing to the management server <NUM> wherein the data processing is targeted at the integrated data stored in the common database <NUM>. The data processing includes a retrieval/tabulation processing and/or a statistical processing, for example. In addition, the data processing can include the processing of integrating the sensitive data. The processing request of the data processing is written by CLI (Command Line Interface) such as SQL statement or GUI (Graphical User Interface).

Hereafter, the functional configuration and the processing of each of the servers and the like constituting the above described data sharing system <NUM> will be explained. Note that the functional block and the processing block indicating each of the functional configurations can be achieved by a distribution group of one or a plurality of devices, computer processors and the computer processors.

<FIG> is the functional block diagram showing an example of the functional configuration of the data providing server <NUM>. With reference to <FIG>, an example of the functional configuration of the data providing server <NUM> will be explained.

The data providing server <NUM> includes a communication unit <NUM>, a control unit <NUM>, a storage unit <NUM>, a key management unit <NUM>, an encryption unit <NUM> and a decryption unit <NUM>.

The communication unit <NUM> includes a communication interface circuit so that the data providing server <NUM> establishes the communication with the servers and the devices via a network NW according to a predetermined communication protocol. The predetermined communication protocol is TCP/IP (Transmission Control Protocol/Internet Protocol), for example. The communication unit <NUM> transmits the received data to the control unit <NUM> and transmits the data received from the control unit <NUM> to the servers and the devices via the network NW. The communication unit <NUM> can also transmit and receive the data to/from the functional blocks other than the control unit <NUM> in the data providing server <NUM>. Note that the communication unit <NUM> transmits and receives the data to/from the devices connected via the network NW, the devices connected locally and the like using a secure communication channel where security is ensured. The explanation of the method for constructing the secure communication channel and the communication method is omitted since they are well known technology using a common key (e.g., session key), a public key and the like.

The communication unit <NUM> corresponds to the sensitive data acquisition unit. For example, the communication unit <NUM> acquires the sensitive data possessed by the organization from the organization joined in the platform. In <FIG>, the data providing server <NUM>-<NUM> associated with the company A can acquire the sensitive data from the terminal device <NUM> operated by the employee of the company A. In the present embodiment, the sensitive data is the information about an individual, for example. The sensitive data is the attribute value (string or numerical value) of the attribute item (column) which is the item indicating the attribute of the individual such as an age, a gender, an income, a residential area and a purchase information. In addition, the sensitive data includes the identifier (string, numerical value or combination of them) as one of the attribute items. The identifier functions as an integrated key for generating the integrated data. A common ID or the like for uniquely identifying the individual can be used as the identifier. The sensitive data is integrated based on the identifier to generate the integrated data. The sensitive data is not limited to the information about the individual. The sensitive data can be log data related to the device, for example. The details of the sensitive data and the details of the data structure of the sensitive data and will be described later.

The control unit <NUM> controls the functions of the data providing server <NUM>. The control unit <NUM> is a processor such as a CPU (Control Processing Unit) operated based on the programs preliminarily stored in the storage unit <NUM>. Note that a DSP (Digital Signal Processor) or the like can be used as the control unit <NUM>. In addition, the control circuit such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit) and an FPGA (Field-Programming Gate Array) can be used as the control unit <NUM>.

The control unit <NUM> controls the encryption unit <NUM> to encrypt the sensitive data obtained via the communication unit <NUM>. In addition, the control unit <NUM> controls the decryption unit <NUM> to decrypt the execution result of the data processing obtained via the communication unit <NUM>.

In addition, the control unit <NUM> can judge whether or not to decrypt the execution result in response to the inquiry transmitted from the management server <NUM>. For example, the control unit <NUM> can judge whether or not to decrypt the execution result based on whether or not the terminal device from which the processing request of the data processing is transmitted has the authority to use the execution result, for example. When the control unit <NUM> judges that the terminal device has the authority, the control unit <NUM> transmits a permission response to the management server <NUM> via the communication unit <NUM>. Thus, the control unit <NUM> controls the decryption unit <NUM> to decrypt the execution result transmitted from the management server <NUM>.

The storage unit <NUM> includes a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk drive or a portable disk device such as a flexible disk and an optical disc, for example. In addition, the storage unit <NUM> stores computer programs, database, tables, keys and the like used for various processing of the data providing server <NUM>. The computer programs can be installed in the storage unit <NUM> from a portable computer-readable recording medium using a conventionally known setup program, for example. The portable recording medium can be a CD-ROM (Compact Disc Read Only Memory) and a DVD-ROM (Digital Versatile Disc Read Only Memory), for example. The computer programs can be installed from a predetermined server, for example.

The storage unit <NUM> stores the encrypted sensitive data, the decrypted execution result of the data processing and the later described encryption key and decryption key managed by the key management unit <NUM>, for example.

The key management unit <NUM> manages the encryption key and the decryption key. The key management unit <NUM> can generate the key corresponding to the encryption scheme requested by the encryption unit <NUM>, for example. For example, when the encryption scheme is the (additive) homomorphic encryption scheme (Paillier method) where addition and subtraction can be performed in the encrypted state, a group of a public key (encryption key) and a secret key (decryption key) is generated.

When the encryption scheme is an order-preserving encryption scheme (OPE scheme: Order Preserving Encryption) where the magnitude relation is not changed between the encrypted text and the plaintext or a retrievable encryption scheme where the coincidence of the plaintext can be judged in the encrypted state, the secret key (common key) is generated. As described above, the encryption key and the decryption key can be different keys such as the public key and the secret key in some cases, although they can be the same key such as the common key in other cases. Note that the explanation of key generation algorithm is omitted since the key generation algorithm is conventionally known technology.

The key management unit <NUM> stores the generated key, parameters for generating the key and the like in the storage unit <NUM>, for example. The key management unit <NUM> manages the generated key, the encryption scheme, the identification of the data (e.g., attribute item, column) to which the encryption is performed and the like in association with each other.

The encryption unit <NUM> encrypts at least a part of the attribute values of the sensitive data obtained by the communication unit <NUM> by the predetermined encryption scheme. The predetermined encryption scheme includes the encryption scheme that is capable of performing the calculation of at least a part of the attribute values of the sensitive data obtained by the communication unit <NUM> in the encrypted state. For example, the predetermined encryption scheme can be a homomorphic encryption scheme, an order-preserving encryption scheme, AES (Advanced Encryption Standard), DES (Data Encryption Standard), the retrievable encryption, SHA (Secure Hash Algorithm), MD5 (Message Digest algorithm <NUM>) and the like. Note that the "calculation" includes the calculation related to addition, subtraction, multiplication and division and the calculation related to retrieval and analysis. In the present embodiment, when the data format of the attribute value of the attribute item included in the sensitive data is a numerical value, the encryption unit <NUM> performs the encryption using the homomorphic encryption scheme (e.g., Paillier scheme, Lifted-Ellgamal scheme, Somewhat Homomorphic Encryption scheme, Fully Homomorphic Encryption scheme) and/or the order-preserving encryption scheme (OPE scheme). Since the processing efficiency varies depending on the encryption scheme and the content of the data processing, each of the attribute items can be stored in a plurality of encryption schemes (e.g., the attribute value encrypted by the homomorphic encryption scheme, the attribute value encrypted by the order-preserving encryption scheme, the attribute value encrypted by the later described retrievable encryption scheme). When the data format is the string, the encryption is performed using the retrievable encryption scheme or the AES encryption since complete matching is possible in the encrypted text, for example. Note that the above described encryption schemes applied depending on the data format are merely examples. The organization possessing the sensitive data can arbitrarily determine the target attribute value of the attribute item to be encrypted and the encryption scheme used for the encryption. In addition, it is also possible to determine whether or not to encrypt the sensitive data according to the intention of the individual.

In the present embodiment, the encryption unit <NUM> does not encrypt the identifier included as one of the attribute items. Because of this, the management server <NUM> integrates the sensitive data received from each of the data providing servers <NUM> based on the identifier to generate the integrated data. The process of generating the integrated data will be descried later. The explanation of encryption algorithm is omitted since the encryption algorithm is conventionally known technology. As another embodiment, it is also possible that the encryption unit <NUM> encrypts the identifier which is included as one of the attribute items.

In addition, the encryption unit <NUM> encrypts a predetermined data (e.g., SQL statement as the processing request) transmitted from the management server <NUM> in accordance with the request from the management server <NUM>.

The decryption unit <NUM> decrypts the execution result of the data processing obtained by the communication unit <NUM>. More specifically, in the execution result to which the decryption processing is requested from the management server <NUM>, the decryption unit <NUM> acquires the corresponding decryption key from the storage unit <NUM> and decrypts the execution result of the data processing of the attribute items encrypted by the encryption key managed by the key management unit <NUM> in accordance with the encryption scheme of the encryption. Note that the explanation of decryption algorithm is omitted since the decryption algorithm is conventionally known technology.

In addition, the decryption unit <NUM> transmits the decrypted execution result to the control unit <NUM>, and the control unit <NUM> transmits the decrypted execution result to the management server <NUM>. Alternatively, the control unit <NUM> can transmit the decrypted execution result to the terminal device <NUM> from which the processing request of the data processing is transmitted in accordance with the request from the management server <NUM>.

<FIG> is a drawing showing an example of the data structure of sensitive data. In the present embodiment, the sensitive data is the information about the individual. The sensitive data is the attribute value (string or numerical value) of the attribute item (column) such as the age, the gender, the income, the residential area and the purchase information. Furthermore, the sensitive data includes the identifier (common ID) as one of the attribute items for uniquely identifying the individual as the integrated key. The identifier can be a numerical value, a string or the combination of the numerical value and the string. For simplifying the explanation, predetermined attribute items are shown in <FIG>. However, the not illustrated attribute items can be further included in the sensitive data. In addition, the sensitive data is not limited to the information about the individual. The sensitive data can be confidential information (e.g., sensing data and log data) related to the system of IoT/NW devices, industrial devices and the like. Furthermore, the integrated key is not limited to the identifier uniquely identifying the individual. An arbitrary value can be used as the integrated key as long as it can uniquely identify the data in a plurality of tables.

In <FIG>, tables T1, T2 and T3 storing the attribute values of the attribute items are shown. The table <NUM> shows the sensitive data provided by the data providing server <NUM>-<NUM> (i.e., the data possessed by the company A). In the table T1, the sensitive data includes "common ID" as the identifier for uniquely identifying the individual, "age" indicating the age of the individual, "gender" indicating the gender of the individual, "income" indicating the income of the individual, and "purchase flag <NUM>" indicating the presence or absence of the purchase of the product <NUM> purchased by the individual as the attribute items. In the table T1, the attribute values of the attribute items of "common ID," "age," "income" and "purchase flag <NUM>" are the numerical values. Although the attribute value of "gender" is the category (string) in <FIG>, the category can be also shown by the numerical value by associating the gender with the numerical value, for example.

In the table T1, the attribute value "<NUM>" is stored for the attribute item "common ID," the attribute value "<NUM>" is stored for the attribute item "age," the attribute value "female" is stored for the attribute item "gender," the attribute value "<NUM>" is stored for the attribute item "income" and the attribute value "<NUM>" is stored for the attribute item "purchase flag <NUM>. " This means that the age of the individual who has the common ID of <NUM> is <NUM> years, the gender is female, the income is <NUM> (ten thousand yen) and the individual has already bought the product <NUM>. Similarly, for the attribute values "<NUM>," "<NUM>," "<NUM>," "<NUM>" and "<NUM>" of the attribute item "common ID," the attribute values are stored for each of the attribute items.

The table <NUM> shows the sensitive data provided by the data providing server <NUM>-<NUM> (i.e., the data possessed by the company B). The data providing server <NUM>-<NUM> provides the sensitive data including the attribute item different from that of the company A possessing the sensitive data shown in the table T1.

In the table T2, the sensitive data includes "common ID" as the identifier for uniquely identifying the individual, "residential area" indicating the area in which the individual lives, "purchase flag <NUM>" indicating the presence or absence of the purchase of the product <NUM> purchased by the individual, and "purchase flag <NUM>" indicating the presence or absence of the purchase of the product <NUM> purchased by the individual as the attribute items. In the table T2, the attribute values of the attribute items "common ID," "purchase flag <NUM>" and "purchase flag <NUM>" are the numerical values, while the attribute values of the attribute item "residential area" are the string. Although the attribute value of "residential area" is the category (string) in <FIG>, the category can be also shown by the numerical value by associating the area with the numerical value, for example. For example, in the table T2, the attribute value "<NUM>" is stored for the attribute item "common ID," the attribute value "Tokyo" is stored for the attribute item "residential area," the attribute value "<NUM>" is stored for the attribute item "purchase flag <NUM>" and the attribute value "<NUM>" is stored for the attribute item "purchase flag <NUM>. " This means that the residential area of the individual who has the common ID of <NUM> is Tokyo, the individual has already bought the product <NUM> and the individual has not bought the product <NUM> yet. Similarly, for the attribute values "<NUM>," "<NUM>," "<NUM>," "<NUM>" and "<NUM>" of the attribute item "common ID," the attribute values are stored for each of the attribute items.

Although the attribute items are different between the table T1 and the table T2 except for "common ID," the record shown by the same "common ID" corresponds to the same individual. For example, the record (individual) identified by the attribute value "<NUM>" of "common ID" in the table T1 is same as the record (individual) identified by the attribute value "<NUM>" of "common ID" in the table T2.

The table T3 shows the sensitive data provided by the data providing server <NUM>-<NUM> (i.e., the data possessed by the company C). The data providing server <NUM>-<NUM> provides the sensitive data different from the sensitive data of the company A and the company B possessing the sensitive data shown in the table T1 and the table T2.

In the table T3, the sensitive data includes "common ID" as the identifier for uniquely identifying the individual, "spouse flag" indicating the presence or absence of the spouse, "number of dependents" indicating the number of the dependents and "purchase flag <NUM>" indicating the presence or absence of the purchase of the product <NUM> purchased by the individual as the attribute item. In the table T3, the attribute values of the attribute items "common ID," "spouse flag," "number of dependents" and "purchase flag <NUM>" are the numerical values. For example, in the table T3, the attribute value "<NUM>" is stored for the attribute item "common ID," the attribute value "<NUM>" is stored for the attribute item "spouse flag," the attribute value "<NUM>" is stored for the attribute item "number of dependents" and the attribute value "<NUM>" is stored for the attribute item "purchase flag <NUM>. " This means that the individual who has the common ID of <NUM> has the spouse, the individual has three dependents and the individual has already bought the product <NUM>. Similarly, for the attribute values "<NUM>," "<NUM>," "<NUM>" and "<NUM>" of the attribute item "common ID," the attribute values are stored for each of the attribute items.

The attribute items are different between the table T3 and the table T1 or T2 except for "common ID. " In addition, the attribute values "<NUM>" and "<NUM>" are included only in the table T3 as the attribute item "common ID" Namely, it is not necessary that the same group of the records is included in all tables. The table can include the group of the records that are different from those of another table. In the present embodiment, as shown in <FIG>, the attribute items included in the sensitive data provided by each of the data providing servers are different except for "common ID" (identifier). However, the same attribute item can be included as another embodiment. In that case, a system administrator or the like can properly specify and determine which of the data providing servers is prioritized as the attribute value of the integrated data.

<FIG> is a drawing showing an example of the data structure of the encrypted sensitive data. In <FIG>, the tables T1e, T2e and T3e in which the attribute values of the attribute items are encrypted except for "common ID" are shown.

In the table T1e, the attribute values of the table T1 are encrypted except for "common ID" based on the encryption key managed by the data providing server <NUM>-<NUM> (company A). For example, the attribute items "age," "income" and "purchase flag <NUM>" whose attribute values are indicated by the numerical values are encrypted by the homomorphic encryption scheme and/or the order-preserving encryption schemes, while the attribute item "gender" whose attribute values are indicated by the string is encrypted by the retrievable encryption scheme. For simplifying the explanation, the values encrypted by the homomorphic encryption scheme are shown in the table T1e for the data of the attribute values indicated by the numerical value (hereafter, same in the tables T2e and T3e).

In the table T2e, the attribute values of the table T2 are encrypted except for "common ID" based on the encryption key managed by the data providing server <NUM>-<NUM> (company B). For example, the attribute items "purchase flag <NUM>" and "purchase flag <NUM>" whose attribute values are indicated by the numerical values are encrypted by the homomorphic encryption scheme and/or the order-preserving encryption scheme, while the attribute item "residential area" whose attribute values are indicated by the string is encrypted by the retrievable encryption scheme.

In the table T3e, the attribute values of the table T3 are encrypted except for "common ID" based on the encryption key managed by the data providing server <NUM>-<NUM> (company C). For example, the attribute items "spouse flag," "number of dependents" and "purchase flag <NUM>" whose attribute values are indicated by the numerical values are encrypted by the homomorphic encryption scheme and/or the order-preserving encryption scheme.

It is not necessary to encrypt the attribute values of all attribute items except for "common ID" in each of the tables by the same encryption key. For example, it is possible to encrypt them by using different keys according to the degree of importance or the like. In addition, it is possible to determine the attribute values to be encrypted according to the disclosure condition or the like of each of the attribute items. For example, it is possible to specify the data providing server <NUM>-<NUM> not to encrypt the attribute values of the attribute item "purchase flag <NUM>" in the table T3 according to the instruction of the organization (company C) possessing the sensitive data.

In addition, although the numerical values of the encrypted data are same in <FIG> when the attribute values of the data are same in <FIG>, the following method can be employed for increasing the security. For example, both attribute values are stored: one is the attribute value (retrieval data) encrypted as it is for a retrieval processing; and the other is the attribute value (communication data) encrypted by adding random values before and after the attribute value. Thus, it is possible to use the retrieval data for the retrieval processing with complete matching and use the communication data for the communication. In this case, the added random values are deleted after the decryption to output the attribute value. Although the attribute values except for "common ID" are encrypted in <FIG>, the attribute item itself and the attribute value of the common ID can be also encrypted.

<FIG> is a drawing showing an example of the data structure of the integrated data. In <FIG>, an integrated table Tm is the table integrated by using the attribute values (identifiers) of the attribute item "common ID" included in the tables T1e, T2e and T3e as the integrated key. Namely, the integrated data is the table Tm including "common ID," "age," "income," "purchase flag <NUM>," "residential area," "purchase flag <NUM>," "purchase flag <NUM>," "spouse flag," "number of dependents" and "purchase flag <NUM>" as the attribute items wherein the attribute values of the attribute items except for "common ID" are encrypted as shown in <FIG>. The integrated data having the data structure shown in <FIG> is stored in the common database <NUM>. The common database <NUM> is a relational database storing a table having the attribute items as columns, for example. Note that the rows of the integrated table are referred to as "record" in this specification.

In the integrated table Tm, the attribute items (columns) "age," "income" and "purchase flag <NUM>" are the sensitive data provided by the data providing server <NUM>-<NUM> (company A). The attribute items (columns) "residential area," "purchase flag <NUM>" and "purchase flag <NUM>" are the sensitive data provided by the data providing server <NUM>-<NUM> (company B). The attribute items (columns) "spouse flag," "number of dependents" and "purchase flag <NUM>" are the sensitive data provided by the data providing server <NUM>-<NUM> (company C).

As for the attribute values of the attribute items included in the table T3 and not included in the tables T1 and T2 (e.g., the attribute values "<NUM>" and "<NUM>" of "common ID"), a designer of the database or an administrator of the management server <NUM> or the like can arbitrarily determine to store a blanc (NULL) value or a dummy numerical value, for example. Alternatively, it is also possible to delete the record in which the attribute values other than the attribute value of the attribute item "common ID" is not stored in the integrated data.

Namely, in the example of <FIG>, the integration processing including the integration of the table in a lateral direction (i.e., addition of "attribute item" (column) and the integration of the table in a vertical direction (i.e., addition of "record") is performed using the attribute item "common ID" shown in the tables T1e, T2e and T3e of <FIG> as the integrated key. Note that the common database <NUM> is not limited to the relational database illustrated above. The kind of the common database <NUM> can be NoSQL, NewSQL and Graph Database, for example.

<FIG> is a functional block diagram showing an example of a functional configuration of the management server <NUM>. With reference to <FIG>, an example of the functional configuration of the management server <NUM> will be explained.

The management server <NUM> includes a communication unit <NUM>, a storage unit <NUM> and a control unit <NUM>.

The communication unit <NUM> includes a communication interface circuit so that the management server <NUM> can establish the communication with the other servers and the devices via the network NW according to a predetermined communication protocol. The communication unit <NUM> transmits the received data to the control unit <NUM> and transmits the data received from the control unit <NUM> to the other servers and the devices via the network NW.

In addition, the communication unit <NUM> functions as the reception unit for receiving the processing request of the later described data processing processed to the integrated data stored in the common database <NUM>. Note that the communication unit <NUM> transmits and receives the data to/from the devices and the like via the network NW using a secure communication channel where security is ensured. The explanation of the method of constructing the secure communication channel and the communication method is omitted since they are well known technology.

The storage unit <NUM> includes a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk drive or a portable disk device such as a flexible disk and an optical disc, for example. In addition, the storage unit <NUM> stores computer programs, database, tables, keys and the like used for various processing of the management server <NUM>. The computer programs can be installed in the storage unit <NUM> from a portable computer-readable recording medium using a conventionally known setup program, for example. The portable recording medium can be a CD-ROM (Compact Disc Read Only Memory) and a DVD-ROM (Digital Versatile Disc Read Only Memory), for example. The computer programs can be installed from a predetermined server, for example.

The storage unit <NUM> has a configuration file <NUM> related to the data processing. The configuration file <NUM> defines a criteria for determining whether or not to execute the data processing. For example, the configuration file <NUM> stores the users or the like having the execution authority of the data processing in association with the attribute items of the integrated data. In addition, the configuration file <NUM> stores the device (organization) from which the data is provided in association with the attribute items of the integrated data. Note that the configuration file <NUM> can be arbitrarily specified by the administrator of the management server <NUM>, the administrator of the data providing server <NUM> or the associated organization.

In addition, the storage unit <NUM> stores the encrypted sensitive data that the communication unit <NUM> received from the data providing server <NUM>.

<FIG> is a drawing showing an example of the data structure of the configuration file. In <FIG>, the configuration file <NUM> stores the "attribute items" included in the integrated data shown in <FIG> by associating "user having authority" for performing the data processing with "server providing the data" (data providing server) providing the corresponding attribute items (columns).

The authority for performing the data processing about the attribute item is the authority for performing the statistical processing and the retrieval processing about the attribute values of the attribute items specified as the object of the data processing. For example, it is the authority for executing the data processing for the attribute item "age" as the object. For example, it is the statistical processing for calculating an average value, a maximum value and a minimum value of the attribute values or the retrieval processing for calculating the number of the records having a predetermined age or more. In addition, it can be the authority for performing the statistical processing for the attribute item "gender" as the object for extracting the records of the female, counting the number of the extracted records, or calculating an average value of the attribute values of a predetermined attribute item, for example.

Here, the "user having authority" for the attribute item "age" is "U1, U2, U3" and the "user having authority" for the attribute item "gender" is "ALL" (all users). Accordingly, as for the data processing processed to the integrated data, in case the average of the attribute item "age" is calculated for the record of the attribute value "female" for the attribute item "gender," the user has the authority for performing the processing request when the user who transmits the processing request is any one of "U1, U2, U3. " Since the other users than "U1, U2, U3" do not have the authority for executing the data processing about "age," the other users cannot execute the data processing of calculating the average of the attribute item "age" of the attribute item "female.

In <FIG>, the control unit <NUM> includes an integral control unit <NUM>, an integrated data generation unit <NUM>, an execution unit <NUM> and a decryption request unit <NUM>. The integral control unit <NUM> is a processor such as a CPU (Control Processing Unit) operated based on programs preliminarily stored in the storage unit <NUM> to control the functions of the management server <NUM>. Note that a DSP (digital signal processor) or the like can be used as the integral control unit <NUM>. In addition, control circuits such as an LSI (large scale integration), an ASIC (Application Specific Integrated Circuit) and an FPGA (Field-Programming Gate Array) can be used as an integral control unit <NUM>.

In accordance with the control of the integral control unit <NUM>, the integrated data generation unit <NUM> generates the integrated data by integrating the encrypted sensitive data received from the data providing servers <NUM> via the communication unit <NUM> and stored in the storage unit <NUM> based on the identifiers (common IDs in the example of <FIG>) included as the attribute item in the sensitive data. Then, the integrated data generation unit <NUM> transmits the generated integrated data to the integral control unit <NUM>, and the integral control unit <NUM> stores the integrated data in the common database <NUM> via the communication unit <NUM>. In addition, after the integrated data is generated, the integrated data generation unit <NUM> can delete the integrated sensitive data from the storage unit <NUM>.

In addition, the integrated data generation unit <NUM> stores the attribute items included in the integrated data in the configuration file <NUM>. It is possible to disclose the attribute items included in the integrated data based on the configuration file <NUM>. Because of this, the user joined in the data sharing system <NUM> can recognize the attribute items to which the data processing can be requested. Although the attribute items are disclosed, the attribute values of the attribute items are encrypted and stored in the common database <NUM>. Thus, the integrated data can be utilized securely in the data sharing system <NUM>. Note that the processing of integrating the sensitive data in the integrated data generation unit <NUM> can be executed by the later described execution unit <NUM> as the data processing of the integrated data or executed by another information processing device which obtains the encrypted sensitive data.

The execution unit <NUM> executes the data processing based on the processing request of the data processing processed to the integrated data. Then, the execution unit <NUM> transmits the execution result to the decryption request unit <NUM>. Here, the data processing includes a retrieval processing and/or a statistical processing targeted at least a part of the attribute items of the integrated data. In the present embodiment, the retrieval processing is the processing of extracting the record satisfying a predetermined condition. In addition, the statistical processing is the processing executed by the function for tabulation, for example. Representatively, the statistical processing is the processing of counting the number of lines (records) of the table (COUNT function), the processing of summing the data of the numerical columns in the table (SUM function), the processing of calculating the average of the data of the numerical columns in the table (AVG function), the processing of calculating the maximum value of the data of an arbitrary column in the table (MAX function), the processing of calculating the minimum value of the data of an arbitrary column in the table (MIN function), and the like. However, the statistical processing is not limited to the above described examples. The statistical processing can be SQL syntax such as "GROUP BY" for grouping (classifying) the data by a target segment and "ORDER BY" for rearranging the data in ascending or descending order.

The processing request of the data processing can be a query described in the SQL statement, for example. More specifically, as the SQL statement targeted at the table Tm which is the integrated data shown in <FIG>, the communication unit <NUM> receives the SQL statement indicated as "select avg (age) from `table Tm' where `residential area'=Tokyo;" as the processing request of the data processing, for example. Based on the SQL statement, the execution unit <NUM> accesses the common database <NUM> via the communication unit <NUM>, extracts the record having the attribute value "Tokyo" of the attribute item "residential area" in the table Tm, and executes the processing of calculating the average value of the attribute values of the attribute item "age" in the extracted record. Since the data of the table Tm is encrypted as described above, the following processes are performed.

For example, the execution unit <NUM> refers to the configuration file <NUM> for the match judgement of the condition of the where clause and acquires the information of the data providing server <NUM> which encrypted the attribute item "residential area. " Then, the execution unit <NUM> transmits the conditional statement of the where clause to the data providing server <NUM> (the data providing server <NUM>-<NUM> in the example of <FIG>) which encrypted the attribute item "residential area" via the communication unit <NUM>. At that time, the execution unit <NUM> requests the data providing server <NUM> to use the encryption scheme capable of executing the encryption in the encrypted state (e.g., AES and retrievable encryption) to acquire the encrypted conditional statement of the where clause. For example, in accordance with the request from the execution unit <NUM>, the data providing server <NUM>-<NUM> encrypts "Tokyo" using the encryption key used when encrypting the attribute item "residential area" with respect to the above described query "select avg (age) from `table Tm' where `residential area'=Tokyo;. " Then, the data providing server <NUM>-<NUM> returns (transmits) "select avg (age) from 'the table Tm' where `residential area'=avf3h54. ;" including the encrypted where clause to the execution unit <NUM> of the management server <NUM>.

Since the attribute values of the attribute item "age" are encrypted by the (additive) homomorphic encryption scheme where addition and subtraction can be performed in the encrypted state, the execution unit <NUM> calculates the average value for the extracted record by using the well known method. As described above, the execution unit <NUM> can execute the SQL statement. Then, the execution result (the encrypted text indicating the average of the attribute values of "age" of the individuals having the attribute value "Tokyo" as "residential area" in the above described example) is outputted.

It is also possible that the execution unit <NUM> judges whether or not to execute the data processing based on the configuration file <NUM> when the execution unit <NUM> receives the processing request of the data processing. As described above, the configuration file <NUM> stores each of the attribute items of the integrated data in association with the user having the authority for executing the data processing. Therefore, the execution unit <NUM> judges whether or not the user who performs the processing request of the data processing has the authority for executing the data processing to the attribute item for the object of the data processing. When the execution unit <NUM> judges that the user does not have the authority, the execution unit <NUM> can transmit an error notification to the user who performs the processing request via the communication unit <NUM> for notifying that the user does not have the authority, for example. When the execution unit <NUM> judges that the user has the authority, the execution unit <NUM> executes the data processing and transmits the execution result to the decryption request unit <NUM>.

In addition, the execution unit <NUM> can execute the data processing based on the judgement from the SQL statement whether or not the attribute item for the object of the data processing is included in the integrated data. The execution unit <NUM> refers to the configuration file <NUM> and acquires the information of the attribute items included in the integrated data. Then, when the execution unit <NUM> judges that the attribute items for the object of the data processing are not included in the integrated data, the execution unit <NUM> can transmit an error notification to the user who performs the processing request via the communication unit <NUM> for notifying that the attribute items for the object of the data processing are not included in the integrated data, for example. In addition, there is a possibility that the user erroneously selected the attribute item for the object of the data processing. Thus, it is possible to provide a proposal for executing the data processing for another attribute item as the object instead of transmitting the error notification. Because of this, user-friendly notification can be transmitted.

The decryption request unit <NUM> transmits the processing request of the decryption processing to the data providing server <NUM> for requesting the data providing server <NUM> to decrypt the execution result of the data processing executed by the execution unit <NUM>. At this time, the decryption request unit <NUM> can transmit the processing request of the decryption processing based on the number of the records included in the execution result. For example, when the number of the records extracted by the condition described in the SQL statement as the processing request is "<NUM>," the result (statistic value) of the statistical processing is coincide with the extracted attribute value of the record. Thus, raw data is disclosed. Accordingly, the administrator of the management server <NUM> and the data providing server <NUM> can preliminarily specify the decryption request unit <NUM> not to transmit the processing request of the decryption processing when the number of the extracted records is "<NUM>" as the decryption condition. It is also possible not to transmit the processing request of the decryption processing even when the number of the extracted record is not "<NUM>" according to the content of the statistical processing. Note that the decryption request unit <NUM> can transmit the processing request of the decryption processing based on the conditions of the record such as the record index, the attribute of the attribute item (column), the keyword and the user attribute instead of the above described number of records. For example, the condition of performing the processing request of the decryption processing can be specified so that only specific users can be decrypted for particular data (specifically, the record No. <NUM>-<NUM> can be decrypted only by the user A) or the data including specific keyword cannot be decrypted (specifically, the decryption is prohibited when the keyword "Tokyo" is included in the address column).

The decryption request unit <NUM> requests the data providing server <NUM> from which the sensitive data including the attribute item for the object of the data processing is provided to decrypt the execution result by the decryption key managed by the data providing server <NUM>. Namely, about the attribute value of the attribute item for the object of the data processing, the execution result calculated for the statistical processing in the encrypted state is encrypted by the encryption key managed by the data providing server <NUM> which provides the sensitive data including the corresponding attribute item. Accordingly, the decryption processing should be executed by the data providing server <NUM> managing the decryption key corresponding to the encryption key. Then, the decryption request unit <NUM> refers to the configuration file <NUM>, acquires the information of the data providing server <NUM> providing the attribute item for the object of the data processing, and transmits the processing request of the decryption processing to the data providing server <NUM>.

It is also possible that the decryption request unit <NUM> inquires the data providing server <NUM> providing the sensitive data including the attribute item for the object of the data processing whether or not the execution result can be decrypted and requests the decryption of the execution result by the decryption key managed by the data providing server <NUM> in accordance with the permission response to the inquiry. For example, the data providing server <NUM> judges whether or not the predetermined decryption condition is satisfied or a responsible person and the like of the organization possessing the sensitive data judges whether or not the execution result can be decrypted. Thus, when the permission response of the decryption is received, the decryption request unit <NUM> transmits the execution result to request the decryption processing. Consequently, the original decryption conditions (e.g., presence/absence of the authority of performing the processing request) can be specified at the side of the data providing server <NUM>. Note that the decryption request unit <NUM> can transmit the processing request so that the decryption processing is executed based on the configuration file <NUM> and the inquiry about the decryption of the execution result.

In addition, the decryption request unit <NUM> acquires the execution result decrypted by the data providing server <NUM> via the communication unit <NUM>, and provides the acquired execution result to the terminal device <NUM> from which the processing request of the data processing is transmitted. Note that the terminal device <NUM> from which the processing request of the data processing is transmitted can preliminarily transmit the public key for encrypting the decrypted execution result to the management server <NUM> at the same time when transmitting the processing request of the data processing. In this case, the decryption request unit <NUM> transmits the public key of the terminal device <NUM> together with the processing request of the decryption processing to the data providing server <NUM>. The data providing server <NUM> encrypts the decrypted execution result using the received public key, and transmits the encrypted data to the management server <NUM>. The terminal device <NUM> receives the execution result encrypted by the public key of the terminal device <NUM> from the management server <NUM> and decrypts the execution result using the secret key of the terminal device <NUM>. Thus, the terminal device <NUM> can acquire the execution result. Consequently, the data processing can be performed without disclosing the execution result to the management server <NUM>.

It is possible that the decryption request unit <NUM> requests the data providing server <NUM> providing the sensitive data including the attribute item for the object of the data processing to decrypt the execution result by the encryption key managed by the data providing server <NUM> and provide the decrypted execution result to the terminal device <NUM> from which the processing request of the data processing is transmitted. Since the execution result is directly transmitted to the terminal device from which the processing request of the data processing is transmitted without passing through the management server <NUM>, the number of communication processes can be reduced. Also in this case, same as the above described case, the public key of the terminal device <NUM> for encrypting the decrypted execution result can be preliminarily transmitted to the management server <NUM> at the same time when transmitting the processing request of the data processing. Although the example of encrypting the execution result by the public key of the terminal device <NUM> is described above, the execution result can be encrypted by the common key preliminarily shared in the data sharing system <NUM>, for example.

<FIG> is a functional block diagram showing an example of the functional configuration of the terminal device <NUM>. With reference to <FIG>, an example of the functional configuration of the terminal device <NUM> will be explained.

The terminal device <NUM> includes a communication unit <NUM>, a storage unit <NUM>, an input unit <NUM>, an output unit <NUM> and a control unit <NUM>. As described above, the terminal device <NUM> can be an information processing device operated by users belonging to the organization joined in a platform (data sharing system <NUM>), for example.

The communication unit <NUM> has the similar function as the communication unit <NUM> of the data providing server <NUM>. The communication unit <NUM> includes a communication interface circuit so that the terminal device <NUM> establishes the communication with the servers and the devices via the network NW according to a predetermined communication protocol. The communication unit <NUM> transmits the received data to the control unit <NUM> and transmits the data received from the control unit <NUM> to the other servers and the devices via the network NW.

The storage unit <NUM> is a memory device having the similar function as the storage unit <NUM> of the data providing server <NUM>. The storage unit <NUM> stores computer programs, database, tables and the like used for various processing of the terminal device <NUM>. The computer programs can be installed in the storage unit <NUM> from a portable computer-readable recording medium using a conventionally known setup program, for example. In addition, the storage unit <NUM> can store the encryption key (public key) for encrypting the execution result of the data processing in the terminal device <NUM> and the decryption key (secret key) for decrypting the execution result encrypted by the encryption key.

The input unit <NUM> is an interface for receiving a user input of the terminal device <NUM>. The input unit <NUM> can be a keyboard, a touch panel and a microphone for detecting a sound input, for example. However, the input unit <NUM> is not limited to the above described examples. The user inputs the processing request of the data processing through the input unit <NUM>. The processing request is written in SQL, for example.

The output unit <NUM> is an interface for outputting the information and notifying the user. The output unit <NUM> can be a display and a speaker for outputting sound, for example. However, the output unit <NUM> is not limited to the above described examples. The output unit <NUM> provides the execution result of the data processing to the user by displaying it on the display, for example.

The control unit <NUM> is a processor such as a CPU (Control Processing Unit) operated based on programs preliminarily stored in the storage unit <NUM> to control the functions of the terminal device <NUM>. The control unit <NUM> transmits the processing request of the data processing inputted through the input unit <NUM> to the management server <NUM> via the communication unit <NUM>. At this time, the control unit <NUM> can transmit the processing request together with the public key stored in the storage unit <NUM> to the management server <NUM>. In addition, the control unit <NUM> acquires the execution result of the data processing via the communication unit <NUM>. When the execution result of the data processing is encrypted by the public key of the terminal device <NUM>, the execution result is obtained by decrypting it by the secret key which is paired with the public key. Note that the execution result can be encrypted by the common key for secure communication preliminarily or arbitrarily constructed in the data sharing system <NUM>.

<FIG> is a flow chart showing an example of the process of storing the integrated data in the common database. With reference to <FIG>, the flow of the processes of integrating the sensitive data provided by the organization joined in the platform (data sharing system <NUM>) and storing the integrated data in the common database <NUM> will be explained. Note that the flow of the processes shown in <FIG> is merely an example. The flow is not limited to the orders shown in <FIG>. In addition, it goes without saying that the process of integrating a plurality of tables into one table shown in <FIG> is merely an example.

In the step S101, the communication unit <NUM> of the data providing server <NUM> acquires the sensitive data from the organization and the like joined in the platform. The communication unit <NUM> transmits the acquired sensitive data to the control unit <NUM>. The control unit <NUM> stores the sensitive data in the storage unit <NUM>.

In the step S102, the control unit <NUM> of the data providing server <NUM> controls the encryption unit <NUM> to execute an encryption process with respect to the sensitive data acquired in the step S101.

According to the control of the control unit <NUM>, the encryption unit <NUM> reads the sensitive data from the storage unit <NUM> and checks the data format and the like of the attribute item (column), for example. Then, the encryption unit <NUM> executes the encryption process corresponding to the data format of the attribute item and the content of the attribute item. For example, when the data format of the attribute value of the attribute item is the numerical value, the encryption process is performed using the homomorphic encryption scheme and/or the order-preserving encryption scheme. When the data format is the string, the encryption process is performed using the retrievable encryption scheme. Note that the encryption unit <NUM> can encrypt the attribute values of the identifier (common ID) (i.e., attribute item) although the encryption can be omitted for them. This is because the identifier can be used as the integrated key for the process of integrating the data even if it is encrypted. In addition, for the encryption process, the encryption unit <NUM> requests the encryption key to the key management unit <NUM> to acquire the key corresponding to the encryption scheme used for the encryption. The encryption unit <NUM> stores the encrypted sensitive data in the storage unit <NUM>.

In the step S103, according to the control of the control unit <NUM>, the communication unit <NUM> of the data providing server <NUM> transmits the encrypted sensitive data stored in the storage unit <NUM> to the management server <NUM>. Note that the processes of the steps S101 to S <NUM> can be performed in parallel in the data providing server <NUM> which is associated with each organization joined in the platform (data sharing system <NUM>).

In the step S104, the communication unit <NUM> of the management server <NUM> acquires the encrypted sensitive data from each data providing server <NUM>. The communication unit <NUM> transmits the encrypted sensitive data to the integral control unit <NUM>. The integral control unit <NUM> stores the encrypted sensitive data in the storage unit <NUM>.

In the step S105, according to the control of the integral control unit <NUM>, the integrated data generation unit <NUM> of the management server <NUM> reads the encrypted sensitive data stored in the storage unit <NUM>, and integrates the sensitive data to generate the integrated data based on the identifier (common ID) included as one of the attribute items of the sensitive data. The integrated data generation unit <NUM> stores the generated integrated data in the storage unit <NUM>.

In the step S106, according to the control of the integral control unit <NUM>, a communication unit <NUM> of the management server <NUM> transmits the integrated data stored in the storage unit <NUM> to the common database <NUM>. The common database <NUM> stores the received integrated data.

<FIG> is a flow chart showing an example of the data processing. With reference to <FIG>, an example of the flow of the data processing in the management server <NUM> will be explained. Note that the flow of the data processing shown in <FIG> is merely an example. The flow is not limited to the orders shown in <FIG>.

In the step S201, the communication unit <NUM> receives the processing request of the data processing from the terminal device <NUM>. Note that the processing request of the data processing can be written in SQL, for example. In addition, the processing request can include the encryption key managed by the terminal device <NUM> for encrypting the decrypted execution result. In addition, the processing request can include the information for identifying the terminal device from which the processing request is transmitted (e.g., the user information of the terminal device <NUM> transmitting the processing request). The communication unit <NUM> transmits the received processing request of the data processing to the integral control unit <NUM>.

In the step S202, according to the control of the integral control unit <NUM>, the execution unit <NUM> judges whether or not the data processing can be executed based on the configuration file <NUM>. For example, the execution unit <NUM> refers to the configuration file <NUM> shown in <FIG> to judge whether or not the user transmitting the processing request of the data processing has the execution authority or judge whether or not the attribute item of the object of the data processing included in the processing request is included in the integrated data. When the execution unit <NUM> judges based on the configuration file <NUM> that the data processing can be executed (Y in the step S202), the process is advanced to the step S203. When the execution unit <NUM> judges that the data processing cannot be executed (N in the step S202), the process is advanced to the step S208.

In the step S203, the execution unit <NUM> acquires the integrated data from the common database <NUM> to execute the data processing. The detailed explanation of the data processing is omitted since it has already been described. Since the sensitive data is encrypted by the encryption scheme that is capable of performing the calculation in the encrypted state, the execution unit <NUM> can calculate the sensitive data in the encrypted state in accordance with the processing request of the data processing and the execution result is also in the encrypted state. The execution unit <NUM> transmits the execution result to the decryption request unit <NUM>.

In the step S204, the decryption request unit <NUM> judges whether or not the execution result can be decrypted. More specifically, the decryption request unit <NUM> judges whether or not the decryption can be executed based on the number of the records included in the execution result (e.g., the number of the records extracted for the statistical processing as the processing request of the data processing). When the decryption request unit <NUM> judges that the number of the records included in the execution result is "<NUM>" (N in the step S204), the process is advanced to the step S208. Otherwise (Y in the step S204), the process is advanced to the step S <NUM>. Instead of judging whether or not the decryption processing can be executed based on the number of the records, the decryption request unit <NUM> can inquire the data providing server <NUM> providing the sensitive data including the attribute item for the object of the data processing whether or not to allow the decryption processing. It is possible to advance the process to the step S208 when the response is not received in a predetermined period after the inquiry.

In the step S205, the decryption request unit <NUM> transmits the processing request of the decryption processing of the execution result. For example, the decryption request unit <NUM> refers to the configuration file <NUM>, and transmits the processing request of the decryption processing to the data providing server <NUM> providing the attribute item specified as the object of the statistical processing via the communication unit <NUM>. In accordance with the processing request of the decryption processing, the data providing server <NUM> executes the decryption processing of the execution result based on the decryption key. Note that the processing request of the decryption processing can include the encryption key of the terminal device <NUM> which transmits the processing request of the data processing so that the data providing server <NUM> can encrypt the decrypted execution result by the encryption key. Because of this, the execution result is not disclosed to other than the data providing server <NUM> providing the data and the terminal device <NUM> transmitting the processing request of the data processing. Thus, the information leakage can be prevented.

In the step S206, the decryption request unit <NUM> acquires the decrypted execution result via the communication unit <NUM>.

In the step S207, the decryption request unit <NUM> provides the acquired execution result to the terminal device <NUM> transmitting the processing request of the data. When the acquired execution result is encrypted by the public key of the terminal device <NUM>, the terminal device <NUM> decrypts the execution result using the secret key.

Furthermore, in the step S208, according to the judgement of not allowing the execution by the execution unit <NUM> in the step S202 and the judgement of not allowing the decryption by the decryption request unit <NUM> in the step S204, the integral control unit <NUM> notifies the error notifying via the communication unit <NUM> that the execution result of the data processing cannot be provided. At this time, the reason such as the absence of the execution authority can be notified. As described above, the data processing is executed in the data sharing system <NUM>.

<FIG> is a block diagram showing a hardware configuration of the management server <NUM>. The management server <NUM> is implemented in a computer <NUM>. The computer <NUM> includes a CPU <NUM>, a main storage <NUM>, an auxiliary storage <NUM> and an interface <NUM>.

The operations of each configuration of the management server <NUM> are stored in the auxiliary storage <NUM> in the form of programs. The CPU <NUM> reads the programs from the auxiliary storage <NUM>, expands the programs in the main storage <NUM>, and executes the above described processes according to the programs. In addition, the CPU <NUM> secures a storage area in the main storage <NUM> according to the programs. Specifically, the programs make the computer <NUM> execute the data processing.

Note that the auxiliary storage <NUM> is an example of a non-transitory tangible medium. A magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory and the like connected via the interface <NUM> can be listed as the other examples of the non-transitory tangible medium. Furthermore, when the programs are distributed to the computer <NUM> via the network, the computer <NUM> receiving the delivery can expand the programs in the main storage <NUM> to execute the processes.

In addition, the programs can be prepared for achieving only a part of the above described functions. Furthermore, the programs can be a so-called difference file (difference program) for achieving the above described functions while combined with the other programs already stored in the auxiliary storage <NUM>. Note that the hardware configuration shown in <FIG> can be used also for the data providing server <NUM> and the terminal device <NUM>. Same as the above described management server <NUM>, the operations of components of the data providing server <NUM> and the terminal device <NUM> are also achieved by the CPU which is operated in accordance with the programs stored in the auxiliary storage.

As described above, the data sharing system of the present embodiment includes a plurality of data providing servers, a common database and a management server, wherein the management server receives the processing request of the data processing with respect to the integrated data obtained by integrating the sensitive data provided from each of the data providing servers and encrypted by the predetermined encryption scheme. Then, the management server executes the data processing in the encrypted state, and requests the data providing server providing the sensitive data including the attribute item of the object of the data processing to decrypt the execution result of the data processing based on the decryption key managed by the data providing server. The integrated data formed by integrating the sensitive data is stored in the common database in the encrypted state and the data processing is executed in the management server. As described above, the management server does not acquire the decryption key of the sensitive data and cannot decrypt the encrypted sensitive data and decrypt the execution result. Thus, the sensitive data and the execution result of the data processing (e.g., statistical processing) using the sensitive data can be prevented from leaking.

Furthermore, in the present embodiment, the common database is the relational database having a table for storing the attribute items as columns. Since the data processing is the retrieval processing and/or the statistical processing targeting at least a part of the attribute items of the integrated data, the organization joined in the data sharing system can perform the retrieval processing and the statistical processing using the attribute values of the attribute items possessed by the other organizations. Consequently, even when the organization only has sparse data, the organization can utilize the data of the other organizations joined in the data sharing system.

Furthermore, in the present embodiment, the processing request of the decryption processing of the execution result is performed based on the number of the records included in the execution result. Consequently, when the number of the records is <NUM>, the execution result is prevented from being decrypted. Thus, the raw data can be prevented from being disclosed.

Furthermore, in the present embodiment, the management server requests the data providing servers providing the sensitive data including the attribute item of the object of the data processing to decrypt the execution result by the decryption key managed by each of the data providing servers. The execution result can be decrypted only by the data providing server providing and encrypting the sensitive data. Thus, the organization possessing the sensitive data can manage the sensitive data safely in terms of security.

Furthermore, in the present embodiment, the management server inquires the data providing server providing the sensitive data including the attribute item of the object of the data processing whether or not the execution result can be decrypted. According to the permission response of the inquiry, the management server requests the data providing server to decrypt the execution result by the decryption key managed by the data providing servers. Consequently, whether or not to decrypt the execution result can be managed also at the side of the data providing server. Thus, the information leakage can be prevented.

Furthermore, in the present embodiment, the management server or the data providing server provides the execution result decrypted by the data providing server to the terminal device from which the processing request of the data processing is transmitted. Consequently, the terminal device from which the processing request of the data processing is transmitted can acquire the execution result.

Furthermore, in the present embodiment, the data processing is executed based on the configuration file which defines a criteria for determining whether or not the data processing can be executed. Consequently, whether or not to execute the data processing can be judged before executing the data processing. Thus, the execution of the data processing requested by the user without having the execution authority of the data processing can be avoided, for example. Therefore, the amount of the data processing can be reduced.

Furthermore, in the present embodiment, the sensitive data is encrypted by at least one of the homomorphic encryption scheme, the order-preserving encryption scheme, the AES, the DES, the retrievable encryption, the SHA and the MD5. Consequently, the data processing can be executed in the encrypted state. Thus, the sensitive data can be utilized while preventing the information leakage.

Furthermore, in the present embodiment, the management server integrates the sensitive data to generate the integrated data and stores the integrated data in the common database. Consequently, the organization joined in the data sharing system can easily utilize the sensitive data possessed by the organization as the integrated data without disclosing the sensitive data to the other organizations.

The terminal device <NUM> is an information processing device used by employees of the organization such as the company A in association with the data providing server <NUM>-<NUM> which joins in the platform and provides the sensitive data. In this case, the terminal device <NUM> can preliminarily acquire the encryption key managed by the data providing server <NUM>-<NUM>.

When the conditional statement of the SQL statement transmitted as the processing request of the data processing is the match judgement of the condition including the attribute item provided by the data providing server <NUM>-<NUM>, the terminal device <NUM> encrypts the conditional statement by the retrievable encryption scheme based on the encryption key acquired from the data providing server <NUM>-<NUM> and transmits the encrypted conditional statement to the management server <NUM>. Consequently, when the data processing is executed in the management server <NUM>, the process of requesting the data providing server <NUM>-<NUM> to encrypt the conditional statement of the SQL statement can be omitted. Thus, the effect of increasing the processing efficiency can be obtained.

The above described embodiments can be carried out in other various forms. Various omission, replacement and change can be applied within the range not deviating from the summary of the present invention. The embodiments and the variation of them are included in the range and summary of the present invention and also included in the invention described in the claims and the range equivalent to them.

Claim 1:
A data sharing system (<NUM>) comprising:
a plurality of data providing servers (<NUM>);
a common database (<NUM>); and
a management server (<NUM>), wherein
each of the plurality of data providing servers includes:
a sensitive data acquisition unit (<NUM>) configured to acquire sensitive data including attribute values of each of attribute items;
a key management unit (<NUM>) configured to manage an encryption key and a decryption key; and
an encryption unit (<NUM>) configured to encrypt at least a part of the attribute values of the sensitive data by a predetermined encryption scheme based on the encryption key,
the common database is configured to store an integrated data obtained by integrating the sensitive data encrypted in the plurality of data providing servers based on an identifier which is included in the sensitive data as one of the attribute items,
the management server includes:
a reception unit (<NUM>) configured to receive a first processing request of a data processing processed to the integrated data stored in the common database;
an execution unit (<NUM>) configured to execute the data processing; and
a decryption request unit (<NUM>) configured to transmit a second processing request of a decryption processing to the plurality of data providing servers for requesting the plurality of data providing servers to decrypt an execution result of the data processing,
each of the plurality of data providing servers further includes a decryption unit configured to decrypt the execution result based on the decryption key in accordance with the second processing request of the decryption processing transmitted from the decryption request unit of the management server, wherein
the common database stores a table including the attribute items as columns,
the data processing includes a retrieval processing and/or a statistical processing targeted at least a part of the attribute items of the integrated data, and
the decryption request unit (<NUM>) requests one of the plurality of data providing servers to decrypt the execution result by a decryption key managed by the one of the plurality of data providing servers, the one of the plurality of data providing servers providing the sensitive data including the attribute items to which the data processing is executed.