Intermediary devices, systems and computer programs
Through the repeated confirmation mechanism of the intermediary device, the financing plan is determined, which solves the problems of repeated purchases and traffic increase by data utilities when multiple personal data management parties collect data, and achieves more efficient data raising and reduces repeated purchases.
Patent Information
- Application Number
- CN202080020197.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-10-15
- Filing Date
- 2020-03-10
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-03-10
AI Technical Summary
When data users raise personal data from personal data management, it is difficult for data users to grasp the managed data situation, resulting in increased workload and increased traffic, and overlapping purchases may occur.
An intermediary device is provided, which includes a request acquisition unit, a repeated confirmation acquisition unit, a determination unit and a acquisition and sending unit, which determines a collection plan through repeated confirmation information, reduces the communication volume of the data user, and avoids repeated purchases.
It is possible to make it easier to raise personal data when the same person stores data to multiple personal data management parties, reduces the traffic of data utilities, and suppresses repeated purchases and data bias.
Smart Images

Figure CN113544726B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This international application claims the benefit of Japanese Patent Application No. 2019-043674 filed in the Japan Patent Office on March 11, 2019, Japanese Patent Application No. 2019-188985 filed in the Japan Patent Office on October 15, 2019, and Japanese Patent Application No. 2019-188986 filed in the Japan Patent Office on October 15, 2019, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present disclosure relates to an intermediary device that mediates personal data transactions between a data user and a personal data manager, and a computer program that enables a computer to function as the intermediary device. Background Art
[0004] A personal data manager who manages personal data is known. An example of a personal data manager is an information repository. The individual who deposits personal data communicates policies on data utilization to the personal data manager, and the personal data manager determines whether to provide the data to a third party based on the notified policies. In addition, Patent Document 1 discloses an information processing system, the purpose of which is to prevent the leakage of personal information from an information processing device held by an information repository where data is deposited.
[0005] Prior art literature
[0006] Patent Literature
[0007] Patent Document 1: Japanese Patent No. 6342094 Summary of the invention
[0008] Problem that the invention aims to solve
[0009] Furthermore, it is considered that when a personal data user such as a company (hereinafter referred to as a data user) collects personal data from a personal data manager, the personal data manager is notified of the conditions for the personal data required by the data user, that is, the object conditions.
[0010] However, it is difficult for the data user to understand what personal data the personal data manager holds. Therefore, it is conceivable that the personal data manager that is the object of the inquiry does not hold enough personal data that meets the object conditions. In this case, the data user may inquire with another personal data manager and communicate again. In this case, the workload of the data user in collecting personal data increases, which in turn increases the communication volume of the data user.
[0011] In addition, it is assumed that the same person has personal data stored in multiple personal data managers. In this case, the data user or the personal data manager cannot understand which data stored in the personal data manager is the data of the same person. Therefore, when the data user collects personal data from multiple personal data managers, overlapping purchases of personal data may occur. Overlapping purchases mentioned here refer to purchasing the personal data of the same person twice through different channels. It is assumed that the data user will consider ways to collect personal data in a way that avoids the above-mentioned overlapping purchases.
[0012] One aspect of the present disclosure is to provide a technology that can not only meet the needs of data users when the same individual deposits data with multiple personal data managers, but also more easily collect the personal data needed by the data users and reduce the amount of communication performed by the data users.
[0013] Technical solutions to the problem
[0014] One scheme of the present disclosure is an intermediary device, which includes a request acquisition unit, a duplicate confirmation acquisition unit, a determination unit, and an acquisition and transmission unit. The request acquisition unit acquires request information. The duplicate confirmation acquisition unit acquires duplicate confirmation information. The duplicate confirmation information is information indicating that the first personal data managed by the first personal data manager and the second personal data managed by the second personal data manager are personal data related to the same person, wherein the second personal data manager is a personal data manager different from the first personal data manager. The determination unit determines a fundraising plan and / or delivery data based on the duplicate confirmation information. The fundraising plan shows conditions related to personal data raised from multiple personal data managers including the first personal data manager and the second personal data manager. The delivery data is data generated based on personal data raised from multiple personal data managers, and is data sent to a user device owned by a data user. The acquisition and transmission unit acquires personal data according to the fundraising plan determined by the determination unit, and / or sends the delivery data determined by the determination unit to the user device.
[0015] According to the above configuration, personal data is collected according to the collection scheme determined based on the duplicate confirmation information. And / or the delivery data determined based on the duplicate confirmation information is sent to the user device. Therefore, it is possible to meet the needs of the data user when the same person deposits data with multiple personal data managers. In addition, since the intermediary device collects data from multiple personal data managers on behalf of the data user, it is easier to collect the personal data required by the data user, and the communication volume of the data user can be reduced.
[0016] In one aspect of the present disclosure, the determination unit may determine the fundraising plan based on the duplicate confirmation information.
[0017] According to the above configuration, personal data is collected according to the collection plan determined based on the duplicate confirmation information. Therefore, it is possible to meet the needs of the data user when the same individual deposits data with multiple personal data managers.
[0018] In one aspect of the present disclosure, the determination unit may determine a solicitation scheme of soliciting either the first personal data or the second personal data indicated by the duplicate confirmation information as personal data relating to the same person.
[0019] According to the above configuration, it is possible to suppress duplicate purchase of personal data concerning the same person and having the same content from a plurality of personal data management parties.
[0020] In one aspect of the present disclosure, the determination unit may determine a procurement scheme of procurement of the cheaper one of the first personal data and the second personal data.
[0021] According to the above configuration, duplicate purchases of personal data concerning the same person and having the same content can be suppressed, and the data user can purchase personal data at a lower price.
[0022] In one aspect of the present disclosure, the determination unit may determine a solicitation scheme of soliciting both the first personal data and the second personal data which are indicated by the duplicate confirmation information as personal data related to the same person.
[0023] According to the above configuration, when the same person deposits personal data having different contents with the first personal data manager and the second personal data manager, personal data of the same person can be collected from a plurality of personal data managers.
[0024] In one aspect of the present disclosure, the duplicate confirmation acquisition unit may acquire the duplicate confirmation information from an external device that manages the duplicate confirmation information or is capable of generating the duplicate confirmation information.
[0025] According to the above configuration, the intermediary device can easily acquire duplication confirmation information reflecting the latest duplication status of personal data. Furthermore, the intermediary device can easily determine a procurement plan based on the latest duplication status.
[0026] In one aspect of the present disclosure, the mediation device may further include a storage unit configured to store the duplicate confirmation information. The duplicate confirmation acquisition unit may acquire the duplicate confirmation information from the storage unit.
[0027] According to the above configuration, even if data is not exchanged between the intermediate device and the external device that manages the duplicate confirmation information, the intermediate device can obtain the duplicate confirmation information, thereby reducing the communication volume of the intermediate device.
[0028] In one embodiment of the present disclosure, each of the multiple personal data managers can assign specified identification information, i.e., registered identification information, to an individual whose personal data is stored at the personal data manager or the personal data of the individual. The duplicate confirmation information can be the following information: the registered identification information of the first personal data manager and the second personal data manager related to the same person.
[0029] According to the above configuration, when multiple personal data managers manage personal data related to the same person with different registration identification information, the intermediary device can grasp which personal data is related to the same person. Therefore, the intermediary device can determine the fundraising plan based on the grasped result.
[0030] In one aspect of the present disclosure, the duplicate confirmation acquisition unit may acquire similarity information as the duplicate confirmation information, where the similarity information indicates similarities between a plurality of personal data acquired from a plurality of information repositories.
[0031] According to the above configuration, even if data is not exchanged between the intermediate device and the external device that manages the duplicate confirmation information, the intermediate device can obtain the duplicate confirmation information, thereby reducing the communication volume of the intermediate device.
[0032] In one aspect of the present disclosure, the personal data manager may be an information repository.
[0033] One solution of the present disclosure is a system, which includes the intermediary device, and may include a notification information acquisition unit and a notification information sending unit. The notification information acquisition unit is configured to acquire notification information corresponding to personal data acquired by the acquisition and sending unit. The notification information is information notified to an individual whose personal data is stored in a personal data management party. The notification information sending unit is configured to send the notification information acquired by the notification information acquisition unit.
[0034] According to the above configuration, the notification information is sent using the personal data acquired from the personal data manager, so that notification information suitable for the individual can be sent to the individual who deposited the personal data.
[0035] Another aspect of the present disclosure is a computer program that causes a computer to function as the mediation device. According to the above configuration, the same effects as those of the mediation device can be obtained. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1It is a diagram showing the configuration of the procurement system according to the first embodiment.
[0037] Figure 2 This is a block diagram showing the hardware configuration of the mediation device according to the first to fifth embodiments.
[0038] Figure 3 This is a block diagram showing the functional structure of the mediation device according to the first embodiment.
[0039] Figure 4 This is a flowchart of the data collection process according to the first embodiment.
[0040] Figure 5 This is a diagram for explaining request information.
[0041] Figure 6 This is a diagram for explaining a metadata request for a first information repository according to a first embodiment.
[0042] Figure 7 This is a diagram for explaining the metadata request of the first embodiment directed to the second information repository.
[0043] Fig. 8A is a diagram showing basic data of the classification table of the first information base; Figure 8B This is a diagram showing the classification table basic data of the second information base.
[0044] Fig. 9 This is a diagram for explaining metadata according to the first embodiment.
[0045] Fig.10 This is a diagram for explaining an example of the logic for determining a plan for collecting personal data.
[0046] Fig.11 This is a diagram for explaining a data request to the first information base.
[0047] Fig.12 This is a diagram for explaining a data request to the second information repository.
[0048] Fig.13 A diagram for explaining delivery data from a repository.
[0049] Fig.14 is a diagram used to illustrate a standard dictionary.
[0050] Fig.15 This is a diagram for explaining the data conversion dictionary of the first information base.
[0051] Fig.16A is a diagram showing delivery data from a first information repository; Fig. 16B This is a diagram showing delivery data from the second information repository.
[0052] Fig.17 This is a diagram showing the delivered data after conversion from the first information repository.
[0053] Fig.18 It is a diagram showing the delivered data after conversion from the second information repository.
[0054] Fig.19 This is a diagram for explaining integrated data generated by integrating delivery data from each information library device.
[0055] Fig. 20 This is a block diagram showing the functional structure of the mediation device according to the second embodiment.
[0056] Fig.21 This is a flowchart showing the data collection process according to the second embodiment.
[0057] Fig. 22 It is a diagram showing the configuration of a procurement system according to a third embodiment.
[0058] Fig.23 It is a block diagram showing the hardware structure of the management side device.
[0059] Fig.24 It is a diagram for explaining the duplication management table held by the management device 9.
[0060] Fig.25 This is a block diagram showing the functional structure of the mediation device according to the third and fourth embodiments.
[0061] Fig.26 This is a flowchart showing the data collection process in the third and fourth embodiments.
[0062] Fig. 27 It is a diagram for explaining an ID request.
[0063] Fig.28 It is a diagram for explaining ID result information.
[0064] Fig.29 It is a diagram for explaining repeated confirmation requests.
[0065] Fig.30 It is a diagram for explaining the repeated result information.
[0066] Fig.31 This is a diagram for explaining the metadata request according to the third embodiment.
[0067] Fig.32 This is a diagram for explaining a metadata request for the first information repository according to the fourth embodiment.
[0068] Fig.33This is a diagram for explaining the metadata request of the fourth embodiment for the second information repository.
[0069] Fig.34 is a diagram showing integrated data in which personal data of the same person is collected.
[0070] Fig.35 This is a diagram showing a duplication status table of price information including personal data.
[0071] Fig.36 This is a block diagram showing the functional structure of the mediation device according to the fifth embodiment.
[0072] Fig.37 This is a flowchart of the data collection process according to the fifth embodiment.
[0073] Fig.38 This is a diagram showing the configuration of a procurement system according to a sixth embodiment.
[0074] Fig.39 This is a block diagram showing the hardware structure of an apparatus for distributing advertisements.
[0075] Fig.40 is a flow chart of the advertisement distribution process.
[0076] Fig.41 This is a flowchart of the data collection process in the seventh and eighth embodiments.
[0077] Fig.42 This is a diagram for explaining the metadata request of the seventh embodiment.
[0078] Fig.43 This is a diagram showing the delivery data from the first information repository that has been anonymized.
[0079] Fig.44 This is a diagram for explaining the metadata request in the eighth embodiment.
[0080] Fig.45 This is a diagram showing the delivery data from the first information base after statistical informatization has been performed.
[0081] Fig.46 This is a block diagram showing the functional structure of the mediation device according to the ninth embodiment.
[0082] Fig.47 This is a flowchart of the data collection process according to the ninth embodiment.
[0083] Fig.48 This is a diagram showing the converted delivery data from the first information repository in the ninth embodiment.
[0084] Fig.49This is a diagram showing the converted delivery data from the second information repository in the ninth embodiment.
[0085] Fig.50 The diagram shows a similarity matrix indicating the similarity between a plurality of personal data.
[0086] Fig.51 : is a graph showing the relationship between the similarity threshold and the number of successful associations.
[0087] Fig.52 FIG. 1 is a diagram showing a coordinate space in which personal data is expressed as data points.
[0088] Fig.53 2 is a diagram showing that the relationship between the similarity threshold and the number of association successes is expanded into multiple dimensions.
[0089] Description of Reference Numerals
[0090] 1…collection system; 2…user device; 2a…data user;
[0091] 3, 7, 8, 11, 12…intermediary device; 4-6…information base device; 4a-6a…information base;
[0092] 9…management device; 9a…registration management party; 33, 73, 83, 113…control unit;
[0093] 331 ... a request acquisition unit; 332 ... a metadata request generation unit; 333 ... a metadata request transmission unit;
[0094] 334 ... metadata receiving unit; 335 ... condition sorting unit; 336 ... fundraising plan determination unit;
[0095] 337 ...data request generating unit; 338 ...data request sending unit; 339 ...data receiving unit;
[0096] 340 ...form processing unit; 341 ...data transmission unit; 731 ...metadata acquisition unit;
[0097] 732 ...update processing unit; 831 ...ID request generating unit; 832 ...ID request sending unit;
[0098] 833 ...ID receiving unit; 834 ...duplicate confirmation generating unit; 835 ...duplicate confirmation sending unit;
[0099] 836 ... repeated confirmation receiving unit; 931 ... repeated confirmation obtaining unit; 932 ... update processing unit; 1231 ... similarity determination unit. DETAILED DESCRIPTION
[0100] Hereinafter, embodiments for implementing the present disclosure will be described with reference to the drawings.
[0101] [1. First embodiment]
[0102] [1-1. Overall composition]
[0103] Figure 1 The procurement system 1 shown includes a user device 2 , an intermediary device 3 , and a plurality of information library devices 4 to 6 .
[0104] The user device 2 is a device owned by a data user 2a that uses personal data. The data user 2a is a company or the like that uses personal data to increase profits.
[0105] Here, the personal data described in this embodiment refers to all information about an individual, regardless of whether it is personally identifiable. Personal data includes personal information that can determine and identify an individual. The personal information described here is, for example, the "personal information" stipulated in Article 2, Paragraph 1 of the Personal Information Protection Act of Japan. In addition to information that can identify an individual through the information itself, personal information also includes information that can be compared with other information and thereby identify the individual. As personal data other than personal information, the individual's location information or purchase information, IP address, Internet browsing history and other information accumulated on the company or the network can be listed. In addition, as personal data other than personal information, data about the individual's actions or status that has been processed so that it cannot be associated with the individual can also be listed.
[0106] The user device 2 is connected to the mediation device 3 via a network such as the Internet or a dedicated wireless / wired communication line network.
[0107] The intermediary device 3 is a device for making a request for personal data from the information base devices 4 to 6 on behalf of the data user 2a, and for acquiring personal data and delivering it to the data user 2a according to conditions suitable for the data user 2a. The intermediary device 3 is, for example, owned by a business operator that mediates the transaction of personal data between the data user 2a and the information base 4a to 6a. The intermediary device 3 is connected to the user device 2 and the information base devices 4 to 6 via a network such as the Internet or a dedicated wireless / wired communication line network. The hardware structure and functions of the intermediary device 3 will be described in detail later.
[0108] The information base devices 4 to 6 are respectively stored in information bases 4a to 6a. The information bases 4a to 6a are responsible for managing personal data deposited by individuals and providing the personal data to third parties such as companies.
[0109] The information base devices 4 to 6 store personal data stored by individuals via information processing terminals 11 to 17 such as smartphones, tablet terminals, and personal computers owned by individuals. The information base devices 4 to 6 are connected to the intermediary device 3 and the information processing terminals 11 to 17 via a network such as the Internet or a dedicated wireless / wired communication line network. As described later, various information is exchanged between the information base devices 4 to 6 and the intermediary device 3, and personal data is delivered to the data user 2a via the intermediary device 3.
[0110] In addition, Figure 1 Only three information base devices 4 to 6 are shown in the figure, but the intermediary device 3 can generally exchange data such as personal data with information base devices other than the three.
[0111] [1-2. Mediation device]
[0112] Next, refer to Figure 2 The hardware configuration of the intermediary device 3 is described below. The intermediary device 3 includes a communication unit 31 , a storage unit 32 , and a control unit 33 .
[0113] The communication unit 31 is a communication interface for connecting the intermediary device 3 to the network. The intermediary device 3 can communicate data with the user device 2 and the information library devices 4 to 6 by wire or wireless via the communication unit 31. In addition, the intermediary device 3 can also be connected to the Internet via the communication unit 31 and communicate data with external devices via the Internet.
[0114] The storage unit 32 stores various data.
[0115] The control unit 33 is composed of a well-known microcomputer having a semiconductor memory such as a CPU 33a, a RAM, a ROM, and a flash memory (hereinafter referred to as a memory 33b). The various functions of the control unit 33 are realized by executing a program stored in a non-transfer physical recording medium by the CPU 33a. In this example, the memory 33b corresponds to a non-transfer physical recording medium storing a program. In addition, a method corresponding to the program is executed by executing the program. In addition, the number of microcomputers constituting the control unit 33 can be one or more.
[0116] The control unit 33 performs the following operations by executing a program through the CPU 33a. Figure 4 The control unit 33 performs the data collection process as shown. Figure 3The request acquisition unit 331, metadata request generation unit 332, metadata request transmission unit 333, metadata reception unit 334, condition arrangement unit 335, procurement plan determination unit 336, data request generation unit 337, data request transmission unit 338, data reception unit 339, format processing unit 340, and data transmission unit 341 shown in the figure function. The method for realizing the functions of the above elements 331 to 341 constituting the control unit 33 is not limited to software, and the functions of some or all of the above elements may be realized by hardware formed by combining logic circuits and analog circuits.
[0117] The following first refers to Figure 3 The functions of the elements 331 to 341 are briefly described. Figure 4 The flowchart of FIG. 3 describes the function of each element 331 to 341 in detail.
[0118] <Request Acquisition Section>
[0119] The request acquisition unit 331 receives request information from the user device 2 via the communication unit 31. The request information is information including conditions of personal data required by the data user 2a, that is, object conditions. A specific example of the request information will be described later.
[0120] <Metadata Request Generating Unit>
[0121] The metadata request generation unit 332 generates a metadata request to be sent to the information library devices 4 to 6 based on the request information received by the request acquisition unit 331. The metadata request mentioned here is information for requesting metadata from the information library devices 4 to 6. The metadata mentioned here refers to information showing the attributes of personal data that matches the object conditions contained in the request information in the personal data held by the information libraries 4a to 6a. The attributes of personal data mentioned here refer to the attributes of the individual involved in the personal data, such as the individual's age, gender, etc. The attributes of personal data can of course also be attributes of the individual other than age and gender. In other words, the attributes of personal data are the various data items contained in the personal data that represent the various attributes of the individual, such as age and gender. That is, the attributes of personal data refer to the data items of personal data.
[0122] In this embodiment, metadata indicates a data summary of all or part of the personal data that meets the target condition and is stored in the information base. The data summary here may be, for example, a part of the attributes of the personal data, statistical information related to each attribute of the personal data, etc.
[0123] Metadata is information indicating what attributes of personal data constitute all or part of the personal data that meets the target conditions and is held by the information repository. Specifically, as described below, metadata includes information on statistics of all or part of the personal data that meets the target conditions and is held by the information repository. Specific examples of metadata requests and metadata will be described below.
[0124] In the present embodiment, the data formats that can be processed by the library devices 4 to 6 are different from each other. Therefore, the metadata request generation unit 332 generates metadata requests for the library devices 4 to 6 according to the data formats that can be processed by the library devices 4 to 6.
[0125] <Metadata Request Transmitting Unit>
[0126] The metadata request transmission unit 333 transmits the metadata request generated by the metadata request generation unit 332 to the information library devices 4 to 6 via the communication unit 31. The information library devices 4 to 6 receiving the metadata request transmit metadata to the intermediary device 3 as a response to the metadata request.
[0127] <Metadata Receiving Unit>
[0128] The metadata receiving unit 334 receives metadata from the information library devices 4 to 6 via the communication unit 31 .
[0129] <Conditional Arrangement Department>
[0130] The condition organizing unit 335 organizes the transaction conditions based on the metadata received from the information library devices 4 to 6 .
[0131] <Raising Plan Determination Department>
[0132] The fundraising plan determination unit 336 determines a fundraising plan suitable for the data user 2a based on the metadata received by the metadata receiving unit 334. The fundraising plan described here shows the conditions related to the personal data collected from the personal data that meets the target conditions held by the information library devices 4 to 6. That is, personal data that meets the conditions shown in the fundraising plan is collected (that is, purchased) from the information library devices 4 to 6. The determination logic of the fundraising plan will be explained later.
[0133] <Data Request Generating Unit>
[0134] The data request generation unit 337 generates a data request according to the fundraising plan determined by the fundraising plan determination unit 336. The data request is data for requesting personal data from the information library devices 4 to 6. The data request generation unit 337 generates a data request for each of the information library devices 4 to 6 according to the data format that can be processed by each of the information library devices 4 to 6. A specific example of the data request will be described later.
[0135] <Data Request Transmitting Section>
[0136] The data request transmission unit 338 transmits the data request generated by the data request generation unit 337 to the library devices 4 to 6 via the communication unit 31 .
[0137] <Data Receiving Section>
[0138] The data receiving unit 339 receives the delivery data from the information library devices 4 to 6 that have received the data request via the communication unit 31. The delivery data includes the personal data specified in the data request. A specific example of the delivery data will be described later.
[0139] <Format Processing Section>
[0140] The format processing unit 340 adjusts the data format of the delivered data received from the plurality of information library devices 4 to 6 into a common data format and integrates the data into one data, thereby generating integrated data. A specific example of the integrated data will be described later.
[0141] <Data Transmission Section>
[0142] The data transmission unit 341 transmits the integrated data generated by the format processing unit 340 to the user device 2 via the communication unit 31. Thus, the personal data collected from the information repositories 4a to 6a is delivered to the data user 2a.
[0143] [1-3. Processing]
[0144] Next, refer to Figure 4 The flowchart of FIG. 3 illustrates the data collection process executed by the control unit 33 of the intermediary device 3. The data collection process is started by receiving request information from the user device 2 via the communication unit 31. In addition, if the request information is received from the data user 2a, the received request information is stored in the storage unit 32.
[0145] <s101>
[0146] In S101, the request acquisition unit 331 acquires the request information from the data user 2a from the storage unit 32. The request information of this embodiment includes Figure 5 The items shown in FIG. 1 are as follows. That is, the request information includes a timestamp, a transaction ID, a statement type, a destination, a transmission source, and statement content. The statement type is data indicating which type of data the information belongs to, such as request information, metadata request, or metadata.
[0147] The sentence content includes information on budget, remuneration, object conditions, request items, distribution statistics axis, utilization organization, utilization purpose, and utilization conditions.
[0148] The budget information includes information on the budget amount that the data user 2a can pay for the transaction and information indicating the fee settlement method of the data user 2a.
[0149] The remuneration information is information about the remuneration paid by the data user 2a to the individual who provided the personal data. The remuneration information includes the form of remuneration, the issuer of remuneration, the time of remuneration issuance, the region where special benefits related to remuneration can be used, the effective time of remuneration, and the expiration time.
[0150] The object condition is a condition of personal data required by the data user 2a. For example, the object condition is a condition for specifying personal attributes (such as gender, age, habits, etc.) of personal data. When the data user 2a requires multiple personal data with different conditions, the object conditions included in the sentence content are also multiple. In addition, the sentence content includes the number of pieces of personal data that the data user 2a needs for each object condition that meets the object condition.
[0151] For example, in Figure 5 In the example, the first object condition is: the gender of the individual involved in the personal data is male and the number of times the individual browsed the recipe website in the last three months is more than 3 times. In addition, the number of personal data that meets this object condition required by data user 2a is 1000. The second object condition is: the gender of the individual involved in the personal data is female and the number of times the individual browsed the recipe website in the last three months is more than 7 times. In addition, the number of personal data that meets this object condition required by data user 2a is 1000.
[0152] The requested items are items of personal data that the data user 2a wishes to be delivered (for example, gender, age group, prefecture of residence, etc.).
[0153] The distribution statistics axis specifies a portion of the items of personal data included in the metadata sent from the information library devices 4 to 6. That is, as described later, the metadata sent from the information library devices 4 to 6 includes a list (i.e., a list) of all or a portion of the personal data that meets the object conditions and is held by the information libraries 4a to 6a. The list includes a portion of the items of the personal data and the data price of the personal data for each personal data ID. In other words, the portion of the personal data items mentioned here are a portion of the attributes of the individual involved in the personal data, such as the unmarried rate, age group, etc. The distribution statistics axis specifies the above-mentioned portion of the items of personal data included in the list. In addition, in the present embodiment, the attributes of the personal data included in the distribution statistics axis are set to attributes other than the attributes specified by the object conditions.
[0154] The information on the use organization, use purpose, and use conditions indicates the use organization, use purpose, and use conditions of personal data. The information on the use organization includes, for example, the legal entity number, name, address, country, industry, etc. of the use organization. The information on the use purpose includes, for example, the type of use (customer analysis, direct mail advertising, etc.) and individual use purpose. Individual use purposes include, for example, customer information expansion, statistics creation, access to the source of personal data, advertising distribution, etc.
[0155] The request acquisition unit 331 receives the request information from the user device 2 .
[0156] <s102>
[0157] Next, in S102, the metadata request generation unit 332 generates a metadata request based on the request information received in S101. A metadata request is generated for each of the information repositories 4a to 6a that are personal data providers. Specifically, Figure 6 An example of a metadata request for the first information repository 4a is shown. Figure 7 An example of a metadata request to the second information repository 5a is shown. Figure 6 as well as Figure 7 The metadata requests shown all contain the same items.
[0158] Specifically, the metadata request includes a timestamp, a transaction ID, a statement type, a reference transaction ID, a destination, a transmission source, and statement content. The reference transaction ID is the request information received in S101, in other words, the transaction ID of the request information about the metadata request.
[0159] The sentence content includes information on remuneration, subject conditions, request items, distribution statistics axis, use organization, use purpose, and use conditions. The information included in the sentence content is the same as that in the case of request information.
[0160] Here, in this embodiment, the data formats that can be processed by each of the library devices 4 to 6 are different. Therefore, the metadata request is generated in accordance with the data format that can be processed by the library devices 4 to 6 of the transmission destination.
[0161] For example, in the data format that can be processed by the first information library device 4, the variable representing the gender of the individual involved in the personal data is "Gender", and the meaning of "the individual's gender is male" is associated with the value "1" stored in the variable. In addition, the meaning of "the individual's gender is female" is associated with the value "2" stored in the variable "Gender".
[0162] On the other hand, for example, in the data format that the second information library device 5 can process, the variable representing the gender of the individual involved in the personal data is "gender", and the meaning of "the individual's gender is male" is associated with the value "male" stored in the variable. In addition, the meaning of "the individual's gender is female" is associated with the value "female" stored in the variable "gender".
[0163] Therefore, the metadata request generation unit 332 generates a request for metadata in the following manner: Figure 6 In the metadata request to the first information library device 4 shown in the figure, the condition "the gender of the individual involved in the personal data is male" in the item of the target condition is specified in a data format such as "Gender=1".
[0164] On the other hand, the metadata request generation unit 332 generates a request for metadata in the form of Figure 7 In the metadata request to the second information library device 5 shown in the figure, the condition "the gender of the individual involved in the personal data is male" in the target condition item is specified in a data format such as "gender = male".
[0165] In addition, based on Fig. 8A as well as Figure 8B The metadata request of each information library device 4 to 6 is created based on the classification table basic data shown. The classification table basic data is information used to convert each item contained in the metadata request, etc. into a data format that each information library device 4 to 6 can process. In the classification table basic data of a certain information library device, the "variable name", "value" and "meaning" described in the data format that the information library device can process are set to correspond to each other. In this embodiment, the classification table basic data of each information library device 4 to 6 that is the transaction object of the intermediary device 3 is pre-stored in the storage unit 32 of the intermediary device 3. However, the location of the classification table basic data is not limited to this. For example, when generating a metadata request, the intermediary device 3 can send information requesting the classification table basic data to each information library device 4 to 6, and obtain the classification table basic data of each information library device 4 to 6 as its response signal. That is, the classification table basic data can be obtained at the timing of generating the metadata request.
[0166] <s103>
[0167] Next, in S103, the metadata request transmission unit 333 transmits the metadata request generated in S102 to the information library devices 4 to 6 via the communication unit 31. The information library devices 4 to 6 receiving the metadata request transmit metadata to the intermediary device 3 as response information to the metadata request.
[0168] <s104>
[0169] Next, in S104, the metadata receiving unit 334 receives metadata from each of the library devices 4 to 6 via the communication unit 31. The metadata is described in a data format that can be processed by each of the library devices 4 to 6.
[0170] The metadata of this implementation includes Fig. 9 The items shown. Fig. 9 The metadata received from the second information library device 5 is shown.
[0171] The metadata includes a timestamp, a transaction ID, a sentence type, a reference transaction ID, a destination station, a transmission source, classification code basic data, and sentence content. The reference transaction ID is a transaction ID of a metadata request related to the metadata, in other words, a transaction ID of a metadata request sent to the information library device that is the transmission source of the metadata. The classification code basic data is information for specifying the classification code basic data related to the information library device that is the transmission source of the metadata.
[0172] The sentence content includes information about the subject, i.e., subject information. The subject information includes the subject conditions included in the request information and the number of all or part of the personal data in the information base that meets the subject conditions. In addition, the subject information indicates what attributes the personal data that meets the subject conditions consists of.
[0173] Specifically, the subject information includes the requested item statistics. The requested item statistics are statistics (mean, variance, skewness, median, etc.), maximum and minimum values, etc. of the personal data related to each attribute specified in the requested item. In addition, the subject information includes the variance-covariance matrix, information on the data price distribution of the personal data, and information on other multivariate statistics.
[0174] Here, the information of data price distribution indicates the data price of personal data included in each category when personal data is classified according to the attribute specified by the distribution statistical axis. For example, the attributes "single married, age group, whether or not a magazine was purchased in the past three months" are specified in the distribution statistical axis. In this case, the information of data price distribution may include the data price of personal data included in the category "single married: single; age group: 30; whether or not a magazine was purchased in the past three months = no" "260, 280, 290, ...".
[0175] In the present embodiment, it is assumed that the number of pieces of information on personal data contained in the metadata is greater than the number of pieces of personal data specified in the request information. In more detail, it is assumed that the number of pieces of information on personal data that meet a certain object condition contained in the metadata is greater than the number of pieces of personal data that meet the object condition specified in the request information. This is because: when selecting the number of personal data specified in the request information based on the metadata, a fundraising scheme suitable for the data user 2a is selected from a variety of fundraising schemes after studying a variety of personal data selection methods (i.e., fundraising schemes). However, the number of personal data whose attributes are displayed by metadata is not limited to this, and the number of personal data may, for example, be the same as the number of personal data specified in the request information.
[0176] <s105>
[0177] Next, in S105, the condition arrangement unit 335 arranges the transaction conditions from the metadata that conforms to the data format of each information library device 4 to 6. Specifically, the condition arrangement unit 335 uses the classification table basic data of each information library device 4 to 6 to adjust the metadata that conforms to the data format of each information library device 4 to 6 into a common data format, thereby arranging the transaction conditions.
[0178] Furthermore, the condition organizing unit 335 generates the following information based on the metadata received from each of the information library devices 4 to 6 in S104: Fig.10 The list shown by the dotted line (hereinafter referred to as the metadata list). The metadata list is data that establishes a correspondence between the ID of personal data, the data source, the attributes specified by the distribution statistics axis, and the data price. The data source is information used to identify which information library the data comes from. As described above, in this embodiment, the number of data items included in the generated metadata list is greater than the number of personal data items specified in the request information. In addition, Fig.10 "1st" in the "Data Source" column of the metadata list indicates the first information library 4a, and "2nd" indicates the second information library 5a.
[0179] <s106>
[0180] Next, in S106, the fundraising plan determination unit 336 determines a fundraising plan suitable for the data user 2a based on the metadata list generated in S105. In the present embodiment, the fundraising plan determination unit 336 determines the fundraising plan based on the data price of each personal data held by the information library devices 4 to 6 and the budget amount specified by the data user 2a. Then, while paying attention to the attributes specified by the distribution statistical axis, the fundraising plan determination unit 336 determines the fundraising plan based on the reproducibility of the distribution of the personal data shown in the metadata (hereinafter referred to as the original data distribution). That is, the fundraising plan determination unit 336 determines the fundraising plan within the range of the budget amount of the data user 2a in such a way that the data distribution of the personal data raised through the fundraising plan is close to the original data distribution.
[0181] Below, refer to Fig.10 The method for determining the fundraising plan is explained in detail. Fig.10 In the example, for simplicity, a metadata list consisting of 100 data is considered. In this example, the request information from the data user 2a contains only one object condition. For example, the request information contains only Figure 5 The target condition 1 is "the individual involved in the personal data is male and has visited the recipe website more than 3 times in the past three months." Fig.10 The 100 data items are data that meet the target conditions. Furthermore, the number of personal data items that meet the target conditions required by the data user 2a is 40 items. That is, 40 data items are selected from the 100 data items. Furthermore, the budget amount of the data user 2a is 11,000 yen.
[0182] The cheapest way to raise the total amount of data price is plan A, that is, sort the data in ascending order of data price and buy the data from No. 1 to No. 40. Fig.10 In the data that was purchased in the fundraising plan, a flag of "1" is marked, and a flag of "0" is marked for the data that was not purchased. The total price of the purchased data in Plan A is 10,570 yen. However, for example, the ratio of unmarried to married people is 59:41 (≒3:2) in the original 100 data (hereinafter referred to as the original data), while it is 12:28 (≒1:2.5) in Plan A, which deviates from the distribution of the original data. In addition, Fig.10 In the data, the value corresponding to unmarried persons is "0" and the value corresponding to married persons is "1". Thus, there is a concern that other items of personal data that can actually be collected do not reproduce the distribution of the original data. Therefore, for other types of purchased data with different details (such as Fig.10 The total amount of data price and the deviation from the distribution of metadata, i.e., the original data distribution, are also studied, and the deviation from the original data distribution can be evaluated in the same manner as in Scheme A. In addition, the deviation from the original data distribution can be evaluated using an indicator such as KL (Kullback-Leibler)-divergence. Fig.10 In the example, the fundraising plan that deviates the least from the original data distribution is Plan C, but the total amount of the data price of Plan C is 12,420 yen, which exceeds the budget. Therefore, Plan B, which deviates the least from the original data distribution within the budget amount, is determined as the fundraising plan. As described above, the fundraising plan determination logic of the present embodiment is to determine the fundraising plan that deviates the least from the original data distribution within the budget amount from multiple fundraising plans. In addition, the case where the request information contains only one object condition is illustrated above, but the same determination logic applies to the case where the request information contains multiple object conditions. In addition, when the request information contains multiple object conditions, in order not to change the number of items of each object condition specified in the request information and change the data to be raised, multiple plans are studied.
[0183] <s107>
[0184] Next, in S107, the data request generator 337 generates a data request for personal data according to the procurement plan determined by the procurement plan determiner 336. The data request generator 337 generates a data request for each of the information library devices 4 to 6 in a format that conforms to the data format that each of the information library devices 4 to 6 can process.
[0185] Fig.11 An example of a data request to the first information repository 4a is shown. Fig.12 Examples of data requests to the second information repository 5a are shown. These data requests all include the same items.
[0186] Specifically, the data request includes a timestamp, a transaction ID, a statement type, a reference transaction ID, a destination, a transmission source, and statement content. The reference transaction ID is a transaction ID of metadata related to the data request, in other words, a transaction ID of metadata received from the information library device that is the transmission target of the data request.
[0187] The sentence content includes the subject information corresponding to each subject condition. The subject information includes the condition sentence, the number of items, the payment amount, and the purchase data.
[0188] The conditional statement expresses the corresponding target condition. The number of items and the payment amount express the number of items of personal data collected from the information library device that is the destination of the data request and the payment amount for the corresponding target condition.
[0189] The purchased data specifies the personal data collected from the information base device to which the data request is sent. Specifically, the purchased data specifies the personal data collected based on each attribute specified by the statistical distribution axis and the data price.
[0190] In addition, the sentence content includes request items, which are items of personal data that the data user 2a wishes to deliver.
[0191] The data request generation unit 337 generates data requests for each of the library devices 4 to 6 using the classification code basic data of each of the library devices 4 to 6 in a manner conforming to the data format that can be processed by each of the library devices 4 to 6 .
[0192] <s108>
[0193] Next, in S108 , the data request transmission unit 338 transmits the data request generated in S107 to the information library devices 4 to 6 via the communication unit 31 .
[0194] <s109>
[0195] Next, in S109, the data receiving unit 339 receives the following data from the information library devices 4 to 6 that have received the data request: Fig.13 The delivery data shown contains the personal data specified by the data request.
[0196] Specifically, the delivery data includes a timestamp, a transaction ID, a statement type, a reference transaction ID, a destination, a transmission source, and statement content. The reference transaction ID is a transaction ID of a data request related to the delivery data, in other words, a transaction ID of a data request sent to the information library device as the transmission destination of the delivery data.
[0197] The sentence content includes the subject information corresponding to each subject condition. The subject information includes the conditional sentence, the number of cases, and the information of the data subject. The conditional sentence and the number of cases are the same as the conditional sentence and the number of cases included in the data request. The data subject is the personal data specified by the purchase data included in the data request. The data subject includes the items specified by the request items in the items of the personal data. In addition, the sentence content includes the information of the request items.
[0198] <s110>
[0199] Next, in S110, the format processing unit 340 unifies the data format of the delivery data received from the plurality of information library devices 4 to 6. Specifically, the format processing unit 340 converts the data format of the delivery data received from each information library device 4 to 6 into a common data format. Then, the format processing unit 340 integrates the delivery data from each information library device 4 to 6 and converted into a common data format into one data. The following is a specific description.
[0200] First, when converting the data format of the delivered data from each of the information library devices 4 to 6 into a common data format, the format processing unit 340 uses Fig.14 The standard dictionary shown. The standard dictionary is stored in the storage unit 32. The standard dictionary is data that is set to correspond to each other the meanings, variable names, and values specified for each item that can be included in the personal data in the intermediary device 3. The specified variable names and values are referred to as "standard variable names" and "standard values" respectively below. The format processing unit 340 first creates a data conversion dictionary for each information library device 4 to 6 using the standard dictionary. The data conversion dictionary is data used to convert the variable names and values of the delivered data of each information library device 4 to 6 into standard variable names and standard values specified by the standard dictionary.
[0201] When creating a dictionary for data conversion, the form processing unit 340 performs Fig. 8A and Figure 8B The classification table basic data of the information base shown and Fig.14 In addition, when performing this check (i.e., matching), for example, the texts of both data in the "meaning" item can be simply matched, or the matching can be made by other methods besides this.
[0202] After checking the basic data of the classification table and the standard dictionary in the "Meaning" item, generate Fig.15 The data conversion dictionary shown is generated by establishing correspondence between the "variable name" and "value" contained in the classification table basic data, the "standard variable name" and "standard value" contained in the standard dictionary, and the "meaning". In addition, the data conversion dictionary can be generated when the data format of the delivered data from each information library device 4 to 6 is converted into a common data format, or the data conversion dictionary can be generated in advance and stored in the storage unit 32.
[0203] Then, the format processing unit 340 converts the variables and values of the delivery data sent from the library device into standard variables and standard values using the data conversion dictionary of the library device. Thus, the data format of the delivery data received from each library device 4 to 6 is converted into a common data format.
[0204] For example, using Fig.15 The data conversion dictionary of the first information library device 4 shown in FIG. Fig.16A The delivery data from the first information library device 4 is converted into Fig.17 Similarly, the data conversion dictionary of the second information library device 5 (not shown) is used to convert Fig. 16B The delivery data from the second information base 5a is converted into Fig.18 Transformed delivery data shown.
[0205] Then, the format processing unit 340 integrates the converted delivery data of each information library device 4 to 6 into one data, and generates the following data: Fig.19 In addition, when generating the integrated data, the format processing unit 340 reassigns the ID of each personal data and accumulates the delivery data of each information library device 4 to 6 in order. In addition, in the integrated data, personal data from a certain information library device and personal data from other information library devices can be distinguished from each other. For example, in Fig.19 In the integrated data shown, the ID of the personal data from the first information base 4a is labeled with "b", and the ID of the personal data from the second information base 5a is labeled with "a".
[0206] As described above, the format processing unit 340 makes the data formats of the delivered data from the plurality of library devices 4 to 6 consistent and integrates them into one data.
[0207] <s111>
[0208] Next, in S111, the data transmission unit 341 transmits the integrated data generated by the format processing unit 340 to the data user 2a.
[0209] After executing S111, the control unit 33 ends Figure 4 data collection and processing.
[0210] [1-4. Effect]
[0211] According to the first embodiment described in detail above, the following effects can be obtained.
[0212] (1a) In this embodiment, the fundraising plan determination unit 336 determines a fundraising plan suitable for the data user 2a based on the metadata received from the information library devices 4 to 6. Then, the data request transmission unit 338 transmits a data request to the information library devices 4 to 6 according to the determined fundraising plan, and the data reception unit 339 receives personal data from the information library devices 4 to 6. Furthermore, the data transmission unit 341 transmits the received personal data to the data user 2a.
[0213] Therefore, compared with the case where the data user 2a directly inquires and collects personal data from the information library devices 4 to 6 when it is difficult to grasp the personal data held by the information library devices 4 to 6, it is easier to collect personal data and the communication volume performed by the data user 2a can be reduced.
[0214] (1b) In the present embodiment, the intermediary device 3 acquires metadata from the library devices 4 to 6 held in the libraries 4a to 6a.
[0215] Here, the following configuration can be considered: the intermediary device 3 stores metadata in its own storage unit 32, and periodically updates the metadata stored in the storage unit 32, and obtains metadata from the storage unit 32. However, in this configuration, there is a case where the metadata obtained from the storage unit 32 is not updated to the latest metadata, and the fundraising plan determination unit 336 determines the fundraising plan based on the old metadata. In contrast, according to the configuration of this embodiment, since the intermediary device 3 obtains metadata from the information library devices 4 to 6, it is possible to determine the fundraising plan based on the latest metadata.
[0216] (1c) In the present embodiment, the recruitment plan determination unit 336 determines the recruitment plan based on metadata that is information indicating the attributes of personal data that meets the target condition among the personal data managed by the information repositories 4a to 6a.
[0217] Therefore, the intermediary device 3 can determine a recruitment plan based on the attributes of the personal data that meets the target conditions among the personal data managed by the information repositories 4a to 6a.
[0218] (1d) In this embodiment, when the request receiving unit 331 acquires the request information, the metadata request sending unit 333 sends a metadata request to the information library devices 4 to 6. Furthermore, the metadata receiving unit 334 receives metadata from the information library devices 4 to 6.
[0219] Therefore, when the intermediary device 3 obtains the request information from the user device 2, it makes an inquiry to the information library devices 4 to 6 and obtains the latest metadata. Therefore, it is possible to determine the procurement plan based on the latest metadata.
[0220] (1e) In this embodiment, the procurement plan determination unit 336 determines the procurement plan based on the price of each personal data stored in the information library devices 4 to 6 and the budget included in the request information. Therefore, an appropriate procurement plan can be determined according to the budget of the data user 2a.
[0221] (1f) In the present embodiment, the recruitment plan determination unit 336 determines the recruitment plan so that the attribute-based distribution of personal data recruited through the recruitment plan approaches the original data distribution indicated by the metadata.
[0222] For example, when determining a personal data collection scheme without considering the original data distribution, personal data may be collected with a distribution that deviates from the original data distribution. As a result, when the data user 2a performs statistics on specific items included in the requested items of personal data, the distribution of metadata is not reproduced, and biased results are obtained.
[0223] On the other hand, according to the configuration of this embodiment, the recruitment scheme is determined based on the reproducibility of the original data distribution, so it is possible to suppress the occurrence of data deviation when actually recruiting personal data.
[0224] In particular, in the present embodiment, it is possible to suppress the occurrence of data deviation as much as possible within the budget of the data user 2a.
[0225] (1g) In the present embodiment, the collection plan determination unit 336 determines a collection plan indicating conditions related to personal data actually collected from personal data meeting the target conditions held by the plurality of information library devices 4 to 6 based on metadata received from the plurality of information library devices 4 to 6. The data receiving unit 339 receives personal data from the plurality of information library devices 4 to 6, and the data sending unit 341 sends the personal data received from the plurality of information library devices 4 to 6 to the data user 2a.
[0226] Therefore, compared with the situation where the data user 2a directly inquires and collects personal data from the information library devices 4 to 6 when it is difficult to grasp the personal data held by the information library devices 4 to 6, it is easier to collect personal data suitable for the data user 2a from multiple information library devices 4 to 6.
[0227] (1h) In this embodiment, the format processing unit 340 unifies the data format of the personal data received from the plurality of information library devices 4 to 6 into a common data format. Furthermore, the data transmission unit 341 transmits the personal data from the plurality of information library devices 4 to 6 and whose data format has been adjusted by the format processing unit 340 to the user device 2.
[0228] Therefore, by unifying the data format into a common data format, personal data can be delivered in a data format that is easy for the data user 2a to handle.
[0229] [2. Second embodiment]
[0230] [2-1. Differences from the first embodiment]
[0231] The basic structure of the second embodiment is the same as that of the first embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the first embodiment represent the same structure, and for this, refer to the above description.
[0232] In the first embodiment described above, when the intermediary device 3 receives request information from the user device 2 , it sends a metadata request to the information library devices 4 to 6 , and receives metadata from the information library devices 4 to 6 .
[0233] In contrast, in the second embodiment, Figure 2 as well as Fig. 20 The intermediary device 7 shown in the figure has a storage unit 72, and a set of metadata (hereinafter referred to as a metadata set) is stored in the storage unit 72. The metadata set includes metadata corresponding to an arbitrary object condition. In addition, when the intermediary device 7 receives request information from the data user 2a, it obtains metadata from the storage unit 72 provided by itself, rather than obtaining metadata from the information library devices 4 to 6, which is different from the first embodiment. The second embodiment will be described in detail below.
[0234] like Figure 2 As shown, the intermediary device 7 of the second embodiment includes a communication unit 71, a storage unit 72, and a control unit 73. The hardware configuration of the above-mentioned components 71 to 73 is the same as the components 31 to 33 of the intermediary device 3 of the first embodiment. However, the data stored in the storage unit 72 is different from that of the first embodiment. Specifically, the storage unit 72 stores a metadata set related to each information base 4a to 6a.
[0235] The metadata set is a data set that can acquire metadata corresponding to any object condition that may be included in the request information. In other words, the metadata set is a data set that can acquire various information such as request item statistics and data price distribution contained in metadata corresponding to any object condition that may be included in the request information. The storage unit 72 stores a metadata set that includes metadata related to all the information repositories 4a to 6a from which the intermediary device 7 can request personal data.
[0236] Specifically, for example, the metadata set includes information such as statistics, maximum values, and minimum values related to the attributes of the personal data such as age, gender, whether single or married, and whether or not the person has purchased magazines, which are stored in all the information repositories from which the intermediary device 7 can request personal data. In addition, the metadata set also includes information about the number of personal data that meet any object condition (i.e., any combination of attributes of personal data) in all the information repositories 4a to 6a from which the intermediary device 7 can request personal data. In addition, the metadata set of a certain information repository includes information about the data price distribution of personal data that meets the object condition in any object condition. The storage unit 72 stores the above metadata set.
[0237] In this embodiment, it is assumed that the metadata set stored in the storage unit 72 is updated regularly at a predetermined frequency (for example, once a month or once a week). In addition, the dataset can be updated by various methods, for example, the update can be performed in the following manner. That is, the owner of the intermediary device 7 receives a storage medium storing a metadata set from each information repository 4a to 6a, and updates the metadata set by storing the metadata set in the received storage medium in the storage unit 72.
[0238] On the other hand, the control unit 73 performs the following operations by executing a program through the CPU 73a. Fig.21 The control unit 73 performs the data collection process as shown. Fig. 20 The request acquisition unit 331, metadata acquisition unit 731, update processing unit 732, procurement plan determination unit 336, data request generation unit 337, data request transmission unit 338, data reception unit 339, format processing unit 340, and data transmission unit 341 shown in the figure function. That is, the control unit 73 of the second embodiment functions as the metadata acquisition unit 731 and update processing unit 732 instead of the request generation unit 332, metadata request transmission unit 333, metadata reception unit 334, and condition arrangement unit 335 of the first embodiment, and the control unit 73 of the second embodiment is different from the control unit 33 of the first embodiment in this point.
[0239] <Metadata Acquisition Section>
[0240] The metadata acquisition unit 731 acquires metadata from the storage unit 72 based on the request information received by the request acquisition unit 331. Specifically, the metadata acquisition unit 731 acquires metadata about each of the information repositories 4a to 6a corresponding to the request information from the metadata set.
[0241] <Update Processing Section>
[0242] The update processing unit 732 updates the metadata set stored in the storage unit 72 .
[0243] [2-2. Processing]
[0244] Next, refer to Fig.21 The flowchart of FIG. 7 is a flowchart of the control unit 73 of the intermediary device 7 of the second embodiment, which replaces the data collection process ( Figure 4 ) and the data collection process performed. Fig.21 In the flowchart of FIG. 1 , the processing of S201, S203 to S208 (i.e., the processing other than S202 and S209) is respectively the same as that described above. Figure 4 Therefore, the description of these processes will be omitted below, and only the different S202 and S209 will be described.
[0245] <s202>
[0246] In S202 , the metadata acquisition unit 731 acquires metadata based on the request information acquired in S201 and the metadata set stored in the storage unit 72 .
[0247] <s209>
[0248] In S209, the update processing unit 732 updates the metadata set stored in the storage unit 72. For example, when the statistical information of the attributes of the personal data or the information such as the data price distribution included in the integrated data is different from the information of the metadata set stored in the storage unit 72, the update processing unit 732 updates the information of the metadata set to the information included in the delivery data.
[0249] [2-3. Effect]
[0250] According to the second embodiment described in detail above, in addition to the effects (1c) and (1e) to (1h) of the first embodiment described above, the following effects can be obtained.
[0251] (2a) In this embodiment, the recruitment plan determination unit 336 determines a recruitment plan suitable for the data user 2a based on the metadata obtained from the storage unit 72. Then, the data request transmission unit 338 receives personal data from the information library devices 4 to 6 according to the determined recruitment plan. Then, the data transmission unit 341 transmits the received personal data to the data user 2a.
[0252] Therefore, compared with a case where the data user 2a directly inquires the information library devices 4 to 6 and collects personal data when it is difficult to grasp the personal data held by the information library devices 4 to 6, it is easier to collect personal data suitable for the data user 2a.
[0253] In particular, the metadata acquisition unit 731 acquires metadata from the storage unit 72. That is, the intermediary device 7 can acquire metadata even without exchanging data with the information repositories 4a to 6a. Therefore, compared with a configuration in which metadata requests are sent to the information repositories 4a to 6a to acquire metadata, the communication volume of the intermediary device 7 can be reduced. In addition, the development cost of a system such as an API (Application Programming Interface) for performing metadata requests and sending and receiving metadata can be suppressed.
[0254] [3. Third embodiment]
[0255] [3-1. Differences from the first embodiment]
[0256] The basic structure of the third embodiment is the same as that of the first embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the first embodiment represent the same structure, and for this, refer to the above description.
[0257] In the first embodiment described above, the intermediary device 3 obtains personal data from multiple information repositories 4a to 6a. Here, it is fully conceivable that the same person deposits personal data in multiple information repositories 4a to 6a. Moreover, the information repositories 4a to 6a or the data user 2a cannot know which personal data deposited in the information repositories 4a to 6a are from the same person. Therefore, when the data user 2a requests personal data from multiple information repositories 4a to 6a, there is a case where the same personal data of the same person is purchased from different information repositories 4a to 6a. In other words, there is a case where overlapping personal data is purchased.
[0258] The third embodiment solves the problem of suppressing the overlapping purchase of the above-mentioned personal data in the following manner. That is, in the third embodiment, Fig. 22 As shown, it is assumed that there is a device (hereinafter referred to as the registration management party 9a): the device knows which person has personal data stored in which information base. And the intermediary device 8 of the third embodiment detects the individual whose personal data is stored in multiple information bases 4a to 6a by querying the device held by the registration management party 9a, that is, the management party device 9. Then, the intermediary device 8 determines a fundraising plan that does not cause overlapping purchases. The structure of the third embodiment is described in detail below.
[0259] like Fig.23 As shown, the management device 9 of the registration management 9a includes a communication unit 91, a storage unit 92, and a control unit 93.
[0260] The communication unit 91 is a communication interface for connecting the management device 9 to the network. The management device 9 can communicate data with the intermediary device 8 by wire or wireless via the communication unit 91. In addition, the management device 9 can be connected to the Internet via the communication unit 91 and communicate data with an external device via the Internet.
[0261] The storage unit 92 stores various data. In this embodiment, the storage unit 92 stores the following data: Fig.24 The duplicate management table is information in which the database ID, the database registrant ID, and the personal ID are set in correspondence with each other.
[0262] The information base ID is an ID for identifying each information base. The registration management party 9a can assign an information base ID to each information base. In this embodiment, the information base IDs of the first information base 4a, the second information base 5a, and the third information base 6a are "00001", "00002", and "00003", respectively.
[0263] The information base registrant ID is an ID assigned by each information base 4a to 6a to the individual who has deposited personal data in the information base 4a to 6a, that is, the registrant. The information base registrant ID is an ID unique to each information base 4a to 6a. In addition, each information base 4a to 6a establishes a one-to-one correspondence between the information base registrant ID of the individual who has deposited personal data and the personal data deposited by the individual and stores them. Therefore, it can also be considered that the information base registrant ID is an ID assigned to the personal data of the individual who has deposited personal data in the information base.
[0264] A personal ID is an ID that corresponds to an individual one-to-one, and is assigned to an individual by, for example, the registration management party 9a. Specifically, for example, the registration management party 9a lends a tool for generating a personal ID to each information base 4a to 6a. Then, each information base 4a to 6a can use the borrowed tool to generate a personal ID. For example, a personal ID can be an ID generated by using a hash function or the like from personal identification information when an individual registers data to the information base 4a to 6a. Specifically, for example, a hash value such as hash(surname_firstname_sex_birthday) can be used as a personal ID. Here, hash is a hash function, and the surname, firstname, sex, and date of birth of the individual who registers the data are input into surname, firstname, sex, and birthday, respectively.
[0265] In this duplication management table, personal data with the same personal ID can be determined to be personal data of the same person.
[0266] On the other hand, the control unit 93 is mainly composed of a well-known microcomputer including a CPU 93a, a RAM, a ROM, a semiconductor memory such as a flash memory (hereinafter referred to as a memory 93b).
[0267] On the other hand, Figure 2 As shown, the intermediary device 8 of the third embodiment includes a communication unit 81, a storage unit 82, and a control unit 83. The hardware configuration of these components 81 to 83 is the same as the components 31 to 33 of the intermediary device 3 of the first embodiment. However, the processing executed by the control unit 83 is partially different from that of the first embodiment.
[0268] Specifically, the control unit 83 performs the following operations by executing a program stored in the memory 83b through the CPU 83a. Fig.26 The control unit 83 performs the data collection process as shown. Fig.25 The request acquisition unit 331, ID request generation unit 831, ID request sending unit 832, ID receiving unit 833, duplicate confirmation generation unit 834, duplicate confirmation sending unit 835, duplicate confirmation receiving unit 836, metadata request generation unit 332, metadata request sending unit 333, metadata receiving unit 334, condition sorting unit 335, fundraising plan determination unit 336, data request generation unit 337, data request sending unit 338, data receiving unit 339, form processing unit 340, and data sending unit 341 function as follows. That is, the control unit 83 of the third embodiment also functions as the ID request generation unit 831, ID request sending unit 832, ID receiving unit 833, duplicate confirmation generation unit 834, duplicate confirmation sending unit 835, and duplicate confirmation receiving unit 836, which is different from the control unit 33 of the first embodiment. The following describes the functional outlines of the elements 832 to 836 and the like where there are differences. Then, with reference to Fig.26 the flowchart of
[0269] <ID request generation unit>
[0270] The ID request generation unit 831 generates an ID request to be sent to the information repository devices 4 to 6 based on the request information containing the object conditions received by the request acquisition unit 331. The ID request described here is information for requesting the information repository registrant ID related to the personal data that meets the object conditions. In this embodiment, the ID request generation unit 831 generates ID requests for each of the information repository devices 4 to 6 in the data formats that each of the information repository devices 4 to 6 can process. Specific examples of the ID request are described later.
[0271] <ID request sending unit>
[0272] The ID request sending unit 832 sends the ID request generated by the ID request generation unit 831 to the multiple information repository devices 4 to 6 via the communication unit 81. As a response to the ID request, the information repository devices 4 to 6 that receive the ID request send the ID result information to the mediation device 3. The ID result information described here is information showing the information repository registrant ID of the personal data that meets the object conditions. The ID result information described in this embodiment also includes the price information of the personal data that meets the object conditions.
[0273] <ID receiving unit>
[0274] The ID receiving unit 833 receives the ID result information from the multiple information repository devices 4 to 6 via the communication unit 81. Specific examples of the ID result information will be described later.
[0275] <duplicate confirmation generation unit>
[0276] The duplicate confirmation generating unit 834 generates a duplicate confirmation request to be sent to the management side device 9 based on the ID result information received from the plurality of information base devices 4 to 6. The duplicate confirmation request mentioned here is information for making a request to confirm whether there is personal data related to the same person among the plurality of personal data shown by the plurality of information base registrant IDs included in the ID result information. A specific example of the duplicate confirmation request will be described later.
[0277] <Repeated confirmation sending section>
[0278] The duplicate confirmation sending unit 835 sends the duplicate confirmation request generated by the duplicate confirmation generating unit 834 to the management device 9 via the communication unit 81. The management device 9 receiving the duplicate confirmation request sends duplicate result information indicating the duplicate confirmation result to the mediation device 8 as a response to the duplicate confirmation request.
[0279] <Repeated confirmation receiving unit>
[0280] The duplication confirmation receiving unit 836 receives duplication result information from the management device 9 via the communication unit 81. A specific example of the duplication result information will be described later.
[0281] <Metadata Request Generating Unit>
[0282] The metadata request generation unit 332 generates a metadata request to be sent to the information library devices 4 to 6 based on the duplication result information received by the duplication confirmation receiving unit 836 and the request information received by the request acquisition unit 331. In the present embodiment, when the personal data of the same person is managed by a plurality of information libraries, the metadata request generation unit 332 generates a metadata request for requesting the data of the same person from one of the plurality of information libraries.
[0283] Each element 333 to 341 after the metadata request transmission unit 333 is basically the same as that of the first embodiment, and thus the description thereof is omitted.
[0284] [3-2. Processing]
[0285] Next, refer to Fig.26 The flowchart of FIG. 8 is a flowchart of the control unit 83 of the intermediary device 8 of the third embodiment, which replaces the data collection process ( Figure 4 ) is used to explain the data collection process performed.
[0286] <s301>
[0287] S301 and above Figure 4 The S101 is the same as that of S101, so the description is omitted.
[0288] <s302>
[0289] Next, in S302 , the ID request generation unit 831 generates an ID request to be transmitted to the information library devices 4 to 6 based on the request information including the target condition received by the request acquisition unit 331 .
[0290] Here, the ID request includes Fig. 27 The items shown. Fig. 27 An example of an ID request for the first information base 4a is shown in FIG. Figure 6 In other words, the content of the ID request is substantially the same as that of the metadata request except that the statement type is "ID request". In particular, the ID request includes information on the object conditions contained in the request information.
[0291] In the present embodiment, the data formats that can be processed by the respective information library devices 4 to 6 are different from each other. Therefore, ID requests are generated for the respective information library devices 4 to 6 according to the data formats that can be processed by the information library devices 4 to 6 of the transmission destination.
[0292] <s303>
[0293] Next, in S303, the ID request transmitter 832 transmits the ID request generated by the ID request generator 831 to the plurality of library devices 4 to 6 via the communication unit 81. The library devices 4 to 6 receiving the ID request transmit ID result information to the intermediate device 3 as a response to the ID request.
[0294] <s304>
[0295] The ID receiving unit 833 receives ID result information from the plurality of library devices 4 to 6 via the communication unit 81. The ID result information is described in a data format that can be processed by each of the library devices 4 to 6.
[0296] The ID result information of this embodiment includes Fig.28 The items shown. Fig.28 2 shows the ID result information received from the first information base 4a.
[0297] The ID result information includes a timestamp, a transaction ID, a statement type, a reference transaction ID, a destination, a sending source, and statement content. The reference transaction ID is the transaction ID of the ID request related to the ID result information, in other words, the transaction ID of the ID request received by the information library device as the sending source of the ID result information.
[0298] The statement content contains a list of the following combinations, namely, combinations of the information base registrant ID and price of personal data that meets the object conditions indicated by the ID request. For example, in Fig.28 In the example, the combination of {1343482, 215} contained in the sentence content means that the database registrant ID of a certain personal data that meets the target condition among the personal data held by the first information database 4a is 1343482 and the price is 215 yen. The intermediary device 8 receives the following from each information database 4a to 6a: Fig.28 The ID result information is shown.
[0299] <s305>
[0300] Next, in S305 , the duplicate confirmation generating unit 834 generates a duplicate confirmation request to be transmitted to the management device 9 based on the ID result information received from the plurality of information library devices 4 to 6 .
[0301] like Fig.29 As shown, the duplicate confirmation request of this embodiment includes items such as a timestamp, a transaction ID, a statement type, a reference transaction ID, a destination station, a transmission source, and statement content.
[0302] The sentence content includes a list of the database registrant IDs received from the databases 4a to 6a and an identifier of each database (in Fig.29 , "1st information library", "2nd information library", etc. in "sentence content").
[0303] <s306>
[0304] Next, in S306, the duplicate confirmation sending unit 835 sends the duplicate confirmation request generated by the duplicate confirmation generating unit 834 to the management device 9 via the communication unit 81. The management device 9 receiving the duplicate confirmation request sends duplicate result information to the mediation device 8 as a response to the duplicate confirmation request.
[0305] <s307>
[0306] The duplication confirmation receiving unit 836 receives duplication result information from the management device 9 via the communication unit 81 .
[0307] like Fig.30 As shown, the duplication result information of this embodiment includes items such as timestamp, transaction ID, statement type, reference transaction ID, destination station, transmission source, and statement content.
[0308] The sentence content includes a combination of the database registrant IDs of the same person in each of the databases 4a to 6a.
[0309] For example, in Fig.30 In the example, the combination of (0900838, 9888100, 430981213) contained in the sentence content indicates that the database registrant ID "0900838" of the first database 4a, the database registrant ID "9888100" of the second database 5a, and the database registrant ID "430981213" of the third database 6a are the IDs of the same person.
[0310] Furthermore, upon receiving a duplicate confirmation request from the intermediary device 8, the management device 9 generates duplicate result information in the following manner. Fig.24 The duplicate management table shown in FIG. 1 is then used to check whether there are multiple database registrant IDs corresponding to the same person ID in the list of database registrant IDs included in the duplicate confirmation request. Furthermore, when there are multiple database registrant IDs corresponding to the same person ID, the management device 9 combines the multiple database registrant IDs into one group. Thus, a combination of database registrant IDs included in the sentence content of the duplicate result information is generated. The management device 9 generates the duplicate result information in the above manner. Fig.24 In the example, the information base registrant ID shown by reference numeral 9a corresponds to the same personal ID. In addition, the information base registrant ID shown by reference numeral 9b also corresponds to the same personal ID.
[0311] <s308>
[0312] The metadata request generation unit 332 generates a metadata request to be transmitted to the information library devices 4 to 6 based on the duplication result information received by the duplication confirmation reception unit 836 and the request information received by the request acquisition unit 331 .
[0313] Here, when the library registrant IDs of a plurality of libraries correspond to the same personal ID, the metadata request generating unit 332 specifies one library among the plurality of libraries. Then, the metadata request generating unit 332 generates a metadata request for libraries other than the specified library so that the libraries other than the specified library transmit metadata excluding the library registrant ID corresponding to the same personal ID.
[0314] Specifically, in this embodiment, the metadata request generation unit 332 checks the price information included in the duplicate result information received in S307 and the ID result information received in S304. Then, the metadata request generation unit 332 determines the information base that provides the personal data of a certain person at the cheapest price, and specifies a condition in the metadata request to send metadata excluding the data of the certain person from the information bases other than the determined information base.
[0315] In addition, in this embodiment, even if it is personal data of the same person, the price of the data may differ among information bases. This is because it is assumed that the profit obtained by the information base may differ among information bases.
[0316] like Fig.31 As shown, the metadata request of this embodiment is in addition to the above Figure 6 In addition to the items of the metadata request shown, the sentence content also includes an item of exclusion ID.
[0317] The exclusion ID is an item showing the repository registrant ID of the personal data not included in the metadata sent from the repository (i.e., excluded). That is, the repository that has received the metadata request will send the metadata to the intermediary device 8 after excluding the data of the repository registrant ID specified by the exclusion ID. Thus, the data of the repository registrant ID corresponding to the same personal ID is excluded from the metadata from the repository other than the specified repository.
[0318] <s309>
[0319] S309 and above Figure 4 The S103 is the same as that of S103, so the description is omitted.
[0320] <s310>
[0321] Next, in S310, the metadata receiving unit 334 receives metadata from each of the information library devices 4 to 6 via the communication unit 81. Here, when the information library registrant IDs of the plurality of information libraries 4a to 6a correspond to the same individual ID, the metadata receiving unit 334 receives metadata including the data of the individual from the information library that provides the personal data of the individual at the cheapest price. Furthermore, the metadata receiving unit 334 receives metadata excluding the data of the individual from information libraries other than the information library that provides the personal data of the individual at the cheapest price. This prevents the metadata receiving unit 334 from receiving metadata including the data of the same person from the plurality of information libraries.
[0322] <S311~S317>
[0323] S311~S317 and the above Figure 4 S105~S111 are the same, so the description is omitted.
[0324] [3-3. Effect]
[0325] According to the third embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment described above, the following effects can be obtained.
[0326] (3a) In this embodiment, the procurement plan determination unit 336 generates a metadata request based on the duplication result information, and determines a procurement plan based on the metadata obtained as a response to the metadata request. That is, the procurement plan determination unit 336 determines a procurement plan based on the duplication result information.
[0327] Therefore, personal data is collected according to the collection scheme determined based on the duplicate confirmation information. This can meet the needs of the data user 2a when the same person deposits data in multiple information repositories 4a to 6a. In addition, the intermediary device 8 collects data from multiple information repositories 4a to 6a on behalf of the data user 2a, so it is easier to collect the personal data required by the data user 2a.
[0328] (3b) In this embodiment, the recruitment plan determination unit 336 determines a recruitment plan for recruiting either the first personal data or the second personal data, wherein the duplication result information indicates that the first personal data and the second personal data are personal data related to the same person.
[0329] Therefore, it is possible to suppress the duplication of purchasing the same personal data concerning the same person from a plurality of information repositories 4a and 5a.
[0330] (3c) In the present embodiment, the procurement plan determination unit 336 determines a procurement plan in which the cheaper personal data is procured from among the first personal data and the second personal data concerning the same person.
[0331] Therefore, it is possible to suppress duplicate purchases of personal data with the same content concerning the same person, and the data user 2a can purchase the personal data at a lower price.
[0332] (3d) In the present embodiment, the duplication confirmation receiving unit 836 acquires duplication result information from the management device 9 which is an external device capable of generating duplication result information.
[0333] Here, it can be considered that the intermediary device 8 Fig.24 The duplication status table shown is stored in its own storage unit 82, and the duplication result information is obtained based on the duplication status table stored in the storage unit 82. However, in this configuration, the duplication status table stored in the storage unit 82 may not be updated to the latest duplication status table, so that the obtained duplication result information may not reflect the latest duplication status of the personal data. In contrast, according to the configuration of this embodiment, since the duplication result information is obtained from the management device 9, the intermediary device 8 can easily obtain the duplication result information reflecting the latest duplication status. Moreover, the intermediary device 8 can easily determine the fundraising plan based on the latest duplication status.
[0334] (3e) In the present embodiment, the duplication result information is information that associates a database registrant ID of a certain database with a database registrant ID of another database related to the same person.
[0335] Therefore, when multiple repositories manage personal data related to the same person with different repository registrant IDs, the intermediary device 8 can determine whether any personal data managed by multiple repositories is personal data related to the same person. Furthermore, the intermediary device 8 can determine a fundraising plan based on the determined result.
[0336] In addition, in the present embodiment, the duplicate result information is equivalent to the duplicate confirmation information, the information base registrant ID is equivalent to the registration identification information, the management device 9 is equivalent to an external device that manages the duplicate confirmation information or can generate duplicate confirmation information, S301 is equivalent to processing as a request acquisition unit, S307 is equivalent to processing as a duplicate confirmation acquisition unit, S312 is equivalent to processing as a determination unit, and S315 and S317 are equivalent to processing as an acquisition and sending unit.
[0337] [4. Fourth embodiment]
[0338] [4-1. Differences from the third embodiment]
[0339] The basic structure of the fourth embodiment is the same as that of the third embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the third embodiment represent the same structure, and for this, refer to the above description.
[0340] In the third embodiment, the intermediary device 8 performs duplicate confirmation to confirm which data stored in the plurality of information repositories 4a to 6a is the data of the same person. Then, the intermediary device 8 determines a procurement scheme to avoid duplicate purchase of personal data of the same person. That is, the intermediary device 8 only procures personal data of the same person from a designated information repository among the plurality of information repositories 4a to 6a.
[0341] On the other hand, it is conceivable that a customer deposits personal data in an information repository so that the information repository can provide certain services to the customer. In this case, if the service content provided by each information repository is different, even if it is the same person, it is possible that the same person deposits personal data of different data items in each information repository. Therefore, it is assumed that the data user 2a wants to collect and obtain the personal data of the same person from multiple information repositories 4a to 6a.
[0342] The fourth embodiment is different from the third embodiment in that the intermediary device 8 collects and gathers personal data of the same person from each of the plurality of information repositories 4a to 6a. The fourth embodiment will be described in detail below.
[0343] The hardware structure and functional elements of the mediation device 8 of the fourth embodiment are the same as those of the third embodiment. In particular, the mediation device 8 of the fourth embodiment has Fig.25 The functions of the elements 331 to 341 and 831 to 836 are basically the same as those in the third embodiment, but the functions of the metadata request generator 332 and the format processor 340 are partially different from those in the third embodiment. The elements 332 and 340 are described below.
[0344] <Metadata Request Generating Unit>
[0345] The metadata request generation unit 332 generates a metadata request to be sent to the information repository devices 4 to 6 based on the duplication result information received by the duplication confirmation receiving unit 836 and the request information received by the request acquisition unit 331. The information repository registrant ID of an individual whose personal data is stored in multiple information repositories can be identified from the received duplication result information. The metadata receiving unit 334 generates a metadata request for requesting metadata that includes only the data of an individual whose personal data is stored in multiple information repositories (i.e., also in other information repositories).
[0346] <Format Processing Section>
[0347] The format processing unit 340 adjusts the data format of the delivered data received from the plurality of information library devices 4 to 6 into a common data format and integrates the data into one data, thereby generating integrated data. In this embodiment, the format processing unit 340 generates the integrated data by collecting personal data of the same person received from the plurality of information library devices 4 to 6.
[0348] [4-2. Processing]
[0349] Next, refer to the above Fig.26 The flowchart of FIG. 1 illustrates a data collection process executed by the control unit 83 of the intermediary device 8 according to the fourth embodiment instead of the data collection process according to the third embodiment.
[0350] <S301~S307>
[0351] S301 to S307 are the same as S301 to S307 of the third embodiment described above, and thus description thereof will be omitted.
[0352] <s308>
[0353] Next, in S308, the metadata request generation unit 332 generates a metadata request to be sent to the information repository devices 4 to 6 based on the duplication result information received in S307 and the request information received in S301. Here, the metadata request generation unit 332 generates a metadata request for requesting metadata including only the data of an individual whose personal data is deposited in a plurality of information repositories.
[0354] Specifically, the metadata request generation unit 332 generates the following Fig.32 as well as Fig.33 The metadata request shown. Fig.32 An example of a metadata request sent to the first information repository 4a is shown in FIG. Fig.33 2 shows an example of sending a metadata request to the second information repository 5a.
[0355] The metadata request of this embodiment includes the above Figure 6 The metadata request shown has basically the same items, but does not include the item of the distribution statistics axis. In addition, the metadata request of this embodiment further includes the item of the object ID in the sentence content.
[0356] The object ID mentioned here is an item indicating the information base registrant ID of an individual included in the metadata sent from the information base. That is, the information base 4a to 6a that receives the metadata request sends the following metadata to the intermediary device 8, that is, the metadata includes only the data of the information base registrant ID specified by the object ID. The information base registrant ID of the individual who has deposited personal data in multiple information bases is recorded in the object ID.
[0357] For example, in the above Fig.24 In the example, the database registrant ID "0900838" of the first database 4a whose database ID is "00001", the database registrant ID "9888100" of the second database 5a whose database ID is "00002", and the database registrant ID "430981213" of the third database 6a whose database ID is "00003" are the IDs of the same person. In addition, the database registrant ID "2910110" of the first database 4a and the database registrant ID "7550360" of the second database 5a are the IDs of the same person.
[0358] Therefore, if Fig.32 As shown, in the first database 4a, database registrant IDs "0900838" and "2910110" are written in the object ID as IDs indicating individuals who have stored data in the plurality of databases 4a to 6a.
[0359] In addition, Fig.32 In the example, as for the first information database 4a, as shown in the request item column, in addition to basic attributes such as gender (Gender) and age group (Age10), it also stores attributes of personal data such as the child's age (Age_minor_child), the number of family members (Num_Family), the frequency of cooking for oneself (Freq_HomeCook), the frequency of using supermarkets (Freq_GSM), the frequency of using convenience stores (Freq_CVS), and the frequency of using drug stores (Freq_DS).
[0360] On the other hand, Fig.33 As shown, in the second database 5a, database registrant IDs "7550360" and "9888100" are written in the object ID as IDs indicating individuals who have stored data in the plurality of databases 4a and 5a.
[0361] In addition, Fig.33 In the example of , as for the second information base 5a, as shown in the request item column, in addition to basic attributes such as gender and age group, it also stores personal data attributes such as monthly browsing history of recipe websites and the amount of money purchased for magazines in three months.
[0362] The metadata request generation unit 332 generates the metadata request as described above.
[0363] <S309~S315>
[0364] S309 to S315 are the same as S309 to S315 of the third embodiment described above, and thus description thereof will be omitted.
[0365] <s316>
[0366] Next, in S316 , the format processing unit 340 adjusts the data format of the delivery data received from the plurality of library devices 4 to 6 into a common data format and integrates the data into one data, thereby generating integrated data.
[0367] exist Fig.34 An example of integrated data is shown in . In the figure, the attribute (i.e., data item) of the personal data shown by symbol 10a is an attribute held by both the first information base 4a and the second information base 5a. On the other hand, the attribute of the personal data shown by symbol 10b is an attribute held only by the first information base 4a. In addition, the attribute of the personal data shown by symbol 10c is an attribute held only by the second information base 5a. The format processing unit 340 generates integrated data by collecting personal data of the same person from multiple information bases 4a to 6a in the manner described above.
[0368] <s317>
[0369] S317 is the same as S317 of the third embodiment described above, so the description thereof is omitted.
[0370] [4-3. Effect]
[0371] According to the fourth embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment and the effects (3a), (3d), and (3e) of the third embodiment, the following effects can be obtained.
[0372] (4a) In the present embodiment, the recruitment scheme determination unit 336 determines the recruitment scheme for both the first personal data and the second personal data, wherein the duplication result information indicates that the first personal data and the second personal data are personal data of the same person.
[0373] Therefore, for example, when the same person deposits different personal data in the first information repository 4a and the second information repository 5a, the personal data of the same person can be collected from the multiple information repositories 4a and 5a. Since the personal data deposited in the multiple information repositories are not necessarily the same, the intermediary device 8 can generate information that does not exist in either of the information repositories 4a and 5a by collecting.
[0374] In addition, the correspondence relationship between each structure of the mediation device 8 in this embodiment and each sentence of the claims is the same as that of the third embodiment.
[0375] [5. Fifth embodiment]
[0376] [5-1. Differences from the third embodiment]
[0377] The basic structure of the fifth embodiment is the same as that of the third embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the third embodiment represent the same structure, and for this, refer to the above description.
[0378] In the third embodiment, the intermediary device 8 obtains the duplicate result information from the external management device 9. In contrast, in the fourth embodiment, a duplicate status table is pre-stored in the storage unit 82 of the intermediary device 8. Furthermore, when receiving the request information from the user device 2, the intermediary device 8 generates the duplicate result information from the storage unit 82 based on the duplicate status table, which is different from the third embodiment. The fifth embodiment will be described in detail below.
[0379] like Figure 2 As shown, the intermediary device 11 of the fifth embodiment includes a communication unit 111, a storage unit 112, and a control unit 113. The hardware configuration of these components 111 to 113 is the same as the components 81 to 83 of the intermediary device 8 of the third embodiment. However, the data stored in the storage unit 112 of the intermediary device 11 of the fifth embodiment is different from that of the third embodiment. Specifically, the storage unit 112 of the fifth embodiment stores Fig.35 The repetition management table shown.
[0380] Fig.35 The repetition status table is the same as above Fig.24 The duplicate management table held by the registration management party 9a shown is basically the same, except that it also contains an item for the price of personal data. That is, Fig.35 The illustrated duplication status table is information in which a database ID, a database registrant ID, a personal ID, and a price of personal data are set in correspondence with each other.
[0381] In this embodiment, it is assumed that the duplicate status table stored in the storage unit 112 is updated regularly at a predetermined frequency (for example, once a month or once a week). In addition, the duplicate status table can be updated in various ways, for example, it can be updated in the following manner. That is, the owner of the intermediary device 11 can receive a storage medium storing the duplicate status table from the registration management party 9a of the management party device 9, and update the duplicate status table by storing the duplicate status table in the received storage medium in the storage unit 112.
[0382] On the other hand, the control unit 113 performs the following operations by executing a program stored in the memory 113b through the CPU 113a. Fig.37 The control unit 113 performs the data collection process as shown. Fig.36 The elements 331 to 341, 831 to 833, 931, and 932 shown in the figure function. That is, the control unit 113 of the fifth embodiment replaces the control unit 113 of the third embodiment. Fig.25 The duplicate confirmation generating unit 834, duplicate confirmation transmitting unit 835 and duplicate confirmation receiving unit 836 shown in the embodiment 3 function as a duplicate confirmation acquiring unit 931 and further function as an update processing unit 932. The duplicate confirmation acquiring unit 931 and the update processing unit 932 which are different from the third embodiment will be described below.
[0383] <Duplicate confirmation acquisition section>
[0384] The duplicate confirmation acquisition unit 931 acquires the duplicate status table from the storage unit 112. Then, the duplicate confirmation acquisition unit 931 generates duplicate result information based on the ID result information received by the ID receiving unit 833 and the duplicate status table acquired from the storage unit 112. The method for generating the duplicate result information is the same as the method for generating the duplicate result information by the management device 9 of the third embodiment, so the description is omitted.
[0385] <Update Processing Section>
[0386] The update processing unit 932 updates the duplication status table stored in the storage unit 112 based on the integrated data generated by the format processing unit 340 .
[0387] For example, when the data included in the integrated data is different from the data registered in the duplication status table, the update processing unit 932 updates the data registered in the duplication status table to the data included in the delivered data. Thus, the duplication status table is updated to the data included in the integrated data, that is, the latest data content recently purchased by the intermediary device 11.
[0388] [5-2. Processing]
[0389] Next, refer to Fig.37 The flowchart of FIG. 1 is a flowchart of the control unit 113 of the intermediary device 11 of the fifth embodiment replacing the data collection process of the third embodiment ( Fig.26 ) is used to explain the data collection process performed.
[0390] <S401~S404>
[0391] S401~S404 and above Fig.26 S301 to S304 are the same, so the description is omitted.
[0392] <s405>
[0393] Next, in S405, the duplicate confirmation acquisition unit 931 acquires the duplicate status table from the storage unit 112. Then, the duplicate confirmation acquisition unit 931 generates duplicate result information based on the ID result information received by the ID reception unit 833 and the duplicate status table acquired from the storage unit 112, and thereby acquires the duplicate result information.
[0394] <S406~S415>
[0395] S406~S415 and above Fig.26 S308~S317 are the same, so the description is omitted.
[0396] <s416>
[0397] Next, in S416 , the update processing unit 932 updates the duplication status table stored in the storage unit 112 based on the integrated data generated by the format processing unit 340 .
[0398] [5-3. Effect]
[0399] According to the fifth embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment and the effects (3a) to (3c) and (3e) of the third embodiment, the following effects can be obtained.
[0400] (5a) In the present embodiment, the intermediary device 11 obtains the duplicate status table from the storage unit 112. Furthermore, the duplicate confirmation acquisition unit 931 generates duplicate result information based on the ID result information received by the ID receiving unit 833 and the obtained duplicate status table, and thereby obtains the duplicate result information. That is, even if the intermediary device 11 and the management device 9 do not exchange data, the intermediary device 11 can obtain the duplicate result information. Therefore, compared with the configuration of sending a duplicate confirmation request to the management device 9 and obtaining the duplicate result information, the communication volume of the management device 9 can be reduced. In addition, the system development cost of the API (Application Programming Interface) used to send and receive the duplicate confirmation request and the duplicate result information can be suppressed.
[0401] In addition, in this embodiment, the duplication status table is equivalent to duplication confirmation information, S401 is equivalent to processing as a request acquisition unit, S405 is equivalent to processing as a duplication confirmation acquisition unit, S410 is equivalent to processing as a determination unit, and S413 and S415 are equivalent to processing as an acquisition and transmission unit.
[0402] [6. Sixth embodiment]
[0403] [6-1. Differences from the third embodiment]
[0404] The basic structure of the sixth embodiment is the same as that of the third embodiment, so the description of the common structure is omitted and the description will be centered on the differences. In addition, the same symbols as those of the third embodiment represent the same structure, and refer to the above description for this. In the sixth embodiment, the user device 2 of the data user 2a uses the personal data collected from the information base 4a~6a to distribute advertisements to individuals who have deposited personal data in the information base 4a~6a, which is different from the above-mentioned third embodiment.
[0405] As in the third embodiment, Fig.38 The procurement system 12 of the sixth embodiment shown includes a user device 2, an intermediary device 3, and a plurality of information library devices 4 to 6. The intermediary device 3 and the plurality of information library devices 4 to 6 of the sixth embodiment are the same as those of the third embodiment.
[0406] On the other hand, Fig.39 As shown, the user device 2 of the sixth embodiment includes a communication unit 21, a storage unit 22, and a control unit 23. The communication unit 21 is a communication interface for connecting the user device 2 to the network. The user device 2 can perform data communication with the intermediary device 8 and the information processing terminals 11 to 17 owned by individuals via the communication unit 21.
[0407] The storage unit 22 stores various data. In the present embodiment, the storage unit 22 stores advertisement information and destination information. The advertisement information mentioned here is advertisement information sent to individuals involved in the personal data collected by the data user 2a from the information bases 4a to 6a, and is advertisement information corresponding to the attributes of the collected personal data (in other words, various attributes such as preferences of the individuals involved in the personal data).
[0408] In addition, the destination information described here is information for specifying the destination to which the advertising information is to be sent. In this embodiment, the individual whose personal data is stored in the information base 4a~6a is assumed to be the destination. The destination information can be an identifier for identifying the destination of the advertising information, such as IDFA (Identification For Advertisers) and ADID (Advertising Identifier), a small text file (cookie) ID, and the email address of the distribution object. In this embodiment, it is assumed that the destination information is included in the personal data obtained from the information base 4a~6a.
[0409] The control unit 23 is mainly composed of a well-known microcomputer having a CPU 23a, a RAM, a ROM, a flash memory or other semiconductor memory (hereinafter referred to as memory 23b). The various functions of the control unit 23 are realized by the CPU 23a executing a program stored in a non-transfer physical recording medium. In this example, the memory 23b corresponds to a non-transfer physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is implemented. The control unit 23 executes the following Fig.40 Ad distribution process shown.
[0410] [6-2. Processing]
[0411] Next, refer to Fig.40 The flowchart of FIG. 1 illustrates the advertisement distribution process executed by the control unit 23 of the user device 2. In addition, the advertisement distribution process is executed at an appropriate timing.
[0412] First, in S501 , the control unit 23 acquires advertisement information and destination information from the storage unit 22 .
[0413] Next, in S502, the control unit 23 distributes the advertisement. Specifically, the control unit 23 transmits the advertisement information acquired in S501 to the destination indicated by the destination information acquired in S501 via the communication unit 21. The control unit 23 ends after executing S502. Fig.40 Advertising distribution processing.
[0414] [6-3. Effect]
[0415] According to the sixth embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment and the effects (3a) to (3e) of the third embodiment, the following effects can be obtained.
[0416] (6a) In the present embodiment, the user device 2 uses the personal data acquired from the information bases 4a to 6a to distribute advertisements to the individuals whose personal data are stored in the information bases 4a to 6a. Specifically, the user device 2 acquires the following information: the advertisement information to be notified to the individuals involved in the personal data acquired from the intermediary device 8, and the destination party information indicating the destination party of the advertisement information. Then, the user device 2 sends the advertisement information to the destination party indicated by the destination party information.
[0417] Therefore, advertisement information is transmitted using personal data acquired from the information base devices 4 to 6. Thus, advertisement distribution suitable for individuals whose personal data are stored in the information bases 4a to 6a can be performed.
[0418] In the present embodiment, the procurement system 12 corresponds to the system, the advertisement information corresponds to the notification information, S501 corresponds to the process as a notification information acquisition unit, and S502 corresponds to the process as a notification information transmission unit.
[0419] [7. Seventh Implementation Method]
[0420] [7-1. Differences from the first embodiment]
[0421] The basic structure of the seventh embodiment is the same as that of the first embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the first embodiment represent the same structure, and for this, refer to the above description.
[0422] In the first embodiment described above, the data user 2a obtains personal data from the information base 4a~6a via the intermediary device 3. Here, it is assumed that the data user does not want to bear the cost of processing personal data. That is, at present, there is also a trend to require security management devices such as the use of privacy tags for data users who obtain personal data from the information base 4a~6a. The security management device refers to necessary and appropriate measures taken by the operator to achieve the security management of personal data such as preventing the leakage, disappearance or damage of personal data. However, for data users such as small and medium-sized enterprises, it is sometimes difficult to implement the above-mentioned security management device. Therefore, the above-mentioned data user may consider obtaining anonymous processed information instead of not implementing security management measures. The anonymous processed information mentioned here refers to information generated based on personal data, and is information generated after changing or deleting the information contained in the personal data so that the individual involved in the personal data will not be identified.
[0423] The seventh embodiment is different from the first embodiment in that the intermediary device 3 generates anonymous processed information based on personal data acquired from the information repositories 4a to 6a and transmits the generated anonymous processed information to the user device 2. The seventh embodiment will be described in detail below.
[0424] The hardware configuration of the procurement system 1 of the seventh embodiment is the same as that of the first embodiment. On the other hand, the processing executed by the mediation device 3 of the seventh embodiment and the data transmitted and received are partially different from those of the first embodiment.
[0425] [7-2. Processing]
[0426] The following reference Fig.41 The control unit 33 of the intermediary device 3 of the seventh embodiment replaces the data collection process ( Figure 4 ) and the data collection process performed. Fig.41 In the flowchart of FIG. 5 , the processing of S501, S503 to S509, and S511 (i.e., the processing other than S502 and S510) is respectively the same as that of the above Figure 4 Therefore, the description of these processes will be omitted below, and only S502 and S510, which are different, will be described.
[0427] <s502>
[0428] In S502, the metadata request generation unit 332 generates a metadata request based on the request information received in S501. Fig.42 The metadata request shown. Fig.42 The metadata request shown is essentially the same as Figure 6 The metadata request of the first embodiment shown is the same, but the category description of the purpose of use of personal data is different. Fig.42 In the metadata request shown, the category of purpose of using personal data is described as "creating anonymous processed information."
[0429] <s510>
[0430] In S510, the form processing unit 340 unifies the data form of the delivery data received from each information library device 4 to 6 and converts the data. Then, the form processing unit 340 unifies the delivery data from each information library device 4 to 6 into one data. Specifically, as in the first embodiment, the form processing unit 340 converts the variable names and values contained in the delivery data received from each information library device 4 to 6 according to the data conversion dictionary of each information library device 4 to 6, thereby unifying the data form of the delivery data received from each information library device 4 to 6. In addition, the form processing unit 340 converts the variable names and values contained in the delivery data to comply with the standards stipulated in the Personal Information Protection Act.
[0431] Specifically, the format processing unit 340 performs the following operations, for example, Fig.15 The conversion dictionary shown is used to convert the information received from the first information base 4a. Fig.16A Then, the format processing unit 340 generates the variable names and values contained in the delivery data shown in FIG. Fig.43 The converted delivery data of the first information base 4a is shown. Fig.43 The converted delivered data shown is anonymized information that has been anonymized. Anonymization is the process of changing or deleting personal data so that the individual involved in the personal data cannot be identified. Anonymization can be, for example, the following process: the granularity of personal data is coarsened to the extent that the individual involved in the personal data cannot be identified.
[0432] Specifically, for example, Fig.43 In the anonymous processed information shown, the information that can identify an individual is deleted. Information that can identify an individual includes, for example, an ID assigned to an individual by the information database (i.e., the database registrant ID) and name. Fig.43 As shown in the ID (a3321, 34acd, 943dd, ...), IDs are assigned to individuals or personal data in a random manner.
[0433] Furthermore, anonymous processed information is information that is unique or rare when viewed as a whole in a specific region (eg, Japan), so information that can identify an individual may be deleted or changed.
[0434] Specifically, for example, the age of an individual in personal data (Demographic: Age) is "115 years old". In this case, information about the age of "115 years old" is relatively rare in Japan and can identify an individual. Therefore, such information can be deleted in the anonymous processed information, or it can be adjusted to "over 100 years old" or the like.
[0435] Furthermore, in the anonymous processed information, information that is unique or rare and can identify an individual in the data sets acquired from the information repositories 4 a to 6 a may be deleted or changed.
[0436] For example, information such as "unmarried or married" (Demographic: Marital) is "divorced" or "death" in the above dataset is unique or rare and can identify individuals. In this case, when a person's "unmarried or married" is "divorced" or "death", Fig.43 As shown in the ID "34acd", the individual's "Single or Married" can be changed to "Divorced or Divorced".
[0437] In addition, for example, information such as the amount of money spent on magazines purchased in three months (Aggregate: 1: TotalExpense3MonthSeasonings) is greater than 5,000 yen is unique or rare in the above data set and can identify an individual. In this case, in the anonymous processing information, Fig.43 As shown in the individual ID "09aba", the actual amount greater than 5,000 yen is not recorded, but the value is adjusted to an integer such as "5,000 yen".
[0438] As described above, the intermediary device 3 converts the delivery data received from each information repository 4a to 6a into anonymous processed information. Furthermore, the intermediary device 3 integrates the anonymous processed information of each information repository 4a to 6a into one data, thereby generating integrated data. In addition, the order of performing the anonymous processing and the data integration processing is not limited to this. For example, after the delivery data of each information repository 4a to 6a is integrated into one data, the anonymous processing can be performed on the integrated data.
[0439] [7-3. Effect]
[0440] According to the seventh embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment described above, the following effects can be obtained.
[0441] In this embodiment, the intermediary device 3 receives personal data from the information library devices 4 to 6 via the communication unit 31, and generates anonymous processed information based on the received personal data. Here, anonymous processed information is information generated based on personal data, and is information (i.e., data) generated by changing or deleting information included in the personal data so that the individual involved in the personal data cannot be identified. In addition, the intermediary device 3 sends the generated anonymous processed information to the user device 2 via the communication unit 31.
[0442] Therefore, the cost of processing personal data by a data user who has difficulty in implementing the security management device can be reduced. In addition, the computer security related to personal data management can be improved.
[0443] [8. Eighth Implementation Method]
[0444] [8-1. Differences from the seventh embodiment]
[0445] The basic structure of the eighth embodiment is the same as that of the seventh embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the seventh embodiment represent the same structure, and for this, refer to the above description.
[0446] In the first embodiment described above, the data user 2a obtains personal data from the information bases 4a to 6a via the intermediary device 3. Here, it is assumed that the data user 2a does not need fine-grained personal data. For example, it is conceivable that the user 2a formulates a market strategy after knowing the extent to which the company's customers purchase competing products. In this case, even if the data is not the company's customers, if the statistical information on the average purchase volume of competing products by a group of individuals with attributes similar to the company's customers can be known, the data user 2a can fully consider the strategy. In this case, fine-grained personal data is not required.
[0447] The eighth embodiment is different from the first embodiment in that the intermediary device 3 generates statistical information based on personal data acquired from the information repositories 4a to 6a and transmits the generated statistical information to the user device 2. The eighth embodiment will be described in detail below.
[0448] The hardware configuration of the procurement system 1 of the eighth embodiment is the same as that of the first embodiment. On the other hand, the processing executed by the mediation device 3 of the eighth embodiment and the data transmitted and received are partially different from those of the first embodiment.
[0449] [8-2. Processing]
[0450] The following refers to the above Fig.41 The control unit 33 of the intermediary device 3 of the eighth embodiment replaces the data collection process ( Figure 4 ) and the data collection process performed. Fig.41 In the flowchart of FIG. 5 , the processing of S501, S503 to S509, and S511 (i.e., the processing other than S502 and S510) is respectively the same as that of the above Figure 4 Therefore, the description of these processes will be omitted below, and only S502 and S510, which are different, will be described.
[0451] <s502>
[0452] In S502, the metadata request generation unit 332 generates a metadata request based on the request information received in S501. Fig.44 The metadata request shown. Fig.44 The metadata request shown is essentially the same as Figure 6 The metadata request of the first embodiment shown is the same, but the category description of the purpose of use of personal data is different. Fig.41 In the metadata request shown, the category of purpose of using personal data is described as "creating statistical information."
[0453] <s510>
[0454] In S510, the form processing unit 340 unifies the data form of the delivery data received from each information library device 4 to 6 and converts the data. Then, the form processing unit 340 unifies the delivery data from each information library device 4 to 6 into one data. Specifically, as in the first embodiment, the form processing unit 340 converts the variable names and values contained in the delivery data received from each information library device 4 to 6 according to the data conversion dictionary of each information library device 4 to 6, thereby unifying the data form of the delivery data received from each information library device 4 to 6. Then, the form processing unit 340 converts the delivery data whose variable names and values have been converted into statistical information. The statistical information mentioned here refers to information obtained by statistically analyzing or processing personal data involving multiple persons obtained from the information libraries 4a to 6a.
[0455] Specifically, for example, the format processing unit 340 performs Fig.15 The conversion dictionary shown in FIG. 1 is used to convert the data received from the first information base 4a into Fig.16A The format processing unit 340 then generates the following: Fig.45 The converted delivery data of the first information base 4a is shown. Fig.45 The converted delivery data shown is the delivery data that has been statistically informatized.
[0456] exist Fig.45 In the statistical information shown, the personal data concerning a plurality of persons received from the first information base 4a is classified into a plurality of groups (e.g., six groups with group IDs 1 to 6). For example, the personal data concerning a plurality of persons may be mapped with appropriate items contained in the personal data (e.g., the amount of money spent on magazine purchases over three months) and clustered, thereby classifying the personal data into a plurality of groups.
[0457] Then, the group size is associated with the total number of individuals that meet various demographic attributes (sex = male; age = 15 years old, etc.) in units of group ID for each group. The group size is the total number of individuals or individual data included in the group.
[0458] Then, the mediation device 3 integrates the statistical information generated for each of the information repositories 4a to 6a into one data, thereby generating integrated data.
[0459] In addition, in the above, statistical information is generated by clustering, but the method of generating statistical information is not limited to this. For example, statistical information can also be generated by other statistical methods such as cross-tab statistics.
[0460] In addition, for example, in the above, statistical information is generated by classifying personal data into a plurality of groups, but, for example, personal data may be aggregated into one group instead of being classified into a plurality of groups. And, statistical information indicating the total number, average, median, variance, etc. of individuals or personal data that meet various demographic attributes, etc. may be generated for the group.
[0461] Furthermore, for example, instead of generating statistical information for each of the information repositories 4a to 6a, all personal data received from the plurality of information repositories 4a to 6a may be aggregated first, and statistical information may be generated based on the aggregated personal data.
[0462] In the eighth embodiment described above, data is not sent to the user device 2 in units of individual data but is sent in units of groups.
[0463] In the eighth embodiment, the statistical information is generated in such a way that the individual involved in the personal data used to generate the statistical information cannot be identified from the generated statistical information. That is, the generated statistical information may be anonymous processed information.
[0464] [8-3. Effect]
[0465] According to the eighth embodiment described in detail above, in addition to the effects (1a) to (1h) of the first embodiment described above, the following effects can be obtained.
[0466] In this embodiment, the intermediary device 3 receives personal data concerning a plurality of persons from the information base devices 4 to 6 via the communication unit 31, and generates statistical information based on the received personal data, the statistical information showing statistical information related to the attributes of the personal data (i.e., items such as gender and age). Then, the intermediary device 3 sends the generated statistical information to the user device 2 via the communication unit 31.
[0467] Therefore, it is possible to provide statistical information to the data user 2a when fine-grained personal data is not required and only statistical information is needed. In addition, since the use of statistical information generally increases the granularity of data, it is possible to reduce the cost of processing personal data for data users who have difficulty in implementing security management devices. In addition, it is possible to improve computer security related to personal data management.
[0468] [9. Ninth Implementation Method]
[0469] [9-1. Differences from the fourth embodiment]
[0470] The basic structure of the ninth embodiment is the same as that of the fourth embodiment, so the description of the common structure is omitted and the description will be mainly focused on the differences. In addition, the same reference numerals as those of the fourth embodiment represent the same structure, and for this, refer to the above description.
[0471] In the fourth embodiment, the intermediary device 8 collects personal data of the same person from multiple information repositories 4a to 6a. In particular, in the fourth embodiment, the intermediary device 8 inquires the management device 9 whether there is personal data of the same person in the personal data stored in multiple information repositories 4a to 6a. Then, the management device 9 uses Fig.24 The three IDs, namely, the repository ID, the repository registrant ID, and the personal ID, identify the personal data of the same person. Furthermore, the broker device 8 acquires a plurality of personal data identified as the personal data of the same person from the plurality of repositories 4a to 6a.
[0472] In the ninth embodiment, personal data of the same person is collected from multiple information repositories 4a to 6a, which is the same as the fourth embodiment. However, in the ninth embodiment, the intermediary device does not query the management device 9. Specifically, the ninth embodiment is different from the fourth embodiment in that the intermediary device identifies multiple personal data with similar combinations of attribute values such as age and gender in the data set containing multiple personal data received from multiple information repositories 4a to 6a. Then, multiple personal data with similar combinations of attribute values are collected from multiple information repositories 4a to 6a as personal data related to the same person. The ninth embodiment is described in detail below.
[0473] Compared with the above-mentioned fourth embodiment, the hardware structure of the procurement system of the ninth embodiment is the same as that of the above-mentioned first embodiment. On the other hand, the function of the mediation device 12 of the ninth embodiment is partially different from that of the first embodiment.
[0474] Specifically, the control unit of the mediation device 12 of the ninth embodiment is as follows: Fig.46 The elements 331 to 341 and 1231 shown function.
[0475] That is, the control unit of the intermediary device 12 of the ninth embodiment is not limited to the control unit of the first embodiment. Figure 3 The point that the elements 331 to 341 shown in the figure function as a similarity determination unit 1231 is different from the first embodiment.
[0476] <Similarity Determination Unit>
[0477] The similarity determination unit 1231 determines a plurality of personal data having similar attribute values from the plurality of personal data received from the plurality of information repositories 4a to 6a. The determination of whether the personal data are similar can be performed by determining whether the similarity between the personal data reaches or exceeds a predetermined threshold. Furthermore, the similarity determination unit 1231 regards the determined plurality of personal data as personal data of the same person and associates them with each other. Then, the plurality of personal data associated with each other by the similarity determination unit 1231 is sent to the data user 2a as personal data of the same person by the data sending unit 341. The processing content of the similarity determination unit 1231 is described in detail below.
[0478] [9-2. Processing]
[0479] Next, refer to Fig.47 The flowchart of the ninth embodiment replaces the data collection process ( Figure 4 ) and the data collection process performed. Fig.47 In the flowchart of FIG. 1 , the processing of S601 to S610 and S612 (i.e., the processing other than S611) is respectively the same as that of the above Figure 4 Therefore, the description of these processes will be omitted below, and only S611 which is the difference will be described.
[0480] <s611>
[0481] In S611, the similarity determination unit 1231 performs similarity determination on the multiple personal data received from the multiple information repositories 4a to 6a. Then, the similarity determination unit 1231 associates the multiple personal data determined to be similar to each other. Similarity determination is a determination made on whether the multiple personal data are similar. Specifically, the similarity determination unit 1231 determines the multiple personal data with similar attribute values in the following manner.
[0482] That is, as a result of unifying the data format by the format processing unit 340, Fig.48 as well as Fig.49 The data set shown.
[0483] Fig.48 The data set obtained by converting the variables and values of the personal data obtained from the first information base 4a into a common format is shown. Fig.49 This shows a data set after the variables and values of the personal data obtained from the second information base 5a are converted into a common format. Fig.48 as well as Fig.49 In the example of , it is assumed that 20 pieces of personal data (personal data with IDs 1 to 20) are acquired from the first information repository 4a and the second information repository 5a, respectively.
[0484] exist Fig.48 as well as Fig.49 In the data set shown, each ID corresponds to each attribute value of personal data. Fig.48 as well as Fig.49 In , a value of "1" indicates compliance with the attribute, and a value of "0" indicates noncompliance with the attribute. For example, in Fig.48 In the data set shown, the personal data of ID=1 is "D:Gender:1"=1, and "D:Age:20-34"=1, which means that the individual involved in the personal data of ID=1 is male and aged between 20 and 34 years old.
[0485] In the first embodiment, the standard values in the common data format include: Fig.14 The texts such as "Male" and "Female" are shown, however, in this embodiment, in order to facilitate subsequent calculations, the standard values are set to numerical values such as "0" and "1".
[0486] What is important here is that the meaning of the variables and values of the data sets received from different information repositories 4a and 5a is converted into a common form by the form processing unit 340 (i.e., the process of S610), so that a consensus is reached. The meaning of the value is, for example, "D: Gender: 1" means male, etc. In this way, the similarity between the personal data obtained from multiple information repositories 4a to 6a with different processable data forms can be calculated.
[0487] Specifically, for example, Fig.48 as well as Fig.49 In the data set shown, the personal data of each ID can be regarded as a vector with each attribute value as a component. Fig.48 In the example, the personal data of ID=1 can be regarded as a vector (1, 0, 0, 1, ...) with attribute values such as "D:Gender:1", "D:Gender:2", "D:Age:0-19", "D:Age:20-34" as components. In addition, the similarity between personal data can be calculated by calculating the similarity or distance between vectors. In addition, as for the relationship between the similarity and distance between vectors, the higher the similarity, the smaller the distance; the lower the similarity, the larger the distance.
[0488] And, by calculating Fig.48 The personal data of ID=1 to 20 received from the first information base 4a shown in FIG. Fig.49 The similarity between the personal data of ID=1 to 20 received from the second information base 5a is obtained by Fig.50 The similarity matrix shown.
[0489] exist Fig.50 In the similarity matrix shown, the row label "1ID" represents the ID of the first information base 4a, and the column label "2ID" represents the ID of the second information base 5a. That is, the component of 1ID=i and 2ID=j represents the similarity between the personal data of ID=i in the first information base 4a and the personal data of ID=j in the second information base 5a.
[0490] In addition, Fig.50 In the example of , the similarity between two personal data (i.e., two vectors) is calculated as cosine similarity, but the method for calculating the similarity between two personal data is not limited to this. For example, other distances or similarities such as Euclidean distance or Mahalanobis distance can also be used to calculate the similarity between two personal data. Fig.50 In the similarity matrix shown, the cosine similarity is not normalized to the range of 0 to 1.
[0491] Then, the similarity determination unit 1231 associates two pieces of personal data whose similarity in the similarity matrix reaches a predetermined threshold (hereinafter referred to as similarity threshold) or more as personal data of the same person.
[0492] For example, in Fig.50 In the example of , when two personal data having a similarity of 5 or more are determined to be personal data of the same person, the following three combinations form a combination of personal data of the same person.
[0493] Personal data of ID=2 in the first information base 4a (1ID=2) and personal data of ID=10 in the second information base 5a (2ID=10)
[0494] Personal data of ID=12 in the first information base 4a (1ID=12) and personal data of ID=12 (2ID=12) or 13 (2ID=13) in the second information base 5a
[0495] Personal data of ID=18 (1ID=18) in the first information base 4a and personal data of ID=7 (2ID=7) in the second information base 5a
[0496] However, there is a case where one piece of personal data shown in the second combination is associated with a plurality of pieces of personal data. In this case, for example, the following processing (1) to (3) can be considered.
[0497] (1) When a plurality of personal data are associated with one personal data, a combination including the one personal data is excluded. That is, only when one personal data is associated with one personal data, the two personal data are determined to be personal data of the same person.
[0498] (2) When a plurality of personal data are associated with one personal data and the similarities between the plurality of personal data and the one personal data are different, personal data with a high similarity to the one personal data is preferentially considered among the plurality of personal data. Furthermore, the personal data preferentially considered among the plurality of personal data is determined to be the personal data of the same person as the one personal data.
[0499] (3) When a plurality of personal data are associated with one personal data and the similarities between the plurality of personal data and the one personal data are the same, if there is personal data with a higher similarity than the one personal data among the plurality of personal data, the personal data with a higher similarity are associated. For example, assuming that in the above example, with respect to the personal data with ID=12 in the second information base 5a, if there is other personal data with a higher similarity than the personal data with ID=12 in the first information base 4a, the other personal data is associated with the personal data with ID=12 in the second information base 5a.
[0500] In addition, at least two of the above (1) to (3) may be used simultaneously. Thus, the similarity determination unit 1231 specifies a plurality of personal data having similar attribute values among the plurality of personal data received from the plurality of information repositories 4a to 6a.
[0501] Then, in the next process of S612 , the plurality of personal data associated with each other by the similarity determination unit 1231 are transmitted to the data user 2 a by the data transmission unit 341 as personal data of the same person.
[0502] [9-3. Effect]
[0503] According to the ninth embodiment described in detail above, in addition to the effect (4a) of the fourth embodiment described above, the following effects can be obtained.
[0504] (9a) In the present embodiment, the intermediary device 12 determines the delivery data based on a similarity matrix showing similarities between a plurality of personal data acquired from a plurality of information repositories 4a to 6a and based on similarities of attribute values of the personal data. In particular, the intermediary device 12 acquires the similarity matrix as duplicate confirmation information.
[0505] Specifically, the intermediary device 12 obtains a plurality of personal data from a plurality of information repositories 4a to 6a, and determines the similarity of the obtained plurality of personal data based on the attribute values of the personal data (S611). Then, the intermediary device 12 associates the plurality of personal data determined to be similar to each other through the similarity determination (S611). Furthermore, the intermediary device 12 sends the delivery data determined based on the associated plurality of personal data to the user device 2.
[0506] Therefore, by regarding a plurality of mutually associated personal data as the personal data of the same person, it is possible to collect personal data related to the same person from the plurality of information repositories 4a to 6a.
[0507] Furthermore, according to the present embodiment, even in a period when the registration manager 9a as in the fourth embodiment does not exist, that is, in a period earlier than the period when the registration manager 9a appears, personal data concerning the same person can be collected from a plurality of information repositories 4a to 6a.
[0508] (9b) In addition, when the items of personal data managed by the first information base 4a are different from the items of personal data managed by the second information base 5a, there may be a need to obtain as many samples of personal data as possible after completing the items of both parties. As described in the fourth embodiment, when the three IDs of the information base ID, the information base registrant ID and the personal ID are used for collection, only multiple personal data that actually relate to the same person are associated. Therefore, there is a situation where the above-mentioned sample number cannot be obtained in large quantities. In this regard, according to this embodiment, by relaxing the similarity threshold when associating personal data, many-to-many association of personal data can be allowed. As a result, the above-mentioned sample number can be increased.
[0509] Furthermore, in this embodiment, Fig.50 The similarity matrix shown is equivalent to similarity information and duplicate confirmation information, S601 is equivalent to processing as a request acquisition unit, S611 is equivalent to processing as a duplicate confirmation acquisition unit, S611 and S612 are equivalent to processing as a determination unit, and S609 and S612 are equivalent to processing as an acquisition and sending unit.
[0510] [10. Other embodiments]
[0511] As mentioned above, although the embodiment for implementing this disclosure was described, this disclosure is not limited to the above-mentioned embodiment, and can be implemented with various modifications.
[0512] (1) In each of the above embodiments, the intermediary device collects personal data from a plurality of information repository devices 4 to 6, but the number of information repository devices from which the intermediary device collects personal data is not limited thereto. For example, in the above first and second embodiments, the intermediary device may collect personal data from only one information repository device, rather than from a plurality of information repository devices.
[0513] (2) In the above embodiments, the information repository is exemplified as the personal data manager, but the personal data manager is not limited to this. For example, the personal data manager may be a carrier such as a telecommunications carrier or a credit card company that has a large amount of customer data but is not specialized in an information repository. In this way, the personal data manager may be a personal data operator engaged in the business of managing personal data deposited by individuals and providing the personal data to third parties.
[0514] (3) In each of the above embodiments, the intermediary device adjusts the data format of the delivery data received from the plurality of information library devices 4 to 6 into a common data format, integrates the data into one data, and delivers it to the data user 2a. However, the delivery method is not limited to this. For example, the intermediary device may not adjust the delivery data received from the plurality of information library devices 4 to 6 into a common data format. In addition, the intermediary device may not integrate the delivery data from the plurality of information library devices 4 to 6 into one delivery data.
[0515] (4) The determination logic of the fundraising plan in the above-mentioned embodiments is only an example, and the fundraising plan can also be determined by other determination logics. For example, in the above-mentioned embodiments, the plan with the highest reproducibility of the original data distribution within the budget amount of the data user 2a is determined as the fundraising plan. However, for example, even if the budget amount is slightly exceeded (i.e., exceeds the specified amount) but the reproducibility of the original data distribution is the highest, this plan can also be determined as the fundraising plan. That is, in the case of determining the fundraising plan based on the budget amount and the reproducibility of the original data distribution, the fundraising plan can be determined in a manner that places more emphasis on reproducibility than on the budget amount. On the other hand, the fundraising plan can also be determined in a manner that places more emphasis on the budget amount than on reproducibility as described in the above-mentioned embodiments.
[0516] In addition, for example, when a personal data manager such as an information database conducts a questionnaire survey on individuals in order to expand personal data, the personal data of individuals who do not answer the questionnaire becomes missing data. In the case where the personal data managed by the personal data manager contains missing data, a collection plan can be determined in a way to minimize the missing data.
[0517] In addition, for example, the collection scheme may be determined in a manner that optimizes the "freshness" of the collected personal data. Specifically, the intermediary device may obtain information about the last updated date and time of the personal data from the personal data manager or its own storage unit, and determine the collection scheme based on the obtained information about the last updated date and time. In this case, for example, the intermediary device may determine the collection scheme in the following manner, that is, the personal data to be collected are designated in order from the personal data with the latest last updated date and time.
[0518] Furthermore, when the data price included in the metadata received from a certain information repository is extremely low or extremely high, in other words, when the data price is below a predetermined threshold or above a predetermined threshold, the data price or the information repository itself is suspicious. In this case, the intermediary device may determine a fundraising plan in a manner that avoids the extremely low or extremely high data and raises personal data. Furthermore, the intermediary device may determine a fundraising plan in a manner that avoids the information repository that presents an extremely low or extremely high data price and raises personal data (i.e., from an information repository other than the information repository).
[0519] Furthermore, for example, the intermediary device may determine a solicitation scheme in which, with reference to factors other than price, personal data other than the lowest price is solicited from a plurality of personal data that meet the same target condition.
[0520] Specifically, as a factor other than price, the intermediary device can determine the personal data to be collected by, for example, referring to the degree of fit between the attributes contained in the personal data that are not specified by the object conditions (hereinafter referred to as non-specified attributes) and the purpose of use of the personal data by the data user 2a (and thus requesting information).
[0521] For example, the intermediary device receives a request message containing the following object conditions from the user device 2: the gender is male and the age group is in the 20s. In addition, the intermediary device receives metadata related to personal data that meets the above object conditions from each information repository 4a to 6a. At this time, it is determined from the information of the use organization contained in the request message that the data user 2a is in an industry related to catering (for example, food manufacturing). Moreover, as attributes other than gender and age group (i.e., non-specified attributes), the personal data retained by the first information repository 4a contains attributes related to catering (meal records, etc.). On the other hand, as non-specified attributes, the personal data retained by the second information repository 5a does not contain attributes related to catering. In this case, the intermediary device can determine that the personal data of the first information repository 4a has a high degree of fit with the use organization or use purpose of the data user 2a, and even if the price of the data in the first information repository 4a is higher than that of the data in the second information repository 5a, the intermediary device can determine a plan to raise data from the first information repository 4a.
[0522] In addition, for example, if the industry of the data user is the same as the industry of the individual whose data is stored in the information repositories 4a to 6a, the intermediary device can prevent the data user from obtaining the data of the individual. In other words, the intermediary device can exclude the personal data of the individual to determine the fundraising plan. That is, the intermediary device can determine the fundraising plan based on the relationship between the data user and the individual whose data is stored in the information repositories 4a to 6a. In addition, the fundraising plan can also be determined by referring to other factors besides price.
[0523] Furthermore, for example, the mediation device may acquire requirements related to conditions for determining a fundraising plan (in other words, a determination logic of a fundraising plan) from the data user 2a, and determine the fundraising plan based on the acquired requirements.
[0524] Furthermore, the mediation device may not select a fundraising plan suitable for the data user 2a from a plurality of plans, but may directly output a fundraising plan suitable for the data user 2a.
[0525] (5) Figure 5 Specific examples of request information and Figure 6 , Figure 7 The specific example of the metadata request is only one example, and the request information may only include Figure 5 etc., may also include Figure 5 Other items not shown in the examples.
[0526] (6) Metadata from a certain information repository may be information indicating the attributes of all personal data held by the information repository, or may be information indicating the attributes of only a portion of the personal data. Furthermore, metadata is not limited to data indicating a portion of the attributes of personal data, but may be data indicating all the attributes of personal data.
[0527] (7) In the second embodiment described above, the storage unit 72 stores a metadata set, but the data stored in the storage unit 72 is not limited thereto. For example, the storage unit 72 may store information indicating the characteristics of each of the information library devices 4 to 6, that is, information library characteristic information. Specifically, the information library characteristic information may be, for example, that the first information library 4a manages a large amount of personal data of women in their twenties to forties; the second information library 5a manages a large amount of personal data of users with families; the third information library 3a manages a large amount of personal data of elderly users over 60 years old, etc. In this case, for example, when the intermediary device receives request information requiring personal data of users with families from the user device 2, the intermediary device may send a metadata request and / or a data request to the second information library 5a that manages a large amount of personal data of users with families. Furthermore, the intermediary device may determine a plan for collecting personal data from the second information library 5a. In addition, the opposite may be true, that is, when the intermediary device receives request information requiring personal data of users with families from the user device 2, the intermediary device may send a metadata request and / or a data request in a manner that avoids information libraries that do not manage personal data of users with families.
[0528] That is, the intermediary device may send a metadata request and / or a data request to an information repository (or even a personal data manager) that is judged to have characteristics that meet the object conditions included in the request information based on the information repository characteristic information. In addition, the intermediary device may not send a metadata request and / or a data request to an information repository (or even a personal data manager) that is judged not to have characteristics that meet the object conditions included in the request information based on the information repository characteristic information.
[0529] Furthermore, instead of acquiring the information base characteristic information from its own storage unit 72 , the intermediary device may query each of the information bases 4 a to 6 a to acquire the information base characteristic information from each of the information bases 4 a to 6 a .
[0530] The information base characteristic information is an example of the manager characteristic information, which is information indicating the characteristics of each personal data manager. The manager characteristic information is an example of the attribute information, which is information indicating the attributes of the personal data managed by the personal data manager.
[0531] (8) The content of the update processing executed by the update processing units 732 and 932 is not limited to the content of the update processing in the second and fifth embodiments described above.
[0532] For example, in the second embodiment described above, the update processing unit 732 can update the metadata set stored in the storage unit 72 based on the personal data collected from the information repositories 4a to 6a. Specifically, for example, with respect to the personal data collected from the information repositories 4a to 6a (i.e., purchased personal data), the attributes of the personal data (i.e., the content of the data) can be known. The update processing unit 732 can update the distribution formed based on the attributes of the personal data held by the information repositories 4a to 6a as suppliers based on the content of the collected personal data, thereby updating the metadata set stored in the storage unit 72.
[0533] Likewise, in the fifth embodiment described above, the update processing unit 932 can update the duplication status table stored in the storage unit 112 based on the personal data collected from the information repositories 4a to 6a. Specifically, for example, the intermediary device collects (i.e., purchases) personal data that meets the object conditions from multiple information repositories 4a to 6a. At this time, the intermediary device compares the attributes (i.e., data content) of the purchased multiple personal data with each other, and determines whether the purchased multiple personal data are personal data related to the same person based on the similarity of the data content, etc. Furthermore, the intermediary device can set the same personal ID for multiple personal data determined to be personal data related to the same person, and newly add the data to the personal data. Fig.35 The repetition status table is shown.
[0534] (9) In the fifth embodiment, the intermediary device does not perform duplication check on the management device 9 but performs duplication check based on the duplication status table stored in the storage unit 112. However, duplication check may be performed on the management device 9 in the following cases.
[0535] That is, the intermediary device uses the duplicate status table stored in the storage unit 112 to confirm the duplicate status of each information base registrant ID included in the ID result information received by the ID receiving unit 833. At this time, there may be a situation where the following information base registrants exist, that is, the duplicate status of the information base registrant cannot be confirmed in the duplicate status table stored in the storage unit 112, for example, there is no matching information base registrant ID in the duplicate status table. In this case, the intermediary device can inquire about the duplicate status of only the information base registrant ID whose duplicate status is unknown from the management side device 9. And based on the duplicate result information received from the management side device 9, the data of the information base registrant ID whose duplicate status is unknown is registered, etc., to update the duplicate status table.
[0536] (10) In the third to fifth embodiments described above, the intermediary device performs duplication check on the ID by querying the management device 9 for the information base registrant ID included in the ID result information, or by referring to the duplication status table stored in the storage unit 112. Then, the intermediary device sends a metadata request to each information base 4a to 6a based on the duplication check result. However, the timing of duplication check is not limited to this.
[0537] For example, in the third embodiment, the intermediary device may send a metadata request to each information repository 4a to 6a instead of an ID request. Here, the intermediary device receives metadata from each information repository 4a to 6a in a format that allows duplication of data of the same person.
[0538] At this time, the intermediary device receives metadata from each of the information repositories 4a to 6a, and a list of information repository registrant IDs related to the individual whose data is included in the metadata.
[0539] Then, the intermediary device makes a duplicate confirmation request for the received list of information base registrant IDs to the management side device 9. As described above, duplicate confirmation may be performed after receiving the metadata.
[0540] (11) In the third to sixth embodiments, the mediation device receives Fig.28 The ID result information shown in the figure includes a list of combinations of information base registrant IDs and prices, but the ID result information is not limited to this. For example, the management device 9 of the registration management party 9a can also retain the following information: Fig.35 In this case, you can keep the following table: Fig.35 The repeated status table containing price information is shown. In this case, Fig.28 The ID result information shown may only contain a list of repository registrant IDs. Fig.30 The duplicate result information shown may include a list of combinations of information repository registrant IDs and prices for each information repository 4a to 6a in the form of ({ID, price}, {ID, price}, {ID, price} ...) Furthermore, the intermediary device may specify, based on the received list, IDs other than the lowest price as excluded IDs in the metadata.
[0541] (12) In the third to sixth embodiments described above, the information for identifying the individual whose personal data is stored in the information bases 4a to 6a, i.e., the information base registrant ID, is exemplified as the registration identification information. However, the registration identification information is not limited to this. The registration identification information may also be, for example, identification information assigned by each information base 4a to 6a to the personal data stored in the information base 4a to 6a.
[0542] (13) In the sixth embodiment, advertisement information is exemplified as the notification information, but the notification information is not limited thereto. For example, the notification information may be recommendation information for recommending a product or service to an individual.
[0543] (14) In the sixth embodiment, it is assumed that the destination information of the advertisement information is included in the personal data acquired from the information repositories 4a to 6a. However, if the destination information is not included in the personal data acquired from the information repositories 4a to 6a, the advertisement can be distributed as follows.
[0544] That is, the advertisement distribution device such as the user device 2 sends notification information such as advertisement information for different transmission targets to the information bases 4a to 6a indirectly through the intermediary device or directly without going through the intermediary device. In addition, the information bases 4a to 6a can send notification information received from the advertisement distribution device to the individual whose personal data is stored. That is, the advertisement distribution device such as the user device 2 can distribute advertisements to the individual whose personal data is stored through the information bases 4a to 6a.
[0545] In this case, the information repositories 4a-6a can distribute advertisements by utilizing certain connections they have with individuals who have stored their personal data.
[0546] Specifically, for example, the information base devices 4 to 6 of the information bases 4a to 6a may send notification information to the information processing terminals 11 to 17 of the individuals storing the personal data via e-mail, or may output notification information to the websites on the Internet browsed by the individuals. In addition, for example, the information base devices 4 to 6 may output notification information in application software installed in the information processing terminals 11 to 17 of the individuals, or may output notification information to terminals installed in areas such as stores visited by the individuals, or may send notification information to the individuals in various other ways.
[0547] According to the above configuration, even if the personal data acquired by the data user 2a or the like does not include the destination information, the data user 2a or the like can distribute advertisements to individuals.
[0548] (15) In the sixth embodiment described above, the user device 2 distributes advertisements, but the subject of advertisement distribution is not limited to this. For example, advertisement distribution may be performed by a device owned by a party other than the data user 2a, such as an advertisement distribution operator such as an advertising agency or a platform operator that distributes advertisements, or by an intermediary device. In this case, the device owned by the advertisement distribution operator or platform operator, or the intermediary device, etc. may perform advertisement distribution. Fig.40 Ad distribution process shown.
[0549] (16) In addition, for example, as described in (14) of [7. Other Embodiments] above, when an intermediary device or the like distributes advertisements to individuals whose personal data are stored in the information repositories 4a to 6a via the information repositories 4a to 6a, the intermediary device or the like may calculate an advertisement achievement index. The advertisement achievement index described herein is an index indicating the achievement related to advertisement distribution.
[0550] Specifically, for example, the intermediary device may calculate the number of unique users as an advertisement achievement indicator using the duplication result information acquired from the management device 9 of the registration management device 9a. The number of unique users is the number of users to whom the advertisement is distributed.
[0551] That is, when each information base 4a to 6a distributes advertisements to individuals whose data is stored in the information base 4a to 6a, there is a case where the same advertisement information is sent from multiple information bases 4a to 6a to individuals whose personal data is stored in multiple information bases 4a to 6a. Even in this case, by using the duplicate result information, it is possible to know to which individual the advertisement information is repeatedly sent, thereby calculating the number of unique users. In addition, the intermediary device can also calculate advertisement achievement indicators other than the number of unique users by using the duplicate result information.
[0552] In addition, for example, an intermediary device or the like can distribute advertisements based on duplicate result information when distributing advertisements via information libraries 4a to 6a. Specifically, for example, an intermediary device or the like sends an exclusion ID together with the transmission content to information library devices other than one information library device among multiple information library devices 4 to 6 so as not to repeatedly send the same advertisement information to the same person from multiple information libraries 4a to 6a. Here, the information library devices 4 to 6 do not distribute advertisements to individuals involved in the information library registrant ID specified by the received exclusion ID. Thus, information library devices other than the one information library device may not distribute advertisements. Of course, advertisement distribution can also be performed by other methods using duplicate result information so as not to repeatedly send the same advertisement information to the same person.
[0553] (17) In the ninth embodiment, the similarity threshold is set to a fixed value, but the similarity threshold is not limited to this, and the similarity threshold may be changed. In this case, for example, the similarity threshold may be changed as follows.
[0554] That is, Fig.51 As shown in FIG. 1 , if the similarity threshold value t is continuously changed, the number of successful associations will change. The number of successful associations is the number of combinations of personal data that are determined to be similar and are associated with each other.
[0555] like Fig.51 As shown in FIG. 1 , the larger the similarity threshold t is, the smaller the number of successful associations is. Therefore, if the similarity threshold t is set too large, it is possible that a combination of personal data that should be considered as the same person is not processed as the same person's personal data combination, resulting in omissions. In addition, if the similarity threshold t is set too small, on the contrary, a large number of combinations of personal data that are not from the same person may be generated. Therefore, it is desirable that the similarity threshold t is neither set too large nor too small.
[0556] Under the above idea, for example, we can consider Fig.51 When the similarity threshold t is continuously changed as shown in FIG. 1 , the value of the similarity threshold t when the change in the number of association successes reaches the maximum is adopted. MAX As the optimal threshold. In other words, t MAX It is the value of the similarity threshold t when the tangent slope of the function n=f(t) reaches the minimum when the number of successful associations n is regarded as a function n=f(t) of the similarity threshold t.
[0557] In addition, at t MAX When the value of is small, etc., if the similarity threshold t is set to t MAX If the personal data is associated with the data, a large number of personal data not from the same person will be combined. In this case, you can use the MAX The value of the similarity threshold t when the change in the number of association successes is large can be the value of the similarity threshold t when the slope of the tangent line of the function n=f(t) is the second smallest slope. 2MAX As the optimal threshold value. Of course, the value of the similarity threshold value t when the slope of the tangent line is the third, fourth, ... minimum slope can also be used as the optimal threshold value t.
[0558] In addition, the user can set the similarity threshold t to t MAX ,t 2MAX Any value among ,…, etc. can also be automatically set by the system.
[0559] In addition, for example, it is also possible to determine whether a plurality of personal data are similar to each other in the following manner. That is, the similarity between the personal data is calculated for the attributes such as age and gender of the personal data (in other words, the data items of the personal data). Then, when it is determined that the similarity of all or part of the attributes reaches or exceeds a threshold, it can be determined that the plurality of personal data are similar to each other.
[0560] In addition, for example, as described in detail below, there are coordinate axes corresponding to data items of personal data, and new coordinate axes are set in the coordinate space in which each personal data is expressed as a point and a vector. Then, when the similarity of each set coordinate axis reaches a threshold or more, it can be determined that multiple personal data are similar to each other, and further it can be determined that they are personal data related to the same person. In addition, for example, the similarity threshold can be changed in the same manner as described above, and the optimal similarity threshold can be calculated. Specifically, the similarity threshold described below can be calculated.
[0561] That is, Fig.52 As shown, first, the data set of personal data acquired from the information repositories 4a to 6a is plotted in the coordinate space. Fig.52 Each data point in represents personal data. In addition, Fig.52 Each coordinate axis of the coordinate space corresponds to each attribute of the personal data (i.e., each data item). For example, for the coordinate axis corresponding to the data item "Gender = Male", each personal data takes the value of 0 or 1 depending on whether it is male or not. In addition, for the coordinate axis corresponding to the data item "Amount of money spent on magazines purchased in three months", the value of each personal data is the corresponding purchase amount.
[0562] Furthermore, by performing principal component analysis or manifold learning on the data set, a new coordinate axis that better describes the data set is formed. Fig.52 In the figure, the x1 axis and the x2 axis are new axes.
[0563] Furthermore, a similarity threshold t=(t1, t2, ...) is set for each new coordinate axis. The similarity threshold t mentioned here can be, for example, a threshold related to the difference in attribute values of each component of two personal data. Specifically, for example, a personal data A is represented by coordinates x in the new coordinate axis. A =(x 1A , x 2A , …). Another personal data B is represented by coordinate x in the new coordinate axis. B =(x 1B , x 2B In this case, when the absolute value of the difference between the components shown below is less than or equal to the similarity threshold, it can be determined that the two personal data A and B are similar to each other.
[0564] Δx1≡|x 1A -x 1B |≦t1 and Δx2≡|x 2A -x 2B |≦t2…
[0565] Moreover, if Fig.53 As shown, when the similarity threshold t=(t1, t2, ...) of each component t i When the change is continuous, the similarity threshold t can be used when the change in the number of association successes n reaches the maximum MAX =(t MAX1 , t MAX2 , …) etc. as the optimal threshold.
[0566] By dynamically changing the similarity threshold t as described above, it is possible to set an optimal similarity threshold t for each personal data set, thereby reducing the possibility of missing a combination of personal data that should be considered as a combination of personal data of the same person, or generating a large number of combinations of personal data that do not come from the same person.
[0567] In addition, it is not necessary to perform principal component analysis or manifold learning to set new coordinate axes. However, by setting new coordinate axes, each person's data can usually be expressed as coordinates with fewer dimensions. Therefore, the amount of calculation in computer processing can be reduced, and the processing speed can be increased.
[0568] (18) In each of the above-mentioned embodiments, the intermediary device directly sends the delivery data based on the personal data obtained from the information base 4a~6a to the user device 2. However, the method of sending the delivery data to the data user 2a is not limited to this. For example, the intermediary device temporarily sends the delivery data to another device that is different from both the intermediary device and the user device. Then, the delivery data can be sent to the user device 2 via the other device. The situation in which the delivery data is sent from the intermediary device to the user device 2 via another device is also included in the scope of "the intermediary device sends the delivery data to the user device 2" described in this application.
[0569] (19) In addition to the above-mentioned intermediary device, the present disclosure may be implemented in various ways, such as a system in which the intermediary device is a constituent element, a program for causing a computer to function as the intermediary device, a non-transferable physical recording medium such as a semiconductor memory storing the program, a method for collecting personal data, etc.
[0570] (20) Multiple functions of one constituent element in each of the above-mentioned embodiments may be realized by multiple constituent elements, or one function of one constituent element may be realized by multiple constituent elements. In addition, multiple functions of multiple constituent elements may be realized by one constituent element, or one function realized by multiple constituent elements may be realized by one constituent element. In addition, part of the structure of each of the above-mentioned embodiments may be omitted. At least part of the structure of each of the above-mentioned embodiments may be added to the structure of each of the other embodiments, or replaced by the structure of each of the other embodiments. Furthermore, all modes included in the technical idea determined by the sentences recorded in the claims are embodiments of the present disclosure.
Claims
1. An intermediary device, It is characterized in that have: a request acquisition unit configured to acquire request information including a condition of personal data required by a data user, that is, an object condition; a duplicate confirmation acquiring unit configured to acquire duplicate confirmation information, the duplicate confirmation information being information indicating that first personal data managed by a first personal data manager and second personal data managed by a second personal data manager are personal data related to the same person, wherein the second personal data manager is a personal data manager different from the first personal data manager; a determination unit configured to determine a collection plan based on the duplicate confirmation information, the collection plan indicating conditions related to personal data collected from a plurality of personal data managers including the first personal data manager and the second personal data manager; and a data acquisition unit configured to acquire personal data according to the fundraising plan determined by the determination unit, the determination unit determines the following solicitation scheme, namely, soliciting any one of the first personal data and the second personal data indicated by the duplicate confirmation information as personal data related to the same person, Each of the plurality of personal data managers assigns a predetermined identification information, namely, registration identification information, to an individual whose personal data is stored at the personal data manager or to the personal data of the individual. The duplicate confirmation information is information indicating the registered identification information related to the same person in the first personal data manager and the second personal data manager.
2. The mediation device according to claim 1, It is characterized in that The determination section determines the fundraising scheme based on the duplicate confirmation information in such a manner that the distribution of personal data collected through the fundraising scheme approaches the distribution of original data.
3. The mediation device according to claim 1, It is characterized in that The determination unit determines the following procurement plan, namely, procurement of the cheaper one of the first personal data and the second personal data.
4. The mediation device according to any one of claims 1 to 3, It is characterized in that The duplicate confirmation acquisition unit acquires the duplicate confirmation information from an external device that manages the duplicate confirmation information or is capable of generating the duplicate confirmation information.
5. The mediation device according to any one of claims 1 to 3, It is characterized in that further comprising a storage unit configured to store the duplicate confirmation information, The duplicate confirmation acquisition unit acquires the duplicate confirmation information from the storage unit.
6. The mediation device according to any one of claims 1 to 3, It is characterized in that Each of the plurality of personal data managers is an information repository.
7. A system, It is characterized in that The system comprises the mediation device according to any one of claims 1 to 3, and further comprises: a notification information acquisition unit configured to acquire notification information corresponding to the personal data acquired by the data acquisition unit, the notification information being information to be notified to an individual whose personal data is deposited at the personal data management unit; and A notification information sending unit is configured to send the notification information acquired by the notification information acquiring unit.
8. A computer program product that enables a computer to function as an intermediary device, wherein: The intermediary device comprises: a request acquisition unit configured to acquire request information including a condition of personal data required by a data user, that is, an object condition; a duplicate confirmation acquisition unit configured to acquire duplicate confirmation information indicating that first personal data managed by the first personal data manager and second personal data managed by the second personal data manager are personal data related to the same person, in, The second personal data manager is a personal data manager different from the first personal data manager; a determination unit configured to determine a collection plan based on the duplicate confirmation information, the collection plan indicating conditions related to personal data collected from a plurality of personal data managers including the first personal data manager and the second personal data manager; as well as a data acquisition unit configured to acquire personal data according to the fundraising plan determined by the determination unit, and / or to transmit the delivery data determined by the determination unit to the user device, the determination unit determines the following solicitation scheme, namely, soliciting any one of the first personal data and the second personal data indicated by the duplicate confirmation information as personal data related to the same person, Each of the plurality of personal data managers assigns a predetermined identification information, namely, registration identification information, to an individual whose personal data is stored at the personal data manager or to the personal data of the individual. The duplicate confirmation information is information indicating the registered identification information related to the same person in the first personal data manager and the second personal data manager.
