JP2013008331A - Device for generating friend relationship and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device and a method for making a new human relationship more accurately.SOLUTION: A friend relationship creation device 1 includes: an action record reception part 11 which receives records of actions made on a terminal 2 in order; an event participant addition part 12 which extracts a participant in an event previously stored in an event participant database 21 from the action records, and adds the participant to the event participant database 21; a common event number totaling part 13 which refers to the event participant database 21, and totals the number of events that one participant and another participant both participate sequentially by other participants; and a friend addition part 14 which adds a participant who has the number, totaled by the common event number totaling part 13, larger than a predetermined number as a friend.

Description

  The present invention relates to an apparatus and method for generating friendships.

  In recent years, an increasing number of users use a social network system (hereinafter referred to as SNS), which is a service using a community-type website. In SNS, communication between friends and acquaintances can be facilitated on the basis of connections in actual social life. In addition, even if there is no connection in actual social life, a new human relationship can be established through a connection such as a hobby, a preference, a residential area, a school of origin, or a connection of “friends of friends” (for example, patents) Reference 1).

JP 2011-048445 A

  However, even if hobbies, preferences, and the like between one user and other users are similar, these users do not necessarily have a sociable relationship.

  An object of this invention is to provide the apparatus and method which can construct | assemble a new human relationship more correctly.

  The present invention provides the following solutions.

  (1) An event participant database in which information of participants participating in the event is stored, behavior record accepting means for sequentially accepting behavior records performed on the terminal, and extracting the event participants from the behavior records, An event participant adding means for adding the extracted participant to the event participant database, and referring to the event participant database, one participant and another participant are common to each of the event participants The common event number counting means that sequentially counts the number of events to be participated for each of the other participants, and a participant whose number counted by the common event number counting means is a predetermined number or more is added as a friend And a friend adding means.

  According to the invention described in (1), the number of actions performed in common is sequentially counted and added as a friend when the number is large. Therefore, it is possible to provide an apparatus capable of constructing a new human relationship more accurately and in real time than the conventional apparatus.

  (2) The apparatus according to (1), wherein the common event count counting unit refers to the event participant database, and for each participant of the event, with one participant and another participant. Is a device that sequentially counts the number of events that participate in common during a predetermined time for each of the other participants.

  According to the invention described in (2), the number of actions performed in common during a predetermined time is sequentially counted and added as a friend when the number is large. Therefore, it is possible to provide an apparatus that can construct a new human relationship more accurately and in real time.

  (3) A method in which a computer generates a friendship, wherein the computer includes an event participant database in which information of participants who participate in an event is stored, and behavior records that sequentially accept behavior records performed at a terminal Receiving the event from the action record, adding the extracted participant to the event participant database, referring to the event participant database, and participating in the event For each participant, a common event number counting step for sequentially counting the number of events that one participant and other participants participate in common for each of the other participants, and the common event number counting step The apparatus which performs the friend addition process which adds the participant whose number to total totals more than predetermined number as a friend.

  According to the method described in (3), the same effect as in (1) can be expected by implementing the invention according to the method.

  ADVANTAGE OF THE INVENTION According to this invention, the apparatus and method which can construct | assemble a new human relationship more correctly can be provided.

It is a figure which shows the whole structure for demonstrating the friend relationship production | generation apparatus 1 which concerns on embodiment of this invention. It is a figure which shows the event participant database 21 which concerns on embodiment of this invention. It is a figure which shows the social graph database 22 which concerns on embodiment of this invention. It is a flowchart of the friend relationship production | generation apparatus 1 which concerns on embodiment of this invention. It is a figure which shows the example of the write-in to the event participant database 21 when one participant participates in event "A". It is a figure which shows the example of the writing to the social graph database 22 after that. It is a Venn diagram showing an example. It is a figure following FIG.

[overall structure]
Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing an overall configuration for explaining a friendship generation device 1. The friend relationship generation device 1 is connected via a network to an action record management server 3 including an action record database 31 in which action records performed at the terminal 2 are stored. The action record database 31 is a database for managing generally well-known logs. The action record includes all operations performed from the terminal 2 via the network, and includes all operations such as transmission / reception of e-mails, reception of Web pages, registration of schedules, purchase of articles, and viewing of videos. .

  The friendship generation device 1 includes a control unit 10 that comprehensively controls each function related to the friendship generation device 1 and a storage unit 20 in which information necessary for the operation of the control unit 10 is stored. The control unit 10 includes an action record receiving unit 11 that sequentially connects to the action record database 31 and sequentially receives action records performed on the terminal 2. The action record accepting unit 11 functions as an action record accepting unit.

  The friendship generation device 1 includes a control unit 10 that comprehensively controls each function related to the friendship generation device 1 and a storage unit 20 in which information necessary for the operation of the control unit 10 is stored. The control unit 10 includes an action record receiving unit 11 that sequentially connects to the action record database 31 and sequentially receives action records performed on the terminal 2. The action record accepting unit 11 functions as an action record accepting unit.

  The storage unit 20 includes an event participant database 21 in which information on participants who participate in the event is stored. Moreover, the control part 10 extracts the participant of the event memorize | stored in the event participant database 21 from the action record which the action record reception part 11 received, and adds the extracted participant to the event participant database 21 A person adding unit 12 is provided. The event participant database 21 and the event participant adding unit 12 function as event participant adding means.

  The event participant database 21 is illustrated in FIG. The event participant database 21 includes an “event ID” field for identifying an event, an “event name” field for indicating the name of the event, and an “event keyword” field for indicating a keyword for identifying the event participant. And a “participant ID” field indicating the ID of the terminal 2 owned by the event participant. In the present embodiment, it is assumed that there are three events for simplicity, but there are actually more events. In this embodiment, for the sake of simplicity, description will be made assuming that there are five participant IDs from 001 to 005.

  The event participant adding unit 12 searches the character string included in the behavior record received by the behavior record receiving unit 11 for the presence or absence of a character string that matches the keyword stored in the “event keyword” field of the event participant database 21. . When there is a character string that matches the keyword, the event participant adding unit 12 determines that the user of the terminal 2 that has transmitted and received the action record including the character string is a participant in the event, It adds to participant database 21.

  For example, it is assumed that the user of the terminal 2 corresponding to the ID “001” requests “buy □□□ DVD” at the terminal 2. This request is stored in the action record database 31. Thereafter, the action record accepting unit 11 connects to the action record database 31 and accepts an action record related to the DVD purchase request operation. The event participant adding unit 12 includes a character string that matches the keyword “□□□” stored in the “event keyword” field of the event participant database 21 in the character string included in the action record. The user of the terminal 2 corresponding to the ID “001” is added as a participant ID “001” to the “participant ID” field, assuming that the user of the event “Purchase DVD of □□□” is a participant.

  Returning to FIG. 1, the control unit 10 refers to the event participant database 21, and determines the number of events in which one participant and other participants participate in common for each participant of the event. A common event count totaling unit 13 that sequentially counts each participant is provided. In addition, the storage unit 20 includes a social graph database 22 in which the results of counting by the common event number counting unit 13 are stored. The common event number counting unit 13 and the social graph database 22 function as a common event number counting unit.

  The event participant database 21 shown in FIG. 2 will be described as an example. First, the common event number counting unit 13 refers to the event participant database 21 and, for the participant ID “001”, the participant corresponding to the participant ID “001” and the participant corresponding to the other participant IDs. And the number of events that participate in common for each of the other participants. The event ID “B” is common between the participant ID “001” and the participant ID “002”, but is not common to other event IDs. Therefore, the number of events in which the participant corresponding to the participant ID “001” and the participant corresponding to the participant ID “002” participate in common is “1”. Similarly, the number of events in which the participant corresponding to the participant ID “001” and the participant corresponding to the participant ID “003” participate in common is “2”, and the participant ID “001”. The number of events that the participant corresponding to the participant and the participant corresponding to the participant ID “004” participate in is “1”, and the participant corresponding to the participant ID “001” and the participant ID The number of events that the participant corresponding to “005” participates in common is “0”.

  FIG. 3 shows the social graph database 22. The social graph database 22 includes a “participant ID” field indicating a participant ID, a “common event number” field indicating the number of events that participate in common with the participant corresponding to the participant ID, and the participants. And a “friendship” field that indicates whether or not is a friendship. The common event number counting unit 13 determines the number of events in which the participant corresponding to the participant ID “001” and the participants corresponding to the other participant IDs participate in common are in ascending order of the other participant IDs. Since “1”, “2”, “1”, and “0” are counted, “1”, “2”, “1”, “ “0” is stored.

  The common event count totaling unit 13 also counts the relationship between the participant IDs “002”, “003”, “004”, and “005” with other participant IDs.

  Returning to FIG. 1, the control unit 10 includes a friend addition unit 14 that adds, as a friend, a participant whose number counted by the common event count totaling unit 13 is a predetermined number or more. The friend addition unit 14 functions as a friend addition unit. In the present embodiment, the predetermined number is assumed to be “3”, but the present invention is not limited to this.

  The social graph database 22 shown in FIG. 3 will be described as an example. The number stored in the “number of common events” field is 2 or less. That is, there is no participant whose number counted by the common event count totaling unit 13 is “3” or more. Therefore, the friend addition unit 14 does not add any participant as a friend. The “friendship” field in the social graph database 22 remains “x”.

[Hardware and Software Configuration of this Embodiment]
The hardware and software configurations of this embodiment will be described. The hardware of the friendship generation device 1 includes a CPU as a control device (control unit), a storage device (storage unit), a communication device (communication unit), a display device (display unit), and an input device (input unit). Is included. Examples of the storage device (storage unit) include a memory (RAM, ROM, etc.), a hard disk drive (HDD), an optical disk (CD, DVD, etc.) drive, and the like. Examples of the communication device (communication unit) include various wired or wireless interface devices. Examples of the display device (display unit) include various displays such as a liquid crystal display or a plasma display. Examples of the input device (input unit) include a keyboard, a pointing device (such as a mouse), a remote control device, and the like.

  The software of the friendship generation device 1 includes a program and data for controlling the hardware. Programs and data are stored in a storage device (storage unit), and are appropriately executed and referenced by a control device (control unit). Further, the computer program and data can be distributed by an electromagnetic method, or can be recorded and distributed on a computer-readable medium such as a CD-ROM.

[flowchart]
FIG. 4 is a flowchart of the friendship generation device 1 according to this embodiment.

  First, the action record accepting unit 11 executes an action record accepting process (S1). In this process, the action record receiving unit 11 executes a process of connecting to the action record database 31 and sequentially receiving action records performed by the terminal 2.

  Next, the event participant adding unit 12 executes an event participant adding process (S2). In this process, the event participant adding unit 12 refers to the “event keyword” field of the event participant database 21 and extracts event participants from the action record received by the action record receiving unit 11. Then, the event participant adding unit 12 adds the extracted participant to the “participant ID” field.

  Next, the common event number totaling unit 13 executes a common event number totaling process (S3). In this process, the common event number counting unit 13 refers to the event participant database 21 and determines the number of events in which one participant and other participants participate in common for each of the event participants. Aggregate sequentially for each of the other participants. Then, the common event count totaling unit 13 writes the count result in the “common event count” field of the social graph database 22.

  Next, the friend addition part 14 performs a friend addition process (S4). In this process, the friend addition unit 14 refers to the “number of common events” field of the social graph database 22, and the number counted by the common event number counting unit 13 is a predetermined number (“3” in the present embodiment) or more. It is determined whether or not. If the number is equal to or greater than the predetermined number (“3” in the present embodiment), the friend addition unit 14 updates the “friend relationship” field for the participant ID from “×” to “◯”, and A participant corresponding to the participant ID is added as a friend.

  When the friend addition process ends, the control unit 10 ends the series of processes.

[Example of friendship generation device 1]
Hereinafter, the Example of the friend relationship production | generation apparatus 1 is demonstrated. In the present embodiment, on the basis that the information stored in the event participant database 21 and the social graph database 22 is in the state shown in FIGS. 2 and 3, the terminal 2 corresponding to the participant ID “001” thereafter. In the following explanation, it is assumed that the participation request for “XX Concert” was executed.

  First, a participation request for “XX concert” from the terminal 2 is written in the action record database 31. Thereafter, the action record accepting unit 11 connects to the action record database 31 and accepts the participation request. Then, the event participant adding unit 12 includes a character string matching the keyword “XXX” stored in the “event keyword” field of the event participant database 21 in the character string included in the action record. And the user of the terminal 2 corresponding to the ID “001” is added as a participant ID “001” to the “participant ID” field, assuming that the user is a participant of the event “XXX concert”. FIG. 5 illustrates this, and “001” is added to the “participant ID” field corresponding to the event ID “A”.

  Subsequently, the common event number counting unit 13 refers to the event participant database 21 and, for the participant ID “001”, the participant corresponding to the participant ID “001” and the participation corresponding to the other participant IDs. The number of events that the participant participates in common is sequentially counted for each of the other participants. Originally, the event ID “B” is common between the participant ID “001” and the participant ID “002” (FIG. 2), but the event ID “A” is also common (FIG. 5). ). Accordingly, the number of events in which the participant corresponding to the participant ID “001” and the participant corresponding to the participant ID “002” participate in common is updated from “1” to “2”. Similarly, between the participant ID “001” and the participant ID “003”, only the event IDs “B” and “C” are common (FIG. 2), but the event ID “A” is newly added. Common (FIG. 5). Therefore, the number of events in which the participant corresponding to the participant ID “001” and the participant corresponding to the participant ID “003” participate in common is updated from “2” to “3”. There is no change in the number of events in which the participant corresponding to the participant ID “001” and the participants corresponding to the participant IDs “004” and “005” participate in common.

  FIG. 6 shows an example of writing to the social graph database 22 at this time. In the social graph database 22 corresponding to the participant ID “001”, the common event number counting unit 13 updates the number of common events with the participant ID “002” from “1” to “2”, and the participant ID “001”. The number of common events with “003” is updated from “2” to “3”.

  Then, the friend addition unit 14 adds a participant whose number counted by the common event count totaling unit 13 is a predetermined number or more (in this embodiment, “3” or more) as a friend. Taking the social graph database 22 shown in FIG. 6 as an example, for the user corresponding to the participant ID “003”, the number stored in the “number of common events” field is “3”. The user is added as a friend by updating the “friend relationship” field of the social graph database 22 from “×” to “◯”.

  7 and 8 show the operations of the common event count totaling unit 13 and the friend adding unit 14 in the above embodiment in a Venn diagram. The common event count totaling unit 13 totals the union of participant IDs written in the event participant database 21 by the control operation sequentially performed by the action record receiving unit 11 and the event participant adding unit 12 for each event. Then, the friend addition unit 14 aggregates the product set (shaded portions in FIGS. 7 and 8) of the union for each event, and identifies the user corresponding to the user ID included in the product set as the friend relationship. .

  FIG. 7 is a Venn diagram showing the relationship between the event and the participant ID shown in FIG. According to this, since the user ID included in the intersection set (shaded portion in FIG. 7) of the union for each event is “002”, the friendship is not established.

  FIG. 8 is a Venn diagram showing the relationship between the event and the participant ID shown in FIG. According to this, since the user IDs included in the intersection set (shaded area in FIG. 8) of each event are “002” and “003”, the user IDs corresponding to “002” and “003” A friendship is established between them.

  According to the invention described in the present embodiment, the number of actions that are performed in common is sequentially counted and added as a friend when the number is large. Therefore, it is possible to provide the friendship generation device 1 that can construct a new human relationship more accurately and in real time than the conventional device.

  The common event number counting unit 13 refers to the event participant database 21, and one participant and another participant participate in “for a predetermined time” in common for each of the event participants. It is preferable to sequentially count the number of events for each of the other participants. In this way, the number of actions commonly performed during a predetermined time can be sequentially counted and added as a friend when the number is large, so it is possible to construct new human relationships more accurately and in real time. A possible friendship generation device 1 can be provided.

  The effects described in the present embodiment are only the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the present embodiment. Absent.

DESCRIPTION OF SYMBOLS 1 Friend relation production | generation apparatus 2 Terminal 10 Control part 11 Action record reception part 12 Event participant addition part 13 Common event number totaling part 14 Friend addition part 20 Storage part 21 Event participant database

Claims (3)

An event participant database in which information on participants participating in the event is stored;
Action record accepting means for sequentially accepting action records performed on the terminal;
Event participant adding means for extracting participants of the event from the behavior record and adding the extracted participants to the event participant database;
Common that refers to the event participant database and sequentially counts the number of events that one participant and other participants participate in common for each of the other participants. Event count counting means,
An apparatus comprising: a friend adding means for adding, as a friend, a participant whose number counted by the common event number counting means is a predetermined number or more. The apparatus of claim 1, comprising:
The common event number counting means refers to the event participant database, and for each of the event participants, the number of events in which one participant and other participants participate in common during a predetermined time. For each of the other participants. A method for a computer to generate friendships,
The computer
It has an event participant database that stores information on participants participating in the event,
An action record accepting step for sequentially accepting action records made on the terminal;
An event participant adding step of extracting the event participant from the action record and adding the extracted participant to the event participant database;
Common that refers to the event participant database and sequentially counts the number of events that one participant and other participants participate in common for each of the other participants. Event count process,
The apparatus which performs the friend addition process which adds the participant whose number totaled by the said common event number totalization process is more than predetermined number as a friend.

Images