JP5726711B2 - Information distribution system and information distribution method - Google Patents

Description

  The present invention relates to an information distribution system and an information distribution method for protecting privacy and preventing information leakage.

  Conventionally, in order to distribute the most suitable information according to the user's situation, the event information provided by the event information provider is accumulated, and the event information is automatically distributed to the user that matches the event information provision conditions. Has been provided (for example, Patent Document 1).

  A schematic diagram of a conventional information distribution system is shown in FIG. The conventional information distribution system includes a user terminal 101, an event information providing server 102, a user information holding server 103, and an event information distribution server 104. These are connected to each other by a network. The event information providing server 102 is a server that provides event information to be provided to the user terminal 101. The event information is provided to the user terminal 101 when information related to the user of the user terminal 101 (hereinafter referred to as user information) satisfies a predetermined condition. The user information holding server 103 has user information related to the user of the user terminal 101. The event information distribution server 104 acquires event information from the event information providing server 102. In addition, the event information distribution server 104 acquires user information from the user information holding server 103 and determines whether or not the user information satisfies a predetermined condition of the event information. When the predetermined condition is satisfied, the event information distribution server 104 distributes the corresponding event information of the event information providing server 102 to the user terminal 101.

JP 2004-348446 A

  However, in the conventional information distribution system, since the user information is transmitted from the user information holding server to the event information distribution server, the event information distribution server can grasp the user information, and there is a problem from the viewpoint of privacy protection. there were. In addition, there is a problem that user information may be leaked when communication between the user information holding server and the event information distribution server is intercepted.

  Accordingly, an object of the present invention made in view of the above-described problems is an information distribution system capable of protecting privacy and preventing information leakage without transmitting user information from a user information holding server to an event information distribution server. And providing an information distribution method.

In order to solve the above problems, an information distribution system according to the present invention is an information distribution system including an event information distribution server that distributes event information to a user terminal, the event information and event information distribution related to the event information. The event information distribution server for storing conditions, and a user information holding server for storing the event information, event information distribution conditions and user information related to the event information, and the event information distribution server Requesting the user information holding server to extract the user information that conforms to the event information distribution conditions, the user information holding server compares the user information with the event information distribution conditions, For user information that meets the event information distribution conditions, the distribution target has only information necessary for distributing the event information. A user information list is transmitted to the event information distribution server, and the event information distribution server, based on the distribution target user information list received from the user information holding server and the event information distribution condition, The information is distributed to the user terminal, and the event information distribution server stores a distribution destination address for distributing the event information and a user ID associated with the distribution destination address in association with each other, and the user The ID is different from the ID related to the user information held by the user information holding server, and the information distribution system further includes an ID conversion server that stores the user ID and the ID in association with each other, The user information holding server transmits the ID of the user information related to the distribution target user information list to an ID conversion server, and the ID conversion server It converts the ID to the user ID, and transmits the user ID to the event information delivery server.

The information distribution method according to the present invention is an information distribution method including an event information distribution server for distributing event information to a user terminal, wherein the event information distribution server includes the event information and the event information related to the event information. Storing a distribution condition; a user information holding server storing the event information; an event information distribution condition related to the event information; and a user information; and the event information distribution server including the user. Requesting the information holding server to extract the user information that conforms to the event information distribution condition, and the user information holding server compares the user information with the event information distribution condition, and the event information Distribution target that has only information necessary for distribution of the event information for user information that meets the distribution conditions A step of transmitting a user information list to the event information distribution server, the event information distribution server based on the distribution target user information received from the user information holding server, and the event information distribution condition, viewed including the steps, a to deliver the event information to the user terminal, the event information delivery server further includes a destination address for delivering the event information, and a user ID according to the destination address The user ID is different from the ID related to the user information held by the user information holding server, and the information distribution method further includes an ID conversion server and the user ID. The user information holding server includes the step of associating and storing the ID, and And transmitting the ID of the user information to the ID conversion server, the ID conversion server converts the ID to the user ID, steps and the including for transmitting the user ID in the event information delivery server It is characterized by that.

  According to the information distribution system and the information distribution method of the present invention, privacy information and information leakage can be prevented without transmitting user information from the user information holding server to the event information distribution server.

1 is a block diagram of an information distribution system according to an embodiment of the present invention. It is a figure which shows the example of the event information table 21a, the event information delivery condition table 22a, the event information table 21b, and the event information delivery condition table 22b. It is a figure which shows the example of the delivery user information table. It is a figure which shows the example of the ID conversion table 52 and the server ID corresponding table 53. It is a flowchart which shows the prior operation | movement of the information delivery system which concerns on one Embodiment of this invention. It is a figure which shows the example of the possession user information table 31, the object comparison process permission information table 32, the event information table 33, and the event information delivery condition table 34. It is a flowchart which shows the prior operation | movement of the information delivery system which concerns on one Embodiment of this invention. It is a figure which shows the example of the event information table 41 and the event information delivery condition table 42. FIG. It is a flowchart which shows operation | movement of the information delivery system which concerns on one Embodiment of this invention. It is a figure which shows the example of the object division | segmentation conversion table 35, ID conversion reception table 51, and the delivery information table 45. It is a schematic diagram of the conventional information delivery system.

  Embodiments of the present invention will be described below.

(Embodiment)
FIG. 1 is a block diagram of an information distribution system according to an embodiment of the present invention. An information distribution system according to an embodiment of the present invention includes a user terminal 1, an event information provision server 2a, an event information provision server 2b, a user information holding server 3, an event information distribution server 4, and an ID conversion. And a server 5, which are connected via a network. In addition, although the structure provided with the event information provision server 2a and the event information provision server 2b as a server which provides event information is shown, it is not restricted to this, Even if there are more than two servers which provide event information, two It may be less.

  The user terminal 1 receives distribution of predetermined event information from the event information distribution server 4 via the network. The user terminal 1 is preferably a mobile phone, a smartphone, a personal computer, or the like.

  The event information providing server 2a includes an event information table 21a, an event information distribution condition table 22a, a control unit 23a, and a communication unit 24a.

  The event information table 21 a stores event information provided to the user terminal 1. FIG. 2A is an example of the event information table 21a. The event information table 21a stores an event ID, event information, and event detailed information of the event information. The event ID is an identification number for uniquely specifying the stored event information. For example, the event information table 21a stores event ID “00100001”, event information “Volunteer Recruitment Notice”, and event detailed information “*******”. The detailed event information is described as “******”, but in reality, detailed information related to the event information, for example, the date and time of the event, the location of the event, and the like are stored.

  The event information distribution condition table 22a stores distribution conditions for distributing each event information stored in the event information table 21a. The event information is provided only to users who satisfy the event information distribution condition. FIG. 2B is an example of the event information distribution condition table 22a. The event information distribution condition table 22a stores an event ID, a distribution classification, a distribution condition, a target range, and a target area. The distribution category is an identifier that uniquely represents the type of event distribution condition related to a predetermined event ID. The distribution condition indicates an age condition among the event information distribution conditions. The target range is a numerical range of distribution conditions. The target area indicates a regional condition among the event information distribution conditions. In other words, the event information distribution condition includes an age condition and a regional condition.

  For example, the event information distribution condition table 22a stores an event ID “00100001”, a distribution classification “target 1”, a distribution condition “adult”, a target range “18 to 65”, and a target area “A city”. That is, “Notification of Volunteer Information” of event ID “00100001” in FIG. 2A is an adult, that is, an age range of 18 to 65 years old, and A city is an address. This is information intended for users.

  The control unit 23a performs various controls related to the event information providing server 2a. The control unit 23a includes an event information / distribution target condition extraction unit 231a and an event information / distribution target condition transmission unit 232a. The event information / distribution target condition extraction unit 231a extracts event information and event information distribution conditions related to the event information from the event information table 21a and the event information distribution condition table 22a. The event information / distribution target condition transmission unit 232a transmits the event information extracted by the event information / distribution target condition extraction unit 231a and the event information distribution condition related to the event information via the communication unit 24a. 3 to send. The communication unit 24a transmits and receives information related to the event information providing server 2a to and from the user information holding server 3 and the event information distribution server 4 via the network.

  The event information providing server 2b includes an event information table 21b, an event information distribution condition table 22b, a control unit 23b, and a communication unit 24b. Each configuration of the event information providing server 2b has the same function as the configuration of the same name related to the event information providing server 2a, and a description thereof will be omitted. 2C shows an example of the event information table 21b, and FIG. 2D shows an example of the event information distribution condition table 22b.

  The user information holding server 3 includes a holding user information table 31, a target comparison processing permission information table 32, an event information table 33, an event information distribution condition table 34, a target classification conversion table 35, a control unit 36, And a communication unit 37.

  The retained user information table 31 stores user information related to the user of the user terminal 1. A unique user ID is assigned to each user information. The target comparison process permission information table 32 stores process permission information indicating whether or not the extraction process of the user information stored in the possessed user information table 31 is permitted. That is, only the information permitted in the target comparison process permission information table 32 among the user information in the retained user information table 31 can be used in the information distribution system. By doing in this way, it is possible to prevent the user information that the user does not want to use in the user information holding server 3 from being used.

  The event information table 33 stores event information received from the event information providing server 2a and / or the event information providing server 2b. The event information distribution condition table 34 stores the event information distribution conditions received from the event information providing server 2a and / or the event information providing server 2b.

  The target classification conversion table 35 includes user information to which event information extracted by the user information extraction unit 364 described later based on the possessed user information table 31, the event information table 33, and the event information distribution condition table 34 is distributed. (Hereinafter referred to as distribution target user information). The distribution target user information includes only information necessary for distribution of the event information among the user information to be distributed. For example, it is changed to the name of the corresponding event information distribution condition and stored in the target category conversion table 35.

  The control unit 36 performs various controls related to the user information holding server 3. The control unit 36 includes a possessed user information acquisition unit 361, a target comparison processing permission information acquisition unit 362, an event information / distribution target condition request unit 363, a user information extraction unit 364, an ID conversion request unit 365, A distribution target user information list transmission unit 366.

  The owned user information acquisition unit 361 acquires user information based on input information from an operation unit (not shown) on the user information holding server 3 and stores the user information in the held user information table 31. To do.

  The target comparison processing permission information acquisition unit 362 acquires target comparison processing permission information based on input information from an operation unit (not shown) on the user information holding server 3 and stores the target comparison processing permission information table 32 in the target comparison processing permission information table 32. Stores comparison processing permission information.

  The event information / distribution target condition requesting unit 363 requests the event information and event information distribution conditions related to the event information from the event information providing server 2a and / or the event information providing server 2b.

  The user information extraction unit 364 extracts distribution target user information that matches the event distribution target condition of the event information based on the possessed user information table 31, the event information table 33, and the event information distribution condition table 34. Further, the user information extraction unit 364 stores the extracted user information in the target category conversion table 35.

  The ID conversion request unit 365 transmits a request for converting the user ID on the user information holding server 3 to the user ID on the event information distribution server 4 to the ID conversion server 5. Also, the ID conversion reception ID issued in response to the request is received from the ID conversion server 5.

  The distribution target user information list transmission unit 366 transmits the information stored in the target classification conversion table 35 and the ID conversion reception ID to the event information distribution server 4.

  The communication unit 37 transmits / receives predetermined information to / from the event information providing server 2, the event information distribution server 4, and the ID conversion server 5 via the network.

  The event information distribution server 4 includes an event information table 41, an event information distribution condition table 42, a distribution target user list file 43, a distribution user information table 44, a distribution information table 45, a control unit 46, a communication Part 47.

  The event information table 41 stores event information received from the event information providing server 2a and / or the event information providing server 2b. The event information distribution condition table 42 stores the event information distribution conditions received from the event information providing server 2a and / or the event information providing server 2b.

  The distribution target user list file 43 stores information of the target classification conversion table 35 transmitted from the user information holding server 3. That is, the contents of the distribution target user list file 43 are the same as the target classification conversion table 35.

  The distribution user information table 44 stores a user ID and a distribution address of the user related to the user ID. Preferably, the distribution destination address is an e-mail address. That is, the event information distribution server 4 refers to the distribution user information table 44 and transmits event information to an e-mail address of a predetermined user. Here, the user ID is an identification number for uniquely identifying the user on the event information distribution server 4.

  FIG. 3 shows an example of the distribution user information table 44. For example, the distribution user information table 44 stores a user ID “1234567” and a distribution address “Higashi.ichiro@aaa.bb.cc”.

  The distribution information table 45 stores which event information is transmitted to which user. The control unit 46 performs various controls related to the event information distribution server 4. The control unit 46 includes an event information / distribution target condition request unit 461, a user extraction processing request unit 462, a distribution target user information list request unit 463, a post-conversion ID request unit 464, and a distribution information generation unit 465. And a distribution information transmitting unit 466.

  The event information / distribution target condition request unit 461 requests event information and event information distribution conditions related to the event information from the event information providing server 2a and / or the event information providing server 2b.

  The user extraction processing request unit 462 transmits a request for extraction processing of a user who provides the event information stored in the event information table 41 to the user information holding server 3.

  The distribution target user information list request unit 463 transmits a request for a list of distribution target user information to the user information holding server 3. The distribution target user information list request unit 463 receives the information stored in the target classification conversion table 35 and the ID conversion reception ID from the user information holding server 3 and stores them in the distribution target user list file 43. .

  The post-conversion ID request unit 464 transmits the ID conversion reception ID to the ID conversion server 5 and requests the post-conversion ID related to the ID conversion reception ID.

  The distribution information generation unit 465 determines which event information is transmitted to which user based on the post-conversion ID list, the distribution target user information list file 43, the event information table 41, and the event information distribution condition table 42. , Generate delivery information. Further, the distribution information generation unit 465 stores the distribution information in the distribution information table 45 with the current date and time information added thereto.

  The distribution information transmission unit 466 acquires the transmission destination email address of each user ID from the distribution user information table 44. Then, the distribution information transmission unit 466 transmits the distribution information stored in the distribution information table 45 to the user terminal 1 based on the mail address of the transmission destination.

  The communication unit 47 transmits / receives predetermined information to / from the event information providing server 2a, the event information providing server 2b, the user information holding server 3 and the ID conversion server 5 via the network.

  The ID conversion server 5 includes an ID conversion reception table 51, an ID conversion table 52, a server ID correspondence table 53, a control unit 54, and a communication unit 55.

  The ID conversion reception table 51 stores ID conversion reception IDs issued by an ID conversion request reception unit 541 described later.

  The ID conversion table 52 stores the user ID in the user information holding server 3 and the user ID in the event information distribution server 4 in a one-to-one correspondence.

  FIG. 4A shows an example of the ID conversion table 52. The ID conversion table 52 in FIG. 4A includes a post-conversion ID, a user ID 1, a user ID 2, and a user ID 3.

  Here, the post-conversion ID is a user ID in the event information distribution server 4, and user ID 1 to user ID 3 are user IDs in the user information holding server 3. Here, an example in which there are two user information holding servers in addition to the user information holding server 3 is shown. Thus, the ID conversion table 52 is useful when there are a plurality of user information holding servers and the user IDs of the servers are different.

  The server ID correspondence table 53 stores the user ID 1, the user ID 2, and the user ID 3 in the ID conversion table 52 in association with the IDs of the user information holding servers used.

  FIG. 4B is an example of the server ID correspondence table 53. The server ID correspondence table 53 stores a server ID and a user ID in association with each other. For example, a server ID “101” and a user ID “user ID1” are stored in association with each other. The server ID is an identifier for specifying the user information holding server, and the server ID “101” is assigned to the user information holding server 3. That is, the user ID 1 is used in the user information holding server 3.

  The control unit 54 performs various controls related to the ID conversion server 5. The control unit 54 includes an ID conversion request receiving unit 541, an ID conversion unit 542, and a post-conversion ID list transmission unit 543.

  When receiving an ID conversion request from the user information holding server 3, the ID conversion request reception unit 541 pays out an ID conversion reception ID and stores the payout ID conversion reception ID in the ID conversion reception table 51.

  The ID conversion unit 542 converts the user ID on the user information holding server into the event information distribution server 4 based on the ID conversion reception ID, the ID conversion reception table 51, the ID conversion table 52, and the server ID correspondence table 53. Convert to the above user ID.

  The post-conversion ID list transmission unit 543 transmits a post-conversion ID list (hereinafter referred to as post-conversion ID list) to the user information holding server 3.

  The communication unit 55 transmits / receives predetermined information to / from the user information holding server 3 and the event information distribution server 4 via the network.

  FIG. 5 shows the prior operation of the information distribution system according to the embodiment of the present invention, that is, the user information holding server 3 stores user information and target comparison processing permission information, and communicates with the event information providing server 2a. The predetermined information is stored in the event information table 41 and the event information distribution condition table 42. Here, although the operation | movement which communicates with the event information provision server 2a is illustrated, it communicates with the event information provision server 2b, and predetermined | prescribed information may be stored.

  First, the possessed user information acquisition unit 361 of the user information possessing server 3 obtains user information based on input information from an operation unit (not shown) on the server, and uses that information in the retained user information table 31. Person information is stored (step S11). Here, it is based on the input information from the operation unit on the server. However, the present invention is not limited to this, and the information may be obtained via a network.

  FIG. 6A shows the possessed user information table 31 in which user information is stored in this way. The owned user information table 31 stores a user ID and information on each attribute item, that is, name, age, sex, and address. For example, in the possessed user information table 31, the name “Ichiro Higashi”, age “30”, gender “male”, and address “A city” are stored as information relating to the user ID “11111”.

  Subsequently, the target comparison processing permission information acquisition unit 362 acquires target comparison processing permission information based on input information from an operation unit (not shown) on the server, and stores the target comparison processing permission information in the target comparison processing permission information table 32. The permission information is stored (step S22). Here, it is based on the input information from the operation unit on the server. However, the present invention is not limited to this, and the information may be obtained via a network.

  FIG. 6B shows the target comparison process permission information table 32 in which the process permission information is stored in this way. The target comparison process permission information table 32 stores a user ID, an attribute item, and process permission information. The process permission information is information indicating whether or not the extraction process of information related to a predetermined attribute item is permitted. When the information extraction process related to the predetermined attribute item is not permitted, the user information holding server 3 cannot extract the information related to the predetermined attribute item. For example, the target comparison processing permission information table 32 stores a user ID “11111”, attribute items “name”, and “none”. In FIG. 6B, the processing permission information is “present” when the attribute item is permitted, and the processing permission information is denoted as “none” when the attribute item is not permitted.

  Subsequently, the event information / distribution target condition request unit 363 of the user information holding server 3 requests the event information and the event information distribution condition related to the event information to the event information providing server 2a via the communication unit 37. (Step S13). The event information providing server 2a receives the event information and the event information distribution target condition via the communication unit 24a (step S14).

  Subsequently, the event information / distribution target condition extraction unit 231a of the event information providing server 2a extracts the event information and the event information distribution condition related to the event information from the event information table 21a and the event information distribution condition table 22a. (Step S15).

  Subsequently, the event information / distribution target condition transmission unit 232a transmits the event information extracted by the event information / distribution target condition extraction unit 231a and the event information distribution condition related to the event information via the communication unit 24a. It transmits to the information holding server 3 (step S16). The event information / distribution target condition request unit 363 of the user information possessing server 3 receives the event information and the event information distribution condition related to the event information via the communication unit 37 (step S17).

  Subsequently, the event information / distribution target condition request unit 363 of the user information possessing server 3 sets the received event information and the event information distribution condition related to the event information as the event information table 33 and the event information distribution condition table, respectively. 34 (step S18).

  The event information table 33 and the event information distribution condition table 34 in which the event information and the event information distribution conditions related to the event information are stored in this way are shown in FIGS. 6C and 6D, respectively.

  As shown in FIG. 6C, the event information table 33 stores a server ID, an event ID, event information, and event detailed information. The server ID represents an ID related to the event information providing server that has transmitted the event information. Here, it is assumed that the server ID of the event information providing server 2a is 001. For example, the event information table 33 stores server ID “001”, event ID “00100001”, event information “Notice of Volunteer Recruitment”, and event detailed information.

  As shown in FIG. 6D, the event information distribution condition table 34 stores a server ID, an event ID, a distribution classification, a distribution condition, a target range, and a target area. For example, the event information distribution condition table 34 includes a server ID “001”, an event ID “00100001”, a distribution classification “target 1”, a distribution condition “adult”, a target range “18 to 65”, and a target area “A city”. Is stored.

  FIG. 7 shows the prior operation of the information distribution system according to the embodiment of the present invention, that is, the event information distribution server 4 communicates with the event information providing server 2a, and the event information table 41 and the event information distribution condition table 42 have predetermined information. This is an operation for storing information. Here, although the operation | movement which communicates with the event information provision server 2a is illustrated, it communicates with the event information provision server 2b, and predetermined | prescribed information may be stored.

  First, the event information / distribution target condition request unit 461 of the event information distribution server 4 requests the event information and the event information distribution condition related to the event information to the event information providing server 2a via the communication unit 47 ( Step S21). The event information providing server 2a receives the event information and the event information distribution target condition via the communication unit 24a (step S22).

  Subsequently, the event information / distribution target condition extraction unit 231a of the event information providing server 2a extracts the event information and the event information distribution condition related to the event information from the event information table 21a and the event information distribution condition table 22a. (Step S23).

  Subsequently, the event information / distribution target condition transmission unit 232a transmits the event information extracted by the event information / distribution target condition extraction unit 231a and the event information distribution condition related to the event information via the communication unit 24a. It transmits to the distribution server 4 (step S24). The event information / distribution target condition request unit 461 of the event information distribution server 4 receives the event information and the event information distribution condition related to the event information via the communication unit 47 (step S25).

  Subsequently, the event information / distribution target condition request unit 461 of the event information distribution server 4 sets the received event information and the event information distribution condition related to the event information as the event information table 41 and the event information distribution condition table 42, respectively. (Step S26).

  FIG. 8A and FIG. 8B respectively show the event information table 33 and the event information distribution condition table 34 in which the event information and the event information distribution conditions related to the event information are stored in this way.

  As shown in FIG. 8A, the event information table 41 stores a server ID, an event ID, event information, and event detailed information. The server ID represents an ID related to the event information providing server that has transmitted the event information. Here, it is assumed that the server ID of the event information providing server 2a is 001. For example, the event information table 41 stores server ID “001”, event ID “00100001”, event information “notice of volunteer recruitment”, and event detailed information.

  As shown in FIG. 8B, the event information distribution condition table 42 stores a server ID, an event ID, a distribution classification, a distribution condition, a target range, and a target area. For example, the event information distribution condition table 42 includes a server ID “001”, an event ID “00100001”, a distribution classification “target 1”, a distribution condition “adult”, a target range “18 to 65”, and a target area “A city”. Is stored.

  Next, the operation of the information distribution system according to the present invention will be described with reference to the flowchart shown in FIG.

  First, the user extraction processing request unit 462 of the event information distribution server 4 sends a request for extraction processing of a user who provides the event information stored in the event information table 41 via the communication unit 47. It transmits to the server 3 (step S31). At this time, the user extraction processing request unit 462 transmits the server ID “001” stored in the event information table 41 to the user information holding server 3.

  Subsequently, the user information holding server 3 receives a request for user extraction processing via the communication unit 37 (step S32).

  Subsequently, the user information extraction unit 364 of the user information holding server 3 extracts user information that matches the event distribution target condition of the event information related to the server ID “001” (step S33). Specifically, the user information extraction unit 364 first extracts a user ID and attribute items whose process permission information is “present” from the target comparison process permission information table 32. Next, the user information extraction unit 364 extracts the user information related to the extracted user ID and attribute item from the possessed user information table 31. Subsequently, the user information extraction unit 364 acquires the event information distribution condition related to the event information of the server ID “001” from the event information distribution condition table 34, compares the event information distribution condition with the user information, User information and user information to be distributed that match the event information distribution conditions are extracted.

  That is, the user information extraction unit 364, for example, from the possessed user information table 31, “adult”, the target range “18 to 65”, and the target area “A city” which are event distribution conditions related to the event ID “00100001”. The user information of the user ID “11111” that conforms to “” is acquired. Similarly, the user information extraction unit 364 reads, from the possessed user information table 31, “elderly”, which is the event distribution condition related to the event ID “00100002”, the target range “66 to 100” of the condition, and the target The user information of the user ID “22222” that matches the area “A city” is acquired. Similarly, the user information extraction unit 364 reads, from the possessed user information table 31, “elderly”, which is the event distribution condition for the event ID “00100003”, the target range “66 to 100” of the condition, and User information of the user ID “55555” that matches the target area “B city” is acquired.

  Subsequently, the user information extraction unit 364 stores the extracted distribution target user information in the target classification conversion table 35 (step S34). At this time, the user information extraction unit 364 stores only information necessary for the distribution of the event information among the distribution target user information, and changes the name to the corresponding event information distribution condition, for example, in the target classification conversion table 35. Store. In this way, even if the information of the target classification conversion table 35 is transmitted to the event information distribution server 4, the information is not user information itself, so that privacy is protected and the event information distribution conditions are the same. The event information distribution server 4 can determine that the original user information converted into the name of the information satisfies the event information distribution condition.

  An example of the target segment conversion table 35 in which predetermined information is stored in this way is shown in FIG. The target classification conversion table 35 stores the user ID, age, and address related to the extracted distribution target user information. For example, a user ID “11111”, an age “adult”, and an address “A city” are stored in the target category conversion table 35. Here, since the age related to the user ID “11111” is 30 years old, it matches the “adult” condition (target range 18 to 65) in the distribution condition of the event ID 00100001 of the information providing server 2a. Therefore, the age related to the user ID “11111” is converted to the same name “adult” as the distribution condition. Further, since the address relating to the user ID “11111” is “A city 1-1 chome 1-1”, it matches the condition “A city” of the target area in the distribution condition of the event ID 00100001 of the information providing server 2a. Therefore, the address relating to the user ID “11111” is converted to the same name “A city” as the distribution condition.

  Subsequently, the user information extraction unit 364 transmits a notification that the storage process has been completed to the event information distribution server 4 via the communication unit 37 (step S35). The event information distribution server 4 receives the notification via the communication unit 47 (step S36).

  Subsequently, the distribution target user information list request unit 463 of the event information distribution server 4 transmits a request for a list of distribution target user information to the user information holding server 3 via the communication unit 47 (step). S37). The user information holding server 3 receives the request via the communication unit 37 (step S38).

  Subsequently, the ID conversion request unit 365 of the user information holding server 3 sends a request for converting the user ID on the user information holding server 3 to the user ID on the event information distribution server 4 to the ID conversion server 5. On the other hand, it transmits via the communication part 37 (step S39). The ID conversion server 5 receives the user ID conversion request via the communication unit 55 (step S40).

  Subsequently, when receiving the request, the ID conversion request receiving unit 541 of the ID conversion server 5 pays out an ID conversion reception ID, and stores the payout ID conversion reception ID in the ID conversion reception table 51 (step S41). FIG. 10B shows information stored in the ID conversion reception table 51. The ID conversion reception table 51 includes an ID conversion reception ID, a server ID, and a pre-conversion ID. For example, the ID conversion reception table 51 stores an ID conversion reception ID “0001”, a server ID “101”, and a pre-conversion ID “11111”.

  Subsequently, the ID conversion request reception unit 541 transmits the ID conversion reception ID to the user information holding server 3 via the communication unit 55 (step S42). Then, the user information possessing server 3 receives the ID conversion acceptance ID via the communication unit 37 (step S43). Hereinafter, the ID conversion request reception unit 541 transmits “0001” as the ID conversion reception ID, and the user information holding server 3 receives the ID conversion reception ID.

  Subsequently, the distribution target user information list transmission unit 366 of the user information holding server 3 transmits the information stored in the target classification conversion table 35 and the ID conversion reception ID to the event information distribution server 4 and the communication unit 37. (Step S44). The distribution target user information list request unit 463 of the event information distribution server 4 receives the information and the ID conversion reception ID via the communication unit 47 (step S45).

  Subsequently, the distribution target user information list request unit 463 of the event information distribution server 4 stores the received information in the distribution target user list file 43 (step S46). The information stored in the distribution target user list file 43 is the same information as the target classification conversion table 35.

  Subsequently, the post-conversion ID request unit 464 transmits “0001”, which is an ID conversion acceptance ID, to the ID conversion server 5 via the communication unit 47 (step S47). The ID conversion server 5 receives the ID conversion reception ID via the communication unit 55 (step S48).

  Subsequently, the ID conversion unit 542 of the ID conversion server 5 determines the user information based on the received ID conversion reception ID, that is, “0001”, the ID conversion reception table 51, the ID conversion table 52, and the server ID correspondence table 53. The user ID on the holding server 3 is converted into the user ID on the event information distribution server 4 (step S49). Specifically, the ID conversion unit 542 first, based on the ID conversion reception ID “0001”, lists the server ID “101” and the pre-conversion IDs “11111”, “22222”, and “55555” from the ID conversion reception table 51. "Get. Next, the ID conversion unit 542 acquires the user ID type “user ID1” related to the server ID “101” from the server ID correspondence table 53. Then, the ID conversion unit 542 converts the user ID on the user information holding server 3 to the corresponding post-conversion ID based on the ID conversion table 52. That is, the ID conversion unit 542 converts the pre-conversion ID lists “11111”, “22222”, and “55555” into “1234567”, “1234666”, and “1357911”, respectively.

  Subsequently, the post-conversion ID list transmission unit 543 of the ID conversion server 5 transmits the post-conversion ID list to the user information holding server 3 via the communication unit 55 (step S50). The post-conversion ID requesting unit 464 of the event information distribution server 4 receives the post-conversion ID list via the communication unit 47 (step S51).

  Subsequently, the distribution information generation unit 465 of the event information distribution server 4 determines which user and which event based on the converted ID list, the distribution target user information list file 43, the event information table 41, and the event information distribution condition table 42. Determine whether to send information and generate distribution information. In addition, the distribution information generation unit 465 stores the distribution information in the distribution information table 45 by adding information on the current date and time (step S52). Specifically, the distribution information generating unit 465 converts the user ID in the distribution target user information list file into a converted ID, that is, a user ID on the event information distribution server 4 by using the converted ID list. Further, the distribution information generation unit 465 determines which event information is to be transmitted to which user based on the event information distribution condition table 42 and the distribution target user information list file.

  FIG. 10C is an example of the distribution information table 45. The distribution information table 45 stores a user ID, a server ID, an event ID, and a date and time. For example, the distribution information table 45 stores a user ID “1234567”, a server ID “001”, an event ID “00100001”, and a date and time “20 *******”. Although the date and time is described as “20 *******”, the date and time when the data is actually stored, for example, October 8, 2011 is stored.

  Further, the distribution information generation unit 465 determines the content and detailed information of the event information to be transmitted based on the event information table 41.

  Subsequently, the distribution information transmission unit 466 acquires the transmission destination mail address of each user ID from the distribution user information table 44 (step S53). Then, the distribution information transmitting unit 466 transmits the distribution information stored in the distribution information table 45 to each user terminal 1 through the communication unit 47 based on the mail address of the transmission destination (step S54). Specifically, for example, regarding the distribution information of the user ID “1234567”, the server ID “001”, the event ID “00100001”, and the date and time “20 *******” in the distribution hand information table 45. Then, the distribution mail address “Higashi.ichiro@aaa.bb.cc” associated with the user ID “1234567” is acquired from the distribution user information table 44, and the distribution information is transmitted to the mail address.

  As described above, according to the present invention, the user information holding server 3 extracts user information that meets the event distribution conditions based on the user information in the held user information table 31 and the event information distribution condition table 34. Among the user information, in order to provide the event information distribution server 4 with a distribution target user information list having only information necessary for event information distribution, the user information holding server 3 sends the user information to the event information distribution server 4. Without transmitting information, privacy protection and information leakage can be prevented.

  Note that if the user ID on the user information holding server 3 and the user ID on the event information distribution server 4 are the same, the ID conversion server 5 may not be provided.

  Although the present invention has been described based on the drawings and examples, it should be noted that those skilled in the art can easily make various modifications and corrections based on the present disclosure. Therefore, it should be noted that these variations and modifications are included in the scope of the present invention. For example, the functions included in each means, each step, etc. can be rearranged so that there is no logical contradiction, and a plurality of means, steps, etc. can be combined or divided into one. .

1 User terminal 2a, 2b Event information providing server 21a, 21b Event information table 22a, 22b Event information distribution condition table 23a, 23b Control unit 231a, 231b Event information / distribution target condition extraction unit 232a, 232b Event information / distribution target condition Transmission unit 24a, 24b Communication unit 3 User information holding server 31 Holding user information table 32 Target comparison processing permission information table 33 Event information table 34 Event information distribution condition table 35 Target classification conversion table 36 Control unit 361 Holding user information acquisition Unit 362 Target comparison processing permission information acquisition unit 363 Event information / distribution target condition request unit 364 User information extraction unit 365 ID conversion request unit 366 Distribution target user information list transmission unit 37 Communication unit 4 Event information distribution server 41 Event information Table 42 Event information distribution condition table 43 Distribution target user list file 44 Distribution user information table 45 Distribution information table 46 Control unit 461 Event information / distribution target condition request unit 462 User extraction processing request unit 463 Distribution target user information list Request unit 464 Conversion ID request unit 465 Distribution information generation unit 466 Distribution information transmission unit 47 Communication unit 5 ID conversion server 51 ID conversion reception table 52 ID conversion table 53 Server ID correspondence table 54 Control unit 541 ID conversion request reception unit 542 ID Conversion unit 543 ID list transmission unit after conversion 101 User terminal 102 Event information providing server 103 User information holding server 104 Event information distribution server

Claims (6)

An information distribution system comprising an event information distribution server for distributing event information to a user terminal,
The event information distribution server for storing the event information and event information distribution conditions relating to the event information;
A user information holding server for storing the event information, an event information distribution condition related to the event information, and user information;
Have
The event information distribution server requests the user information holding server to extract the user information that meets the event information distribution conditions,
The user information holding server compares the user information with the event information distribution condition, and for the user information conforming to the event information distribution condition, the distribution target includes only information necessary for the distribution of the event information. Send the user information list to the event information distribution server,
The event information distribution server distributes the event information to the user terminal based on the distribution target user information received from the user information holding server and the event information distribution condition ,
The event information distribution server stores a distribution destination address for distributing the event information and a user ID related to the distribution destination address in association with each other, and the user ID is stored by the user information holding server. Unlike the ID related to the user information we have,
The information distribution system further includes an ID conversion server that stores the user ID and the ID in association with each other,
The user information holding server transmits the ID of the user information related to the distribution target user information list to an ID conversion server,
The ID conversion server converts the ID into the user ID, and transmits the user ID to the event information distribution server . The user information holding server further stores processing permission information indicating whether or not to compare the user information with the event information distribution condition,
The information distribution system according to claim 1, wherein the user information holding server compares the user information with the event information distribution condition based on the processing permission information. The distribution target user information list includes information obtained by converting the user ID and the user information related to the user ID into a name of the corresponding event information distribution condition. 2. The information distribution system according to 2. An information distribution method comprising an event information distribution server for distributing event information to a user terminal,
The event information distribution server storing the event information and event information distribution conditions related to the event information;
A user information holding server storing the event information, an event information distribution condition related to the event information, and user information;
The event information distribution server requests the user information holding server to extract the user information that meets the event information distribution conditions;
The user information holding server compares the user information with the event information distribution condition, and for the user information that matches the event information distribution condition, the distribution target has only information necessary for the distribution of the event information. Transmitting a user information list to the event information distribution server;
The event information distribution server distributes the event information to the user terminal based on the distribution target user information list received from the user information holding server and the event information distribution condition;
Only including,
The event information distribution server further includes a step of storing a distribution destination address for distributing the event information and a user ID related to the distribution destination address, wherein the user ID is the user Unlike the ID related to user information held by the information holding server,
The information distribution method further includes a step in which an ID conversion server stores the user ID and the ID in association with each other,
The user information holding server transmitting the ID of the user information related to the distribution target user information list to an ID conversion server;
The ID conversion server converts the ID into the user ID, and transmits the user ID to the event information distribution server;
Information distribution method characterized by including Mukoto a. The user information holding server further includes a step of storing processing permission information indicating whether or not to compare the user information with the event information distribution condition;
5. The information distribution method according to claim 4, wherein the user information holding server compares the user information with the event information distribution condition based on the processing permission information. The distribution target user information list includes information obtained by converting the user ID and the user information related to the user ID into the corresponding event information distribution condition name. 5. The information delivery method according to 5.

Images