WO2022185556A1

WO2022185556A1 - Interaction management device, interaction management method, and recording medium

Info

Publication number: WO2022185556A1
Application number: PCT/JP2021/024285
Authority: WO
Inventors: 親弘寺田; 洋千住
Original assignee: Sansan株式会社
Priority date: 2021-03-05
Filing date: 2021-06-28
Publication date: 2022-09-09
Also published as: JP2022135971A

Abstract

[Problem] To acquire and manage interaction relation information on connection among users by using interaction information on interaction other than exchange of business cards. [Solution] An interaction management device 1 comprises a user identifier acquisition unit 131 that acquires a user identifier, an interaction information determination unit 132 that determines, among one or more pieces of interaction information, interaction information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and satisfying a predetermined condition, an other user information acquisition unit 134 that acquires other user information including another user identifier that is different from the user identifier acquired by the user identifier acquisition unit 131 and corresponds to the interaction information determined by the interaction information determination unit 132, and an interaction relation accumulation unit 135 that accumulates interaction relation information that associates the other user information with the user identifier, to thereby enable acquisition and management of interaction relation information on connection among users by using interaction information on interaction other than exchange of business cards.

Description

AC control device, AC control method, and recording medium

The present invention relates to an exchange management device or the like that uses exchange information concerning exchanges between two or more people to manage information concerning exchanges.

Conventionally, there was a business card exchange system that managed the exchange of business cards (see Patent Document 1, for example).

JP 2020-129309 A

However, in the conventional technology, it was not possible to acquire and manage interaction relationship information relating to connections between users using information relating to interactions other than the exchange of business cards.

The interaction management device of the first invention comprises a user identifier acquisition unit that acquires a user identifier, and information related to interaction between two or more users, which is information corresponding to the user identifier acquired by the user identifier acquisition unit. a user identifier different from the user identifier acquired by the interaction information determining unit that determines, from among one or more pieces of interaction information, interaction information that satisfies a predetermined condition, and the interaction information; Other user information acquisition unit for acquiring other user information including a user identifier corresponding to the interaction information determined by the determination unit, and an interaction relationship storage unit for storing interaction relationship information that associates the other user information with the user identifier. It is an exchange management device.

With this configuration, it is possible to acquire and manage interaction relationship information related to connections between users using interaction information.

Further, in the exchange management device of the second invention, in contrast to the first invention, the predetermined condition is a business exchange condition for determining that the exchange is for business, and the exchange information determination unit and an exchange management device that determines exchange information that is exchange information corresponding to a user identifier acquired by a user identifier acquisition unit and that satisfies a business exchange condition.

With this configuration, it is possible to acquire and manage interaction relationship information relating to business ties between users using interaction information.

In addition, the interaction management device of the third invention further comprises an inquiry unit for inquiring of the user whether or not to store the interaction relationship information with respect to the first or second invention, and the interaction relationship storage unit comprises: The exchange management device accumulates the exchange relation information only when the result of the inquiry by the inquiry unit is the result of accumulating the exchange relation information.

With such a configuration, it is possible to accumulate only the exchange relationship information necessary for the user.

In addition, in the exchange management device of the fourth invention, in any one of the first to third inventions, the other user information acquisition unit includes a character string or exchange information included in the exchange information determined by the exchange information determination unit. Using the user identifier corresponding to the information, search a user information storage unit that stores one or more pieces of user information having a user identifier and one or more user attribute values, and use the search result to acquire other user information. It is an exchange management device that

With this configuration, it is possible to acquire and manage accurate other user information using the user information in the user information storage unit.

Further, in the exchange management device of the fifth invention, in contrast to any one of the first to fourth inventions, the exchange information is an email, and the exchange information determination unit is configured to use the user identifier acquired by the user identifier acquisition unit. determines an email that satisfies a predetermined condition from the emails sent to the email address corresponding to the other user information acquisition unit uses the email determined by the interaction information determination unit to acquire other user information , is an exchange management device.

With this configuration, it is possible to acquire and manage exchange relationship information related to connections between users using emails stored in the mail server.

Further, in the exchange management device of the sixth invention, in contrast to the fifth invention, the other user information acquisition unit obtains the other user information using the information of the signature in the mail determined by the exchange information determination unit. It is an exchange management device to acquire.

With this configuration, it is possible to acquire and manage exchange relationship information related to connections between users using email signatures stored in the mail server.

Further, in the exchange management device of the seventh invention, in contrast to the fifth or sixth invention, the other user information acquisition unit acquires the domain name of the mail address of the mail sender determined by the exchange information determination unit. Then, an organization identifier corresponding to the domain name is obtained from the domain information storage unit storing one or more pieces of domain information having a pair of the domain name and the organization identifier, and other user information is obtained using the organization identifier. It is an exchange management device.

Further, in the exchange management device of the eighth invention, for any one of the fifth to seventh inventions, the predetermined condition is a condition regarding a mail address, and the exchange information determining unit stores It is an exchange management device that determines an e-mail that satisfies a predetermined condition by using the e-mail address of the sender of each of one or more e-mails.

With this configuration, it is possible to acquire and manage exchange relationship information related to connections between users using email addresses of emails.

Further, the exchange management apparatus of the ninth invention is an exchange management apparatus in which, in contrast to any one of the fifth to eighth inventions, the other user information includes mail-related information regarding mail.

With such a configuration, it is also possible to manage email-related information.

Further, in the exchange management device of the tenth invention, in contrast to any one of the first to fourth inventions, the exchange information is schedule information for specifying a schedule of the user, and the exchange information determination unit includes a user identifier Determines schedule information that satisfies a predetermined condition from one or more schedule information corresponding to the user identifier acquired by the acquisition unit, and the other user information acquisition unit uses the schedule information determined by the exchange information determination unit, It is an exchange management device that acquires other user information.

With this configuration, it is possible to acquire and manage exchange relationship information related to connections between users using the schedule information stored in the calendar server.

Further, an exchange management device of the eleventh invention is, in relation to any one of the first to tenth inventions, a business card information accepting unit that accepts business card information related to business cards of other users in association with the user identifier; The other user information acquisition unit acquires other user information including another user identifier corresponding to the business card information, and the interaction relationship storage unit stores interaction relationship information that associates the other user information with the user identifier. is.

With such a configuration, it is also possible to manage the interaction information acquired based on the exchange of business cards.

Further, the exchange management device of the twelfth invention determines whether or not there is a change in other user information corresponding to exchange information or business card information for any one of the first to eleventh inventions. The exchange management device further includes a change determination unit and an exchange processing unit that performs predetermined processing when the change determination unit determines that there is a change.

With this configuration, it is possible to take appropriate action when it is determined that there is a change in other user information acquired using exchange information such as e-mail.

According to the interaction management device of the present invention, it is possible to acquire and manage interaction relationship information relating to connections between users using interaction information relating to interactions other than business card exchanges.

Conceptual diagram of exchange management system A in Embodiment 1 Block diagram of the exchange management system A Block diagram of the same exchange management device 1 Flowchart explaining an operation example of the same exchange management device 1 Flowchart explaining an example of the same exchange relationship information processing Flowchart for explaining an example of same exchange processing Flowchart explaining an example of business card information processing Diagram showing an example of the same user information management table Diagram showing an example of the same domain information management table Diagram showing an example of the exchange relationship management table Diagram showing an example of the same business term dictionary Diagram showing an example of the same non-business term dictionary Diagram showing an example of the same condition management table Diagram showing an example of the same calendar schedule information management table Diagram showing an example of the web conference schedule information management table Diagram showing an example of the same email Diagram showing an example of the same screen Diagram showing an example of the same screen Overview of the computer system Block diagram of the same computer system

Embodiments of the exchange management device, etc. will be described below with reference to the drawings. It should be noted that, since components denoted by the same reference numerals in the embodiments perform similar operations, repetitive description may be omitted.

(Embodiment 1)
In the present embodiment, by using exchange information acquired from an information server storing two or more pieces of exchange information relating to exchanges between two or more people, information on other users who are the exchange partners is acquired, An exchange management system including an exchange management device that accumulates exchange relationship information that associates information on other users with user identifiers will be described. Note that the exchange information is, for example, e-mail, reservation information registered in a calendar server, or reservation information registered in a web conference server.

Further, in the present embodiment, regarding an exchange management system having an exchange management device that determines one or more business exchange information, which is exchange information related to business, from two or more pieces of exchange information, and acquires other user information from the business exchange information explain.

In addition, in the present embodiment, an exchange management system including an exchange management device that inquires the user as to whether or not to accumulate exchange relationship information and accumulates exchange relationship information when the answer is yes will be described.

In addition, in the present embodiment, an exchange management device that acquires accurate other user information from the user information storage unit using exchange information etc., acquires exchange relationship information using the other user information, and accumulates it The provided exchange management system will be described.

Further, in the present embodiment, other user information is acquired from the exchange information, which is an email sent to the email address corresponding to the user identifier, and interaction relationship information is acquired and accumulated using the other user information. An exchange management system having an exchange management device will be described.

In addition, in the present embodiment, an exchange management system equipped with an exchange management device that acquires other user information from email signatures will be described.

In addition, in the present embodiment, a communication management system including a communication management device that acquires the domain name of the email address of the sender of the email and acquires the organization name corresponding to the domain name from the domain DB will be described.

In addition, in the present embodiment, an exchange management system including an exchange management device that determines whether or not an email is business exchange information using the email address of the sender of the email will be described.

In addition, in the present embodiment, an exchange management system equipped with an exchange management device that also accumulates mail-related information such as the date and time of mail reception, the text of the mail, and the title will be described.

In addition, in the present embodiment, an exchange management system including an exchange management device that also accepts and accumulates business card information will be described. Further, an exchange management system including an exchange management device that acquires and accumulates exchange relationship information using the business card information when business card information is also received will be described.

Furthermore, in the present embodiment, an exchange management system equipped with an exchange management device that performs a predetermined action using exchange relationship information will be described.

FIG. 1 is a conceptual diagram of an exchange management system A according to this 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 .

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. In addition, the kind of exchange management apparatus 1 is not asked. Further, the details of the interaction relationship information will be described later.

The information server 2 is a server that stores one or more exchange information. The information server 2 is, for example, a mail server, a calendar server that stores schedule information for each time slot in a calendar, and a web conference server that stores schedule information for web conferences. The calendar server is, for example, a Google calendar server or a CalDAV server. Also, the web conference server is a server that manages information on web conferences such as Zoom (registered trademark) and Teams.

The information server 2 receives, for example, one or more emails obtained from the mail server, one or more schedule information obtained from the calendar server, and one or more schedule information obtained from the web conference server. may be a server that stores one or two or more types of information. The information server 2 is, for example, a cloud server, an ASP server, or the like. Note that the type of the information server 2 does not matter.

The terminal device 3 is a terminal used by the user. The terminal device 3 is, for example, a terminal that transmits business card information to the exchange management device 1, transmits answers 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 smart phone, etc., and the type thereof does not matter.

The exchange management device 1 is preferably 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 LAN.

FIG. 2 is a block diagram of the exchange management system A according to this embodiment. FIG. 3 is a block diagram of the exchange management device 1. As shown in FIG.

The exchange management device 1 includes a storage unit 11, a reception unit 12, a processing unit 13, and a transmission 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 interaction relationship storage unit 114 . The reception unit 12 includes a business card information reception unit 121 . The processing unit 13 includes a user identifier acquisition unit 131 , an interaction information determination unit 132 , a question unit 133 , another user information acquisition unit 134 , an interaction relationship accumulation unit 135 , a change determination unit 136 and an interaction processing unit 137 .

The information server 2 includes a server storage unit 21, a server reception unit 22, a server processing unit 23, and a server transmission unit 24.

The terminal device 3 includes a terminal storage unit 31, a terminal reception unit 32, a terminal processing unit 33, a terminal transmission unit 34, a terminal reception unit 35, and a terminal output unit 36.

Various types of information are stored in the storage unit 11 that constitutes the exchange management device 1 . The various types of information are, for example, user information (to be described later), business card information (to be described later), domain information (to be described later), interaction information, interaction relationship information, and various screen information. Various types of screen information are, for example, inquiry screen information for forming an inquiry screen, and interaction-related screen information forming a screen containing one or more pieces of interaction-related information. The screen information is implemented by HTML, XML, or a program, for example, but any implementation means, structure, or the like may be used.

The exchange information is information related to exchanges between two or more users. The exchange information is information from which exchange relationship information, which will be described later, is obtained. Exchange information includes, for example, email, calendar schedule information that is schedule information input to a calendar server, and web conference schedule information that is schedule information input to a web conference server. Mail is electronic mail. The exchange information may or may not include information related to exchanging business cards. Note that the calendar server may be called a schedule management server or the like. The web conference server may be called a web conference information management server or the like.

The calendar schedule information includes, for example, one or more of information such as the name of the other party of the meeting, the name of the company of the other party, the start time of the meeting, the end time of the meeting, the location of the meeting, and the like.

The web conference schedule information includes, for example, one or more of information such as the name of the other party of the conference, the name of the company of the other party, the start time of the web conference, the end time of the web conference, and the like.

It should be noted that calendar schedule information and web conference schedule information can be referred to as schedule information without distinguishing between them.

The interaction relationship information is information indicating that two or more users have interacted or have interacted with each other. The interaction relationship information may be any information that can identify the interaction relationship. The interaction relationship information is usually information that associates other user information with user identifiers. The interaction relationship information may be information having other user information and a user identifier, the interaction relationship information may be link information between the other user information and the user identifier, or other user information associated with the user identifier. good. The interaction relationship information may be any information indicating that two or more users have interacted or that there is an interaction, and the data structure and contents thereof are not limited. A user identifier is information that identifies a user. The user identifier is, for example, a user ID, an e-mail address, a telephone number, a terminal identifier of the terminal device 3 used by the user, etc., but any information that can identify the user may be used. The identifier of the terminal device 3 is, for example, an IP address or MAC address. Other user information is information about other users. The other user is a user other than the user identified by the user identifier associated with the other user information. The other user information is, for example, one or more of the user identifier of the other user and one or more user attribute values of the other user. User attribute values are, for example, a name, an organization identifier of an organization to which the user belongs, a position, a telephone number, a FAX number, an address, and a URL. The organization identifier is, for example, a company name or organization name. The address is, for example, the address of the organization to which the user belongs, or the address of the person's home. The URL is the URL of the home page of the organization to which the user belongs.

The user information storage unit 111 stores one or more pieces of user information. User information is information about a user. User information has a user identifier that identifies a user. User information may be associated with a user identifier. 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 more preferable that the user information in the user information storage unit 111 is guaranteed to be correct 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 looking at the business card image of each user.

The business card information storage unit 112 stores one or more business card information. The business card information is information related to business cards. Business card information is associated with a user identifier. The user identifier corresponding to the business card information of one user and the user identifier included in the user information of the one user are preferably the same information, but may be different information. However, it is preferable to associate the business card information of one user with the user information of the one user. The business card information is information related to the business card of the user. The business card information has, for example, a business card image and one or more item information. The item information is information that constitutes a business card. The item information includes, for example, name, organization identifier of belonging organization, title, telephone number, FAX number, address, and URL. The item information may be the same as the user attribute value.

It should be noted that the user information of one user in the user information storage unit 111 and the business card information in the business card information storage unit 112 may be partially or wholly the same information.

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 (domain name) of the email address and the organization identifier. The domain information is, for example, a set of a domain character string of an email address and an organization identifier. Domain information is, for example, information indicating a link between a character string of a domain of an e-mail address and an organization identifier.

The interaction relationship storage unit 114 stores one or more interaction relationship information. Contact information typically corresponds to a user identifier. It should be noted that corresponding to the user identifier may include the user identifier. The interaction relationship information in the interaction relationship storage unit 114 is information specifying interaction with other users of the user identified by the user identifier. The interaction 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 interaction, such as "mail", "calendar", "web conference", and "business card". “Mail” is information indicating that there was an exchange by e-mail. "Calendar" is information indicating that there was an interaction corresponding to the schedule information registered in the calendar server. "Web conference" is information indicating that there was an exchange through a web conference. "Business card" is information indicating that there was an interaction corresponding to the reception of the business card.

The receiving unit 12 receives various types of information. Various kinds of information are, for example, a start instruction, exchange information, business card information, a user identifier, and an instruction to send various kinds of information. The start instruction is an instruction to start a process of acquiring one or more pieces of exchange information from each of one or more information servers 2 . The various information transmission instructions are, for example, user information transmission instructions, business card information transmission instructions, and exchange relationship information transmission instructions.

The business card information reception unit 121 receives business card information related to business cards of other users in association with user identifiers. The user identifier here is the identifier of the user who received the business card corresponding to the business card information. A user identifier here is an identifier of one user who is not another user.

Acceptance here usually means reception from the terminal device 3, but acceptance of information input from an input device such as a keyboard, mouse, or touch panel, or reading from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory. It is a concept that includes the reception of information that has been received.

The processing unit 13 performs various types of processing. The various processes are, for example, processes performed by the user identifier acquisition unit 131, the interaction information determination unit 132, the question unit 133, the other user information acquisition unit 134, the interaction storage unit 135, the change determination unit 136, and the interaction processing unit 137. be.

The processing unit 13 acquires various types of information in accordance with various information transmission instructions. For example, the processing unit 13 acquires the interaction relationship information from the interaction relationship storage unit 114 according to an instruction to transmit the interaction relationship information.

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 whose interaction information is to be acquired. The user identifier acquisition unit 131 acquires one or more user identifiers stored in the user information storage unit 111, for example. The user identifier acquisition unit 131 acquires, for example, a user identifier transmitted from the terminal device 3 and received by the reception 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.

The exchange information determination unit 132 determines, from among one or more pieces of exchange information, exchange information that is exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and that satisfies a predetermined condition. One or more pieces of exchange information are information obtained directly or indirectly from the information server 2 . The one or more exchange information includes, for example, one or more exchange information received by the receiving unit 12, one or more exchange information stored in the storage unit 11, and one or more exchange information stored in each of the one or more information servers 2. exchange information, one or more pieces of exchange information stored in an information processing device (not shown) obtained from one or more information servers 2; The exchange information is preferably information originally stored in the information server 2 . Exchange information is e-mail and schedule information, for example. The exchange information may be information obtained by processing the information originally stored in the information server 2 .

Determining exchange information includes, for example, obtaining exchange information and obtaining a link to exchange information.

Predetermined conditions are, for example, business exchange conditions. The business interaction condition is a condition specifying that it is an interaction in business.

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

The exchange information determination unit 132 determines, for example, exchange information that is exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and that satisfies the business exchange conditions.

The interaction information determining unit 132 determines emails that meet predetermined conditions from one or more emails sent to the email address corresponding to the user identifier acquired by the user identifier acquiring unit 131 . The predetermined conditions here are appropriately referred to as mail conditions.

The exchange information determination unit 132 determines an email that satisfies the email conditions by using the email addresses of the senders of one or more stored emails.

The e-mail conditions are, for example, e-mail response conditions, e-mail address conditions, and e-mail content conditions.

　The condition for responding by e-mail is, for example, that two users have sent and replied to the e-mail. This condition is a condition for not regarding the case of only one-sided mail transmission as communication.

The condition for responding to e-mails is, for example, that two users exchange at least N times (N is a natural number equal to or greater than 2). Such a condition is, for example, a condition for not considering small exchanges or one-sided mail transmissions as the exchanges of the present application.

The condition for replying by e-mail is, for example, that two users have exchanged N times or more in a predetermined period (for example, three months or one year). It is a condition for not considering it as an exchange of the present application.

The e-mail address condition is that the e-mail address of the other party (e.g. source of e-mail, destination of e-mail) contains a predetermined character string (e.g., "co.jp", "ac.jp", etc.). . A condition regarding the e-mail address is that the e-mail address of the other party does not contain a predetermined character string. The e-mail address condition is, for example, that the other party's e-mail address is not an e-mail address considered to be a personal e-mail address (for example, an address including "gmail.com" or "yahoo.co.jp").

The condition regarding the content of the email is, for example, that it is not spam. It should be noted that a known mailer technique can be used as a technique for judging whether or not an email is spam. Further, the condition regarding the content of the mail is, for example, that the mail contains many terms stored in a business term dictionary (not shown). A mail containing a large number of terms means that it contains a number of terms equal to or greater than a threshold value, or contains terms equal to or greater than a threshold value or in a ratio greater than a threshold value. In addition, the conditions regarding the content of the email are, for example, the result of classification processing (prediction processing) using a machine learning classifier (learning model, learning device, etc.). It is to be judged to be mail. Such a classifier is data obtained by performing learning processing using a machine learning algorithm using one or more positive examples of business emails and one or more negative examples of non-business emails as training data. . For machine learning, so-called deep learning, random forest, decision tree, SVM, etc. can be used, but any algorithm can be used. As machine learning, for example, various TensorFlow modules, R language random forest modules, TinySVM, etc. can be used. A business term dictionary is a storage area such as a database or a file in which two or more terms used in business are accumulated. A business term can be a phrase or a sentence. Phrases and sentences are, for example, "I am always indebted to you", "Thank you for your continued support", "KingRegards", and the like.

The exchange information determination unit 132 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 131 . Such predetermined conditions are appropriately referred to as scheduled conditions.

A schedule condition is, for example, schedule information for a work day (for example, Monday to Friday). The schedule condition is, for example, schedule information for a schedule during working hours on a working day (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. It should be noted that the schedule information including the organization identifier includes, for example, a predetermined character string indicating the company, such as "stock company", "limited company", and "stock company". Machine learning can also be used to identify whether a string is an organization identifier. That is, the interaction information determination unit 132 provides a classifier that classifies whether or not it is an organization identifier and a character string acquired from the schedule information to a module that performs machine learning prediction processing, and the classification result (organization identifier whether or not) may be obtained. Such a classifier is data obtained by providing one or more positive examples that are tissue identifiers and one or more negative examples that are not tissue identifiers to a module that performs machine learning processing. In addition, as described above, deep learning, random forest, decision tree, SVM, etc. can be used for such machine learning as well, but any algorithm can be used.

Also, the predetermined condition may be, for example, that the answer to an inquiry by the inquiry unit 133, which will be described later, is an answer to the effect that "accumulate exchange relationship information".

The questioning unit 133 asks the user whether or not to store the interaction relationship information. Inquiring of the user means, for example, transmitting to the user's terminal device 3, but it does not have to be an active inquiry, and the inquiry method does not matter. Moreover, the timing and trigger of such inquiry to the user are not limited.

For example, when the exchange management device 1 is accessed from the user's terminal device 3, the inquiry unit 133 displays screen information (inquiry screen information) to the terminal device 3. The inquiry screen is, for example, a screen including an interface such as a button or menu item for instructing accumulation of the interaction information, a screen including a message asking the user whether or not to accumulate the interaction relationship information, or the like. The question part 133 transmits inquiry screen information to the terminal device 3 after logging in to the exchange management apparatus 1, for example. For example, when the exchange management device 1 receives an instruction to output an inquiry screen from the terminal device 3 , the inquiry unit 133 transmits inquiry screen information to the terminal device 3 . For example, the question unit 133 asks the user whether or not to accumulate the interaction relationship information each time the interaction information is acquired. The questioning unit 133 asks the user, for example, at a predetermined date and time (for example, "every day at 12:00", "10:00 on the first day of every month", etc.). The inquiry unit 133 inquires of the user, for example, when an instruction having a user identifier is received. Note that this instruction is an instruction to accumulate exchange relationship information.

The other user information acquisition unit 134 acquires other user information including other user identifiers. The other user identifier is another user identifier different from the user identifier acquired by the user identifier acquisition unit 131 .

The other user information acquisition unit 134 acquires other user information, for example, using exchange information. Other user information acquisition unit 134 acquires other user information, for example, using information corresponding to exchange information.

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 obtains the search result. to obtain other user information. The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, a character string (for example, name and company name) included in the exchange information determined by the exchange information determination unit 132 as a key, and retrieves the character string. Acquire other user information including part or all of the included user information. 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, and includes a character string that matches or is similar to the character string. User information is determined, a user identifier corresponding to the user information is acquired as another user identifier, and other user information including the other user identifier is acquired. A similar character string is a character string with the maximum degree of similarity, or a character string with a degree of similarity greater than or equal to a threshold.

Hereinafter, when the exchange information is email, when the exchange information is calendar schedule information, when the exchange information is web meeting schedule information, and when the business card information received by the business card information receiving unit 121 is received, the other user The operation of the information acquisition unit 134 will be described.
(1) When exchange information is email

The other user information acquisition unit 134 acquires other user information, for example, using the email determined by the exchange information determination unit 132.

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

It should be noted that the other user information here may include mail-related information regarding mail. The mail-related information is, for example, one or more of the date and time of mail reception, the text of the mail, the title of the mail, and the like.

For example, the other user information acquisition unit 134 detects a signature character string from the email determined by the interaction information determination unit 132, and acquires one or more user attribute values from the signature character string. Note that the user attribute value includes, for example, one or more information among name, company name, department name, title, address, telephone number, FAX number, e-mail address, and URL. Then, the other user information acquisition unit 134 acquires, for example, other user information having the one or more user attribute values.

The other user information acquisition unit 134 detects, for example, a character string of a signature from the mail determined by the interaction information determination unit 132 (usually received mail here), and from the character string of the signature, one or more users An attribute value is acquired, the user information storage unit 111 is searched using the one or more user attribute values, and other user information having part or all of matching user information is acquired.

It should be noted that the method by which the other user information acquisition unit 134 detects the signature character string from the mail does not matter. For example, the other user information acquisition unit 134 examines the lines above the lowest line having characters in the mail, detects a blank line having no characters, and extracts characters from the line next to the blank line. Get up to the lowest line with the signature area as a character string. The other user information acquisition unit 134, for example, checks from the first line of the mail, and continues the signature delimiter line (for example, the character “*”, “━”, “+”, etc.), which is a line having a predetermined character string. and a row having a predetermined number or more) to the row one row above the signature delimiter row, which is a row below the row, as a character string in the signature area. The other user information acquisition unit 134, for example, retrieves the character strings of a predetermined number of lines immediately below a line containing a specific character string in the mail (for example, a line containing "Best Regards", "Thank you for your consideration", etc.) as a string in the signature area.

The other user information acquisition unit 134 acquires the domain name of the email address of the sender of the email determined by the exchange information determination unit 132 (received email here), and combines the organization identifier corresponding to the domain name with the domain name and the organization identifier. from the domain information storage unit 113 that stores one or more pieces of domain information having a pair with and, using the organization identifier, other user information is acquired.

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 obtains other user information having one or more user attribute values that the matching user information has. get.

The other user information acquisition unit 134 acquires the email address of the sender of the email determined by the exchange information determination unit 132 (received email here), searches the user information storage unit 111 using the email address, and finds a match. acquire other user information that has part or all of the user information that Note that the user information here usually includes one or more attribute values of the correct user.

The other user information acquisition unit 134 acquires the name or the like that is the character string before the predetermined character string “Mr.” “Mr.” “Mr.” , the user information storage unit 111 is searched, and other user information having part or all of the matching user information is acquired.

The other user information acquisition unit 134 acquires a character string including the first character of the mail (here, outgoing mail) determined by the interaction information determination unit 132 as a name, etc., and uses the name, etc. to store information in the user information storage unit 111 to acquire other user information having part or all of the matching user information.
(2) When exchange information is calendar schedule information

The other user information acquisition unit 134 uses the calendar schedule information determined by the exchange information determination unit 132 to acquire other user information. The other user information here may include part or all of the calendar schedule information. A part or all of the calendar schedule information is, for example, the start date and time of the meeting, the place of the meeting, information specifying that the meeting is face-to-face, and the like.

Other user information acquisition unit 134, for example, from the calendar schedule information determined by exchange information determination unit 132, acquires one or more attribute values (for example, company name, name, etc.), and uses the one or more attribute values , the user information storage unit 111 is searched, and other user information having part or all of the matching user information is acquired.
(3) When exchange information is web conference schedule information

The other user information acquisition unit 134 uses the web conference schedule information determined by the exchange information determination unit 132 to acquire other user information. The other user information here may include part or all of the web conference schedule information. Information of part or all of the web conference schedule information is, for example, the start date and time of the conference, information specifying that it is a web conference, and the like.

Other user information acquisition unit 134, for example, acquires one or more attribute values (for example, company name, name, etc.) from the web conference schedule information determined by exchange information determination unit 132, and uses the one or more attribute values. Then, the user information storage unit 111 is searched, and other user information having part or all of the matching user information is acquired.
(4) When the business card information accepted by the business card information accepting unit 121 is accepted

The other user information acquisition unit 134 may acquire other user information including other user identifiers corresponding to the business card information accepted by the business card information acceptance unit 121 .

The other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more items of information included in the business card information, and retrieves other user information having part or all of matching user information. to get

The other user information acquisition unit 134 acquires other user information including, for example, one or more item information included in the business card information received by the business card information reception unit 121 .

The interaction relationship storage unit 135 stores interaction relationship information that associates other user information with user identifiers. In addition, other user information here is the information which the other user information acquisition part 134 acquired. Also, the user identifier here is information obtained by the user identifier obtaining unit 131 .

For example, the interaction relationship storage unit 135 stores interaction 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.

The interaction relationship storage unit 135 stores, for example, interaction relationship information having 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 .

For example, the interaction relationship storage unit 135 stores interaction 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.

It does not matter where the interaction relationship accumulation unit 135 accumulates the interaction relationship information. The interaction relationship accumulation unit 135 accumulates interaction relationship information in the interaction relationship storage unit 114, for example. However, the exchange relation accumulation unit 135 may accumulate the exchange relation information in another device (not shown). It is preferable that the interaction relationship accumulation unit 135 accumulates the interaction relationship information in a device that uses the interaction relationship information.

For example, the interaction relationship accumulation unit 135 accumulates the interaction relationship information only when the result of the inquiry by the question unit 133 is to accumulate the interaction relationship information. In other words, it is preferable to store only the interaction relationship information that the user has determined to store.

The change determination unit 136 determines whether or not there is a change in the other user's information corresponding to the exchange information or business card information. Changes include, for example, transfers, promotions, job changes, and employment within an organization.

The change determination unit 136, for example, determines the user information 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, and determines the organization identifier and department included in the other user information. determining whether or not one or more predetermined user attribute values such as an identifier, title, address, etc., are different from corresponding user attribute values of the user information; determine that there was

The change determination unit 136 is, for example, other user information acquired by the other user information acquisition unit 134, and other user information including a name and one or more other user attribute values (for example, company name, title, department name). to search the user information storage unit 111, determine whether or not there is user information that matches the name and has one or more different user attribute values, and if the user information exists, the user It is determined that the user corresponding to the information has changed.

The AC processing unit 137 performs predetermined processing when the change determination unit 136 determines that there is a change.

When the change determination unit 136 determines that there is a change, the interaction processing unit 137 does not perform a predetermined process using the interaction relationship information accumulated by the interaction relationship storage unit 135 in association with the user identifier. preferred.

The predetermined processing includes notification of change information and posting of change information on the web page. Change information is information indicating that a user has been transferred, that there has been a change in the user, or the like. Moreover, 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 there has been a change. Notification of change information is a process of notifying other users of change information.

The interaction processing unit 137 acquires the user identifier of the user for whom the change determination unit 136 determines that there has been a change in the notification of the change information, and from one or more pieces of interaction information corresponding to the user identifier, the user identifier. Transfer information is transmitted to other users identified by corresponding other user identifiers. It should be noted that the change information transmission means may be e-mail, FAX, short message, or the like. The transmission of the change information may be processing for displaying the change information on the screen output by the other user when the other user identified by the other user identifier logs in to the exchange management device 1 .

The exchange processing unit 137 posts change information indicating that the user who has changed has changed, that the user has changed, etc., when posting on the web page.

The transmission unit 14 transmits various types of information. Various types of information are, for example, information to the effect that exchange relationship information has been accumulated. The transmission unit 14 transmits various kinds of information to the terminal device 3, for example.

For example, the transmission unit 14 transmits various information corresponding to various information transmission instructions. The transmitting unit 14, for example, transmits one or more items of exchange relationship information corresponding to the instruction to transmit the exchange relationship information.

Various types of information are stored in the server storage unit 21 that constitutes the information server 2 .

When the information server 2 is a mail server, the server storage unit 21 stores one or more mails. A mail is associated with, for example, a recipient's mail address for receiving the mail. Each email is associated with, for example, the email address of the sender of the email. A mail is associated with, for example, a user identifier.

When the information server 2 is a calendar server, the server storage unit 21 stores one or more pieces of calendar schedule information. A user identifier is associated with the calendar schedule information. The user identifier of one user's calendar server and the user identifier used by one user's exchange management device 1 may be different. However, if the two user identifiers are different, it is assumed that the storage unit 11 manages the correspondence between the two user identifiers.

When the information server 2 is a web conference server, the server storage unit 21 stores one or more web conference schedule information. A user identifier is associated with the web conference schedule information. Note that the user identifier of the web conference server of one user and the user identifier used by the exchange management device 1 of one user may be different. However, if the two user identifiers are different, it is assumed that the storage unit 11 manages the correspondence between the two user identifiers.

The server reception unit 22 receives various instructions and information. The server reception unit 22 receives various instructions and information from the exchange management device 1 or the terminal device 3, for example. Various instructions and information are, for example, exchange information transmission instructions and exchange information (e.g., e-mail, schedule information). The exchange information transmission instruction is an instruction to transmit exchange information.

The server processing unit 23 performs various types of processing. Various types of processing are, for example, processing of accumulating received exchange information in the server storage unit 21 . The various types of processing are, for example, processing for acquiring exchange information corresponding to an exchange information transmission instruction from the server storage unit 21 .

The server transmission unit 24 transmits various types of information. Various types of information are exchange information.

Various types of information are stored in the terminal storage unit 31 that constitutes the terminal device 3 . Various types of information are, for example, user identifiers, business card information, exchange information, and exchange-related information.

The terminal reception unit 32 receives various instructions and information. Various instructions and information are, for example, a start instruction and business card information.

Here, reception means reception of information input from input devices such as keyboards, mice, and touch panels, reception of information transmitted via wired or wireless communication lines, and recording on optical discs, magnetic discs, semiconductor memories, etc. This is a concept that includes acceptance of information read from a medium. Any means such as a touch panel, a keyboard, a mouse, or a menu screen may be used as means for inputting various instructions and information.

The terminal processing unit 33 performs various types of processing. The various types of processing are, for example, processing for converting instructions and information received by the terminal reception unit 32 into instructions and information for a data structure to be transmitted. The various types of processing are, for example, processing for converting information received by the terminal reception unit 35 into information of a data structure to be output.

The terminal transmission unit 34 transmits various instructions and information. Various instructions and information are, for example, a start instruction and business card information.

The terminal reception unit 35 receives various types of information. Various types of information are, for example, various types of screen information, interaction information, business card information, and transfer information.

The terminal output unit 36 outputs various information. Various types of information are, for example, various types of screen information, interaction information, business card information, and transfer information.

Here, output means 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 transmission to another processing device or other program. This is a concept that includes delivery of processing results.

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 it is feasible.

The process by which information is stored in the storage unit 11 or the like does not matter. For example, information may be stored in the storage unit 11 or the like via a recording medium, or information transmitted via a communication line or the like may be stored in the storage unit 11 or the like. Alternatively, information input via an input device may be stored in the storage unit 11 or the like.

The receiving unit 12, the business card information receiving unit 121, the server receiving unit 22, and the terminal receiving unit 35 are usually implemented by wireless or wired communication means, but may be implemented by means of receiving broadcast.

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

The transmission unit 14, the inquiry unit 133, the server transmission unit 24, and the terminal transmission unit 34 are usually realized by wireless or wired communication means, but may be realized by broadcasting means.

The terminal reception unit 32 can be realized by device drivers for input means such as touch panels and keyboards, control software for menu screens, and the like.

The terminal output unit 36 may or may not include output devices such as displays and speakers. The terminal output unit 36 can be realized by output device driver software, or by output device driver software and an output device.

Next, an operation example of exchange management system A will be described. First, an operation example of the exchange management device 1 will be described with reference to the flowchart of FIG.

(Step S401) The processing unit 13 determines whether it is time to acquire exchange information. If it is the time to acquire AC information, the process goes to step S402, and if it is not the time to acquire AC information, the process goes to step S409.

(Step S402) The processing unit 13 substitutes 1 for the counter i.

(Step S403) The processing unit 13 determines whether or not there is the i-th type of exchange information for which exchange information is to be acquired. If the i-th type of alternating current information exists, the process goes to step S404, and if the i-th type of alternating current information does not exist, the process returns to step S401. It is assumed that which type of exchange information exists or not is predetermined and the processing unit 13 can determine. Also, for example, there are one or more types of exchange information out of three types of exchange information: mail, calendar server schedule information, and web conference server schedule information.

(Step S404) The processing unit 13 substitutes 1 for the counter j.

(Step S405) The processing unit 13 determines whether or not there is a user identifier of the j-th user for whom interaction information processing is to be performed. If the user identifier of the j-th user exists, go to step S406, otherwise go to step S408. Note that the interaction relationship information processing is a process of acquiring and accumulating interaction relationship information for one user. Also, the processing unit 13 determines whether or not the user identifier of the j-th user exists in the user information storage unit 111, for example.

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

(Step S407) The processing unit 13 increments the counter j by 1. Return to step S405.

(Step S408) The processing unit 13 increments the counter i by 1. Return to step S403.

(Step S409) The business card information reception unit 121 determines whether business card information has been received. If the business card information has been received, the process goes to step S410, and if the business card information has not been received, the process goes to step S411.

(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.

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

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

In addition, in the flowchart of FIG. 4, the process of acquiring the interaction relationship information of each user was performed for each information server 2 in order. However, a process of acquiring interaction relationship information from one or more information servers 2 may be performed for each user. That is, in the flowchart of FIG. 4, the order of processing does not matter.

Further, in the flowchart of FIG. 4, the interaction relationship information or interaction information that can be the basis of the interaction relationship information is acquired in advance for each user and recorded in the storage unit 11 or a device (not shown). In addition, an inquiry may be made as to whether or not to store the exchange relationship information, and if the answer to the inquiry is that the exchange relationship information should be stored, the exchange relationship information may be stored. The predetermined timing is, for example, the timing at which the user logs into the exchange management device 1, the timing at which the instruction from the user is received, or the like, but the timing is not limited.

Furthermore, in the flowchart of FIG. 4, the process ends when the power is turned off or when the process ends.

Next, an example of the interaction relation information processing in steps S406 and S412 will be described using the flowchart of FIG.

(Step S501) The interaction information determining 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 in step S403 exists, or the interaction information received in step S411. Get exchange information.

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

(Step S502) The exchange information determination unit 132 substitutes 1 for the counter i.

(Step S503) The exchange information determination unit 132 determines whether or not the i-th exchange information exists among the one or more pieces of exchange information acquired in step S501. If the i-th exchange information exists, go to step S504, and if the i-th exchange information does not exist, return to the higher-level processing.

(Step S504) The exchange information determination unit 132 determines whether or not the i-th exchange information satisfies a predetermined condition. If the predetermined condition is satisfied, the process goes to step S505, and if the predetermined condition is not satisfied, the process goes to step S514.

(Step S505) The other user information acquisition unit 134 acquires other user information using the i-th exchange information.

(Step S506) The inquiry unit 133 determines whether or not to inquire of the user. When inquiring, go to step S506, and when not inquiring, go to step S510. For example, whether or not to inquire is determined in advance. In addition, the question unit 133 determines whether or not to inquire according to the other user information. For example, the inquiry unit 133 determines whether or not the exchange relationship information corresponding to the other user information acquired in step S505 has already been accumulated, and if not already accumulated, determines to inquire.

(Step S507) The questioning unit 133 asks the user whether or not to store the interaction relationship information corresponding to the other user information acquired in step S505.

(Step S508) The inquiry unit 133 determines whether or not a reply to the inquiry result in step S507 has been received from the terminal device 3. If an answer has been received, the process goes to step S509; otherwise, the process returns to step S508.

(Step S509) If the response received in step S508 is an answer to the effect that "interacting relationship information is to be accumulated," the interaction relationship storage unit 135 proceeds to step S510, where it responds to the effect that "interacting relationship information is not to be accumulated." If so, go to step S512.

(Step S510) The interaction relationship storage unit 135 acquires interaction relationship information using the other user information acquired in step S505 and the user identifier corresponding to the interaction information.

(Step S511) The interaction relationship accumulation unit 135 accumulates the interaction relationship information acquired in step S510.

(Step S512) The change determination unit 136 compares the other user information acquired in step S505 with the corresponding user information to determine whether it has been changed (whether there is a change, etc.). If changed, go to step S513; if not changed, go to step S514.

(Step S513) The AC processing unit 137 performs AC processing. An example of AC processing will be described with reference to the flowchart of FIG.

(Step S514) The exchange information determination unit 132 increments the counter i by 1. Return to step S503.

Next, an example of the AC process in step S513 will be described using the flowchart of FIG.

(Step S601) The AC processing unit 137 substitutes 1 for the counter i.

(Step S602) The exchange processing unit 137 determines whether or not there is another i-th user identifier. If the i-th user identifier exists, go to step S603, and if the i-th user identifier does not exist, return to the upper process. The exchange processing unit 137 determines whether or not another i-th user identifier exists in the user information storage unit 111, for example. The interaction processing unit 137 also determines whether or not another i-th user identifier exists in the interaction relationship storage unit 114, for example.

(Step S603) The interaction processing unit 137 determines whether or not the i-th user identifier exists in the interaction relationship information of the interaction relationship storage unit 114 corresponding to the user identifier of the corresponding user (other i-th user (whether or not there is interaction with the user identified by the identifier). If there is an alternating current, go to step S604; if there is no alternating current, go to step S605.

(Step S604) The exchange processing unit 137 transmits the acquired other user information to another user identified by the i-th user identifier.

(Step S605) The AC processing unit 137 increments the counter i by 1. Return to step S602.

In the flowchart of FIG. 6, for example, at step S602, the interaction processing unit 137 acquires a user identifier corresponding to the other user information determined to have been changed at step S512, and It may be determined whether or not i-th other user information paired with the user identifier exists in the interaction relationship storage unit 114 . Then, when the i-th other user information exists in the interaction relationship storage unit 114, the process may proceed to step S604. In such a case, step S603 is unnecessary.

　In other words, in the flowchart of Fig. 6, it is sufficient to notify other users with whom the user who has changed has contact with the change information.

Next, an example of business card information processing in step S410 will be described using the flowchart of FIG.

(Step S701) The other user information acquisition unit 134 acquires the received business card information. Next, the other user information acquisition unit 134 acquires other user information including another user identifier using the business card information.

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

(Step S703) The interaction relationship accumulation unit 135 accumulates the interaction relationship information acquired in step S702.

(Step S704) The change determination unit 136 compares the other user information acquired in step S701 with the corresponding user information to determine whether it has been changed (changed, etc.). If changed, go to step S705; if not changed, return to the higher-level processing.

(Step S705) The AC processing unit 137 performs AC processing. Return to upper process. An example of AC processing has been described with reference to the flowchart of FIG.

In the flowchart of FIG. 7, the processing unit 13 may use the received business card information to form business card information to be stored, and may perform processing such as storing the business card information in the business card information storage unit 112. .

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

Next, an operation example of the terminal device 3 will be described. A 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 receiving unit 32 into instructions and information for the 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 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, and the like. The terminal processing unit 33 converts the information received by the terminal receiving unit 35 into information having a data structure to be output. The terminal output unit 36 outputs various screen information, interaction information, business card information, transfer information, and the like.

A specific operation of the exchange management system A according to this embodiment will be described below.
A conceptual diagram of the exchange management system A is shown in FIG.

Assume that the user information storage unit 111 of the exchange management device 1 stores a user information management table having the structure shown in FIG. 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 the business card information management table. That is, in the user information management table, information having a business card image (for example, 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 an item. Information. Information that does not have a business card image (for example, information of "ID=384") may also be considered to be business card information.
A business card information management table may be stored in the business card information storage unit 112 separately from the user information management table.

The user information management table manages one or more records having "ID", "user identifier", "password", "user information", and "business card image". "User information" includes "name", "notification destination information (mail address)", "company name", and the like. "ID" is information for identifying a record. Although not shown in FIG. 8, "user information" includes user attributes such as a department identifier, title, telephone number, FAX number, and URL. Having a value is preferred.

In addition, the domain information management table shown in FIG. 9 is stored in the domain information storage unit 113. The domain information management table manages one or more records having "ID", "domain information" and "organization identifier".

In addition, the interaction relationship storage unit 114 stores an interaction relationship management table having the structure shown in FIG. The interaction relationship management table is a table that stores one or more interaction 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 by some means of interaction. "Type identifier" is information indicating the type of interaction. Here, the "type identifier" is "mail (eg, "1")", "calendar (eg, "2")", "web conference (eg, "3")", "business card (eg, "4")". is either "Additional information" is additional information in the exchange relationship information, such as mail-related information, business card exchange-related information, calendar-related information, and web conference-related information. The business card exchange related information here has a registration date indicating the date when the business card information was registered, but may have other information such as a memo entered by the user. The calendar-related information here includes start date and time, end date and time, place, title, and the like. The web conference-related information here includes start date and time, end date and time, topic, and the like.

In addition, the storage unit 11 stores a business term dictionary shown in FIG. The business term dictionary stores character strings such as terms, phrases, and sentences that are frequently used in business situations, business emails, and schedule information related to business.

The storage unit 11 also stores a non-business term dictionary shown in FIG. The non-business term dictionary stores character strings such as terms, phrases, and sentences that are not used or rarely used in business situations, business mails, and schedule information related to business.

In addition, the storage unit 11 stores a condition management table shown in FIG. The condition management table is a table for managing business exchange conditions. The condition management table stores one or more records having "ID", "business exchange condition" and "type identifier".

Here, the business exchange condition for "ID = 1" is to include either "co.jp" or "ac.jp" in the other party's email address. Also, the business exchange condition for "ID=2" is that there are two or more exchanges of e-mails (one or more replies to e-mail transmissions). Also, the business exchange condition for "ID=3" is that the number of business terms in the character string in the email is greater than the number of non-business terms. Also, the business interaction condition for "ID=4" is to include business terms in the schedule information of the calendar. Further, the business interaction condition of "ID=5" is that the schedule information in the calendar is on a day other than Saturdays, Sundays, and holidays (usually a working day), and the time zone indicated by the schedule information is between 9:00 and 18:00. There is something.

Further, when the type identifier is "email", here, the interaction information determination unit 132 acquires the interaction relationship information for an email that satisfies "ID=1" AND "ID=2" AND "ID=3". It shall be determined as the original exchange information.

If the type identifier is "calendar", here, the exchange information determination unit 132 selects the calendar schedule information that satisfies "ID=4" or "ID=5" as the exchange from which the exchange relationship information is acquired. shall be determined as information.

Furthermore, if the type identifier is "web conference", here, the exchange information determination unit 132 determines the calendar schedule information that satisfies "ID=6" as the exchange information from which the exchange relationship information is to be obtained. shall be

Exchange management system A includes, as information servers 2, a mail server 2 (1) that manages emails of one or more users, calendar servers 2 (2) that manage calendar schedule information of one or more users, It is assumed that there is a web conference server 2 (3) that manages the above web conference schedule information of each user.

A calendar schedule information management table shown in FIG. 14 is stored in the server storage unit 21 of the calendar server 2 (2). The calendar schedule information management table manages one or more records having "ID", "user identifier", "start date and time", "end date and time", "title", and the like.

In addition, the web conference schedule information management table shown in FIG. 15 is stored in the server storage unit 21 of the web conference server 2 (3). The web conference schedule information management table manages one or more records having "ID", "user identifier", "start date and time", "end date and time", "topics", and the like.

In this situation, the following three specific examples will be explained. Specific example 1 is a process of determining exchange information using mail, calendar schedule information, and web conference schedule information, and accumulating other user information corresponding to the exchange information. It should be noted that the accumulated other user information is information that can serve as a basis for interaction relationship information. Specific example 2 is a process of inquiring of a user whether or not to store exchange relationship information using accumulated other user information, and accumulating exchange relationship information in response to the other user information that is a reply that the exchange relationship information is to be accumulated. It is a specific example for explaining. Specific example 3 is an example of accumulating exchange relationship information when business card information of a partner with whom business cards have been exchanged is received.

(Specific 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 acquire exchange information.

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

Next, the interaction information determining 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 means (API, IP address, etc.) for accessing the mail server 2(1). An unprocessed mail is a mail that the exchange information determination unit 132 has not yet read from the mail server 2(1). Here, it is assumed that exchange information determination unit 132 has obtained

mails

1601, 1602, etc. shown in FIG.

Next, the exchange information determining unit 132 determines whether or not the mails (1601, 1602, etc.) in FIG. 16 satisfy all business exchange conditions of "ID=1, 2, 3" in FIG. Here, it is assumed that the exchange information determining unit 132 determines that the business exchange condition of "ID=1" is satisfied because the email address of the sender of the email 1601 in FIG. 16 is "ay@s.jp". . In addition, the exchange information determination unit 132 detects from the read mail (not shown) that Ichiro Yamada, identified by the user identifier "1001", has responded to this mail, and has "ID=2". Suppose that it is determined that the conditions for business exchange are satisfied. Furthermore, exchange information determination unit 132 performs morphological analysis on a character string paired with <title> and a character string paired with <text> of email 1601, acquires one or more terms, and obtains one or more terms, and the business terms in FIG. Get the number of business terms in the mail 1601 by looking up the dictionary. Also, the interaction information determination unit 132 refers to the non-business term dictionary of FIG. 12 and acquires the number of non-business terms in the email 1601 . Then, it is assumed that the exchange information determination unit 132 determines that the business exchange condition of "ID=3" is satisfied. From the above, the exchange information determination unit 132 determines the mail 1601 in FIG. 16 as exchange information that satisfies the predetermined conditions.

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 mail 1601, "S Co., Ltd. Business Department Chief Ako Yamamoto 〒105-0000 Tokyo...". Further, the other user information acquisition unit 134 searches the user information management table of FIG. 8 using the acquired character string of the signature portion. Next, the other user information acquisition unit 134 retrieves the other user information "<user identifier> 1384 <name> Ako Yamamoto <e-mail address> ay@s.jp <company name> S stock" from the user information management table of FIG. Company..." is acquired. Here, the other user information acquisition unit 134 acquires the character string of the signature portion from the mail, and acquires the 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 from the mail using the character string of the signature portion.

Next, the other user information acquisition unit 134 stores the other user information in the storage unit 11 in a pair with the user identifier "1001" and the type identifier "email". It should be noted that such other user information is information that may serve as a basis for interaction relationship information.

Next, the exchange information determination unit 132 determines whether the mail 1602 in FIG. 16 satisfies all business exchange conditions of "ID=1, 2, 3" in FIG. Here, the exchange information determining unit 132 determines that the business exchange condition of "ID=1" is not satisfied because the mail address of the sender of the mail 1601 in FIG. 16 is "star@google.com". do. That is, the exchange information determining unit 132 determines that the mail 1602 in FIG. 16 does not satisfy the business exchange conditions, and does not select it as exchange information that satisfies the predetermined conditions.

It is assumed that the exchange information determination unit 132 has performed the above processing on all read emails. Assume that, as a result, the exchange information determination unit 132 selects only the mail 1601 as exchange information that satisfies a predetermined condition. Then, it is assumed that the other user information acquisition unit 134 stores only one other user information corresponding to the mail 1601 in a pair with the user identifier "1001".

Next, exchange information determining unit 132 refers to calendar server 2(2) and determines one or more schedule information (information having start date and time, end date and time, title, etc.) paired with user identifier "1001" as shown in FIG. is read from the calendar schedule information management table. Note that one or more pieces of schedule information paired with the user identifier "1001" include schedule information with "ID=1" in FIG.

Then, the exchange information determination unit 132 determines whether or not each piece of schedule information satisfies the business exchange condition of "ID=4" or "ID=5" in FIG. Here, the exchange information determination unit 132 acquires the term "meeting" from the title of the calendar schedule information "○○ meeting @Y company Mr. Jiro Aoki", and the term "meeting" of "ID=1" in FIG. It detects that it exists in 11 business term dictionaries, and determines that it satisfies the business exchange condition of "ID=4". In addition, the exchange information determination unit 132 uses the start date and time “2021/1/19 16:00” and the end date and time “2021/1/19 17:00” included in the calendar schedule information with “ID=1” to determine the It is judged that the business exchange condition of 13 "ID = 5" is satisfied. Then, the exchange information determining unit 132 determines the calendar schedule information of "ID=1" in FIG. 14 as the exchange information that satisfies the predetermined condition.

Next, the other user information acquisition unit 134 acquires other user information using the exchange information. Specifically, the other user information acquisition unit 134 searches the user information management table of FIG. It is determined that the record matches the record with ID=3. Then, the other user information acquisition unit 134 acquires other user information "<user identifier> 1003 <name> Jiro Aoki <email address> aoki@y.com <company name> Y company...".

Next, the other user information acquisition unit 134 stores the other user information in the storage unit 11 in a pair with the user identifier "1001" and the type identifier "calendar". It should be noted that such other user information is information that may serve as a basis for interaction relationship information.

It is assumed that the exchange information determination unit 132 has performed the above processing on all read calendar schedule information. As a result, the exchange information determination unit 132 determined that the second and subsequent calendar schedule information acquired from the calendar server 2(2) did not satisfy the business exchange conditions of "ID=4" and "ID=5" in FIG. It is assumed that Then, it is assumed that the exchange information determination unit 132 selects only the calendar schedule information of "ID=1" in FIG. 14 as the exchange information that satisfies the predetermined condition. Then, assume that the other user information acquiring unit 134 stores only one other user information corresponding to the calendar schedule information of "ID=1" in FIG. 14 in pair with the user identifier "1001".

Next, the exchange information determination unit 132 refers to the web conference server 2(3), and sets one or more web conference schedule information (information including start date and time, end date and time, topics, etc.) paired with the user identifier "1001". is read from the web conference schedule information management table of FIG. Note that one or more web conference schedule information paired with the user identifier "1001" includes the web conference schedule information with "ID=1" in FIG.

Then, the exchange information determination unit 132 determines whether or not each of the one or more web conference schedule information satisfies the business exchange condition of "ID=6" in FIG. Here, the exchange information determining unit 132 determines 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 determining unit 132 determines the web conference schedule information with "ID=1" in FIG. 15 as exchange information that satisfies a predetermined condition.

Next, the other user information acquisition unit 134 acquires other user information using the exchange information. Specifically, the other user information acquisition unit 134 extracts “Co., Ltd. X” and “Suzuki B child” from the character string of topics, searches the user information management table of FIG. It is determined that the record (not shown) matches. Then, the other user information acquisition unit 134 acquires the other user information "<user identifier> 1058 <name> Boko Suzuki <email address> sb@x.com <company name> Co., Ltd. X..." and

Next, the other user information acquisition unit 134 stores the other user information in the storage unit 11 in a pair with the user identifier "1001" and the type identifier "web conference". It should be noted that such other user information is information that may serve as a basis for interaction relationship information.

It is assumed that the exchange information determination unit 132 has performed the above processing on all acquired web conference schedule information. As a result, the exchange information determination unit 132 determined that the second and subsequent web conference schedule information acquired from the web conference server 2(3) did not meet the business exchange conditions of "ID=6" in FIG. and Then, it is assumed that the exchange information determination unit 132 selects only the web conference schedule information with "ID=1" in FIG. 15 as the exchange information that satisfies the predetermined condition. Then, assume that the other user information acquiring unit 134 stores only one other user information corresponding to the web conference schedule information of "ID=1" in FIG. 15 in pair with the user identifier "1001".

Assume that the above processing has also been performed for the user identifiers of other users.

(Specific example 2)
Next, it is assumed that the user “Ichiro Yamada” identified by the user identifier “1001” has logged into the exchange management device 1 using his own terminal device 3 . After the login process, the processing unit 13 of the interaction management device 1 acquires one or more other user identifiers paired with the user identifier "1001" from the interaction relationship management table having the structure shown in FIG. The exchange management device 1 acquires user information paired with one or more other user identifiers from the user information management table. Also, the exchange management device 1 uses the other user information accumulated in the storage unit 11 in the process of the specific example 1 to acquire the number of pieces of other user information "3" paired with the user identifier "1001". Then, it is assumed that the exchange management device 1 configures screen information including the acquired user information and the number of other user information “3” and transmits the screen information to the terminal device 3 .

Next, assume that Ichiro Yamada's terminal device 3 receives the screen information and outputs the screen shown in FIG. In FIG. 17, 1701 is the user information of other users who have exchanges with Ichiro Yamada. Further, 1702 is information for notifying the existence of other user information stored in a pair 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 basis of interaction information.

And Ichiro Yamada instructed the area of 1702. Then, the terminal device 3 accepts such an instruction and transmits an instruction to output a business card creation screen having the user identifier “1001” to the exchange management device 1 . It can be said that the business card creation screen is a screen for creating contact information.

Next, the reception unit 12 of the exchange management device 1 receives an instruction to output the business card creation screen having the user identifier "1001".

Next, the inquiry unit 133 acquires from the storage unit 11 three pieces of other user information paired with the user identifier "1001". Next, the inquiry unit 133 uses the three pieces of other user information to compose inquiry screen information for inquiring whether or not to perform business card creation processing. Next, the inquiry unit 133 transmits the inquiry screen information to the terminal device 3 of Ichiro Yamada. Note that the process of creating a business card here is the process of creating contact information.

Next, Ichiro Yamada's terminal device 3 receives the inquiry screen information and outputs the inquiry screen. An example of such an output is shown in FIG. In FIG. 18, three pieces of other user information are displayed, and a "name card creation" button 2 is displayed for each piece of other user information. Instructing the "create name card" button (1801, 1802, 1803) means that the user is instructed to create interaction information using other user information corresponding to the button.

Then, on the screen of FIG. 18, assume that Ichiro Yamada has instructed all of the "create business card"

buttons

1801, 1802, and 1803.

Next, Ichiro Yamada's terminal device 3 accepts such an instruction, and transmits to the exchange management device 1 a reply to the effect that "to accumulate exchange relationship information" for each of the three pieces of other user information.

Next, the inquiry unit 133 of the interaction management device 1 receives a response to the effect that "accumulate interaction relationship information" for each of the three pieces of other user information.

Next, the interaction storage unit 135 uses the other user information corresponding to the “create business card” button 1801 to generate the interaction relationship information “<date and time received> 2021/1/15 18:00:07 <title> XX business negotiation <text>...", other user identifier "1384", and type identifier "email" are acquired, and this set of information is associated with the user identifier "1001" and stored in the exchange relationship management table of FIG. accumulate. Such information is record 1001 in FIG.

In addition, the interaction storage unit 135 uses the other user information corresponding to the “create business card” button 1802 to generate the interaction relationship information “<start date and time> 2021/1/19 16:00 <end date and time> 2021/1/19”. 17:00 Acquire <location> Company Y <other> XX meeting", other user identifier "1003", and type identifier "calendar", associate this set of information with user identifier "1001", and Accumulate in 10 exchange relationship management tables. Such information is record 1002 in FIG.

In addition, the interaction storage unit 135 uses the other user information corresponding to the “create name card” button 1803 to generate the interaction relationship information “<start date and time> 2021/1/25 13:00 <end date and time> 2021/1/25”. 14:00 About the <Tobik> Alliance...", the other user identifier "1058", and the type identifier "web conference" are acquired, and the set of information is associated with the user identifier "1001", and the Accumulate in the exchange relationship management table. Such information is record 1003 in FIG.

Through the above processing, we were able to accumulate exchange relationship information using email, calendar schedule information, or web conference schedule information.

(Specific example 3)
Ichiro Yamada entered business card information including a business card image of "Hanako Tanaka" with whom he had exchanged business cards and a registration instruction into the terminal device 3 on January 18, 2021. Then, the terminal device 3 accepts the business card information and the registration instruction, and transmits the registration instruction including the business card information and the user identifier “1001” to the exchange management device 1 .

Next, the business card information reception unit 121 of the exchange management device 1 receives the registration instruction including the business card information and the user identifier "1001".

Next, the other user information acquisition unit 134 acquires the received business card information. Next, the other user information acquisition unit 134 searches the user information management table of FIG. 8 using the business card information, and acquires another user identifier "1002". Note that the other user information acquisition unit 134 acquires today's date “2021/1/18” (registration date) from a clock (not shown).

Next, the interaction relationship storage unit 135 stores interaction relationship information including another user identifier “1002”, a type identifier “business card”, and a registration date “2021/1/18” in the interaction relationship management table of FIG. do. Such information is record 1004 in FIG.

As described above, we were able to accumulate exchange-related information by registering business card exchanges.

As described above, according to the present embodiment, it is possible to acquire and manage exchange relationship information regarding connections between users using exchange information such as emails, calendar schedule information, and web conference schedule information.

In addition, according to the present embodiment, by accumulating the interaction relationship information after confirming the user's intention to accumulate, only the interaction relationship information necessary for the user can be accumulated.

Also, according to the present embodiment, it is possible to acquire and manage accurate other user information using the user information in the user information storage unit 111 .

In addition, according to the present embodiment, it is possible to manage the interaction information acquired based on the exchange of business cards together.

Furthermore, according to the present embodiment, appropriate actions can be taken when it is determined that there is a change in other user information acquired using exchange information such as e-mail.

It should be noted that the processing in the present embodiment may be realized by software. Then, this software may be distributed by software download or the like. Also, this software may be recorded on a recording medium such as a CD-ROM and distributed. Note that this also applies to other embodiments in this specification. The software that implements the exchange management device 1 in this embodiment is the following program. In other words, this program comprises a computer, a user identifier acquisition unit that acquires a user identifier, and information related to interaction between two or more users, and information corresponding to the user identifier acquired by the user identifier acquisition unit. an exchange information determination unit that determines exchange information that satisfies a predetermined condition from one or more pieces of exchange information; and another user identifier different from the user identifier acquired by the user identifier acquisition unit, Other user information acquisition unit for acquiring other user information including a user identifier corresponding to the interaction information determined by the interaction information determination unit; and interaction relationship storage for storing interaction relationship information that associates the other user information with the user identifier. It is a program for functioning as a department.

Also, FIG. 19 shows the appearance of a computer that executes the program described in this specification and implements the exchange management device 1 of the various embodiments described above. The embodiments described above may be implemented in computer hardware and computer programs running thereon. FIG. 19 is an overview diagram of this computer system 300, and FIG. 20 is a block diagram of the system 300. As shown in FIG.

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

20, a computer 301 includes a CD-ROM drive 3012, an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, a ROM 3015 for storing programs such as a boot-up program, It includes a RAM 3016 connected and for temporarily storing application program instructions and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs and data. Although not shown here, computer 301 may also include a network card that provides connection to a LAN.

A program that causes the computer system 300 to execute the functions of the exchange management device 1 of the embodiment described above may be stored in the CD-ROM 3101, inserted into the CD-ROM drive 3012, and transferred to the hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored in hard disk 3017 . Programs are loaded into RAM 3016 during execution. The program may be loaded directly from CD-ROM 3101 or network.

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 exchange management device 1 of the embodiment described above. A program need only contain those parts of instructions that call the appropriate functions (modules) in a controlled manner to produce the desired result. How the computer system 300 operates is well known and will not be described in detail.

In the above program, the step of transmitting information, the step of receiving information, etc. are performed by hardware. processing) are not included.

Also, the computer that executes the above program may be singular or plural. That is, centralized processing may be performed, or distributed processing may be performed.

Also, in each of the above embodiments, it goes without saying that two or more communication means existing in one device may be physically realized in one medium.

Also, in each of the above embodiments, each process may be implemented by centralized processing by a single device, or may be implemented by distributed processing by a plurality of devices.

It goes without saying that the present invention is not limited to the above embodiments, and that various modifications are possible and are also included within the scope of the present invention.

INDUSTRIAL APPLICABILITY As described above, the interaction management apparatus according to the present invention has the effect of being able to acquire and manage interaction relationship information relating to connections between users using interaction information relating to interactions other than exchanging business cards. It is useful as a server or the like to be managed.

Claims

a user identifier acquisition unit that acquires a user identifier;
Exchange information that is information related to interaction between two or more users, is information corresponding to the user identifier acquired by the user identifier acquiring unit, and satisfies a predetermined condition, among the one or more interaction information. an exchange information determination unit that determines from
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 that includes a user identifier corresponding to the interaction information determined by the interaction information determination unit; ,
An interaction management device comprising: an interaction relationship accumulation unit that accumulates interaction relationship information that associates the other user information with the user identifier.
The predetermined condition is a business interaction condition for determining that it is an interaction in business,
The exchange information determination unit,
2. The exchange management device according to claim 1, wherein exchange information that is exchange information corresponding to said user identifier acquired by said user identifier acquisition unit and that satisfies said business exchange condition is determined.
further comprising an inquiry unit for inquiring of the user whether or not to accumulate the exchange relationship information;
The exchange relationship storage unit
2. The interaction management device according to claim 1, wherein said interaction relationship information is accumulated only when the result of the inquiry by said question unit is a result of accumulating said interaction relationship information.
The other user information acquisition unit
A user 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 included in the exchange information determined by the exchange information determining unit or a user identifier corresponding to the exchange information 2. The exchange management device according to claim 1, wherein the information storage unit is searched, and other user information is acquired using the search result.
the exchange information is an email;
The exchange information determination unit,
determining an email that satisfies a predetermined condition from emails sent to the email address corresponding to the user identifier acquired by the user identifier acquiring unit;
The other user information acquisition unit
2. The exchange management device according to claim 1, wherein other user information is acquired using the mail determined by said exchange information determination unit.
The other user information acquisition unit
6. The exchange management device according to claim 5, wherein the other user's information is obtained by using the signature information in the mail determined by the exchange information determination unit.
The other user information acquisition unit
Acquiring the domain name of the email address of the sender of the email determined by the exchange information determination unit, storing an organization identifier corresponding to the domain name, and storing one or more pieces of domain information having a pair of the domain name and the organization identifier 6. The exchange management device according to claim 5, wherein the information is obtained from the domain information storage unit, and the other user information is obtained using the organization identifier.
The predetermined condition is a condition regarding an e-mail address,
The exchange information determination unit,
6. The exchange management device according to claim 5, wherein the emails satisfying the predetermined condition are determined using the email addresses of the senders of the one or more stored emails.
6. The communication management device according to claim 5, wherein said other user information includes mail-related information regarding mail.
The exchange information is schedule information specifying a schedule of the user,
The exchange information determination unit,
Determine 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;
The other user information acquisition unit
2. The exchange management device according to claim 1, wherein other user information is acquired using the schedule information determined by said exchange information determination unit.
a business card information reception unit that receives business card information related to business cards of other users in association with user identifiers;
The other user information acquisition unit
acquiring other user information including another user identifier corresponding to the business card information;
The exchange relationship storage unit
2. The interaction management device according to claim 1, wherein interaction relationship information that associates said other user information with said user identifier is stored.
a change determination unit that determines whether or not there is a change in other user information corresponding to the exchange information;
2. The exchange management apparatus according to claim 1, further comprising an exchange processing section that performs predetermined processing when said change judgment section judges that there is a change.
An interaction management method implemented by a user identifier acquisition unit, an interaction information determination unit, an other user information acquisition unit, and an interaction relationship storage unit,
a user identifier obtaining step in which the user identifier obtaining unit obtains a user identifier;
The interaction information determination unit selects interaction information that is information about interaction between two or more users, is information corresponding to the user identifier acquired in the user identifier acquisition step, and satisfies a predetermined condition. , an exchange information decision step of deciding from one or more exchange information;
The other user information acquisition unit is another user identifier different from the user identifier acquired in the user identifier acquisition step, and includes a user identifier corresponding to the interaction information determined in the interaction information determination step. an other user information acquisition step of acquiring information;
and an interaction management method, wherein the interaction relationship storage unit stores interaction relationship information that associates the other user information with the user identifier.
the computer,
a user identifier acquisition unit that acquires a user identifier;
Exchange information that is information related to interaction between two or more users, is information corresponding to the user identifier acquired by the user identifier acquiring unit, and satisfies a predetermined condition, among the one or more interaction information. an exchange information determination unit that determines from
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 that includes a user identifier corresponding to the interaction information determined by the interaction information determination unit; ,
A recording medium recording a program for functioning as an interaction relationship storage unit that stores interaction relationship information that associates the other user information with the user identifier.