Interaction management apparatus, interaction management method, and program

Abstract

To obtain and manage interaction relation information on associations between users using interaction information on interactions other than exchange of business cards.SOLUTION: An interaction management apparatus 1 includes: a user identifier acquisition unit 131 which acquires a user identifier; an interaction information determination unit 132 which determines interaction information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and satisfying a predetermined condition, from among one or more pieces of interaction information; an another-user information acquisition unit 134 which acquires another-user information including a user identifier which is different from the user identifier acquired by the user identifier acquisition unit 131 and corresponding to the interaction information determined by the interaction information determination unit 132; and an interaction relation accumulation unit 135 which accumulates interaction-related information associating the another-user information with the user identifier. By using interaction information relating to interactions other than exchange of business cards, interaction relation information on associations between users can be acquired and managed.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an exchange management device and the like that uses exchange information regarding exchanges between two or more people to manage information regarding the exchanges. [Background technology]

[0002] Conventionally, there has been a business card exchange system that manages the exchange of business cards (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-129309 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, it is not possible to acquire and manage exchange relationship information regarding ties between users using information regarding exchanges other than the exchange of business cards. [Means for solving the problem]

[0005] The interaction management device of the first invention is an interaction management device comprising: a user identifier acquisition unit that acquires a user identifier; an interaction information determination unit that determines, from one or more pieces of interaction information, interaction information that is information regarding an interaction between two or more users, which information corresponds to the user identifier acquired by the user identifier acquisition unit, and satisfies a predetermined condition; a other user information acquisition unit that acquires other user information including a user identifier that is different from the user identifier acquired by the user identifier acquisition unit and corresponds to the interaction information determined by the interaction information determination unit; and an interaction relationship storage unit that stores interaction relationship information that associates other user information with the user identifier.

[0006] With this configuration, exchange relationship information regarding ties between users can be acquired and managed using the exchange information.

[0007] In addition, the exchange management device of the second invention is an exchange management device in which, compared to the first invention, the predetermined conditions are business exchange conditions for determining that the exchange is a business exchange, and the exchange information determination unit is exchange information corresponding to the user identifier acquired by the user identifier acquisition unit, and determines exchange information that satisfies the business exchange conditions.

[0008] With this configuration, exchange relationship information regarding business ties between users can be acquired and managed using the exchange information.

[0009] In addition, the exchange management device of the third invention is an exchange management device that, in contrast to the first or second invention, further includes a query unit that queries a user as to whether or not to accumulate exchange relationship information, and the exchange relationship accumulation unit accumulates the exchange relationship information only when the result of the inquiry by the query unit is to accumulate the exchange relationship information.

[0010] With this configuration, it is possible to store only the exchange relationship information that is necessary for the user.

[0011] In addition, the exchange management device of the fourth invention is an exchange management device in which, compared to any one of the first to third inventions, the other user information acquisition unit searches a user information storage unit in which one or more pieces of user information having a user identifier and one or more user attribute values ​​are stored, using a character string contained in the exchange information determined by the exchange information determination unit or a user identifier corresponding to the exchange information, and acquires other user information using the search results.

[0012] With this configuration, accurate information about other users can be acquired and managed using the user information in the user information storage unit.

[0013] In addition, the exchange management device of the fifth invention is an exchange management device in which, compared to any one of the first to fourth inventions, the exchange information is email, the exchange information determination unit determines emails that satisfy predetermined conditions from emails sent to email addresses corresponding to the user identifier acquired by the user identifier acquisition unit, and the other user information acquisition unit acquires other user information using the email determined by the exchange information determination unit.

[0014] With this configuration, exchange relationship information regarding ties between users can be acquired and managed using e-mails stored in the mail server.

[0015] In addition, the interaction management device of the sixth invention is an interaction management device in which, compared to the fifth invention, the other user information acquisition unit acquires other user information using signature information in the email determined by the interaction information determination unit.

[0016] With this configuration, it is possible to obtain and manage exchange relationship information regarding ties between users by using the signatures of emails stored in the mail server.

[0017] In addition, the interaction management device of the seventh invention is an interaction management device in which, compared to the fifth or sixth invention, the other user information acquisition unit acquires the domain name of the email address of the sender of the email determined by the interaction information determination unit, acquires an organization identifier corresponding to the domain name from a domain information storage unit in which one or more pieces of domain information having pairs of domain names and organization identifiers are stored, and acquires other user information using the organization identifier.

[0018] With this configuration, it is possible to obtain and manage exchange relationship information regarding ties between users by using the signatures of emails stored in the mail server.

[0019] In addition, the exchange management device of the eighth invention is an exchange management device in which, compared to any one of the fifth to seventh inventions, the predetermined condition is a condition related to an email address, and the exchange information determination unit determines emails that satisfy the predetermined condition using the email address of the sender of each of one or more stored emails.

[0020] With this configuration, exchange relationship information regarding ties between users can be acquired and managed using email addresses.

[0021] A ninth aspect of the present invention is an exchange management device according to any one of the fifth to eighth aspects of the present invention, wherein the other user information includes mail-related information about mail.

[0022] With this configuration, email-related information can also be managed.

[0023] Furthermore, the exchange management device of the tenth invention is an exchange management device in which, compared to any one of the first to fourth inventions, the exchange information is schedule information that specifies the user's schedule, the exchange information determination unit determines schedule information that satisfies a predetermined condition from one or more schedule information corresponding to the user identifier acquired by the user identifier acquisition unit, and the other user information acquisition unit acquires other user information using the schedule information determined by the exchange information determination unit.

[0024] With this configuration, it is possible to obtain and manage exchange relationship information regarding ties between users by using the schedule information stored in the calendar server.

[0025] In addition, the exchange management device of the eleventh invention is an exchange management device comprising, with respect to any one of the first to tenth inventions, a business card information accepting unit that accepts business card information relating to the business card of another user in correspondence with a user identifier, an other user information acquisition unit that acquires other user information including other user identifiers corresponding to the business card information, and an exchange relationship storage unit that stores exchange relationship information that associates the other user information with the user identifier.

[0026] With this configuration, exchange relationship information acquired based on the exchange of business cards can also be managed.

[0027] In addition, the exchange management device of the twelfth invention is an exchange management device that, with respect to any one of the first to eleventh inventions, further comprises a change determination unit that determines whether there has been a change in other user information corresponding to the exchange information or business card information, and an exchange processing unit that performs predetermined processing when the change determination unit determines that there has been a change.

[0028] With this configuration, if it is determined that there has been a change in the information about other users acquired using communication information such as emails, appropriate action can be taken. Effect of the Invention

[0029] According to the interaction management device of the present invention, interaction information on interactions other than the exchange of business cards can be used to acquire and manage interaction relationship information on ties between users. [Brief description of the drawings]

[0030] [Figure 1] Conceptual diagram of exchange management system A in embodiment 1. [Diagram 2] Block diagram of the exchange management system A [Diagram 3] Block diagram of the AC management device 1 [Figure 4] A flowchart illustrating an example of the operation of the AC management device 1. [Diagram 5] A flowchart illustrating an example of the exchange relationship information processing [Figure 6] A flowchart illustrating an example of the exchange process. [Figure 7] A flowchart illustrating an example of the business card information processing [Figure 8] FIG. 13 is a diagram showing an example of the user information management table. [Figure 9] FIG. 13 is a diagram showing an example of the domain information management table. [Figure 10] FIG. 13 is an example of the exchange relationship management table. [Figure 11]A diagram showing an example of the business term dictionary. [Figure 12] A diagram showing an example of the non-business term dictionary. [Figure 13] FIG. 13 shows an example of the condition management table. [Figure 14] FIG. 13 is a diagram showing an example of the calendar schedule information management table. [Figure 15] FIG. 13 shows an example of the web conference schedule information management table. [Figure 16] An example of the email is shown below. [Figure 17] A diagram showing an example of the screen [Figure 18] A diagram showing an example of the screen [Figure 19] Overview of the computer system [Figure 20] Block diagram of the computer system DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0031] Hereinafter, an embodiment of an AC management device and the like will be described with reference to the drawings. In the embodiments, components with the same reference numerals perform similar operations, so that repeated description may be omitted.

[0032] (Embodiment 1) In this embodiment, an exchange management system is described that includes an exchange management device that acquires information on other users who are exchange partners by using exchange information acquired from an information server that stores two or more pieces of exchange information related to exchanges between two or more people, and accumulates exchange relationship information that associates the information on the other users with user identifiers. Note that the exchange information is, for example, reservation information registered in an email or calendar server or reservation information registered in a web conference server.

[0033] In addition, in this embodiment, an exchange management system is described that includes an exchange management device that determines one or more business exchange information that is business-related exchange information from two or more exchange information, and acquires other user information from the business exchange information.

[0034] In addition, in this embodiment, an exchange management system will be described that includes an exchange management device that queries a user as to whether or not to store exchange relationship information and stores the exchange relationship information if the user answers that the information should be stored.

[0035] In addition, in this embodiment, we will describe an exchange management system that includes an exchange management device that uses exchange information, etc. to obtain accurate information about other users from a user information storage unit, and uses the information about other users to obtain and store exchange relationship information.

[0036] In addition, in this embodiment, we will describe an exchange management system that is equipped with an exchange management device that obtains other user information from exchange information, which is an email sent to an email address corresponding to a user identifier, and obtains and stores exchange relationship information using the other user information.

[0037] In this embodiment, a communication management system including a communication management device that acquires information about other users from the signature of an email will be described.

[0038] In this embodiment, a description will be given of an exchange management system including an exchange management device that acquires the domain name of the email address of the sender of an email, and acquires the organization name corresponding to the domain name from the domain DB.

[0039] In this embodiment, a communication management system will be described that includes a communication management device that uses the email address of the sender of the email to determine whether or not the email is business communication information.

[0040] In addition, in this embodiment, a communication management system will be described that includes a communication management device that also stores mail-related information such as the mail reception date and time, the mail body, and the title.

[0041] In this embodiment, an exchange management system including an exchange management device that also accepts and stores business card information will be described. In addition, an exchange management system including an exchange management device that, when the business card information is also accepted, acquires and stores exchange relationship information using the business card information will be described.

[0042] Furthermore, in this embodiment, a description will be given of an exchange management system including an exchange management device that performs a predetermined action using exchange relationship information.

[0043] 1 is a conceptual diagram of an exchange management system A according to the present embodiment. The exchange management system A includes an exchange management device 1, one or more information servers 2, and one or more terminal devices 3.

[0044] The exchange management device 1 is a device that acquires and accumulates exchange relationship information. The exchange management device 1 is usually a so-called server, such as a cloud server or an ASP server. The type of the exchange management device 1 is not important. Details of the exchange relationship information will be described later.

[0045] The information server 2 is a server in which one or more pieces of exchange information are stored. The information server 2 is, for example, a mail server, a calendar server in which schedule information for each time period on a calendar is stored, or a web conference server in which schedule information for web conferences is stored. The calendar server is, for example, a Google Calendar server or a CalDAV server. The web conference server is, for example, a server that manages information on web conferences such as Zoom (registered trademark) or Teams.

[0046] The information server 2 may be a server that stores one or more types of information, such as one or more emails obtained from a mail server, one or more schedule information obtained from a calendar server, and one or more schedule information obtained from a web conference server. The information server 2 is, for example, a cloud server, an ASP server, etc. The type of the information server 2 is not important.

[0047] The terminal device 3 is a terminal used by a user. The terminal device 3 is a terminal that transmits business card information to the exchange management device 1, transmits responses to inquiries from the exchange management device 1, and outputs exchange information and exchange relationship information. The terminal device 3 is, for example, a so-called personal computer, a tablet terminal, a smartphone, or the like, and the type is not important.

[0048] It is preferable that the exchange management device 1 is capable of communicating with one or more information servers 2 and one or more terminal devices 3 via a network such as the Internet or a LAN.

[0049] Fig. 2 is a block diagram of the AC management system A in this embodiment. Fig. 3 is a block diagram of the AC management device 1.

[0050] The exchange management device 1 includes a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit 14. The storage unit 11 includes a user information storage unit 111, a business card information storage unit 112, a domain information storage unit 113, and an exchange relationship storage unit 114. The receiving unit 12 includes a business card information accepting unit 121. The processing unit 13 includes a user identifier acquiring unit 131, an exchange information determining unit 132, a questioning unit 133, a other user information acquiring unit 134, an exchange relationship accumulation unit 135, a change determining unit 136, and an exchange processing unit 137.

[0051] The information server 2 includes a server storage unit 21, a server receiving unit 22, a server processing unit 23, and a server transmitting unit 24.

[0052] The terminal device 3 includes a terminal storage unit 31, a terminal reception unit 32, a terminal processing unit 33, a terminal transmission unit , a terminal reception unit 35, and a terminal output unit .

[0053] Various types of information are stored in the storage unit 11 constituting the exchange management device 1. The various types of information are, for example, user information (described later), business card information (described later), domain information (described later), exchange information, exchange relationship information, and various types of screen information. The various types of screen information are, for example, inquiry screen information for constituting an inquiry screen, and exchange relationship screen information for constituting a screen including one or more pieces of exchange relationship information. The screen information is realized, for example, by HTML, XML, or a program, but the realization means, structure, etc. are not important.

[0054] The interaction information is information regarding interactions between two or more users. The interaction information is information that is the source of acquiring the interaction relationship information described below. The interaction information is, for example, email, calendar schedule information which is schedule information input to a calendar server, web conference schedule information which is schedule information input to a web conference server, etc. Email is electronic mail. The interaction information may be considered to include or not include information regarding the exchange of business cards. The calendar server may be referred to as a schedule management server, etc. The web conference server may be referred to as a web conference information management server, etc.

[0055] The calendar schedule information includes, for example, one or more pieces of information such as the name of the other party in the meeting, the name of the other party's company, the start time of the meeting, the end time of the meeting, and the location of the meeting.

[0056] The Web conference schedule information includes, for example, one or more pieces of information such as the name of the other party in the conference, the name of the other party's company, the start time of the Web conference, and the end time of the Web conference.

[0057] It should be noted that calendar schedule information and Web conference schedule information may be referred to as schedule information without distinction.

[0058] The exchange relationship information is information indicating that an exchange has occurred or is occurring between two or more users. The exchange relationship information may be information that can identify an exchange relationship. The exchange relationship information is usually information that associates other user information with a user identifier. The exchange relationship information may be information having other user information and a user identifier, the exchange relationship information may be information of a link between other user information and a user identifier, or other user information associated with a user identifier. The exchange relationship information may be information indicating that an exchange has occurred or is occurring between two or more users, and the data structure and contents are not important. The user identifier is information that identifies a user. The user identifier is, for example, a user ID, an email address, a telephone number, a terminal identifier of a terminal device 3 used by a user, or the like, but may be any information that can identify a user. The identifier of the terminal device 3 is, for example, an IP address or a MAC address. The other user information is information regarding the other user. The other user is a user other than the user identified by the user identifier to which the other user information is associated. The other user information is, for example, the user identifier of the other user, and one or more of the user attribute values ​​of the other user. The user attribute values ​​are, for example, the name, the organization identifier of the organization to which the user belongs, a job title, a telephone number, a fax number, an address, and a URL. The organization identifier is, for example, the company name or the name of the organization. The address is, for example, the address of the organization to which the user belongs, or the home address. The URL is the URL of the homepage of the organization to which the user belongs.

[0059] The user information storage unit 111 stores one or more pieces of user information. The user information is information about a user. The user information has a user identifier that identifies the user. The user information may be associated with the user identifier. The user information has one or more user attribute values. It is preferable that the user information in the user information storage unit 111 is accurate information. It is even more preferable that the user information in the user information storage unit 111 is guaranteed to be accurate information. The user information in the user information storage unit 111 is, for example, information input by each user. The user information in the user information storage unit 111 is, for example, information input by a person after looking at the business card image of each user.

[0060] The business card information storage unit 112 stores one or more pieces of business card information. The business card information is information related to a business card. The business card information is associated with a user identifier. It is preferable that the user identifier corresponding to the business card information of a user and the user identifier included in the user information of the user are the same information, but they may be different information. However, it is preferable that the business card information of a user and the user information of the user are associated with each other. The business card information is information related to the user's business card. The business card information has, for example, a business card image and one or more pieces of item information. The item information is information constituting the business card. The item information is, for example, a name, an organization identifier of an organization to which the user belongs, a job title, a telephone number, a fax number, an address, and a URL. The item information may be the same as a user attribute value.

[0061] The user information in user information storage unit 111 and the business card information in business card information storage unit 112 for one user may be partially or entirely the same information.

[0062] The domain information storage unit 113 stores one or more pieces of domain information. The domain information is information indicating the correspondence between the domain character string of an email address (domain name) and an organization identifier. The domain information is, for example, a pair of the domain character string of an email address and an organization identifier. The domain information is, for example, information indicating a link between the domain character string of an email address and an organization identifier.

[0063] The exchange relationship storage unit 114 stores one or more pieces of exchange relationship information. The exchange relationship information usually corresponds to a user identifier. Corresponding to a user identifier may include the user identifier. The exchange relationship information in the exchange relationship storage unit 114 is information that specifies the exchange between the user identified by the user identifier and other users. The exchange relationship information may have a type identifier. The type identifier is information that identifies the type of exchange. The type identifier is, for example, a flag that identifies the type of exchange, such as "email", "calendar", "web conference", and "business card". "Email" is information indicating that an exchange has occurred by e-mail. "Calendar" is information indicating that an exchange has occurred corresponding to the schedule information registered in the calendar server. "Web conference" is information indicating that an exchange has occurred by a web conference. "Business card" is information indicating that an exchange has occurred corresponding to receiving a business card.

[0064] The receiving unit 12 receives various information. The various information is, for example, a start instruction, exchange information, business card information, a user identifier, and an instruction to transmit various information. The start instruction is an instruction to start a process of acquiring one or more pieces of exchange information from one or more information servers 2. The instruction to transmit various information is, for example, an instruction to transmit user information, an instruction to transmit business card information, and an instruction to transmit exchange relationship information.

[0065] The business card information receiving unit 121 receives business card information related to the business card of another user in association with the user identifier. The user identifier here is the identifier of the user who received the business card corresponding to the business card information. The user identifier here is the identifier of a single user, not of another user.

[0066] Here, acceptance usually means receiving information from terminal device 3, but it is a concept that also includes acceptance of information input from input devices such as a keyboard, mouse, or touch panel, and acceptance of information read from recording media such as optical disks, magnetic disks, and semiconductor memories.

[0067] The processing unit 13 performs various types of processing. The various types of processing are, for example, processing performed by a user identifier acquisition unit 131, an exchange information determination unit 132, a question unit 133, a different user information acquisition unit 134, an exchange relationship accumulation unit 135, a change determination unit 136, and an exchange processing unit 137.

[0068] The processing unit 13 acquires various pieces of information in accordance with the transmission instructions for the various pieces of information. For example, the processing unit 13 acquires the exchange relationship information from the exchange relationship storage unit 114 in accordance with the transmission instruction for the exchange relationship information.

[0069] The user identifier acquisition unit 131 acquires one or more user identifiers. The user identifier acquisition unit 131 acquires the user identifier of the user for which exchange relationship information is to be acquired. The user identifier acquisition unit 131 acquires, for example, one or more user identifiers stored in the user information storage unit 111. The user identifier acquisition unit 131 acquires, for example, a user identifier transmitted from the terminal device 3 and received by the receiving unit 12. Note that the user identifier acquisition unit 131 may acquire one or more user identifiers from one or more information servers 2, a recording medium (not shown), an external device (not shown), or the like.

[0070] The exchange information determination unit 132 determines, from among one or more pieces of exchange information, exchange information that corresponds to the user identifier acquired by the user identifier acquisition unit 131 and satisfies a predetermined condition. The one or more pieces of exchange information are information acquired directly or indirectly from the information server 2. The one or more pieces of exchange information are, for example, one or more pieces of exchange information received by the receiving unit 12, one or more pieces of exchange information stored in the storage unit 11, one or more pieces of exchange information stored in each of the one or more information servers 2, and one or more pieces of exchange information acquired from each of the one or more information servers 2 and stored in an information processing device (not shown). It is preferable that the exchange information is information that was originally stored in the information server 2. The exchange information is, for example, email or schedule information. The exchange information may be information that has been processed from information that was originally stored in the information server 2.

[0071] Determining the exchange information may include, for example, acquiring the exchange information, acquiring a link to the exchange information, and the like.

[0072] The predetermined condition is, for example, a business exchange condition. The business exchange condition is a condition that specifies that the exchange is in a business context.

[0073] The predetermined condition is, for example, that user information corresponding to information acquired from the exchange information (for example, name, company name, etc.) exists in the user information storage unit 111.

[0074] The interaction information determination unit 132 determines, for example, interaction information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and which satisfies the business interaction condition.

[0075] The interaction information determination unit 132 determines an email that satisfies a predetermined condition from one or more emails sent to an email address corresponding to the user identifier acquired by the user identifier acquisition unit 131. The predetermined condition here is appropriately referred to as an email condition.

[0076] The interaction information determination unit 132 determines emails that satisfy the email conditions by using the email addresses of the senders of the one or more stored emails.

[0077] The email conditions include, for example, conditions regarding responses by email, conditions regarding email addresses, and conditions regarding the contents of emails.

[0078] A condition for replying by email is, for example, that emails are sent and replied to between two users. This condition is set so that a one-way email transmission alone is not considered to be an exchange.

[0079] A condition for replying by email is, for example, that there is N or more exchanges (N is a natural number equal to or greater than 2) between two users. Such a condition is a condition for not regarding, for example, a small amount of exchange or a one-sided email transmission as an exchange according to the present application.

[0080] The condition for replying by email is, for example, that two users exchange emails N times or more over a certain period of time (e.g., three months or one year). This condition is used to exclude short-term email exchanges from being considered as exchanges of the present application.

[0081] The condition regarding email addresses is that the recipient's (e.g., the sender of the email or the recipient of the email) email address contains a specified character string (e.g., "co.jp", "ac.jp", etc.). The condition regarding email addresses is that the recipient's email address does not contain a specified character string. The condition regarding email addresses is, for example, that the recipient's email address is not an email address that is considered to be a personal email address (e.g., an address that contains "gmail.com" or "yahoo.co.jp").

[0082] The condition regarding the content of the email is, for example, that it is not a spam email. The technology for determining whether or not it is a spam email can be a known mailer technology. The condition regarding the content of the email is, for example, that it is an email that contains many terms stored in a business terminology dictionary (not shown). An email that contains many terms means that it contains a number of terms equal to or greater than a threshold value, or contains terms at a ratio equal to or greater than a threshold value. The condition regarding the content of the email is, for example, that it is determined to be a business email as a result of a classification process (which may be called a prediction process) using a machine learning classifier (which may be called a learning model, a learning device, etc.). The classifier is data acquired by performing a learning process using a machine learning algorithm using one or more positive examples that are business emails and one or more negative examples that are not business emails as teacher data. The machine learning can be so-called deep learning, random forest, decision tree, SVM, etc., but the algorithm is not important. The machine learning can be, for example, various modules of TensorFlow (registered trademark), a random forest module of R language, TinySVM, etc. The business term dictionary is a storage area such as a database or a file that stores two or more terms used in business. A business term may be a phrase or a sentence. Examples of phrases or sentences include "Thank you for your continued support," "We look forward to working with you in the future," "King Regards," etc.

[0083] The exchange information determination unit 132 determines schedule information that satisfies a predetermined condition from one or more pieces of schedule information corresponding to the user identifier acquired by the user identifier acquisition unit 131. Such a predetermined condition is appropriately referred to as a schedule condition.

[0084] The schedule condition is, for example, schedule information of a schedule on a work day (for example, from Monday to Friday). The schedule condition is, for example, schedule information of a schedule on a work day during work hours (for example, between 9:00 and 18:00). The schedule condition is, for example, schedule information including an organization identifier such as a company name. The schedule information including an organization identifier includes a predetermined character string indicating that the information is a company, such as "Inc.", "Limited Company," or "(Stock)." Machine learning can be used to identify whether a character string is an organization identifier. That is, the exchange information determination unit 132 may provide a classifier that classifies whether the information is an organization identifier and a character string acquired from the schedule information to a module that performs machine learning prediction processing, and obtain a classification result (whether the information is an organization identifier or not). The classifier is data obtained by providing one or more positive examples that are organization identifiers and one or more negative examples that are not organization identifiers to a module that performs machine learning learning processing. As described above, deep learning, random forest, decision tree, SVM, etc. can be used for such machine learning, but the algorithm is not important.

[0085] Furthermore, the predetermined condition may be, for example, a response to an inquiry by questioning unit 133 (described later) that "Exchange relationship information is to be stored."

[0086] The questioning unit 133 asks the user whether or not to store exchange relationship information. The questioning of the user is, for example, a transmission to the user's terminal device 3, but it does not have to be a proactive question, and the questioning method does not matter. In addition, the timing and trigger of such a question to the user do not matter.

[0087] For example, when the user's terminal device 3 accesses the exchange management device 1, the questioning unit 133 transmits screen information (question screen information) constituting a question screen for inquiring the user whether or not to store the exchange relationship information to the terminal device 3. The questioning screen is, for example, a screen including an interface such as a button or menu items for instructing the storage of the exchange relationship information, a screen including a message for inquiring the user whether or not to store the exchange relationship information, and the like. For example, the questioning unit 133 transmits the question screen information to the terminal device 3 after logging in to the exchange management device 1. For example, when the exchange management device 1 receives an output instruction of a question screen from the terminal device 3, the questioning unit 133 transmits the question screen information to the terminal device 3. For example, the questioning unit 133 inquires the user whether or not to store the exchange relationship information each time exchange information is acquired. For example, the questioning unit 133 inquires the user at a predetermined date and time (for example, "12 o'clock every day", "10 o'clock on the first day of each month", etc.). For example, the questioning unit 133 inquires the user when an instruction having a user identifier is received. This instruction is an instruction to store exchange relationship information.

[0088] The other user information acquisition unit 134 acquires other user information including the other user identifier. The other user identifier is a user identifier different from the user identifier acquired by the user identifier acquisition unit 131.

[0089] The other user information acquisition unit 134 acquires the other user information by using, for example, the interaction information. The other user information acquisition unit 134 acquires the other user information by using, for example, information corresponding to the interaction information.

[0090] The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, a character string included in the exchange information determined by the exchange information determination unit 132 or a user identifier corresponding to the exchange information, and acquires other user information using the search result. The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, a character string (for example, a name and a company name) included in the exchange information determined by the exchange information determination unit 132 as a key, and acquires other user information including part or all of the information of the user information including the character string. The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, a character string included in the exchange information determined by the exchange information determination unit 132 as a key, determines user information including a character string that matches or is similar to the character string, acquires a user identifier corresponding to the user information as the other user identifier, and acquires other user information including the other user identifier. Note that a similar character string is a character string with the highest similarity, or a character string with a similarity equal to or greater than a threshold value.

[0091] Below, the operation of the other user information acquisition unit 134 will be described in the cases where the interaction information is email, where the interaction information is calendar schedule information, where the interaction information is web conference schedule information, and where the business card information receiving unit 121 receives business card information. (1) If the communication information is via email

[0092] The other user information acquisition unit 134 acquires other user information by using the email determined by the interaction information determination unit 132, for example.

[0093] The other user information acquisition unit 134 acquires other user information, for example, by using the signature information in the email determined by the interaction information determination unit 132 .

[0094] The other user information here may include email-related information about the email, which may be, for example, one or more of the following information: the date and time the email was received, the body of the email, the title of the email, and so on.

[0095] The other user information acquisition unit 134, for example, detects a character string of a signature from the email determined by the interaction information determination unit 132, and acquires one or more user attribute values ​​from the character string of the signature. The user attribute value has, for example, one or more pieces of information among a name, a company name, a department name, a title, an address, a telephone number, a fax number, an email address, and a URL. Then, the other user information acquisition unit 134 acquires other user information having, for example, the one or more user attribute values.

[0096] The other user information acquisition unit 134, for example, detects a signature character string from an email (here, typically a received email) determined by the interaction information determination unit 132, acquires one or more user attribute values ​​from the signature character string, searches the user information storage unit 111 using the one or more user attribute values, and acquires other user information having some or all of the matching user information.

[0097] The method by which the other user information acquisition unit 134 detects the character string of the signature from the email is not important. For example, the other user information acquisition unit 134 checks the lines from the lowest line having characters in the email to the lines above, detects a blank line without characters, and acquires the line next to the blank line to the lowest line having characters as the character string of the signature area. For example, the other user information acquisition unit 134 checks from the first line of the email, and acquires the line next to the signature delimiter line (for example, a line having a predetermined number or more consecutive characters "*" or "━" or "+"), which is a line having a predetermined character string, to the line one line above the signature delimiter line, which is a lower line of the line, as the character string of the signature area. For example, the other user information acquisition unit 134 acquires the character string of a predetermined number of lines immediately below a line containing a specific character string in the email (for example, a line containing "Best Regards", "Thank you in advance", etc.) as the character string of the signature area.

[0098] The other user information acquisition unit 134 acquires the domain name of the email address of the sender of the email (here, the received email) determined by the exchange information determination unit 132, acquires the organization identifier corresponding to the domain name from the domain information storage unit 113 which stores one or more pieces of domain information each having a pair of a domain name and an organization identifier, and acquires other user information using the organization identifier.

[0099] The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the organization identifier and the name in the email, and acquires other user information having one or more user attribute values ​​contained in matching user information.

[0100] The other user information acquisition unit 134 acquires the email address of the sender of the email (here, the received email) determined by the interaction information determination unit 132, searches the user information storage unit 111 using the email address, and acquires other user information having part or all of the matching user information. Note that the user information here usually includes one or more attribute values ​​of the accurate user.

[0101] The other user information acquisition unit 134 acquires the name or the like that is the character string preceding the specified character string "sama," "san," or "dono" in the email determined by the exchange information determination unit 132, and searches the user information storage unit 111 using the name or the like to acquire other user information that has some or all of the matching user information.

[0102] The other user information acquisition unit 134 acquires a character string including the first character of the email (here, the sent email) determined by the interaction information determination unit 132 as a name, etc., searches the user information storage unit 111 using the name, etc., and acquires other user information having some or all of the matching user information. (2) When the communication information is calendar schedule information

[0103] The other user information acquisition unit 134 acquires other user information using the calendar schedule information determined by the exchange information determination unit 132. The other user information here may include a part or all of the calendar schedule information. The part or all of the calendar schedule information may be, for example, the start date and time of a meeting, the location of the meeting, information identifying that it is a face-to-face meeting, etc.

[0104] The other user information acquisition unit 134, for example, acquires one or more attribute values ​​(e.g., company name, name, etc.) from the calendar schedule information determined by the interaction information determination unit 132, searches the user information storage unit 111 using the one or more attribute values, and acquires other user information having some or all of the matching user information. (3) When the information on the exchange is about a scheduled web conference

[0105] The other user information acquisition unit 134 acquires other user information using the web conference schedule information determined by the exchange information determination unit 132. The other user information here may include a part or all of the information of the web conference schedule information. The part or all of the information of the web conference schedule information is, for example, the start date and time of the conference, information identifying that it is a web conference, etc.

[0106] The other user information acquisition unit 134, for example, acquires one or more attribute values ​​(e.g., company name, name, etc.) from the web conference schedule information determined by the exchange information determination unit 132, searches the user information storage unit 111 using the one or more attribute values, and acquires other user information having some or all of the matching user information. (4) When the business card information receiving unit 121 receives the business card information received

[0107] The other user information acquiring unit 134 may acquire other user information including the identifiers of other users corresponding to the business card information accepted by the business card information accepting unit 121 .

[0108] The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more items of information contained in the business card information, and acquires other user information having some or all of the matching user information.

[0109] The other user information acquiring unit 134 acquires other user information including, for example, one or more items of information contained in the business card information accepted by the business card information accepting unit 121 .

[0110] The exchange relationship storage unit 135 stores exchange relationship information that associates other user information with a user identifier. The other user information here is information acquired by the other user information acquisition unit 134. The user identifier here is information acquired by the user identifier acquisition unit 131.

[0111] The exchange relationship storage unit 135 stores exchange relationship information, which is other user information acquired by the other user information acquisition unit 134, in association with the user identifier acquired by the user identifier acquisition unit 131, for example.

[0112] The exchange relationship storage unit 135 stores exchange relationship information having, for example, the user identifier acquired by the user identifier acquisition unit 131 and the other user information acquired by the other user information acquisition unit 134.

[0113] The exchange relationship storage unit 135 stores exchange relationship information, which is link information to other user information acquired by the other user information acquisition unit 134, in association with the user identifier acquired by the user identifier acquisition unit 131, for example.

[0114] There is no restriction on where the exchange relationship accumulation unit 135 accumulates the exchange relationship information. For example, the exchange relationship accumulation unit 135 accumulates the exchange relationship information in the exchange relationship storage unit 114. However, the exchange relationship accumulation unit 135 may accumulate the exchange relationship information in another device (not shown). It is preferable that the exchange relationship accumulation unit 135 accumulates the exchange relationship information in a device that uses the exchange relationship information.

[0115] The exchange relationship storage unit 135 stores the exchange relationship information only when, for example, the result of the inquiry by the questioning unit 133 is to store the exchange relationship information. In other words, it is preferable to store only the exchange relationship information that the user desires to store.

[0116] The change determination unit 136 determines whether there is a change in the other user information corresponding to the communication information or the business card information. The change may be, for example, a transfer within an organization, a promotion, a job change, or employment.

[0117] The change determination unit 136, for example, determines the user information that is most similar to the other user information acquired by the other user information acquisition unit 134 from the user information in the user information storage unit 111, determines whether or not one or more predetermined user attribute values, such as an organization identifier, a department identifier, a job title, an address, etc., included in the other user information are different from the corresponding user attribute values ​​of the user information, and determines that a change has occurred if different user attribute values ​​are present.

[0118] The change determination unit 136 searches the user information storage unit 111 using the other user information acquired by the other user information acquisition unit 134, for example, the other user information including a name and one or more other user attribute values ​​(e.g., company name, title, department name), determines whether or not there is user information with a matching name and one or more different other user attribute values, and if such user information is present, determines that there has been a change in the user corresponding to the user information.

[0119] When the change determination section 136 determines that there is a change, the AC processing section 137 performs a predetermined process.

[0120] When the change determination unit 136 determines that there has been a change, it is preferable that the exchange processing unit 137 performs a predetermined process using the exchange relationship information stored by the exchange relationship storage unit 135 in association with the user identifier.

[0121] The predetermined processing includes notification of change information, posting of change information on a web page, etc. Change information is information indicating that a user has been transferred, that there has been a change in the user, etc. It is preferable that the change information includes one or more user attribute values ​​after the change. However, the change information may be, for example, only the name and information indicating that a change has occurred. Notification of change information is processing to inform other users of change information.

[0122] In notifying the change information, the communication processing unit 137 acquires the user identifier of the user for whom the change determination unit 136 has determined that there has been a change, and transmits the change information to the other user identified by the other user identifier corresponding to the user identifier from one or more pieces of communication relationship information corresponding to the user identifier. The means for transmitting the change information may be any means, such as email, fax, or short message. The transmission of the change information may be a process for displaying the change information on a screen output by the other user when the other user identified by the other user identifier logs into the communication management device 1.

[0123] The interaction processing unit 137 posts, on the web page, change information indicating that a user who has changed has been transferred, that there has been a change in the user, and the like.

[0124] The transmission unit 14 transmits various types of information. For example, the various types of information is information indicating that exchange relationship information has been accumulated. The transmission unit 14 transmits various types of information to the terminal device 3, for example.

[0125] The transmission unit 14 transmits, for example, various kinds of information corresponding to the transmission instruction for various kinds of information. The transmission unit 14 transmits, for example, one or more pieces of exchange relationship information corresponding to the transmission instruction for exchange relationship information.

[0126] The server storage unit 21 constituting the information server 2 stores various types of information.

[0127] When the information server 2 is a mail server, one or more mails are stored in the server storage unit 21. For example, a destination mail address for receiving the mail is associated with the mail. For example, a sender mail address for sending the mail is associated with the mail. For example, a user identifier is associated with the mail.

[0128] When the information server 2 is a calendar server, one or more pieces of calendar schedule information are stored in the server storage unit 21. The calendar schedule information is associated with a user identifier. Note that the user identifier of the calendar server for one user and the user identifier used by the exchange management device 1 for one user may be different. However, when the two user identifiers are different, the storage unit 11 is assumed to manage the correspondence between the two user identifiers.

[0129] When the information server 2 is a web conference server, one or more pieces of web conference schedule information are stored in the server storage unit 21. The web conference schedule information is associated with a user identifier. Note that the user identifier of a user's web conference server and the user identifier used by the exchange management device 1 of a user may be different. However, when the two user identifiers are different, the storage unit 11 is assumed to manage the correspondence between the two user identifiers.

[0130] The server receiving unit 22 receives various instructions and information. The server receiving unit 22 receives various instructions and information, for example, from the exchange management device 1 or the terminal device 3. The various instructions and information are, for example, an instruction to send exchange information, and exchange information (e.g., email, schedule information). An instruction to send exchange information is an instruction to send exchange information.

[0131] The server processing unit 23 performs various processes. For example, the various processes are processes for storing the received exchange information in the server storage unit 21. For example, the various processes are processes for acquiring, from the server storage unit 21, exchange information corresponding to an instruction to transmit the exchange information.

[0132] The server transmission unit 24 transmits various types of information, which are exchange information.

[0133] Various types of information are stored in the terminal storage unit 31 constituting the terminal device 3. The various types of information are, for example, a user identifier, business card information, exchange information, and exchange-related information.

[0134] The terminal reception unit 32 receives various instructions and information, such as a start instruction and business card information.

[0135] Here, acceptance is a concept that includes acceptance of information input from an input device such as a keyboard, mouse, or touch panel, receipt of information transmitted via a wired or wireless communication line, acceptance of information read from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory, etc. Means for inputting various instructions and information may be anything, such as a touch panel, keyboard, mouse, or menu screen.

[0136] The device processing unit 33 performs various types of processing. For example, the various types of processing are processing for converting instructions and information accepted by the terminal accepting unit 32 into instructions and information with a data structure to be transmitted. For example, the various types of processing are processing for converting information received by the terminal receiving unit 35 into information with a data structure to be output.

[0137] The terminal transmitting unit 34 transmits various instructions and information, such as a start instruction and business card information.

[0138] The terminal receiving unit 35 receives various types of information, such as various types of screen information, exchange relationship information, business card information, and transfer information.

[0139] The terminal output unit 36 ​​outputs various types of information, such as various types of screen information, exchange relationship information, business card information, and transfer information.

[0140] Here, output is a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs, etc.

[0141] The storage unit 11, the user information storage unit 111, the business card information storage unit 112, the domain information storage unit 113, the server storage unit 21, and the terminal storage unit 31 are preferably non-volatile recording media, but may also be realized as volatile recording media.

[0142] There is no restriction on the process by which information is stored in the storage unit 11, etc. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information inputted via an input device may be stored in the storage unit 11, etc.

[0143] The receiving unit 12, the business card information accepting unit 121, the server receiving unit 22, and the terminal receiving unit 35 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0144] The processing unit 13, the user identifier acquisition unit 131, the exchange information determination unit 132, the question unit 133, the other user information acquisition unit 134, the exchange relationship storage unit 135, the change determination unit 136, the exchange processing unit 137, the server processing unit 23, and the terminal processing unit 33 can usually be realized by a processor, a memory, or the like. The processing procedure of the processing unit 13 is usually realized by software, and the software is recorded in a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuit). The processor is, for example, an MPU, a CPU, a GPU, or the like, and the type is not important.

[0145] The transmitting unit 14, the interrogating unit 133, the server transmitting unit 24, and the terminal transmitting unit 34 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0146] The terminal reception unit 32 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0147] The terminal output unit 36 ​​may or may not include an output device such as a display, a speaker, etc. The terminal output unit 36 ​​may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.

[0148] Next, a description will be given of an example of the operation of the AC management system A. First, a description will be given of an example of the operation of the AC management device 1 with reference to the flowchart of FIG.

[0149] (Step S401) The processing unit 13 judges whether it is time to acquire exchange information. If it is time to acquire exchange information, the process proceeds to step S402, and if it is not time to acquire exchange information, the process proceeds to step S409.

[0150] (Step S402) The processing unit 13 assigns 1 to a counter i.

[0151] (Step S403) The processing unit 13 judges whether or not the i-th type of exchange information for which exchange information is to be acquired exists. If the i-th type of exchange information exists, the process proceeds to step S404, and if the i-th type of exchange information does not exist, the process returns to step S401. Note that it is assumed that whether or not the type of exchange information exists is predetermined and the processing unit 13 is capable of judging it. Also, for example, one or more types of exchange information exist among the three types of exchange information, namely, email, schedule information of a calendar server, and schedule information of a web conference server.

[0152] (Step S404) The processing unit 13 assigns 1 to a counter j.

[0153] (Step S405) The processing unit 13 judges whether or not the user identifier of the jth user for which exchange relationship information processing is performed exists. If the user identifier of the jth user exists, the process proceeds to step S406, and if not, the process proceeds to step S408. Note that exchange relationship information processing is a process of acquiring exchange relationship information for one user and storing it, etc. Also, the processing unit 13 judges, for example, whether or not the user identifier of the jth user exists in the user information storage unit 111.

[0154] (Step S406) The processing unit 13 performs exchange relationship information processing. An example of the exchange relationship information processing will be described with reference to the flowchart of FIG.

[0155] (Step S407) The processing unit 13 increments the counter j by 1. The process returns to step S405.

[0156] (Step S408) The processing unit 13 increments the counter i by 1. The process returns to step S403.

[0157] (Step S409) The business card information accepting unit 121 judges whether or not the business card information has been received. If the business card information has been received, the process proceeds to step S410, and if the business card information has not been received, the process proceeds to step S411.

[0158] (Step S410) The processing unit 13 performs business card information processing. Return to step S401. An example of business card information processing will be described with reference to the flowchart of FIG.

[0159] (Step S411) The receiving unit 12 judges whether or not the exchange information has been received. If the exchange information has been received, the process proceeds to step S412, and if the exchange information has not been received, the process returns to step S401.

[0160] (Step S412) The processing unit 13 performs exchange relationship information processing. Return to step S401. An example of the exchange relationship information processing will be described with reference to the flowchart of FIG.

[0161] In the flowchart of Fig. 4, the process of acquiring exchange relationship information of each user is performed in order for each information server 2. However, the process of acquiring exchange relationship information from one or more information servers 2 for each user may be performed. In other words, the order of the processes in the flowchart of Fig. 4 does not matter.

[0162] 4, exchange relationship information or exchange information that can be the source of exchange relationship information may be acquired in advance for each user and recorded in the storage unit 11 or a device not shown, and at a predetermined timing, the user may be inquired as to whether or not to store the exchange relationship information, and if the answer to the inquiry is to store the information, the exchange relationship information may be stored. Note that the predetermined timing may be, for example, the timing when the user logs in to the exchange management device 1 or the timing when an instruction from the user is received, but the timing is not critical.

[0163] Furthermore, in the flowchart of FIG. 4, the process ends when the power is turned off or an interrupt for ending the process occurs.

[0164] Next, an example of the exchange relationship information processing in steps S406 and S412 will be described with reference to the flowchart of FIG.

[0165] (Step S501) The interaction information determination unit 132 acquires one or more pieces of interaction information corresponding to the user identifier from the information server 2 in which the i-th type of interaction information exists in step S403, or acquires the interaction information received in step S411.

[0166] When the interaction information determination unit 132 acquires one or more pieces of interaction information corresponding to a user identifier from the information server 2, the user identifier acquisition unit 131 acquires the user identifier. The user identifier acquired by the user identifier acquisition unit 131 here is the j-th user identifier in step S405.

[0167] (Step S502) The AC information determination unit 132 assigns 1 to a counter i.

[0168] (Step S503) The exchange information determination unit 132 judges whether or not the i-th exchange information exists among the one or more exchange information acquired in step S501. If the i-th exchange information exists, the process proceeds to step S504, and if the i-th exchange information does not exist, the process returns to the upper process.

[0169] (Step S504) The exchange information determination unit 132 judges whether the i-th exchange information satisfies a predetermined condition. If the i-th exchange information satisfies the predetermined condition, the process proceeds to step S505. If the i-th exchange information does not satisfy the predetermined condition, the process proceeds to step S514.

[0170] (Step S505) The other user information acquisition unit 134 acquires other user information by using the i-th interaction information.

[0171] (Step S506) Questioning unit 133 judges whether to make an inquiry to the user. If an inquiry is to be made, the process proceeds to step S506, and if an inquiry is not to be made, the process proceeds to step S510. Note that, for example, whether to make an inquiry is determined in advance. Also, questioning unit 133 judges whether to make an inquiry depending on the other user information. For example, questioning unit 133 judges whether exchange relationship information corresponding to the other user information acquired in step S505 has already been stored, and if not, judges to make an inquiry.

[0172] (Step S507) The inquiry unit 133 inquires of the user as to whether or not to store exchange relationship information corresponding to the other user information acquired in step S505.

[0173] (Step S508) Interrogator 133 judges whether or not a response to the inquiry result in step S507 has been received from terminal device 3. If a response has been received, the process proceeds to step S509, and if not, the process returns to step S508.

[0174] (Step S509) If the response received in step S508 is a response indicating that the exchange relationship information will be stored, the exchange relationship storage unit 135 proceeds to step S510, and if the response is a response indicating that the exchange relationship information will not be stored, the exchange relationship storage unit 135 proceeds to step S512.

[0175] (Step S510) The exchange relationship accumulation unit 135 acquires exchange relationship information using the other user information acquired in step S505 and the user identifier corresponding to the exchange information.

[0176] (Step S511) The exchange relationship storage unit 135 stores the exchange relationship information acquired in step S510.

[0177] (Step S512) The change determination unit 136 compares the other user information acquired in step S505 with the corresponding user information and determines whether it has been changed (whether there has been a change of position, etc.). If it has been changed, the process proceeds to step S513, and if it has not been changed, the process proceeds to step S514.

[0178] (Step S513) The exchange processing unit 137 performs an exchange process. An example of the exchange process will be described with reference to the flowchart of FIG.

[0179] (Step S514) The AC information determination unit 132 increments the counter i by 1. The process returns to step S503.

[0180] Next, an example of the exchange process in step S513 will be described with reference to the flowchart in FIG.

[0181] (Step S601) The AC processing unit 137 assigns 1 to a counter i.

[0182] (Step S602) The interaction processing unit 137 judges whether or not another i-th user identifier exists. If the i-th user identifier exists, the process proceeds to step S603, and if the i-th user identifier does not exist, the process returns to the upper level process. The interaction processing unit 137 judges whether or not another i-th user identifier exists in, for example, the user information storage unit 111. The interaction processing unit 137 also judges whether or not another i-th user identifier exists in, for example, the interaction relationship storage unit 114.

[0183] (Step S603) The interaction processing unit 137 judges whether the i-th user identifier exists in the interaction relationship information in the interaction relationship storage unit 114 corresponding to the user identifier of the corresponding user (whether there is interaction with a user identified by another i-th user identifier). If there is interaction, the process proceeds to step S604, and if there is no interaction, the process proceeds to step S605.

[0184] (Step S604) The interaction processing unit 137 transmits the acquired other user information to the other user identified by the i-th user identifier.

[0185] (Step S605) The AC processing unit 137 increments the counter i by 1. The process returns to step S602.

[0186] 6, for example, in step S602, the exchange processing unit 137 may obtain a user identifier corresponding to the other user information determined to have been changed in step S512, and determine whether or not the i-th other user information paired with the user identifier exists in the exchange relationship storage unit 114. Then, if the i-th other user information exists in the exchange relationship storage unit 114, the process may proceed to step S604. In this case, step S603 is unnecessary.

[0187] In other words, in the flowchart of FIG. 6, it is sufficient to notify other users who have interactions with the user who has been transferred of the transfer information.

[0188] Next, an example of the business card information processing in step S410 will be described with reference to the flowchart in FIG.

[0189] (Step S701) The other user information acquiring unit 134 acquires the received business card information. Next, the other user information acquiring unit 134 uses the business card information to acquire other user information including other user identifiers.

[0190] (Step S702) The exchange relationship accumulation unit 135 acquires exchange relationship information that associates the other user information acquired in step S701 with the user identifier.

[0191] (Step S703) The exchange relationship storage unit 135 stores the exchange relationship information acquired in step S702.

[0192] (Step S704) The change determination unit 136 compares the other user information acquired in step S701 with the corresponding user information and determines whether it has been changed (whether there has been a change, etc.). If it has been changed, the process proceeds to step S705, and if it has not been changed, the process returns to the upper process.

[0193] (Step S705) The AC processing unit 137 performs the AC process. Then, the process returns to the upper level process. Note that an example of the AC process has been described with reference to the flowchart in FIG.

[0194] In the flowchart of FIG. 7, the processing unit 13 may use the received business card information to configure business card information to be stored, and may store the business card information in the business card information storage unit 112, or the like.

[0195] Next, an example of the operation of the information server 2 will be described. When the server receiving unit 22 of the information server 2 receives exchange information, the server processing unit 23 stores the exchange information in the server storage unit 21. When the server receiving unit 22 receives an instruction to transmit exchange information from the terminal device 3 or the exchange management device 1, the server processing unit 23 transmits the exchange information corresponding to the transmission instruction to the terminal device 3 or the exchange management device 1.

[0196] Next, an example of the operation of the terminal device 3 will be described. The terminal reception unit 32 of the terminal device 3 receives various instructions and information. The terminal processing unit 33 converts the instructions and information received by the terminal reception unit 32 into instructions and information with a data structure to be transmitted. The terminal transmission unit 34 transmits the various instructions and information to the exchange management device 1 and the information server 2. In addition, in response to the transmission of various instructions and information to the exchange management device 1, the terminal reception unit 35 receives various screen information, exchange relationship information, business card information, transfer information, etc. The terminal processing unit 33 converts the information received by the terminal reception unit 35 into information with a data structure to be output. The terminal output unit 36 ​​outputs various screen information, exchange relationship information, business card information, transfer information, etc.

[0197] The specific operation of the AC management system A in this embodiment will be described below. The conceptual diagram of the exchange management system A is shown in Figure 1.

[0198] Now, it is assumed that a user information management table having the structure shown in Fig. 8 is stored in the user information storage unit 111 of the interaction management device 1. The user information management table is a table for managing user information. In this specific example, it is assumed that the user information management table also serves as a business card information management table. In other words, in the user information management table, information having a business card image (e.g., information of "ID=1,2,3") is business card information, and each user attribute value of the user information in the business card information is item information. It is also possible to consider information that does not have a business card image (e.g., information of "ID=384") as business card information. Furthermore, a business card information management table may be stored in the business card information storage unit 112 separately from the user information management table.

[0199] The user information management table manages one or more records having an "ID," "user identifier," "password," "user information," and "business card image." The "user information" has information such as "name," "notification information (email address)," and "company name." Note that the "ID" is information that identifies the record, and although not shown in FIG. 8, it is preferable for the "user information" to have user attribute values ​​such as a department identifier, title, telephone number, fax number, URL, etc.

[0200] Moreover, the domain information storage unit 113 stores a domain information management table shown in Fig. 9. The domain information management table manages one or more records having an "ID", "domain information", and an "organization identifier".

[0201] In addition, the exchange relationship storage unit 114 stores an exchange relationship management table having a structure shown in FIG. 10. The exchange relationship management table is a table that stores one or more exchange relationship information. The exchange relationship management table manages one or more records having "ID", "user identifier", "other user identifier", "type identifier", and "additional information". The other user identifier paired with the user identifier is an identifier of another user who has interacted with the user identified by the user identifier through some exchange means. The "type identifier" is information indicating the type of interaction. Here, the "type identifier" is one of "email (e.g., "1")", "calendar (e.g., "2")", "web conference (e.g., "3")", and "business card (e.g., "4")". The "additional information" is additional information in the exchange relationship information, such as e-mail-related information, business card exchange-related information, calendar-related information, and web conference-related information. Here, the business card exchange-related information has a registration date indicating the date on which the business card information was registered, but may also have other information such as a memo entered by the user. Calendar related information here includes start date / time, end date / time, location, title, etc. Web conference related information here includes start date / time, end date / time, topic, etc.

[0202] The storage unit 11 also stores a business terminology dictionary as shown in Fig. 11. The business terminology dictionary stores character strings such as terms, phrases, or sentences that are frequently used in business situations, business emails, and business-related schedule information.

[0203] The storage unit 11 also stores a non-business term dictionary shown in Fig. 12. The non-business term dictionary stores character strings such as terms, phrases, or sentences that are not used or are rarely used in business situations, business emails, or business-related schedule information.

[0204] The storage unit 11 also stores a condition management table shown in Fig. 13. The condition management table is a table for managing business exchange conditions. The condition management table stores one or more records having an "ID", "business exchange condition", and "type identifier".

[0205] Here, the business exchange condition for "ID=1" is that the recipient's email address contains either "co.jp" or "ac.jp", etc. The business exchange condition for "ID=2" is that there has been two or more email exchanges (one or more replies to an email sent). The business exchange condition for "ID=3" is that the number of business terms in the string of characters in the email is greater than the number of non-business terms. The business exchange condition for "ID=4" is that the calendar appointment information contains business terms. The business exchange condition for "ID=5" is that the calendar appointment information is for a day other than Saturdays, Sundays, and holidays (usually a working day), and the time period indicated by the appointment information is between 9:00 and 18:00.

[0206] Also, in the case where the type identifier is “email”, the exchange information determination unit 132 determines that email that satisfies “ID=1” AND “ID=2” AND “ID=3” is the exchange information that will be the source for obtaining exchange relationship information.

[0207] Also, in the case where the type identifier is “calendar”, the exchange information determination unit 132 determines calendar schedule information that satisfies “ID=4” OR “ID=5” as the exchange information from which exchange relationship information is obtained.

[0208] Furthermore, in the case where the type identifier is "Web conference", the exchange information determination unit 132 determines the calendar schedule information satisfying "ID=6" as exchange information from which exchange relationship information is obtained.

[0209] The exchange management system A has, as information server 2, a mail server 2(1) that manages emails of one or more users, a calendar server 2(2) that manages calendar schedule information of one or more users, and a web conference server 2(3) that manages web conference schedule information of one or more users.

[0210] The server storage unit 21 of the calendar server 2(2) stores a calendar schedule information management table shown in Fig. 14. The calendar schedule information management table manages one or more records having an "ID", "user identifier", "start date and time", "end date and time", "title", etc.

[0211] The server storage unit 21 of the web conference server 2(3) stores a web conference schedule information management table shown in Fig. 15. The web conference schedule information management table manages one or more records having an "ID", "user identifier", "start date and time", "end date and time", "topics", and the like.

[0212] In this situation, the following three concrete examples will be described. Concrete Example 1 is a process in which exchange information is determined using email, calendar schedule information, and web conference schedule information, and other user information corresponding to the exchange information is stored. The stored other user information is information that can be the source of exchange relationship information. Concrete Example 2 is a concrete example that explains a process in which the stored other user information is used to inquire a user as to whether or not to store exchange relationship information, and the exchange relationship information is stored for other user information that answers that the information should be stored. Concrete Example 3 is an example in which exchange relationship information is stored when business card information of a person with whom business cards have been exchanged is received.

[0213] (Example 1) For example, it is assumed that a predetermined time has come and the processing unit 13 of the exchange management device 1 has determined that it is time to obtain exchange information.

[0214] Next, the processing unit 13 acquires the first user identifier "1001" from the user information management table.

[0215] Next, the exchange information determination unit 132 acquires one or more unprocessed emails corresponding to the user identifier "1001" from the mail server 2(1). It is assumed that the exchange information determination unit 132 has a means (API, IP address, etc.) for accessing the mail server 2(1). It is assumed that the unprocessed emails are emails that the exchange information determination unit 132 has not yet read from the mail server 2(1). Here, it is assumed that the exchange information determination unit 132 acquires emails 1601, 1602, etc. shown in FIG. 16, which are addressed to the user identifier "1001", from the mail server.

[0216] Next, the exchange information determination unit 132 judges whether the emails (1601, 1602, etc.) in FIG. 16 satisfy all the business exchange conditions of "ID=1, 2, 3" in FIG. 13. Here, the exchange information determination unit 132 judges that the email 1601 in FIG. 16 satisfies the business exchange condition of "ID=1" because the email address of the sender is "ay@s.jp". Also, the exchange information determination unit 132 detects from the read email (not shown) that Yamada Ichiro, identified by the user identifier "1001", has responded to this email, and judges that the business exchange condition of "ID=2" is satisfied. Furthermore, the exchange information determination unit 132 performs morphological analysis on the character string paired with the <title> of the email 1601 and the character string paired with the <body>, acquires one or more terms, and acquires the number of business terms in the email 1601 by referring to the business term dictionary in FIG. 11. 12, and acquires the number of non-business terms in the email 1601. Then, the exchange information determination unit 132 determines that the email 1601 satisfies the business exchange condition of "ID=3". From the above, the exchange information determination unit 132 determines the email 1601 in FIG. 16 as exchange information that satisfies the predetermined condition.

[0217] Next, the other user information acquisition unit 134 acquires other user information using the exchange information. Specifically, the other user information acquisition unit 134 acquires the character string of the signature part from the email 1601, "Yamamoto Ako, Business Department, Chief, S Corporation, 105-0000 Tokyo, . . . ". Also, the other user information acquisition unit 134 searches the user information management table of FIG. 8 using the acquired character string of the signature part. Next, the other user information acquisition unit 134 acquires other user information "<User Identifier> 1384 <Name> Yamamoto Ako <Email Address> ay@s.jp <Company Name> S Corporation . . . " from the user information management table of FIG. 8. Note that here, the other user information acquisition unit 134 acquires the character string of the signature part from the email, and acquires other user information from the user information management table using the character string. However, the other user information acquisition unit 134 may acquire other user information using the character string of the signature part from the email.

[0218] Next, the other user information acquisition unit 134 pairs the other user information with the user identifier "1001" and the type identifier "email" and accumulates the other user information in the storage unit 11. Note that such other user information is information that may be the source of exchange relationship information.

[0219] Next, the exchange information determination unit 132 judges whether or not the email 1602 in Fig. 16 satisfies all the business exchange conditions of "ID=1, 2, 3" in Fig. 13. Here, the exchange information determination unit 132 judges that the sender's email address of the email 1601 in Fig. 16 is "star@google.com", and therefore does not satisfy the business exchange condition of "ID=1". In other words, the exchange information determination unit 132 judges that the email 1602 in Fig. 16 does not satisfy the business exchange conditions, and does not select it as exchange information that satisfies the predetermined conditions.

[0220] It is assumed that the interaction information determination unit 132 has performed the above process on all the read emails. As a result, it is assumed that the interaction information determination unit 132 has selected only email 1601 as interaction information that satisfies the predetermined condition. Then, it is assumed that the other user information acquisition unit 134 has stored only one other user information corresponding to email 1601, paired with the user identifier "1001".

[0221] Next, the exchange information determination unit 132 refers to the calendar server 2(2) and reads out one or more pieces of schedule information (information having a start date and time, an end date and time, a title, etc.) paired with the user identifier "1001" from the calendar schedule information management table in Fig. 14. Note that the one or more pieces of schedule information paired with the user identifier "1001" includes the schedule information of "ID=1" in Fig. 14.

[0222] Then, the exchange information determination unit 132 judges whether one or more pieces of schedule information satisfy the business exchange condition of "ID=4" or "ID=5" in FIG. 13. Here, the exchange information determination unit 132 acquires the term "meeting" from the title of the calendar schedule information "XX meeting @ Y company Aoki Jiro-san", detects that the term "meeting" of "ID=1" in FIG. 14 exists in the business terminology dictionary of FIG. 11, and judges that the business exchange condition of "ID=4" is satisfied. In addition, the exchange information determination unit 132 judges that the business exchange condition of "ID=5" in FIG. 13 is satisfied using the start date and time "2021 / 1 / 19 16:00" and the end date and time "2021 / 1 / 19 17:00" of the calendar schedule information of "ID=1". Then, the exchange information determination unit 132 determines the calendar schedule information of "ID=1" in FIG. 14 as exchange information that satisfies the predetermined condition.

[0223] Next, the other user information acquisition unit 134 acquires other user information using the interaction information. Specifically, the other user information acquisition unit 134 searches the user information management table of Fig. 8 using "Y Company" and "Aoki Jiro" in the title "XX meeting @Y Company Aoki Jiro" and determines that it matches the record of "ID=3". Then, the other user information acquisition unit 134 acquires other user information "<user identifier>1003 <name>Aoki Jiro <email address>aoki@y.com <company name>Y Company...".

[0224] Next, the other user information acquisition unit 134 pairs the other user information with the user identifier "1001" and the type identifier "calendar" and accumulates the other user information in the storage unit 11. Note that such other user information is information that may be the source of exchange relationship information.

[0225] It is assumed that the interaction information determination unit 132 has performed the above process on all of the read calendar schedule information. As a result, it is assumed that the interaction information determination unit 132 has determined that the second and subsequent calendar schedule information acquired from the calendar server 2(2) did not satisfy the business interaction conditions of "ID=4" and "ID=5" in FIG. 13. It is assumed that the interaction information determination unit 132 has selected only the calendar schedule information of "ID=1" in FIG. 14 as interaction information that satisfies the predetermined conditions. It is assumed that the other user information acquisition unit 134 has stored only one other user information corresponding to the calendar schedule information of "ID=1" in FIG. 14, paired with the user identifier "1001".

[0226] Next, the exchange information determination unit 132 refers to the Web conference server 2(3) and reads out one or more pieces of Web conference schedule information (information including start date / time, end date / time, topics, etc.) paired with the user identifier "1001" from the Web conference schedule information management table in Fig. 15. Note that the one or more pieces of Web conference schedule information paired with the user identifier "1001" includes the Web conference schedule information of "ID=1" in Fig. 15.

[0227] Then, the exchange information determination unit 132 judges whether or not each of the one or more pieces of Web conference schedule information satisfies the business exchange condition of "ID=6" in Fig. 13. Here, the exchange information determination unit 132 judges that the "start date and time, end date and time" of the Web conference schedule information of "ID=1" in Fig. 15 satisfies the business exchange condition of "ID=6". Then, the exchange information determination unit 132 determines the Web conference schedule information of "ID=1" in Fig. 15 as exchange information that satisfies the predetermined condition.

[0228] Next, the other user information acquisition unit 134 acquires other user information using the interaction information. Specifically, the other user information acquisition unit 134 extracts "X Co., Ltd." and "Suzuki Bko" from the character string of the topics, and uses the terms to search the user information management table of Fig. 8 and determines that it matches a certain record (not shown). Then, it is assumed that the other user information acquisition unit 134 acquires other user information "<user identifier>1058 <name>Suzuki Bko <email address>sb@x.com <company name>X Co., Ltd.".

[0229] Next, the other user information acquisition unit 134 pairs the other user information with the user identifier "1001" and the type identifier "web conference" and accumulates the other user information in the storage unit 11. Note that such other user information is information that may be the source of exchange relationship information.

[0230] It is assumed that the interaction information determination unit 132 has performed the above process on all acquired Web conference schedule information. As a result, it is assumed that the interaction information determination unit 132 has determined that the second and subsequent Web conference schedule information acquired from the Web conference server 2 (3) did not satisfy the business interaction condition of "ID=6" in FIG. 13. It is assumed that the interaction information determination unit 132 has selected only the Web conference schedule information of "ID=1" in FIG. 15 as interaction information that satisfies the predetermined condition. It is assumed that the other user information acquisition unit 134 has stored only one other user information corresponding to the Web conference schedule information of "ID=1" in FIG. 15, paired with the user identifier "1001".

[0231] It is assumed that the above process is also performed for the user identifiers of other users.

[0232] (Example 2) Next, assume that a user "Yamada Ichiro" identified by a user identifier "1001" logs into the exchange management device 1 using his / her terminal device 3. Then, after the login process, the processing unit 13 of the exchange management device 1 acquires one or more other user identifiers that are paired with the user identifier "1001" from an exchange relationship management table having the structure shown in FIG. 10. The exchange management device 1 acquires user information that is paired with each of the one or more other user identifiers from the user information management table. In addition, the exchange management device 1 acquires the number of other user information that are paired with the user identifier "1001", "3", using the other user information accumulated in the storage unit 11 in the process of concrete example 1. Then, the exchange management device 1 composes screen information including the acquired user information and the number of other user information "3", and transmits it to the terminal device 3.

[0233] Next, suppose that Yamada Ichiro's terminal device 3 receives the screen information and outputs the screen shown in Fig. 17. In Fig. 17, 1701 is user information of other users who have interactions with Yamada Ichiro. Also, 1702 is information for notifying the existence of other user information stored in pairs with the user identifier "1001". It can also be said that 1702 is information for notifying the existence of other user information that can be the source of exchange relationship information.

[0234] It is assumed that Yamada Ichiro designates the area 1702. The terminal device 3 then accepts the designation and transmits an output instruction for a business card creation screen having the user identifier "1001" to the exchange management device 1. The business card creation screen can be said to be a creation screen for exchange relationship information.

[0235] Next, the receiving unit 12 of the exchange management device 1 receives an output instruction for the business card creation screen having the user identifier "1001."

[0236] Next, the questioning unit 133 obtains three pieces of other user information paired with the user identifier "1001" from the storage unit 11. Next, the questioning unit 133 uses the three pieces of other user information to configure inquiry screen information for inquiring whether or not to perform the business card creation process. Next, the questioning unit 133 transmits the inquiry screen information to Yamada Ichiro's terminal device 3. Note that the business card creation process here refers to the creation of exchange relationship information.

[0237] Next, Yamada Ichiro's terminal device 3 receives the inquiry screen information and outputs the inquiry screen. An example of such output is shown in Fig. 18. In Fig. 18, three pieces of other user information are displayed, and a "Create business card" button 2 is displayed for each piece of other user information. When a "Create business card" button (1801, 1802, 1803) is instructed, the user is instructed to create exchange relationship information using the other user information corresponding to the button.

[0238] 18, it is assumed that Yamada Ichiro has designated all of the "Create business card" buttons 1801, 1802, and 1803.

[0239] Next, Yamada Ichiro's terminal device 3 accepts the instruction and transmits a response to the interaction management device 1 to the effect that "exchange relationship information will be stored" for each of the three pieces of other user information.

[0240] Next, the questioning unit 133 of the exchange management device 1 receives the answer to the effect that "exchange relationship information will be stored" for each of the three pieces of other user information.

[0241] Next, the exchange relationship storage unit 135 uses the other user information corresponding to the "Create business card" button 1801 to acquire the exchange relationship information "<Received date and time> 2021 / 1 / 15 18:00:07 <Title> XX business negotiation <Body>...", the other user identifier "1384", and the type identifier "email", and stores the set of information in the exchange relationship management table of Fig. 10 in association with the user identifier "1001". Such information is the record 1001 in Fig. 10.

[0242] In addition, the exchange relationship storage unit 135 uses the other user information corresponding to the "Create business card" button 1802 to acquire the exchange relationship information "<Start date and time> 2021 / 1 / 19 16:00 <End date and time> 2021 / 1 / 19 17:00 <Location> Y Company <Other> ○○ Meeting", the other user identifier "1003", and the type identifier "Calendar", and stores the set of information in the exchange relationship management table of Fig. 10 in association with the user identifier "1001". Such information is the record of 1002 in Fig. 10.

[0243] In addition, the exchange relationship storage unit 135 uses the other user information corresponding to the "Create business card" button 1803 to acquire the exchange relationship information "<Start date and time> 2021 / 1 / 25 13:00 <End date and time> 2021 / 1 / 25 14:00 <Tobic> Regarding the alliance...", the other user identifier "1058", and the type identifier "Web conference", and stores the set of information in the exchange relationship management table of Fig. 10 in association with the user identifier "1001". Such information is the record of 1003 in Fig. 10.

[0244] Through the above process, exchange relationship information can be accumulated using emails, calendar schedule information, or web conference schedule information.

[0245] (Example 3) On January 18, 2021, Yamada Ichiro inputs business card information including a business card image of "Tanaka Hanako," with whom he exchanged business cards, and a registration instruction into the terminal device 3. Then, the terminal device 3 accepts the business card information and the registration instruction, and transmits the business card information and a registration instruction including the user identifier "1001" to the interaction management device 1.

[0246] Next, the business card information receiving unit 121 of the interaction management device 1 receives the registration instruction including the business card information and the user identifier "1001".

[0247] Next, the other user information acquisition unit 134 acquires the received business card information. Next, the other user information acquisition unit 134 uses the business card information to search the user information management table of FIG. 8 and acquires the other user identifier "1002". In addition, the other user information acquisition unit 134 acquires today's date "2021 / 1 / 18" (registration date) from a clock (not shown).

[0248] Next, the exchange relationship storage unit 135 stores exchange relationship information including the other user identifier "1002", the type identifier "business card", and the registration date "2021 / 1 / 18" in the exchange relationship management table of Fig. 10. Such information is the record of 1004 in Fig. 10.

[0249] As described above, we were able to accumulate information on social relationships by registering the exchange of business cards.

[0250] As described above, according to this embodiment, exchange relationship information regarding ties between users can be acquired and managed by using exchange information such as emails, calendar schedule information, and web conference schedule information.

[0251] Furthermore, according to this embodiment, by storing exchange relationship information after confirming the user's intention to store it, it is possible to store only the exchange relationship information necessary for the user.

[0252] Furthermore, according to this embodiment, by using the user information in user information storage section 111, accurate information on other users can be acquired and managed.

[0253] Furthermore, according to this embodiment, exchange relationship information acquired based on the exchange of business cards can also be managed.

[0254] Furthermore, according to this embodiment, if it is determined that there has been a change in other user information acquired using communication information such as e-mails, appropriate action can be taken.

[0255] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software for realizing the exchange management device 1 in this embodiment is a program as follows. That is, this program causes a computer to function as a user identifier acquisition unit that acquires a user identifier, an exchange information determination unit that determines, from one or more pieces of exchange information, exchange information that is information about an exchange between two or more users and corresponds to the user identifier acquired by the user identifier acquisition unit and satisfies a predetermined condition, a different user information acquisition unit that acquires other user information including a user identifier that is different from the user identifier acquired by the user identifier acquisition unit and corresponds to the exchange information determined by the exchange information determination unit, and an exchange relationship storage unit that accumulates exchange relationship information that associates the other user information with the user identifier.

[0256] Fig. 19 shows the appearance of a computer that executes the program described in this specification to realize the AC management device 1 of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and a computer program executed thereon. Fig. 19 is an overview of this computer system 300, and Fig. 20 is a block diagram of the system 300.

[0257] In FIG. 19, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0258] 20, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0259] A program for causing computer system 300 to execute the functions of AC management device 1 of the above-described embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and further transferred to hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 at the time of execution. The program may also be loaded directly from CD-ROM 3101 or the network.

[0260] The program does not necessarily include an operating system (OS) or a third party program that causes the computer 301 to execute the functions of the AC management device 1 of the above-mentioned embodiment. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner to obtain a desired result. How the computer system 300 operates is well known, and a detailed description will be omitted.

[0261] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmitting step (processing that is performed only by hardware).

[0262] The program may be executed by a single computer or a plurality of computers. That is, the program may be executed by a centralized processing or a distributed processing.

[0263] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0264] In each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0265] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0266] As described above, the interaction management device of the present invention has the effect of being able to acquire and manage interaction relationship information regarding ties between users using interaction information regarding interactions other than the exchange of business cards, and is useful as a server for managing interaction relationship information. [Explanation of symbols]

[0267] A Exchange Management System 1 AC control device 2 Information Server 3 Terminal Equipment 11 Storage area 12 Receiving section 13 Processing section 14 Transmitter 21 Server Storage 22 Server Receiving Unit 23 Server Processing Unit 24 Server transmission section 31 Terminal storage section 32 Terminal Reception 33 Terminal Processing Section 34 Terminal transmitter 35 Terminal receiving section 36 Terminal Output Section 111 User information storage section 112 Business card information storage section 113 Domain information storage section 114 Exchange Relationship Storage Unit 121 Business Card Information Reception Department 131 User Identifier Acquisition Unit 132 Exchange Information Determination Department 133 Question Section 134 Other user information acquisition unit 135 Exchange Relationships Department 136 Change Judgment Unit 137 AC Processing Unit

Claims

1. a user identifier acquisition unit that acquires a user identifier; an exchange information determination unit that determines, from among one or more pieces of exchange information, exchange information that is information regarding an exchange between two or more users, corresponds to the user identifier acquired by the user identifier acquisition unit, and satisfies a predetermined condition; a different user information acquisition unit that acquires different user information including a user identifier that is different from the user identifier acquired by the user identifier acquisition unit and corresponds to the interaction information determined by the interaction information determination unit; an exchange relationship storage unit that stores exchange relationship information that associates the other user information with the user identifier; A change determination unit that determines whether there is a change in other user information corresponding to the interaction information; and an AC processing unit that performs a predetermined process when the change determination unit determines that there is a change.

2. The exchange information is an email, the predetermined conditions are conditions regarding a response by email, The exchange information determination unit is The exchange management device according to claim 1 , further comprising: determining exchange information that corresponds to the user identifier acquired by the user identifier acquisition unit and that satisfies the predetermined condition.

3. a questioning unit for asking a user whether or not to store the exchange relationship information, The exchange relationship storage unit includes:

3. The exchange management device according to claim 1, wherein the exchange relationship information is stored only when a result of an inquiry by the interrogation section indicates that the exchange relationship information should be stored.

4. The interaction information is calendar schedule information, which is schedule information input to a calendar server, or web conference schedule information, which is schedule information input to a web conference server, The exchange information determination unit is determining schedule information that satisfies a predetermined condition from one or more pieces of schedule information corresponding to the user identifier acquired by the user identifier acquisition unit; The other user information acquisition unit, The interaction management device according to claim 1 , further comprising: acquiring other user information using the schedule information determined by the interaction information determination unit.

5. a business card information receiving unit that receives business card information relating to the business card of another user in association with the user identifier; a processing unit that associates the business card information with the user identifier and accumulates the business card information in a business card information storage unit in which the business card information is stored, The other user information acquisition unit, Acquire other user information including another user identifier corresponding to the business card information; The exchange relationship storage unit includes: The interaction management device according to claim 1 , further comprising: exchange relationship information that associates the other user information with the user identifier.

6. An AC management method comprising all steps performed by an AC management device according to any one of claims 1 to 5.

7. Computer, A program for causing an AC management device to function as the AC management device according to any one of claims 1 to 5.

Images