WO2023188136A1 - System, distribution control server, distribution control server control method, and storage medium - Google Patents

System, distribution control server, distribution control server control method, and storage medium Download PDF

Info

Publication number
WO2023188136A1
WO2023188136A1 PCT/JP2022/016081 JP2022016081W WO2023188136A1 WO 2023188136 A1 WO2023188136 A1 WO 2023188136A1 JP 2022016081 W JP2022016081 W JP 2022016081W WO 2023188136 A1 WO2023188136 A1 WO 2023188136A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
server
provision
information
Prior art date
Application number
PCT/JP2022/016081
Other languages
French (fr)
Japanese (ja)
Inventor
雄亮 佐藤
由梨香 道下
泰正 光畑
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to PCT/JP2022/016081 priority Critical patent/WO2023188136A1/en
Publication of WO2023188136A1 publication Critical patent/WO2023188136A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services

Definitions

  • the present invention relates to a system, a distribution control server, a distribution control server control method, and a storage medium.
  • Patent Document 1 states that an intermediary company (data distribution control device) receives data collection compensation from a data utilization company.
  • the data collection consideration in Patent Document 1 is compensation for providing data paid by a data utilization company.
  • the intermediary company pays data intermediary fees, data provision fees (individuals), and data provision fees (company) based on the consideration for data collection from data utilization companies.
  • Data brokerage fees are compensation paid to intermediary companies for data brokerage.
  • Data provision fee (individuals) is compensation paid to each individual who is a data subject for providing data.
  • Data provision fees (company) are compensation paid to each data providing company for providing data. In this way, data flow is promoted by providing incentives to data intermediaries, individuals (data subjects), and data providers (holders).
  • the information transaction device of Patent Document 2 stores catalog information including detailed information regarding one or more datasets including personal information that can be provided from an information provider device to an information destination device.
  • the information transaction device receives a data set provision request from the information provision destination device.
  • the information transaction device outputs a request to transmit the data set indicated by the provision request to the information provider device.
  • JP2020-129311A International Publication No. 2021/085061
  • Patent Document 1 and Patent Document 2 do not take into consideration the cost of allowing personal data to be provided to a third party.
  • the main purpose of the present invention is to provide a system, a distribution control server, a control method for a distribution control server, and a storage medium that contribute to further development of an information distribution system.
  • a service server operated by a service provider that stores user data generated by providing services to users
  • the distribution control server includes a utilization server and a distribution control server operated by an information distribution business, and the distribution control server stores data for registering the user data in the information distribution system as data that can be provided to a third party. control the data provision for providing the user data registered by the data storage from the service server to the data utilization server, and provide the service provider and the user with the data storage for the data storage.
  • a system is provided that performs control for the information distribution business to pay compensation and receive compensation for the data provision from the data utilization business.
  • a service provider controls data accumulation for registering user data generated by providing services to users in an information distribution system as data that can be provided to a third party.
  • an accumulation control unit, and a data provision unit for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization operator.
  • a data distribution control unit that controls, and controls for the information distribution business operator to pay accumulation consideration for the data storage to the service provider and the user, and for the information distribution business operator to receive the provision consideration for the data provision from the data utilization business operator.
  • a distribution control server is provided, which includes a payment control unit that performs payment processing.
  • the distribution control server user data generated when a service provider provides a service to a user is registered in the information distribution system as data that can be provided to a third party.
  • control data accumulation and provide data for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider.
  • a distribution control server that performs control such that the information distribution business operator receives compensation for the data provision from the data utilization business operator, and pays the service provider and the user compensation for storing the data;
  • a control method is provided.
  • information distribution is performed in a computer installed in a distribution control server, using user data generated when a service provider provides a service to a user as data that can be provided to a third party.
  • a computer-readable storage medium is provided that stores a program for controlling the process and executing the process.
  • a system a distribution control server, a control method for a distribution control server, and a storage medium are provided that contribute to further development of an information distribution system.
  • the effects of the present invention are not limited to the above. According to the present invention, other effects may be achieved instead of or in addition to the above effects.
  • FIG. 1 is a diagram for explaining an overview of one embodiment.
  • FIG. 2 is a flowchart illustrating an example of the operation of one embodiment.
  • FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment.
  • FIG. 4 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 5 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 6 is a diagram illustrating an example of the accumulation consideration definition according to the first embodiment.
  • FIG. 7 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 8 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 1 is a diagram for explaining an overview of one embodiment.
  • FIG. 2 is a flowchart illustrating an example of the operation of one embodiment.
  • FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment.
  • FIG. 9 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 10 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 11 is a diagram showing an example of catalog information according to the first embodiment.
  • FIG. 12 is a diagram illustrating an example of the provided consideration definition according to the first embodiment.
  • FIG. 13 is a diagram showing an example of a data provision application according to the first embodiment.
  • FIG. 14 is a diagram for explaining the operation of the information distribution system according to the first embodiment.
  • FIG. 15 is a diagram illustrating an example of the processing configuration of the distribution control server according to the first embodiment.
  • FIG. 16 is a diagram showing an example of a part of the user information database according to the first embodiment.
  • FIG. 17 is a diagram illustrating an example of the location information database according to the first embodiment.
  • FIG. 18 is a diagram showing an example of the accumulated transaction management database according to the first embodiment.
  • FIG. 19 is a diagram illustrating an example of the provided transaction management database according to the first embodiment.
  • FIG. 20 is a diagram illustrating an example of the processing configuration of the service server according to the first embodiment.
  • FIG. 21 is a diagram showing an example of the customer information database according to the first embodiment.
  • FIG. 22 is a diagram showing an example of the processing configuration of the transaction server according to the first embodiment.
  • FIG. 23 is a diagram illustrating an example of an account opener list according to the first embodiment.
  • FIG. 24 is a diagram illustrating an example of a processing configuration of a terminal according to the first embodiment.
  • FIG. 24 is a diagram illustrating an example of a processing configuration of a terminal according to the first embodiment.
  • FIG. 25 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment.
  • FIG. 26 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment.
  • FIG. 27 is a diagram illustrating an example of the hardware configuration of a distribution control server according to the present disclosure.
  • the system includes a service server 101, a data utilization server 102, and a distribution control server 103 (see FIG. 1).
  • the service server 101 is operated by a service provider and stores user data generated by providing services to users.
  • the data utilization server 102 is operated by a data utilization business.
  • the distribution control server 103 is operated by an information distribution business.
  • the distribution control server 103 controls data accumulation for registering user data in the information distribution system as data that can be provided to a third party (step S1 in FIG. 2).
  • the distribution control server 103 controls data provision for providing user data registered through data accumulation from the service server 101 to the data utilization server 102 (step S2).
  • the distribution control server 103 pays the service provider and the user an accumulation fee for data accumulation (step S3).
  • the distribution control server 103 performs control for the information distribution business to receive compensation for providing data from the data utilization business (step S4).
  • the information distribution business pays compensation for data storage to the data storage operator (the service business providing services to the user) and the user.
  • the data provider can earn revenue before the data provider (service provider) and the data provider (data utilization provider) conclude a data provision contract.
  • the information distribution business receives a portion of the consideration paid by the data provider, thereby recovering the consideration paid in advance for data accumulation.
  • the information distribution system pays the data provider the price for data storage, allowing the data provider to quickly recover its investment in data storage.
  • the hurdles for data providers to enter the information distribution system will be lowered, more data providers will participate in the system, and the information distribution system will further develop.
  • the information distribution system disclosed herein reduces the burden on data providers by having the information distribution business pay compensation for data accumulation to service providers and individuals involved in data accumulation. Furthermore, the information distribution system encourages individuals to accumulate data such as sensitive personal information by paying compensation for data accumulation.
  • Basic risk 1 is that the actual status of data providers (such as the number of data providers) is unknown at the stage of considering whether or not the data provider will participate in the system.
  • Basic risk 2 is that at the stage when a data provider is considering whether to participate in the system, it is unclear how many users will consent to the accumulation of data.
  • cost risk 1 is that the timing of recovering the cost of preparing a data set for third party provision is after the data provision contract is fulfilled.
  • Cost risk 2 is that the timing of recovering the cost of repairing business operations and owned systems is after the data provision contract is fulfilled.
  • Cost risk 3 is that the timing of setting fees for users, considering payment methods, and revising implementation costs is after the data provision contract has been fulfilled.
  • the information distribution system disclosed herein eliminates or reduces the basic risk and cost risk by paying compensation for data accumulation to the data provider before providing the data.
  • FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment.
  • participating members (actors) of the information distribution system include information distribution businesses, service businesses, data utilization businesses, and trading businesses.
  • An information distribution business is a business that provides a platform for data distribution services (information distribution services) for personal data accumulated by service providers.
  • the information distribution business operator controls data distribution between businesses (service businesses, data utilization businesses).
  • the information distribution business includes a distribution control server 10.
  • the distribution control server 10 is operated by an information distribution business.
  • the distribution control server 10 is a server device that controls (realizes) data distribution between service providers and controls data distribution between service providers and data utilization providers.
  • the distribution control server 10 realizes an information distribution service for data held by a service provider.
  • a service provider is an entity that provides services to individuals.
  • the service provider may be a private company or a public institution.
  • Examples of service providers include medical institutions (hospitals, pharmacies, etc.) that provide medical services to users, retailers, and educational providers that teach languages, sports, art, etc. to customers.
  • Each service provider includes a service server 20 for providing services to customers.
  • the service server 20 is managed and operated by a service provider.
  • the service server 20 holds (stores) data generated when a service provider provides a service to a user, data necessary for providing a service to a user, and the like.
  • a service provider maintains user data regarding services provided to users.
  • a data utilization business is an entity that does not provide services directly to individuals.
  • Examples of data utilization businesses include businesses such as pharmaceutical companies.
  • a pharmaceutical company develops a new drug using data obtained from a service provider.
  • an entity that does not provide services to individuals will be treated as a "data utilization business entity” and explained, but when a data utilization business entity provides services to users, it will be referred to as a “service business entity”. It is natural to behave. In other words, depending on the business form of the data utilization business, the data utilization business can also become a service provider.
  • the data utilization business is equipped with a data utilization server 30 for acquiring and utilizing data from the service business.
  • the data utilization server 30 is operated by a data utilization business.
  • a transaction business operator is an entity that realizes a transaction between a service business operator and a data utilization business operator. Transaction operators realize data distribution between data generators (service operators) and data consumers (data utilization operators).
  • the transaction business operator is equipped with a transaction server 40 for realizing the data distribution.
  • a user who uses the information distribution system uses a terminal 50.
  • the devices shown in FIG. 3 are interconnected via a network.
  • the distribution control server 10 and the service server 20 are connected by wired or wireless communication means and configured to be able to communicate with each other.
  • an information distribution business may include two or more distribution control servers 10.
  • the information distribution system includes data usage servers 30 and transaction servers 40 according to the number of businesses participating in the system.
  • a user requests to enter into a new contract (a contract for enjoying a service) with a service provider while providing his/her name, etc. to the service provider.
  • a user who wants to visit a hospital submits his or her health insurance card with his or her name written on it to the hospital.
  • the user accesses the service server 20 operated by the EC business and creates an account.
  • the service provider generates a "personal identification ID" for identifying new customers (users). For example, a hospital assigns a consultation ticket number for managing users (patients) and generates the consultation ticket number as a personal identification ID.
  • the EC business generates a membership number or the like as a personal identification ID for managing customers.
  • the service server 20 stores the generated personal identification ID (eg, medical card number, membership number, etc.) in a database or the like.
  • the user can receive services from the service provider. For example, a user receives medical services (health checkup, medical examination, etc.) from a hospital. Alternatively, the user performs online shopping using an EC company.
  • medical services health checkup, medical examination, etc.
  • Data accumulation means that a service provider (user data provider) registers user data in an information distribution system as data that can be provided to a third party.
  • the distribution control server 10 controls data accumulation so that data related to services provided to users by a data accumulator (service provider) is targeted for data distribution. That is, the distribution control server 10 controls data accumulation for registering user data in the information distribution system as data that can be provided to a third party.
  • the accumulated data will be subject to data distribution. Furthermore, the accumulation of user data requires the consent of the user (the user from whom the user data was generated) (consent to data accumulation).
  • Storage is the subject of information distribution (data distribution) to user data held by a service provider, and a fee is paid to the user who consents to the storage. Compensation will also be paid to service providers that hold the accumulated data (user data of users who have consented to the use of their data). Compensation for data storage is paid by the information distribution system (information distribution business) to the data storage person and the user.
  • the distribution control server 10 controls data sharing for sharing user data registered through data accumulation from one service server 20 to another service server 20.
  • the distribution control server 10 controls data provision for providing user data registered through data accumulation from the service server 20 to the data utilization server 30.
  • “Sharing” is a means for service providers to acquire data accumulated by other service providers. For example, data distribution through “sharing” is used when an EC business acquires data generated by a hospital providing services to users. EC businesses use data acquired from hospitals through data sharing to provide better services to users.
  • “Sharing” is used to improve the convenience of service users themselves, so no compensation is paid to users for data distribution (compensation to users). This is because “sharing” is used for users to utilize data accumulated by other service providers in order to receive better services from service providers.
  • Provision is a means for a data utilization business to acquire data accumulated by other service businesses. For example, when a pharmaceutical company obtains the results of a medical examination or medical examination from a hospital, data distribution through “provision” is used. Pharmaceutical companies use the data they obtain from hospitals to help develop new drugs.
  • Provision is a method used by data utilization businesses that do not directly provide services to users, so compensation for data distribution (compensation for users) will be incurred. That is, when “provision” is performed, consideration is paid to the user. Furthermore, when “provision” is performed, a consideration is paid from the data acquirer (data provider) to the data provider (data accumulator) and the information distribution system (information distribution business).
  • the distribution control server 10 controls data sharing for data sharing destinations (service providers receiving data supply) to acquire accumulated data.
  • the distribution control server 10 controls data provision for a data provision destination (a data utilization business that receives data supply) to acquire accumulated data.
  • the account generated in the information distribution system will be referred to as a "system account.”
  • the user operates the terminal 50 in his possession to access the distribution control server 10.
  • the distribution control server 10 displays a WEB page for generating a system account.
  • the user performs an operation (for example, pressing a predetermined button) to generate a system account.
  • the distribution control server 10 acquires information necessary for generating the user's system account. Specifically, the distribution control server 10 acquires the user's login information (login ID, password) and personal information (name, date of birth, contact information, account information, etc.).
  • the distribution control server 10 Upon acquiring login information, personal information, etc., the distribution control server 10 generates a user ID (Identifier) for uniquely identifying the user in the information distribution system.
  • a user ID Identifier
  • the distribution control server 10 associates and stores the generated user ID, login information, personal information (for example, name, date of birth, contact information), etc. of the user.
  • the distribution control server 10 stores this information in a "user information database.” Details of the user information database will be described later.
  • the distribution control server 10 issues the generated user ID to the user (terminal 50).
  • the terminal 50 stores the issued user ID.
  • a user goes to a hospital counter and tells hospital staff that he or she wishes to utilize user data held by the hospital (applies for data utilization).
  • the hospital staff inputs the user's personal identification information, the user's personal identification ID (eg, medical card number), and the company code into the hospital terminal 60.
  • the user's personal identification ID eg, medical card number
  • personal identification information is information for identifying the user. Examples of the personal identification information include the user's name or a combination of name and date of birth.
  • the business code is identification information (ID) for identifying a service business that participates in the information distribution system. For example, different codes are assigned to hospitals and e-commerce businesses.
  • ID identification information
  • the business code is shared among system participants (information distribution business, service business, data utilization business) by any means. For example, when a service provider participates in an information distribution system, the information distribution provider generates a provider code to be assigned to the service provider. The information distribution business operator notifies the service business operator, etc. of the generated business code.
  • the hospital terminal 60 transmits an "ID cooperation request" including the acquired personal identification information, personal identification ID, and business code to the distribution control server 10.
  • a user who wishes to utilize the user data of an EC company operates the terminal 50 to access the service server 20 of the EC company (see FIG. 5).
  • the user logs into the EC company's account and applies for data utilization on the account.
  • the service server 20 transmits an "ID cooperation request" including the user's personal identification information, personal identification ID, and business code to the distribution control server 10.
  • the distribution control server 10 receives, from the hospital terminal 60 and the service server 20, the personal identification information of the person requesting ID cooperation, the personal identification ID, and the company code of the service provider (for example, hospital, e-commerce company) that is the target of ID cooperation. get.
  • the service provider for example, hospital, e-commerce company
  • the distribution control server 10 identifies the service provider targeted for ID cooperation from the provider code. Further, the distribution control server 10 identifies the user registered in the system account from the personal identification information. The distribution control server 10 associates the service provider with the personal identification ID in the account of the identified user.
  • ID linkage Once the personal identification ID is registered in the system account (ID linkage is completed), the service provider targeted for ID linkage will be able to "accumulate" user data of users who wish to utilize the data.
  • the accumulated consideration definition includes an accumulated consideration ID for identifying the accumulated consideration definition, a data set (data type) for which consideration is to be paid, and an information distribution system (information distribution business) by accumulating one data. Includes the consideration paid by the person (individual) and the distribution rate of the consideration.
  • the data type for which compensation is to be paid is the type of user data to be accumulated.
  • the accumulation consideration definition is determined in advance for each data type.
  • the distribution rate of consideration is the distribution rate between the service provider and the user of the consideration paid by the information distribution business.
  • FIG. 6 shows that when data classified as "disease name" is stored, a compensation of 10 yen is paid to the data storage person and the user. Further, FIG. 6 shows that 80% of the consideration is paid to the data accumulator (hospital, etc.) and 20% is paid to the user.
  • the service provider When a service provider provides a service to a user, the service provider stores the user's personal identification ID and user data (personal data) in association with each other. For example, when a hospital examines a user and obtains the name of the disease, the hospital stores the user's personal identification ID (examination ticket number, etc.) in association with the disease name (for example, a specific disease name such as stomach cancer).
  • the service server 20 uses a "customer information database" to store the user's personal identification ID and user data in association with each other. Note that details of the customer information database will be described later.
  • the service server 20 of the service provider stores user data (data generated as a result of service provision, data necessary for service provision) regarding a user who has completed ID linkage (a user who has applied for data utilization), In addition, controls related to data accumulation are performed.
  • the service server 20 specifies the user who has acquired the user data, and requests the distribution control server 10 to obtain consent regarding data storage.
  • the service server 20 transmits a "storage consent acquisition request" including the user's personal identification ID, business code, and information regarding the user data to be stored (user data information) to the distribution control server 10 (step S01 in FIG. 7). ).
  • the user data information includes the type of user data (for example, disease name) acquired by the service provider (service server 20), the date and time of acquisition of the data, and the like.
  • the distribution control server 10 Upon receiving the accumulation consent acquisition request, the distribution control server 10 identifies the user based on the personal identification ID and the business code. The distribution control server 10 transmits a data storage inquiry including user data information etc. to the specified user (step S02).
  • the terminal 50 that has received the data storage inquiry acquires the user's intention regarding data storage. For example, the terminal 50 uses a GUI (Graphical User Interface) to obtain the user's intention. For example, the terminal 50 displays the user's intention (agree or disapprove to the data storage) using a GUI that says, "Do you agree to the storage of the disease name obtained from the medical examination on April 1, 2021?" get.
  • GUI Graphic User Interface
  • the terminal 50 may present the user with compensation for data accumulation, which is obtained based on the accumulation compensation definition published by the distribution control server 10.
  • the terminal 50 transmits a response to the data storage inquiry (agreeing to data storage or refusing data storage) to the distribution control server 10 (step S03).
  • the distribution control server 10 transfers the response to the data storage inquiry obtained from the terminal 50 to the service server 20.
  • the distribution control server 10 transmits the response obtained from the terminal 50 to the service server 20 as a response to the storage consent acquisition request (step S04).
  • the service server 20 when it stores user data in response to providing a service to the user, it transmits a storage consent acquisition request including information regarding the user data to the distribution control server 10.
  • the distribution control server 10 transmits a data storage inquiry including information regarding user data to a terminal 50 owned by the user, and receives a response to the data storage inquiry from the terminal 50.
  • the distribution control server 10 transfers the received response to the service server 20.
  • the service server 20 does not take any special action.
  • the service server 20 registers the user data of the user who has consented to the data accumulation in the information distribution system as accumulated data. Specifically, the service server 20 transmits "location information" regarding users who have consented to data storage to the distribution control server 10 (see FIG. 8).
  • the location information is information regarding the storage location of user data (data storage entity; service provider), etc.
  • the location information includes a data ID for identifying user data (accumulated data), a personal identification ID, a business code, the type of data held, and the like.
  • the distribution control server 10 stores the acquired location information in the "location information database.” Details of the location information database will be described later.
  • the location information database stores data ID, personal identification ID, business code, data type, etc. in association with each other.
  • the distribution control server 10 registers the history of accumulated transactions in the transaction ledger.
  • the distribution control server 10 pays compensation for data accumulation at a predetermined timing (for example, at the beginning of the month) based on the history of accumulation transactions.
  • the distribution control server 10 pays remuneration to the data accumulator and user based on the published accumulation remuneration definition.
  • the service server 20 transmits location information including the data type of the user data stored in the service server 20 to the distribution control server 10.
  • the distribution control server 10 stores user data in response to receiving the location information. Thereafter, the distribution control server 10 pays the service provider and the user an accumulation fee for data accumulation. At this time, the distribution control server 10 calculates the accumulated consideration to be paid to the service provider and the user based on the accumulated consideration definition.
  • EC company B acquires user data (medical examination results; disease name) accumulated in hospital A by "sharing".
  • hospital is equipped with a service server 20-1
  • the EC business is equipped with a service server 20-2.
  • EC business operator B (service server 20-2) transmits a "sharing request" to distribution control server 10 (step S11).
  • the distribution control server 10 Based on the sharing request, the distribution control server 10 identifies the user who is the target of data distribution and the data storage person (hospital A) of the data to be distributed. The distribution control server 10 transmits an inquiry regarding data sharing to the terminal 50 owned by the identified target person (step S12).
  • the terminal 50 that has received the data sharing inquiry acquires the user's intention regarding data sharing.
  • the terminal 50 uses a GUI (Graphical User Interface) to obtain the user's intention.
  • GUI Graphic User Interface
  • the terminal 50 displays a GUI that says, "You can receive better service by sharing your hospital examination results with the e-commerce company. Do you want to share?” and displays the user's intention. (Agree/disagree to data sharing).
  • the terminal 50 transmits a response to the data sharing inquiry (agreeing to data sharing or refusing data sharing) to the distribution control server 10 (step S13).
  • the distribution control server 10 transmits a sharing instruction to the data storage person (hospital A) (step S14).
  • Hospital A which received the sharing instruction, refers to the customer information database and sends the examination results (disease name) of the target user to the service server 20-2, which is the designated data sharing destination. Transmit (step S15).
  • the transaction business operator forms an alliance with at least one service business operator among the multiple service business operators participating in the information distribution system. For example, a trading company that handles medical data collaborates with medical institutions (hospitals, pharmacies, etc.). Alternatively, a trading business that handles education-related data collaborates with an education business.
  • the transaction business operator stores a business code related to the partner service business operator.
  • the transaction business operator stores the business code of the data utilization business operator. For example, when a trading business starts a transaction with a data utilization business, it generates a business code of the data utilization business.
  • the business code of the data utilization business is shared among the information distribution business, transaction business, and data utilization business by any method.
  • the trading business entity sells the data (accumulated data) held by the partner service business entity to the data utilization business entity (acts as an intermediary in the sale).
  • the affiliated service provider shown in FIG. 10 is a medical institution
  • the transaction provider sells data held by the affiliated medical institution to a pharmaceutical company or the like.
  • transaction server 40 a user who wishes to obtain consideration by providing data through a transaction operator needs to open an account with the transaction operator (transaction server 40).
  • transaction server 40 Among the users who participate in the information distribution system, those who wish to earn profits by providing data open an "information account" in the transaction server 40.
  • the user presents the user ID issued by the distribution control server 10 to the transaction server 40 and opens an information account.
  • Transaction server 40 stores the acquired user ID.
  • the transaction server 40 manages user IDs of users who have opened accounts using an account opener list.
  • catalog information In order to realize data distribution by "provision", information distribution businesses prepare catalog information. The person in charge (system administrator) of the information distribution business defines catalog information that describes data that can be sold (see FIG. 11). Catalog information is information indicating details of data that the information distribution system can sell to data utilization businesses.
  • the data set name included in the catalog information shown in FIG. 11 is information for identifying the catalog information. For example, a data set related to a medical examination is given a data set name such as "Examination Results 1", and a data set related to medical examination results is given a data set name such as "Examination Results 1".
  • the data type included in the catalog information indicates the type of data held by the service provider (accumulated data that can be provided to a third party). For example, information such as “height”, “weight”, and “blood pressure” in the medical examination results, and “disease name”, “medication taking”, and “examination results” in the medical examination results correspond to the data type.
  • the data format defines the format in which data is provided.
  • the data utilization business obtains catalog information through the transaction business. More specifically, the data utilization server 30 transmits a “catalog information presentation request” to the transaction server 40.
  • the transaction server 40 Upon receiving the catalog information presentation request, the transaction server 40 transmits a "catalog information transmission request" to the distribution control server 10.
  • the distribution control server 10 transmits catalog information defined by the information distribution business to the transaction server 40.
  • the transaction server 40 selects catalog information regarding the partner service provider and transmits it to the data utilization server 30.
  • the transaction server 40 selects catalog information related to the business of a pharmaceutical company and transmits it to the data utilization business.
  • the data utilization business views the received catalog information and identifies the catalog information necessary for its own business.
  • Provision A data utilization business that wishes to acquire data accumulated by a service business will acquire the data through "provision.”
  • the distribution control server 10 publishes the registered standard of the provided consideration as a "provided consideration definition" (see FIG. 12).
  • the provided consideration definition includes the provided consideration ID for identifying the provided consideration definition, the data set (data type) for which consideration is to be paid, and the data provider (pharmaceutical company) by providing one data. Includes the consideration paid from C) and the distribution rate of the consideration.
  • the data type for which compensation is to be paid is the data type of the provided user data.
  • the distribution rate of consideration is the distribution rate of the consideration paid by the data utilization business to the service business, the user, and the distribution business.
  • FIG. 12 shows that if you provide the "disease name" data, a compensation of 15 yen will be paid by the data provider.
  • Figure 12 shows that 70% of the compensation obtained is paid to the data accumulator (hospital, etc.), 20% is paid to the user, and 10% is paid to the information distribution business (information distribution system consortium). Indicates that it will be paid.
  • Employees of the data provider refer to the published catalog information and provision consideration definition and create a data provision application.
  • a staff member or the like inputs a data provision application as shown in FIG. 13 into the data utilization server 30.
  • the data provision application includes requirements for the provided data to be provided to the data utilization business as a result of the data provision, and a provision consideration presentation that includes details regarding the presentation of the provision consideration to be paid by the data utilization business as a result of the data provision. .
  • the data provision application includes information on the business requesting data provision, the type of data to be provided, the amount of data desired to be obtained, the consideration to be paid by the data provider, and the amount of consideration. Including distribution rate.
  • Information regarding the business entity requesting data provision includes the name of the business entity, business code, data provision destination (data transmission destination address), etc. .
  • the data utilization server 30 transmits a data provision application to the transaction server 40 (step S21).
  • the transaction server 40 that receives the data provision application assigns a provision application ID to the data provision application and manages the received data provision application. Thereafter, the transaction server 40 transmits a "provision request" including the provision application ID, data provision application, and account opener list to the distribution control server 10 (step S22).
  • the distribution control server 10 In response to receiving the provision request, the distribution control server 10 notifies the data provider (data accumulator) and obtains the user's consent regarding the data provision.
  • the distribution control server 10 refers to the location information database and identifies the data accumulator (data provider) that holds the data type described in the data provision application.
  • the distribution control server 10 notifies the transaction server 40 of information regarding the identified data accumulator. Specifically, the distribution control server 10 transmits a "provider notification" including the provision application ID, the name of the identified data storage person, contact information (address of the service server 20), etc. to the transaction server 40 (step S23). ).
  • the distribution control server 10 stores the personal identification IDs of users who are listed in the account opener list and who contributed to (related to) the generation of accumulated data corresponding to the type of data to be provided. Identify.
  • the distribution control server 10 transmits an inquiry regarding data provision to the contact information (email address that can be received by the terminal 50) of the user corresponding to the specified personal identification ID (step S24).
  • the data provision inquiry includes information on the data provision requestor (in the above example, pharmaceutical company C), information on the data storage person (hospital A), and the type of data requested to be provided (for example, disease name).
  • the terminal 50 that has received the inquiry for data provision displays a GUI for acquiring the user's intention regarding data provision.
  • the terminal 50 uses the GUI to obtain the user's intention (agree or disapprove to data provision).
  • the terminal 50 transmits a response to the data provision inquiry (agreeing to the data provision or refusing the data provision) to the distribution control server 10 (step S25).
  • the distribution control server 10 identifies the user to whom the data is to be provided, and sends a data provision inquiry to the terminal 50 of the identified user. Obtain whether the user agrees to the provision or not. Further, the distribution control server 10 specifies a service provider that stores user data to which the data is to be provided, and transmits a provider notification containing information on the identified service provider to the transaction server 40.
  • the transaction server 40 receives the provider notification and requests the service provider specified by the distribution control server 10 to conclude a data provision application contract with the data utilization provider. Specifically, the transaction server 40 sends a “provision contract conclusion request” including the provision application ID and data provision application to the contact information notified from the distribution control server 10 (for example, the service server 20-1 of hospital A). (Step S26).
  • the data accumulator In response to receiving a request to conclude a provision contract, the data accumulator negotiates with the data provider (data utilization business) regarding data provision.
  • a staff member of the data storage company inputs the results of examining the data provision application into the service server 20.
  • the service server 20 transmits a response to the request for conclusion of a provision contract to the transaction server 40 in accordance with the obtained examination result (step S27).
  • the service server 20 transmits an affirmative response to the transaction server 40 indicating that the service server 20 accepts the data provision application (concludes a data provision contract).
  • the service server 20 transmits a negative response to the transaction server 40 indicating that the service server 20 does not accept the data provision application (not concluding a data provision contract).
  • the transaction server 40 stores that the data transaction application contract has been established. Further, the transaction server 40 notifies the distribution control server 10 and the data utilization server 30 that the contract for the data provision application has been concluded. Specifically, the transaction server 40 transmits a "provision contract establishment notification" including the provision application ID to the distribution control server 10 and the data utilization server 30 (step S28).
  • the transaction server 40 If a negative response is received (if the data provision contract is not established), the transaction server 40 notifies the data utilization server 30 that the contract for the data provision application is not established.
  • the data utilization server 30 transmits a "provision contract cancellation notification" including the provision application ID to the transaction server 40 (not shown in FIG. 14).
  • the transaction server 40 transfers the received provision contract cancellation notice to the distribution control server 10.
  • the staff of the data utilization business When applying for data provision again, the staff of the data utilization business enters the data provision application with new conditions into the data utilization server 30.
  • the data utilization server 30 transmits a new data provision application to the transaction server 40.
  • the transaction server 40 transmits a data provision contract conclusion request including a new data provision application to the service server 20.
  • the data accumulator examines the presented new conditions and notifies the data provider of the results of the examination via the transaction server 40.
  • the data accumulator and the data provider repeat price negotiations as described above.
  • the distribution control server 10 Upon receiving the provision contract establishment notification, the distribution control server 10 transmits a provision instruction to the data accumulator (hospital A) regarding the user who has consented to data provision (step S29). As described above, when the provision of five disease name data is requested, the distribution control server 10 transmits a provision instruction regarding the five disease name data to the service server 20-1. For example, the distribution control server 10 instructs the service server 20-1 to provide disease names for five users.
  • Hospital A which has received the provision instruction, refers to the customer information database and transmits the user data of the consenting user to the specified data provision destination (step S30).
  • the distribution control server 10 transmits the user data to the service server 20 when the user agrees to provide the data and a contract regarding the data provision application is established between the service provider and the data utilization provider. to the data utilization server 30.
  • the distribution control server 10 registers the history of supply transactions in the transaction ledger.
  • the distribution control server 10 requests the data provider to pay for the data provision based on the history of the provision transaction.
  • the distribution control server 10 pays the data accumulator and the user compensation for providing the data at a predetermined timing (for example, at the beginning of the month).
  • the distribution control server 10 makes payments to the data accumulator (data provider) and the user based on conditions (compensation) agreed upon between the parties.
  • the distribution control server 10 performs control for the information distribution business to receive compensation for providing data from the data utilization business. Specifically, in response to an instruction to the service server 20 to send user data to the data utilization server 30, the distribution control server 10 transmits the data provision application for which the contract was established and the data provision transaction history. remember. The distribution control server 10 calculates the provision consideration based on the requirements for the provision data of the data provision application for which the contract has been established and the provision consideration presentation.
  • FIG. 15 is a diagram showing an example of a processing configuration (processing module) of the distribution control server 10 according to the first embodiment.
  • the distribution control server 10 includes a communication control section 201, a user registration section 202, an ID cooperation section 203, a consideration definition disclosure section 204, and an accumulation consent control section 205. Further, the distribution control server 10 includes a location information management section 206, a data distribution control section 207, a catalog information management section 208, a payment control section 209, and a storage section 210.
  • the communication control unit 201 is a means for controlling communication with other devices.
  • the communication control unit 201 receives data (packets) from the service server 20. Furthermore, the communication control unit 201 transmits data to the service server 20.
  • the communication control unit 201 passes data received from other devices to other processing modules.
  • the communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 201.
  • the communication control unit 201 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.
  • the user registration unit 202 is a means for realizing the above-mentioned user registration (user system registration).
  • the user registration unit 202 acquires personal information (name, date of birth, contact information, account information, etc.) from the user's terminal 50.
  • the user registration unit 202 Upon acquiring the personal information, the user registration unit 202 generates a user ID for identifying the user. For example, the user registration unit 202 assigns a unique number each time a user registers with the system, and uses the assigned value as the user ID.
  • the user registration unit 202 stores the user ID and personal information in the user information database (see FIG. 16).
  • the user information database stores user IDs, personal information, and personal identification IDs for each service provider in association with each other.
  • the user information database shown in FIG. 16 is an example, and is not intended to limit the items to be stored.
  • the date and time of user registration may be registered in the user information database.
  • the user registration unit 202 transmits the generated user ID to the terminal 50.
  • the ID cooperation unit 203 is a means for realizing the above-mentioned ID cooperation.
  • the ID collaboration unit 203 receives an “ID collaboration request” from a service provider's terminal (for example, the hospital terminal 60) or the service server 20.
  • the ID cooperation request includes personal identification information, personal identification ID, and company code of the user who desires ID cooperation (registration of service provider).
  • the ID collaboration unit 203 searches the user information database using personal identification information (user's name, combination of name and date of birth, etc.) as a key, and identifies the corresponding user.
  • the ID cooperation unit 203 sets the personal identification ID included in the ID cooperation request in the field corresponding to the business code in the personal identification ID field of the identified user. That is, the ID cooperation unit 203 identifies the user registered in the system account from the personal identification information, and associates the service provider with the personal identification ID in the account of the identified user.
  • the consideration definition publishing unit 204 is a means for publishing the accumulated consideration definition and the provided consideration definition.
  • the consideration definition publishing unit 204 acquires the accumulated consideration definition shown in FIG. 6 and the provided consideration definition shown in FIG. 12 in response to operations by employees of the information distribution business.
  • the consideration definition publishing unit 204 publishes the acquired accumulated consideration definition and provided consideration definition. For example, the consideration definition publishing unit 204 posts the accumulated consideration definition and the provided consideration definition on the homepage.
  • the storage consent control unit 205 is a means for controlling consent for data storage.
  • the storage consent control unit 205 receives a storage consent acquisition request from the service server 20.
  • the storage consent control unit 205 refers to the user information database and identifies the user whose consent is to be obtained based on the personal identification ID and business code included in the received storage consent acquisition request.
  • the storage consent control unit 205 specifies the user shown in the first line of FIG. do.
  • the storage consent control unit 205 sends a data storage inquiry to the specified user's contact information (such as an e-mail address that can be received by the terminal 50).
  • the data storage inquiry includes information on the service provider who requested consent for data storage (for example, the name of the company), user data information (data type of data for which consent was obtained, date and time of acquisition), etc.
  • the storage consent control unit 205 receives a response to the data storage inquiry from the user's terminal 50.
  • the storage consent control unit 205 transmits (transfers) the acquired response to the service server 20.
  • the location information management unit 206 is a means for managing location information obtained from a service provider.
  • the location information management unit 206 processes location information and stores user data generated when a service provider provides a service to a user in order to register it in an information distribution system as data that can be provided to a third party. control.
  • the location information management unit 206 operates as an “accumulation control unit”.
  • the location information management unit 206 stores the location information acquired from each service server 20 in the location information database (see FIG. 17). As shown in FIG. 17, the location information database stores personal identification ID, business code, data ID, data type, data storage date, etc. in association with each other.
  • location information database shown in FIG. 17 is an example, and is not intended to limit the items to be stored. Further, in the drawings including FIG. 17, for ease of understanding, the provider code is expressed using the name of the service provider.
  • the location information management unit 206 records the history of accumulated transactions in the transaction ledger every time data is registered in the location information database. Specifically, the location information management unit 206 adds an entry to the accumulated transaction management database every time it processes the location information received from the service server 20 (see FIG. 18).
  • the location information management unit 206 stores the user ID, operator code, data ID, data type of accumulated data, data accumulation date, and accumulation consideration definition of the user corresponding to the processed location information.
  • the IDs are associated and stored.
  • the location information management unit 206 obtains the accumulated consideration ID by referring to table information that stores data types and accumulated consideration IDs in association with each other.
  • the data distribution control unit 207 is a means for controlling data distribution by "sharing” or “providing".
  • the data distribution control unit 207 receives a sharing request from the service server 20.
  • the sharing request includes the personal identification ID of the user whose data is to be obtained, the provider code of the source of the sharing request, and the type of data desired to be obtained.
  • the sharing request includes the personal identification ID generated for the user by EC company B (service server 20-2), the company code of EC company B, and "disease name" as the data type. .
  • the data distribution control unit 207 identifies the data distribution target based on the personal identification ID and business code included in the sharing request. Specifically, the data distribution control unit 207 refers to the user information database shown in FIG. 16 and identifies the target person. In the above example, upon receiving a sharing request including the personal identification ID "EC01" from EC business operator B, the data distribution control unit 207 determines that user U1 is the target of data distribution from the entry in the first line shown in FIG. Understand that you are a person.
  • the data distribution control unit 207 uses the identified user's personal identification ID and the data type included in the sharing request to identify the service provider that has accumulated the necessary data. Specifically, the data distribution control unit 207 refers to the location information database shown in FIG. 17 and identifies a service provider that accumulates data corresponding to the data type included in the sharing request. In the above example, the hospital A is specified based on the personal identification ID "HL01" of the user U1 and the data type "disease name" included in the sharing request.
  • the data distribution control unit 207 instructs the sender of the sharing request that data sharing is not possible. send a negative response indicating
  • EC business operator B service server 20-2
  • the data distribution control unit 207 makes an inquiry to the data distribution target regarding data sharing. Specifically, the data distribution control unit 207 sends an inquiry regarding data sharing to the contact information of the data distribution target person. In the above example, the inquiry is sent to the terminal 50 owned by the user U1.
  • the data sharing inquiry includes information such as the source of the data sharing request, the data storage person, and the type of data to be shared.
  • EC business operator B is set as the data sharing request source
  • hospital A is set as the data storage person
  • "disease name" is set as the data type to be shared.
  • the data distribution control unit 207 receives a response to the data sharing inquiry from the terminal 50.
  • the data distribution control unit 207 If the user refuses data sharing, the data distribution control unit 207 notifies the data sharing requester that data sharing is not possible. In the above example, the data distribution control unit 207 transmits a negative response to the sharing request to the service server 20-2 of the EC company B.
  • the data distribution control unit 207 sends a sharing instruction to the data accumulator.
  • the sharing instruction is sent to the service server 20-1 of hospital A, which is the data accumulator.
  • the sharing instruction includes the personal identification ID generated by the data accumulator, information regarding the data sharing destination, and the data type of the data sharing target.
  • a sharing instruction containing user U1's personal identification ID "HL01", the address of e-commerce company B's service server 20-2, and the data type "disease name" is sent to hospital A's service server 20-1. Sent.
  • the data distribution control unit 207 transmits a sharing instruction that includes the personal identification ID of the user (target person) who has consented to data sharing and is generated by the data accumulator.
  • the data distribution control unit 207 receives a “provision request” from the transaction server 40.
  • the provision request includes a provision application ID, a data provision application, and a list of account openers.
  • the data distribution control unit 207 refers to the location information database and identifies a data accumulator (data provider) that accumulates user data corresponding to the data type described in the data provision application. In the example of FIG. 17, the data distribution control unit 207 specifies "hospital A" from the data type "disease name”.
  • the data distribution control unit 207 notifies the transaction server 40 of information regarding the identified data accumulator.
  • the data distribution control unit 207 transmits a “provider notification” including the name of the identified data accumulator (hospital A in the above example), contact information (address of the service server 20 of hospital A), etc. to the transaction server 40. .
  • the data distribution control unit 207 stores table information that associates and stores the data accumulator's operator code, the data accumulator's name, contact information, etc. that have been input in advance to the distribution control server 10 by the staff of the information distribution business. , and obtain information regarding the data accumulator.
  • the data distribution control unit 207 also stores user data of the type of data that is a user listed in the account opener list and that is the target of data provision to the data accumulator specified based on the data provision application. Identify the user's personal identification ID that has been stored.
  • the data distribution control unit 207 refers to the user information database and Obtain the personal identification ID "HL01".
  • the data distribution control unit 207 refers to the location information database shown in FIG. 17 and confirms that Hospital A has accumulated the data type "disease name" for which data provision was requested regarding the user with the personal identification ID "HL01". do.
  • the data distribution control unit 207 specifies the personal identification ID "HL01" as the personal identification ID of the data distribution target.
  • the data distribution control unit 207 makes an inquiry to the data distribution target person about providing data. Specifically, the data distribution control unit 207 sends an inquiry regarding data provision to the contact information of the data distribution target person. In the above example, a data provision inquiry is sent to the terminal 50 owned by the user U1.
  • the data provision inquiry includes information regarding the source of the data provision request, information regarding the data storage person, and the type of data requested to be provided.
  • an inquiry is sent to the terminal 50 that includes pharmaceutical company C as the source of the request for data provision, hospital A as the data storage person, and "name of disease" as the type of data requested to be provided.
  • the data distribution control unit 207 receives a response to the data provision inquiry from the terminal 50.
  • the data distribution control unit 207 receives a "notification of establishment of a provision contract" or a "notification of cancellation of a provision contract" from the transaction server 40.
  • the data distribution control unit 207 When receiving the provision contract cancellation notification, the data distribution control unit 207 does not perform any special processing. Alternatively, the data distribution control unit 207 may notify the user who has agreed to the data provision inquiry that the data provision contract has not been established.
  • the data distribution control unit 207 transmits a provision instruction to the data accumulator regarding the user who has agreed to provide the data.
  • the provision instructions include the personal identification ID of the user who has agreed to provide the data, information regarding the data provider (e.g., business name, business code, address of the data utilization server 30), and the data type of the data to be provided. and are included.
  • the data distribution control unit 207 instructs the service server 20 to provide the disease name data of the five users who have agreed to provide the data. Send.
  • the data distribution control unit 207 corresponds to the user ID of the user, the operator code of the data storage company, the data ID, the data type, the data provision date, and the provision application ID included in the provision contract establishment notification. Attach and memorize.
  • the catalog information management unit 208 is a means for managing catalog information.
  • Catalog information management section 208 stores catalog information created by a system administrator in storage section 210.
  • the catalog information management unit 208 receives a “catalog information transmission request” from the transaction server 40. In response to receiving the request, the catalog information management unit 208 transmits the catalog information stored in the storage unit 210 to the transaction server 40.
  • the payment control unit 209 is a means for controlling payments for transactions (data accumulation, data provision) that occur in the information distribution system. For example, the payment control unit 209 controls payments related to data transactions that occur during a consideration payment period (for example, one month) at a predetermined timing (for example, at the beginning of a month).
  • the payment control unit 209 When data is accumulated, the payment control unit 209 performs control to pay the service provider and the user an accumulation fee for the data accumulation. Furthermore, when data is provided, the payment control unit 209 performs control so that the information distribution business receives compensation for the data provision from the data utilization business.
  • the settlement control unit 209 refers to the accumulated transaction management database at a predetermined timing (for example, at the beginning of the month) and calculates the accumulated consideration (accumulated consideration paid to the data accumulator) for each entry belonging to the consideration payment period (for example, one month). , the accumulation consideration paid to the user).
  • the payment control unit 209 calculates the accumulation consideration for hospital A accumulating data of the user's "disease name" corresponding to the personal identification ID "HL01". At this time, the payment control unit 209 obtains the corresponding accumulated consideration definition based on the accumulated consideration ID of each entry.
  • the payment consideration is calculated based on the accumulated consideration definition shown in FIG. 6, the accumulated consideration is paid to hospital A of "8 yen" and to the user of "2 yen.”
  • the payment control unit 209 calculates the accumulation consideration to be paid to each data accumulation person by adding up the accumulation consideration calculated for each entry in the consideration payment period (for example, one month) for each data accumulation person. Similarly, the payment control unit 209 calculates the accumulated consideration to be paid to each user by adding up the accumulated consideration calculated for each entry in the consideration payment period for each user.
  • the data provider (data utilization business) pays the information distribution business at a predetermined timing (for example, at the end of the month) for the data provision transaction concluded during the compensation payment period (for example, one month). For example, when a data provision contract is established based on the data provision application shown in FIG. 13, the pharmaceutical company pays a consideration of "100 yen" to the information distribution business.
  • the payment control unit 209 refers to the provision transaction management database at a predetermined timing (for example, at the beginning of the month), and calculates the provision consideration (paid to the data provider) for each entry belonging to the consideration payment period (for example, one month). Calculate the consideration (provided consideration paid to the user).
  • the payment control unit 209 calculates the compensation for the hospital A providing the data of the user's "disease name" corresponding to the personal identification ID "HL01". At this time, the payment control unit 209 identifies the corresponding data provision application (data provision application agreed upon between the parties) based on the provision application ID of each entry.
  • the payment control unit 209 calculates the provision consideration to be paid to the data provider and the user based on the provision data requirements and provision consideration presentation of the specified data provision application (data provision conditions agreed upon between the parties). The payment control unit 209 calculates the consideration to be paid to the data provider and the user based on the requirements of the provided data (data amount) and the presentation of the provided consideration (unit price of the provided data, distribution rate).
  • the payment control unit 209 calculates the provided consideration to be paid to each data accumulator by adding up the provided consideration calculated for each entry in the consideration payment period (for example, one month) for each data provider (data accumulator). calculate. Similarly, the payment control unit 209 calculates the provided consideration to be paid to each user by adding up the provided consideration calculated for each entry in the consideration payment period for each user.
  • the payment control unit 209 pays the calculated compensation (compensation for data storage, compensation for data provision) to each data storage person and user.
  • the payment control unit 209 searches the user information database using the user ID described in the accumulated transaction management database and the provided transaction management database as a key, and obtains the user's account information.
  • the payment control unit 209 uses the acquired account information (bank account information, credit card information, etc.) to pay the user.
  • the payment control unit 209 pays the consideration to the data accumulator using the account information obtained by referring to the table information that stores the business code and the payee of the consideration in association with each other.
  • the storage unit 210 stores information necessary for the operation of the distribution control server 10.
  • a user information database and the like are constructed in the storage unit 210.
  • FIG. 20 is a diagram showing an example of a processing configuration (processing module) of the service server 20 according to the first embodiment.
  • the service server 20 includes a communication control section 301, an ID cooperation control section 302, a data distribution request section 303, a data accumulation control section 304, a data distribution section 305, and a contract conclusion control section 306. , and a storage unit 307.
  • the communication control unit 301 is a means for controlling communication with other devices.
  • the communication control unit 301 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 301 transmits data to the distribution control server 10.
  • the communication control unit 301 passes data received from other devices to other processing modules.
  • the communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 301.
  • the communication control unit 301 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.
  • the ID cooperation control unit 302 is a means for controlling user ID cooperation.
  • the ID cooperation control unit 302 obtains a request for ID cooperation from a user who is logged into an account using a GUI (Graphical User Interface) or the like.
  • GUI Graphic User Interface
  • the ID linkage control unit 302 provides information such as " "ID cooperation request” is sent to the distribution control server 10.
  • the user's personal identification ID, personal identification information, user data, etc. are managed using a customer information database (see FIG. 21).
  • the customer information database holds information (flag) indicating whether or not user ID linkage has been completed.
  • the ID linkage control unit 302 sets a flag in the ID linkage status field of the corresponding user (in FIG. 21, a circle is set).
  • the data distribution request unit 303 is a means for requesting data distribution (data sharing) regarding user data to an information distribution business.
  • the data distribution request unit 303 transmits a sharing request to the distribution control server 10 in response to an operation by a staff member of the service provider.
  • the data distribution request unit 303 sends a sharing request to the distribution control server 10, including the personal identification ID of the user whose data is to be acquired, the operator code of the own device, and the type of data desired to be acquired. .
  • the data accumulation control unit 304 is a means for controlling the accumulation of user data resulting from providing services to users.
  • the data accumulation control unit 304 associates the user's personal identification ID with the user's user data (data generated as a result of providing a service to the user, or data necessary for the service provided to the user). and stored in the customer information database.
  • the data accumulation control unit 304 stores user data in a field corresponding to the type of generated data (stores the specific content of the data). At this time, the data accumulation control unit 304 generates a data ID for identifying the user data, and stores it in association with the user data and the data accumulation date.
  • FIG. 21 shows an example of a customer information database built in the service server 20-1 of hospital A.
  • the data storage control unit 304 requests the information distribution business operator to obtain consent for storage of the user data each time the user data is stored in the customer information database.
  • the data accumulation control unit 304 transmits an accumulation consent acquisition request including the user's personal identification ID, business code, and user data information to the distribution control server 10.
  • the data storage control unit 304 receives a response to the storage consent acquisition request from the distribution control server 10.
  • the data storage control unit 304 takes no particular action.
  • the data accumulation control unit 304 transmits location information to the distribution control server 10. For example, consider a case where a service is provided to a user with personal identification ID "HL01" and disease name data is generated as a medical examination result. In this case, location information including the personal identification ID "HL01”, the business code "Hospital A”, the data ID "HLD01”, and the data type "Disease name” is transmitted to the distribution control server 10.
  • the data distribution unit 305 is a means for realizing data distribution by "sharing” or “providing”.
  • the data distribution unit 305 processes the “sharing instruction” or “provision instruction” received from the distribution control server 10.
  • the data distribution unit 305 When receiving a sharing instruction, the data distribution unit 305 refers to the customer information database and identifies an entry corresponding to the personal identification ID and data type included in the sharing instruction. For example, when receiving a sharing instruction including the personal identification ID "HL01" and the data type "disease name", the data distribution unit 305 specifies the entry shown in the top row of FIG. 21.
  • the data distribution unit 305 transmits the user data written in the corresponding data type field of the specified entry to the data sharing destination specified by the sharing instruction.
  • "stomach cancer” is transmitted to the service server 20-2 of EC company B.
  • the data distribution unit 305 processes the provision instruction in the same way as the sharing instruction.
  • the data distribution unit 305 transmits user data determined by the personal identification ID and data type included in the provision instruction to the data provision destination specified by the provision instruction.
  • the data distribution unit 305 may transmit the user's personal identification information (name, etc.) to the service server 20 of the other party. Furthermore, the data distribution unit 305 may assign an ID to the provided data so that a business operator receiving the provided data can associate the obtained data with each other. For example, the data distribution unit 305 may calculate a hash value of the user's personal identification information and transmit the hash value to the data distribution destination as the user's ID.
  • the contract conclusion control unit 306 is a means for controlling data provision contracts.
  • the contract conclusion control unit 306 processes the provision contract conclusion request received from the transaction server 40. Upon receiving the request, the contract conclusion control unit 306 notifies the staff of the service provider of the contents of the request.
  • the contract conclusion control unit 306 obtains the content decided by the staff (accept or reject the data provision application) using a GUI or the like.
  • the contract conclusion control unit 306 transmits an affirmative response to the transaction server 40 indicating that a data provision contract based on the data provision application is concluded.
  • the contract conclusion control unit 306 transmits a negative response to the transaction server 40 indicating that the data provision contract based on the data provision application will not be concluded.
  • the storage unit 307 stores information necessary for the operation of the service server 20.
  • the storage unit 307 stores account information of each actor (service provider, user, information distribution provider), provider code, personal identification ID, etc. in association with each other.
  • the processing configuration of the data utilization server 30 can be the same as that of the service server 20.
  • the data distribution requesting unit 303 of the data utilization server 30 may present information to the user (such as an employee of a data utilization business) and accept operations from the user. Specifically, the data distribution requesting unit 303 displays a list of catalog information acquired from the transaction server 40 and transmits the data provision application input by the user to the transaction server 40.
  • the data utilization server 30 obtains from the transaction server 40 that the contract for the data provision application has not been concluded, it notifies the staff of the data utilization business to that effect. In this case, the data utilization server 30 obtains an instruction for a new data provision application or cancellation of a data provision application from a staff member or the like. The data utilization server 30 transmits a new data provision application or provision contract cancellation notification to the transaction server 40.
  • the data utilization server 30 may control payments related to data provision. Specifically, the data utilization server 30 may pay for the data provision application agreed upon with the data accumulator, or may output a payment slip or the like.
  • FIG. 22 is a diagram showing an example of a processing configuration (processing module) of the transaction server 40 according to the first embodiment.
  • the transaction server 40 includes a communication control section 401, an account opening section 402, a catalog information request section 403, a provision application processing section 404, and a storage section 405.
  • the communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 401 transmits data to the distribution control server 10. Communication control unit 401 passes data received from other devices to other processing modules. The communication control unit 401 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 401.
  • the communication control unit 401 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.
  • the account opening unit 402 is a means for opening an account for a user who wishes to distribute data by provision.
  • the account opening unit 402 acquires the user ID from the user's terminal 50.
  • the account opening unit 402 adds the acquired user ID to the account opening person list (see FIG. 23).
  • the catalog information requesting unit 403 is a means for transmitting a "catalog information transmission request" to the distribution control server 10.
  • the catalog information requesting unit 403 Upon receiving the “catalog information presentation request” from the data utilization server 30, the catalog information requesting unit 403 transmits a “catalog information transmission request” to the distribution control server 10.
  • the catalog information requesting unit 403 acquires the catalog information stored in the distribution control server 10.
  • the catalog information requesting unit 403 selects catalog information related to a service provider with which the device itself is affiliated, and transmits it to the data utilization provider (data utilization server 30). Note that the catalog information requesting unit 403 selects catalog information regarding the affiliated service provider based on the operator code of the affiliated service provider and the operator code included in the catalog information.
  • the provision application processing unit 404 is a means for processing a data provision application received from the data utilization server 30. Upon receiving the data provision application, the provision application processing unit 404 assigns a provision application ID to the received data provision application. The provision application processing unit 404 manages data provision applications using the provision application ID.
  • the provision application processing unit 404 transmits a "provision request" including a provision application ID, a data provision application, and a list of account openers to the distribution control server 10.
  • the provision application processing unit 404 receives the provider notification from the distribution control server 10.
  • the provider notification includes the provider application ID, the name of the data storage person who stores the data to be provided, the contact information (the address of the service server 20), and the like.
  • the provision application processing unit 404 Upon receiving the provider notification, the provision application processing unit 404 requests the data storage person to enter into a data provision contract.
  • the provision application processing unit 404 transmits a “provision contract conclusion request” including the provision application ID and the data provision application to the service server 20 of the data accumulator.
  • the provision application processing unit 404 receives a response to the provision contract conclusion request from the service server 20.
  • the provision application processing unit 404 When receiving an affirmative response (a response indicating that the data accumulator accepts the data provision application), the provision application processing unit 404 stores the provision application ID of the data provision application for which a contract has been established. Furthermore, the provision application processing unit 404 notifies the distribution control server 10 and the data utilization server 30 that a data provision application contract has been established. The provision application processing unit 404 transmits a “provision contract establishment notification” including the provision application ID to the distribution control server 10 and the data utilization server 30.
  • the provision application processing unit 404 When receiving a negative response (a response indicating that the data accumulator does not accept the data provision application), the provision application processing unit 404 notifies the data utilization server 30 that the contract for the data provision application has not been concluded.
  • the provision application processing unit 404 receives a new data provision application (data provision application with revised conditions) or a provision contract cancellation notice from the data utilization server 30.
  • the provision application processing unit 404 transmits a provision contract conclusion request including the new data provision contract to the data accumulator's service server 20.
  • the provision application processing unit 404 transfers the received provision contract cancellation notification to the distribution control server 10.
  • the storage unit 405 stores information necessary for the operation of the transaction server 40.
  • the storage unit 405 stores the company code of the partner service provider.
  • FIG. 24 is a diagram illustrating an example of a processing configuration (processing module) of the terminal 50 according to the first embodiment.
  • the terminal 50 includes a communication control section 501, a personal information input section 502, an inquiry processing section 503, and a storage section 504.
  • the communication control unit 501 is a means for controlling communication with other devices.
  • the communication control unit 501 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 501 transmits data to the distribution control server 10.
  • Communication control unit 501 passes data received from other devices to other processing modules.
  • the communication control unit 501 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 501.
  • the communication control unit 501 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.
  • the personal information input unit 502 is a means for inputting personal information into the distribution control server 10 during user registration.
  • the personal information input unit 502 inputs personal information (name, date of birth, contact information, account information, etc.) into the distribution control server 10 using any means.
  • the personal information input unit 502 uses the GUI to obtain the above-mentioned personal information from the user, and transmits the obtained personal information to the distribution control server 10.
  • the personal information input unit 502 stores the user ID issued by the distribution control server 10 in the storage unit 504.
  • the inquiry processing unit 503 is a means for processing inquiries about data accumulation, inquiries about data sharing, or inquiries about data provision.
  • the inquiry processing unit 503 obtains the user's intention (agreement, disagreement) using a GUI that matches the content of the inquiry (data accumulation, data sharing, data provision).
  • the inquiry processing unit 503 transmits a response including the user's intention to the distribution control server 10.
  • the storage unit 504 stores information necessary for the operation of the terminal 50.
  • Examples of the hospital terminal 60 include mobile terminal devices such as smartphones and tablets, computers (personal computers, notebook computers), and the like.
  • the hospital terminal 60 can be any equipment or device as long as it accepts operations from hospital staff and can communicate with the distribution control server 10 and the like. Further, since the configuration of the hospital terminal 60 is obvious to those skilled in the art, detailed explanation will be omitted.
  • the hospital terminal 60 may send an ID cooperation request to the distribution control server 10 in response to an operation by a hospital staff member.
  • the hospital terminal 60 also transmits the ID cooperation request to its own service server 20.
  • the service server 20 (ID linkage control unit 302) sets a flag in the ID linkage status field of the user entry (customer information database entry) corresponding to the personal identification ID included in the ID linkage request.
  • FIG. 25 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. The operation of the system during data accumulation will be explained with reference to FIG.
  • the service server 20 After acquiring the user data of the user, the service server 20 transmits a storage consent acquisition request to the distribution control server 10 (step S41).
  • the distribution control server 10 transmits a data storage inquiry to the user's terminal 50 (step S42).
  • the distribution control server 10 receives a response (agreeing to data storage, not agreeing) from the terminal 50 (step S43).
  • the distribution control server 10 transmits a response from the terminal 50 to the service server 20 (step S44).
  • the service server 20 transmits the location information to the distribution control server 10 (step S45).
  • the distribution control server 10 stores location information.
  • FIG. 26 is a sequence diagram showing an example of the operation of the information distribution system according to the first embodiment. The operation of the system when providing data will be explained with reference to FIG.
  • the transaction server 40 Upon acquiring the data provision application from the data utilization server 30, the transaction server 40 transmits a provision request including the data provision application and the list of account openers to the distribution control server 10 (step S51).
  • the distribution control server 10 identifies the data provider that has accumulated the data to be provided, and transmits a provider notification containing information about the specified data provider to the transaction server 40 (step S52). ).
  • the distribution control server 10 Before and after transmitting the provider notification, the distribution control server 10 transmits a data provision inquiry to the terminal 50 owned by the data provision target (step S53).
  • the distribution control server 10 receives a response regarding the data provision inquiry from the terminal 50 (step S54).
  • the transaction server 40 which has received the provider notification, transmits a request to conclude a provision contract to the service server 20 of the data provider (step S55).
  • the service server 20 transmits a response according to the service provider's examination results to the transaction server 40 (step S56).
  • the transaction server 40 sends a provision contract establishment notification to the distribution control server 10 and the data utilization server 30 (step S57). ).
  • the distribution control server 10 transmits a provision instruction to the service server 20 of the data accumulator (data provider) (step S58).
  • the service server 20 transmits the specified data to the data provider (data utilization server 30) (step S59).
  • the information distribution business pays compensation for data accumulation to the data provider and the user.
  • the data provider can earn revenue before the data provider and the data provider conclude a data provision contract.
  • the information distribution business operator receives a portion of the consideration paid by the data provider as provision consideration, thereby recovering the expenses paid in advance for data storage.
  • the information distribution system pays the data provider the price for data accumulation, allowing the data provider to quickly recover the investment it made when entering the information distribution system.
  • the hurdles for data providers to enter the information distribution system will be lowered, and more data providers will participate in the system.
  • the information distribution system will further develop as more data providers participate in the system.
  • FIG. 27 is a diagram showing an example of the hardware configuration of the distribution control server 10.
  • the distribution control server 10 can be configured by an information processing device (so-called computer), and has the configuration illustrated in FIG. 27.
  • the distribution control server 10 includes a processor 311, a memory 312, an input/output interface 313, a communication interface 314, and the like.
  • the components such as the processor 311 are connected by an internal bus or the like and are configured to be able to communicate with each other.
  • the configuration shown in FIG. 27 is not intended to limit the hardware configuration of the distribution control server 10.
  • the distribution control server 10 may include hardware that is not shown, and may not include the input/output interface 313 if necessary.
  • the number of processors 311 and the like included in the distribution control server 10 is not limited to the example shown in FIG. 27; for example, a plurality of processors 311 may be included in the distribution control server 10.
  • the processor 311 is, for example, a programmable device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs including an operating system (OS).
  • OS operating system
  • the memory 312 is a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like.
  • the memory 312 stores OS programs, application programs, and various data.
  • the input/output interface 313 is an interface for a display device or input device (not shown).
  • the display device is, for example, a liquid crystal display.
  • the input device is, for example, a device such as a keyboard or a mouse that receives user operations.
  • the communication interface 314 is a circuit, module, etc. that communicates with other devices.
  • the communication interface 314 includes a NIC (Network Interface Card).
  • the functions of the distribution control server 10 are realized by various processing modules.
  • the processing module is realized, for example, by the processor 311 executing a program stored in the memory 312. Further, the program can be recorded on a computer-readable storage medium.
  • the storage medium can be non-transitory, such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. That is, the present invention can also be implemented as a computer program product.
  • the above program can be updated via a network or by using a storage medium that stores the program.
  • the processing module may be realized by a semiconductor chip.
  • the service server 20 and the like can be configured by an information processing device in the same way as the distribution control server 10, and the basic hardware configuration thereof is not different from the distribution control server 10, so a description thereof will be omitted.
  • the distribution control server 10 which is an information processing device, is equipped with a computer, and the functions of the distribution control server 10 can be realized by having the computer execute a program. Further, the distribution control server 10 executes the control method of the distribution control server 10 using the program.
  • a service provider requests an information distribution company to obtain consent for data storage (obtain user consent).
  • the service provider may directly obtain the user's consent for data storage.
  • the service server 20 may transmit location information to the distribution control server 10 when the user agrees to data storage.
  • the above embodiment has been described on the premise that the data provider and the data provider mainly negotiate the unit price of the provided data (price per piece of data).
  • the data provider and the data provider may negotiate the amount of data or the distribution rate.
  • a data utilization business may pay compensation for providing data to an information distribution business via a transaction business.
  • the information distribution business operator may pay the consideration to the data accumulator (data provider) or user via the transaction business operator.
  • the user information database is configured inside the distribution control server 10, but the database may be configured in an external database server or the like. That is, some functions of the distribution control server 10 may be implemented in another server. More specifically, the above-described "data distribution control unit (data distribution control means)" etc. may be implemented in any device included in the system.
  • each device distributed control server 10, service server 20, etc.
  • data transmitted and received between these devices may be encrypted.
  • personal information of users is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable that encrypted data be transmitted and received.
  • each embodiment may be used alone or in combination.
  • the present invention is suitably applicable to an information distribution system that distributes accumulated data regarding services provided to users.
  • the distribution control server is controlling data accumulation for registering the user data in an information distribution system as data that can be provided to a third party; controlling data provision for providing the user data registered by the data accumulation from the service server to the data utilization server; paying storage fees for the data storage to the service provider and the user;
  • the service server When the service server stores the user data, the service server transmits a storage consent acquisition request including information regarding the user data to the distribution control server;
  • the distribution control server transmits a data accumulation inquiry including information regarding the user data to a terminal owned by the user, receives a response to the data accumulation inquiry from the terminal owned by the user, and
  • the system according to appendix 1, wherein the system forwards the received response to the service server.
  • the service server transmits location information including the data type of the stored user data to the distribution control server;
  • the distribution control server is performing the data accumulation of the user data in response to receiving the location information;
  • the system according to supplementary note 2, wherein the accumulation consideration to be paid to the service provider and the user is calculated based on an accumulation consideration definition predetermined for each data type.
  • the accumulation consideration definition includes the data type of the user data to be accumulated, the consideration paid by the information distribution business for accumulating one data, the service provider of the consideration paid by the information distribution business, and the The system according to appendix 3, comprising: a user distribution rate; [Additional note 5] Requirements for the provided data to be provided from the data utilization server to the data utilization business operator through the data provision, and provided consideration including details of the presentation of the provision consideration to be paid by the data utilization business operator upon the data provision.
  • a transaction server that receives a data provision application including a presentation and transmits a provision request including the data provision application to the distribution control server;
  • the distribution control server is Upon receiving the provision request, the user to whom the data is to be provided is identified, and a data provision inquiry is sent to the identified user's terminal, thereby ensuring that the user agrees to the data provision.
  • a provider notification containing information on the identified service provider to the transaction server; 5.
  • the distribution control server sends the service to the service server.
  • the system according to appendix 5 wherein the system instructs to transmit the stored user data to the data utilization server.
  • the distribution control server transfers the data provision application for which the contract has been concluded and the data provision transaction.
  • the distribution control server calculates the provision consideration based on the requirements of the provision data of the data provision application for which the contract has been established and the provision consideration presentation.
  • the provision consideration presentation includes the data type of the provided user data, the consideration paid by the data utilization business operator for providing one piece of data, and the service business operator of the consideration paid by the data utilization business operator. , and a distribution rate to each of the user and the information distribution business operator.
  • an accumulation control unit that controls data accumulation for registering user data generated when a service provider provides a service to a user in an information distribution system as data that can be provided to a third party; a data distribution control unit that controls data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider; and, a payment control unit that performs control such that an information distribution business operator pays accumulation fees for the data storage to the service provider and the user, and receives compensation for the data provision from the data utilization business operator; Distribution control server equipped with.
  • a method for controlling a distribution control server the method comprising: paying a service provider and the user a compensation for storing the data; and controlling an information distribution business to receive compensation for providing the data from the data utilization business.
  • Distribution control server 20 Service server 20-1 Service server 20-2 Service server 30 Data utilization server 40 Transaction server 50 Terminal 60 Hospital terminal 101 Service server 102 Data utilization server 103 Distribution control server 201 Communication control unit 202 User registration Section 203 ID cooperation section 204 Consideration definition disclosure section 205 Accumulation consent control section 206 Location information management section 207 Data distribution control section 208 Catalog information management section 209 Payment control section 210 Storage section 301 Communication control section 302 ID cooperation control section 303 Data distribution request Section 304 Data accumulation control section 305 Data distribution section 306 Contract conclusion control section 307 Storage section 311 Processor 312 Memory 313 Input/output interface 314 Communication interface 401 Communication control section 402 Account opening section 403 Catalog information request section 404 Providing application processing section 405 Storage section 501 Communication control section 502 Personal information input section 503 Inquiry processing section 504 Storage section

Abstract

Provided is a system that further develops an information distribution system. According to the present invention, a service server is operated by a service business operator, and stores user data generated by providing services to users. A data utilization server is operated by a data utilization business operator. A distribution control server is operated by an information distribution business operator. The distribution control server controls data accumulation for registering the user data in an information distribution system as data that can be provided to third parties. The distribution control server controls data provision for providing, from the service server to the data utilization server, the user data registered through the data accumulation. The distribution control server pays the service business operator and the users accumulation compensation for the data accumulation. The distribution control server performs control for the information distribution business operator to receive, from the data utilization business operator, provision compensation for the data provision.

Description

システム、流通制御サーバ、流通制御サーバの制御方法及び記憶媒体System, distribution control server, distribution control server control method, and storage medium
　本発明は、システム、流通制御サーバ、流通制御サーバの制御方法及び記憶媒体に関する。 The present invention relates to a system, a distribution control server, a distribution control server control method, and a storage medium.
　病院などに保有されている個人情報を、個人の同意に基づき事業者などの情報提供先の装置に提供する情報流通システムが存在する。 There are information distribution systems that provide personal information held by hospitals, etc., to equipment provided by information providers, such as businesses, based on the consent of the individual.
　例えば、特許文献１には、仲介企業（データ流通制御装置）は、データ活用企業からデータ収集対価を受領する、と記載されている。特許文献１のデータ収集対価は、データ活用企業から支払われるデータ提供に対する対価である。仲介企業は、データ活用企業からのデータ収集対価に基づいて、データ仲介料、データ提供料（個）およびデータ提供料（企）を支払う。データ仲介料は、仲介企業に支払われるデータ仲介に対する対価である。データ提供料（個）は、データ主体である各個人に支払われるデータ提供に対する対価である。データ提供料（企）は、各データ提供企業に支払われるデータ提供に対する対価である。このように、データ仲介者、個人（データ主体）およびデータ提供者（保有者）に対してインセンティブを与えることで、データ流通を促進する。 For example, Patent Document 1 states that an intermediary company (data distribution control device) receives data collection compensation from a data utilization company. The data collection consideration in Patent Document 1 is compensation for providing data paid by a data utilization company. The intermediary company pays data intermediary fees, data provision fees (individuals), and data provision fees (company) based on the consideration for data collection from data utilization companies. Data brokerage fees are compensation paid to intermediary companies for data brokerage. Data provision fee (individuals) is compensation paid to each individual who is a data subject for providing data. Data provision fees (company) are compensation paid to each data providing company for providing data. In this way, data flow is promoted by providing incentives to data intermediaries, individuals (data subjects), and data providers (holders).
　特許文献２の情報取引装置は、情報提供元装置から情報提供先装置へ提供できる個人情報を含む一つ以上のデータセットに関する詳細情報を含むカタログ情報を記憶する。情報取引装置は、情報提供先装置からデータセットの提供要求を受け付ける。情報取引装置は、提供要求が示すデータセットの送信要求を、情報提供元装置へ出力する。 The information transaction device of Patent Document 2 stores catalog information including detailed information regarding one or more datasets including personal information that can be provided from an information provider device to an information destination device. The information transaction device receives a data set provision request from the information provision destination device. The information transaction device outputs a request to transmit the data set indicated by the provision request to the information provider device.
特開２０２０－１２９３１１号公報JP2020-129311A 国際公開第２０２１／０８５０６１号International Publication No. 2021/085061
　特許文献１や特許文献２に開示された情報流通システム（データ流通システム）においてユーザデータを第三者に提供可能とするためには、データ提供元（データ蓄積者）は相応のコストを費やし環境等を整備する必要がある。しかし、パーソナルデータ取引市場への参入を検討するデータ提供元は、データ取引の実現まで売上を計上できない現状がある。 In order to be able to provide user data to a third party in the information distribution system (data distribution system) disclosed in Patent Document 1 and Patent Document 2, the data provider (data accumulator) has to spend a corresponding amount of cost to improve the environment. etc. need to be maintained. However, data providers considering entering the personal data trading market are currently unable to record sales until data trading is completed.
　そのため、データ提供元は、パーソナルデータ取引市場（情報流通システム）への参加を躊躇することもある。情報流通システムに参加するデータ提供元が増えなければ、パーソナルデータのデータ流通のさらなる発展は期待できない。 Therefore, data providers may hesitate to participate in the personal data trading market (information distribution system). Unless the number of data providers participating in the information distribution system increases, further development of personal data distribution cannot be expected.
　なお、当該問題は、特許文献１や特許文献２に開示された技術を適用しても解決できない。特許文献１や特許文献２では、パーソナルデータを第三者提供可能とすることのコストは考慮されていない。 Note that this problem cannot be solved even by applying the techniques disclosed in Patent Document 1 and Patent Document 2. Patent Document 1 and Patent Document 2 do not take into consideration the cost of allowing personal data to be provided to a third party.
　本発明は、情報流通システムをより発展させることに寄与する、システム、流通制御サーバ、流通制御サーバの制御方法及び記憶媒体を提供することを主たる目的とする。 The main purpose of the present invention is to provide a system, a distribution control server, a control method for a distribution control server, and a storage medium that contribute to further development of an information distribution system.
　本発明の第１の視点によれば、サービス事業者により運営され、利用者にサービスを提供することで発生したユーザデータを記憶する、サービスサーバと、データ利活用事業者により運営される、データ利活用サーバと、情報流通事業者により運営される、流通制御サーバと、を含み、前記流通制御サーバは、前記ユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、前記データ蓄積により登録された前記ユーザデータを前記サービスサーバから前記データ利活用サーバに提供するためのデータ提供を制御し、前記サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を前記情報流通事業者が受け取るための制御を行う、システムが提供される。 According to a first aspect of the present invention, there is provided a service server operated by a service provider that stores user data generated by providing services to users; The distribution control server includes a utilization server and a distribution control server operated by an information distribution business, and the distribution control server stores data for registering the user data in the information distribution system as data that can be provided to a third party. control the data provision for providing the user data registered by the data storage from the service server to the data utilization server, and provide the service provider and the user with the data storage for the data storage. A system is provided that performs control for the information distribution business to pay compensation and receive compensation for the data provision from the data utilization business.
　本発明の第２の視点によれば、サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する、蓄積制御部と、前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する、データ流通制御部と、サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、決済制御部と、を備える、流通制御サーバが提供される。 According to the second aspect of the present invention, a service provider controls data accumulation for registering user data generated by providing services to users in an information distribution system as data that can be provided to a third party. an accumulation control unit, and a data provision unit for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization operator. a data distribution control unit that controls, and controls for the information distribution business operator to pay accumulation consideration for the data storage to the service provider and the user, and for the information distribution business operator to receive the provision consideration for the data provision from the data utilization business operator. A distribution control server is provided, which includes a payment control unit that performs payment processing.
　本発明の第３の視点によれば、流通制御サーバにおいて、サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御し、サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、流通制御サーバの制御方法が提供される。 According to the third aspect of the present invention, in the distribution control server, user data generated when a service provider provides a service to a user is registered in the information distribution system as data that can be provided to a third party. control data accumulation, and provide data for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider. a distribution control server that performs control such that the information distribution business operator receives compensation for the data provision from the data utilization business operator, and pays the service provider and the user compensation for storing the data; A control method is provided.
　本発明の第４の視点によれば、流通制御サーバに搭載されたコンピュータに、サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する処理と、前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する処理と、サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う処理と、を実行させるためのプログラムを記憶する、コンピュータ読取可能な記憶媒体が提供される。 According to the fourth aspect of the present invention, information distribution is performed in a computer installed in a distribution control server, using user data generated when a service provider provides a service to a user as data that can be provided to a third party. A process of controlling data accumulation for registration in the system, and transferring the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider. processing for controlling the provision of data for providing data, paying the service provider and the user the accumulation consideration for the data accumulation, and the information distribution business operator receiving the provision consideration for the data provision from the data utilization business operator. A computer-readable storage medium is provided that stores a program for controlling the process and executing the process.
　本発明の各視点によれば、情報流通システムをより発展させることに寄与する、システム、流通制御サーバ、流通制御サーバの制御方法及び記憶媒体が提供される。なお、本発明の効果は上記に限定されない。本発明により、当該効果の代わりに、又は当該効果と共に、他の効果が奏されてもよい。 According to each aspect of the present invention, a system, a distribution control server, a control method for a distribution control server, and a storage medium are provided that contribute to further development of an information distribution system. Note that the effects of the present invention are not limited to the above. According to the present invention, other effects may be achieved instead of or in addition to the above effects.
図１は、一実施形態の概要を説明するための図である。FIG. 1 is a diagram for explaining an overview of one embodiment. 図２は、一実施形態の動作の一例を示すフローチャートである。FIG. 2 is a flowchart illustrating an example of the operation of one embodiment. 図３は、第１の実施形態に係る情報流通システムの概略構成の一例を示す図である。FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment. 図４は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 4 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図５は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 5 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図６は、第１の実施形態に係る蓄積対価定義の一例を示す図である。FIG. 6 is a diagram illustrating an example of the accumulation consideration definition according to the first embodiment. 図７は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 7 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図８は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 8 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図９は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 9 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図１０は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 10 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図１１は、第１の実施形態に係るカタログ情報の一例を示す図である。FIG. 11 is a diagram showing an example of catalog information according to the first embodiment. 図１２は、第１の実施形態に係る提供対価定義の一例を示す図である。FIG. 12 is a diagram illustrating an example of the provided consideration definition according to the first embodiment. 図１３は、第１の実施形態に係るデータ提供申込の一例を示す図である。FIG. 13 is a diagram showing an example of a data provision application according to the first embodiment. 図１４は、第１の実施形態に係る情報流通システムの動作を説明するための図である。FIG. 14 is a diagram for explaining the operation of the information distribution system according to the first embodiment. 図１５は、第１の実施形態に係る流通制御サーバの処理構成の一例を示す図である。FIG. 15 is a diagram illustrating an example of the processing configuration of the distribution control server according to the first embodiment. 図１６は、第１の実施形態に係る利用者情報データベースの一部の一例を示す図である。FIG. 16 is a diagram showing an example of a part of the user information database according to the first embodiment. 図１７は、第１の実施形態に係る所在情報データベースの一例を示す図である。FIG. 17 is a diagram illustrating an example of the location information database according to the first embodiment. 図１８は、第１の実施形態に係る蓄積取引管理データベースの一例を示す図である。FIG. 18 is a diagram showing an example of the accumulated transaction management database according to the first embodiment. 図１９は、第１の実施形態に係る提供取引管理データベースの一例を示す図である。FIG. 19 is a diagram illustrating an example of the provided transaction management database according to the first embodiment. 図２０は、第１の実施形態に係るサービスサーバの処理構成の一例を示す図である。FIG. 20 is a diagram illustrating an example of the processing configuration of the service server according to the first embodiment. 図２１は、第１の実施形態に係る顧客情報データベースの一例を示す図である。FIG. 21 is a diagram showing an example of the customer information database according to the first embodiment. 図２２は、第１の実施形態に係る取引サーバの処理構成の一例を示す図である。FIG. 22 is a diagram showing an example of the processing configuration of the transaction server according to the first embodiment. 図２３は、第１の実施形態に係る口座開設者リストの一例を示す図である。FIG. 23 is a diagram illustrating an example of an account opener list according to the first embodiment. 図２４は、第１の実施形態に係る端末の処理構成の一例を示す図である。FIG. 24 is a diagram illustrating an example of a processing configuration of a terminal according to the first embodiment. 図２５は、第１の実施形態に係る情報流通システムの動作の一例を示すシーケンス図である。FIG. 25 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. 図２６は、第１の実施形態に係る情報流通システムの動作の一例を示すシーケンス図である。FIG. 26 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. 図２７は、本願開示に係る流通制御サーバのハードウェア構成の一例を示す図である。FIG. 27 is a diagram illustrating an example of the hardware configuration of a distribution control server according to the present disclosure.
　はじめに、一実施形態の概要について説明する。なお、この概要に付記した図面参照符号は、理解を助けるための一例として各要素に便宜上付記したものであり、この概要の記載はなんらの限定を意図するものではない。また、特段の釈明がない場合には、各図面に記載されたブロックはハードウェア単位の構成ではなく、機能単位の構成を表す。各図におけるブロック間の接続線は、双方向及び単方向の双方を含む。一方向矢印については、主たる信号（データ）の流れを模式的に示すものであり、双方向性を排除するものではない。なお、本明細書及び図面において、同様に説明されることが可能な要素については、同一の符号を付することにより重複説明が省略され得る。 First, an overview of one embodiment will be described. Note that the drawing reference numerals added to this summary are added to each element for convenience as an example to aid understanding, and the description of this summary is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks depicted in each drawing represent the configuration of functional units rather than the configuration of hardware units. Connection lines between blocks in each figure include both bidirectional and unidirectional connections. The unidirectional arrows schematically indicate the main signal (data) flow, and do not exclude bidirectionality. Note that, in this specification and the drawings, elements that can be explained in the same manner may be designated by the same reference numerals, so that redundant explanation can be omitted.
　一実施形態に係るシステムは、サービスサーバ１０１と、データ利活用サーバ１０２と、流通制御サーバ１０３と、を含む（図１参照）。サービスサーバ１０１は、サービス事業者により運営され、利用者にサービスを提供することで発生したユーザデータを記憶する。データ利活用サーバ１０２は、データ利活用事業者により運営される。流通制御サーバ１０３は、情報流通事業者により運営される。流通制御サーバ１０３は、ユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する（図２のステップＳ１）。流通制御サーバ１０３は、データ蓄積により登録されたユーザデータをサービスサーバ１０１からデータ利活用サーバ１０２に提供するためのデータ提供を制御する（ステップＳ２）。流通制御サーバ１０３は、サービス事業者及び利用者にデータ蓄積に対する蓄積対価を支払う（ステップＳ３）。流通制御サーバ１０３は、データ利活用事業者からデータ提供に対する提供対価を情報流通事業者が受け取るための制御を行う（ステップＳ４）。 The system according to one embodiment includes a service server 101, a data utilization server 102, and a distribution control server 103 (see FIG. 1). The service server 101 is operated by a service provider and stores user data generated by providing services to users. The data utilization server 102 is operated by a data utilization business. The distribution control server 103 is operated by an information distribution business. The distribution control server 103 controls data accumulation for registering user data in the information distribution system as data that can be provided to a third party (step S1 in FIG. 2). The distribution control server 103 controls data provision for providing user data registered through data accumulation from the service server 101 to the data utilization server 102 (step S2). The distribution control server 103 pays the service provider and the user an accumulation fee for data accumulation (step S3). The distribution control server 103 performs control for the information distribution business to receive compensation for providing data from the data utilization business (step S4).
　上記システムでは、情報流通事業者は、データ蓄積に対する対価をデータ蓄積者（利用者にサービスを提供するサービス事業者）と利用者に支払う。即ち、データ提供元（サービス事業者）とデータ提供先（データ利活用事業者）がデータ提供契約を締結する前に、データ提供元は収益を得ることができる。また、情報流通事業者は、データ提供契約が履行された際、データ提供先が支払う対価の一部を受け取ることで、先行してデータ蓄積に対して支払った対価を回収する。このように、情報流通システムからデータ蓄積の対価がデータ提供元に支払われることで、データ提供元はデータ蓄積に対する投資を早期に回収できることになる。その結果、データ提供元が情報流通システムに参入する際のハードルが低くなり、より多くのデータ提供元がシステムに参加し、情報流通システムがより発展する。 In the above system, the information distribution business pays compensation for data storage to the data storage operator (the service business providing services to the user) and the user. In other words, the data provider can earn revenue before the data provider (service provider) and the data provider (data utilization provider) conclude a data provision contract. Furthermore, when the data provision contract is fulfilled, the information distribution business receives a portion of the consideration paid by the data provider, thereby recovering the consideration paid in advance for data accumulation. In this way, the information distribution system pays the data provider the price for data storage, allowing the data provider to quickly recover its investment in data storage. As a result, the hurdles for data providers to enter the information distribution system will be lowered, more data providers will participate in the system, and the information distribution system will further develop.
　上記説明したように、データ提供元が情報流通システムに参加する際には、初期投資のリスクを許容しつつ、パーソナルデータ取引市場への接続環境やデータベースの整備等を実行する必要がある。また、現状のパーソナルデータ取引において、個人に対するデータ蓄積に対する対価の支払いは行われておらず、その結果として個人の同意を必要とする要配慮個人情報といった価値の高いデータの取引量が少ないのが現状である。本願開示の情報流通システムは、情報流通事業者からデータ蓄積に対する対価をデータ蓄積に関与するサービス事業者及び個人に支払うことでデータ提供元の負担を軽減する。また、情報流通システムは、個人に対してもデータ蓄積の対価を支払うことで、要配慮個人情報のようなデータの蓄積を促す。 As explained above, when a data provider participates in an information distribution system, it is necessary to prepare the connection environment to the personal data trading market and the database while accepting the risk of initial investment. Additionally, in current personal data transactions, individuals are not compensated for data storage, and as a result, the amount of highly valuable data such as sensitive personal information that requires individual consent is small. This is the current situation. The information distribution system disclosed herein reduces the burden on data providers by having the information distribution business pay compensation for data accumulation to service providers and individuals involved in data accumulation. Furthermore, the information distribution system encourages individuals to accumulate data such as sensitive personal information by paying compensation for data accumulation.
　また、本願開示の情報流通システムは、以下の基本リスクとコストリスクを解消することもできる。基本リスク１は、データ提供元がシステムに参入するか否かの検討段階では、データ提供先の実態（データ提供先の存在数等）が不明な点である。基本リスク２は、データ提供元がシステムに参入するか否かの検討段階では、どの程度の利用者がデータの蓄積に同意するか不明な点である。また、コストリスク１は、第三者提供用のデータセット整備コストの回収タイミングは、データ提供契約が履行された後である点である。コストリスク２は、業務および保有システムの改修コストの回収タイミングは、データ提供契約が履行された後である点である。コストリスク３は、利用者への対価設定とその支払い方法の検討および実装コストの改修タイミングは、データ提供契約が履行された後である点である。本願開示の情報流通システムは、データ蓄積に対する対価をデータ提供前にデータ提供元に支払うことで、上記基本リスク及びコストリスクを解消又は低減する。 Additionally, the information distribution system disclosed in this application can also eliminate the following basic risks and cost risks. Basic risk 1 is that the actual status of data providers (such as the number of data providers) is unknown at the stage of considering whether or not the data provider will participate in the system. Basic risk 2 is that at the stage when a data provider is considering whether to participate in the system, it is unclear how many users will consent to the accumulation of data. Moreover, cost risk 1 is that the timing of recovering the cost of preparing a data set for third party provision is after the data provision contract is fulfilled. Cost risk 2 is that the timing of recovering the cost of repairing business operations and owned systems is after the data provision contract is fulfilled. Cost risk 3 is that the timing of setting fees for users, considering payment methods, and revising implementation costs is after the data provision contract has been fulfilled. The information distribution system disclosed herein eliminates or reduces the basic risk and cost risk by paying compensation for data accumulation to the data provider before providing the data.
　以下に具体的な実施形態について、図面を参照してさらに詳しく説明する。 Specific embodiments will be described in more detail below with reference to the drawings.
［第１の実施形態］
　第１の実施形態について、図面を用いてより詳細に説明する。 [First embodiment]
The first embodiment will be described in more detail using the drawings.
［システム構成］
　図３は、第１の実施形態に係る情報流通システムの概略構成の一例を示す図である。図３に示すように、情報流通システムの参加メンバー（アクター）には、情報流通事業者と、サービス事業者と、データ利活用事業者と、取引事業者と、が含まれる。 [System configuration]
FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment. As shown in FIG. 3, participating members (actors) of the information distribution system include information distribution businesses, service businesses, data utilization businesses, and trading businesses.
　情報流通事業者は、サービス事業者に蓄積されたパーソナルデータのデータ流通サービス（情報流通サービス）のプラットフォームを提供する事業者である。情報流通事業者は、事業者（サービス事業者、データ利活用事業者）間のデータ流通を制御する。情報流通事業者は、流通制御サーバ１０を備える。 An information distribution business is a business that provides a platform for data distribution services (information distribution services) for personal data accumulated by service providers. The information distribution business operator controls data distribution between businesses (service businesses, data utilization businesses). The information distribution business includes a distribution control server 10.
　流通制御サーバ１０は、情報流通事業者により運営される。流通制御サーバ１０は、サービス事業者間のデータ流通を制御（実現）したり、サービス事業者とデータ利活用事業者の間のデータ流通を制御したりするサーバ装置である。流通制御サーバ１０は、サービス事業者が保持するデータの情報流通サービスを実現する。 The distribution control server 10 is operated by an information distribution business. The distribution control server 10 is a server device that controls (realizes) data distribution between service providers and controls data distribution between service providers and data utilization providers. The distribution control server 10 realizes an information distribution service for data held by a service provider.
　サービス事業者は、個人にサービスを提供する主体である。サービス事業者は、民間の事業者であってもよいし公的機関であってもよい。サービス事業者には、例えば、利用者に医療サービスを提供する医療機関（病院、薬局等）、小売業者、顧客に語学、スポーツ、芸術等を教える教育事業者等が例示される。 A service provider is an entity that provides services to individuals. The service provider may be a private company or a public institution. Examples of service providers include medical institutions (hospitals, pharmacies, etc.) that provide medical services to users, retailers, and educational providers that teach languages, sports, art, etc. to customers.
　各サービス事業者は、顧客にサービスを提供するためのサービスサーバ２０を備える。サービスサーバ２０は、サービス事業者により管理、運営される。サービスサーバ２０は、サービス事業者が利用者にサービスを提供することで生じたデータ、利用者にサービスを提供するために必要なデータ等を保持（記憶）する。サービス事業者は、利用者に提供するサービスに関するユーザデータを保持する。 Each service provider includes a service server 20 for providing services to customers. The service server 20 is managed and operated by a service provider. The service server 20 holds (stores) data generated when a service provider provides a service to a user, data necessary for providing a service to a user, and the like. A service provider maintains user data regarding services provided to users.
　データ利活用事業者は、個人に直接サービスを提供しない主体である。データ利活用事業者には、製薬会社のような事業者が例示される。例えば、製薬会社は、サービス事業者から取得したデータを用いて新薬を開発する。 A data utilization business is an entity that does not provide services directly to individuals. Examples of data utilization businesses include businesses such as pharmaceutical companies. For example, a pharmaceutical company develops a new drug using data obtained from a service provider.
　なお、本願開示では、個人にサービスを提供しない主体を「データ利活用事業者」と扱い説明を行うが、データ利活用事業者が利用者にサービスを提供する際には「サービス事業者」として振る舞うのは当然である。即ち、データ利活用事業者の業務形態によっては、当データ利活用事業者がサービス事業者にもなり得る。 In addition, in this disclosure, an entity that does not provide services to individuals will be treated as a "data utilization business entity" and explained, but when a data utilization business entity provides services to users, it will be referred to as a "service business entity". It is natural to behave. In other words, depending on the business form of the data utilization business, the data utilization business can also become a service provider.
　データ利活用事業者は、サービス事業者からデータを取得し利活用するためのデータ利活用サーバ３０を備える。データ利活用サーバ３０は、データ利活用事業者により運営される。 The data utilization business is equipped with a data utilization server 30 for acquiring and utilizing data from the service business. The data utilization server 30 is operated by a data utilization business.
　取引事業者は、サービス事業者とデータ利活用事業者の間の取引を実現する主体である。取引事業者は、データ生成者（サービス事業者）とデータ消費者（データ利活用事業者）の間のデータ流通を実現する。 A transaction business operator is an entity that realizes a transaction between a service business operator and a data utilization business operator. Transaction operators realize data distribution between data generators (service operators) and data consumers (data utilization operators).
　取引事業者は、当該データ流通の実現のための取引サーバ４０を備える。 The transaction business operator is equipped with a transaction server 40 for realizing the data distribution.
　情報流通システムを利用する利用者は、端末５０を使用する。 A user who uses the information distribution system uses a terminal 50.
　図３に示す各装置はネットワークを介して相互に接続されている。例えば、流通制御サーバ１０とサービスサーバ２０は、有線又は無線の通信手段により接続され、相互に通信が可能となるように構成されている。 The devices shown in FIG. 3 are interconnected via a network. For example, the distribution control server 10 and the service server 20 are connected by wired or wireless communication means and configured to be able to communicate with each other.
　図３に示す構成は例示であって、本願開示の情報流通システムの構成等を限定する趣旨ではない。例えば、情報流通事業者には２台以上の流通制御サーバ１０が含まれていてもよい。また、取引事業者やデータ利活用事業者に関し、システムに参加している事業者の数に応じたデータ利活用サーバ３０や取引サーバ４０が情報流通システムに含まれる。 The configuration shown in FIG. 3 is an example, and is not intended to limit the configuration of the information distribution system disclosed herein. For example, an information distribution business may include two or more distribution control servers 10. Furthermore, regarding trading businesses and data utilization businesses, the information distribution system includes data usage servers 30 and transaction servers 40 according to the number of businesses participating in the system.
［システムの概略動作］
　続いて、第１の実施形態に係る情報流通システムの概略動作について説明する。 [Summary system operation]
Next, the general operation of the information distribution system according to the first embodiment will be explained.
　利用者は、サービスの提供を受けたいサービス事業者と個別に契約を締結する。例えば、利用者は、氏名等をサービス事業者に提供しつつ当該サービス事業者と新たな契約（サービスを享受するための契約）をしたい旨を申し出る。 　Users conclude individual contracts with the service providers they wish to receive services from. For example, a user requests to enter into a new contract (a contract for enjoying a service) with a service provider while providing his/her name, etc. to the service provider.
　例えば、病院を受診したい利用者は、氏名等が記載された健康保険証等を当該病院に提出する。あるいは、オンラインショッピングに係るサービスを提供するＥＣ（Electronic Commerce）事業者については、利用者は、当該ＥＣ事業者が運営するサービスサーバ２０にアクセスしアカウントを生成する。 For example, a user who wants to visit a hospital submits his or her health insurance card with his or her name written on it to the hospital. Alternatively, for an EC (Electronic Commerce) business that provides services related to online shopping, the user accesses the service server 20 operated by the EC business and creates an account.
　サービス事業者は、新規な顧客（利用者）を識別するための「個人識別ＩＤ」を生成する。例えば、病院は、利用者（患者）を管理するための診察券番号を採番し、当該診察券番号を個人識別ＩＤとして生成する。ＥＣ事業者は、顧客を管理するための会員番号等を個人識別ＩＤとして生成する。サービスサーバ２０は、生成した個人識別ＩＤ（例えば、診察券番号や会員番号等）をデータベース等に記憶する。 The service provider generates a "personal identification ID" for identifying new customers (users). For example, a hospital assigns a consultation ticket number for managing users (patients) and generates the consultation ticket number as a personal identification ID. The EC business generates a membership number or the like as a personal identification ID for managing customers. The service server 20 stores the generated personal identification ID (eg, medical card number, membership number, etc.) in a database or the like.
　個人識別ＩＤが生成されると、利用者は、サービス事業者からサービスの提供を受けることができる。例えば、利用者は病院から医療サービス（健康診断や診察等）を受ける。あるいは、利用者は、ＥＣ事業者を利用してオンラインショッピングを行う。 Once the personal identification ID is generated, the user can receive services from the service provider. For example, a user receives medical services (health checkup, medical examination, etc.) from a hospital. Alternatively, the user performs online shopping using an EC company.
　サービス事業者が利用者にサービスを提供したこと等で生じたユーザデータを、データ流通の対象とするためには、データの「蓄積」が必要になる。データ蓄積は、サービス事業者（ユーザデータの提供元）が、ユーザデータを第三者に提供可能なデータとして情報流通システムに登録することである。流通制御サーバ１０は、データ蓄積者（サービス事業者）から利用者に提供されるサービスに関するデータをデータ流通の対象とするためのデータ蓄積を制御する。即ち、流通制御サーバ１０は、ユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する。 In order to make user data generated by service providers providing services to users, etc., subject to data distribution, it is necessary to "accumulate" the data. Data accumulation means that a service provider (user data provider) registers user data in an information distribution system as data that can be provided to a third party. The distribution control server 10 controls data accumulation so that data related to services provided to users by a data accumulator (service provider) is targeted for data distribution. That is, the distribution control server 10 controls data accumulation for registering user data in the information distribution system as data that can be provided to a third party.
　蓄積されたデータがデータ流通の対象となる。また、ユーザデータの蓄積には利用者（ユーザデータ生成の元になった利用者）の承諾（データ蓄積に対する同意）が必要になる。 The accumulated data will be subject to data distribution. Furthermore, the accumulation of user data requires the consent of the user (the user from whom the user data was generated) (consent to data accumulation).
　「蓄積」は、サービス事業者が保持するユーザデータを情報流通（データ流通）の対象とするものであり、当該蓄積に同意した利用者には対価が支払われる。また、蓄積データ（データ活用に同意した利用者のユーザデータ）を保持するサービス事業者にも対価が支払われる。データ蓄積に対する対価は、情報流通システム（情報流通事業者）からデータ蓄積者及び利用者に支払われる。 "Storage" is the subject of information distribution (data distribution) to user data held by a service provider, and a fee is paid to the user who consents to the storage. Compensation will also be paid to service providers that hold the accumulated data (user data of users who have consented to the use of their data). Compensation for data storage is paid by the information distribution system (information distribution business) to the data storage person and the user.
　情報流通システムにおけるデータ流通の手段として「共有」と「提供」が存在する。流通制御サーバ１０は、データ蓄積により登録されたユーザデータを一のサービスサーバ２０から他のサービスサーバ２０に共有するためのデータ共有を制御する。流通制御サーバ１０は、データ蓄積により登録されたユーザデータをサービスサーバ２０からデータ利活用サーバ３０に提供するためのデータ提供を制御する。 "Sharing" and "providing" exist as means of data distribution in an information distribution system. The distribution control server 10 controls data sharing for sharing user data registered through data accumulation from one service server 20 to another service server 20. The distribution control server 10 controls data provision for providing user data registered through data accumulation from the service server 20 to the data utilization server 30.
　「共有」は、サービス事業者が、他のサービス事業者により蓄積されたデータを取得するための手段である。例えば、病院が利用者にサービス提供することで生成されたデータをＥＣ事業者が取得する際に「共有」によるデータ流通が用いられる。ＥＣ事業者は、データ共有により病院から取得したデータを用いて利用者によりよいサービスを提供する。 "Sharing" is a means for service providers to acquire data accumulated by other service providers. For example, data distribution through "sharing" is used when an EC business acquires data generated by a hospital providing services to users. EC businesses use data acquired from hospitals through data sharing to provide better services to users.
　「共有」は、サービス利用者自身の利便性の向上に用いられるため、利用者にデータ流通に対する対価（利用者に対する対価）は支払われない。「共有」は、利用者がサービス事業者からより良いサービスの提供を受けるため他のサービス事業者が蓄積したデータを活用するために使用されるためである。 "Sharing" is used to improve the convenience of service users themselves, so no compensation is paid to users for data distribution (compensation to users). This is because "sharing" is used for users to utilize data accumulated by other service providers in order to receive better services from service providers.
　「提供」は、データ利活用事業者が、他のサービス事業者により蓄積されたデータを取得するための手段である。例えば、製薬会社が病院から健康診断の結果や診察の結果を取得する際に「提供」によるデータ流通が用いられる。製薬会社は、データ提供により病院から取得したデータを用いて新薬の開発に役立てる。 "Provision" is a means for a data utilization business to acquire data accumulated by other service businesses. For example, when a pharmaceutical company obtains the results of a medical examination or medical examination from a hospital, data distribution through "provision" is used. Pharmaceutical companies use the data they obtain from hospitals to help develop new drugs.
　「提供」は、利用者に直接サービスを提供しないデータ利活用事業者が用いる手段のため、データ流通に対する対価（利用者に対する対価）が発生する。即ち、「提供」が行われると、利用者に対して対価が支払われる。また、「提供」が行われると、データ取得者（データ提供先）からデータ提供元（データ蓄積者）及び情報流通システム（情報流通事業者）に対して対価が支払われる。 "Provision" is a method used by data utilization businesses that do not directly provide services to users, so compensation for data distribution (compensation for users) will be incurred. That is, when "provision" is performed, consideration is paid to the user. Furthermore, when "provision" is performed, a consideration is paid from the data acquirer (data provider) to the data provider (data accumulator) and the information distribution system (information distribution business).
　なお、本願開示では、便宜上、取引事業者には対価（手数料）が発生しないものとして説明する。実際には、データ提供先からデータ提供元等に支払われる対価の一部が取引事業者に「手数料」として支払われてもよい。 In addition, in the disclosure of this application, for convenience, explanation will be given on the assumption that no consideration (commission) is incurred for the transaction business operator. In reality, a part of the consideration paid by the data provider to the data provider may be paid to the transaction business operator as a "commission."
　流通制御サーバ１０は、データ共有先（データの供給を受けるサービス事業者）が蓄積されたデータを取得するためのデータ共有を制御する。流通制御サーバ１０は、データ提供先（データの供給を受けるデータ利活用事業者）が蓄積されたデータを取得するためのデータ提供を制御する。 The distribution control server 10 controls data sharing for data sharing destinations (service providers receiving data supply) to acquire accumulated data. The distribution control server 10 controls data provision for a data provision destination (a data utilization business that receives data supply) to acquire accumulated data.
＜システムアカウントの生成＞
　情報流通システムの利用者は事前に登録（利用者登録、システム登録）を行う必要がある。より具体的には、利用者は、流通制御サーバ１０にアクセスし、アカウント生成のための手続きを行う。以降の説明において、情報流通システムに生成されたアカウントを「システムアカウント」と表記する。 <Creating a system account>
Users of the information distribution system must register in advance (user registration, system registration). More specifically, the user accesses the distribution control server 10 and performs procedures for creating an account. In the following description, the account generated in the information distribution system will be referred to as a "system account."
　システムアカウントを生成するため、利用者は、所持する端末５０を操作して、流通制御サーバ１０にアクセスする。端末５０のアクセスに応じて、流通制御サーバ１０は、システムアカウントを生成するためのＷＥＢ（ウェブ）ページを表示する。 In order to generate a system account, the user operates the terminal 50 in his possession to access the distribution control server 10. In response to the access from the terminal 50, the distribution control server 10 displays a WEB page for generating a system account.
　利用者は、システムアカウント生成のための操作（例えば、所定ボタンの押下）を行い、システムアカウントを生成する。その際、流通制御サーバ１０は、利用者のシステムアカウント生成に必要な情報を取得する。具体的には、流通制御サーバ１０は、利用者のログイン情報（ログインＩＤ、パスワード）や個人情報（氏名、生年月日、連絡先、口座情報等）を取得する。 The user performs an operation (for example, pressing a predetermined button) to generate a system account. At this time, the distribution control server 10 acquires information necessary for generating the user's system account. Specifically, the distribution control server 10 acquires the user's login information (login ID, password) and personal information (name, date of birth, contact information, account information, etc.).
　ログイン情報、個人情報等を取得すると、流通制御サーバ１０は、当該利用者を情報流通システムにおいて一意に識別するためのユーザＩＤ（Identifier）を生成する。 Upon acquiring login information, personal information, etc., the distribution control server 10 generates a user ID (Identifier) for uniquely identifying the user in the information distribution system.
　流通制御サーバ１０は、当該生成された利用者のユーザＩＤ、ログイン情報及び個人情報（例えば、氏名、生年月日、連絡先）等を対応付けて記憶する。流通制御サーバ１０は、これらの情報を「利用者情報データベース」に記憶する。利用者情報データベースの詳細は後述する。 The distribution control server 10 associates and stores the generated user ID, login information, personal information (for example, name, date of birth, contact information), etc. of the user. The distribution control server 10 stores this information in a "user information database." Details of the user information database will be described later.
　流通制御サーバ１０は、生成したユーザＩＤを利用者（端末５０）に払い出す。端末５０は、払い出されたユーザＩＤを記憶する。 The distribution control server 10 issues the generated user ID to the user (terminal 50). The terminal 50 stores the issued user ID.
＜ＩＤの連携＞
　上述のように、サービス事業者が保持するユーザデータをデータ流通の対象とするためには、「データ蓄積」が必要となる。データ蓄積を実現するためには、システムアカウントのＩＤ（ユーザＩＤ）とサービス事業者が生成したＩＤ（個人識別ＩＤ）を連携する必要がある。 <ID cooperation>
As mentioned above, "data accumulation" is required in order to make user data held by a service provider the subject of data distribution. In order to realize data accumulation, it is necessary to link the system account ID (user ID) and the ID (personal identification ID) generated by the service provider.
　例えば、図４に示すように、利用者は病院の窓口において、当該病院が保持するユーザデータの活用を希望している旨を病院職員に伝える（データ活用の申し込みを行う）。病院職員は、利用者の個人特定情報、利用者の個人識別ＩＤ（例えば、診察券番号）及び事業者コードを病院端末６０に入力する。 For example, as shown in FIG. 4, a user goes to a hospital counter and tells hospital staff that he or she wishes to utilize user data held by the hospital (applies for data utilization). The hospital staff inputs the user's personal identification information, the user's personal identification ID (eg, medical card number), and the company code into the hospital terminal 60.
　なお、個人特定情報は、利用者を特定するための情報である。個人特定情報には、利用者の氏名、又は、氏名と生年月日の組み合わせ等が例示される。 Note that personal identification information is information for identifying the user. Examples of the personal identification information include the user's name or a combination of name and date of birth.
　また、事業者コードは、情報流通システムに参加するサービス事業者を識別するための識別情報（ＩＤ）である。例えば、病院とＥＣ事業者には異なるコードが割り当てられる。事業者コードは、任意の手段によりシステム参加者（情報流通事業者、サービス事業者、データ利活用事業者）の間で共有される。例えば、サービス事業者が情報流通システムに参加する際、情報流通事業者が当該サービス事業者に割り当てる事業者コードを生成する。情報流通事業者は、当該生成した事業者コードをサービス事業者等に通知する。 Further, the business code is identification information (ID) for identifying a service business that participates in the information distribution system. For example, different codes are assigned to hospitals and e-commerce businesses. The business code is shared among system participants (information distribution business, service business, data utilization business) by any means. For example, when a service provider participates in an information distribution system, the information distribution provider generates a provider code to be assigned to the service provider. The information distribution business operator notifies the service business operator, etc. of the generated business code.
　病院端末６０は、取得した個人特定情報、個人識別ＩＤ及び事業者コードを含む「ＩＤ連携要求」を流通制御サーバ１０に送信する。 The hospital terminal 60 transmits an "ID cooperation request" including the acquired personal identification information, personal identification ID, and business code to the distribution control server 10.
　あるいは、ＥＣ事業者のユーザデータの活用を希望する利用者は、端末５０を操作して、当該ＥＣ事業者のサービスサーバ２０にアクセスする（図５参照）。利用者は、ＥＣ事業者のアカウントにログインし、当該アカウント上でデータ活用のための申請を行う。当該申請に応じて、サービスサーバ２０は、利用者の個人特定情報、個人識別ＩＤ及び事業者コードを含む「ＩＤ連携要求」を流通制御サーバ１０に送信する。 Alternatively, a user who wishes to utilize the user data of an EC company operates the terminal 50 to access the service server 20 of the EC company (see FIG. 5). The user logs into the EC company's account and applies for data utilization on the account. In response to the application, the service server 20 transmits an "ID cooperation request" including the user's personal identification information, personal identification ID, and business code to the distribution control server 10.
　流通制御サーバ１０は、病院端末６０やサービスサーバ２０からＩＤ連携希望者の個人特定情報、個人識別ＩＤ及びＩＤ連携の対象となるサービス事業者（例えば、病院、ＥＣ事業者）の事業者コードを取得する。 The distribution control server 10 receives, from the hospital terminal 60 and the service server 20, the personal identification information of the person requesting ID cooperation, the personal identification ID, and the company code of the service provider (for example, hospital, e-commerce company) that is the target of ID cooperation. get.
　流通制御サーバ１０は、事業者コードからＩＤ連携の対象となっているサービス事業者を特定する。また、流通制御サーバ１０は、個人特定情報からシステムアカウントに登録された利用者を特定する。流通制御サーバ１０は、当該特定した利用者のアカウントにおいてサービス事業者と個人識別ＩＤを対応付ける。 The distribution control server 10 identifies the service provider targeted for ID cooperation from the provider code. Further, the distribution control server 10 identifies the user registered in the system account from the personal identification information. The distribution control server 10 associates the service provider with the personal identification ID in the account of the identified user.
　個人識別ＩＤがシステムアカウントに登録されると（ＩＤ連携が完了すると）、ＩＤ連携の対象となったサービス事業者は、データ活用を希望する利用者のユーザデータを「蓄積」可能となる。 Once the personal identification ID is registered in the system account (ID linkage is completed), the service provider targeted for ID linkage will be able to "accumulate" user data of users who wish to utilize the data.
＜データ蓄積＞
　情報流通事業者の職員等は、データ蓄積に対する対価の基準を作成する。職員等は、作成した対価の基準を流通制御サーバ１０に登録する。流通制御サーバ１０は、当該登録された蓄積対価の基準を「蓄積対価定義」として公開する（図６参照）。 <Data accumulation>
Employees of information distribution businesses will create standards for compensation for data accumulation. A staff member or the like registers the created compensation standard in the distribution control server 10. The distribution control server 10 publishes the registered standard of accumulated consideration as "accumulated consideration definition" (see FIG. 6).
　図６に示すように、蓄積対価定義には、蓄積対価定義を識別するための蓄積対価ＩＤ、対価の支払い対象となるデータセット（データ種類）、１データの蓄積により情報流通システム（情報流通事業者）から支払われる対価、対価の分配率を含む。対価の支払い対象となるデータ種類は、蓄積されるユーザデータの種類である。蓄積対価定義は、データ種類ごとに予め定められる。対価の分配率は、情報流通事業者から支払われる対価のサービス事業者と利用者の分配率である。 As shown in Figure 6, the accumulated consideration definition includes an accumulated consideration ID for identifying the accumulated consideration definition, a data set (data type) for which consideration is to be paid, and an information distribution system (information distribution business) by accumulating one data. Includes the consideration paid by the person (individual) and the distribution rate of the consideration. The data type for which compensation is to be paid is the type of user data to be accumulated. The accumulation consideration definition is determined in advance for each data type. The distribution rate of consideration is the distribution rate between the service provider and the user of the consideration paid by the information distribution business.
　図６は、「病名」に分類されるデータを蓄積すると１０円の対価がデータ蓄積者と利用者に支払われることを示す。また、図６は、対価のうち８０％はデータ蓄積者（病院等）に支払われ、２０％は利用者に支払われることを示す。 FIG. 6 shows that when data classified as "disease name" is stored, a compensation of 10 yen is paid to the data storage person and the user. Further, FIG. 6 shows that 80% of the consideration is paid to the data accumulator (hospital, etc.) and 20% is paid to the user.
　サービス事業者は、利用者にサービスを提供すると、当該利用者の個人識別ＩＤとユーザデータ（パーソナルデータ）を対応付けて記憶する。例えば、病院は、利用者の診察を行い病名が得られると、当該利用者の個人識別ＩＤ（診察券番号等）と病名（例えば、胃がん等の具体的な病名）を対応付けて記憶する。例えば、サービスサーバ２０は、「顧客情報データベース」を用いて利用者の個人識別ＩＤとユーザデータを対応付けて記憶する。なお、顧客情報データベースの詳細は後述する。 When a service provider provides a service to a user, the service provider stores the user's personal identification ID and user data (personal data) in association with each other. For example, when a hospital examines a user and obtains the name of the disease, the hospital stores the user's personal identification ID (examination ticket number, etc.) in association with the disease name (for example, a specific disease name such as stomach cancer). For example, the service server 20 uses a "customer information database" to store the user's personal identification ID and user data in association with each other. Note that details of the customer information database will be described later.
　サービス事業者のサービスサーバ２０は、ＩＤ連携の完了した利用者（データ活用の申し込みをした利用者）に関し、ユーザデータ（サービス提供の結果生じるデータ、サービスの提供に必要なデータ）を記憶するたびに、データ蓄積に関する制御を行う。 Every time the service server 20 of the service provider stores user data (data generated as a result of service provision, data necessary for service provision) regarding a user who has completed ID linkage (a user who has applied for data utilization), In addition, controls related to data accumulation are performed.
　具体的には、サービスサーバ２０は、ユーザデータを取得した利用者を指定し、データ蓄積に関する同意を取得するように流通制御サーバ１０に要求する。サービスサーバ２０は、当該利用者の個人識別ＩＤ、事業者コード及び蓄積するユーザデータに関する情報（ユーザデータ情報）を含む「蓄積同意取得要求」を流通制御サーバ１０に送信する（図７のステップＳ０１）。 Specifically, the service server 20 specifies the user who has acquired the user data, and requests the distribution control server 10 to obtain consent regarding data storage. The service server 20 transmits a "storage consent acquisition request" including the user's personal identification ID, business code, and information regarding the user data to be stored (user data information) to the distribution control server 10 (step S01 in FIG. 7). ).
　ユーザデータ情報には、サービス事業者（サービスサーバ２０）が取得したユーザデータの種類（例えば、病名）や当該データの取得日時等が含まれる。 The user data information includes the type of user data (for example, disease name) acquired by the service provider (service server 20), the date and time of acquisition of the data, and the like.
　蓄積同意取得要求を受信すると、流通制御サーバ１０は、個人識別ＩＤ及び事業者コードに基づいて利用者を特定する。流通制御サーバ１０は、特定した利用者に対し、ユーザデータ情報等を含むデータ蓄積の問合せを送信する（ステップＳ０２）。 Upon receiving the accumulation consent acquisition request, the distribution control server 10 identifies the user based on the personal identification ID and the business code. The distribution control server 10 transmits a data storage inquiry including user data information etc. to the specified user (step S02).
　データ蓄積の問合せを受信した端末５０は、データ蓄積に関する利用者の意思を取得する。例えば、端末５０は、ＧＵＩ（Graphical User Interface）を用いて利用者の意思を取得する。例えば、端末５０は、「２０２１年４月１日の診察で得られた病名の蓄積に同意しますか？」といった内容のＧＵＩを用いて、利用者の意思（データ蓄積に同意、不同意）を取得する。 The terminal 50 that has received the data storage inquiry acquires the user's intention regarding data storage. For example, the terminal 50 uses a GUI (Graphical User Interface) to obtain the user's intention. For example, the terminal 50 displays the user's intention (agree or disapprove to the data storage) using a GUI that says, "Do you agree to the storage of the disease name obtained from the medical examination on April 1, 2021?" get.
　その際、端末５０は、流通制御サーバ１０により公開されている蓄積対価定義に基づき得られるデータ蓄積に対する対価を利用者に提示してもよい。 At that time, the terminal 50 may present the user with compensation for data accumulation, which is obtained based on the accumulation compensation definition published by the distribution control server 10.
　端末５０は、データ蓄積の問合せに対する応答（データ蓄積に同意、又は、データ蓄積を拒否）を流通制御サーバ１０に送信する（ステップＳ０３）。 The terminal 50 transmits a response to the data storage inquiry (agreeing to data storage or refusing data storage) to the distribution control server 10 (step S03).
　流通制御サーバ１０は、端末５０から取得したデータ蓄積の問合せに対する応答をサービスサーバ２０に転送する。流通制御サーバ１０は、蓄積同意取得要求に対する応答として端末５０から取得した応答をサービスサーバ２０に送信する（ステップＳ０４）。 The distribution control server 10 transfers the response to the data storage inquiry obtained from the terminal 50 to the service server 20. The distribution control server 10 transmits the response obtained from the terminal 50 to the service server 20 as a response to the storage consent acquisition request (step S04).
　このように、サービスサーバ２０は、利用者にサービスを提供したことに応じて、ユーザデータを記憶すると、当該ユーザデータに関する情報を含む蓄積同意取得要求を流通制御サーバ１０に送信する。流通制御サーバ１０は、利用者が所持する端末５０に、ユーザデータに関する情報を含むデータ蓄積の問合せを送信し、端末５０からデータ蓄積の問合せに対する応答を受信する。流通制御サーバ１０は、受信した応答をサービスサーバ２０に転送する。 In this manner, when the service server 20 stores user data in response to providing a service to the user, it transmits a storage consent acquisition request including information regarding the user data to the distribution control server 10. The distribution control server 10 transmits a data storage inquiry including information regarding user data to a terminal 50 owned by the user, and receives a response to the data storage inquiry from the terminal 50. The distribution control server 10 transfers the received response to the service server 20.
　利用者がデータ蓄積を拒否した場合、サービスサーバ２０は特段の対応を行わない。 If the user refuses data storage, the service server 20 does not take any special action.
　利用者がデータ蓄積に同意した場合、サービスサーバ２０は、当該データ蓄積に同意した利用者のユーザデータを蓄積データとして情報流通システムに登録する。具体的には、サービスサーバ２０は、データ蓄積に同意した利用者に関する「所在情報」を流通制御サーバ１０に送信する（図８参照）。 If the user agrees to data accumulation, the service server 20 registers the user data of the user who has consented to the data accumulation in the information distribution system as accumulated data. Specifically, the service server 20 transmits "location information" regarding users who have consented to data storage to the distribution control server 10 (see FIG. 8).
　所在情報は、ユーザデータの保管場所（データの蓄積主体；サービス事業者）等に関する情報である。所在情報には、ユーザデータ（蓄積データ）を識別するためのデータＩＤ、個人識別ＩＤ、事業者コード、保持するデータの種類等が含まれる。 The location information is information regarding the storage location of user data (data storage entity; service provider), etc. The location information includes a data ID for identifying user data (accumulated data), a personal identification ID, a business code, the type of data held, and the like.
　流通制御サーバ１０は、取得した所在情報を「所在情報データベース」に記憶する。所在情報データベースの詳細は後述する。当該所在情報データベースは、データＩＤ、個人識別ＩＤ、事業者コード及びデータ種類等を対応付けて記憶する。 The distribution control server 10 stores the acquired location information in the "location information database." Details of the location information database will be described later. The location information database stores data ID, personal identification ID, business code, data type, etc. in association with each other.
　流通制御サーバ１０は、蓄積取引の履歴を取引台帳に登録する。流通制御サーバ１０は、蓄積取引の履歴に基づき、予め定められたタイミング（例えば、月初）でデータ蓄積に関する対価を支払う。流通制御サーバ１０は、公開された蓄積対価定義に基づきデータ蓄積者と利用者に対価を支払う。 The distribution control server 10 registers the history of accumulated transactions in the transaction ledger. The distribution control server 10 pays compensation for data accumulation at a predetermined timing (for example, at the beginning of the month) based on the history of accumulation transactions. The distribution control server 10 pays remuneration to the data accumulator and user based on the published accumulation remuneration definition.
　このように、サービスサーバ２０は、利用者がユーザデータの蓄積に同意すると、サービスサーバ２０に記憶されたユーザデータのデータ種類を含む所在情報を流通制御サーバ１０に送信する。流通制御サーバ１０は、所在情報を受信したことに応じてユーザデータのデータ蓄積を行う。その後、流通制御サーバ１０は、サービス事業者及び利用者にデータ蓄積に対する蓄積対価を支払う。その際、流通制御サーバ１０は、蓄積対価定義に基づき、サービス事業者と利用者に支払う蓄積対価を算出する。 In this way, when the user agrees to store user data, the service server 20 transmits location information including the data type of the user data stored in the service server 20 to the distribution control server 10. The distribution control server 10 stores user data in response to receiving the location information. Thereafter, the distribution control server 10 pays the service provider and the user an accumulation fee for data accumulation. At this time, the distribution control server 10 calculates the accumulated consideration to be paid to the service provider and the user based on the accumulated consideration definition.
＜データ共有＞
　他のサービス事業者が蓄積したデータ（他のサービス事業者が利用者にサービスを提供した結果生じたユーザデータ）の取得を希望するサービス事業者は、「共有」によって当該データを取得する。 <Data sharing>
A service provider who wishes to acquire data accumulated by another service provider (user data generated as a result of other service providers providing services to users) obtains the data through "sharing."
　ここでは、図９を参照しつつ、ＥＣ事業者Ｂが、病院Ａに蓄積された利用者のデータ（診察結果；病名）を「共有」により取得する場合について説明する。なお、病院はサービスサーバ２０－１を備え、ＥＣ事業者はサービスサーバ２０－２を備える。 Here, with reference to FIG. 9, a case will be described in which EC company B acquires user data (medical examination results; disease name) accumulated in hospital A by "sharing". Note that the hospital is equipped with a service server 20-1, and the EC business is equipped with a service server 20-2.
　ＥＣ事業者Ｂ（サービスサーバ２０－２）は、「共有要請」を流通制御サーバ１０に送信する（ステップＳ１１）。 EC business operator B (service server 20-2) transmits a "sharing request" to distribution control server 10 (step S11).
　流通制御サーバ１０は、共有要請に基づいて、データ流通の対象者である利用者と流通させるデータのデータ蓄積者（病院Ａ）を特定する。流通制御サーバ１０は、特定された対象者が所持する端末５０に対して、データ共有に関する問合せを送信する（ステップＳ１２）。 Based on the sharing request, the distribution control server 10 identifies the user who is the target of data distribution and the data storage person (hospital A) of the data to be distributed. The distribution control server 10 transmits an inquiry regarding data sharing to the terminal 50 owned by the identified target person (step S12).
　データ共有の問合せを受信した端末５０は、データ共有に関する利用者の意思を取得する。例えば、端末５０は、ＧＵＩ（Graphical User Interface）を用いて利用者の意思を取得する。上記の例では、端末５０は、「病院の診察結果をＥＣ事業者へ共有することで、より良いサービスが受けられます。共有しますか？」といった内容のＧＵＩを表示し、利用者の意思（データ共有に同意、不同意）を取得する。 The terminal 50 that has received the data sharing inquiry acquires the user's intention regarding data sharing. For example, the terminal 50 uses a GUI (Graphical User Interface) to obtain the user's intention. In the above example, the terminal 50 displays a GUI that says, "You can receive better service by sharing your hospital examination results with the e-commerce company. Do you want to share?" and displays the user's intention. (Agree/disagree to data sharing).
　端末５０は、データ共有の問合せに対する応答（データ共有に同意、又は、データ共有を拒否）を流通制御サーバ１０に送信する（ステップＳ１３）。 The terminal 50 transmits a response to the data sharing inquiry (agreeing to data sharing or refusing data sharing) to the distribution control server 10 (step S13).
　利用者の同意が得られれば、流通制御サーバ１０は、データ蓄積者（病院Ａ）に対して共有指示を送信する（ステップＳ１４）。 If the user's consent is obtained, the distribution control server 10 transmits a sharing instruction to the data storage person (hospital A) (step S14).
　共有指示を受信した病院Ａ（サービスサーバ２０－１）は、顧客情報データベースを参照し、対象となる利用者の診察結果（病名）等を指定されたデータ共有先であるサービスサーバ２０－２に送信する（ステップＳ１５）。 Hospital A (service server 20-1), which received the sharing instruction, refers to the customer information database and sends the examination results (disease name) of the target user to the service server 20-2, which is the designated data sharing destination. Transmit (step S15).
　続いて、「提供」によるデータ流通について説明する。 Next, we will explain data distribution by "provision".
＜口座開設＞
　データ提供により対価を取得しようとする利用者は、取引事業者に口座を開設する必要がある。図１０を参照しつつ、提供のための口座開設について説明する。 <Account opening>
Users who wish to receive compensation by providing data must open an account with a transaction operator. Opening an account for provision will be explained with reference to FIG.
　取引事業者は、情報流通システムに参加する複数のサービス事業者のうち少なくとも１以上のサービス事業者と提携を行う。例えば、医療に関するデータを取り扱う取引事業者は、医療機関（病院、薬局等）と提携する。あるいは、教育に関するデータを取り扱う取引事業者は、教育事業者と提携する。取引事業者は、提携先のサービス事業者に関する事業者コードを記憶する。 The transaction business operator forms an alliance with at least one service business operator among the multiple service business operators participating in the information distribution system. For example, a trading company that handles medical data collaborates with medical institutions (hospitals, pharmacies, etc.). Alternatively, a trading business that handles education-related data collaborates with an education business. The transaction business operator stores a business code related to the partner service business operator.
　また、取引事業者は、データ利活用事業者の事業者コードを記憶する。例えば、取引事業者は、データ利活用事業者と取引を開始する際に当該データ利活用事業者の事業者コードを生成する。データ利活用事業者の事業者コードは、任意の方法によって、情報流通事業者、取引事業者及びデータ利活用事業者の間で共有される。 Additionally, the transaction business operator stores the business code of the data utilization business operator. For example, when a trading business starts a transaction with a data utilization business, it generates a business code of the data utilization business. The business code of the data utilization business is shared among the information distribution business, transaction business, and data utilization business by any method.
　取引事業者は、提携先のサービス事業者が保持するデータ（蓄積されたデータ）をデータ利活用事業者に販売する（販売の仲介をする）。例えば、図１０に示す提携サービス事業者が医療機関であれば、取引事業者は、提携先の医療機関が保持するデータを製薬会社等に販売する。 The trading business entity sells the data (accumulated data) held by the partner service business entity to the data utilization business entity (acts as an intermediary in the sale). For example, if the affiliated service provider shown in FIG. 10 is a medical institution, the transaction provider sells data held by the affiliated medical institution to a pharmaceutical company or the like.
　上述のように、取引事業者を介したデータ提供により対価を取得したい利用者は、取引事業者（取引サーバ４０）に口座を開設する必要がある。情報流通システムに参加する利用者のうちデータ提供により収益を得たい利用者は、取引サーバ４０に「情報口座」を開設する。 As mentioned above, a user who wishes to obtain consideration by providing data through a transaction operator needs to open an account with the transaction operator (transaction server 40). Among the users who participate in the information distribution system, those who wish to earn profits by providing data open an "information account" in the transaction server 40.
　利用者は、流通制御サーバ１０から払い出されたユーザＩＤを取引サーバ４０に提示し、情報口座を開設する。取引サーバ４０は、取得したユーザＩＤを記憶する。取引サーバ４０は、口座開設した利用者のユーザＩＤを口座開設者リストにより管理する。 The user presents the user ID issued by the distribution control server 10 to the transaction server 40 and opens an information account. Transaction server 40 stores the acquired user ID. The transaction server 40 manages user IDs of users who have opened accounts using an account opener list.
＜カタログ情報＞
　「提供」によるデータ流通を実現するため、情報流通事業者はカタログ情報を用意する。情報流通事業者の担当者（システム管理者）は、販売可能なデータを記載したカタログ情報を定義する（図１１参照）。カタログ情報は、情報流通システムがデータ利活用事業者に販売可能なデータの詳細を示す情報である。 <Catalog information>
In order to realize data distribution by "provision", information distribution businesses prepare catalog information. The person in charge (system administrator) of the information distribution business defines catalog information that describes data that can be sold (see FIG. 11). Catalog information is information indicating details of data that the information distribution system can sell to data utilization businesses.
　図１１に示すカタログ情報に含まれるデータセット名は、カタログ情報を識別するための情報である。例えば、健康診断に関するデータセットには「検診結果１」、診察結果に関するデータセットには「診察結果１」といったデータセット名が付与される。 The data set name included in the catalog information shown in FIG. 11 is information for identifying the catalog information. For example, a data set related to a medical examination is given a data set name such as "Examination Results 1", and a data set related to medical examination results is given a data set name such as "Examination Results 1".
　カタログ情報に含まれるデータ種類は、サービス事業者が保持しているデータ（第三者に提供可能な蓄積データ）の種類を示す。例えば、検診結果における「身長」、「体重」、「血圧」や診察結果における「病名」、「服薬」、「検査結果」等の情報がデータ種類に相当する。データフォーマットは、どのような形式でデータが提供されるのかを規定する。 The data type included in the catalog information indicates the type of data held by the service provider (accumulated data that can be provided to a third party). For example, information such as "height", "weight", and "blood pressure" in the medical examination results, and "disease name", "medication taking", and "examination results" in the medical examination results correspond to the data type. The data format defines the format in which data is provided.
　データ利活用事業者は、取引事業者を介してカタログ情報を取得する。より具体的には、データ利活用サーバ３０は、取引サーバ４０に対して「カタログ情報提示要求」を送信する。 The data utilization business obtains catalog information through the transaction business. More specifically, the data utilization server 30 transmits a “catalog information presentation request” to the transaction server 40.
　カタログ情報提示要求を受信すると、取引サーバ４０は、流通制御サーバ１０に対して「カタログ情報送信要求」を送信する。 Upon receiving the catalog information presentation request, the transaction server 40 transmits a "catalog information transmission request" to the distribution control server 10.
　カタログ情報送信要求の受信に応じて、流通制御サーバ１０は、情報流通事業者により定義されたカタログ情報を取引サーバ４０に送信する。 In response to receiving the catalog information transmission request, the distribution control server 10 transmits catalog information defined by the information distribution business to the transaction server 40.
　取引サーバ４０は、提携先のサービス事業者に関するカタログ情報を選択し、データ利活用サーバ３０に送信する。例えば、上記の例では、取引サーバ４０は、製薬会社の業務に関するカタログ情報を選択してデータ利活用事業者に送信する。データ利活用事業者は、受信したカタログ情報を閲覧し、自身の事業に必要なカタログ情報を特定する。 The transaction server 40 selects catalog information regarding the partner service provider and transmits it to the data utilization server 30. For example, in the above example, the transaction server 40 selects catalog information related to the business of a pharmaceutical company and transmits it to the data utilization business. The data utilization business views the received catalog information and identifies the catalog information necessary for its own business.
＜提供によるデータ流通＞
　サービス事業者が蓄積したデータの取得を希望するデータ利活用事業者は、「提供」によって当該データを取得する。 <Data distribution by provision>
A data utilization business that wishes to acquire data accumulated by a service business will acquire the data through "provision."
　ここでは、製薬会社Ｃが、病院Ａの蓄積データ（診察結果；例えば、病名）を「提供」により取得する場合について説明する。 Here, a case will be described in which pharmaceutical company C acquires accumulated data (medical examination results; for example, disease name) of hospital A by "provision."
　情報流通事業者の職員等は、データ提供に対する対価の基準を作成する。職員等は、作成した対価の基準を流通制御サーバ１０に登録する。流通制御サーバ１０は、当該登録された提供対価の基準を「提供対価定義」として公開する（図１２参照）。 Employees of information distribution business operators, etc. will create standards for compensation for data provision. A staff member or the like registers the created compensation standard in the distribution control server 10. The distribution control server 10 publishes the registered standard of the provided consideration as a "provided consideration definition" (see FIG. 12).
　図１２に示すように、提供対価定義には、提供対価定義を識別するための提供対価ＩＤ、対価の支払い対象となるデータセット（データ種類）、１つのデータの提供によりデータ提供先（製薬会社Ｃ）から支払われる対価、対価の分配率を含む。対価の支払い対象となるデータ種類は、提供されるユーザデータのデータ種類である。対価の分配率は、データ利活用事業者から支払われる対価のサービス事業者、利用者及び流通事業者それぞれへの分配率である。 As shown in Figure 12, the provided consideration definition includes the provided consideration ID for identifying the provided consideration definition, the data set (data type) for which consideration is to be paid, and the data provider (pharmaceutical company) by providing one data. Includes the consideration paid from C) and the distribution rate of the consideration. The data type for which compensation is to be paid is the data type of the provided user data. The distribution rate of consideration is the distribution rate of the consideration paid by the data utilization business to the service business, the user, and the distribution business.
　図１２は、「病名」のデータを提供すると１５円の対価がデータ提供先から支払われることを示す。また、図１２は、得られた対価のうち７０％はデータ蓄積者（病院等）に支払われ、２０％は利用者に支払われ、１０％は情報流通事業者（情報流通システムのコンソーシアム）に支払われることを示す。 FIG. 12 shows that if you provide the "disease name" data, a compensation of 15 yen will be paid by the data provider. In addition, Figure 12 shows that 70% of the compensation obtained is paid to the data accumulator (hospital, etc.), 20% is paid to the user, and 10% is paid to the information distribution business (information distribution system consortium). Indicates that it will be paid.
　データ提供先（製薬会社Ｃ）の職員等は、公開されているカタログ情報、提供対価定義を参照し、データ提供申込を作成する。職員等は、データ利活用サーバ３０に図１３に示すようなデータ提供申込を入力する。データ提供申込には、データ提供によりデータ利活用事業者に提供される提供データの要件と、データ提供によりデータ利活用事業者が支払う提供対価の提示に関する詳細を含む提供対価提示と、が含まれる。 Employees of the data provider (Pharmaceutical Company C) refer to the published catalog information and provision consideration definition and create a data provision application. A staff member or the like inputs a data provision application as shown in FIG. 13 into the data utilization server 30. The data provision application includes requirements for the provided data to be provided to the data utilization business as a result of the data provision, and a provision consideration presentation that includes details regarding the presentation of the provision consideration to be paid by the data utilization business as a result of the data provision. .
　図１３に示すように、データ提供申込には、データ提供を要請する事業者の情報、データ提供の対象となるデータの種類、取得を希望するデータ量、データ提供先から支払われる対価、対価の分配率を含む。 As shown in Figure 13, the data provision application includes information on the business requesting data provision, the type of data to be provided, the amount of data desired to be obtained, the consideration to be paid by the data provider, and the amount of consideration. Including distribution rate.
　なお、データ提供を要請する事業者（データ利活用事業者、例えば、製薬会社Ｃ）に関する情報は、当該事業者の名称、事業者コード、データの提供先（データの送信先アドレス）等を含む。 Information regarding the business entity requesting data provision (data utilization business entity, for example, pharmaceutical company C) includes the name of the business entity, business code, data provision destination (data transmission destination address), etc. .
　図１４を参照して、データ提供時の情報流通システムの動作を説明する。 With reference to FIG. 14, the operation of the information distribution system when providing data will be explained.
　はじめに、データ利活用サーバ３０は、データ提供申込を取引サーバ４０に送信する（ステップＳ２１）。 First, the data utilization server 30 transmits a data provision application to the transaction server 40 (step S21).
　データ提供申込を受信した取引サーバ４０は、データ提供申込に提供申込ＩＤを付与して当該受信したデータ提供申込を管理する。その後、取引サーバ４０は、提供申込ＩＤ、データ提供申込と口座開設者リストを含む「提供要請」を流通制御サーバ１０に送信する（ステップＳ２２）。 The transaction server 40 that receives the data provision application assigns a provision application ID to the data provision application and manages the received data provision application. Thereafter, the transaction server 40 transmits a "provision request" including the provision application ID, data provision application, and account opener list to the distribution control server 10 (step S22).
　流通制御サーバ１０は、提供要請の受信に応じて、データ提供元（データ蓄積者）に関する通知とデータ提供に関する利用者の同意取得を行う。 In response to receiving the provision request, the distribution control server 10 notifies the data provider (data accumulator) and obtains the user's consent regarding the data provision.
　流通制御サーバ１０は、所在情報データベースを参照し、データ提供申込に記載されたデータ種類を保持するデータ蓄積者（データ提供元）を特定する。流通制御サーバ１０は、特定したデータ蓄積者に関する情報を取引サーバ４０に通知する。具体的には、流通制御サーバ１０は、提供申込ＩＤ、特定したデータ蓄積者の名称、連絡先（サービスサーバ２０のアドレス）等を含む「提供元通知」を取引サーバ４０に送信する（ステップＳ２３）。 The distribution control server 10 refers to the location information database and identifies the data accumulator (data provider) that holds the data type described in the data provision application. The distribution control server 10 notifies the transaction server 40 of information regarding the identified data accumulator. Specifically, the distribution control server 10 transmits a "provider notification" including the provision application ID, the name of the identified data storage person, contact information (address of the service server 20), etc. to the transaction server 40 (step S23). ).
　また、流通制御サーバ１０は、口座開設者リストに記載された利用者であって、データ提供の対象となるデータ種類に対応する蓄積データの発生に寄与（関連）した利用者の個人識別ＩＤを特定する。 Additionally, the distribution control server 10 stores the personal identification IDs of users who are listed in the account opener list and who contributed to (related to) the generation of accumulated data corresponding to the type of data to be provided. Identify.
　流通制御サーバ１０は、特定された個人識別ＩＤに対応する利用者の連絡先（端末５０が受信可能なメールアドレス）にデータ提供に関する問合せを送信する（ステップＳ２４）。 The distribution control server 10 transmits an inquiry regarding data provision to the contact information (email address that can be received by the terminal 50) of the user corresponding to the specified personal identification ID (step S24).
　データ提供の問合せには、データ提供の要請元（上記の例では製薬会社Ｃ）の情報、データ蓄積者（病院Ａ）の情報、提供が要望されたデータ種類（例えば、病名）が含まれる。 The data provision inquiry includes information on the data provision requestor (in the above example, pharmaceutical company C), information on the data storage person (hospital A), and the type of data requested to be provided (for example, disease name).
　データ提供の問合せを受信した端末５０は、データ提供に関する利用者の意思を取得するためのＧＵＩを表示する。端末５０は、ＧＵＩを用いて、利用者の意思（データ提供に同意、不同意）を取得する。 The terminal 50 that has received the inquiry for data provision displays a GUI for acquiring the user's intention regarding data provision. The terminal 50 uses the GUI to obtain the user's intention (agree or disapprove to data provision).
　端末５０は、データ提供の問合せに対する応答（データ提供に同意、又は、データ提供を拒否）を流通制御サーバ１０に送信する（ステップＳ２５）。 The terminal 50 transmits a response to the data provision inquiry (agreeing to the data provision or refusing the data provision) to the distribution control server 10 (step S25).
　このように、流通制御サーバ１０は、提供要請を受信すると、データ提供の対象となる利用者を特定し、当該特定された利用者の端末５０に、データ提供の問合せを送信することで、データ提供に利用者が同意するか否かを取得する。また、流通制御サーバ１０は、データ提供の対象となるユーザデータを記憶しているサービス事業者を特定し、当該特定したサービス事業者の情報を含む提供元通知を取引サーバ４０に送信する。 In this way, upon receiving the request for data provision, the distribution control server 10 identifies the user to whom the data is to be provided, and sends a data provision inquiry to the terminal 50 of the identified user. Obtain whether the user agrees to the provision or not. Further, the distribution control server 10 specifies a service provider that stores user data to which the data is to be provided, and transmits a provider notification containing information on the identified service provider to the transaction server 40.
　取引サーバ４０は、提供元通知を受信し、流通制御サーバ１０により特定されたサービス事業者に対してデータ利活用事業者との間でデータ提供申込の契約締結を依頼する。具体的には、取引サーバ４０は、提供申込ＩＤ及びデータ提供申込を含む「提供契約締結依頼」を流通制御サーバ１０から通知された連絡先（例えば、病院Ａのサービスサーバ２０－１）に送信する（ステップＳ２６）。 The transaction server 40 receives the provider notification and requests the service provider specified by the distribution control server 10 to conclude a data provision application contract with the data utilization provider. Specifically, the transaction server 40 sends a “provision contract conclusion request” including the provision application ID and data provision application to the contact information notified from the distribution control server 10 (for example, the service server 20-1 of hospital A). (Step S26).
　提供契約締結依頼を受信したことに応じて、データ蓄積者は、データ提供先（データ利活用事業者）とデータ提供に関する交渉を行う。データ蓄積者の職員等は、データ提供申込を検討した結果をサービスサーバ２０に入力する。サービスサーバ２０は、取得した検討結果に応じて提供契約締結依頼に対する応答を取引サーバ４０に送信する（ステップＳ２７）。 In response to receiving a request to conclude a provision contract, the data accumulator negotiates with the data provider (data utilization business) regarding data provision. A staff member of the data storage company inputs the results of examining the data provision application into the service server 20. The service server 20 transmits a response to the request for conclusion of a provision contract to the transaction server 40 in accordance with the obtained examination result (step S27).
　具体的には、データ提供申込に記載された条件（主に、データ提供に対する対価の提案）に同意すれば、データ蓄積者の職員は、その旨をサービスサーバ２０に入力する。サービスサーバ２０は、データ提供申込に応じる旨（データ提供契約を締結する旨）を示す肯定応答を取引サーバ４０に送信する。 Specifically, if the employee of the data storage company agrees to the conditions stated in the data provision application (mainly the proposal for compensation for data provision), the data storage employee will input this into the service server 20. The service server 20 transmits an affirmative response to the transaction server 40 indicating that the service server 20 accepts the data provision application (concludes a data provision contract).
　データ提供申込に記載された条件に同意できなければ、データ蓄積者の職員は、その旨をサービスサーバ２０に入力する。サービスサーバ２０は、データ提供申込に応じない旨（データ提供契約を締結しない旨）を示す否定応答を取引サーバ４０に送信する。 If the data storage employee does not agree with the conditions stated in the data provision application, he/she will input that fact into the service server 20. The service server 20 transmits a negative response to the transaction server 40 indicating that the service server 20 does not accept the data provision application (not concluding a data provision contract).
　肯定応答を受信した場合（データ提供契約が成立の場合）、取引サーバ４０は、データ取引申込の契約が成立したことを記憶する。また、取引サーバ４０は、データ提供申込の契約が成立したことを流通制御サーバ１０及びデータ利活用サーバ３０に通知する。具体的には、取引サーバ４０は、提供申込ＩＤを含む「提供契約成立通知」を流通制御サーバ１０及びデータ利活用サーバ３０に送信する（ステップＳ２８）。 If an affirmative response is received (if the data provision contract is established), the transaction server 40 stores that the data transaction application contract has been established. Further, the transaction server 40 notifies the distribution control server 10 and the data utilization server 30 that the contract for the data provision application has been concluded. Specifically, the transaction server 40 transmits a "provision contract establishment notification" including the provision application ID to the distribution control server 10 and the data utilization server 30 (step S28).
　否定応答を受信した場合（データ提供契約が不成立の場合）、取引サーバ４０は、データ提供申込の契約が不成立であることをデータ利活用サーバ３０に通知する。 If a negative response is received (if the data provision contract is not established), the transaction server 40 notifies the data utilization server 30 that the contract for the data provision application is not established.
　データ提供申込の契約が不成立の場合、データ利活用事業者の職員等は、データ提供申込を取り下げるか、条件を引き上げて再びデータ提供を申し込むか検討する。 If a data provision application contract is not concluded, the staff of the data utilization business will consider whether to withdraw the data provision application or raise the conditions and reapply for data provision.
　データ提供申込を取り下げる場合には、データ利活用事業者の職員等は、その旨をデータ利活用サーバ３０に入力する。データ利活用サーバ３０は、提供申込ＩＤを含む「提供契約取消通知」を取引サーバ４０に送信する（図１４に図示せず）。取引サーバ４０は、受信した提供契約取消通知を流通制御サーバ１０に転送する。 If the data provision application is to be withdrawn, the staff of the data utilization business operator, etc., inputs this into the data utilization server 30. The data utilization server 30 transmits a "provision contract cancellation notification" including the provision application ID to the transaction server 40 (not shown in FIG. 14). The transaction server 40 transfers the received provision contract cancellation notice to the distribution control server 10.
　再びデータ提供申込を行う場合には、データ利活用事業者の職員等は、新たな条件を設定したデータ提供申込をデータ利活用サーバ３０に入力する。データ利活用サーバ３０は、新たなデータ提供申込を取引サーバ４０に送信する。 When applying for data provision again, the staff of the data utilization business enters the data provision application with new conditions into the data utilization server 30. The data utilization server 30 transmits a new data provision application to the transaction server 40.
　取引サーバ４０は、新たなデータ提供申込を含むデータ提供契約締結依頼をサービスサーバ２０に送信する。データ蓄積者は、提示された新たな条件を検討し、検討結果を、取引サーバ４０を介してデータ提供先に通知する。データ蓄積者とデータ提供先は、上記のような価格交渉を繰り返す。 The transaction server 40 transmits a data provision contract conclusion request including a new data provision application to the service server 20. The data accumulator examines the presented new conditions and notifies the data provider of the results of the examination via the transaction server 40. The data accumulator and the data provider repeat price negotiations as described above.
　提供契約成立通知を受信すると、流通制御サーバ１０は、データ提供に対する同意が得られた利用者に関し、データ蓄積者（病院Ａ）に提供指示を送信する（ステップＳ２９）。上述のように、５件の病名データの提供が求められた場合には、流通制御サーバ１０は、５件の病名データに関し、サービスサーバ２０－１に提供指示を送信する。例えば、流通制御サーバ１０は、５名の利用者に関する病名の提供指示をサービスサーバ２０－１に行う。 Upon receiving the provision contract establishment notification, the distribution control server 10 transmits a provision instruction to the data accumulator (hospital A) regarding the user who has consented to data provision (step S29). As described above, when the provision of five disease name data is requested, the distribution control server 10 transmits a provision instruction regarding the five disease name data to the service server 20-1. For example, the distribution control server 10 instructs the service server 20-1 to provide disease names for five users.
　提供指示を受信した病院Ａ（サービスサーバ２０－１）は、顧客情報データベースを参照し、同意した利用者のユーザデータを指定されたデータ提供先に送信する（ステップＳ３０）。 Hospital A (service server 20-1), which has received the provision instruction, refers to the customer information database and transmits the user data of the consenting user to the specified data provision destination (step S30).
　このように、流通制御サーバ１０は、データ提供に利用者が同意し、且つ、サービス事業者とデータ利活用事業者の間でデータ提供申込に関する契約が成立すると、サービスサーバ２０に対してユーザデータをデータ利活用サーバ３０に送信するように指示する。 In this way, the distribution control server 10 transmits the user data to the service server 20 when the user agrees to provide the data and a contract regarding the data provision application is established between the service provider and the data utilization provider. to the data utilization server 30.
　さらに、流通制御サーバ１０は、提供取引の履歴を取引台帳に登録する。流通制御サーバ１０は、提供取引の履歴に基づき、データ提供の対価の支払をデータ提供先に請求する。流通制御サーバ１０は、予め定められたタイミング（例えば、月初）でデータ提供に対する対価をデータ蓄積者及び利用者に支払う。流通制御サーバ１０は、データ蓄積者（データ提供元）と利用者に対し、当事者間で合意した条件（対価）に基づき支払を行う。 Additionally, the distribution control server 10 registers the history of supply transactions in the transaction ledger. The distribution control server 10 requests the data provider to pay for the data provision based on the history of the provision transaction. The distribution control server 10 pays the data accumulator and the user compensation for providing the data at a predetermined timing (for example, at the beginning of the month). The distribution control server 10 makes payments to the data accumulator (data provider) and the user based on conditions (compensation) agreed upon between the parties.
　このように、流通制御サーバ１０は、データ利活用事業者からデータ提供に対する提供対価を情報流通事業者が受け取るための制御を行う。具体的には、流通制御サーバ１０は、サービスサーバ２０に対してユーザデータをデータ利活用サーバ３０に送信するように指示したことに応じて、契約が成立したデータ提供申込とデータ提供の取引履歴を記憶する。流通制御サーバ１０は、契約が成立したデータ提供申込の提供データの要件と提供対価提示に基づき提供対価を算出する。 In this way, the distribution control server 10 performs control for the information distribution business to receive compensation for providing data from the data utilization business. Specifically, in response to an instruction to the service server 20 to send user data to the data utilization server 30, the distribution control server 10 transmits the data provision application for which the contract was established and the data provision transaction history. remember. The distribution control server 10 calculates the provision consideration based on the requirements for the provision data of the data provision application for which the contract has been established and the provision consideration presentation.
　続いて、第１の実施形態に係る情報流通システムに含まれる各装置の詳細について説明する。 Next, details of each device included in the information distribution system according to the first embodiment will be explained.
［流通制御サーバ］
　図１５は、第１の実施形態に係る流通制御サーバ１０の処理構成（処理モジュール）の一例を示す図である。図１５を参照すると、流通制御サーバ１０は、通信制御部２０１と、利用者登録部２０２と、ＩＤ連携部２０３と、対価定義公開部２０４と、蓄積同意制御部２０５と、を備える。さらに、流通制御サーバ１０は、所在情報管理部２０６と、データ流通制御部２０７と、カタログ情報管理部２０８と、決済制御部２０９と、記憶部２１０と、を備える。 [Distribution control server]
FIG. 15 is a diagram showing an example of a processing configuration (processing module) of the distribution control server 10 according to the first embodiment. Referring to FIG. 15, the distribution control server 10 includes a communication control section 201, a user registration section 202, an ID cooperation section 203, a consideration definition disclosure section 204, and an accumulation consent control section 205. Further, the distribution control server 10 includes a location information management section 206, a data distribution control section 207, a catalog information management section 208, a payment control section 209, and a storage section 210.
　通信制御部２０１は、他の装置との間の通信を制御する手段である。例えば、通信制御部２０１は、サービスサーバ２０からデータ（パケット）を受信する。また、通信制御部２０１は、サービスサーバ２０に向けてデータを送信する。通信制御部２０１は、他の装置から受信したデータを他の処理モジュールに引き渡す。通信制御部２０１は、他の処理モジュールから取得したデータを他の装置に向けて送信する。このように、他の処理モジュールは、通信制御部２０１を介して他の装置とデータの送受信を行う。通信制御部２０１は、他の装置からデータを受信する受信部としての機能と、他の装置に向けてデータを送信する送信部としての機能と、を備える。 The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the service server 20. Furthermore, the communication control unit 201 transmits data to the service server 20. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.
　利用者登録部２０２は、上述の利用者登録（利用者のシステム登録）を実現する手段である。利用者登録部２０２は、利用者の端末５０から個人情報（氏名、生年月日、連絡先、口座情報等）を取得する。 The user registration unit 202 is a means for realizing the above-mentioned user registration (user system registration). The user registration unit 202 acquires personal information (name, date of birth, contact information, account information, etc.) from the user's terminal 50.
　利用者登録部２０２は、当該個人情報を取得すると、利用者を識別するためのユーザＩＤを生成する。例えば、利用者登録部２０２は、利用者のシステム登録のたびに一意な値を採番し、当該採番された値をユーザＩＤとして用いる。 Upon acquiring the personal information, the user registration unit 202 generates a user ID for identifying the user. For example, the user registration unit 202 assigns a unique number each time a user registers with the system, and uses the assigned value as the user ID.
　利用者登録部２０２は、ユーザＩＤと個人情報を利用者情報データベースに記憶する（図１６参照）。なお、図１６に示すように、利用者情報データベースは、ユーザＩＤ、個人情報及びサービス事業者ごとの個人識別ＩＤを対応付けて記憶する。また、図１６に示す利用者情報データベースは例示であって、記憶する項目等を限定する趣旨ではない。例えば、利用者登録された日時等が利用者情報データベースに登録されていてもよい。 The user registration unit 202 stores the user ID and personal information in the user information database (see FIG. 16). Note that, as shown in FIG. 16, the user information database stores user IDs, personal information, and personal identification IDs for each service provider in association with each other. Further, the user information database shown in FIG. 16 is an example, and is not intended to limit the items to be stored. For example, the date and time of user registration may be registered in the user information database.
　利用者登録部２０２は、生成したユーザＩＤを端末５０に送信する。 The user registration unit 202 transmits the generated user ID to the terminal 50.
　ＩＤ連携部２０３は、上述のＩＤ連携を実現する手段である。ＩＤ連携部２０３は、サービス事業者の端末（例えば、病院端末６０）やサービスサーバ２０から「ＩＤ連携要求」を受信する。ＩＤ連携要求には、ＩＤ連携（サービス事業者の登録）を希望する利用者の個人特定情報、個人識別ＩＤ及び事業者コードが含まれる。 The ID cooperation unit 203 is a means for realizing the above-mentioned ID cooperation. The ID collaboration unit 203 receives an “ID collaboration request” from a service provider's terminal (for example, the hospital terminal 60) or the service server 20. The ID cooperation request includes personal identification information, personal identification ID, and company code of the user who desires ID cooperation (registration of service provider).
　ＩＤ連携部２０３は、個人特定情報（利用者の氏名、氏名と生年月日の組み合わせ等）をキーとして利用者情報データベースを検索し、対応する利用者を特定する。ＩＤ連携部２０３は、当該特定された利用者の個人識別ＩＤフィールドのうち事業者コードに対応するフィールドにＩＤ連携要求に含まれる個人識別ＩＤを設定する。即ち、ＩＤ連携部２０３は、個人特定情報からシステムアカウントに登録された利用者を特定し、当該特定した利用者のアカウントにおいてサービス事業者と個人識別ＩＤを対応付ける。 The ID collaboration unit 203 searches the user information database using personal identification information (user's name, combination of name and date of birth, etc.) as a key, and identifies the corresponding user. The ID cooperation unit 203 sets the personal identification ID included in the ID cooperation request in the field corresponding to the business code in the personal identification ID field of the identified user. That is, the ID cooperation unit 203 identifies the user registered in the system account from the personal identification information, and associates the service provider with the personal identification ID in the account of the identified user.
　対価定義公開部２０４は、蓄積対価定義及び提供対価定義を公開する手段である。対価定義公開部２０４は、情報流通事業者の職員等の操作に応じて、図６に示される蓄積対価定義や図１２に示される提供対価定義を取得する。 The consideration definition publishing unit 204 is a means for publishing the accumulated consideration definition and the provided consideration definition. The consideration definition publishing unit 204 acquires the accumulated consideration definition shown in FIG. 6 and the provided consideration definition shown in FIG. 12 in response to operations by employees of the information distribution business.
　対価定義公開部２０４は、取得した蓄積対価定義や提供対価定義を公開する。例えば、対価定義公開部２０４は、蓄積対価定義や提供対価定義をホームページに掲載する。 The consideration definition publishing unit 204 publishes the acquired accumulated consideration definition and provided consideration definition. For example, the consideration definition publishing unit 204 posts the accumulated consideration definition and the provided consideration definition on the homepage.
　蓄積同意制御部２０５は、データ蓄積の同意に関する制御を行う手段である。蓄積同意制御部２０５は、サービスサーバ２０から蓄積同意取得要求を受信する。蓄積同意制御部２０５は、利用者情報データベースを参照し、当該受信した蓄積同意取得要求に含まれる個人識別ＩＤ及び事業者コードに基づいて同意取得の対象となっている利用者を特定する。 The storage consent control unit 205 is a means for controlling consent for data storage. The storage consent control unit 205 receives a storage consent acquisition request from the service server 20. The storage consent control unit 205 refers to the user information database and identifies the user whose consent is to be obtained based on the personal identification ID and business code included in the received storage consent acquisition request.
　例えば、図１６に示す利用者情報データベースにおいて、個人識別ＩＤ「ＨＬ０１」及び病院Ａの事業者コードを取得した場合、蓄積同意制御部２０５は、図１６の１行目に示される利用者を特定する。蓄積同意制御部２０５は、当該特定した利用者の連絡先（端末５０で受信可能なメールアドレス等）にデータ蓄積の問合せを送信する。 For example, in the user information database shown in FIG. 16, when the personal identification ID "HL01" and the business code of hospital A are acquired, the storage consent control unit 205 specifies the user shown in the first line of FIG. do. The storage consent control unit 205 sends a data storage inquiry to the specified user's contact information (such as an e-mail address that can be received by the terminal 50).
　データ蓄積の問合せには、データ蓄積に対する同意取得を依頼したサービス事業者の情報（例えば、事業者名）、ユーザデータ情報（同意を得るデータのデータ種類、取得日時）等が含まれる。 The data storage inquiry includes information on the service provider who requested consent for data storage (for example, the name of the company), user data information (data type of data for which consent was obtained, date and time of acquisition), etc.
　蓄積同意制御部２０５は、利用者の端末５０からデータ蓄積の問合せに対する応答を受信する。蓄積同意制御部２０５は、取得した応答をサービスサーバ２０に送信（転送）する。 The storage consent control unit 205 receives a response to the data storage inquiry from the user's terminal 50. The storage consent control unit 205 transmits (transfers) the acquired response to the service server 20.
　所在情報管理部２０６は、サービス事業者から取得する所在情報を管理する手段である。所在情報管理部２０６は、所在情報を処理し、サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する。所在情報管理部２０６は、「蓄積制御部」として動作する。 The location information management unit 206 is a means for managing location information obtained from a service provider. The location information management unit 206 processes location information and stores user data generated when a service provider provides a service to a user in order to register it in an information distribution system as data that can be provided to a third party. control. The location information management unit 206 operates as an “accumulation control unit”.
　所在情報管理部２０６は、各サービスサーバ２０から取得した所在情報を所在情報データベースに記憶する（図１７参照）。図１７に示すように、所在情報データベースは、個人識別ＩＤ、事業者コード、データＩＤ、データ種類、データ蓄積日等を対応付けて記憶する。 The location information management unit 206 stores the location information acquired from each service server 20 in the location information database (see FIG. 17). As shown in FIG. 17, the location information database stores personal identification ID, business code, data ID, data type, data storage date, etc. in association with each other.
　なお、図１７に示す所在情報データベースは例示であって、記憶する項目等を限定する趣旨ではない。また、図１７を含む図面において、理解の容易のため、事業者コードをサービス事業者の名称を用いて表記している。 Note that the location information database shown in FIG. 17 is an example, and is not intended to limit the items to be stored. Further, in the drawings including FIG. 17, for ease of understanding, the provider code is expressed using the name of the service provider.
　所在情報管理部２０６は、所在情報データベースにデータ登録をするたびに、蓄積取引の履歴を取引台帳に記録する。具体的には、所在情報管理部２０６は、サービスサーバ２０から受信した所在情報を処理するたびに、蓄積取引管理データベースにエントリを追加する（図１８参照）。 The location information management unit 206 records the history of accumulated transactions in the transaction ledger every time data is registered in the location information database. Specifically, the location information management unit 206 adds an entry to the accumulated transaction management database every time it processes the location information received from the service server 20 (see FIG. 18).
　図１８に示すように、所在情報管理部２０６は、処理した所在情報に対応する利用者のユーザＩＤ、事業者コード、データＩＤ、蓄積されたデータのデータ種類、データ蓄積日、蓄積対価定義のＩＤを対応付けて記憶する。所在情報管理部２０６は、データ種類と蓄積対価ＩＤを対応付けて記憶するテーブル情報を参照し、蓄積対価ＩＤを得る。 As shown in FIG. 18, the location information management unit 206 stores the user ID, operator code, data ID, data type of accumulated data, data accumulation date, and accumulation consideration definition of the user corresponding to the processed location information. The IDs are associated and stored. The location information management unit 206 obtains the accumulated consideration ID by referring to table information that stores data types and accumulated consideration IDs in association with each other.
　データ流通制御部２０７は、「共有」又は「提供」によるデータ流通を制御する手段である。 The data distribution control unit 207 is a means for controlling data distribution by "sharing" or "providing".
　はじめに、「共有」に関するデータ流通について説明する。 First, we will explain data distribution related to "sharing".
　データ流通制御部２０７は、サービスサーバ２０から共有要請を受信する。共有要請には、データ取得の対象となる利用者の個人識別ＩＤ、共有要請の送信元の事業者コード、取得を希望するデータ種類が含まれる。図９の例では、ＥＣ事業者Ｂ（サービスサーバ２０－２）が利用者に対して生成した個人識別ＩＤ、ＥＣ事業者Ｂの事業者コード、データ種類として「病名」が共有要請に含まれる。 The data distribution control unit 207 receives a sharing request from the service server 20. The sharing request includes the personal identification ID of the user whose data is to be obtained, the provider code of the source of the sharing request, and the type of data desired to be obtained. In the example of FIG. 9, the sharing request includes the personal identification ID generated for the user by EC company B (service server 20-2), the company code of EC company B, and "disease name" as the data type. .
　データ流通制御部２０７は、共有要請に含まれる個人識別ＩＤ、事業者コードに基づいてデータ流通の対象者を特定する。具体的には、データ流通制御部２０７は、図１６に示す利用者情報データベースを参照し、当該対象者を特定する。上記の例では、ＥＣ事業者Ｂから「ＥＣ０１」の個人識別ＩＤを含む共有要請を受信すると、データ流通制御部２０７は、図１６に示す１行目のエントリから利用者Ｕ１がデータ流通の対象者であることを把握する。 The data distribution control unit 207 identifies the data distribution target based on the personal identification ID and business code included in the sharing request. Specifically, the data distribution control unit 207 refers to the user information database shown in FIG. 16 and identifies the target person. In the above example, upon receiving a sharing request including the personal identification ID "EC01" from EC business operator B, the data distribution control unit 207 determines that user U1 is the target of data distribution from the entry in the first line shown in FIG. Understand that you are a person.
　その後、データ流通制御部２０７は、特定された利用者の個人識別ＩＤと共有要請に含まれるデータ種類を用いて必要なデータを蓄積しているサービス事業者を特定する。具体的には、データ流通制御部２０７は、図１７に示す所在情報データベースを参照し、共有要請に含まれるデータ種類に対応するデータを蓄積するサービス事業者を特定する。上記の例では、利用者Ｕ１の個人識別ＩＤ「ＨＬ０１」と共有要請に含まれるデータ種類「病名」に基づき、病院Ａが特定される。 Thereafter, the data distribution control unit 207 uses the identified user's personal identification ID and the data type included in the sharing request to identify the service provider that has accumulated the necessary data. Specifically, the data distribution control unit 207 refers to the location information database shown in FIG. 17 and identifies a service provider that accumulates data corresponding to the data type included in the sharing request. In the above example, the hospital A is specified based on the personal identification ID "HL01" of the user U1 and the data type "disease name" included in the sharing request.
　なお、利用者の個人識別ＩＤと共有要請に含まれるデータ種類の組み合わせが所在情報データベースに記憶されていない場合には、データ流通制御部２０７は、共有要請の送信元に対してデータ共有不可を示す否定応答を送信する。上記の例では、利用者Ｕ１の個人識別ＩＤ「ＨＬ０１」とデータ種類「病名」の組み合わせが所在情報データベースに登録されていなければ、否定応答がＥＣ事業者Ｂ（サービスサーバ２０－２）に送信される。 Note that if the combination of the user's personal identification ID and the data type included in the sharing request is not stored in the location information database, the data distribution control unit 207 instructs the sender of the sharing request that data sharing is not possible. send a negative response indicating In the above example, if the combination of user U1's personal identification ID "HL01" and data type "disease name" is not registered in the location information database, a negative response will be sent to EC business operator B (service server 20-2). be done.
　データ流通の対象者と流通させるデータの蓄積者が特定されると、データ流通制御部２０７は、データ流通対象者に対してデータ共有の問い合わせを行う。具体的には、データ流通制御部２０７は、データ流通対象者の連絡先に、データ共有に関する問合せを送信する。上記の例では、利用者Ｕ１が所持する端末５０に上記問合せが送信される。 Once the data distribution target and the data storage person to be distributed are specified, the data distribution control unit 207 makes an inquiry to the data distribution target regarding data sharing. Specifically, the data distribution control unit 207 sends an inquiry regarding data sharing to the contact information of the data distribution target person. In the above example, the inquiry is sent to the terminal 50 owned by the user U1.
　なお、データ共有の問合せには、データ共有の要請元、データ蓄積者、データ共有されるデータ種類等の情報が含まれる。上記の例では、データ共有の要請元としてＥＣ事業者Ｂ、データ蓄積者として病院Ａ、データ共有されるデータ種類として「病名」がそれぞれ設定される。 Note that the data sharing inquiry includes information such as the source of the data sharing request, the data storage person, and the type of data to be shared. In the above example, EC business operator B is set as the data sharing request source, hospital A is set as the data storage person, and "disease name" is set as the data type to be shared.
　データ流通制御部２０７は、データ共有の問合せに対する応答を端末５０から受信する。 The data distribution control unit 207 receives a response to the data sharing inquiry from the terminal 50.
　利用者がデータ共有を拒否している場合には、データ流通制御部２０７は、データ共有不可をデータ共有要請元に通知する。上記の例では、データ流通制御部２０７は、ＥＣ事業者Ｂのサービスサーバ２０－２に対して共有要請に対する否定応答を送信する。 If the user refuses data sharing, the data distribution control unit 207 notifies the data sharing requester that data sharing is not possible. In the above example, the data distribution control unit 207 transmits a negative response to the sharing request to the service server 20-2 of the EC company B.
　利用者がデータ共有に同意した場合には、データ流通制御部２０７は、データ蓄積者に対して共有指示を送信する。上記の例では、データ蓄積者である病院Ａのサービスサーバ２０－１に共有指示が送信される。 If the user agrees to data sharing, the data distribution control unit 207 sends a sharing instruction to the data accumulator. In the above example, the sharing instruction is sent to the service server 20-1 of hospital A, which is the data accumulator.
　共有指示には、データ蓄積者が生成した個人識別ＩＤと、データ共有先に関する情報と、データ共有する対象のデータ種類と、が含まれる。上記の例では、利用者Ｕ１の個人識別ＩＤ「ＨＬ０１」と、ＥＣ事業者Ｂのサービスサーバ２０－２のアドレスと、データ種類「病名」を含む共有指示が病院Ａのサービスサーバ２０－１に送信される。 The sharing instruction includes the personal identification ID generated by the data accumulator, information regarding the data sharing destination, and the data type of the data sharing target. In the above example, a sharing instruction containing user U1's personal identification ID "HL01", the address of e-commerce company B's service server 20-2, and the data type "disease name" is sent to hospital A's service server 20-1. Sent.
　このように、データ流通制御部２０７は、データ共有に同意した利用者（対象者）の個人識別ＩＤであってデータ蓄積者が生成した個人識別ＩＤを含む共有指示を送信する。 In this way, the data distribution control unit 207 transmits a sharing instruction that includes the personal identification ID of the user (target person) who has consented to data sharing and is generated by the data accumulator.
　続いて、「提供」に関するデータ流通について説明する。 Next, we will explain data distribution related to "provision".
　データ流通制御部２０７は、取引サーバ４０から「提供要請」を受信する。提供要請には、提供申込ＩＤ、データ提供申込及び口座開設者リストが含まれる。 The data distribution control unit 207 receives a “provision request” from the transaction server 40. The provision request includes a provision application ID, a data provision application, and a list of account openers.
　データ流通制御部２０７は、所在情報データベースを参照し、データ提供申込に記載されたデータ種類に対応するユーザデータを蓄積するデータ蓄積者（データ提供元）を特定する。図１７の例では、データ流通制御部２０７は、データ種類「病名」から「病院Ａ」を特定する。 The data distribution control unit 207 refers to the location information database and identifies a data accumulator (data provider) that accumulates user data corresponding to the data type described in the data provision application. In the example of FIG. 17, the data distribution control unit 207 specifies "hospital A" from the data type "disease name".
　データ流通制御部２０７は、特定したデータ蓄積者に関する情報を取引サーバ４０に通知する。データ流通制御部２０７は、特定したデータ蓄積者の名称（上記の例では病院Ａ）、連絡先（病院Ａのサービスサーバ２０のアドレス）等を含む「提供元通知」を取引サーバ４０に送信する。 The data distribution control unit 207 notifies the transaction server 40 of information regarding the identified data accumulator. The data distribution control unit 207 transmits a “provider notification” including the name of the identified data accumulator (hospital A in the above example), contact information (address of the service server 20 of hospital A), etc. to the transaction server 40. .
　なお、データ流通制御部２０７は、情報流通事業者の職員等が流通制御サーバ１０に予め入力したデータ蓄積者の事業者コード、データ蓄積者の名称、連絡先等を対応付けて記憶するテーブル情報を参照し、上記データ蓄積者に関する情報を取得する。 Note that the data distribution control unit 207 stores table information that associates and stores the data accumulator's operator code, the data accumulator's name, contact information, etc. that have been input in advance to the distribution control server 10 by the staff of the information distribution business. , and obtain information regarding the data accumulator.
　また、データ流通制御部２０７は、口座開設者リストに記載された利用者であって、上記データ提供申込に基づいて特定されたデータ蓄積者にデータ提供の対象となっているデータ種類のユーザデータが蓄積されている利用者の個人識別ＩＤを特定する。 The data distribution control unit 207 also stores user data of the type of data that is a user listed in the account opener list and that is the target of data provision to the data accumulator specified based on the data provision application. Identify the user's personal identification ID that has been stored.
　図１６の例では、口座開設者リストに氏名「Ｕ１」の利用者のユーザＩＤが含まれていれば、データ流通制御部２０７は、利用者情報データベースを参照し、当該利用者の病院Ａに関する個人識別ＩＤ「ＨＬ０１」を取得する。データ流通制御部２０７は、図１７に示す所在情報データベースを参照し、病院Ａは個人識別ＩＤ「ＨＬ０１」の利用者に関してデータ提供が要請されたデータ種類「病名」を蓄積していることを確認する。データ流通制御部２０７は、データ流通対象者の個人識別ＩＤとして個人識別ＩＤ「ＨＬ０１」を特定する。 In the example of FIG. 16, if the account opener list includes the user ID of the user with the name "U1", the data distribution control unit 207 refers to the user information database and Obtain the personal identification ID "HL01". The data distribution control unit 207 refers to the location information database shown in FIG. 17 and confirms that Hospital A has accumulated the data type "disease name" for which data provision was requested regarding the user with the personal identification ID "HL01". do. The data distribution control unit 207 specifies the personal identification ID "HL01" as the personal identification ID of the data distribution target.
　データ流通対象者が特定されると、データ流通制御部２０７は、データ流通対象者に対してデータ提供の問い合わせを行う。具体的には、データ流通制御部２０７は、データ流通対象者の連絡先に対して、データ提供に関する問合せを送信する。上記の例では、利用者Ｕ１が所持する端末５０にデータ提供の問合せが送信される。 Once the data distribution target person is specified, the data distribution control unit 207 makes an inquiry to the data distribution target person about providing data. Specifically, the data distribution control unit 207 sends an inquiry regarding data provision to the contact information of the data distribution target person. In the above example, a data provision inquiry is sent to the terminal 50 owned by the user U1.
　データ提供の問合せには、データ提供の要請元に関する情報、データ蓄積者に関する情報、提供が要望されたデータ種類が含まれる。上記の例では、データ提供の要請元として製薬会社Ｃ、データ蓄積者として病院Ａ、提供が要望されたデータ種類として「病名」を含む問合せが端末５０に送信される。 The data provision inquiry includes information regarding the source of the data provision request, information regarding the data storage person, and the type of data requested to be provided. In the above example, an inquiry is sent to the terminal 50 that includes pharmaceutical company C as the source of the request for data provision, hospital A as the data storage person, and "name of disease" as the type of data requested to be provided.
　データ流通制御部２０７は、端末５０からデータ提供の問合せに対する応答を受信する。 The data distribution control unit 207 receives a response to the data provision inquiry from the terminal 50.
　データ流通制御部２０７は、取引サーバ４０から「提供契約成立通知」又は「提供契約取消通知」を受信する。 The data distribution control unit 207 receives a "notification of establishment of a provision contract" or a "notification of cancellation of a provision contract" from the transaction server 40.
　提供契約取消通知を受信した場合、データ流通制御部２０７は、特段の処理を行わない。あるいは、データ流通制御部２０７は、データ提供の問合せに同意した利用者に対してデータ提供契約が成立しなかった旨を通知してもよい。 When receiving the provision contract cancellation notification, the data distribution control unit 207 does not perform any special processing. Alternatively, the data distribution control unit 207 may notify the user who has agreed to the data provision inquiry that the data provision contract has not been established.
　提供契約成立通知を受信した場合、データ流通制御部２０７は、データ提供に同意した利用者に関し、データ蓄積者に対して提供指示を送信する。提供指示には、データ提供に同意した利用者の個人識別ＩＤと、データ提供先に関する情報（例えば、事業者名、事業者コード、データ利活用サーバ３０のアドレス）と、提供するデータのデータ種類と、が含まれる。 When receiving the provision contract establishment notification, the data distribution control unit 207 transmits a provision instruction to the data accumulator regarding the user who has agreed to provide the data. The provision instructions include the personal identification ID of the user who has agreed to provide the data, information regarding the data provider (e.g., business name, business code, address of the data utilization server 30), and the data type of the data to be provided. and are included.
　例えば、上述のように、５件の病名データの提供が求められた場合には、データ流通制御部２０７は、データ提供に同意した５人の利用者の病名データに関し、サービスサーバ２０に提供指示を送信する。 For example, as described above, when the provision of disease name data for five cases is requested, the data distribution control unit 207 instructs the service server 20 to provide the disease name data of the five users who have agreed to provide the data. Send.
　データ流通制御部２０７は、提供指示を送信するたびに、提供取引の履歴を取引台帳に記録する。具体的には、データ流通制御部２０７は、提供指示を送信するたびに、提供取引管理データベースにエントリを追加する（図１９参照）。 Each time the data distribution control unit 207 transmits a provision instruction, it records the history of the provision transaction in the transaction ledger. Specifically, the data distribution control unit 207 adds an entry to the provision transaction management database every time a provision instruction is transmitted (see FIG. 19).
　図１９に示すように、データ流通制御部２０７は、利用者のユーザＩＤ、データ蓄積者の事業者コード、データＩＤ、データ種類、データ提供日、提供契約成立通知に含まれる提供申込ＩＤを対応付けて記憶する。 As shown in FIG. 19, the data distribution control unit 207 corresponds to the user ID of the user, the operator code of the data storage company, the data ID, the data type, the data provision date, and the provision application ID included in the provision contract establishment notification. Attach and memorize.
　カタログ情報管理部２０８は、カタログ情報を管理する手段である。カタログ情報管理部２０８は、システム管理者が作成したカタログ情報を記憶部２１０に記憶する。 The catalog information management unit 208 is a means for managing catalog information. Catalog information management section 208 stores catalog information created by a system administrator in storage section 210.
　カタログ情報管理部２０８は、取引サーバ４０から「カタログ情報送信要求」を受信する。当該要求の受信に応じて、カタログ情報管理部２０８は、記憶部２１０に記憶されたカタログ情報を取引サーバ４０に送信する。 The catalog information management unit 208 receives a “catalog information transmission request” from the transaction server 40. In response to receiving the request, the catalog information management unit 208 transmits the catalog information stored in the storage unit 210 to the transaction server 40.
　決済制御部２０９は、情報流通システムで発生した取引（データ蓄積、データ提供）の決済に関する制御を行う手段である。例えば、決済制御部２０９は、予め定められたタイミング（例えば、月初）に、対価支払期間（例えば、１ヶ月）に生じたデータ取引に関する支払を制御する。 The payment control unit 209 is a means for controlling payments for transactions (data accumulation, data provision) that occur in the information distribution system. For example, the payment control unit 209 controls payments related to data transactions that occur during a consideration payment period (for example, one month) at a predetermined timing (for example, at the beginning of a month).
　決済制御部２０９は、データ蓄積が行われると、サービス事業者及び利用者にデータ蓄積に対する蓄積対価を支払うための制御を行う。また、決済制御部２０９は、データ提供が行われると、データ利活用事業者からデータ提供に対する提供対価を情報流通事業者が受け取るための制御を行う。 When data is accumulated, the payment control unit 209 performs control to pay the service provider and the user an accumulation fee for the data accumulation. Furthermore, when data is provided, the payment control unit 209 performs control so that the information distribution business receives compensation for the data provision from the data utilization business.
＜データ蓄積に対する対価の支払い＞
　決済制御部２０９は、予め定めがタイミング（例えば、月初）に蓄積取引管理データベースを参照し、対価支払対象期間（例えば、１ヶ月間）に属する各エントリについて蓄積対価（データ蓄積者に支払う蓄積対価、利用者に支払う蓄積対価）を算出する。 <Payment for data accumulation>
The settlement control unit 209 refers to the accumulated transaction management database at a predetermined timing (for example, at the beginning of the month) and calculates the accumulated consideration (accumulated consideration paid to the data accumulator) for each entry belonging to the consideration payment period (for example, one month). , the accumulation consideration paid to the user).
　図１８に示す１行目の例では、決済制御部２０９は、病院Ａが個人識別ＩＤ「ＨＬ０１」に対応する利用者の「病名」をデータ蓄積したことに対する蓄積対価を計算する。その際、決済制御部２０９は、各エントリの蓄積対価ＩＤに基づいて対応する蓄積対価定義を取得する。 In the example of the first line shown in FIG. 18, the payment control unit 209 calculates the accumulation consideration for hospital A accumulating data of the user's "disease name" corresponding to the personal identification ID "HL01". At this time, the payment control unit 209 obtains the corresponding accumulated consideration definition based on the accumulated consideration ID of each entry.
　例えば、図６に示す蓄積対価定義に基づいて支払対価が計算されると、病院Ａには「８円」、利用者には「２円」の蓄積対価が支払われる。 For example, when the payment consideration is calculated based on the accumulated consideration definition shown in FIG. 6, the accumulated consideration is paid to hospital A of "8 yen" and to the user of "2 yen."
　決済制御部２０９は、データ蓄積者ごとに、対価支払対象期間（例えば、１ヶ月）の各エントリについて計算した蓄積対価を合算することで、各データ蓄積者に支払う蓄積対価を計算する。同様に、決済制御部２０９は、利用者ごとに、対価支払対象期間の各エントリについて計算した蓄積対価を合算することで、各利用者に支払う蓄積対価を計算する。 The payment control unit 209 calculates the accumulation consideration to be paid to each data accumulation person by adding up the accumulation consideration calculated for each entry in the consideration payment period (for example, one month) for each data accumulation person. Similarly, the payment control unit 209 calculates the accumulated consideration to be paid to each user by adding up the accumulated consideration calculated for each entry in the consideration payment period for each user.
＜データ提供に対する対価の支払い＞
　データ提供元（データ利活用事業者）は、予め定めたタイミング（例えば、月末）に、対価支払対象期間（例えば、１ヶ月）に成立したデータ提供取引の対価を情報流通事業者に支払う。例えば、図１３に示すデータ提供申込によるデータ提供契約が成立すると、製薬会社は「１００円」の対価を情報流通事業者に支払う。 <Payment of consideration for data provision>
The data provider (data utilization business) pays the information distribution business at a predetermined timing (for example, at the end of the month) for the data provision transaction concluded during the compensation payment period (for example, one month). For example, when a data provision contract is established based on the data provision application shown in FIG. 13, the pharmaceutical company pays a consideration of "100 yen" to the information distribution business.
　決済制御部２０９は、予め定めがタイミング（例えば、月初）に提供取引管理データベースを参照し、対価支払対象期間（例えば、１ヶ月間）に属する各エントリについて提供の対価（データ提供元に支払う提供対価、利用者に支払う提供対価）を計算する。 The payment control unit 209 refers to the provision transaction management database at a predetermined timing (for example, at the beginning of the month), and calculates the provision consideration (paid to the data provider) for each entry belonging to the consideration payment period (for example, one month). Calculate the consideration (provided consideration paid to the user).
　図１９に示す１行目の例では、決済制御部２０９は、病院Ａが個人識別ＩＤ「ＨＬ０１」に対応する利用者の「病名」をデータ提供したことに対する対価を計算する。その際、決済制御部２０９は、各エントリの提供申込ＩＤに基づいて対応するデータ提供申込（当事者間で合意したデータ提供申込）を特定する。 In the example of the first line shown in FIG. 19, the payment control unit 209 calculates the compensation for the hospital A providing the data of the user's "disease name" corresponding to the personal identification ID "HL01". At this time, the payment control unit 209 identifies the corresponding data provision application (data provision application agreed upon between the parties) based on the provision application ID of each entry.
　決済制御部２０９は、特定されたデータ提供申込（当事者間で合意したデータ提供の条件）の提供データの要件及び提供対価提示に基づいてデータ提供元及び利用者に支払う提供対価を算出する。決済制御部２０９は、提供データの要件（データ量）、提供対価提示（提供データの単価、分配率）に基づいてデータ提供元と利用者に支払う対価を計算する。 The payment control unit 209 calculates the provision consideration to be paid to the data provider and the user based on the provision data requirements and provision consideration presentation of the specified data provision application (data provision conditions agreed upon between the parties). The payment control unit 209 calculates the consideration to be paid to the data provider and the user based on the requirements of the provided data (data amount) and the presentation of the provided consideration (unit price of the provided data, distribution rate).
　例えば、図１３に示すデータ提供申込に基づいて支払対価が計算されると、１つの提供データあたり、病院Ａには「１４円」、利用者には「４円」の対価が支払われる。なお、情報流通事業者への分配率は「１０％」なので、１つの提供データあたり、情報流通事業者は当該データ提供により「２円」の収益を得る。図１３のデータ提供申込に記載されたデータ要件は５個のデータ量を規定しているので、病院Ａは「７０（＝１４×５）円」の収益を得る。また、情報流通事業者は、「１０（＝２×５）円」の収益を得る。 For example, when the consideration to be paid is calculated based on the data provision application shown in FIG. 13, hospital A is paid "14 yen" and the user is paid "4 yen" for each provided data. Note that the distribution rate to the information distribution business is "10%," so for each piece of provided data, the information distribution business earns a profit of "2 yen" from providing that data. Since the data requirements stated in the data provision application in FIG. 13 specify the amount of data for five items, Hospital A obtains a profit of "70 (=14×5) yen." In addition, the information distribution business obtains a profit of "10 (=2×5) yen".
　決済制御部２０９は、データ提供元（データ蓄積者）ごとに、対価支払対象期間（例えば、１ヶ月）の各エントリについて計算した提供対価を合算することで、各データ蓄積者に支払う提供対価を計算する。同様に、決済制御部２０９は、利用者ごとに、対価支払対象期間の各エントリについて計算した提供対価を合算することで、各利用者に支払う提供対価を計算する。 The payment control unit 209 calculates the provided consideration to be paid to each data accumulator by adding up the provided consideration calculated for each entry in the consideration payment period (for example, one month) for each data provider (data accumulator). calculate. Similarly, the payment control unit 209 calculates the provided consideration to be paid to each user by adding up the provided consideration calculated for each entry in the consideration payment period for each user.
　決済制御部２０９は、計算した対価（データ蓄積の対価、データ提供の対価）を各データ蓄積者、利用者に支払う。 The payment control unit 209 pays the calculated compensation (compensation for data storage, compensation for data provision) to each data storage person and user.
　決済制御部２０９は、蓄積取引管理データベースや提供取引管理データベースに記載されたユーザＩＤをキーとして利用者情報データベースを検索し、利用者の口座情報を取得する。決済制御部２０９は、取得した口座情報（銀行口座情報、クレジットカード情報等）を用いて利用者に対価を支払う。 The payment control unit 209 searches the user information database using the user ID described in the accumulated transaction management database and the provided transaction management database as a key, and obtains the user's account information. The payment control unit 209 uses the acquired account information (bank account information, credit card information, etc.) to pay the user.
　決済制御部２０９は、事業者コードと対価の支払先を対応付けて記憶するテーブル情報を参照することで得られる口座情報を用いてデータ蓄積者に対価を支払う。 The payment control unit 209 pays the consideration to the data accumulator using the account information obtained by referring to the table information that stores the business code and the payee of the consideration in association with each other.
　記憶部２１０は、流通制御サーバ１０の動作に必要な情報を記憶する。記憶部２１０には、利用者情報データベース等が構築される。 The storage unit 210 stores information necessary for the operation of the distribution control server 10. A user information database and the like are constructed in the storage unit 210.
［サービスサーバ］
　図２０は、第１の実施形態に係るサービスサーバ２０の処理構成（処理モジュール）の一例を示す図である。図２０を参照すると、サービスサーバ２０は、通信制御部３０１と、ＩＤ連携制御部３０２と、データ流通要請部３０３と、データ蓄積制御部３０４と、データ流通部３０５と、契約締結制御部３０６と、記憶部３０７と、を備える。 [Service server]
FIG. 20 is a diagram showing an example of a processing configuration (processing module) of the service server 20 according to the first embodiment. Referring to FIG. 20, the service server 20 includes a communication control section 301, an ID cooperation control section 302, a data distribution request section 303, a data accumulation control section 304, a data distribution section 305, and a contract conclusion control section 306. , and a storage unit 307.
　通信制御部３０１は、他の装置との間の通信を制御する手段である。例えば、通信制御部３０１は、流通制御サーバ１０からデータ（パケット）を受信する。また、通信制御部３０１は、流通制御サーバ１０に向けてデータを送信する。通信制御部３０１は、他の装置から受信したデータを他の処理モジュールに引き渡す。通信制御部３０１は、他の処理モジュールから取得したデータを他の装置に向けて送信する。このように、他の処理モジュールは、通信制御部３０１を介して他の装置とデータの送受信を行う。通信制御部３０１は、他の装置からデータを受信する受信部としての機能と、他の装置に向けてデータを送信する送信部としての機能と、を備える。 The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 301 transmits data to the distribution control server 10. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.
　ＩＤ連携制御部３０２は、利用者のＩＤ連携に関する制御を行う手段である。ＩＤ連携制御部３０２は、ＧＵＩ（Graphical User Interface）等を用いてアカウントにログインしている利用者からＩＤ連携の要望を取得する。ＩＤ連携制御部３０２は、利用者からの要望に応じて、個人特定情報（ログインしている利用者の氏名等）、個人識別ＩＤ（当該利用者の会員番号等）及び事業者コードを含む「ＩＤ連携要求」を流通制御サーバ１０に送信する。 The ID cooperation control unit 302 is a means for controlling user ID cooperation. The ID cooperation control unit 302 obtains a request for ID cooperation from a user who is logged into an account using a GUI (Graphical User Interface) or the like. In response to a request from a user, the ID linkage control unit 302 provides information such as " "ID cooperation request" is sent to the distribution control server 10.
　なお、利用者の個人識別ＩＤ、個人特定情報及びユーザデータ等は、顧客情報データベースを用いて管理される（図２１参照）。図２１に示すように、顧客情報データベースは、利用者のＩＤ連携が完了しているか否かの情報（フラグ）を保持する。ＩＤ連携制御部３０２は、ＩＤ連携を完了すると、対応する利用者のＩＤ連携状態フィールドにフラグをセットする（図２１では、丸印が設定されている）。 Note that the user's personal identification ID, personal identification information, user data, etc. are managed using a customer information database (see FIG. 21). As shown in FIG. 21, the customer information database holds information (flag) indicating whether or not user ID linkage has been completed. When the ID linkage is completed, the ID linkage control unit 302 sets a flag in the ID linkage status field of the corresponding user (in FIG. 21, a circle is set).
　データ流通要請部３０３は、利用者のデータに関するデータ流通（データ共有）を情報流通事業者に要請する手段である。データ流通要請部３０３は、サービス事業者の職員等の操作に応じて、共有要請を流通制御サーバ１０に送信する。具体的には、データ流通要請部３０３は、データ取得の対象となる利用者の個人識別ＩＤ、自装置の事業者コード、取得を希望するデータ種類を含む共有要請を流通制御サーバ１０に送信する。 The data distribution request unit 303 is a means for requesting data distribution (data sharing) regarding user data to an information distribution business. The data distribution request unit 303 transmits a sharing request to the distribution control server 10 in response to an operation by a staff member of the service provider. Specifically, the data distribution request unit 303 sends a sharing request to the distribution control server 10, including the personal identification ID of the user whose data is to be acquired, the operator code of the own device, and the type of data desired to be acquired. .
　データ蓄積制御部３０４は、利用者に対してサービスを提供した結果生じるユーザデータの蓄積に関する制御を行う手段である。データ蓄積制御部３０４は、利用者の個人識別ＩＤと、当該利用者のユーザデータ（利用者にサービスを提供した結果生じたデータ、又は、利用者に提供するサービスに必要なデータ）を対応付けて顧客情報データベースに記憶する。 The data accumulation control unit 304 is a means for controlling the accumulation of user data resulting from providing services to users. The data accumulation control unit 304 associates the user's personal identification ID with the user's user data (data generated as a result of providing a service to the user, or data necessary for the service provided to the user). and stored in the customer information database.
　図２１に示すように、データ蓄積制御部３０４は、発生したデータの種類に応じたフィールドにユーザデータを記憶する（具体的なデータの内容を記憶する）。その際、データ蓄積制御部３０４は、ユーザデータを識別するためのデータＩＤを生成し、ユーザデータ及びデータ蓄積日と対応付けて記憶する。なお、図２１は、病院Ａのサービスサーバ２０－１に構築された顧客情報データベースの一例を示す。 As shown in FIG. 21, the data accumulation control unit 304 stores user data in a field corresponding to the type of generated data (stores the specific content of the data). At this time, the data accumulation control unit 304 generates a data ID for identifying the user data, and stores it in association with the user data and the data accumulation date. Note that FIG. 21 shows an example of a customer information database built in the service server 20-1 of hospital A.
　ここで、ＩＤ連携が完了している利用者に関し、データ蓄積制御部３０４は、ユーザデータを顧客情報データベースに記憶するたびに、当該ユーザデータの蓄積に関する同意取得を情報流通事業者に要求する。 Here, for users for whom ID linkage has been completed, the data storage control unit 304 requests the information distribution business operator to obtain consent for storage of the user data each time the user data is stored in the customer information database.
　具体的には、データ蓄積制御部３０４は、利用者の個人識別ＩＤ、事業者コード及びユーザデータ情報を含む蓄積同意取得要求を流通制御サーバ１０に送信する。 Specifically, the data accumulation control unit 304 transmits an accumulation consent acquisition request including the user's personal identification ID, business code, and user data information to the distribution control server 10.
　データ蓄積制御部３０４は、流通制御サーバ１０から蓄積同意取得要求に対する応答を受信する。 The data storage control unit 304 receives a response to the storage consent acquisition request from the distribution control server 10.
　利用者がユーザデータの蓄積を拒否した場合には、データ蓄積制御部３０４は、特段の対応を行わない。 If the user refuses to store user data, the data storage control unit 304 takes no particular action.
　利用者がユーザデータの蓄積に同意した場合には、データ蓄積制御部３０４は、所在情報を流通制御サーバ１０に送信する。例えば、個人識別ＩＤ「ＨＬ０１」の利用者にサービスが提供され、診察結果として病名のデータが発生した場合を考える。この場合、個人識別ＩＤ「ＨＬ０１」、事業者コード「病院Ａ」、データＩＤ「ＨＬＤ０１」、データ種類「病名」を含む所在情報が流通制御サーバ１０に送信される。 If the user agrees to accumulate user data, the data accumulation control unit 304 transmits location information to the distribution control server 10. For example, consider a case where a service is provided to a user with personal identification ID "HL01" and disease name data is generated as a medical examination result. In this case, location information including the personal identification ID "HL01", the business code "Hospital A", the data ID "HLD01", and the data type "Disease name" is transmitted to the distribution control server 10.
　データ流通部３０５は、「共有」又は「提供」によるデータ流通を実現する手段である。データ流通部３０５は、流通制御サーバ１０から受信した「共有指示」又は「提供指示」を処理する。 The data distribution unit 305 is a means for realizing data distribution by "sharing" or "providing". The data distribution unit 305 processes the “sharing instruction” or “provision instruction” received from the distribution control server 10.
　共有指示を受信した場合には、データ流通部３０５は、顧客情報データベースを参照し、共有指示に含まれる個人識別ＩＤ、データ種類に対応するエントリを特定する。例えば、個人識別ＩＤ「ＨＬ０１」、データ種類「病名」を含む共有指示を受信した場合には、データ流通部３０５は、図２１の最上段に示されるエントリを特定する。 When receiving a sharing instruction, the data distribution unit 305 refers to the customer information database and identifies an entry corresponding to the personal identification ID and data type included in the sharing instruction. For example, when receiving a sharing instruction including the personal identification ID "HL01" and the data type "disease name", the data distribution unit 305 specifies the entry shown in the top row of FIG. 21.
　データ流通部３０５は、特定されたエントリの対応するデータ種類フィールドに記載されたユーザデータを共有指示で指定されたデータ共有先に送信する。図９及び図２１の例では、「胃がん」がＥＣ事業者Ｂのサービスサーバ２０－２に送信される。 The data distribution unit 305 transmits the user data written in the corresponding data type field of the specified entry to the data sharing destination specified by the sharing instruction. In the examples of FIGS. 9 and 21, "stomach cancer" is transmitted to the service server 20-2 of EC company B.
　データ流通部３０５は、提供指示に関しても共有指示と同様に処理をする。データ流通部３０５は、提供指示に含まれる個人識別ＩＤとデータ種類により定まるユーザデータを、提供指示により指定されたデータ提供先に送信する。 The data distribution unit 305 processes the provision instruction in the same way as the sharing instruction. The data distribution unit 305 transmits user data determined by the personal identification ID and data type included in the provision instruction to the data provision destination specified by the provision instruction.
　なお、データ流通部３０５は、共有指示に基づいて共有データを送信する際、利用者の個人特定情報（氏名等）を相手先のサービスサーバ２０に送信してもよい。また、データ流通部３０５は、提供データを受信した事業者が、取得データの対応付けを可能とするように提供するデータにＩＤを付与してもよい。例えば、データ流通部３０５は、利用者の個人特定情報のハッシュ値を計算し、当該ハッシュ値を利用者のＩＤとしてデータ流通先に送信してもよい。 Note that when transmitting shared data based on a sharing instruction, the data distribution unit 305 may transmit the user's personal identification information (name, etc.) to the service server 20 of the other party. Furthermore, the data distribution unit 305 may assign an ID to the provided data so that a business operator receiving the provided data can associate the obtained data with each other. For example, the data distribution unit 305 may calculate a hash value of the user's personal identification information and transmit the hash value to the data distribution destination as the user's ID.
　契約締結制御部３０６は、データ提供の契約に関する制御を行う手段である。契約締結制御部３０６は、取引サーバ４０から受信した提供契約締結依頼を処理する。契約締結制御部３０６は、当該依頼を受信すると、サービス事業者の職員等に当該依頼の内容を通知する。 The contract conclusion control unit 306 is a means for controlling data provision contracts. The contract conclusion control unit 306 processes the provision contract conclusion request received from the transaction server 40. Upon receiving the request, the contract conclusion control unit 306 notifies the staff of the service provider of the contents of the request.
　職員等は、図１３に示すようなデータ提供申込を検討し、データ提供契約を締結するか否か決定する。契約締結制御部３０６は、ＧＵＩ等を用いて職員が決定した内容（データ提供申込を受け入れる、又は、拒否する）を取得する。 Employees, etc. will consider the data provision application as shown in Figure 13 and decide whether to conclude a data provision contract. The contract conclusion control unit 306 obtains the content decided by the staff (accept or reject the data provision application) using a GUI or the like.
　データ提供申込が受け入れられた場合、契約締結制御部３０６は、データ提供申込によるデータ提供契約を締結する旨を示す肯定応答を取引サーバ４０に送信する。 If the data provision application is accepted, the contract conclusion control unit 306 transmits an affirmative response to the transaction server 40 indicating that a data provision contract based on the data provision application is concluded.
　データ提供申込が拒否された場合、契約締結制御部３０６は、データ提供申込によるデータ提供契約を締結しない旨を示す否定応答を取引サーバ４０に送信する。 If the data provision application is rejected, the contract conclusion control unit 306 transmits a negative response to the transaction server 40 indicating that the data provision contract based on the data provision application will not be concluded.
　記憶部３０７は、サービスサーバ２０の動作に必要な情報を記憶する。例えば、記憶部３０７は、各アクター（サービス事業者、利用者、情報流通事業者）の口座情報と事業者コード、個人識別ＩＤ等を対応付けて記憶する。 The storage unit 307 stores information necessary for the operation of the service server 20. For example, the storage unit 307 stores account information of each actor (service provider, user, information distribution provider), provider code, personal identification ID, etc. in association with each other.
［データ利活用サーバ］
　データ利活用サーバ３０の処理構成は、サービスサーバ２０と同一とすることができる。データ利活用サーバ３０のデータ流通要請部３０３は、利用者（データ利活用事業者の職員等）に情報を提示し、利用者からの操作を受け付ければよい。具体的には、データ流通要請部３０３は、取引サーバ４０から取得したカタログ情報の一覧等を表示し、利用者が入力したデータ提供申込を取引サーバ４０に送信すればよい。 [Data utilization server]
The processing configuration of the data utilization server 30 can be the same as that of the service server 20. The data distribution requesting unit 303 of the data utilization server 30 may present information to the user (such as an employee of a data utilization business) and accept operations from the user. Specifically, the data distribution requesting unit 303 displays a list of catalog information acquired from the transaction server 40 and transmits the data provision application input by the user to the transaction server 40.
　また、データ利活用サーバ３０は、取引サーバ４０からデータ提供申込の契約が不成立であることを取得すると、その旨をデータ利活用事業者の職員等に通知する。この場合、データ利活用サーバ３０は、職員等から新たなデータ提供申込やデータ提供申込のキャンセルの指示を取得する。データ利活用サーバ３０は、新たなデータ提供申込や提供契約取消通知を取引サーバ４０に送信する。 Further, when the data utilization server 30 obtains from the transaction server 40 that the contract for the data provision application has not been concluded, it notifies the staff of the data utilization business to that effect. In this case, the data utilization server 30 obtains an instruction for a new data provision application or cancellation of a data provision application from a staff member or the like. The data utilization server 30 transmits a new data provision application or provision contract cancellation notification to the transaction server 40.
　データ利活用サーバ３０は、データ提供に関する支払に関する制御を行ってもよい。具体的には、データ利活用サーバ３０は、データ蓄積者との間で合意したデータ提供申込の支払を行ってもよいし、支払のための伝票等を出力してもよい。 The data utilization server 30 may control payments related to data provision. Specifically, the data utilization server 30 may pay for the data provision application agreed upon with the data accumulator, or may output a payment slip or the like.
［取引サーバ］
　図２２は、第１の実施形態に係る取引サーバ４０の処理構成（処理モジュール）の一例を示す図である。図２２を参照すると、取引サーバ４０は、通信制御部４０１と、口座開設部４０２と、カタログ情報要求部４０３と、提供申込処理部４０４と、記憶部４０５と、を備える。 [Transaction server]
FIG. 22 is a diagram showing an example of a processing configuration (processing module) of the transaction server 40 according to the first embodiment. Referring to FIG. 22, the transaction server 40 includes a communication control section 401, an account opening section 402, a catalog information request section 403, a provision application processing section 404, and a storage section 405.
　通信制御部４０１は、他の装置との間の通信を制御する手段である。例えば、通信制御部４０１は、流通制御サーバ１０からデータ（パケット）を受信する。また、通信制御部４０１は、流通制御サーバ１０に向けてデータを送信する。通信制御部４０１は、他の装置から受信したデータを他の処理モジュールに引き渡す。通信制御部４０１は、他の処理モジュールから取得したデータを他の装置に向けて送信する。このように、他の処理モジュールは、通信制御部４０１を介して他の装置とデータの送受信を行う。通信制御部４０１は、他の装置からデータを受信する受信部としての機能と、他の装置に向けてデータを送信する送信部としての機能と、を備える。 The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 401 transmits data to the distribution control server 10. Communication control unit 401 passes data received from other devices to other processing modules. The communication control unit 401 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 401. The communication control unit 401 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.
　口座開設部４０２は、提供によるデータ流通を希望する利用者の口座を開設する手段である。口座開設部４０２は、利用者の端末５０からユーザＩＤを取得する。口座開設部４０２は、取得したユーザＩＤを口座開設者リストに追加する（図２３参照）。 The account opening unit 402 is a means for opening an account for a user who wishes to distribute data by provision. The account opening unit 402 acquires the user ID from the user's terminal 50. The account opening unit 402 adds the acquired user ID to the account opening person list (see FIG. 23).
　カタログ情報要求部４０３は、流通制御サーバ１０に対して「カタログ情報送信要求」を送信する手段である。 The catalog information requesting unit 403 is a means for transmitting a "catalog information transmission request" to the distribution control server 10.
　カタログ情報要求部４０３は、データ利活用サーバ３０から「カタログ情報提示要求」を受信すると、流通制御サーバ１０に対して「カタログ情報送信要求」を送信する。 Upon receiving the “catalog information presentation request” from the data utilization server 30, the catalog information requesting unit 403 transmits a “catalog information transmission request” to the distribution control server 10.
　当該要求を送信することに応じて、カタログ情報要求部４０３は、流通制御サーバ１０が記憶しているカタログ情報を取得する。カタログ情報要求部４０３は、自装置が提携しているサービス事業者が関係するカタログ情報を選択して、データ利活用事業者（データ利活用サーバ３０）に送信する。なお、カタログ情報要求部４０３は、提携先のサービス事業者の事業者コードとカタログ情報に含まれる事業者コードに基づいて提携先のサービス事業者に関するカタログ情報を選択する。 In response to sending the request, the catalog information requesting unit 403 acquires the catalog information stored in the distribution control server 10. The catalog information requesting unit 403 selects catalog information related to a service provider with which the device itself is affiliated, and transmits it to the data utilization provider (data utilization server 30). Note that the catalog information requesting unit 403 selects catalog information regarding the affiliated service provider based on the operator code of the affiliated service provider and the operator code included in the catalog information.
　提供申込処理部４０４は、データ利活用サーバ３０から受信するデータ提供申込を処理する手段である。データ提供申込を受信すると、提供申込処理部４０４は、当該受信したデータ提供申込に提供申込ＩＤを付与する。提供申込処理部４０４は、提供申込ＩＤを用いてデータ提供申込を管理する。 The provision application processing unit 404 is a means for processing a data provision application received from the data utilization server 30. Upon receiving the data provision application, the provision application processing unit 404 assigns a provision application ID to the received data provision application. The provision application processing unit 404 manages data provision applications using the provision application ID.
　提供申込処理部４０４は、提供申込ＩＤ、データ提供申込と口座開設者リストを含む「提供要請」を流通制御サーバ１０に送信する。 The provision application processing unit 404 transmits a "provision request" including a provision application ID, a data provision application, and a list of account openers to the distribution control server 10.
　提供申込処理部４０４は、流通制御サーバ１０から提供元通知を受信する。当該提供元通知には、提供申込ＩＤ、データ提供の対象となるデータを蓄積するデータ蓄積者の名称、連絡先（サービスサーバ２０のアドレス）等が含まれる。 The provision application processing unit 404 receives the provider notification from the distribution control server 10. The provider notification includes the provider application ID, the name of the data storage person who stores the data to be provided, the contact information (the address of the service server 20), and the like.
　提供元通知を受信すると、提供申込処理部４０４は、データ蓄積者にデータ提供契約の依頼を行う。提供申込処理部４０４は、提供申込ＩＤ及びデータ提供申込を含む「提供契約締結依頼」をデータ蓄積者のサービスサーバ２０に送信する。 Upon receiving the provider notification, the provision application processing unit 404 requests the data storage person to enter into a data provision contract. The provision application processing unit 404 transmits a “provision contract conclusion request” including the provision application ID and the data provision application to the service server 20 of the data accumulator.
　提供申込処理部４０４は、サービスサーバ２０から提供契約締結依頼に対する応答を受信する。 The provision application processing unit 404 receives a response to the provision contract conclusion request from the service server 20.
　肯定応答（データ蓄積者はデータ提供申込に応じる旨の応答）を受信した場合、提供申込処理部４０４は、契約が成立したデータ提供申込の提供申込ＩＤを記憶する。さらに、提供申込処理部４０４は、データ提供申込の契約が成立したことを流通制御サーバ１０及びデータ利活用サーバ３０に通知する。提供申込処理部４０４は、提供申込ＩＤを含む「提供契約成立通知」を流通制御サーバ１０及びデータ利活用サーバ３０に送信する。 When receiving an affirmative response (a response indicating that the data accumulator accepts the data provision application), the provision application processing unit 404 stores the provision application ID of the data provision application for which a contract has been established. Furthermore, the provision application processing unit 404 notifies the distribution control server 10 and the data utilization server 30 that a data provision application contract has been established. The provision application processing unit 404 transmits a “provision contract establishment notification” including the provision application ID to the distribution control server 10 and the data utilization server 30.
　否定応答（データ蓄積者はデータ提供申込に応じない旨の応答）を受信した場合、提供申込処理部４０４は、データ提供申込の契約が不成立であることをデータ利活用サーバ３０に通知する。 When receiving a negative response (a response indicating that the data accumulator does not accept the data provision application), the provision application processing unit 404 notifies the data utilization server 30 that the contract for the data provision application has not been concluded.
　この場合、提供申込処理部４０４は、データ利活用サーバ３０から、新たなデータ提供申込（条件が見直されたデータ提供申込）又は提供契約取消通知を受信する。 In this case, the provision application processing unit 404 receives a new data provision application (data provision application with revised conditions) or a provision contract cancellation notice from the data utilization server 30.
　新たなデータ提供申込を受信した場合、提供申込処理部４０４は、当該新たなデータ提供契約を含む提供契約締結依頼をデータ蓄積者のサービスサーバ２０に送信する。 If a new data provision application is received, the provision application processing unit 404 transmits a provision contract conclusion request including the new data provision contract to the data accumulator's service server 20.
　提供契約取消通知を受信した場合、提供申込処理部４０４は、受信した提供契約取消通知を流通制御サーバ１０に転送する。 When receiving the provision contract cancellation notification, the provision application processing unit 404 transfers the received provision contract cancellation notification to the distribution control server 10.
　記憶部４０５は、取引サーバ４０の動作に必要な情報を記憶する。記憶部４０５は、提携先のサービス事業者の事業者コードを記憶する。 The storage unit 405 stores information necessary for the operation of the transaction server 40. The storage unit 405 stores the company code of the partner service provider.
［端末］
　図２４は、第１の実施形態に係る端末５０の処理構成（処理モジュール）の一例を示す図である。図２４を参照すると、端末５０は、通信制御部５０１と、個人情報入力部５０２と、問合せ処理部５０３と、記憶部５０４と、を備える。 [Terminal]
FIG. 24 is a diagram illustrating an example of a processing configuration (processing module) of the terminal 50 according to the first embodiment. Referring to FIG. 24, the terminal 50 includes a communication control section 501, a personal information input section 502, an inquiry processing section 503, and a storage section 504.
　通信制御部５０１は、他の装置との間の通信を制御する手段である。例えば、通信制御部５０１は、流通制御サーバ１０からデータ（パケット）を受信する。また、通信制御部５０１は、流通制御サーバ１０に向けてデータを送信する。通信制御部５０１は、他の装置から受信したデータを他の処理モジュールに引き渡す。通信制御部５０１は、他の処理モジュールから取得したデータを他の装置に向けて送信する。このように、他の処理モジュールは、通信制御部５０１を介して他の装置とデータの送受信を行う。通信制御部５０１は、他の装置からデータを受信する受信部としての機能と、他の装置に向けてデータを送信する送信部としての機能と、を備える。 The communication control unit 501 is a means for controlling communication with other devices. For example, the communication control unit 501 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 501 transmits data to the distribution control server 10. Communication control unit 501 passes data received from other devices to other processing modules. The communication control unit 501 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 501. The communication control unit 501 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.
　個人情報入力部５０２は、利用者登録の際に個人情報を流通制御サーバ１０に入力する手段である。個人情報入力部５０２は、任意の手段を用いて個人情報（氏名、生年月日、連絡先、口座情報等）を流通制御サーバ１０に入力する。例えば、個人情報入力部５０２は、ＧＵＩを用いて上記個人情報を利用者から取得し、当該取得した個人情報を流通制御サーバ１０に送信する。 The personal information input unit 502 is a means for inputting personal information into the distribution control server 10 during user registration. The personal information input unit 502 inputs personal information (name, date of birth, contact information, account information, etc.) into the distribution control server 10 using any means. For example, the personal information input unit 502 uses the GUI to obtain the above-mentioned personal information from the user, and transmits the obtained personal information to the distribution control server 10.
　個人情報入力部５０２は、流通制御サーバ１０から払い出されたユーザＩＤを記憶部５０４に記憶する。 The personal information input unit 502 stores the user ID issued by the distribution control server 10 in the storage unit 504.
　問合せ処理部５０３は、データ蓄積の問合せ、データ共有の問合せ又はデータ提供の問合せを処理する手段である。問合せ処理部５０３は、問い合わせの内容（データ蓄積、データ共有、データ提供）に合わせたＧＵＩを用いて利用者の意思（同意、不同意）を取得する。問合せ処理部５０３は、利用者の意思を含む応答を流通制御サーバ１０に送信する。 The inquiry processing unit 503 is a means for processing inquiries about data accumulation, inquiries about data sharing, or inquiries about data provision. The inquiry processing unit 503 obtains the user's intention (agreement, disagreement) using a GUI that matches the content of the inquiry (data accumulation, data sharing, data provision). The inquiry processing unit 503 transmits a response including the user's intention to the distribution control server 10.
　記憶部５０４は、端末５０の動作に必要な情報を記憶する。 The storage unit 504 stores information necessary for the operation of the terminal 50.
［病院端末］
　病院端末６０には、スマートフォン、タブレット等の携帯端末装置やコンピュータ（パーソナルコンピュータ、ノートパソコン）等が例示される。病院端末６０は、病院職員の操作を受け付け、流通制御サーバ１０等と通信可能であれば任意の機器、デバイスとすることができる。また、病院端末６０の構成等は当業者にとって明らかであるので、詳細な説明を省略する。 [Hospital terminal]
Examples of the hospital terminal 60 include mobile terminal devices such as smartphones and tablets, computers (personal computers, notebook computers), and the like. The hospital terminal 60 can be any equipment or device as long as it accepts operations from hospital staff and can communicate with the distribution control server 10 and the like. Further, since the configuration of the hospital terminal 60 is obvious to those skilled in the art, detailed explanation will be omitted.
　病院端末６０は、病院職員の操作に応じて、ＩＤ連携要求を流通制御サーバ１０に送信すればよい。また、病院端末６０は、ＩＤ連携要求を自社のサービスサーバ２０にも送信する。サービスサーバ２０（ＩＤ連携制御部３０２）は、ＩＤ連携要求に含まれる個人識別ＩＤに対応する利用者のエントリ（顧客情報データベースのエントリ）のＩＤ連携状態フィールドにフラグをセットする。 The hospital terminal 60 may send an ID cooperation request to the distribution control server 10 in response to an operation by a hospital staff member. The hospital terminal 60 also transmits the ID cooperation request to its own service server 20. The service server 20 (ID linkage control unit 302) sets a flag in the ID linkage status field of the user entry (customer information database entry) corresponding to the personal identification ID included in the ID linkage request.
［システムの動作］
　続いて、第１の実施形態に係る情報流通システムの動作について説明する。図２５は、第１の実施形態に係る情報流通システムの動作の一例を示すシーケンス図である。図２５を参照し、データ蓄積時のシステムの動作を説明する。 [System operation]
Next, the operation of the information distribution system according to the first embodiment will be explained. FIG. 25 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. The operation of the system during data accumulation will be explained with reference to FIG.
　サービスサーバ２０は、利用者のユーザデータを取得すると、蓄積同意取得要求を流通制御サーバ１０に送信する（ステップＳ４１）。 After acquiring the user data of the user, the service server 20 transmits a storage consent acquisition request to the distribution control server 10 (step S41).
　流通制御サーバ１０は、利用者の端末５０に対し、データ蓄積の問合せを送信する（ステップＳ４２）。 The distribution control server 10 transmits a data storage inquiry to the user's terminal 50 (step S42).
　流通制御サーバ１０は、端末５０から応答（データ蓄積に同意、不同意）を受信する（ステップＳ４３）。 The distribution control server 10 receives a response (agreeing to data storage, not agreeing) from the terminal 50 (step S43).
　流通制御サーバ１０は、端末５０から応答をサービスサーバ２０に送信する（ステップＳ４４）。 The distribution control server 10 transmits a response from the terminal 50 to the service server 20 (step S44).
　サービスサーバ２０は、利用者がデータ蓄積に同意すると、所在情報を流通制御サーバ１０に送信する（ステップＳ４５）。流通制御サーバ１０は、所在情報を記憶する。 When the user agrees to data storage, the service server 20 transmits the location information to the distribution control server 10 (step S45). The distribution control server 10 stores location information.
　図２６は、第１の実施形態に係る情報流通システムの動作の一例を示すシーケンス図である。図２６を参照し、データ提供時のシステムの動作を説明する。 FIG. 26 is a sequence diagram showing an example of the operation of the information distribution system according to the first embodiment. The operation of the system when providing data will be explained with reference to FIG.
　データ利活用サーバ３０からデータ提供申込を取得すると、取引サーバ４０は、当該データ提供申込と口座開設者リストを含む提供要請を流通制御サーバ１０に送信する（ステップＳ５１）。 Upon acquiring the data provision application from the data utilization server 30, the transaction server 40 transmits a provision request including the data provision application and the list of account openers to the distribution control server 10 (step S51).
　流通制御サーバ１０は、データ提供の対象となっているデータを蓄積しているデータ提供元を特定し、当該特定したデータ提供元の情報を含む提供元通知を取引サーバ４０に送信する（ステップＳ５２）。 The distribution control server 10 identifies the data provider that has accumulated the data to be provided, and transmits a provider notification containing information about the specified data provider to the transaction server 40 (step S52). ).
　提供元通知の送信に前後して、流通制御サーバ１０は、データ提供の対象者が所持する端末５０に対してデータ提供の問合せを送信する（ステップＳ５３）。 Before and after transmitting the provider notification, the distribution control server 10 transmits a data provision inquiry to the terminal 50 owned by the data provision target (step S53).
　流通制御サーバ１０は、端末５０からデータ提供の問合せに関する応答を受信する（ステップＳ５４）。 The distribution control server 10 receives a response regarding the data provision inquiry from the terminal 50 (step S54).
　提供元通知を受信した取引サーバ４０は、データ提供元のサービスサーバ２０に提供契約締結依頼を送信する（ステップＳ５５）。 The transaction server 40, which has received the provider notification, transmits a request to conclude a provision contract to the service server 20 of the data provider (step S55).
　サービスサーバ２０は、サービス事業者の検討結果に応じた応答を取引サーバ４０に送信する（ステップＳ５６）。 The service server 20 transmits a response according to the service provider's examination results to the transaction server 40 (step S56).
　データ提供の当事者間で契約が締結されると（サービスサーバ２０から肯定応答を受信すると）、取引サーバ４０は、提供契約成立通知を流通制御サーバ１０とデータ利活用サーバ３０に送信する（ステップＳ５７）。 When a contract is concluded between the data provision parties (when an affirmative response is received from the service server 20), the transaction server 40 sends a provision contract establishment notification to the distribution control server 10 and the data utilization server 30 (step S57). ).
　流通制御サーバ１０は、データ蓄積者（データ提供元）のサービスサーバ２０に対して提供指示を送信する（ステップＳ５８）。 The distribution control server 10 transmits a provision instruction to the service server 20 of the data accumulator (data provider) (step S58).
　サービスサーバ２０は、データ提供先（データ利活用サーバ３０）に指定されたデータを送信する（ステップＳ５９）。 The service server 20 transmits the specified data to the data provider (data utilization server 30) (step S59).
　以上のように、第１の実施形態に係る情報流通システムにおいて、情報流通事業者は、データ蓄積に対する対価をデータ提供元と利用者に支払う。その結果、データ提供元とデータ提供先がデータ提供契約を締結する前に、データ提供元は収益を得ることができる。また、情報流通事業者は、データ提供契約が履行された際、データ提供先が支払う対価の一部を提供対価として受け取ることで、先行してデータ蓄積に対して支払った費用を回収する。このように、情報流通システムからデータ蓄積の対価がデータ提供元に支払われることで、データ提供元は情報流通システムに参入する際に費やした投資を早期に回収できる。その結果、データ提供元が情報流通システムに参入する際のハードルが低くなり、より多くのデータ提供元がシステムに参加する。多くのデータ提供元がシステムに参加することで、情報流通システムはさらに発展する。 As described above, in the information distribution system according to the first embodiment, the information distribution business pays compensation for data accumulation to the data provider and the user. As a result, the data provider can earn revenue before the data provider and the data provider conclude a data provision contract. Furthermore, when the data provision contract is fulfilled, the information distribution business operator receives a portion of the consideration paid by the data provider as provision consideration, thereby recovering the expenses paid in advance for data storage. In this way, the information distribution system pays the data provider the price for data accumulation, allowing the data provider to quickly recover the investment it made when entering the information distribution system. As a result, the hurdles for data providers to enter the information distribution system will be lowered, and more data providers will participate in the system. The information distribution system will further develop as more data providers participate in the system.
　続いて、情報流通システムを構成する各装置のハードウェアについて説明する。図２７は、流通制御サーバ１０のハードウェア構成の一例を示す図である。 Next, the hardware of each device that makes up the information distribution system will be explained. FIG. 27 is a diagram showing an example of the hardware configuration of the distribution control server 10.
　流通制御サーバ１０は、情報処理装置（所謂、コンピュータ）により構成可能であり、図２７に例示する構成を備える。例えば、流通制御サーバ１０は、プロセッサ３１１、メモリ３１２、入出力インターフェイス３１３及び通信インターフェイス３１４等を備える。上記プロセッサ３１１等の構成要素は内部バス等により接続され、相互に通信可能に構成されている。 The distribution control server 10 can be configured by an information processing device (so-called computer), and has the configuration illustrated in FIG. 27. For example, the distribution control server 10 includes a processor 311, a memory 312, an input/output interface 313, a communication interface 314, and the like. The components such as the processor 311 are connected by an internal bus or the like and are configured to be able to communicate with each other.
　但し、図２７に示す構成は、流通制御サーバ１０のハードウェア構成を限定する趣旨ではない。流通制御サーバ１０は、図示しないハードウェアを含んでもよいし、必要に応じて入出力インターフェイス３１３を備えていなくともよい。また、流通制御サーバ１０に含まれるプロセッサ３１１等の数も図２７の例示に限定する趣旨ではなく、例えば、複数のプロセッサ３１１が流通制御サーバ１０に含まれていてもよい。 However, the configuration shown in FIG. 27 is not intended to limit the hardware configuration of the distribution control server 10. The distribution control server 10 may include hardware that is not shown, and may not include the input/output interface 313 if necessary. Further, the number of processors 311 and the like included in the distribution control server 10 is not limited to the example shown in FIG. 27; for example, a plurality of processors 311 may be included in the distribution control server 10.
　プロセッサ３１１は、例えば、ＣＰＵ（Central Processing Unit）、ＭＰＵ（Micro Processing Unit）、ＤＳＰ（Digital Signal Processor）等のプログラマブルなデバイスである。あるいは、プロセッサ３１１は、ＦＰＧＡ（Field Programmable Gate Array）、ＡＳＩＣ（Application Specific Integrated Circuit）等のデバイスであってもよい。プロセッサ３１１は、オペレーティングシステム（ＯＳ；Operating System）を含む各種プログラムを実行する。 The processor 311 is, for example, a programmable device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs including an operating system (OS).
　メモリ３１２は、ＲＡＭ（Random Access Memory）、ＲＯＭ（Read Only Memory）、ＨＤＤ（Hard Disk Drive）、ＳＳＤ（Solid State Drive）等である。メモリ３１２は、ＯＳプログラム、アプリケーションプログラム、各種データを格納する。 The memory 312 is a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. The memory 312 stores OS programs, application programs, and various data.
　入出力インターフェイス３１３は、図示しない表示装置や入力装置のインターフェイスである。表示装置は、例えば、液晶ディスプレイ等である。入力装置は、例えば、キーボードやマウス等のユーザ操作を受け付ける装置である。 The input/output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device such as a keyboard or a mouse that receives user operations.
　通信インターフェイス３１４は、他の装置と通信を行う回路、モジュール等である。例えば、通信インターフェイス３１４は、ＮＩＣ（Network Interface Card）等を備える。 The communication interface 314 is a circuit, module, etc. that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card).
　流通制御サーバ１０の機能は、各種処理モジュールにより実現される。当該処理モジュールは、例えば、メモリ３１２に格納されたプログラムをプロセッサ３１１が実行することで実現される。また、当該プログラムは、コンピュータが読み取り可能な記憶媒体に記録することができる。記憶媒体は、半導体メモリ、ハードディスク、磁気記録媒体、光記録媒体等の非トランジェント（non-transitory）なものとすることができる。即ち、本発明は、コンピュータプログラム製品として具現することも可能である。また、上記プログラムは、ネットワークを介してダウンロードするか、あるいは、プログラムを記憶した記憶媒体を用いて、更新することができる。さらに、上記処理モジュールは、半導体チップにより実現されてもよい。 The functions of the distribution control server 10 are realized by various processing modules. The processing module is realized, for example, by the processor 311 executing a program stored in the memory 312. Further, the program can be recorded on a computer-readable storage medium. The storage medium can be non-transitory, such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. That is, the present invention can also be implemented as a computer program product. Furthermore, the above program can be updated via a network or by using a storage medium that stores the program. Furthermore, the processing module may be realized by a semiconductor chip.
　なお、サービスサーバ２０等も流通制御サーバ１０と同様に情報処理装置により構成可能であり、その基本的なハードウェア構成は流通制御サーバ１０と相違する点はないので説明を省略する。 Note that the service server 20 and the like can be configured by an information processing device in the same way as the distribution control server 10, and the basic hardware configuration thereof is not different from the distribution control server 10, so a description thereof will be omitted.
　情報処理装置である流通制御サーバ１０は、コンピュータを搭載し、当該コンピュータにプログラムを実行させることで流通制御サーバ１０の機能が実現できる。また、流通制御サーバ１０は、当該プログラムにより流通制御サーバ１０の制御方法を実行する。 The distribution control server 10, which is an information processing device, is equipped with a computer, and the functions of the distribution control server 10 can be realized by having the computer execute a program. Further, the distribution control server 10 executes the control method of the distribution control server 10 using the program.
［変形例］
　なお、上記実施形態にて説明した情報流通システムの構成、動作等は例示であって、システムの構成等を限定する趣旨ではない。 [Modified example]
Note that the configuration, operation, etc. of the information distribution system described in the above embodiments are merely examples, and are not intended to limit the configuration, etc. of the system.
　上記実施形態では、サービス事業者が情報流通事業者にデータ蓄積の同意取得（利用者の同意取得）を依頼する場合について説明した。しかし、サービス事業者（サービスサーバ２０）が直接、利用者のデータ蓄積に対する同意を取得してもよい。サービスサーバ２０は、ユーザデータを記憶するたびに、利用者が所持する端末５０にデータ蓄積の問合せを送信する。サービスサーバ２０は、利用者がデータ蓄積に同意すると、所在情報を流通制御サーバ１０に送信してもよい。 In the above embodiment, a case has been described in which a service provider requests an information distribution company to obtain consent for data storage (obtain user consent). However, the service provider (service server 20) may directly obtain the user's consent for data storage. Each time the service server 20 stores user data, it sends a data storage inquiry to the terminal 50 owned by the user. The service server 20 may transmit location information to the distribution control server 10 when the user agrees to data storage.
　上記実施形態では、データ提供元とデータ提供先は、主に提供データの単価（１データあたりの対価）について価格交渉する場合を前提に説明を行った。データ提供元とデータ提供先は、データ量について交渉を行ったり、分配率について交渉を行ったりしてもよい。 The above embodiment has been described on the premise that the data provider and the data provider mainly negotiate the unit price of the provided data (price per piece of data). The data provider and the data provider may negotiate the amount of data or the distribution rate.
　データ利活用事業者は、取引事業者を介してデータ提供に対する対価を情報流通事業者に支払ってもよい。あるいは、情報流通事業者は、データ蓄積者（データ提供元）や利用者に支払う対価を、取引事業者を介して支払ってもよい。 A data utilization business may pay compensation for providing data to an information distribution business via a transaction business. Alternatively, the information distribution business operator may pay the consideration to the data accumulator (data provider) or user via the transaction business operator.
　上記実施形態では、流通制御サーバ１０の内部に利用者情報データベースが構成される場合について説明したが、当該データベースは外部のデータベースサーバ等に構築されてもよい。即ち、流通制御サーバ１０の一部の機能は別のサーバに実装されていてもよい。より具体的には、上記説明した「データ流通制御部（データ流通制御手段）」等がシステムに含まれるいずれかの装置に実装されていればよい。 In the above embodiment, a case has been described in which the user information database is configured inside the distribution control server 10, but the database may be configured in an external database server or the like. That is, some functions of the distribution control server 10 may be implemented in another server. More specifically, the above-described "data distribution control unit (data distribution control means)" etc. may be implemented in any device included in the system.
　各装置（流通制御サーバ１０、サービスサーバ２０等）間のデータ送受信の形態は特に限定されないが、これら装置間で送受信されるデータは暗号化されていてもよい。これらの装置間では、利用者の個人情報等が送受信され、これらの情報を適切に保護するためには、暗号化されたデータが送受信されることが望ましい。 The form of data transmission and reception between each device (distribution control server 10, service server 20, etc.) is not particularly limited, but data transmitted and received between these devices may be encrypted. Personal information of users is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable that encrypted data be transmitted and received.
　上記説明で用いた流れ図（フローチャート、シーケンス図）では、複数の工程（処理）が順番に記載されているが、実施形態で実行される工程の実行順序は、その記載の順番に制限されない。実施形態では、例えば各処理を並行して実行する等、図示される工程の順番を内容的に支障のない範囲で変更することができる。 Although a plurality of steps (processes) are described in order in the flowcharts (flowcharts, sequence diagrams) used in the above description, the order in which the steps are executed in the embodiment is not limited to the order in which they are described. In the embodiment, the order of the illustrated steps can be changed within a range that does not affect the content, such as executing each process in parallel, for example.
　上記の実施形態は本願開示の理解を容易にするために詳細に説明したものであり、上記説明したすべての構成が必要であることを意図したものではない。また、複数の実施形態について説明した場合には、各実施形態は単独で用いてもよいし、組み合わせて用いてもよい。例えば、実施形態の構成の一部を他の実施形態の構成に置き換えることや、実施形態の構成に他の実施形態の構成を加えることも可能である。さらに、実施形態の構成の一部について他の構成の追加、削除、置換が可能である。 The above embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all the configurations described above are necessary. Further, when a plurality of embodiments are described, each embodiment may be used alone or in combination. For example, it is also possible to replace a part of the configuration of the embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of the embodiment. Furthermore, it is possible to add, delete, or replace some of the configurations of the embodiments with other configurations.
　上記の説明により、本発明の産業上の利用可能性は明らかであるが、本発明は、利用者に提供されるサービスに関する蓄積データを流通する情報流通システムなどに好適に適用可能である。 The industrial applicability of the present invention is clear from the above description, and the present invention is suitably applicable to an information distribution system that distributes accumulated data regarding services provided to users.
　上記の実施形態の一部又は全部は、以下の付記のようにも記載され得るが、以下には限られない。
［付記１］
　サービス事業者により運営され、利用者にサービスを提供することで発生したユーザデータを記憶する、サービスサーバと、
　データ利活用事業者により運営される、データ利活用サーバと、
　情報流通事業者により運営される、流通制御サーバと、
　を含み、
　前記流通制御サーバは、
　前記ユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、
　前記データ蓄積により登録された前記ユーザデータを前記サービスサーバから前記データ利活用サーバに提供するためのデータ提供を制御し、
　前記サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、
　前記データ利活用事業者から前記データ提供に対する提供対価を前記情報流通事業者が受け取るための制御を行う、システム。
［付記２］
　前記サービスサーバは、前記ユーザデータを記憶すると、前記ユーザデータに関する情報を含む蓄積同意取得要求を前記流通制御サーバに送信し、
　前記流通制御サーバは、前記利用者が所持する端末に、前記ユーザデータに関する情報を含むデータ蓄積の問合せを送信し、前記利用者が所持する端末から前記データ蓄積の問合せに対する応答を受信し、前記受信した応答を前記サービスサーバに転送する、付記１に記載のシステム。
［付記３］
　前記サービスサーバは、前記利用者が前記ユーザデータの蓄積に同意すると、前記記憶されたユーザデータのデータ種類を含む所在情報を前記流通制御サーバに送信し、
　前記流通制御サーバは、
　前記所在情報を受信したことに応じて前記ユーザデータの前記データ蓄積を行い、
　前記データ種類ごとに予め定められた蓄積対価定義に基づき、前記サービス事業者と前記利用者に支払う前記蓄積対価を算出する、付記２に記載のシステム。
［付記４］
　前記蓄積対価定義は、前記蓄積されるユーザデータのデータ種類と、１つのデータの蓄積により前記情報流通事業者から支払われる対価と、前記情報流通事業者から支払われる対価の前記サービス事業者と前記利用者の分配率と、を含む、付記３に記載のシステム。
［付記５］
　前記データ利活用サーバから、前記データ提供により前記データ利活用事業者に提供される提供データの要件と、前記データ提供により前記データ利活用事業者が支払う前記提供対価の提示の詳細を含む提供対価提示と、を含むデータ提供申込を受信し、前記データ提供申込を含む提供要請を前記流通制御サーバに送信する、取引サーバをさらに含み、
　前記流通制御サーバは、
　前記提供要請を受信すると、前記データ提供の対象となる前記利用者を特定し、前記特定された利用者の端末に、データ提供の問合せを送信することで、前記データ提供に前記利用者が同意するか否かを取得すると共に、
　前記データ提供の対象となる前記ユーザデータを記憶している前記サービス事業者を特定し、前記特定したサービス事業者の情報を含む提供元通知を前記取引サーバに送信し、
　前記取引サーバは、前記特定されたサービス事業者に対し前記データ利活用事業者との間で前記データ提供申込の契約締結を依頼する、付記１乃至４のいずれか一項に記載のシステム。
［付記６］
　前記流通制御サーバは、前記データ提供に前記利用者が同意し、且つ、前記サービス事業者と前記データ利活用事業者の間で前記データ提供申込に関する契約が成立すると、前記サービスサーバに対して前記記憶されたユーザデータを前記データ利活用サーバに送信するように指示する、付記５に記載のシステム。
［付記７］
　前記流通制御サーバは、前記サービスサーバに対して前記記憶されたユーザデータを前記データ利活用サーバに送信するように指示したことに応じて、前記契約が成立したデータ提供申込と前記データ提供の取引履歴を記憶する、付記６に記載のシステム。
［付記８］
　前記流通制御サーバは、前記契約が成立したデータ提供申込の前記提供データの要件と前記提供対価提示に基づき前記提供対価を算出する、付記７に記載のシステム。
［付記９］
　前記提供対価提示は、前記提供されるユーザデータのデータ種類と、１つのデータの提供により前記データ利活用事業者から支払われる対価と、前記データ利活用事業者から支払われる対価の前記サービス事業者、前記利用者及び前記情報流通事業者それぞれへの分配率と、を含む、付記８に記載のシステム。
［付記１０］
　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する、蓄積制御部と、
　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する、データ流通制御部と、
　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、決済制御部と、
　を備える、流通制御サーバ。
［付記１１］
　流通制御サーバにおいて、
　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、
　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御し、
　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、流通制御サーバの制御方法。
［付記１２］
　流通制御サーバに搭載されたコンピュータに、
　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する処理と、
　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する処理と、
　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う処理と、
　を実行させるためのプログラムを記憶する、コンピュータ読取可能な記憶媒体。 Part or all of the above embodiments may be described as in the following additional notes, but are not limited to the following.
[Additional note 1]
A service server operated by a service provider and storing user data generated by providing services to users;
A data utilization server operated by a data utilization business;
A distribution control server operated by an information distribution business;
including;
The distribution control server is
controlling data accumulation for registering the user data in an information distribution system as data that can be provided to a third party;
controlling data provision for providing the user data registered by the data accumulation from the service server to the data utilization server;
paying storage fees for the data storage to the service provider and the user;
A system that performs control for the information distribution business to receive compensation for the data provision from the data utilization business.
[Additional note 2]
When the service server stores the user data, the service server transmits a storage consent acquisition request including information regarding the user data to the distribution control server;
The distribution control server transmits a data accumulation inquiry including information regarding the user data to a terminal owned by the user, receives a response to the data accumulation inquiry from the terminal owned by the user, and The system according to appendix 1, wherein the system forwards the received response to the service server.
[Additional note 3]
When the user agrees to store the user data, the service server transmits location information including the data type of the stored user data to the distribution control server;
The distribution control server is
performing the data accumulation of the user data in response to receiving the location information;
The system according to supplementary note 2, wherein the accumulation consideration to be paid to the service provider and the user is calculated based on an accumulation consideration definition predetermined for each data type.
[Additional note 4]
The accumulation consideration definition includes the data type of the user data to be accumulated, the consideration paid by the information distribution business for accumulating one data, the service provider of the consideration paid by the information distribution business, and the The system according to appendix 3, comprising: a user distribution rate;
[Additional note 5]
Requirements for the provided data to be provided from the data utilization server to the data utilization business operator through the data provision, and provided consideration including details of the presentation of the provision consideration to be paid by the data utilization business operator upon the data provision. further comprising a transaction server that receives a data provision application including a presentation and transmits a provision request including the data provision application to the distribution control server;
The distribution control server is
Upon receiving the provision request, the user to whom the data is to be provided is identified, and a data provision inquiry is sent to the identified user's terminal, thereby ensuring that the user agrees to the data provision. In addition to obtaining whether or not
identifying the service provider that stores the user data to which the data is to be provided, and transmitting a provider notification containing information on the identified service provider to the transaction server;
5. The system according to any one of appendices 1 to 4, wherein the transaction server requests the identified service provider to conclude a contract for the data provision application with the data utilization provider.
[Additional note 6]
When the user agrees to the data provision and a contract regarding the data provision application is established between the service provider and the data utilization provider, the distribution control server sends the service to the service server. The system according to appendix 5, wherein the system instructs to transmit the stored user data to the data utilization server.
[Additional note 7]
In response to instructing the service server to transmit the stored user data to the data utilization server, the distribution control server transfers the data provision application for which the contract has been concluded and the data provision transaction. The system according to appendix 6, which stores history.
[Additional note 8]
The system according to appendix 7, wherein the distribution control server calculates the provision consideration based on the requirements of the provision data of the data provision application for which the contract has been established and the provision consideration presentation.
[Additional note 9]
The provision consideration presentation includes the data type of the provided user data, the consideration paid by the data utilization business operator for providing one piece of data, and the service business operator of the consideration paid by the data utilization business operator. , and a distribution rate to each of the user and the information distribution business operator.
[Additional note 10]
an accumulation control unit that controls data accumulation for registering user data generated when a service provider provides a service to a user in an information distribution system as data that can be provided to a third party;
a data distribution control unit that controls data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider; and,
a payment control unit that performs control such that an information distribution business operator pays accumulation fees for the data storage to the service provider and the user, and receives compensation for the data provision from the data utilization business operator;
Distribution control server equipped with.
[Additional note 11]
In the distribution control server,
Controls data accumulation for registering user data generated by service providers providing services to users in the information distribution system as data that can be provided to third parties,
controlling data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider;
A method for controlling a distribution control server, the method comprising: paying a service provider and the user a compensation for storing the data; and controlling an information distribution business to receive compensation for providing the data from the data utilization business.
[Additional note 12]
On the computer installed in the distribution control server,
A process for controlling data accumulation for registering user data generated when a service provider provides services to users in an information distribution system as data that can be provided to a third party;
a process for controlling data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider;
A process of performing control such that an information distribution business operator receives compensation for providing the data from the data utilization business operator by paying accumulation compensation for the data storage to the service provider and the user;
A computer-readable storage medium that stores a program for executing.
　なお、引用した上記の先行技術文献の各開示は、本書に引用をもって繰り込むものとする。以上、本発明の実施形態を説明したが、本発明はこれらの実施形態に限定されるものではない。これらの実施形態は例示にすぎないということ、及び、本発明のスコープ及び精神から逸脱することなく様々な変形が可能であるということは、当業者に理解されるであろう。即ち、本発明は、請求の範囲を含む全開示、技術的思想にしたがって当業者であればなし得る各種変形、修正を含むことは勿論である。 Furthermore, each disclosure of the cited prior art documents mentioned above shall be incorporated into this document by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are illustrative only and that various modifications can be made without departing from the scope and spirit of the invention. That is, it goes without saying that the present invention includes the entire disclosure including the claims and various modifications and modifications that can be made by those skilled in the art in accordance with the technical idea.
１０　　　流通制御サーバ
２０　　　サービスサーバ
２０－１　サービスサーバ
２０－２　サービスサーバ
３０　　　データ利活用サーバ
４０　　　取引サーバ
５０　　　端末
６０　　　病院端末
１０１　　サービスサーバ
１０２　　データ利活用サーバ
１０３　　流通制御サーバ
２０１　　通信制御部
２０２　　利用者登録部
２０３　　ＩＤ連携部
２０４　　対価定義公開部
２０５　　蓄積同意制御部
２０６　　所在情報管理部
２０７　　データ流通制御部
２０８　　カタログ情報管理部
２０９　　決済制御部
２１０　　記憶部
３０１　　通信制御部
３０２　　ＩＤ連携制御部
３０３　　データ流通要請部
３０４　　データ蓄積制御部
３０５　　データ流通部
３０６　　契約締結制御部
３０７　　記憶部
３１１　　プロセッサ
３１２　　メモリ
３１３　　入出力インターフェイス
３１４　　通信インターフェイス
４０１　　通信制御部
４０２　　口座開設部
４０３　　カタログ情報要求部
４０４　　提供申込処理部
４０５　　記憶部
５０１　　通信制御部
５０２　　個人情報入力部
５０３　　問合せ処理部
５０４　　記憶部 10 Distribution control server 20 Service server 20-1 Service server 20-2 Service server 30 Data utilization server 40 Transaction server 50 Terminal 60 Hospital terminal 101 Service server 102 Data utilization server 103 Distribution control server 201 Communication control unit 202 User registration Section 203 ID cooperation section 204 Consideration definition disclosure section 205 Accumulation consent control section 206 Location information management section 207 Data distribution control section 208 Catalog information management section 209 Payment control section 210 Storage section 301 Communication control section 302 ID cooperation control section 303 Data distribution request Section 304 Data accumulation control section 305 Data distribution section 306 Contract conclusion control section 307 Storage section 311 Processor 312 Memory 313 Input/output interface 314 Communication interface 401 Communication control section 402 Account opening section 403 Catalog information request section 404 Providing application processing section 405 Storage section 501 Communication control section 502 Personal information input section 503 Inquiry processing section 504 Storage section

Claims (12)

  1. 　サービス事業者により運営され、利用者にサービスを提供することで発生したユーザデータを記憶する、サービスサーバと、
    　データ利活用事業者により運営される、データ利活用サーバと、
    　情報流通事業者により運営される、流通制御サーバと、
    　を含み、
    　前記流通制御サーバは、
    　前記ユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、
    　前記データ蓄積により登録された前記ユーザデータを前記サービスサーバから前記データ利活用サーバに提供するためのデータ提供を制御し、
    　前記サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、
    　前記データ利活用事業者から前記データ提供に対する提供対価を前記情報流通事業者が受け取るための制御を行う、システム。     A service server operated by a service provider and storing user data generated by providing services to users;
    A data utilization server operated by a data utilization business;
    A distribution control server operated by an information distribution business;
    including;
    The distribution control server is
    controlling data accumulation for registering the user data in an information distribution system as data that can be provided to a third party;
    controlling data provision for providing the user data registered by the data accumulation from the service server to the data utilization server;
    paying storage fees for the data storage to the service provider and the user;
    A system that performs control for the information distribution business to receive compensation for the data provision from the data utilization business.
  2. 　前記サービスサーバは、前記ユーザデータを記憶すると、前記ユーザデータに関する情報を含む蓄積同意取得要求を前記流通制御サーバに送信し、
    　前記流通制御サーバは、前記利用者が所持する端末に、前記ユーザデータに関する情報を含むデータ蓄積の問合せを送信し、前記利用者が所持する端末から前記データ蓄積の問合せに対する応答を受信し、前記受信した応答を前記サービスサーバに転送する、請求項１に記載のシステム。     When the service server stores the user data, the service server transmits a storage consent acquisition request including information regarding the user data to the distribution control server;
    The distribution control server transmits a data accumulation inquiry including information regarding the user data to a terminal owned by the user, receives a response to the data accumulation inquiry from the terminal owned by the user, and The system of claim 1, forwarding received responses to the service server.
  3. 　前記サービスサーバは、前記利用者が前記ユーザデータの蓄積に同意すると、前記記憶されたユーザデータのデータ種類を含む所在情報を前記流通制御サーバに送信し、
    　前記流通制御サーバは、
    　前記所在情報を受信したことに応じて前記ユーザデータの前記データ蓄積を行い、
    　前記データ種類ごとに予め定められた蓄積対価定義に基づき、前記サービス事業者と前記利用者に支払う前記蓄積対価を算出する、請求項２に記載のシステム。     When the user agrees to store the user data, the service server transmits location information including the data type of the stored user data to the distribution control server;
    The distribution control server is
    performing the data accumulation of the user data in response to receiving the location information;
    The system according to claim 2, wherein the accumulation consideration to be paid to the service provider and the user is calculated based on an accumulation consideration definition predetermined for each data type.
  4. 　前記蓄積対価定義は、前記蓄積されるユーザデータのデータ種類と、１つのデータの蓄積により前記情報流通事業者から支払われる対価と、前記情報流通事業者から支払われる対価の前記サービス事業者と前記利用者の分配率と、を含む、請求項３に記載のシステム。 The accumulation consideration definition includes the data type of the user data to be accumulated, the consideration paid by the information distribution business for accumulating one data, the service provider of the consideration paid by the information distribution business, and the 4. The system of claim 3, comprising a user's share.
  5. 　前記データ利活用サーバから、前記データ提供により前記データ利活用事業者に提供される提供データの要件と、前記データ提供により前記データ利活用事業者が支払う前記提供対価の提示の詳細を含む提供対価提示と、を含むデータ提供申込を受信し、前記データ提供申込を含む提供要請を前記流通制御サーバに送信する、取引サーバをさらに含み、
    　前記流通制御サーバは、
    　前記提供要請を受信すると、前記データ提供の対象となる前記利用者を特定し、前記特定された利用者の端末に、データ提供の問合せを送信することで、前記データ提供に前記利用者が同意するか否かを取得すると共に、
    　前記データ提供の対象となる前記ユーザデータを記憶している前記サービス事業者を特定し、前記特定したサービス事業者の情報を含む提供元通知を前記取引サーバに送信し、
    　前記取引サーバは、前記特定されたサービス事業者に対し前記データ利活用事業者との間で前記データ提供申込の契約締結を依頼する、請求項１乃至４のいずれか一項に記載のシステム。     Requirements for the provided data to be provided from the data utilization server to the data utilization business operator through the data provision, and provided consideration including details of the presentation of the provision consideration to be paid by the data utilization business operator upon the data provision. further comprising a transaction server that receives a data provision application including a presentation and transmits a provision request including the data provision application to the distribution control server;
    The distribution control server is
    Upon receiving the provision request, the user to whom the data is to be provided is identified, and a data provision inquiry is sent to the identified user's terminal, thereby ensuring that the user agrees to the data provision. In addition to obtaining whether or not
    identifying the service provider that stores the user data to which the data is to be provided, and transmitting a provider notification containing information on the identified service provider to the transaction server;
    5. The system according to claim 1, wherein the transaction server requests the identified service provider to conclude a contract for the data provision application with the data utilization provider.
  6. 　前記流通制御サーバは、前記データ提供に前記利用者が同意し、且つ、前記サービス事業者と前記データ利活用事業者の間で前記データ提供申込に関する契約が成立すると、前記サービスサーバに対して前記記憶されたユーザデータを前記データ利活用サーバに送信するように指示する、請求項５に記載のシステム。 When the user agrees to the data provision and a contract regarding the data provision application is established between the service provider and the data utilization provider, the distribution control server sends the service to the service server. The system according to claim 5, wherein the system instructs to transmit the stored user data to the data utilization server.
  7. 　前記流通制御サーバは、前記サービスサーバに対して前記記憶されたユーザデータを前記データ利活用サーバに送信するように指示したことに応じて、前記契約が成立したデータ提供申込と前記データ提供の取引履歴を記憶する、請求項６に記載のシステム。 In response to instructing the service server to transmit the stored user data to the data utilization server, the distribution control server transfers the data provision application for which the contract has been concluded and the data provision transaction. 7. The system of claim 6, storing history.
  8. 　前記流通制御サーバは、前記契約が成立したデータ提供申込の前記提供データの要件と前記提供対価提示に基づき前記提供対価を算出する、請求項７に記載のシステム。 The system according to claim 7, wherein the distribution control server calculates the provision consideration based on the requirements of the provision data of the data provision application for which the contract has been established and the provision consideration presentation.
  9. 　前記提供対価提示は、前記提供されるユーザデータのデータ種類と、１つのデータの提供により前記データ利活用事業者から支払われる対価と、前記データ利活用事業者から支払われる対価の前記サービス事業者、前記利用者及び前記情報流通事業者それぞれへの分配率と、を含む、請求項８に記載のシステム。 The provision consideration presentation includes the data type of the provided user data, the consideration paid by the data utilization business operator for providing one piece of data, and the service business operator of the consideration paid by the data utilization business operator. , a distribution rate to each of the user and the information distribution business.
  10. 　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する、蓄積制御部と、
    　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する、データ流通制御部と、
    　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、決済制御部と、
    　を備える、流通制御サーバ。     an accumulation control unit that controls data accumulation for registering user data generated when a service provider provides a service to a user in an information distribution system as data that can be provided to a third party;
    a data distribution control unit that controls data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider; and,
    a payment control unit that performs control such that an information distribution business operator pays accumulation fees for the data storage to the service provider and the user, and receives compensation for the data provision from the data utilization business operator;
    Distribution control server equipped with.
  11. 　流通制御サーバにおいて、
    　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御し、
    　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御し、
    　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う、流通制御サーバの制御方法。     In the distribution control server,
    Controls data accumulation for registering user data generated by service providers providing services to users in the information distribution system as data that can be provided to third parties,
    controlling data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider;
    A method for controlling a distribution control server, the method comprising: paying a service provider and the user a compensation for storing the data; and controlling an information distribution business to receive compensation for providing the data from the data utilization business.
  12. 　流通制御サーバに搭載されたコンピュータに、
    　サービス事業者が利用者にサービスを提供することで発生したユーザデータを第三者に提供可能なデータとして情報流通システムに登録するためのデータ蓄積を制御する処理と、
    　前記データ蓄積により登録された前記ユーザデータを前記サービス事業者により運営されるサービスサーバからデータ利活用事業者により運営されるデータ利活用サーバに提供するためのデータ提供を制御する処理と、
    　サービス事業者及び前記利用者に前記データ蓄積に対する蓄積対価を支払い、前記データ利活用事業者から前記データ提供に対する提供対価を情報流通事業者が受け取るための制御を行う処理と、
    　を実行させるためのプログラムを記憶する、コンピュータ読取可能な記憶媒体。     On the computer installed in the distribution control server,
    A process for controlling data accumulation for registering user data generated when a service provider provides services to users in an information distribution system as data that can be provided to a third party;
    a process for controlling data provision for providing the user data registered through the data accumulation from a service server operated by the service provider to a data utilization server operated by a data utilization provider;
    A process of performing control such that an information distribution business operator receives compensation for providing the data from the data utilization business operator by paying accumulation compensation for the data storage to the service provider and the user;
    A computer-readable storage medium that stores a program for executing.
PCT/JP2022/016081 2022-03-30 2022-03-30 System, distribution control server, distribution control server control method, and storage medium WO2023188136A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/016081 WO2023188136A1 (en) 2022-03-30 2022-03-30 System, distribution control server, distribution control server control method, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/016081 WO2023188136A1 (en) 2022-03-30 2022-03-30 System, distribution control server, distribution control server control method, and storage medium

Publications (1)

Publication Number Publication Date
WO2023188136A1 true WO2023188136A1 (en) 2023-10-05

Family

ID=88199752

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/016081 WO2023188136A1 (en) 2022-03-30 2022-03-30 System, distribution control server, distribution control server control method, and storage medium

Country Status (1)

Country Link
WO (1) WO2023188136A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100186066A1 (en) * 2009-01-20 2010-07-22 Pollard Stephen M Methods and systems for facilitating personal data propagation
JP2016511890A (en) * 2013-02-08 2016-04-21 イージー アズ ア ドリンク プロダクションズ， インク．ＥＺ Ａｓ Ａ Ｄｒｉｎｋ Ｐｒｏｄｕｃｔｉｏｎｓ， Ｉｎｃ． Provision of personal data market
JP2016154011A (en) * 2016-02-29 2016-08-25 ヤフー株式会社 Information transaction device, information transaction method, and information transaction program
JP2019128648A (en) * 2018-01-22 2019-08-01 株式会社 みずほ銀行 Information management system, information management method and information management program
JP2020129311A (en) * 2019-02-08 2020-08-27 富士通株式会社 Data distribution control device, data distribution control method, and data distribution control program
WO2021085064A1 (en) * 2019-10-31 2021-05-06 日本電気株式会社 Information transaction device, information transaction method, and program

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100186066A1 (en) * 2009-01-20 2010-07-22 Pollard Stephen M Methods and systems for facilitating personal data propagation
JP2016511890A (en) * 2013-02-08 2016-04-21 イージー アズ ア ドリンク プロダクションズ， インク．ＥＺ Ａｓ Ａ Ｄｒｉｎｋ Ｐｒｏｄｕｃｔｉｏｎｓ， Ｉｎｃ． Provision of personal data market
JP2016154011A (en) * 2016-02-29 2016-08-25 ヤフー株式会社 Information transaction device, information transaction method, and information transaction program
JP2019128648A (en) * 2018-01-22 2019-08-01 株式会社 みずほ銀行 Information management system, information management method and information management program
JP2020129311A (en) * 2019-02-08 2020-08-27 富士通株式会社 Data distribution control device, data distribution control method, and data distribution control program
WO2021085064A1 (en) * 2019-10-31 2021-05-06 日本電気株式会社 Information transaction device, information transaction method, and program

Similar Documents

Publication Publication Date Title
JP4514783B2 (en) Health management data communication system
US9934493B2 (en) Real-time transactions for a virtual account
US8355935B2 (en) Third party information transfer
TW381241B (en) Electronic wallet based on distributed network
US20090192941A1 (en) Digital marketplace for healthcare data
US20180322543A1 (en) System and Method for Healthcare Donations using a Private Distributed Ledger
US20100241458A1 (en) System for communication of health care data
US11455597B2 (en) Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal
Meessen The role of digital strategies in financing health care for universal health coverage in low-and middle-income countries
KR20220068024A (en) System for providing insurance information using artificial intelligence and personal health records and method thereof
KR20030026693A (en) A bond repayment transit system on the base of Internet and transitting method thereof
Vian et al. A blockchain profile for medicaid applicants and recipients
AU2020101898A4 (en) MHOC- Blockchain Technology: Medicine and Healthcare Observation Care using Blockchain Technology
US20220005032A1 (en) System and method for online transactions using cryptographic digital tokens
JP6046793B1 (en) Bank system, method and program executed by bank system
WO2023188136A1 (en) System, distribution control server, distribution control server control method, and storage medium
JP2007200278A (en) Child-rearing environment support system
Frisse State and community-based efforts to foster interoperability
KR102151706B1 (en) Blood donation transfer system based on blockchain
WO2023243015A1 (en) System and method
WO2023188135A1 (en) System, distribution control server, control method for distribution control server, and recording medium
WO2023242933A1 (en) System and method
WO2024009336A1 (en) System and method
WO2023242961A1 (en) Server device, method for controlling server device, and storage medium
JP4969035B2 (en) Insurance business management system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22935281

Country of ref document: EP

Kind code of ref document: A1