WO2022186085A1 - Interaction management device, interaction management method, and program - Google Patents

Interaction management device, interaction management method, and program Download PDF

Info

Publication number
WO2022186085A1
WO2022186085A1 PCT/JP2022/008005 JP2022008005W WO2022186085A1 WO 2022186085 A1 WO2022186085 A1 WO 2022186085A1 JP 2022008005 W JP2022008005 W JP 2022008005W WO 2022186085 A1 WO2022186085 A1 WO 2022186085A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
user
exchange
unit
identifier
Prior art date
Application number
PCT/JP2022/008005
Other languages
French (fr)
Japanese (ja)
Inventor
親弘 寺田
洋 千住
彩子 荒川
真人 荻野
健太 杉原
真優 山本
Original Assignee
Sansan株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sansan株式会社 filed Critical Sansan株式会社
Priority to JP2023503788A priority Critical patent/JPWO2022186085A1/ja
Publication of WO2022186085A1 publication Critical patent/WO2022186085A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services

Definitions

  • the present invention relates to an exchange management device or the like that uses exchange information concerning exchanges between two or more parties to manage information concerning exchanges.
  • relationship information which is information about the connection between two parties, using information about interactions other than the exchange of business cards.
  • the exchange management device of the first invention comprises an exchange determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information related to an exchange between two or more parties, and an exchange determination unit.
  • a relationship acquisition unit that acquires relationship information that associates the first identifier and the second identifier, which are the target identifiers of each of the two parties, corresponding to the exchange information acquired by the relationship acquisition unit, and accumulates the relationship information acquired by the relationship acquisition unit and a relationship storage unit.
  • the two or more pieces of exchange information stored in the storage unit include two or more types of exchange information, and the exchange determination unit 2.
  • the exchange determination unit acquires from the storage unit the exchange information that satisfies a predetermined condition. be.
  • the exchange management device of the fourth aspect of the present invention further comprises an interrogation unit for inquiring of the user whether or not to store the relationship information with respect to any one of the third aspects of the invention, wherein the relationship storage unit 2.
  • the relationship acquisition unit includes a character string included in the exchange information determined by the exchange determination unit or a target identifier corresponding to the exchange information is used to search a target information storage unit in which one or more target information having a target identifier and one or more target attribute values are stored, and the search result is used to acquire related information. It is a device.
  • the exchange information includes chat history information in chats conducted between users, history of telephone calls between users, Call history information, billing information, contract information, registration information of registrants who registered for the event, inquiry information entered in the inquiry form on the organization's website, and transmission from the sender to the recipient
  • Gift information business activity information, customer information, order information, employment information, pamphlet acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information about gifts to be given.
  • the exchange management device of the seventh invention is, for any one of the first to sixth inventions, a business card information reception unit that receives business card information related to business cards of other users in association with the first identifier;
  • the relationship acquisition unit is an exchange management device that acquires relationship information in which the first identifier and the second identifier corresponding to the business card information are associated with each other.
  • the exchange management device of the eighth invention in contrast to any one of the first to seventh inventions, there is no change in other user information, which is the information of the user identified by the second identifier corresponding to the exchange information.
  • the exchange management device further includes a change determination unit that determines whether or not there is a change, and an exchange processing unit that performs predetermined processing when the change determination unit determines that there is a change.
  • exchange information is used in an information system whose direct purpose is not communication between two or more parties. It is an exchange management device that is accumulated non-communication system information.
  • the exchange management device of the present invention includes an exchange information determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information related to exchanges between two or more users, and an exchange information determination unit. acquires other user information including one user identifier corresponding to the exchange information acquired by and another user identifier different from the one user identifier and corresponding to the exchange information acquired by the exchange information determination unit
  • the interaction management device includes an other user information acquisition unit and an interaction relationship storage unit that stores interaction relationship information in which one user identifier and other user information are associated with each other.
  • the two or more pieces of exchange information stored in the storage unit include two or more types of exchange information
  • the exchange information determination unit includes: , the exchange management device according to claim 1, which acquires two or more types of exchange information.
  • the exchange management device of the present invention is the exchange management device according to claim 1 or the exchange management device, wherein the exchange information determination unit acquires exchange information that satisfies a predetermined condition from the storage unit, in contrast to the above invention.
  • the exchange management device of the present invention further comprises an inquiry unit for inquiring of the user whether or not to store the exchange relationship information, and the exchange relationship storage unit is configured such that the result of the inquiry by the inquiry unit is: 2.
  • the other user information acquisition unit uses a character string included in the exchange information determined by the exchange information determination unit or a user identifier corresponding to the exchange information to obtain the user 2.
  • the exchange management device according to claim 1, wherein a user information storage unit storing one or more pieces of user information having an identifier and one or more user attribute values is searched, and other user information is acquired using the search result.
  • the exchange information includes chat history information in chats conducted between users, call history information that is information on the history of telephone calls between users, and billing information.
  • contract information registration information of registrants who registered for the event, inquiry information entered in the inquiry form on the organization's website, gift information regarding gifts sent from the giver to the recipient, sales
  • It is an interaction management device that is activity information, customer information, order information, employment information, pamphlet acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information.
  • the business card information reception unit receives business card information related to business cards of other users in association with the user identifier
  • the other user information acquisition unit corresponds to the business card information.
  • the interaction relationship accumulation unit is an exchange management device that acquires other user information including other user identifiers and accumulates the other user information in association with the user identifiers.
  • a change determination unit that determines whether or not there is a change in other user information corresponding to the exchange information, and if the change determination unit determines that there is a change, and an exchange processing unit that performs predetermined processing.
  • the exchange management device of the present invention it is possible to acquire and manage relational information regarding the connection between two parties using exchange information.
  • 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.
  • 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.
  • an exchange management device acquires accurate other user information from the user information storage unit using exchange information and the like, acquires exchange relationship information using the other user information, and accumulates it.
  • An exchange management system that
  • exchange information which is an email sent to the email address corresponding to the user identifier
  • exchange relationship information is acquired using the other user information and accumulated.
  • 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.
  • 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.
  • 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.
  • 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.
  • information X is associated with information Y
  • information Y can be obtained from information X or information X can be obtained from information Y
  • the method of association does not matter.
  • Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, and information Y may be included in information X. etc. is fine.
  • 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.
  • server such as a cloud server or an ASP server.
  • 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 includes, for example, a mail server, a calendar server that stores schedule information for each time slot in a calendar, a web conference server that stores schedule information for web conferences, a chat server that implements a chat function, and telephone call history.
  • the calendar server is, for example, a Google Calendar (registered trademark) server or a CalDAV server.
  • the web conference server is a server that manages information on web conferences such as Zoom (registered trademark) and Teams (registered trademark).
  • the telephone server is, for example, a server that holds telephone information such as MiiTel (registered trademark).
  • the information server 2 receives, for example, one or more emails obtained from a mail server, one or more schedule information obtained from a calendar server, one or more schedule information obtained from a web conference server, chat 1 or 2 or more chat history information obtained from the server, 1 or 2 or more call history information obtained from the telephone server, 1 or 2 or more bill information obtained from the bill management server, contract management server one or more contract information obtained from, one or more registration information obtained from a registration server, receiving inquiries on the website of an organization (e.g., company, sole proprietor, local government), Inquiry information management server that manages, gift management server that receives and manages gift information related to gifts sent from the sender to the recipient, and supports the presentation of gifts, sales support server that manages sales activity information, customer information order management server for managing order information, recruitment management server for managing recruitment information, pamphlet order management server for managing and providing pamphlet information, expense information management server for managing expense information, questionnaire information 1 or 2 of a questionnaire management server that manages answer information, an admission management server that manages admission information related to entering
  • 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 sales support server is, for example, a server for supporting MA (marketing automation) and a server for supporting SFA (sales force automation).
  • the customer management server is, for example, a server for supporting CRM (Customer Relationship Management).
  • 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), one or more types of 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 two or more types of exchange information in the storage unit 11 are information acquired from different information servers 2 respectively. Moreover, when the storage unit 11 is included in the information server 2 , it is preferable that two or more types of exchange information exist in different storage units 11 .
  • 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 is, for example, communication system information and non-communication system information.
  • the exchange information is preferably associated with the type identifier.
  • the type identifier is information that identifies the type of exchange.
  • the type identifier corresponds, for example, to the information server 2 that originally stored the exchange information.
  • Communication system information is information about the communication system.
  • a communication system is an information system whose direct purpose is communication between two or more users. Communication systems are, for example, mail systems, web conference systems, chat systems, and telephones.
  • a web conference system may be called a video conference system or a TV conference system.
  • the communication system information is, for example, e-mail (particularly information on the body of the e-mail), web conference reservation information, which is schedule information registered in the web conference server, chat history information, and telephone call history information.
  • the chat history information includes, for example, one or more types of information among a set of character strings that are the content of the chat and user identifiers of two or more users who have chatted.
  • the user identifier here is, for example, the user's name and user's ID.
  • the call history information includes one or more types of information among a voice uttered by the user, a set of character strings resulting from character recognition of the voice uttered by the user, and user identifiers of each of the two users who made the call.
  • the user identifier here is, for example, a telephone number, a user's name, or a user's ID.
  • Non-communication system information is information related to non-communication systems.
  • a non-communicative system is one whose direct purpose is not communication.
  • Non-communication systems include, for example, a schedule management system, an invoice management system that manages the transmission and receipt of invoices, a contract management system that manages contracts, a registration management system that receives registrations for events, and an inquiry information management system. , gift management system, sales support system, customer management system, etc.
  • the system may be a server.
  • the sales support system and the customer management system do not have to be distinguished.
  • the sales support system and customer management system may be, for example, so-called MA, SFA, CRM.
  • an event is some event.
  • the event here is preferably an event related to business.
  • Non-communication system information includes, for example, calendar reservation information that is schedule information registered in a calendar server that constitutes a schedule management system, invoice information that is managed by an invoice management server that constitutes an invoice management system, and a contract management system.
  • contract information managed by the contract management server that makes up the registration management system registration information managed by the registration server that makes up the registration management system, gift information managed by the server that makes up the inquiry information management system, sales that make up the sales support system Sales activity information managed by the support server, customer information managed by the customer management server constituting the customer management system, order information managed by the order management server constituting the order management system, managed by the recruitment management server constituting the recruitment management system This is the recruitment information.
  • the exchange information may or may not include information related to exchanging business cards.
  • Information related to business card exchange is, for example, a set of a user identifier and business card information, or a set of user identifiers of each of the two users who have exchanged business cards.
  • 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 calendar schedule information is preferably associated with the user identifier of the user of the calendar.
  • a company may be rephrased as an organization.
  • 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 the web conference schedule information is preferably associated with the user identifier of one of the participants (for example, the organizer) of the web conference.
  • calendar schedule information and web conference schedule information can be referred to as schedule information without distinguishing between them.
  • the chat history information of the chat system includes, for example, the user identifier of the chat sender and the user identifier of the chat receiver.
  • Chat history information has, for example, chat strings.
  • the chat string is a string entered by the user.
  • Telephone call history information includes, for example, the user identifiers of the two people who made the call.
  • the user identifier here is usually a telephone number, but may be a name or the like registered in each communication medium.
  • the call history information includes, for example, a call character string that is a character string obtained by subjecting the voice of the call to character recognition processing.
  • the call history information includes, for example, voices of calls.
  • the invoice information is information related to invoices.
  • Billing information includes, for example, billing organization name information (e.g. billing company name), billing address information (e.g. billing company address), billing organization name information (e.g. billing company name) ), billing address information (e.g. billing company address) It has billing amount information, payee information, and payment date information.
  • the billing information also includes the billing contact identifier of the contact of the billing organization that sent the billing information.
  • the invoicing person in charge identifier is, for example, the name of the invoicing person in charge and the ID of the invoicing person in charge.
  • the billing information also includes a billing contact identifier for a contact at the billing organization that receives the billing information.
  • the billing contact person identifier is, for example, the name of the billing contact person or the ID of the billing contact person.
  • the contract information is information related to the contract.
  • Contract information has, for example, contractor organization name information of two or more contractors.
  • the contractor organization name information is, for example, the organization name of the parties to the contract.
  • the contract information has an identifier of the person in charge of the contract of the contractor organization.
  • the contract manager identifier is, for example, the name of the contract manager or the ID of the contract manager.
  • the contract information includes, for example, representative identification information of parties to the contract.
  • the representative identification information is information for identifying the representative, such as the name of the representative and the ID of the representative.
  • the registration information includes, for example, registrant identification information of registrants who registered for the event and event identifiers.
  • the registrant identification information is information for identifying registrants participating in the event, such as registrant names and registrant IDs.
  • An event identifier is information for identifying an event.
  • the event identifier is associated with, for example, event-related party identification information that identifies event-related parties.
  • the event-related person identification information is organizer identification information for identifying the organizer of the event, and speaker identification information for identifying the speaker (for example, lecturer) in the event.
  • the organizer identification information is information for identifying the organizer of the event, such as the name of the organizer and the ID of the organizer.
  • the speaker identification information is information for identifying the speaker in the event, and is, for example, the name of the speaker and the ID of the speaker.
  • Inquiry information includes, for example, delivery date information that specifies the delivery date of the form, receipt date information that specifies the date of receipt of the question, one or more questioner attribute values, question content, response content, and the person in charge of creating the form. Or it has the user identifier of the person in charge of creating the form.
  • One or more questioner attribute values are, for example, the name of the company to which the questioner belongs, the name of the department to which the questioner belongs, the position of the questioner, the email address of the questioner, and the name of the questioner. It is preferable that the inquiry information is associated with the user identifier of the user who receives the inquiry.
  • the gift information includes, for example, the date when the gift was sent and received, which is the date when the gift was sent, the content information indicating the content of the gift, one or more presenter attribute values of the gift sender (presenter), the gift delivery Has one or more beneficiary attribute values of the previous person (the beneficiary).
  • the presenter attribute value of the presenter is, for example, the name of the presenter, the mail address of the presenter, and the telephone number of the presenter.
  • the beneficiary attribute value of the beneficiary is, for example, the name of the beneficiary, the e-mail address of the beneficiary, and the telephone number of the beneficiary.
  • the gift information is preferably associated with the user identifier of the presenter.
  • Sales activity information consists of sales representative information, date of sales, customer information (called sales customer information), type of sales It has content information indicating the content.
  • Salesperson information includes, for example, the name of the salesperson, the name of the company to which the salesperson belongs, the name of the department to which the salesperson belongs, the title of the salesperson, the email address of the salesperson, and the telephone number of the salesperson. have.
  • the sales customer information includes, for example, the name of the customer, the name of the company to which the customer belongs, the name of the department to which the customer belongs, the position of the customer, the email address of the customer, and the telephone number of the customer. It is preferable that the sales activity information is associated with the user identifier of the sales representative.
  • the customer information includes, for example, the date when the customer and the person in charge contacted (contact date), the person in charge information of the customer's person in charge, and one or more customer attribute values.
  • the information on the person in charge includes, for example, the name of the person in charge, the name of the company to which the person in charge belongs, the name of the department to which the person in charge belongs, the title of the person in charge, the email address of the person in charge, and the telephone number of the person in charge.
  • One or more customer attribute values are, for example, the name of the customer, the name of the company to which the customer belongs, the name of the department to which the customer belongs, the position of the customer, the email address of the customer, and the telephone number of the customer.
  • the customer information is preferably associated with the user identifier of the person in charge.
  • the order information includes, for example, orderer information, order destination information, order date, delivery date, order details information, and transaction amount.
  • the orderer information is information about the orderer.
  • Orderer information includes, for example, name, address, telephone number, and e-mail address.
  • the order destination information is information about the order destination.
  • Order destination information includes, for example, name, company name, address, telephone number, and e-mail address.
  • the order detail information includes, for example, product name, quantity, unit price, and total price for each product.
  • the order information is preferably associated with the user identifier of the orderer or the user identifier of the user to whom the order is placed.
  • Recruitment information includes, for example, applicant information, applicant information, application date, interview date, application content information, and result information.
  • Applicant information is information about the applicant.
  • Applicant information includes, for example, name, address, telephone number, and e-mail address.
  • Applicant information is information about an organization (usually a company) to which the applicant applies.
  • the applicant information includes, for example, the company name, the name of the person in charge of the company (for example, the person in charge of the personnel department), the address of the company, the telephone number of the company, and the e-mail address of the person in charge of the company.
  • the application content information includes, for example, job type, information indicating whether or not the applicant is a regular employee, working hours, and salary.
  • Result information is information about the result of adoption.
  • the result information includes, for example, stage information specifying the stage leading up to employment, interview implementation information indicating whether or not an interview was conducted, and employment result information indicating whether or not the applicant was hired. It is preferable that the employment information is associated with the user identifier of the applicant or the user identifier of the person in charge of the applicant.
  • the pamphlet acquisition information is information about the acquisition of the pamphlet.
  • the pamphlet acquisition information includes, for example, acquirer information about the acquirer who acquired the pamphlet, organization information about the organization providing the pamphlet, and content information indicating the content of the pamphlet.
  • Acquirer information includes the name, address, e-mail address, and telephone number of the acquirer.
  • the organization information of the providing organization includes, for example, the company name, the company's telephone number, and the information of the person in charge of the company providing the pamphlet.
  • the person-in-charge information includes, for example, the name, email address, and telephone number of the person in charge.
  • the pamphlet content information includes, for example, a character string indicating an outline of the pamphlet and type information indicating the types of items such as products and services described in the pamphlet.
  • Expense information is information about expenses.
  • the expense information includes, for example, applicant information about the applicant of the expense, permitter information about the permitter who permits the use of the expense, and content information about the contents of the expense.
  • Applicant information includes, for example, the applicant's name, email address, and telephone number.
  • the permitter information includes, for example, the permitter's name, email address, and telephone number.
  • Expense content information includes, for example, types such as item of expense, amount of expense, date of use, and merchandise purchased.
  • Questionnaire information is information related to the questionnaires conducted for users.
  • the questionnaire information has, for example, one or more question information, answer information for each question information, respondent information, implementer information, questionnaire distribution date, and answer date.
  • the respondent information includes, for example, the respondent's name, email address, and telephone number.
  • the information on the implementer includes the name of the company that implements the questionnaire and information on the person in charge of the company.
  • the information on the person in charge has the name, email address, and telephone number of the person in charge.
  • the entry information includes, for example, visitor information, building information, and entry date.
  • Visitor information is information about visitors.
  • the visitor information includes, for example, the visitor's name, e-mail address, and telephone number.
  • the building information includes, for example, the owner information of the building that has been entered, and the address of the building.
  • the owner information includes the name of the company that owns the building, information about the representative of the company, and information about the manager who manages the building.
  • the representative information includes, for example, the company representative's name, email address, and telephone number.
  • the manager information includes the manager's name, email address, and telephone number.
  • Virtual space check-in information is information about the user's check-in to the virtual space.
  • the virtual space check-in information is arbitrarily referred to as check-in information.
  • the check-in information includes, for example, check-in person information who has checked in to the virtual space, spatial information about the virtual space, and check-in date.
  • the check-in person information includes the name, email address, and telephone number of the user who has checked in.
  • the space information includes the name of the virtual space and information on the operator of the virtual space.
  • the operator information includes the company name of the operator, the name of the operator of the company, the e-mail address, and the telephone number.
  • 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 in the user information storage unit 111 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.
  • 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.
  • the interaction relationship information is information specifying interaction with other users of the user identified by the user identifier.
  • Contact information typically corresponds to a user identifier.
  • the interaction relationship information usually corresponds to other user identifiers of other users who have an interaction relationship with the user identified by the user identifier. It should be noted that corresponding to the user identifier (including other user identifiers) may include 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”, “chat”, “telephone”, “bill”, “contract”, “event”, 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.
  • “Chat” is information indicating that there was an exchange using the chat system.
  • “Telephone” is information indicating that there was an exchange (a call was made) by telephone.
  • "Bill” is information indicating that bills were exchanged and there was interaction.
  • “Contract” is information indicating that the contract was exchanged and there was interaction. This is information indicating that there was interaction in the "event”.
  • "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 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 .
  • the user identifier acquisition unit 131 acquires, for example, one user identifier corresponding to the friendship information.
  • 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 user identifier acquired by the user identifier acquiring unit 131 may be a user identifier acquired by the other user information acquiring unit 134, which will be described later.
  • the exchange information determination unit 132 determines exchange information from the storage unit 11 that stores one or more exchange information.
  • the storage unit 11 here may be the server storage unit 21 of the information server 2 .
  • the exchange information determination unit 132 determines the exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 from among one or more pieces of exchange information.
  • the exchange information determination unit 132 may determine all obtainable exchange information.
  • Acquirable exchange information is, for example, exchange information in the storage unit 11 .
  • Acquirable exchange information is, for example, exchange information stored in one or more accessible information servers 2 .
  • the exchange information determination unit 132 determines one or more pieces of exchange information from among two or more types of exchange information. In other words, it is preferable that the exchange information determination unit 132 determines one or more pieces of exchange information from pieces of exchange information associated with two or more types of identifiers. In other words, the exchange information determined by the exchange information determination unit 132 is preferably two or more types of exchange information.
  • Two or more types of exchange information have corresponding type identifiers of "email”, “calendar”, “web conference”, “chat”, “telephone”, “invoice”, “contract”, “event”, “inquiry”, “gift”, "email”, "email”, "calendar”, "web conference”, “chat”, “telephone”, “invoice”, “contract”, “event”, “inquiry”, “gift”, "email”, "email”, "calendar”, "web conference”, “chat”, “telephone”, “invoice”, “contract”, “event”, “inquiry”, “gift”, " There are two types of exchange information: sales activities, customers, recruitment, pamphlets, expenses, questionnaires, admission, virtual space check-ins, and business cards.
  • the interaction information determination unit 132 determines one or more pieces of interaction information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 determines, for example, exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and satisfying a predetermined condition from among one or more pieces of exchange information.
  • 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 one or two or more information servers 2.
  • the exchange information described above is 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 .
  • a predetermined condition is, for example, a content condition.
  • the content condition is, for example, a condition regarding a character string that exchange information has.
  • a predetermined condition is, for example, a frequency condition.
  • the frequency condition is a condition regarding the frequency of alternating current.
  • the frequency condition is, for example, that the number of times of alternating current is greater than or equal to a threshold.
  • the frequency condition is, for example, that exchanges by e-mail are equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of pairs of user identifiers corresponding to calendar information is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of web conferences held is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of chats is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of telephone calls is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of inquiries made by one user is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of gift presentations by one user is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of sales to one user is equal to or greater than a threshold.
  • the frequency condition is, for example, that the number of orders placed by one user is equal to or greater than a threshold. Note that "greater than or equal to the threshold" may be replaced with "greater than the threshold”.
  • a predetermined condition is, for example, a time condition.
  • the timing condition is a condition regarding the timing of the exchange.
  • the timing condition is, for example, that the timing of the exchange is a predetermined timing, and the timing condition is that the timing of the exchange is not a predetermined timing, for example.
  • the predetermined period is, for example, the mid-year gift period (for example, July) and the year-end gift period (for example, December).
  • a non-predetermined period is, for example, Christmas time (eg, December 24th to December 25th). It is preferable that the time condition is a period for interaction in business.
  • 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).
  • 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.
  • prediction processing machine learning classifier
  • 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.
  • machine learning so-called deep learning, random forest, decision tree, SVM, etc. can be used, but any algorithm can be used.
  • 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.
  • 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.
  • 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.
  • deep learning, random forest, decision tree, SVM, etc. can be used for such machine learning as well, but any algorithm can be used.
  • 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 exchange information determination unit 132 determines exchange information using, for example, communication system information.
  • the communication system information is e-mail, web conference reservation information, chat history information, or call history information, for example.
  • the exchange information determination unit 132 determines exchange information using, for example, non-communication system information.
  • Non-communication system information for example, invoice information, contract information, registration information, inquiry information, gift information, sales activity information, customer information, order information, employment information, brochure acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information.
  • the exchange information determination unit 132 determines one or more pieces of chat history information from, for example, one or more pieces of chat history information in the storage unit 11 . For example, the exchange information determination unit 132 determines one or more pieces of chat history information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . The exchange information determination unit 132 determines, for example, one or more pieces of chat history information that satisfy a predetermined condition from the one or more pieces of chat history information in the storage unit 11 .
  • the predetermined conditions are, for example, business interaction conditions and frequency conditions.
  • the content conditions for chat history information are, for example, business exchange conditions.
  • a content condition is, for example, that the business term stored in the storage unit 11 is included in the character string of the chat history information.
  • a business exchange condition for chat history information is, for example, that the class of a character string (text, etc.) in the chat history information is "business.”
  • the process of determining the class of a character string is a known technique.
  • the exchange information determination unit 132 learns the acquired binary classification as a result of learning processing of two or more teacher data having a character string and a class (for example, "business" or not) by a machine learning algorithm. Use a vessel.
  • the interaction information determining unit 132 supplies the learning device and the chat history information to a machine learning prediction processing module, executes the module, and determines whether the class of the chat history information is “business”. decide. Then, the exchange information determination unit 132 determines one or more pieces of chat history information corresponding to the class "business".
  • the frequency condition regarding the chat history information is, for example, that the chat history information corresponds to the other user with whom the user identified by the user identifier acquired by the user identifier acquiring unit 131 has chatted more times than or equal to a threshold.
  • the exchange information determination unit 132 determines that, among the two or more user identifiers corresponding to the one or more pieces of chat history information to be determined, there is a set of two user identifiers whose frequency of appearance is equal to or greater than the threshold. Whether or not it exists is determined, and the chat history information corresponding to the set of two user identifiers having such frequency of occurrence is determined.
  • the interaction information determination unit 132 may acquire two user identifiers forming the interaction relationship information.
  • the exchange information determination unit 132 determines one or more pieces of call history information from, for example, one or more pieces of call history information in the storage unit 11 .
  • Exchange information determination unit 132 determines one or more pieces of call history information corresponding to the user identifier acquired by user identifier acquisition unit 131 .
  • the exchange information determination unit 132 determines, for example, one or more pieces of call history information that satisfy a predetermined condition from the one or more pieces of call history information in the storage unit 11 .
  • the predetermined conditions are, for example, business interaction conditions and frequency conditions.
  • the call history information includes, for example, a character string obtained by recognizing a voice call.
  • the content conditions related to call history information are, for example, business exchange conditions.
  • a content condition is, for example, that the business term stored in the storage unit 11 is included in the character string of the call history information.
  • a business interaction condition for call history information is, for example, that the class of character strings (such as sentences) in the call history information is "business.” Note that the process of determining the class of a character string is a known technique as described above.
  • the exchange information determination unit 132 determines whether or not the class of the call history information is "business" using a known technique. Then, the exchange information determination unit 132 determines one or more pieces of call history information corresponding to the class "business".
  • the frequency condition regarding the call history information is, for example, that the user identified by the user identifier acquired by the user identifier acquiring unit 131 is the call history information corresponding to the user with whom the number of times the user has made a call is equal to or greater than the threshold. is. That is, for example, the exchange information determination unit 132 determines that, among the two or more user identifiers corresponding to the one or more pieces of call history information to be determined, there is a set of two user identifiers whose frequency of appearance is equal to or greater than the threshold. It determines whether or not it exists, and determines the call history information corresponding to the set of two user identifiers with such frequency of occurrence. Note that the interaction information determination unit 132 may acquire two user identifiers forming the interaction relationship information.
  • the exchange information determination unit 132 determines one or more items of invoice information from, for example, one or more items of invoice information in the storage unit 11 .
  • the interaction information determination unit 132 determines, for example, one or more items of invoice information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more items of bill information that satisfy a predetermined condition from among the items of bill information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • a predetermined condition is, for example, a frequency condition.
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • Conditions for the content of invoice information are conditions for the information contained in the invoice.
  • the content conditions of the invoice information are, for example, ⁇ the amount of the invoice information is equal to or greater than the threshold value'', and ⁇ the item name of the invoice (such as the name of the product purchased) is a predetermined item name. That is.
  • the frequency condition is that the appearance frequency of a pair of two user identifiers corresponding to one piece of billing information is equal to or greater than a threshold.
  • the user identifier corresponding to the bill information may be a user identifier paired with the bill information, billing source identification information included in the bill information, or billing destination identification information included in the bill information.
  • the exchange information determination unit 132 determines one or more pieces of contract information from, for example, one or more pieces of contract information in the storage unit 11 .
  • the interaction information determination unit 132 determines, for example, one or more pieces of contract information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the interaction information determination unit 132 may determine one or more pieces of contract information that satisfy a predetermined condition from among one or more pieces of contract information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • the conditions for the content of the contract information are the conditions for the information contained in the contract.
  • Content conditions of the contract information include, for example, ⁇ the amount of money included in the contract information is equal to or greater than the threshold value'', and ⁇ the title of the contract is a predetermined specific title (for example, ⁇ collaborative research contract "Sales Agreement") and not a predetermined specific title (eg, "Sales Agreement").
  • the contract information frequency condition is that the frequency of appearance of a pair of two user identifiers corresponding to one piece of contract information is equal to or greater than a threshold.
  • the user identifier corresponding to the contract information may be a user identifier paired with the contract information, or may be billing party identification information included in the contract information or billing party identification information included in the contract information.
  • the exchange information determination unit 132 determines one or more registration information items from the one or more registration information items in the storage unit 11 .
  • the interaction information determining unit 132 determines one or more pieces of registration information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example.
  • the exchange information determination unit 132 may determine one or more pieces of registration information that satisfy a predetermined condition from among one or more pieces of registration information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • Registration information content conditions are conditions related to the content of registration information.
  • the content condition of the registration information is, for example, "the seminar corresponding to the registration information is a seminar for business". Whether or not the seminar is for business is determined using, for example, the title of the seminar corresponding to the registration information. For example, when a business term is included in the title of the seminar corresponding to the registered information, the interaction information determination unit 132 determines that the seminar is for business. For example, the exchange information determining unit 132 acquires a class indicating whether or not the seminar title, which is a character string, is a business or not through machine learning prediction processing, which is the prediction processing described above.
  • the registration information frequency condition is that the appearance frequency of a pair of two user identifiers corresponding to one piece of registration information is equal to or greater than a threshold.
  • the user identifier corresponding to the registration information is the user identifier included in the registration information (for example, the identifier of the user who applied for the seminar) and the user identifier corresponding to the registration information (for example, the identifier of the seminar organizer). .
  • the interaction information determination unit 132 determines one or more pieces of inquiry information from, for example, one or more pieces of inquiry information in the storage unit 11 .
  • the interaction information determination unit 132 determines, for example, one or more pieces of inquiry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more pieces of inquiry information that satisfy a predetermined condition from among one or more pieces of inquiry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • the content conditions of the inquiry information are conditions related to the content of the registration information.
  • the content condition of the inquiry information is, for example, that the content information (character string) included in the inquiry information is information about the content of business. Whether or not the content information is business-related content information can be determined by the above-described character string class classification technique.
  • the exchange information determination unit 132 determines one or more pieces of gift information from the one or more items of gift information in the storage unit 11 .
  • the exchange information determination unit 132 determines, for example, one or more pieces of gift information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more pieces of gift information that satisfy a predetermined condition from among the one or more pieces of gift information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the predetermined conditions are, for example, timing conditions and content conditions.
  • the timing conditions of the gift information are the conditions related to the gift sending and receiving date that the gift information has.
  • the time conditions are, for example, that the date of receipt of the gift delivery falls on a day during the mid-year gift period (eg, July), that the date of receipt of the gift delivery falls on a day during the year-end gift period (eg, December), and that the date of receipt of the gift delivery falls on a day during the Christmas period. (for example, from 12/24 to 12/25).
  • Gift information content conditions are conditions related to content information possessed by gift information.
  • the content condition is, for example, that the content information of the gift information includes specific information (for example, "opening celebration” or "establishment celebration”).
  • the interaction information determination unit 132 determines one or more pieces of business activity information from, for example, one or more pieces of business activity information in the storage unit 11 .
  • the exchange information determination unit 132 determines one or more pieces of business activity information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more sales activity information items that satisfy a predetermined condition from the one or more sales activity information items corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, frequency conditions and content conditions.
  • the frequency condition of the sales activity information is, for example, that the number of sales customer information of one customer corresponding to one salesperson in the sales activity information is equal to or greater than a threshold or greater than the threshold (the number of sales is large). be.
  • the content condition of the sales activity information is, for example, the case where the sales activity information includes information indicating that a contract has been concluded as a result of sales.
  • the interaction information determination unit 132 determines one or more pieces of customer information from, for example, one or more pieces of customer information in the storage unit 11 .
  • the interaction information determination unit 132 determines, for example, one or more pieces of customer information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more pieces of customer information that satisfy a predetermined condition from among the pieces of customer information corresponding to the user identifiers acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, frequency conditions and content conditions.
  • the customer information frequency condition is, for example, that the customer information of one customer corresponding to one person in charge exists in a number equal to or greater than a threshold value (the number of opportunities for the relationship between the person in charge and the customer is high). that).
  • Content conditions for customer information are, for example, when the customer information includes information indicating that a contract has been concluded.
  • the interaction information determination unit 132 determines one or more pieces of order information from, for example, one or more pieces of order information in the storage unit 11 .
  • the interaction information determination unit 132 determines one or more items of order information corresponding to the user identifier acquired by the user identifier acquisition unit 131, for example.
  • the exchange information determination unit 132 may determine one or more pieces of order information that satisfy a predetermined condition from the one or more pieces of order information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, frequency conditions and content conditions.
  • the order information frequency condition is, for example, that the number of orderer information of one orderer corresponding to one orderer in the order information is greater than or equal to a threshold value (one orderer for one orderer) are ordering frequently).
  • the content conditions of the order information are, for example, the conditions related to the transaction amount contained in the order information and the conditions related to the product name contained in the order information.
  • the condition regarding the transaction amount is, for example, that the transaction amount is greater than or equal to a threshold.
  • the condition regarding the product name is, for example, that the product name is a predetermined product name.
  • the exchange information determination unit 132 determines one or more pieces of employment information from, for example, one or more pieces of employment information in the storage unit 11 .
  • the exchange information determining unit 132 determines one or more pieces of employment information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example.
  • the exchange information determination unit 132 may determine one or more pieces of employment information that satisfy a predetermined condition from among one or more pieces of employment information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • a predetermined condition is, for example, a content condition.
  • the content conditions of the employment information are, for example, the conditions related to the application content information contained in the employment information, or the conditions related to the result information contained in the employment information.
  • the conditions for the application content information are, for example, that the occupation is a specific occupation, and that the information indicating whether or not the applicant is a regular employee is "regular employee.”
  • Conditions related to the result information are, for example, that the stage information is information indicating that the hiring step has reached a specific stage, that the interview implementation information is information that indicates that an interview was conducted, and that the recruitment result information. is information that indicates that the applicant has been "adopted".
  • the exchange information determination unit 132 determines one or more pamphlet acquisition information from, for example, one or more pamphlet acquisition information in the storage unit 11 . For example, the exchange information determination unit 132 determines one or more pieces of pamphlet acquisition information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more pamphlet acquisition information that satisfies a predetermined condition from one or more pamphlet acquisition information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • a predetermined condition is, for example, a content condition.
  • the content conditions of the pamphlet acquisition information are, for example, the conditions related to the content information and the type information contained in the pamphlet acquisition information.
  • a condition regarding the content information is, for example, that the content information includes business terms.
  • the condition regarding the type information is, for example, that the type information is information of a predetermined type.
  • the exchange information determination unit 132 determines one or more pieces of expense information from, for example, one or more items of expense information in the storage unit 11 .
  • the exchange information determination unit 132 determines, for example, one or more pieces of expense information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the exchange information determination unit 132 may determine one or more expense information items that satisfy a predetermined condition from among the one or more expense information items corresponding to the user identifiers acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • the content conditions for the expense information are, for example, that the item of expense is a predetermined item, that the amount is equal to or greater than the threshold, and that the type of product purchased is of a predetermined type.
  • the frequency condition of expense information is that one applicant applies for expenses more than or equal to the threshold, and that one applicant applies for expenses more than or equal to the threshold in a unit period. It is what we are doing.
  • the interaction information determination unit 132 determines one or more pieces of questionnaire information from, for example, one or more pieces of questionnaire information in the storage unit 11 .
  • the interaction information determination unit 132 determines, for example, one or more pieces of questionnaire information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • the interaction information determination unit 132 may determine one or more pieces of questionnaire information that satisfy a predetermined condition from among one or more pieces of questionnaire information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • Predetermined conditions are, for example, content conditions and frequency conditions.
  • the conditions for the contents of the questionnaire information are, for example, that it contains answer information and that the answer information satisfies predetermined conditions.
  • the condition for the frequency of questionnaire information is, for example, that one user has sent answers to the questionnaire more than or equal to the threshold.
  • the interaction information determination unit 132 determines one or more pieces of admission information from, for example, one or more pieces of admission information in the storage unit 11 .
  • the interaction information determining unit 132 determines, for example, one or more pieces of museum admission information corresponding to the user identifier acquired by the user identifier acquiring unit 131 .
  • the exchange information determination unit 132 may determine one or more pieces of hall entry information that satisfy a predetermined condition from the one or more pieces of hall entry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • a predetermined condition is, for example, a frequency condition.
  • the condition for the frequency of admission information is, for example, that the number of admission information associated with one user identifier is greater than or equal to a threshold (the number of visits to the facility is large).
  • the exchange information determination unit 132 determines one or more pieces of check-in information from, for example, one or more pieces of check-in information in the storage unit 11 .
  • the interaction information determining unit 132 determines one or more pieces of check-in information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example.
  • the exchange information determination unit 132 may determine one or more pieces of check-in information that satisfy a predetermined condition from among one or more pieces of check-in information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
  • a predetermined condition is, for example, a frequency condition.
  • the check-in information frequency condition is, for example, that the number of check-in information associated with one user identifier is greater than or equal to a threshold (a large number of check-ins).
  • 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.
  • 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.
  • 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 .
  • 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, for example, one user identifier corresponding to the interaction information acquired by the interaction information determination unit 132 . Further, the other user information acquisition unit 134 acquires other user information including, for example, another user identifier that is different from the one user identifier and that corresponds to the interaction information acquired by the interaction information determination unit 132. .
  • the acquisition of one user identifier by the other user information acquisition unit 134 may be acquisition of one user identifier acquired by the user identifier acquisition unit 131, or acquisition of the interaction information acquired by the interaction information determination unit 132. may be used to obtain one user identifier. Acquiring one user identifier may be information identified by one user identifier, information about the user, and information constituting interaction information.
  • 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.
  • the other user information acquisition unit 134 acquires other user information using the communication system information.
  • the exchange information determination unit 132 uses the non-communication system information to acquire other user information.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the signature delimiter line for example, the character “*”, “ ⁇ ”, “+”, etc.
  • the other user information acquisition unit 134 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 of .
  • 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.
  • 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.
  • attribute values for example, company name, name, etc.
  • 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 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 .
  • exchange information is chat history information
  • the other user information acquisition unit 134 acquires other user information corresponding to the chat history information determined by the exchange information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the chat history information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the chat history information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has interacted with the user identified by the user identifier acquired by the user identifier acquisition unit 131 through chat. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the chat history information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more of the acquired user identifiers as a key, and obtains part or all of the matching user information. Get user information.
  • the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to (6) When exchange information is call history information
  • the other user information acquisition unit 134 acquires other user information corresponding to the call history information determined by the exchange information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the call history information determined by the exchange information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the call history information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has made a telephone call with the user identified by the user identifier acquired by the user identifier acquisition unit 131 . Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
  • the other user information acquisition unit 134 is, for example, one or more user identifiers (for example, telephone numbers) associated with the call history information determined by the interaction information determination unit 132, and the user identifier acquisition unit 131 acquires Acquire one or more user identifiers paired with the user identifier.
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more of the acquired user identifiers as a key, and obtains part or all of the matching user information. Get user information.
  • the other user information acquisition unit 134 acquires a character string included in the call history information paired with the user identifier acquired by the user identifier acquisition unit 131.
  • the other user information acquisition unit 134 performs morphological analysis on the character string (for example, "Hello, Mr. Taro Yamada from A Co., Ltd. is there?"), and from the analysis result, 1
  • the above attribute values are acquired, the user information storage unit 111 is searched using the one or more attribute values, and other user information having part or all of the matching user information is acquired.
  • the one or more attribute values are, for example, a company name (eg, "A Corporation"), a name (eg, "Taro Yamada"), and a name (eg, "Yamada").
  • the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to (7) When exchange information is invoice information
  • the other user information acquisition unit 134 acquires other user information corresponding to the invoice information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the invoice information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the invoice information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has exchanged bills with the user identified by the user identifier acquired by the user identifier acquisition unit 131 . Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the invoice information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more acquired user identifiers, and obtains a part or all of the matching user information. Get user information.
  • the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to (8) When exchange information is contract information
  • the other user information acquisition unit 134 acquires other user information corresponding to the contract information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the contract information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the contract information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has made a contract with the user identified by the user identifier acquired by the user identifier acquisition unit 131 or who has made a contract. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
  • Other user information acquisition unit 134 for example, from the contract information determined by exchange information determination unit 132, one or more attribute values name of the representative corresponding to Next, the other user information acquisition unit 134 acquires other user information including the one or more attribute values, for example.
  • Other user information acquisition unit 134 for example, from the contract information determined by exchange information determination unit 132, one or more attribute values name of the representative corresponding to Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more attribute values, and obtains other user information having part or all of the matching user information. to get
  • Other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more attribute values of A, and finds one that has some or all of the matching user information. Get the user information of the user of .
  • the user information of one user may be the user identifier of one user, or may include the user identifier of one user.
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more attribute values of the user B, and searches other users having part or all of the matching user information Get information.
  • a and B may be exchanged.
  • the other user information acquisition unit 134 acquires other user information corresponding to the registration information determined by the interaction information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the registration information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the registration information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Acquire the above user identifiers. Each of the one or more user identifiers is an identifier of a user who interacted with the user identified by the user identifier acquired by the user identifier acquisition unit 131 at the event. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
  • the other user information acquisition unit 134 is, for example, one or more user identifiers associated with the registration information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Acquire the above user identifiers.
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more user identifiers, and searches for other users having part or all of the matching user information. Get information.
  • the other user information acquisition unit 134 acquires, for example, one or more attribute values (eg, company name, department name, name) of the registration information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more attribute values, for example.
  • attribute values eg, company name, department name, name
  • the other user information acquisition unit 134 acquires, for example, one or more attribute values (for example, company name, department name, name) of the registration information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more attribute values, and obtains other user information having part or all of the matching user information. to get (10) When exchange information is inquiry information
  • the other user information acquisition unit 134 acquires other user information corresponding to the inquiry information determined by the exchange information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the inquiry information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • Other user information acquisition unit 134 for example, one or more questioner attribute values (eg, name, company name, department name, title, email address, telephone number) possessed by the inquiry information determined by the interaction information determination unit 132 get. Next, the other user information acquisition unit 134 acquires other user information including the one or more questioner attribute values, for example.
  • questioner attribute values eg, name, company name, department name, title, email address, telephone number
  • Other user information acquisition unit 134 for example, one or more questioner attribute values (eg, name, company name, department name, title, email address, telephone number) possessed by the inquiry information determined by the interaction information determination unit 132 get.
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more questioner attribute values, and has part or all of the matching user information Get user information.
  • (11) When exchange information is gift information
  • the other user information acquisition unit 134 acquires other user information corresponding to the gift information determined by the exchange information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the gift information determined by the exchange information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, one or more beneficiary attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more beneficiary attribute values, for example.
  • one or more beneficiary attribute values eg, name, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, one or more presenter attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more presenter attribute values, for example.
  • one or more presenter attribute values eg, name, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, one or more beneficiary attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more beneficiary attribute values, and obtains part or all of the matching user information. Get user information.
  • one or more beneficiary attribute values eg, name, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, one or more presenter attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more presenter attribute values, and obtains a part or all of the matching user information. Get user information.
  • one or more presenter attribute values eg, name, email address, phone number
  • the other user information acquisition unit 134 acquires part or all of the user information corresponding to the above-described gift giver as information of one user, and obtains part or all of the user information corresponding to the above-described beneficiary. information may be acquired as other user information. Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 acquires part or all of the user information corresponding to the above-described giftee as information of one user, and acquires the above-described user information corresponding to the giftee as other user information. You can get it. User information of such one user corresponds to one user identifier. (12) When exchange information is sales activity information
  • the other user information acquisition unit 134 acquires other user information corresponding to the business activity information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the business activity information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, one or more customer information (eg, name, company name, department name, title, email address, phone number) included in the business activity information determined by the interaction information determination unit 132. do. Next, the other user information acquisition unit 134 acquires other user information including information on the one or more customers, for example.
  • customer information eg, name, company name, department name, title, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, sales person information (eg, name, company name, department name, title, email address, telephone number) included in the sales activity information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the salesperson information, for example.
  • sales person information eg, name, company name, department name, title, email address, telephone number
  • the other user information acquisition unit 134 acquires, for example, one or more customer information (eg, name, company name, department name, title, email address, phone number) included in the business activity information determined by the interaction information determination unit 132. do. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the information of the one or more customers, for example, and searches for other users who have part or all of the matching user information. Get information.
  • customer information eg, name, company name, department name, title, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, salesperson information included in the sales activity information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the salesperson information, and obtains other user information having part or all of the matching user information. get.
  • the other user information acquisition unit 134 may associate the other user information acquired using the customer information described above with the other user information acquired using the salesperson information described above as information on one user. good. Such one user information corresponds to one user identifier.
  • the other user information acquisition part 134 may match with other user information acquired using the customer's information mentioned above.
  • User information of such one user corresponds to one user identifier. (13)
  • exchange information is customer information
  • the other user information acquisition unit 134 acquires other user information corresponding to the customer information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the customer information determined by the interaction information determination unit 132 . Note that such one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, one or more customer attribute values (eg, name, company name, department name, title, email address, phone number) of the customer information determined by the interaction information determination unit 132. . Next, the other user information acquisition unit 134 acquires other user information including information on the one or more customers, for example.
  • customer attribute values eg, name, company name, department name, title, email address, phone number
  • the other user information acquisition unit 134 acquires, for example, the person in charge information (eg, name, company name, department name, title, email address, telephone number) included in the customer information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
  • the person in charge information eg, name, company name, department name, title, email address, telephone number
  • the other user information acquisition unit 134 acquires, for example, one or more customer attribute values (eg, name, company name, department name, title, email address, phone number) of the customer information determined by the interaction information determination unit 132. .
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more customer attribute values, and searches for other users having part or all of the matching user information. Get information.
  • the other user information acquisition unit 134 acquires, for example, the person in charge information included in the customer information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 treats the other user information acquired using the person in charge information described above as the information of one user, and associates it with the other user information acquired using the one or more customer attribute values described above. can be Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 treats the other user information acquired using the one or more customer attribute values described above as information of one user, and associates the other user information acquired using the person in charge information described above with the other user information.
  • the other user information acquisition unit 134 acquires other user information corresponding to the order information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the order information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, orderer information (for example, name, address, telephone number, email address) included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the orderer information, for example.
  • orderer information for example, name, address, telephone number, email address
  • the other user information acquisition unit 134 acquires, for example, order destination information (for example, name, company name, address, telephone number, email address) included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the order destination information, for example.
  • order destination information for example, name, company name, address, telephone number, email address
  • the other user information acquisition unit 134 acquires, for example, orderer information included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the orderer information, for example, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 acquires order destination information included in the order information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the orderer information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 may regard the other user information acquired using the orderer information described above as the information of one user, and associate it with the other user information acquired using the order destination information described above. .
  • Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may regard the other user information acquired using the order destination information described above as the information of one user and associate it with the other user information acquired using the orderer information described above. .
  • User information of such one user corresponds to one user identifier.
  • the other user information acquisition unit 134 acquires other user information corresponding to the employment information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the employment information determined by the exchange information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, applicant information (eg, name, address, phone number, email address) included in the employment information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the applicant information, for example.
  • applicant information eg, name, address, phone number, email address
  • the other user information acquisition unit 134 acquires, for example, the information (eg, name, email address) of the person in charge contained in the applicant information contained in the employment information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including, for example, the information of the person in charge.
  • the information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, applicant information included in the employment information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the applicant information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 acquires the information of the person in charge contained in the applicant information contained in the employment information determined by the exchange information determination unit 132 .
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the information of the person in charge, and obtains other user information having part or all of the matching user information. get.
  • the other user information acquisition unit 134 may associate the other user information acquired using the applicant information described above with the other user information acquired using the information of the person in charge described above as information of one user. good. Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may associate the other user information acquired using the above-described information of the person in charge with the other user information acquired using the above-described applicant information as the information of one user. good. User information of such one user corresponds to one user identifier. (15) When exchange information is pamphlet acquisition information
  • the other user information acquisition unit 134 acquires other user information corresponding to the pamphlet acquisition information determined by the interaction information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the pamphlet acquisition information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires acquirer information (for example, name, address, telephone number, email address) included in the pamphlet acquisition information determined by the interaction information determination unit 132, for example. Next, the other user information acquisition unit 134 acquires other user information including the acquirer information, for example.
  • acquirer information for example, name, address, telephone number, email address
  • the other user information acquisition unit 134 acquires, for example, information on the person in charge of the providing company (eg, name, email address) included in the pamphlet acquisition information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
  • information on the person in charge of the providing company eg, name, email address
  • the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
  • the other user information acquisition unit 134 acquires acquirer information included in the pamphlet acquisition information determined by the interaction information determination unit 132, for example. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the acquirer information, for example, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 acquires, for example, person-in-charge information included in the pamphlet acquisition information determined by the exchange information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 may regard the other user information acquired using the acquirer information described above as the information of one user, and associate it with the other user information acquired using the person in charge information described above. .
  • Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may set the other user information acquired using the person in charge information described above as the information of one user, and may associate it with the other user information acquired using the acquirer information described above. .
  • User information of such one user corresponds to one user identifier.
  • the other user information acquisition unit 134 acquires other user information corresponding to the expense information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the expense information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires applicant information (eg, name, address, phone number, email address) included in the expense information determined by the interaction information determination unit 132, for example.
  • applicant information eg, name, address, phone number, email address
  • other user information acquisition part 134 acquires other user information including the applicant information concerned, for example.
  • the other user information acquisition unit 134 acquires, for example, authorized person information (eg, name, email address) included in the expense information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the authorized person information, for example.
  • authorized person information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, the applicant information included in the expense information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the applicant information, for example, and acquires other user information having part or all of the matching user information do.
  • the other user information acquisition unit 134 acquires the permitter information included in the expense information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the authorized person information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 may set the other user information acquired using the applicant information described above as the information of one user, and may associate it with the other user information acquired using the permitter information described above. .
  • Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may set the other user information acquired using the above-described permitter information as information of one user, and may associate the other user information acquired using the above-described applicant information. .
  • User information of such one user corresponds to one user identifier. (17) When exchange information is questionnaire information
  • the other user information acquisition unit 134 acquires other user information corresponding to the questionnaire information determined by the interaction information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the questionnaire information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, respondent information (eg, name, address, phone number, email address) included in the questionnaire information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the answerer information, for example.
  • respondent information eg, name, address, phone number, email address
  • the other user information acquisition unit 134 acquires, for example, person-in-charge information (eg, name, email address) included in the information on the person conducting the questionnaire contained in the questionnaire information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
  • person-in-charge information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, respondent information included in the questionnaire information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the answerer information, for example, and acquires other user information having part or all of the matching user information do.
  • the other user information acquisition unit 134 acquires, for example, the person-in-charge information included in the questionnaire information determined by the interaction information determination unit 132 .
  • the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 may set the other user information acquired using the respondent information described above as the information of one user and associate it with the other user information acquired using the person in charge information described above. .
  • Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may set the other user information acquired using the person in charge information described above as the information of one user, and associate it with the other user information acquired using the respondent information described above. .
  • User information of such one user corresponds to one user identifier.
  • the other user information acquisition unit 134 acquires other user information corresponding to the building entry information determined by the exchange information determination unit 132 .
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the admission information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, visitor information (eg, name, address, phone number, email address) included in the admission information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the visitor information, for example.
  • visitor information eg, name, address, phone number, email address
  • the other user information acquisition unit 134 acquires, for example, representative information (eg, name, email address) included in the admission information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the representative information, for example.
  • representative information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, administrator information (eg, name, email address) included in the admission information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the administrator information, for example.
  • administrator information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, visitor information included in the admission information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the visitor information, for example, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 acquires, for example, representative information included in the admission information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the representative information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 acquires, for example, administrator information included in the building entry information determined by the exchange information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the administrator information, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 treats the other user information acquired using the visitor information described above as the information of one user, and corresponds to the other user information acquired using the representative information or administrator information described above. You can attach it. Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 treats the other user information acquired using the above-described representative information or administrator information as information of one user, and corresponds to the other user information acquired using the above-described visitor information. You can attach it. User information of such one user corresponds to one user identifier. (19) When exchange information is check-in information
  • the other user information acquisition unit 134 acquires other user information corresponding to the check-in information determined by the interaction information determination unit 132.
  • the other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the check-in information determined by the interaction information determination unit 132 .
  • the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
  • the other user information acquisition unit 134 acquires, for example, check-in person information (eg, name, phone number, email address) included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the check-in person information, for example.
  • check-in person information eg, name, phone number, email address
  • the other user information acquisition unit 134 acquires operator information (eg, name, email address) included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the operator information, for example.
  • operator information eg, name, email address
  • the other user information acquisition unit 134 acquires, for example, check-in person information included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the check-in person information, and searches for other user information having part or all of the matching user information. get.
  • the other user information acquisition unit 134 acquires operator information included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the operator information, for example, and acquires other user information having part or all of the matching user information. do.
  • the other user information acquisition unit 134 may associate the other user information acquired using the check-in person information described above with the other user information acquired using the operator information described above as information of one user. good. Such one user information corresponds to one user identifier.
  • the other user information acquisition unit 134 may associate the other user information acquired using the operator information described above with the other user information acquired using the check-in person information described above as information of one user. good. User information of such one user corresponds to one user identifier.
  • the interaction relationship storage unit 135 stores interaction relationship information that associates other user information with user identifiers.
  • other user information here is the information which the other user information acquisition part 134 acquired.
  • the user identifier here is, for example, information acquired by the user identifier acquiring unit 131 .
  • the user identifier may be information acquired by the other user information acquiring unit 134, 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.
  • the interaction relationship storage unit 135 stores, for example, interaction relationship information having a user identifier and other user information acquired by the other user information acquisition unit 134 .
  • the interaction relationship storage unit 135 stores interaction relationship information, which is link information to the other user information acquired by the other user information acquisition unit 134, in association with the user identifier.
  • the interaction relationship accumulation unit 135 accumulates interaction relationship information in the interaction relationship storage unit 114, for example.
  • 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.
  • 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 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.
  • 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.
  • Predetermined processing includes notification of change information, posting of change information on a web page, transmission of other user information that has changed, or one or more user attribute values included in the other user information.
  • 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.
  • 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.
  • the transmission unit 14 transmits various information corresponding to various information transmission instructions.
  • server storage unit 21 that constitutes the information server 2 .
  • the server storage unit 21 stores one or more mails.
  • Each email is associated with, for example, the email address of the recipient who receives the email.
  • 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.
  • 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.
  • 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 storage unit 21 stores one or more pieces of chat history information.
  • the chat history information is associated with user identifiers of one or more users who have chatted.
  • the user identifier of one user's chat 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.
  • the server storage unit 21 stores one or more pieces of call history information.
  • the call history information is associated with user identifiers of two or more users who have made calls. Note that the user identifier of the telephone 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 storage unit 21 stores one or more items of invoice information.
  • the invoice information is associated with one or more user identifiers of the user identifier of the user who issued the invoice and the user identifier of the user who accepts the invoice.
  • the user identifier of one user's bill management 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.
  • the server storage unit 21 stores one or more pieces of contract information.
  • the contract information is associated with user identifiers of one or more users who conclude the contract.
  • the user identifier of one user's contract management 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.
  • the server storage unit 21 stores one or more pieces of registration information.
  • the registration information is associated with the user identifier of the user who registered for the event.
  • the registration information may be associated with the user identifiers of the parties involved in the event.
  • a person concerned is, for example, an organizer of an event, a speaker at the event, or the like.
  • the user identifier of the registration 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 instruction, exchange information (e.g., mail, schedule information, chat history information, call history information or call voice, bill information, contract information, registration information).
  • exchange information transmission instruction is an instruction to transmit exchange information.
  • the server reception unit 22 receives, for example, interaction information associated with the user identifier.
  • 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 processing unit 23 is, for example, a process of storing the received exchange information in the server storage unit 21 in association with the user identifier.
  • the user identifier is the user identifier of the user who transmitted the exchange information, and the exchange information received corresponding to the exchange information.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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. Note that the timing of acquiring the exchange information is, for example, when the instruction is received or when a predetermined time comes, but the timing does not matter.
  • 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, 1 or 2 or more out of 8 types of exchange information: mail, calendar server schedule information, web conference server schedule information, chat history information, call history information, invoice information, contract information, registration information types of exchange information exist.
  • 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.
  • 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. The judgment as to whether or not the user identifier of the j-th user exists may be considered to be the same as the judgment as to whether or not the j-th exchange information exists.
  • 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.
  • the business card information processing is processing such as obtaining contact information using business card information.
  • 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.
  • 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).
  • 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.
  • the process ends when the power is turned off or when the process ends.
  • 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.
  • the exchange information determination unit 132 acquires one or more pieces of exchange information corresponding to a user identifier from the information server 2, for example, 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.
  • the exchange information determination unit 132 may acquire all the i-th exchange information without determining whether the i-th exchange information satisfies a predetermined condition. In such a case, step S504 is unnecessary.
  • Step S505 The other user information acquisition unit 134 acquires other user information using the i-th exchange information. As described above, there are various possible algorithms for the other user information acquisition unit 134 to acquire other user 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.
  • the questioning unit 133 determines that the other user information acquired in step S505 or the interaction information corresponding to the other user information satisfies a predetermined question condition
  • the questioning unit 133 inquires of the user. I judge.
  • the question conditions are, for example, that the exchange information is not of a specific type of exchange information and that the exchange information is of a specific type of exchange information.
  • the question condition is, for example, that the character string possessed by the interaction information or other user information contains a specific term, or that the character string possessed by the exchange information or other user information does not contain a specific term.
  • 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.
  • the interaction relationship accumulation unit 135 accumulates the interaction relationship information acquired in step S510.
  • the storage destination of the interaction relationship information is, for example, the interaction relationship storage unit 114 of the interaction management device 1, but may be another device.
  • 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.
  • 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 another 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.
  • 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.
  • step S410 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.
  • 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. .
  • the server processing section 23 accumulates the exchange information in the server storage section 21 .
  • 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 .
  • 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 .
  • 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.
  • FIG. 1 A conceptual diagram of the exchange management system A is shown in FIG. 1
  • the user information management table is a table for managing user 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”, “telephone number”, and the like.
  • "ID” is information for identifying a record.
  • "user information” includes user attributes such as a department identifier, title, telephone number, FAX number, and URL. Having a value is preferred.
  • 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”.
  • 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.
  • the "type identifier” is "mail (eg, “1")”, “calendar (eg, “2”)”, “web conference (eg, “3")", “business card (eg, "4")”. "Chat (e.g. '5')” "Phone (e.g. '6')” "Bill (e.g. '7')” "Contract (e.g. '8')” 'Registration (e.g. '9') )”. "Additional information” is additional information in the exchange relationship information, such as mail-related information, business card exchange-related information, calendar-related information, web conference-related information, chat strings, call strings, and billing 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.
  • 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.
  • 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”.
  • the exchange information determination unit 132 determines all target bill information or contract information as exchange information.
  • 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, The web conference server 2 (3) that manages the above web conference schedule information of each user, the chat server 2 (4) that manages chat history information of one or more users, and manages call history information of one or more users.
  • a telephone server 2 (5) that manages bill information of one or more users
  • a bill management server 2 (6) that manages bill information of one or more users
  • a contract management server 2 (7) that manages contract information of one or more users
  • 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.
  • 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.
  • 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 4 is an example of accumulating exchange relationship information when chat history information is received.
  • Specific example 5 is an example of accumulating exchange relationship information when call history information is received.
  • Specific example 6 is an example of accumulating exchange relationship information when bill information is received.
  • Specific example 7 is an example of accumulating exchange relationship information when contract information is received.
  • Specific example 8 is an example of accumulating exchange relationship information when registration information is received.
  • the processing unit 13 acquires the first user identifier "1001" from the user information management table.
  • 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).
  • exchange information determination unit 132 has obtained mails 1601, 1602, etc. shown in FIG.
  • 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> Aiko Yamamoto ⁇ e-mail address> ay@s.co.jp ⁇ company name> from the user information management table of FIG. S Co., Ltd.”.
  • 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.
  • the other user information acquisition unit 134 may acquire other user information from the mail using the character string of the signature portion.
  • 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.
  • 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".
  • 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.
  • 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
  • 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.
  • Ichiro Yamada's terminal device 3 receives the screen information and outputs the screen shown in FIG.
  • 1701 is the user information of other users who have exchanges with Ichiro Yamada.
  • 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.
  • 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 .
  • the business card creation screen is a screen for creating contact information.
  • 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".
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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".
  • the other user information acquisition unit 134 acquires the received business card information.
  • 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).
  • 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.
  • the chat management table is a table in which chat history information, which is information on chats between two or more users, is managed.
  • the chat management table is a table for managing one or more records having "ID”, "user identifier", "date and time”, and "chat character string”.
  • ID is an identifier that identifies a series of chat interactions.
  • User identifier is the ID of the user who entered the chat string.
  • Date and time is the date and time when the chat string was received.
  • “Chat string” is a string entered by the user.
  • the exchange information determination unit 132 acquires chat history information corresponding to the user identifier "1001" from the chat server.
  • the exchange information determination unit 132 acquires chat history information corresponding to the user identifier "1002" from the chat server.
  • the exchange information determination unit 132 determines that business terms such as "thank you for your help", "meeting", and "corporation" appear five or more times in the acquired chat history information. Business exchanges also meet, judge.
  • the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "chat” and accumulates the other user information in the storage unit 11.
  • the other user information acquisition unit 134 acquires from the storage unit 11, for example, the type identifier "chat" corresponding to the chat server that has transmitted the chat history information.
  • the storage unit 11 stores type identifiers in association with information identifying each information server 2 (for example, IP address, URL, etc.).
  • the other user information is, for example, "1002, 1003, chat".
  • the other user information may be, for example, the record structure shown in FIG.
  • the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
  • the call management table is a table in which call history information, which is information on telephone calls made between two or more users, is managed.
  • the call management table is a table for managing one or more records having "ID", "user identifier", "date and time”, and "call character string”.
  • ID is an identifier that identifies an interaction in a series of calls.
  • User Identifier is the telephone number of the user who made the voice corresponding to the call string.
  • “Date and time” is the date and time when the voice corresponding to the call character string was received.
  • a “call character string” is a character string obtained by performing speech recognition processing on the voice uttered by the user. Note that the telephone server stores voice, and the exchange management device 1 that receives the voice may perform voice recognition processing on the voice and acquire a call character string.
  • the user identifier acquisition unit 131 acquired the telephone number "03-1111-1122" paired with the first user identifier "1001" from the user information management table.
  • the exchange information determination unit 132 acquires call history information corresponding to the telephone number "03-1111-1122" from the telephone server.
  • the user identifier acquisition unit 131 acquired the telephone number "03-2222-2222" paired with the second user identifier "1002" from the user information management table.
  • the exchange information determination unit 132 acquires call history information corresponding to the telephone number "03-2222-2222" from the telephone server.
  • the exchange information determination unit 132 refers to the dictionary of FIG. Get the number of terms.
  • the other user information acquisition unit 134 acquires the user identifier "1003" paired with the telephone number "03-3333-3333” from the user information management table of FIG.
  • the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "telephone” and accumulates the other user information in the storage unit 11.
  • the other user information is, for example, "1002, 1003, telephone".
  • the other user information may be, for example, the record structure shown in FIG.
  • the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
  • the other user information acquisition unit 134 acquires the user identifiers constituting the other user information from the call history without referring to the user information management table. Get from information.
  • the bill management table shown in FIG. 21 is stored in the server storage unit 21 of the bill management server 2(5).
  • the bill management table is a table in which bill information sent from a sender user to a recipient user is managed.
  • the bill management table manages one or more records having "ID”, "sender user identifier”, “destination user identifier”, “sender company name”, “destination company name”, “billing amount”, and "invoice image”. It is a table that "ID” is identification information corresponding to one invoice.
  • “Sender User Identifier” is the ID of the user who sent the invoice.
  • “Destination User Identifier” is the ID of the user who received the invoice.
  • “Sender company name” is the company name to which the sender user belongs.
  • “Destination company name” is the name of the company to which the destination user belongs.
  • the interaction information determination unit 132 acquires interaction information paired with the user identifier "1001" acquired by the user identifier acquisition unit 131 from the invoice management server 2 (5).
  • the exchange information determination unit 132 acquires the sender user identifier "1001" and the recipient user identifier "1002" of the exchange information.
  • the exchange information determination unit 132 determines that the set of the user identifier "1001" and the user identifier "1002" already exists in the table of FIG. In other words, the exchange information determination unit 132 determines not to use the exchange information acquired from the invoice management server 2(5).
  • the interaction information determination unit 132 acquires interaction information paired with the user identifier "1002" acquired by the user identifier acquisition unit 131 from the invoice management server 2 (5).
  • the exchange information determination unit 132 acquires the sender user identifier "1002" and the recipient user identifier "1003" of the exchange information.
  • the interaction information determination unit 132 determines that the set of the user identifiers "1002" and "1003" does not exist in the table of FIG. In other words, the exchange information determination unit 132 determines to use the exchange information acquired from the invoice management server 2(5).
  • the other user information acquisition unit 134 acquires the user identifier "1002" and the user identifier "1003".
  • the interaction relationship storage unit 135 acquires from the storage unit 11 the type identifier "invoice” corresponding to the invoice management server 2 (5).
  • the interaction relationship accumulation unit 135 pairs the user identifier “1002”, the user identifier “1003”, and the type identifier “bill” and accumulates the other user information in the storage unit 11 .
  • the other user information is, for example, "1002, 1003, invoice”.
  • the other user information may be, for example, the record structure shown in FIG.
  • the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
  • the contract management table shown in FIG. 22 is stored in the server storage unit 21 of the contract management server 2 (6).
  • the contract management table is a table in which contract information indicating a contract between a user of a contracting party "A" and a user of a contracting party "B" is managed.
  • the contract management table is a table for managing one or more records having "ID”, "user identifier”, “user identifier”, "company name”, “company name”, “contract amount”, and "text of contract”. .
  • ID is identification information corresponding to one contract.
  • a User Identifier is the ID of the user of "A” who is a party to the contract.
  • “B user identifier” is the ID of the user of "B", the party to the contract.
  • Party A company name is the company name of Party A.
  • “Company name of B” is the name of the company of B.
  • the interaction information determination unit 132 acquires interaction information paired with the user identifier "1001" acquired by the user identifier acquisition unit 131 from the contract management server 2 (6).
  • the exchange information determination unit 132 acquires the sender user identifier "1001" and the recipient user identifier "1002" of the exchange information.
  • the exchange information determination unit 132 determines that the set of the user identifier "1001" and the user identifier "1002" already exists in the table of FIG. That is, the exchange information determination unit 132 determines not to use the exchange information acquired from the contract management server 2 (6).
  • the interaction information determination unit 132 acquires interaction information paired with the user identifier "1002" acquired by the user identifier acquisition unit 131 from the contract management server 2 (6).
  • the exchange information determination unit 132 acquires the sender user identifier "1002" and the recipient user identifier "1003" of the exchange information.
  • the interaction information determination unit 132 determines that the set of the user identifiers "1002" and "1003" does not exist in the table of FIG. That is, the exchange information determination unit 132 determines to use the exchange information acquired from the contract management server 2 (6).
  • the other user information acquisition unit 134 acquires the user identifier "1002" and the user identifier "1003".
  • the interaction relationship storage unit 135 acquires from the storage unit 11 the type identifier "contract” corresponding to the contract management server 2 (6).
  • the interaction relationship accumulation unit 135 pairs the user identifier “1002”, the user identifier “1003”, and the type identifier “contract” and accumulates the other user information in the storage unit 11 .
  • the other user information is, for example, "1002, 1003, contract”.
  • the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
  • the registration management table is a table in which registration information of each of one or more users who have applied for participation in one or more events is managed.
  • the registration management table is a table for managing one or more records having "ID”, "name”, “company name”, “position”, and "event identifier”. “ID” is information for identifying a record.
  • the “event identifier” is information that identifies the event for which the user applied for participation.
  • the event management table shown in FIG. 24 is stored in the server storage unit 21 of the registration server 2 (7).
  • the event management table is a table for managing one or more pieces of event information.
  • the event management table is a table for managing one or more records having "ID”, "event identifier”, "title”, and “date and time”. “ID” is information for identifying a record. "Title” is the title of the event.
  • the processing unit 13 acquires registration information contained in the registration management table (FIG. 23) from the registration server 2 (7). Also, the processing unit 13 acquires event information contained in the event management table (FIG. 24) from the registration server 2 (7).
  • the other user information acquisition unit 134 searches the user information management table of FIG. 8 using the representative “Jiro Aoki” and the company name “Y company” included in the event information as keys, and acquires the user identifier “1003”. do.
  • the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "event” and accumulates the other user information in the storage unit 11.
  • the other user information is, for example, "1002, 1003, event”.
  • the other user information may be, for example, the record structure shown in FIG.
  • the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the second and subsequent users.
  • 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.
  • 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.
  • the software that implements the exchange management device 1 in the present embodiment is the following program.
  • this program comprises: a computer, an exchange information determination unit for acquiring exchange information from a storage unit that stores one or more pieces of exchange information that are information related to exchanges between two or more users; One user identifier corresponding to the exchange information acquired by the determination unit, and another user identifier different from the one user identifier, the other user including the other user identifier corresponding to the exchange information acquired by the exchange information determination unit
  • exchange relationship information indicating relationships between users is acquired and accumulated.
  • an exchange management apparatus that acquires and accumulates relationship information between organizations and individuals or between organizations using one or more exchange information will be described.
  • the relationship information relating to the relationship between individuals in the first embodiment may be acquired and accumulated.
  • the exchange relationship information may be referred to as relationship information.
  • an exchange management device that acquires and accumulates relational information using only exchange information that satisfies a predetermined condition (for example, business exchange information) from two or more pieces of exchange information will be described.
  • an exchange management apparatus that inquires of a user whether or not to accumulate relational information and accumulates the relational information when the answer is yes will be described.
  • an exchange management device that also accepts and accumulates business card information will be described. Also, an exchange management apparatus that acquires and accumulates related information using business card information when business card information is also received will be described.
  • the conceptual diagram of the exchange management system B in this embodiment is the same as FIG. 1 except for the reference numerals of the exchange management device 4.
  • the exchange management system B includes an exchange management device 4 , one or more information servers 2 , and one or more terminal devices 3 .
  • the exchange management device 4 is a device that acquires and accumulates related information. It is preferable that the exchange management device 4 includes all the processes performed by the exchange management device 1 . In other words, it is preferable that the exchange management device 4 has all the components of the exchange management device 1 .
  • the exchange management device 1 is usually a so-called server, such as a cloud server or an ASP server. It should be noted that the type of the exchange management device 4 does not matter. Further, the details of the interaction relationship information will be described later.
  • the exchange management device 4 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. 25 is a block diagram of the exchange management device 4 that constitutes the exchange management system B in this embodiment.
  • the exchange management device 4 includes a storage section 41 , a reception section 42 , a processing section 43 and a transmission section 44 .
  • the storage unit 41 includes a target information storage unit 411, a business card information storage unit 112, a domain information storage unit 113, and an interaction relationship storage unit 414.
  • the target information storage section 411 includes a user information storage section 111 and an organization information storage section 4111 .
  • the reception unit 42 includes a business card information reception unit 121 .
  • Processing unit 43 includes user identifier acquisition unit 131 , interaction determination unit 431 , question unit 133 , relationship acquisition unit 432 , relationship accumulation unit 433 , change determination unit 136 , and interaction processing unit 137 .
  • the various types of information are stored in the storage unit 41 that constitutes the exchange management device 4 .
  • the various types of information are, for example, target information, business card information, domain information, one or more types of interaction information, relationship information, and various screen information, which will be described later.
  • the exchange information here is information related to exchanges between two or more parties. It is preferable that the two or more types of exchange information in the storage unit 41 are information acquired from different information servers 2 respectively. Moreover, when the storage unit 41 is included in the information server 2 , it is preferable that two or more types of exchange information exist in different storage units 41 .
  • the target information storage unit 411 stores one or more target information.
  • the target information is information to be searched when trying to acquire accurate relational information.
  • the target information is user information or organization information described later.
  • the target information has a target identifier and one or more target attribute values.
  • a target identifier is information that identifies a target.
  • a target is a user or an organization.
  • a subject identifier is a user identifier or an organizational identifier.
  • a target attribute value is a user attribute value or an organization attribute value.
  • the organization attribute value is organization information.
  • Organization attribute values are, for example, organization name (eg, company name), address, telephone number, and representative information.
  • the representative information is, for example, the name of the representative, the e-mail address of the representative, and the telephone number of the representative.
  • the organization information storage unit 4111 stores one or more pieces of organization information.
  • the organization information is information about the organization.
  • the organization information includes, for example, an organization identifier, company name, company phone number, company address, and company representative information.
  • the organization identifier is information for identifying an organization, such as an organization ID or company name.
  • the representative information includes, for example, the name of the representative, the e-mail address of the representative, and the telephone number of the representative.
  • the organization information is preferably associated with an organization identifier.
  • the organization information storage unit 4111 is appropriately called an organization DB.
  • the user information storage unit 111 is appropriately referred to as a user DB.
  • the exchange relationship storage unit 414 stores one or more pieces of relationship information.
  • Relationship information is information about the relationship between two parties.
  • the two parties are preferably an organization and an organization or an organization and an individual (user), but they may be an individual and an individual. It can be said that the relationship information is information indicating that there is a relationship between two parties.
  • the relationship information may be any information that can identify the interaction relationship between the two.
  • Relationship information is information that associates two target identifiers.
  • the two target identifiers are the first identifier and the second identifier.
  • a subject identifier is an organization identifier that identifies an organization or a user identifier that identifies an individual.
  • the relationship information is, for example, relationship information between organizations and relationship information between organizations and individuals. However, the relationship information may be relationship information between individuals.
  • the relationship information between organizations is, for example, information having two organization identifiers, organization information of the second organization corresponding to the organization identifier of the first organization, organization identifier of the first organization and organization of the second organization. Information that has information and information that has organizational information of two organizations.
  • the relationship information between an organization and an individual is, for example, information having an organization identifier and a user identifier, information having an organization identifier and user information, information having an organization information and a user identifier, and information having an organization information and a user information. be.
  • the relationship information between individuals is the exchange relationship information described in the first embodiment.
  • the receiving unit 42 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 receiver 42 may be the same as the receiver 12 .
  • the processing unit 43 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 432, the question unit 133, the relationship acquisition unit 432, the relationship storage unit 433, the change determination unit 136, and the interaction processing unit 137.
  • the exchange determination unit 431 acquires one or more pieces of exchange information from the storage unit 41 .
  • the storage unit 41 here may be the server storage unit 21 of the information server 2 .
  • the alternating current determining section 431 may be the same as the alternating current determining section 132 .
  • the exchange determination unit 431 acquires two or more types of exchange information from the storage unit 41, for example.
  • the exchange determination unit 431 acquires, for example, exchange information that satisfies predetermined conditions from the storage unit 41 .
  • the relationship acquisition unit 432 acquires relationship information in which the object identifiers of the two parties corresponding to the interaction information acquired by the interaction determination unit 431 are associated.
  • Each subject identifier of the two parties is a first identifier and a second identifier.
  • the first identifier or second identifier is an organization identifier or a user identifier. At least one of the first identifier or the second identifier is preferably an organizational identifier, but both may be user identifiers.
  • the processing of the exchange determination unit 431 when both are user identifiers may be the same processing as that of the other user information acquisition unit 134 . Also, such processing is described in the first embodiment.
  • the organization identifier may be any information that can identify the organization.
  • the user identifier should be information that can identify an individual.
  • the relationship acquisition unit 432 searches the target information storage unit 411 using the character string included in the interaction information determined by the interaction determination unit 431 or the target identifier corresponding to the interaction information, and uses the search result to obtain the relationship information. get.
  • the relationship acquisition unit 432 acquires, for example, relationship information that associates the first identifier with the second identifier corresponding to the business card information.
  • the relationship acquisition unit 432 acquires relationship information using communication system information. Also, the relationship acquisition unit 432 acquires relationship information using non-communication system information.
  • relationship acquisition unit 432 For each type of exchange information will be described below. It should be noted that the operation when the relationship acquisition unit 432 acquires the relationship information regarding the relationship between individuals may be the same as the operation of the other user information acquisition unit 134, so the description is omitted here.
  • exchange information is call history information (1-1) When forming relationship information between an organization and an individual
  • the relationship acquisition unit 432 acquires the telephone number associated with the call history information determined by the exchange information determination unit 132.
  • a telephone number is, for example, a company's telephone number.
  • the relationship acquisition unit 432 acquires, for example, the company name or organization identifier paired with the telephone number from the organization DB.
  • the relationship acquisition unit 432 configures, for example, relationship information that associates the user identifier acquired by the user identifier acquisition unit 131 with the acquired company name or organization identifier.
  • the user identifier here is, for example, information for identifying the user who made a call to one company.
  • the relationship acquisition unit 432 may search the user DB using the telephone number associated with the call history information as a key to acquire the user identifier.
  • the phone number in such a case is the phone number of the user who made the call.
  • the relationship acquiring unit 432 morphologically analyzes a character string included in the call history information (for example, "Hello, is it A Corporation? !”), and from the analysis result, A company name (for example, “A Corporation”) may be obtained.
  • the relationship acquisition unit 432 searches the organization DB using the company name included in the call history information as a key, acquires an organization identifier paired with the company name, and obtains the organization identifier. and the acquired user identifier may be configured. (1-2) When obtaining relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, two telephone numbers associated with the call history information determined by the exchange information determination unit 132. Next, the relationship acquisition unit 432 acquires, for example, a company name or organization identifier paired with one telephone number from the organization DB. Also, the relationship acquisition unit 432 acquires, for example, a company name or an organization identifier paired with another telephone number from the organization DB. Next, the relationship acquisition unit 432 configures relationship information that associates, for example, two company names or two organization identifiers.
  • the relationship acquiring unit 432 morphologically analyzes the character string included in the call history information (for example, "Hello, is it A Corporation? !”), and from the analysis result, A company name (for example, “A Corporation”) may be acquired.
  • the method by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the call history information does not matter.
  • the relationship acquisition unit 432 obtains, for example, a billing person in charge identifier (corresponding to a billing person's user identifier (e.g., user ID, name)) and a billing person in charge identifier included in the invoice information determined by the interaction information determination unit 132. (corresponding to the billing user identifier). Next, the relationship acquisition unit 432 searches the user DB using the billing user identifier as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the user identifier of the billing party with the company name of the billing party.
  • a billing person in charge identifier corresponding to a billing person's user identifier (e.g., user ID, name)
  • a billing person in charge identifier included in the invoice information determined by the interaction information determination unit 132 corresponding to the billing user identifier.
  • the relationship acquisition unit 432 searches the user DB using the billing user identifier as a key, and acquires the company name.
  • the relationship acquisition unit 432 searches the user DB using the user name and company name of the invoicing party associated with the invoice information as keys, acquires the user identifier of the invoicing party, and obtains the user identifier and the invoicing party. You may constitute the relationship information which matches with the company name of.
  • the relationship acquisition unit 432 may acquire the company name of the billing party included in the invoice information, and configure relationship information that associates the company name with the user identifier of the billing party.
  • the relationship acquisition unit 432 may search the organization DB using the acquired company name or the like as a key, acquire an organization identifier, and configure relationship information that associates the organization identifier with the billing user identifier. (2-1-2) When configuring relationship information between billing user and billing organization
  • the relationship acquisition unit 432 acquires the user identifier of the billing party (for example, user ID, name) and the user identifier of the billing party associated with the invoice information determined by the exchange information determination unit 132 .
  • the relationship acquisition unit 432 searches the user DB using the user identifier of the invoicing party as a key, and acquires the company name.
  • the relationship acquisition unit 432 configures relationship information that associates the user identifier of the invoicing party with the company name of the invoicing party.
  • the relationship acquisition unit 432 searches the user DB using the user name and company name of the billing party associated with the bill information as keys, acquires the user identifier of the billing party, You may constitute the relationship information which matches with the company name of.
  • the relationship acquisition unit 432 may acquire the company name of the billing party included in the invoice information, and configure relationship information that associates the company name with the user identifier of the billing party.
  • the relationship acquisition unit 432 may search the organization DB using the acquired company name or the like as a key, acquire an organization identifier, and configure relationship information that associates the organization identifier with the billing user identifier. (2-2) When configuring relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, the billing company name and the billing company name included in the invoice information. Next, the relationship acquisition unit 432 configures, for example, relationship information that associates the two company names.
  • the relationship acquisition unit 432 acquires the user identifier of the billing party associated with the invoice information determined by the interaction information determination unit 132, and obtains the user identifier of the billing party. may be used as a key to search the user DB to obtain the company name.
  • the relationship acquisition unit 432 searches the organization DB using the acquired two company names (for example, company name and telephone number) as keys, acquires the organization identifiers corresponding to the two company names, etc.
  • Relational information that associates the two organization identifiers may be configured.
  • relationship acquisition unit 432 acquires the user identifier of the billing party or the billing party, the company name of the billing party or the billing party, etc., using the invoice information.
  • exchange information is contract information (3-1) When constituting relationship information between an organization and an individual
  • the relationship acquisition unit 432 acquires, for example, two person-in-charge identifiers (corresponding to user identifiers) included in the contract information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 acquires, for example, a company name paired with one user identifier from the user DB. Next, the relationship acquisition unit 432 configures relationship information that associates the company name with another user identifier, for example.
  • the relationship obtaining unit 432 may obtain the company name included in the contract information (for example, the company name corresponding to Party A or the company name corresponding to Party B). Further, when acquiring a company name, the relationship acquiring unit 432 acquires from the user DB a company name paired with the other user identifier from two or more company names included in the contract information, A company name that is not a name may be adopted as the company name that constitutes the related information. (3-2) When acquiring relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, two user identifiers included in the contract information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 acquires, for example, the company name paired with each of the two user identifiers from the user DB. Next, the relationship acquisition unit 432 configures, for example, relationship information that associates the two company names.
  • the relationship acquiring unit 432 may acquire two company names (for example, company names corresponding to A and B) included in the contract information.
  • relationship acquisition unit 432 acquires the company name, user identifier, or the like using the contract information may be used.
  • exchange information is registration information (4-1) When forming relationship information between an organization and an individual When configuring relationship information
  • the relationship acquisition unit 432 acquires the registrant identification information (corresponding to the user identifier) and the organizer identification information (corresponding to the user identifier) included in the registration information determined by the exchange information determining unit 132. Next, the relationship acquisition unit 432 searches the user DB using the organizer identification information as a key and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the registrant identification information with the company name.
  • the relationship acquisition unit 432 searches the user DB using the name and company name of the registrant included in the registration information as keys, and acquires the user identifier. Also good.
  • the relationship acquisition unit 432 may acquire the company name of the organizer included in the registration information. (4-1-2) When configuring relationship information between the organization of registrants for the event and the person in charge of the event, etc.
  • the relationship acquisition unit 432 acquires the registrant's company name and organizer identification information (corresponding to the user identifier) included in the registration information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the company name with the organizer identification information.
  • the relationship acquiring unit 432 may acquire the company name paired with the name and telephone number included in the registration information from the user DB.
  • the relationship acquisition unit 432 may search the user DB using the organizer's name, telephone number, etc. included in the registration information as keys, and acquire the user identifier. (4-2) When obtaining relationship information between organizations
  • the relationship acquisition unit 432 acquires the registrant's company name and the sponsor's company name included in the registration information determined by the exchange information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the two company names.
  • any method may be used by which the relationship acquisition unit 432 acquires the company name, user identifier, etc. using the registration information.
  • exchange information is inquiry information (5-1) When forming relational information between an organization and an individual (5-1-1) When forming relational information between an inquirer and an organization responding to an inquiry
  • the relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as a key to acquire a user identifier. Further, the relationship acquiring unit 432 acquires, for example, the name of the person in charge of the corresponding organization or the user identifier of the person in charge of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the acquired person-in-charge name or the like as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the acquired user identifier with the company name.
  • the relationship acquisition unit 432 may acquire the user identifier of the inquiry information when acquiring the questioner's user identifier.
  • the relationship acquiring unit 432 may acquire the company name of the corresponding organization included in the inquiry information.
  • the relationship acquiring unit 432 may acquire the company name of the corresponding organization included in the inquiry information.
  • the relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as keys, and acquires the company name. Also, the relationship acquisition unit 432 acquires, for example, the name of the person in charge of the corresponding organization and the name of the company included in the inquiry information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the name of the person in charge or the like as a key, and acquires the user identifier. Next, the relationship acquisition unit 432 configures relationship information that associates the acquired company name with the user identifier.
  • the relationship acquisition unit 432 may acquire the questioner's company name included in the inquiry information.
  • the relationship acquiring unit 432 may acquire the user identifier included in the inquiry information. (5-2) When obtaining relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as keys, and acquires the company name. Further, the relationship acquiring unit 432 acquires, for example, the name of the person in charge of the corresponding organization or the user identifier of the person in charge of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the acquired person-in-charge name or the like as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the two acquired company names.
  • the relationship acquisition unit 432 may acquire the questioner's company name included in the inquiry information determined by the interaction information determination unit 132 . Further, when acquiring the company name of the corresponding organization, the relationship acquiring unit 432 may acquire the company name of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 .
  • relationship acquisition unit 432 acquires the company name, user identifier, etc. using the inquiry information.
  • exchange information is sales activity information (6-1) When forming relationship information between organizations and individuals (6-1-1) When acquiring relationship information between sales representatives and sales organizations
  • the relationship acquisition unit 432 acquires, for example, the salesperson information (eg, the name of the salesperson) and the sales customer information (eg, the customer's company name) included in the sales activity information determined by the interaction information determination unit 132. . Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
  • the salesperson information eg, the name of the salesperson
  • the sales customer information eg, the customer's company name
  • the relationship acquisition unit 432 searches the user DB using the salesperson information included in the sales activity information, acquires the user identifier corresponding to the salesperson information, and combines the user identifier with the sales customer information. may be configured to correspond to the relationship information.
  • the relationship acquisition unit 432 searches the user DB using sales customer information (for example, the customer's name and department name), acquires the customer's company name, and acquires relationship information that associates the user identifier with the company name. may be configured. (6-1-2) When acquiring relationship information between the organization of the sales representative and the person in charge of the sales organization
  • the relationship acquisition unit 432 acquires, for example, salesperson information (for example, the company name of the salesperson) and sales customer information (for example, the name of the customer, the company name of the customer, etc.) included in the sales activity information determined by the interaction information determination unit 132. ) and get Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
  • salesperson information for example, the company name of the salesperson
  • sales customer information for example, the name of the customer, the company name of the customer, etc.
  • the relationship acquisition unit 432 searches the user DB using the salesperson information included in the sales activity information, acquires the company name corresponding to the salesperson information, and combines the company name with the sales customer information. may be configured to correspond to the relationship information.
  • the relationship acquisition unit 432 searches the user DB using the sales customer information (for example, the customer's name and department name), acquires the user identifier of the customer, and combines the user identifier with the company name of the salesperson. may be configured to correspond to the relationship information. (6-2) When obtaining relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, salesperson information (eg, salesperson's company name) and sales customer information (eg, customer's company name) included in the sales activity information determined by the interaction information determination unit 132. do. Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
  • salesperson information eg, salesperson's company name
  • sales customer information eg, customer's company name
  • the relationship acquisition unit 432 searches the user DB using, for example, the salesperson information (for example, the name and telephone number of the person in charge) possessed by the sales activity information, and obtains the company name corresponding to the salesperson information. It is also possible to configure relationship information that is acquired and associates the company name with the sales customer information.
  • the salesperson information for example, the name and telephone number of the person in charge
  • the relationship acquisition unit 432 searches the user DB using the sales customer information (for example, the customer's name and department name), acquires the customer's company name, and obtains the relationship that associates the sales representative information with the company name. information may be configured.
  • the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the sales activity information.
  • the exchange information is customer information (7-1) When configuring relationship information between an organization and an individual (7-1-1) When acquiring relationship information between a person in charge and a customer's organization
  • the relationship acquisition unit 432 acquires, for example, the person in charge information (for example, the name of the person in charge) included in the customer information determined by the exchange information determination unit 132 and one or more customer attribute values (for example, the customer's company name). . Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
  • the person in charge information for example, the name of the person in charge
  • customer attribute values for example, the customer's company name
  • the relationship acquisition unit 432 searches the user DB using the person-in-charge information included in the customer information, acquires the user identifier corresponding to the person-in-charge information, and combines the user identifier with one or more customer attribute values. may be configured to correspond to the relationship information.
  • the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's company name, and obtains the person in charge information and the company name. Corresponding relationship information may be configured.
  • the relationship acquisition unit 432 searches the user DB using the person-in-charge information (for example, name and phone number of the person-in-charge) included in the customer information as a key, acquires a user identifier, and acquires the user identifier and one or more customer attributes. You may configure the relationship information which associates with a value (for example, a customer's company name). (7-1-2) When acquiring relationship information between the organization of the person in charge and the customer
  • the relationship acquisition unit 432 acquires the person in charge information (eg, the company name of the salesperson) included in the customer information determined by the interaction information determination unit 132 and one or more customer attribute values (eg, the customer's name, the customer's company first name). Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
  • the person in charge information eg, the company name of the salesperson
  • customer attribute values eg, the customer's name, the customer's company first name.
  • the relationship acquisition unit 432 searches the user DB using the person-in-charge information included in the customer information, acquires the company name corresponding to the person-in-charge information, and obtains the company name and one or more customer attribute values (for example, the customer's name) may be associated with relational information.
  • the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's user identifier, and acquires the user identifier and the company name of the person in charge. You may comprise the relationship information which matches. (7-2) When obtaining relationship information between organizations
  • the relationship acquisition unit 432 acquires the person-in-charge information (for example, the company name of the salesperson) and one or more customer attribute values (for example, the company name of the customer) included in the customer information determined by the interaction information determination unit 132. get. Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
  • the person-in-charge information for example, the company name of the salesperson
  • customer attribute values for example, the company name of the customer
  • relationship acquisition unit 432 searches the user DB using, for example, the person in charge information (for example, the name and phone number of the person in charge) possessed by the customer information, acquires the company name corresponding to the person in charge information, Relationship information may be configured to associate the company name with one or more customer attribute values.
  • the person in charge information for example, the name and phone number of the person in charge
  • Relationship information may be configured to associate the company name with one or more customer attribute values.
  • the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's company name, and obtains the person in charge information and the company name. Corresponding relationship information may be configured.
  • relationship acquisition unit 432 may search the organization DB using the acquired company name or the like, acquire an organization identifier, and configure relationship information using the organization identifier.
  • any method may be used by which the relationship acquisition unit 432 acquires an organization identifier, a user identifier, or the like using customer information.
  • exchange information is order information (8-1) When forming relationship information between an organization and an individual (8-1-1) When forming relationship information between an orderer and an organization that received an order
  • the relationship acquisition unit 432 acquires, for example, orderer information (eg, name, telephone number) and order destination information (eg, company name) included in the order information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
  • orderer information eg, name, telephone number
  • order destination information eg, company name
  • the relationship acquisition unit 432 may search the user DB using the orderer information included in the order information, acquire the user identifier, and configure relationship information that associates the user identifier with the orderer information.
  • the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the orderer information. Relationship information may be configured.
  • the relationship acquisition unit 432 may search the organization DB using the acquired company name, acquire an organization identifier, and configure relationship information that associates the organization identifier with the orderer information. (8-1-2) When configuring relationship information between the orderer's organization and the person in charge of the organization that received the order
  • the relationship acquisition unit 432 acquires, for example, orderer information (for example, company name) and order recipient information (for example, the name of the person in charge of the order recipient, company name) included in the order information determined by the interaction information determination unit 132. do. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
  • orderer information for example, company name
  • order recipient information for example, the name of the person in charge of the order recipient, company name
  • the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information.
  • orderer information for example, name and telephone number
  • the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information. may be configured.
  • the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name of the person who received the order, the company name), acquires the user identifier, and associates the user identifier with the orderer information. Relationship information may be configured.
  • the relationship acquisition unit 432 may search an organization DB using the acquired company name, acquire an organization identifier, and configure relationship information that associates the organization identifier with order destination information. (8-2) When acquiring relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, orderer information (eg, company name) and order destination information (eg, company name) included in the order information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
  • orderer information eg, company name
  • order destination information e.g, company name
  • the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information.
  • orderer information for example, name and telephone number
  • the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information. may be configured.
  • the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the orderer information. Relationship information may be configured.
  • the relationship acquisition unit 432 searches the organization DB using the two acquired company names (the name of the orderer's company and the name of the company to which the order is placed), acquires two organization identifiers, and obtains the two organization identifiers. It is also possible to configure relationship information that associates two organization identifiers.
  • the relationship acquisition unit 432 uses the employment information to compose relationship information between the applicant and the organization to which the applicant applies.
  • the relationship acquisition unit 432 acquires, for example, applicant information (eg, name) and applicant information (eg, company name of the applicant) contained in the employment information determined by the exchange information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the applicant information with the applicant information.
  • applicant information eg, name
  • applicant information eg, company name of the applicant
  • the relationship acquisition unit 432 searches the user DB using the applicant information (for example, name and telephone number) included in the employment information, acquires the user identifier, and associates the user identifier with the applicant information. may be configured.
  • the relationship acquisition unit 432 searches the user DB using the applicant information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the applicant information. Relationship information may be configured.
  • the relationship acquisition unit 432 searches the organization DB using the applicant information (for example, the company name and telephone number of the applicant), acquires the organization identifier, and associates the organization identifier with the applicant information. information may be configured.
  • relationship acquisition unit 432 acquires an organization identifier, a user identifier, or the like using employment information.
  • exchange information is pamphlet acquisition information
  • the relationship acquisition unit 432 uses the pamphlet acquisition information to compose relationship information between the pamphlet acquirer and the pamphlet-related organization.
  • the relationship acquisition unit 432 acquires, for example, acquirer information (eg, name) contained in the pamphlet acquisition information determined by the interaction information determination unit 132 and organization information (eg, company name) relating to the organization providing the pamphlet. Next, the relationship acquisition unit 432 configures relationship information that associates the acquirer information with the organization information.
  • acquirer information eg, name
  • organization information eg, company name
  • the relationship acquisition unit 432 may search the user DB using acquirer information (eg, name and phone number), acquire a user identifier, and configure relationship information that associates the user identifier with organization information. good.
  • acquirer information eg, name and phone number
  • the relationship acquisition unit 432 searches the user DB using information on the person in charge of the company providing the pamphlet included in the organization information (for example, the name and telephone number of the person in charge), acquires the company name, and obtains the company name. It is also possible to configure relationship information that correlates with acquirer information.
  • the relationship acquisition unit 432 searches the organization DB using organization information (for example, company name, telephone number), acquires an organization identifier, and configures relationship information that associates the organization identifier with acquirer information.
  • organization information for example, company name, telephone number
  • the relationship acquisition unit 432 uses the expense information to compose relationship information between the applicant and the organization that processes the expense.
  • the relationship acquisition unit 432 acquires, for example, applicant information (eg, name) included in the expense information determined by the exchange information determination unit 132 and organization information (eg, company name) related to the organization that handles expense processing. Next, the relationship acquisition unit 432 configures relationship information that associates the applicant information and the organization information.
  • applicant information eg, name
  • organization information eg, company name
  • the relationship acquisition unit 432 searches the user DB using the applicant information (eg, name, phone number), acquires the user identifier, and configures relationship information that associates the user identifier with the organization information. good.
  • applicant information eg, name, phone number
  • the relationship acquisition unit 432 searches the user DB using the permitter information (for example, the permitter's name and email address) that the organization information has, acquires the company name, and combines the company name and the applicant information.
  • the permitter information for example, the permitter's name and email address
  • Corresponding relationship information may be configured.
  • the relationship acquisition unit 432 searches the organization DB using organization information (for example, company name and phone number), acquires an organization identifier, and configures relationship information that associates the organization identifier and applicant information. Also good.
  • organization information for example, company name and phone number
  • the relationship acquisition unit 43 acquires the organization identifier, the user identifier, etc. using the expense information.
  • exchange information is questionnaire information (12-1)
  • the relationship acquisition unit 432 acquires, for example, respondent information (eg, name) and implementer information (eg, company name) included in the questionnaire information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 constructs relationship information that associates the respondent information and the implementer information.
  • respondent information eg, name
  • implementer information eg, company name
  • the relationship acquisition unit 432 searches the user DB using respondent information (e.g., name, email address), acquires a user identifier, and composes relationship information that associates the user identifier with the executor information. Also good.
  • respondent information e.g., name, email address
  • the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and email address of the person in charge), acquires the company name, and acquires relationship information that associates the company name with the respondent information. may be configured.
  • the relationship acquisition unit 432 searches the organization DB using the executor information (eg, company name, telephone number), acquires the organization identifier, and configures relationship information that associates the company name and the organization identifier. Also good. (12-1-2) When configuring relationship information between the organization of the respondent to the questionnaire and the person in charge of the organization conducting the questionnaire
  • the relationship acquisition unit 432 acquires, for example, respondent information (for example, company name to which the respondent belongs) and implementer information (for example, the name of the person in charge) included in the questionnaire information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 constructs relationship information that associates the respondent information and the implementer information.
  • respondent information for example, company name to which the respondent belongs
  • implementer information for example, the name of the person in charge
  • the relationship acquisition unit 432 searches the user DB using respondent information (for example, name and email address), acquires a company name, and composes relationship information that associates the company name with the executor information. Also good.
  • respondent information for example, name and email address
  • the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and email address of the person in charge), acquires the user identifier, and acquires the relationship information that associates the user identifier with the respondent information. may be configured.
  • the relationship acquisition unit 432 searches the organization DB using respondent information (e.g., company name, telephone number), acquires an organization identifier, and configures relationship information that associates the organization identifier with the implementer information. can be (12-2) When acquiring relationship information between organizations
  • the relationship acquisition unit 432 acquires, for example, respondent information (eg company name) and implementer information (eg company name) included in the questionnaire information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
  • respondent information eg company name
  • implementer information eg company name
  • the relationship acquisition unit 432 searches the user DB using the respondent information (for example, the respondent's name and telephone number), acquires the company name, and acquires relationship information that associates the company name with the implementer information. may be configured.
  • the respondent information for example, the respondent's name and telephone number
  • the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and telephone number of the person in charge), acquires the company name, and acquires relationship information that associates the company name with the respondent information. may be configured.
  • relationship acquisition unit 432 acquires the company name of the questionnaire respondent and the company name of the organization implementing the questionnaire, searches the organization DB using the two company names, and acquires two organization identifiers. Then, relationship information may be configured to associate the two organization identifiers.
  • the relationship acquisition unit 432 uses the building entry information to configure relationship information between visitors and related organizations such as buildings.
  • the relationship acquisition unit 432 acquires, for example, visitor information (eg, name) and building information (eg, owner information, such as company name) contained in the admission information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the visitor information with the building information.
  • visitor information eg, name
  • building information eg, owner information, such as company name
  • the relationship acquisition unit 432 may search the user DB using visitor information (eg, name, phone number), acquire a user identifier, and configure relationship information that associates the user identifier with building information. good.
  • visitor information eg, name, phone number
  • the relationship acquisition unit 432 searches the user DB using administrator information (for example, the name and email address of the administrator) included in the building information, acquires the company name, and obtains the company name and visitor information.
  • administrator information for example, the name and email address of the administrator
  • Corresponding relationship information may be configured.
  • the relationship acquisition unit 432 searches the organization DB using building information (eg, owner information, eg, company name), acquires an organization identifier, and associates the organization identifier with visitor information. configure information;
  • building information eg, owner information, eg, company name
  • the relationship acquisition unit 432 uses the check-in information to compose relationship information between the check-in person and the organization related to the spatial information.
  • the relationship acquisition unit 432 acquires, for example, check-in person information (eg, name) and operator information (eg, operator's company name) included in the check-in information determined by the exchange information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the check-in person information with the operator information.
  • check-in person information eg, name
  • operator information eg, operator's company name
  • the relationship acquisition unit 432 searches the user DB using check-in person information (eg, name, phone number), acquires a user identifier, and configures relationship information that associates the user identifier with operator information.
  • check-in person information eg, name, phone number
  • the relationship acquisition unit 432 searches the user DB using operator information (for example, the operator's name and email address), acquires the company name, and associates the company name with the check-in person information. may be configured.
  • operator information for example, the operator's name and email address
  • relationship acquisition unit 432 searches the organization DB using, for example, the operator information (for example, the operator's company name) included in the check-in information determined by the interaction information determination unit 132, acquires an organization identifier
  • Relationship information may be configured to associate the organization identifier and check-in person information.
  • the method by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the check-in information does not matter.
  • the relationship accumulation unit 433 accumulates the relationship information acquired by the relationship acquisition unit 432.
  • the storage destination in which the relationship storage unit 433 stores the relationship information does not matter.
  • the relationship storage unit 433 stores the relationship information in the exchange relationship storage unit 414, but may store the relationship information in an external device (not shown).
  • the relationship accumulation unit 433 accumulates the relationship information only when the result of the inquiry by the question unit 133 is to accumulate the relationship information.
  • the transmission unit 44 transmits various types of information. Various types of information are transmitted, for example, information to the effect that related information has been accumulated, and various types of information corresponding to various information transmission instructions.
  • the transmitting unit 44 for example, transmits one or more related information corresponding to the related information transmission instruction.
  • the transmission unit 44 transmits various kinds of information to the terminal device 3, for example.
  • the storage unit 41, the target information storage unit 411, the exchange relationship storage unit 414, and the organization information storage unit 4111 are preferably non-volatile recording media, but can also be realized with volatile recording media.
  • the process by which information is stored in the storage unit 41 or the like does not matter.
  • information may be stored in the storage unit 41 or the like via a recording medium, or information transmitted via a communication line or the like may be stored in the storage unit 41 or the like.
  • information input via an input device may be stored in the storage unit 41 or the like.
  • the receiving unit 42 is usually realized by wireless or wired communication means, but may be realized by means for receiving broadcast.
  • the processing unit 43, the relationship acquiring unit 432, and the relationship accumulating unit 433 can usually be implemented by a processor, memory, or the like.
  • the processing procedure of the processing unit 43 and the like 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).
  • the processor may be a CPU, MPU, GPU, or the like, and may be of any type.
  • the transmission unit 44 is usually realized by wireless or wired communication means, but may be realized by broadcasting means.
  • Step S2601 The processing unit 43 performs exchange relation information processing.
  • the interaction related information processing is a process of acquiring relationship information using interaction information. An example of the interaction relation information processing will be described with reference to the flowchart of FIG. 27 .
  • step S2601 an example of the interaction relation information processing in step S2601 will be described using the flowchart of FIG. In the flow chart of FIG. 27, description of the same steps as those of the flow chart of FIG. 5 will be omitted.
  • Step S2701 The relationship acquisition unit 432 performs relationship information acquisition processing. An example of related information acquisition processing will be described with reference to the flowchart of FIG. 28 .
  • the relationship storage unit 433 stores one or more pieces of relationship information acquired in step S2701. Note that the relationship storage unit 433 acquires one or more pieces of relationship information from a buffer (not shown), and stores each relationship information in the exchange relationship storage unit 414 .
  • the relational information accumulated by the relational accumulation unit 433 is, for example, relational information between an individual and an organization, and relational information between organizations.
  • the relationship storage unit 433 preferably stores different types of relationship information in different storage areas (for example, different databases, different devices).
  • step S2701 an example of related information acquisition processing in step S2701 will be described using the flowchart of FIG.
  • Step S2801 The relationship acquisition unit 432 substitutes 1 for the counter i.
  • Step S2802 The relationship acquisition unit 432 determines whether there is i-th relationship information that can be acquired using the exchange information to be used. If the i-th relational information exists, go to step S2803; otherwise, return to the higher-level processing.
  • the i-th relational information is either relational information between an organization and an individual, or relational information between organizations. Whether to acquire such relationship information is determined in advance depending on the type of exchange information. Also, there are usually one or two pieces of relationship information between an organization and an individual.
  • Step S2803 The relationship acquisition unit 432 acquires the first identifier using the exchange information to be used.
  • Step S2804 The relationship acquisition unit 432 acquires the second identifier using the exchange information to be used.
  • Step S2805 The relationship acquisition unit 432 constructs relationship information using the first identifier and the second identifier, and temporarily stores it in a buffer (not shown).
  • Step S2806 The relationship acquisition unit 432 increments the counter i by 1. Return to step S2802.
  • the organization information storage unit 4111 stores an organization information management table shown in FIG.
  • the organization information management table is a table for managing one or more pieces of organization information.
  • the organization information here has "organization identifier", "company name” and "telephone number”.
  • the interaction relationship storage unit 414 stores a first relationship management table having the structure shown in FIG.
  • the first relationship management table is a table for managing first relationship information that specifies the relationship between individuals and organizations (here, companies).
  • the first relationship management table manages one or more records having "ID”, "first identifier (user identifier)", “second identifier” and "type”.
  • ID is information for identifying a record.
  • the "first identifier (user identifier)" is the first identifier that constitutes the relationship information, and is a user identifier here.
  • “Secondary identifier" has "company name” and "organization identifier”. Part or all of the "second identifier” is a second identifier that constitutes the relationship information.
  • the second identifier here is "company name”, “organization identifier”, or “company name” and “organization identifier”.
  • “Type” is information specifying the type of exchange information from which the relationship information is acquired. Here, for example, “contract”, “invoice” or “event”.
  • the interaction relationship storage unit 414 stores a second relationship management table having the structure shown in FIG.
  • the second relationship management table is a table for managing second relationship information specifying relationships between organizations.
  • the second relationship management table manages one or more records having "ID”, “first identifier”, “second identifier” and “type”.
  • the "first identifier” and “second identifier” in FIG. 31 respectively have "company name” and "organization identifier”.
  • a specific example 1 is a case of acquiring the first relationship information specifying the relationship between an individual and an organization.
  • Concrete example 2 is a case of acquiring second relational information specifying a relationship between organizations.
  • the processing unit 43 acquires the invoice management table shown in FIG. 22 from the information server 2 (contract management server) that manages contract information, and temporarily stores it in the storage unit 41.
  • FIG. 23 from the information server 2 (registration server) that manages registration information, and temporarily stores it in the storage unit 41.
  • the relationship acquisition unit 432 acquires one or more pieces of first relationship information from the invoice management table (Fig. 21) according to the procedure described above.
  • the relationship acquisition unit 432 adds the type “bill” to each of the acquired four pieces of first relationship information.
  • the relationship accumulation unit 433 determines whether or not each of the four obtained pieces of first relationship information exists in the first relationship management table. Here, it is assumed that the relationship accumulation unit 433 has determined that the four pieces of first relationship information do not exist in the first relationship management table. Then, the relationship accumulation unit 433 accumulates the four pieces of first relationship information and the type "bill" in the first relationship management table.
  • the relationship acquisition unit 432 acquires one or more pieces of first relationship information from the contract management table (Fig. 22) according to the procedure described above.
  • the relationship acquisition unit 432 adds the type “contract” to each of the acquired four pieces of first relationship information.
  • the relationship accumulation unit 433 determines that each of the acquired four pieces of first relationship information exists in the first relationship management table. Then, the relationship accumulation unit 433 detects that each of the four pieces of first relationship information is not associated with the type "contract", and sets the attribute value "type” paired with each of the four pieces of first relationship information to " Add "Contract".
  • the relationship acquisition unit 432 acquires one or more pieces of first relationship information by referring to the registration management table (FIG. 23) and the event management table (FIG. 24) according to the procedure described above.
  • the user DB (FIG. 8) is searched using "name>corporation X" as a key, and the user identifier "1002" is acquired.
  • the relationship acquisition unit 432 searches the organization DB (FIG. 29) using “ ⁇ company name>Y company” as a key, and acquires the organization identifier “C01”. Then, the relationship acquisition unit 432 configures the first relationship information " ⁇ first identifier>1002 ⁇ second identifier> ⁇ company name> Y company ⁇ organization identifier> C01 ⁇ /second identifier>".
  • the user DB (FIG. 8) is searched using "Company Y" as a key, and the user identifier "1003" is obtained.
  • the relationship acquisition unit 432 searches the organization DB (FIG. 29) using " ⁇ company name> Co. Q" as a key, and acquires the organization identifier "C04". Then, the relationship acquisition unit 432 constructs the first relationship information " ⁇ first identifier>1003 ⁇ second identifier> ⁇ company name>Q Inc. ⁇ organization identifier>C04 ⁇ /second identifier>".
  • the relationship acquisition unit 432 configures the first relationship information " ⁇ first identifier>1002 ⁇ second identifier> ⁇ company name>Q Inc. ⁇ organization identifier>C04 ⁇ /second identifier>”. Also, the relationship acquiring unit 432 adds the type “event” to each of the three pieces of first relationship information acquired.
  • the relationship acquisition unit 432 acquires one or more pieces of second relationship information using the invoice management table (Fig. 21) according to the procedure described above.
  • the relationship acquisition unit 432 obtains the two pieces of second relationship information " ⁇ first identifier> ⁇ company name> Co., Ltd.
  • the relationship acquisition unit 432 adds the type “bill” to each of the two pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the organization DB using the company name and acquires the organization identifier.
  • the relationship accumulation unit 433 determines whether or not each of the two pieces of acquired second relationship information exists in the second relationship management table. Here, it is assumed that the relationship accumulation unit 433 determines that the two pieces of second relationship information do not exist in the second relationship management table. Then, the relationship accumulation unit 433 accumulates the two pieces of second relationship information and the type "bill" in the second relationship management table.
  • the relationship acquisition unit 432 acquires one or more pieces of second relationship information using the contract management table (Fig. 22) according to the procedure described above.
  • the relationship acquisition unit 432 obtains the two pieces of second relationship information " ⁇ first identifier> ⁇ company name> Co., Ltd.
  • the relationship acquiring unit 432 adds the type “contract” to each of the two pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the organization DB using the company name and acquires the organization identifier.
  • the relationship accumulating unit 433 determines that the acquired two sets of second relationship information exist in the second relationship management table. Then, the relationship accumulation unit 433 detects that each of the two pieces of second relationship information is not associated with the type "contract", and sets the attribute value "type” paired with each of the four pieces of first relationship information to " Add "Contract".
  • the relationship acquisition unit 432 acquires one or more pieces of second relationship information by referring to the registration management table (FIG. 23) and the event management table (FIG. 24) according to the procedure described above.
  • the relationship acquisition unit 432 uses FIGS. 23 and 24 to obtain the three pieces of second relationship information " ⁇ first identifier> ⁇ company name> ⁇ organization identifier>C02 ⁇ /first identifier> ⁇ Second Identifier> ⁇ Company Name>Company Y ⁇ Organization Identifier>C01 ⁇ /Second Identifier>" " ⁇ First Identifier> ⁇ Company Name>Company Y ⁇ Organization Identifier>C01 ⁇ /First Identifier> ⁇ Second Identifier> > ⁇ Company name> Co., Ltd.
  • the relationship acquiring unit 432 adds the type “event” to each of the three pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the event management table of FIG. 24 using the event identifier of FIG. 23 as a key to acquire the company name. The relationship acquisition unit 432 also searches the organization DB using the company name as a key to acquire an organization identifier.
  • accurate relational information can be obtained and managed using the target information storage unit.
  • the software that implements the exchange management device 4 in this embodiment is the following program.
  • the program comprises: an exchange determination unit that acquires exchange information from a storage unit that stores one or more exchange information that is information related to an exchange between two or more parties; A relationship acquisition unit that acquires relationship information in which a first identifier and a second identifier, which are object identifiers of each of two parties corresponding to the acquired interaction information, are associated with each other, and accumulates the relationship information acquired by the relationship acquisition unit.
  • This is a program for functioning as a relation storage unit.
  • FIG. 32 shows the appearance of a computer that executes the programs described in this specification and realizes the exchange management device 4 and the like of the various embodiments described above.
  • the embodiments described above may be implemented in computer hardware and computer programs running thereon.
  • FIG. 32 is an overview diagram of this computer system 300
  • FIG. 33 is a block diagram of the system 300. As shown in FIG.
  • a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303 and a monitor 304.
  • 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.
  • computer 301 may also include a network card that provides connection to a LAN.
  • a program that causes computer system 300 to execute the functions of exchange management device 4 of the above-described embodiment may be stored in CD-ROM 3101, inserted into CD-ROM drive 3012, and transferred to hard disk 3017. .
  • 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 4 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.
  • the step of transmitting information, the step of receiving information, etc. are performed by hardware. processing) are not included.
  • 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.
  • two or more communication means existing in one device may be physically realized in one medium.
  • each process may be implemented by centralized processing by a single device, or may be implemented by distributed processing by a plurality of devices.
  • the exchange management device 4 has the effect of being able to acquire and manage relational information concerning the connection between two parties using exchange information concerning exchanges, and a server or the like that manages exchange information. is useful as

Abstract

[Problem] Conventional interaction management devices were not able to obtain and manage relationship information pertaining to a connection between two people by using interaction information pertaining to an interaction therebetween. [Solution] The present invention makes it possible to obtain and manage relationship information pertaining to a relationship between two people by using interaction information pertaining to an interaction therebetween, by providing an interaction management device 4 equipped with: an interaction determination unit 431 for obtaining interaction information from a storage unit 41 for storing one or more pieces of interaction information, which is information pertaining to an interaction between two or more people; a relationship acquisition unit 432 for acquiring relationship information which associates a first identifier with a second identifier, which are target identifiers for each of the two people who correspond to the interaction information obtained by the interaction determination unit 431; and a relationship storage unit 433 for storing the relationship information acquired by the relationship acquisition unit 432.

Description

交流管理装置、交流管理方法、およびプログラムAC control device, AC control method, and program
　本発明は、二者以上の間での交流に関する交流情報を用いて、交流に関する情報を管理する交流管理装置等に関するものである。 The present invention relates to an exchange management device or the like that uses exchange information concerning exchanges between two or more parties 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 obtain and manage relationship information, which is information about the connection between two parties, using information about interactions other than the exchange of business cards.
　本第一の発明の交流管理装置は、二者以上の間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流決定部と、交流決定部が取得した交流情報に対応する二者の各々の対象識別子である第一識別子と第二識別子とを対応付けた関係情報を取得する関係取得部と、関係取得部が取得した関係情報を蓄積する関係蓄積部とを具備する交流管理装置である。 The exchange management device of the first invention comprises an exchange determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information related to an exchange between two or more parties, and an exchange determination unit. a relationship acquisition unit that acquires relationship information that associates the first identifier and the second identifier, which are the target identifiers of each of the two parties, corresponding to the exchange information acquired by the relationship acquisition unit, and accumulates the relationship information acquired by the relationship acquisition unit and a relationship storage unit.
　かかる構成により、交流情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 With such a configuration, it is possible to acquire and manage relational information regarding the connection between two parties using exchange information.
　また、本第二の発明の交流管理装置は、第一の発明に対して、格納部に格納されている２以上の交流情報には、２種類以上の交流情報が含まれ、交流決定部は、格納部から、２種類以上の交流情報を取得する請求項１記載の交流管理装置である。 Further, in the exchange management device of the second invention, in contrast to the first invention, the two or more pieces of exchange information stored in the storage unit include two or more types of exchange information, and the exchange determination unit 2. The exchange management device according to claim 1, wherein two or more types of exchange information are acquired from the storage unit.
　かかる構成により、２種類以上の交流情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage relational information relating to the connection between two parties using two or more types of exchange information.
　また、本第三の発明の交流管理装置は、第二の発明に対して、交流決定部は、格納部から、予め決められた条件を満たす交流情報を取得する請求項１または交流管理装置である。 In addition, in the exchange management device of the third invention, in contrast to the second invention, the exchange determination unit acquires from the storage unit the exchange information that satisfies a predetermined condition. be.
　かかる構成により、適切な交流情報のみを用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage relational information regarding the connection between two parties using only appropriate exchange information.
　また、本第四の発明の交流管理装置は、第三いずれか１つの発明に対して、関係情報を蓄積するか否かをユーザに問い合わせる質問部をさらに具備し、関係蓄積部は、質問部による問合せの結果が、関係情報を蓄積するとの結果である場合のみ、関係情報を蓄積する請求項１から交流管理装置である。 Further, the exchange management device of the fourth aspect of the present invention further comprises an interrogation unit for inquiring of the user whether or not to store the relationship information with respect to any one of the third aspects of the invention, wherein the relationship storage unit 2. The communication management apparatus according to claim 1, wherein the relationship information is stored only when the result of the inquiry by the is a result of storing the relationship information.
　かかる構成により、ユーザにとって必要な関係情報のみを蓄積できる。 With this configuration, it is possible to accumulate only the relevant information necessary for the user.
　また、本第五の発明の交流管理装置は、第四いずれか１つの発明に対して、関係取得部は、交流決定部が決定した交流情報に含まれる文字列または交流情報に対応する対象識別子を用いて、対象識別子と１以上の対象属性値とを有する１以上の対象情報が格納される対象情報格納部を検索し、検索結果を用いて、関係情報を取得する請求項１から交流管理装置である。 Further, in the exchange management device of the fifth invention, in contrast to any one of the fourth inventions, the relationship acquisition unit includes a character string included in the exchange information determined by the exchange determination unit or a target identifier corresponding to the exchange information is used to search a target information storage unit in which one or more target information having a target identifier and one or more target attribute values are stored, and the search result is used to acquire related information. It is a device.
　かかる構成により、対象情報格納部を用いて、正確な関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage accurate relational information using the target information storage unit.
　また、本第六の発明の交流管理装置は、第五いずれか１つの発明に対して、交流情報は、ユーザ間で行われたチャットにおけるチャット履歴情報、ユーザ間の電話での通話の履歴の情報である通話履歴情、請求書情報、契約書情報、イベントに登録した登録者の登録情報、組織のウェブサイト上の問い合わせフォームに対して入力された問合情報、贈り元から贈り先に送信されるギフトに関するギフト情報、営業活動情報、顧客情報、注文情報、採用情報、パンフレット取得情報、経費情報、アンケート情報、入館情報、またはバーチャル空間チェックイン情報である請求項１から交流管理装置である。 Further, in the exchange management device of the sixth invention, in contrast to any one of the fifth inventions, the exchange information includes chat history information in chats conducted between users, history of telephone calls between users, Call history information, billing information, contract information, registration information of registrants who registered for the event, inquiry information entered in the inquiry form on the organization's website, and transmission from the sender to the recipient Gift information, business activity information, customer information, order information, employment information, pamphlet acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information about gifts to be given. .
　かかる構成により、チャットサーバに格納されているチャット履歴情報を用いて、ユーザ間の結びつきに関する関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage relationship information related to connections between users using the chat history information stored in the chat server.
　また、本第七の発明の交流管理装置は、第一から第六いずれか１つの発明に対して、第一識別子に対応付けて他のユーザの名刺に関する名刺情報を受け付ける名刺情報受付部と、関係取得部は、第一識別子と名刺情報に対応する第二識別子とを対応付けた関係情報を取得する交流管理装置である。 Further, the exchange management device of the seventh invention is, for any one of the first to sixth inventions, a business card information reception unit that receives business card information related to business cards of other users in association with the first identifier; The relationship acquisition unit is an exchange management device that acquires relationship information in which the first identifier and the second identifier corresponding to the business card information are associated with each other.
　かかる構成により、名刺交換による関係情報も一緒に管理できる。 With this configuration, it is possible to manage related information by exchanging business cards together.
　また、本第八の発明の交流管理装置は、第一から第七いずれか１つの発明に対して、交流情報に対応する第二識別子で識別されるユーザの情報である他ユーザ情報に変化があるか否かを判断する変化判断部と、変化があると変化判断部が判断した場合に、予め決められた処理を行う交流処理部とをさらに具備する交流管理装置である。 Further, in the exchange management device of the eighth invention, in contrast to any one of the first to seventh inventions, there is no change in other user information, which is the information of the user identified by the second identifier corresponding to the exchange information. The exchange management device further includes a change determination unit that determines whether or not there is a change, and an exchange processing unit that performs predetermined processing when the change determination unit determines that there is a change.
　かかる構成により、他ユーザ情報に変化がある場合に、適切なアクションを行える。 With this configuration, appropriate actions can be taken when there is a change in other user information.
　また、本第九の発明の交流管理装置は、第一から第八いずれか１つの発明に対して、交流情報は、二者以上の間でのコミュニケーションを直接的な目的とはしない情報システムにおいて蓄積された非コミュニケーションシステム情報である交流管理装置である。 In addition, in the exchange management device of the ninth invention, in contrast to any one of the first to eighth inventions, exchange information is used in an information system whose direct purpose is not communication between two or more parties. It is an exchange management device that is accumulated non-communication system information.
　かかる構成により、非コミュニケーションシステム情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 With such a configuration, it is possible to acquire and manage relational information regarding the connection between two parties using non-communication system information.
　本発明の交流管理装置は、２人以上のユーザ間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流情報決定部と、交流情報決定部が取得した交流情報に対応する一のユーザ識別子と、一のユーザ識別子とは異なる他ユーザ識別子であり、交流情報決定部が取得した交流情報に対応する他ユーザ識別子を含む他ユーザ情報を取得する他ユーザ情報取得部と、一のユーザ識別子と他ユーザ情報とを対応付けた交流関係情報を蓄積する交流関係蓄積部とを具備する交流管理装置である。 The exchange management device of the present invention includes an exchange information determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information related to exchanges between two or more users, and an exchange information determination unit. acquires other user information including one user identifier corresponding to the exchange information acquired by and another user identifier different from the one user identifier and corresponding to the exchange information acquired by the exchange information determination unit The interaction management device includes an other user information acquisition unit and an interaction relationship storage unit that stores interaction relationship information in which one user identifier and other user information are associated with each other.
　かかる構成により、交流情報を用いて、ユーザ間の結びつきに関する交流関係情報を取得し、管理できる。 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 present invention, in contrast to the above invention, the two or more pieces of exchange information stored in the storage unit include two or more types of exchange information, and the exchange information determination unit includes: , the exchange management device according to claim 1, which acquires two or more types of exchange information.
　かかる構成により、２種類以上の交流情報を用いて、ユーザ間のビジネスにおける結びつきに関する交流関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage interaction relationship information related to business ties between users using two or more types of interaction information.
　また、本発明の交流管理装置は、上記発明に対して、交流情報決定部は、格納部から、予め決められた条件を満たす交流情報を取得する請求項１または交流管理装置である。 In addition, the exchange management device of the present invention is the exchange management device according to claim 1 or the exchange management device, wherein the exchange information determination unit acquires exchange information that satisfies a predetermined condition from the storage unit, in contrast to the above invention.
　かかる構成により、交流情報を用いて、ユーザ間のビジネスにおける結びつきに関する交流関係情報を取得し、管理できる。 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 exchange management device of the present invention further comprises an inquiry unit for inquiring of the user whether or not to store the exchange relationship information, and the exchange relationship storage unit is configured such that the result of the inquiry by the inquiry unit is: 2. The exchange management apparatus according to claim 1, wherein the exchange relation information is accumulated only when it is a 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.
　また、本発明の交流管理装置は、上記発明に対して、他ユーザ情報取得部は、交流情報決定部が決定した交流情報に含まれる文字列または交流情報に対応するユーザ識別子を用いて、ユーザ識別子と１以上のユーザ属性値とを有する１以上のユーザ情報が格納されるユーザ情報格納部を検索し、検索結果を用いて、他ユーザ情報を取得する請求項１から交流管理装置である。 Further, in the exchange management device of the present invention, in contrast to the above invention, the other user information acquisition unit uses a character string included in the exchange information determined by the exchange information determination unit or a user identifier corresponding to the exchange information to obtain the user 2. The exchange management device according to claim 1, wherein a user information storage unit storing one or more pieces of user information having an identifier and one or more user attribute values is searched, and other user information is acquired using the search result.
　かかる構成により、カレンダーサーバに格納されている予定情報を用いて、正確な他ユーザ情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage accurate other user information using the schedule information stored in the calendar server.
　また、本発明の交流管理装置は、上記発明に対して、交流情報は、ユーザ間で行われたチャットにおけるチャット履歴情報、ユーザ間の電話での通話の履歴の情報である通話履歴情、請求書情報、契約書情報、イベントに登録した登録者の登録情報、組織のウェブサイト上の問い合わせフォームに対して入力された問合情報、贈り元から贈り先に送信されるギフトに関するギフト情報、営業活動情報、顧客情報、注文情報、採用情報、パンフレット取得情報、経費情報、アンケート情報、入館情報、またはバーチャル空間チェックイン情報である、交流管理装置である。 In addition, in the exchange management apparatus of the present invention, in contrast to the above invention, the exchange information includes chat history information in chats conducted between users, call history information that is information on the history of telephone calls between users, and billing information. contract information, registration information of registrants who registered for the event, inquiry information entered in the inquiry form on the organization's website, gift information regarding gifts sent from the giver to the recipient, sales It is an interaction management device that is activity information, customer information, order information, employment information, pamphlet acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information.
　かかる構成により、チャットサーバに格納されているチャット履歴情報を用いて、ユーザ間の結びつきに関する交流関係情報を取得し、管理できる。 With this configuration, it is possible to acquire and manage exchange relationship information relating to connections between users using chat history information stored in the chat server.
　また、本発明の交流管理装置は、上記発明に対して、ユーザ識別子に対応付けて他のユーザの名刺に関する名刺情報を受け付ける名刺情報受付部と、他ユーザ情報取得部は、名刺情報に対応する他のユーザ識別子を含む他ユーザ情報を取得し、交流関係蓄積部は、他ユーザ情報を、ユーザ識別子に対応付けて蓄積する交流管理装置である。 Further, in the exchange management device of the present invention, in contrast to the above invention, the business card information reception unit receives business card information related to business cards of other users in association with the user identifier, and the other user information acquisition unit corresponds to the business card information. The interaction relationship accumulation unit is an exchange management device that acquires other user information including other user identifiers and accumulates the other user information in association with the user identifiers.
　かかる構成により、名刺交換による交流関係情報も一緒に管理できる。 With such a configuration, it is possible to manage information related to exchanges by exchanging business cards together.
　また、本発明の交流管理装置は、上記発明に対して、交流情報に対応する他ユーザ情報に変化があるか否かを判断する変化判断部と、変化があると変化判断部が判断した場合に、予め決められた処理を行う交流処理部とをさらに具備する交流管理装置である。 Further, in the exchange management device of the present invention, in contrast to the above invention, there is provided a change determination unit that determines whether or not there is a change in other user information corresponding to the exchange information, and if the change determination unit determines that there is a change, and an exchange processing unit that performs predetermined processing.
　かかる構成により、他ユーザ情報に変化がある場合に、適切なアクションを行える。 With this configuration, appropriate actions can be taken when there is a change in other user information.
　本発明による交流管理装置によれば、交流情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 According to the exchange management device of the present invention, it is possible to acquire and manage relational information regarding the connection between two parties using exchange information.
実施の形態１における交流管理システムＡの概念図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 同チャット管理表を示す図Diagram showing the same chat management table 同通話管理表を示す図Diagram showing the same call management table 同請求書管理表を示す図Diagram showing the invoice management table 同契約書管理表を示す図Diagram showing the contract management table 同登録管理表を示す図Diagram showing the same registration management table 同イベント管理表を示す図Diagram showing the same event management table 実施の形態２における交流管理装置４のブロック図Block diagram of exchange management device 4 according to Embodiment 2 同交流管理装置４の動作例について説明するフローチャートFlowchart explaining an operation example of the same exchange management device 4 同交流関係情報処理の例について説明するフローチャートFlowchart explaining an example of the same exchange relationship information processing 同関係情報取得処理の例について説明するフローチャートFlowchart for explaining an example of same relation information acquisition processing 同組織情報管理表を示す図Diagram showing the organization information management table 同第一関係管理表を示す図Diagram showing the first relationship management table 同第二関係管理表を示す図Diagram showing the second relationship management table 上記実施の形態におけるコンピュータシステムの概観図Schematic diagram of a computer system in the above embodiment 同コンピュータシステムのブロック図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.
　また、本実施の形態において、２以上の交流情報からビジネスに関する交流情報である１以上のビジネス交流情報を決定し、ビジネス交流情報から他ユーザ情報を取得する交流管理装置を具備する交流管理システムについて説明する。 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 is provided that acquires accurate other user information from the user information storage unit using exchange information and the like, acquires exchange relationship information using the other user information, and accumulates it. An exchange management system that
　また、本実施の形態において、ユーザ識別子に対応するメールアドレス宛に送信されたメールである交流情報から他ユーザ情報を取得し、当該他ユーザ情報を用いて交流関係情報を取得し、蓄積する交流管理装置を具備する交流管理システムについて説明する。 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 exchange relationship information is acquired using the other user information and accumulated. An exchange management system having a 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.
　なお、本明細書において、情報Ｘが情報Ｙに対応付いていることは、情報Ｘから情報Ｙを取得できること、または情報Ｙから情報Ｘを取得できることであり、その対応付けの方法は問わない。情報Ｘと情報Ｙとがリンク付いていても良いし、同じバッファに存在していても良いし、情報Ｘが情報Ｙに含まれていても良いし、情報Ｙが情報Ｘに含まれている等でも良い。 In this specification, the fact that information X is associated with information Y means that information Y can be obtained from information X or information X can be obtained from information Y, and the method of association does not matter. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, and information Y may be included in information X. etc. is fine.
　図１は、本実施の形態における交流管理システムＡの概念図である。交流管理システムＡは、交流管理装置１、１または２以上の情報サーバ２、および１または２以上の端末装置３を備える。 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.
　情報サーバ２は、１または２以上の交流情報が格納されるサーバである。情報サーバ２は、例えば、メールサーバ、カレンダーの各時間帯における予定情報が格納されるカレンダーサーバ、ウェブ会議の予定情報が格納されるウェブ会議サーバ、チャット機能を実現するチャットサーバ、電話の通話履歴情報を格納する電話サーバ、請求書情報が格納される請求書管理サーバ、契約書情報が格納される契約書管理サーバ、イベントへの参加の登録を示す情報である登録情報を管理する登録サーバである。カレンダーサーバは、例えば、Googleカレンダー（登録商標）のサーバ、CalDAVサーバである。また、ウェブ会議サーバは、例えば、Zoom（登録商標）やTeams（登録商標）等のウェブ会議の情報を管理するサーバである。また、電話サーバは、例えば、MiiTel（登録商標）等の電話の情報を保持するサーバである。 The information server 2 is a server that stores one or more exchange information. The information server 2 includes, for example, a mail server, a calendar server that stores schedule information for each time slot in a calendar, a web conference server that stores schedule information for web conferences, a chat server that implements a chat function, and telephone call history. A telephone server that stores information, an invoice management server that stores invoice information, a contract management server that stores contract information, and a registration server that manages registration information that indicates registration for participation in an event. be. The calendar server is, for example, a Google Calendar (registered trademark) 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 (registered trademark). Also, the telephone server is, for example, a server that holds telephone information such as MiiTel (registered trademark).
　情報サーバ２は、例えば、メールサーバから取得された１または２以上のメール、カレンダーサーバから取得された１または２以上の予定情報、ウェブ会議サーバから取得された１または２以上の予定情報、チャットサーバから取得された１または２以上のチャット履歴情報、電話サーバから取得された１または２以上の通話履歴情報、請求書管理サーバから取得された１または２以上の請求書情報、契約書管理サーバから取得された１または２以上の契約書情報、登録サーバから取得された１または２以上の登録情報、組織（例えば、企業、個人事業主、地方公共団体）のウェブサイト上の問い合わせを受け付け、管理する問合情報管理サーバ、贈り元から贈り先に送信されるギフトに関するギフト情報を受信し、管理し、ギフトの贈呈を支援するギフト管理サーバ、営業活動情報を管理する営業支援サーバ、顧客情報を管理する顧客管理サーバ、注文情報を管理する注文管理サーバ、採用情報を管理する採用管理サーバ、パンフレット情報を管理し、提供するパンフレット注文管理サーバ、経費情報を管理する経費情報管理サーバ、アンケート情報および回答情報を管理するアンケート管理サーバ、ビルやホテル等の建物への入館に関する入館情報を管理する入館管理サーバ、またはバーチャル空間におけるチェックイン情報を管理するチェックイン管理サーバ等のうちの１または２種類以上の情報が格納されるサーバでも良い。情報サーバ２は、例えば、クラウドサーバ、ＡＳＰサーバ等である。なお、情報サーバ２の種類は問わない。また、営業支援サーバは、例えば、ＭＡ（マーケティングオートメーション）を支援するためのサーバ、ＳＦＡ（営業支援システム：Sales Force Automation）を支援するためのサーバである。顧客管理サーバは、例えば、ＣＲＭ（Customer Relationship Management）を支援するためのサーバである。 The information server 2 receives, for example, one or more emails obtained from a mail server, one or more schedule information obtained from a calendar server, one or more schedule information obtained from a web conference server, chat 1 or 2 or more chat history information obtained from the server, 1 or 2 or more call history information obtained from the telephone server, 1 or 2 or more bill information obtained from the bill management server, contract management server one or more contract information obtained from, one or more registration information obtained from a registration server, receiving inquiries on the website of an organization (e.g., company, sole proprietor, local government), Inquiry information management server that manages, gift management server that receives and manages gift information related to gifts sent from the sender to the recipient, and supports the presentation of gifts, sales support server that manages sales activity information, customer information order management server for managing order information, recruitment management server for managing recruitment information, pamphlet order management server for managing and providing pamphlet information, expense information management server for managing expense information, questionnaire information 1 or 2 of a questionnaire management server that manages answer information, an admission management server that manages admission information related to entering buildings such as buildings and hotels, or a check-in management server that manages check-in information in a virtual space A server that stores more than one type of information may be used. 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 sales support server is, for example, a server for supporting MA (marketing automation) and a server for supporting SFA (sales force automation). The customer management server is, for example, a server for supporting CRM (Customer Relationship Management).
　端末装置３は、ユーザが使用する端末である。端末装置３は、例えば、交流管理装置１に名刺情報を送信したり、交流管理装置１からの問合せに対する回答を送信したり、交流情報や交流関係情報を出力したりする端末である。端末装置３は、例えば、いわゆるパーソナルコンピュータ、タブレット端末、スマートフォン等であり、その種類は問わない。 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), one or more types of 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.
　なお、格納部１１の２種類以上の交流情報は、各々、異なる情報サーバ２から取得された情報であることは好適である。また、格納部１１が情報サーバ２に含まれる構成である場合、２種類以上の各種類の交流情報は、各々、異なる格納部１１に存在することは好適である。 It is preferable that the two or more types of exchange information in the storage unit 11 are information acquired from different information servers 2 respectively. Moreover, when the storage unit 11 is included in the information server 2 , it is preferable that two or more types of exchange information exist in different storage units 11 .
　交流情報は、２人以上のユーザ間での交流に関する情報である。交流情報は、後述する交流関係情報を取得する元になる情報である。交流情報は、例えば、コミュニケーションシステム情報、非コミュニケーションシステム情報である。交流情報は、種類識別子と対応付いていることは好適である。種類識別子は、交流の種類を識別する情報である。種類識別子は、例えば、交流情報を元々格納していた情報サーバ２に対応する。 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 is, for example, communication system information and non-communication system information. The exchange information is preferably associated with the type identifier. The type identifier is information that identifies the type of exchange. The type identifier corresponds, for example, to the information server 2 that originally stored the exchange information.
　コミュニケーションシステム情報とは、コミュニケーションシステムに関する情報である。コミュニケーションシステムとは、２以上のユーザ間におけるコミュニケーションを直接的な目的とする情報システムである。コミュニケーションシステムは、例えば、メールシステム、ウェブ会議システム、チャットシステム、電話である。ウェブ会議システムは、ビデオ会議システム、ＴＶ会議システムと言っても良い。コミュニケーションシステム情報は、例えば、メール（特に、メールの本文の情報）、ウェブ会議サーバに登録された予定情報であるウェブ会議予約情報、チャット履歴情報、電話の通話履歴情報である。チャット履歴情報は、例えば、行われたチャットの内容である文字列の集合、チャットを行った２以上の各ユーザのユーザ識別子のうちの１種類以上の情報を含む。ここでのユーザ識別子は、例えば、ユーザの氏名、ユーザのＩＤである。通話履歴情報は、ユーザが発した音声、ユーザが発した音声を文字認識した結果の文字列の集合、電話した二人の各ユーザのユーザ識別子のうちの１種類以上の情報を含む。ここでのユーザ識別子は、例えば、電話番号、ユーザの氏名、ユーザのＩＤである。 　Communication system information is information about the communication system. A communication system is an information system whose direct purpose is communication between two or more users. Communication systems are, for example, mail systems, web conference systems, chat systems, and telephones. A web conference system may be called a video conference system or a TV conference system. The communication system information is, for example, e-mail (particularly information on the body of the e-mail), web conference reservation information, which is schedule information registered in the web conference server, chat history information, and telephone call history information. The chat history information includes, for example, one or more types of information among a set of character strings that are the content of the chat and user identifiers of two or more users who have chatted. The user identifier here is, for example, the user's name and user's ID. The call history information includes one or more types of information among a voice uttered by the user, a set of character strings resulting from character recognition of the voice uttered by the user, and user identifiers of each of the two users who made the call. The user identifier here is, for example, a telephone number, a user's name, or a user's ID.
　非コミュニケーションシステム情報とは、非コミュニケーションシステムに関する情報である。非コミュニケーションシステムとは、コミュニケーションを直接的な目的とはしないシステムである。非コミュニケーションシステムは、例えば、スケジュール管理システム、請求書の送信と受け取りとを管理する請求書管理システム、契約書を管理する契約書管理システム、イベントに対する登録を受け付ける登録管理システム、問合情報管理システム、ギフト管理システム、営業支援システム、顧客管理システム等である。なお、システムは、サーバでも良い。また、営業支援システムと顧客管理システムは、特に区別しなくても良い。営業支援システムと顧客管理システムは、例えば、いわゆるＭＡ、ＳＦＡ、ＣＲＭでも良い。また、イベントとは、何らかの行事である。ここでのイベントは、ビジネスに関するイベントであることは好適である。イベントは、例えば、セミナー、講習会、展示会、商品またはサービスの発表会である。スケジュール管理システムは、例えば、ｇｏｏｇｌｅ　ｃａｌｅｎｄａｒ（登録商標）である。請求書管理システムは、例えば、ＢｉｌｌＯｎｅ（登録商標）である。契約書管理システムは、例えば、ＣｏｎｔｒａｃｔＯｎｅ（登録商標）である。非コミュニケーションシステム情報は、例えば、スケジュール管理システムを構成するカレンダーサーバに登録された予定情報であるカレンダー予約情報、請求書管理システムを構成する請求書管理サーバが管理する請求書情報、契約書管理システムを構成する契約書管理サーバが管理する契約書情報、登録管理システムを構成する登録サーバが管理する登録情報、問合情報管理システムを構成するサーバが管理するギフト情報、営業支援システムを構成する営業支援サーバが管理する営業活動情報、顧客管理システムを構成する顧客管理サーバが管理する顧客情報、注文管理システムを構成する注文管理サーバが管理する注文情報、採用管理システムを構成する採用管理サーバが管理する採用情報である。 Non-communication system information is information related to non-communication systems. A non-communicative system is one whose direct purpose is not communication. Non-communication systems include, for example, a schedule management system, an invoice management system that manages the transmission and receipt of invoices, a contract management system that manages contracts, a registration management system that receives registrations for events, and an inquiry information management system. , gift management system, sales support system, customer management system, etc. Note that the system may be a server. Also, the sales support system and the customer management system do not have to be distinguished. The sales support system and customer management system may be, for example, so-called MA, SFA, CRM. Moreover, an event is some event. The event here is preferably an event related to business. The event is, for example, a seminar, workshop, exhibition, product or service presentation. The schedule management system is, for example, google calendar (registered trademark). A bill management system is, for example, BillOne®. The contract management system is, for example, ContractOne (registered trademark). Non-communication system information includes, for example, calendar reservation information that is schedule information registered in a calendar server that constitutes a schedule management system, invoice information that is managed by an invoice management server that constitutes an invoice management system, and a contract management system. contract information managed by the contract management server that makes up the registration management system, registration information managed by the registration server that makes up the registration management system, gift information managed by the server that makes up the inquiry information management system, sales that make up the sales support system Sales activity information managed by the support server, customer information managed by the customer management server constituting the customer management system, order information managed by the order management server constituting the order management system, managed by the recruitment management server constituting the recruitment management system This is the recruitment information.
　交流情報は、名刺交換に関する情報を含まないと考えても良いし、含むと考えても良い。なお、名刺交換に関する情報は、例えば、ユーザ識別子と名刺情報との組、名刺交換した二人の各ユーザのユーザ識別子の組である。また、カレンダーサーバは、スケジュール管理サーバ等と言っても良い。ウェブ会議サーバは、ウェブ会議情報管理サーバ等と言っても良い。 The exchange information may or may not include information related to exchanging business cards. Information related to business card exchange is, for example, a set of a user identifier and business card information, or a set of user identifiers of each of the two users who have exchanged business cards. Also, 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 calendar schedule information is preferably associated with the user identifier of the user of the calendar. In addition, a company may be rephrased as an organization.
　ウェブ会議予定情報は、例えば、会議の相手先の氏名、相手先の会社名、ウェブ会議の開始時刻、ウェブ会議の終了時刻等のうちの１以上の情報を有する。なお、ウェブ会議予定情報は、ウェブ会議のいずれかの参加者（例えば、主催者）のユーザ識別子に対応づいていることは好適である。 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 the web conference schedule information is preferably associated with the user identifier of one of the participants (for example, the organizer) of the web conference.
　なお、カレンダー予定情報とウェブ会議予定情報とを区別せずに、予定情報と言っても良い。 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 chat history information of the chat system includes, for example, the user identifier of the chat sender and the user identifier of the chat receiver. Chat history information has, for example, chat strings. The chat string is a string entered by the user.
　電話の通話履歴情報は、例えば、通話した二人のユーザ識別子を有する。ここでのユーザ識別子は、通常、電話番号であるが、各通話媒体に登録された氏名等でも良い。通話履歴情報は、例えば、通話の音声を文字認識処理して取得された文字列である通話文字列を有する。通話履歴情報は、例えば、通話の音声を有する。 Telephone call history information includes, for example, the user identifiers of the two people who made the call. The user identifier here is usually a telephone number, but may be a name or the like registered in each communication medium. The call history information includes, for example, a call character string that is a character string obtained by subjecting the voice of the call to character recognition processing. The call history information includes, for example, voices of calls.
　請求書情報は、請求書に関する情報である。請求書情報は、例えば、請求元組織名情報（例えば、請求元の会社名）、請求元住所情報（例えば、請求元の会社の住所）、請求先組織名情報（例えば、請求先の会社名）、請求先住所情報（例えば、請求先の会社の住所）
請求額情報、支払先情報、支払期日情報を有する。また、請求書情報は、請求書情報を送信した請求元組織の担当者の請求元担当者識別子を有する。請求元担当者識別子は、例えば、請求元の担当者名、請求元の担当者のＩＤである。また、請求書情報は、請求書情報を受信する請求先組織の担当者の請求先担当者識別子を有する。請求先担当者識別子は、例えば、請求先の担当者名、請求先担当者のＩＤである。 The invoice information is information related to invoices. Billing information includes, for example, billing organization name information (e.g. billing company name), billing address information (e.g. billing company address), billing organization name information (e.g. billing company name) ), billing address information (e.g. billing company address)
It has billing amount information, payee information, and payment date information. The billing information also includes the billing contact identifier of the contact of the billing organization that sent the billing information. The invoicing person in charge identifier is, for example, the name of the invoicing person in charge and the ID of the invoicing person in charge. The billing information also includes a billing contact identifier for a contact at the billing organization that receives the billing information. The billing contact person identifier is, for example, the name of the billing contact person or the ID of the billing contact person.
　契約書情報は、契約書に関する情報である。契約書情報は、例えば、２以上の各契約者の契約者組織名情報を有する。契約者組織名情報は、例えば、契約の当事者の組織名である。また、契約書情報は、契約者組織の契約の担当者識別子を有する。契約の担当者識別子は、例えば、契約の担当者名、契約の担当者のＩＤである。契約書情報は、例えば、契約の当事者の代表者識別情報を有する。代表者識別情報は、代表者を識別する情報であり、例えば、代表者の氏名、代表者のＩＤである。 The contract information is information related to the contract. Contract information has, for example, contractor organization name information of two or more contractors. The contractor organization name information is, for example, the organization name of the parties to the contract. Also, the contract information has an identifier of the person in charge of the contract of the contractor organization. The contract manager identifier is, for example, the name of the contract manager or the ID of the contract manager. The contract information includes, for example, representative identification information of parties to the contract. The representative identification information is information for identifying the representative, such as the name of the representative and the ID of the representative.
　登録情報は、例えば、イベントに登録した登録者の登録者識別情報と、イベント識別子とを有する。登録者識別情報は、イベントへの参加の登録者を識別する情報であり、例えば、登録者名、登録者のＩＤである。また、イベント識別子は、イベントを識別する情報である。イベント識別子は、例えば、イベント関係者を識別するイベント関係者識別情報が対応付いている。イベント関係者識別情報は、イベントの主催者を識別する主催者識別情報、イベントにおける登壇者（例えば、講師）を識別する登壇者識別情報である。主催者識別情報は、イベントの主催者を識別する情報であり、例えば、主催者の氏名、主催者のＩＤである。登壇者識別情報は、イベントにおける登壇者を識別する情報であり、例えば、登壇者の氏名、登壇者のＩＤである。 The registration information includes, for example, registrant identification information of registrants who registered for the event and event identifiers. The registrant identification information is information for identifying registrants participating in the event, such as registrant names and registrant IDs. An event identifier is information for identifying an event. The event identifier is associated with, for example, event-related party identification information that identifies event-related parties. The event-related person identification information is organizer identification information for identifying the organizer of the event, and speaker identification information for identifying the speaker (for example, lecturer) in the event. The organizer identification information is information for identifying the organizer of the event, such as the name of the organizer and the ID of the organizer. The speaker identification information is information for identifying the speaker in the event, and is, for example, the name of the speaker and the ID of the speaker.
　問合情報は、例えば、フォームの配信日を特定する配信日情報、質問の受領日を特定する受領日情報、１以上の質問者属性値、質問の内容、回答の内容、フォーム作成の担当者またはフォーム作成の担当者のユーザ識別子を有する。１以上の質問者属性値は、例えば、質問者が属する会社名、質問者が属する部署名、質問者の役職、質問者のメールアドレス、質問者の氏名である。なお、問合情報は、問合せを受ける側のユーザのユーザ識別子に対応づいていることは好適である。 Inquiry information includes, for example, delivery date information that specifies the delivery date of the form, receipt date information that specifies the date of receipt of the question, one or more questioner attribute values, question content, response content, and the person in charge of creating the form. Or it has the user identifier of the person in charge of creating the form. One or more questioner attribute values are, for example, the name of the company to which the questioner belongs, the name of the department to which the questioner belongs, the position of the questioner, the email address of the questioner, and the name of the questioner. It is preferable that the inquiry information is associated with the user identifier of the user who receives the inquiry.
　ギフト情報は、例えば、ギフトを送付し、受領された日であるギフト送付受領日、ギフトの内容を示す内容情報、ギフトの送付者（贈呈者）の１以上の贈呈者属性値、ギフトの送付先の人（受贈者）の１以上の受贈者属性値を有する。贈呈者の贈呈者属性値は、例えば、贈呈者の氏名、贈呈者のメールアドレス、贈呈者の電話番号である。受贈者の受贈者属性値は、例えば、受贈者の氏名、受贈者のメールアドレス、受贈者の電話番号である。なお、ギフト情報は、贈呈者のユーザ識別子に対応づいていることは好適である。 The gift information includes, for example, the date when the gift was sent and received, which is the date when the gift was sent, the content information indicating the content of the gift, one or more presenter attribute values of the gift sender (presenter), the gift delivery Has one or more beneficiary attribute values of the previous person (the beneficiary). The presenter attribute value of the presenter is, for example, the name of the presenter, the mail address of the presenter, and the telephone number of the presenter. The beneficiary attribute value of the beneficiary is, for example, the name of the beneficiary, the e-mail address of the beneficiary, and the telephone number of the beneficiary. Note that the gift information is preferably associated with the user identifier of the presenter.
　営業活動情報は、営業担当者情報、営業の日付、営業先である顧客の情報（営業顧客情報と言う。）、営業の種類（例えば、「商談」「案件」「問合せ」）、営業活動の内容を示す内容情報を有する。営業担当者情報は、例えば、営業担当者の氏名、営業担当者が属する会社名、営業担当者が属する部署名、営業担当者の役職、営業担当者のメールアドレス、営業担当者の電話番号を有する。営業顧客情報は、例えば、顧客の氏名、顧客が属する会社名、顧客が属する部署名、顧客の役職、顧客のメールアドレス、顧客の電話番号を有する。なお、営業活動情報は、営業担当者のユーザ識別子に対応づいていることは好適である。 Sales activity information consists of sales representative information, date of sales, customer information (called sales customer information), type of sales It has content information indicating the content. Salesperson information includes, for example, the name of the salesperson, the name of the company to which the salesperson belongs, the name of the department to which the salesperson belongs, the title of the salesperson, the email address of the salesperson, and the telephone number of the salesperson. have. The sales customer information includes, for example, the name of the customer, the name of the company to which the customer belongs, the name of the department to which the customer belongs, the position of the customer, the email address of the customer, and the telephone number of the customer. It is preferable that the sales activity information is associated with the user identifier of the sales representative.
　顧客情報は、例えば、顧客と担当者が接触した日（接触日）、顧客の担当者の担当者情報、１以上の顧客属性値を有する。担当者情報は、例えば、担当者の氏名、担当者が属する会社名、担当者が属する部署名、担当者の役職、担当者のメールアドレス、担当者の電話番号を有する。１以上の顧客属性値は、例えば、顧客の氏名、顧客が属する会社名、顧客が属する部署名、顧客の役職、顧客のメールアドレス、顧客の電話番号である。なお、顧客情報は、担当者のユーザ識別子に対応づいていることは好適である。 The customer information includes, for example, the date when the customer and the person in charge contacted (contact date), the person in charge information of the customer's person in charge, and one or more customer attribute values. The information on the person in charge includes, for example, the name of the person in charge, the name of the company to which the person in charge belongs, the name of the department to which the person in charge belongs, the title of the person in charge, the email address of the person in charge, and the telephone number of the person in charge. One or more customer attribute values are, for example, the name of the customer, the name of the company to which the customer belongs, the name of the department to which the customer belongs, the position of the customer, the email address of the customer, and the telephone number of the customer. The customer information is preferably associated with the user identifier of the person in charge.
　注文情報は、例えば、発注者情報、注文先情報、注文日、納期、注文内容情報、取引金額を有する。発注者情報は、発注者に関する情報である。発注者情報は、例えば、氏名、住所、電話番号、メールアドレスを有する。注文先情報は、注文先に関する情報である。注文先情報は、例えば、氏名、会社名、住所、電話番号、メールアドレスを有する。注文内容情報は、例えば、商品名、数量、単価、商品ごとの合計金額を有する。なお、注文情報は、発注者のユーザ識別子、または注文先のユーザのユーザ識別子に対応づいていることは好適である。 The order information includes, for example, orderer information, order destination information, order date, delivery date, order details information, and transaction amount. The orderer information is information about the orderer. Orderer information includes, for example, name, address, telephone number, and e-mail address. The order destination information is information about the order destination. Order destination information includes, for example, name, company name, address, telephone number, and e-mail address. The order detail information includes, for example, product name, quantity, unit price, and total price for each product. The order information is preferably associated with the user identifier of the orderer or the user identifier of the user to whom the order is placed.
　採用情報は、例えば、応募者情報、応募先情報、応募日、面接日、応募内容情報、結果情報を有する。応募者情報は、応募者に関する情報である。応募者情報は、例えば、氏名、住所、電話番号、メールアドレスを有する。応募先情報は、応募先の組織（通常、企業）に関する情報である。応募先情報は、例えば、会社名、会社の担当者（例えば、人事部の担当者）の氏名、会社の住所、会社の電話番号、会社の担当者のメールアドレスを有する。応募内容情報は、例えば、職種、正社員か否かを示す情報、勤務時間、給与を有する。結果情報とは、採用の結果に関する情報である。結果情報は、例えば、採用までの段階を特定する段階情報、面接を行ったか否かを示す面接実施情報、採用に至ったか否かを示す採用結果情報を有する。なお、採用情報は、応募者のユーザ識別子、または応募先の担当者のユーザ識別子に対応づいていることは好適である。 Recruitment information includes, for example, applicant information, applicant information, application date, interview date, application content information, and result information. Applicant information is information about the applicant. Applicant information includes, for example, name, address, telephone number, and e-mail address. Applicant information is information about an organization (usually a company) to which the applicant applies. The applicant information includes, for example, the company name, the name of the person in charge of the company (for example, the person in charge of the personnel department), the address of the company, the telephone number of the company, and the e-mail address of the person in charge of the company. The application content information includes, for example, job type, information indicating whether or not the applicant is a regular employee, working hours, and salary. Result information is information about the result of adoption. The result information includes, for example, stage information specifying the stage leading up to employment, interview implementation information indicating whether or not an interview was conducted, and employment result information indicating whether or not the applicant was hired. It is preferable that the employment information is associated with the user identifier of the applicant or the user identifier of the person in charge of the applicant.
　パンフレット取得情報は、パンフレットを取得したことに関する情報である。パンフレット取得情報は、例えば、パンフレットを取得した取得者に関する取得者情報、パンフレットの提供組織に関する組織情報、パンフレットの内容を示す内容情報を有する。取得者情報は、取得者の氏名、住所、メールアドレス、電話番号を有する。提供組織の組織情報は、例えば、会社名、会社の電話番号、パンフレットの提供企業の担当者情報を有する。担当者情報は、例えば、担当者の氏名、メールアドレス、電話番号を有する。パンフレットの内容情報は、例えば、パンフレットの概要を示す文字列、パンフレットに掲載されている商品やサービス等の事項の種類を示す種類情報を有する。 The pamphlet acquisition information is information about the acquisition of the pamphlet. The pamphlet acquisition information includes, for example, acquirer information about the acquirer who acquired the pamphlet, organization information about the organization providing the pamphlet, and content information indicating the content of the pamphlet. Acquirer information includes the name, address, e-mail address, and telephone number of the acquirer. The organization information of the providing organization includes, for example, the company name, the company's telephone number, and the information of the person in charge of the company providing the pamphlet. The person-in-charge information includes, for example, the name, email address, and telephone number of the person in charge. The pamphlet content information includes, for example, a character string indicating an outline of the pamphlet and type information indicating the types of items such as products and services described in the pamphlet.
　経費情報は、経費に関する情報である。経費情報は、例えば、経費の申請者に関する申請者情報、経費の使用を許可する許可者に関する許可者情報、経費の内容に関する内容情報を有する。申請者情報は、例えば、申請者の氏名、メールアドレス、電話番号を有する。許可者情報は、例えば、許可者の氏名、メールアドレス、電話番号を有する。経費の内容情報は、例えば、経費の科目、金額、使用日、購入した商品等の種類を有する。 Expense information is information about expenses. The expense information includes, for example, applicant information about the applicant of the expense, permitter information about the permitter who permits the use of the expense, and content information about the contents of the expense. Applicant information includes, for example, the applicant's name, email address, and telephone number. The permitter information includes, for example, the permitter's name, email address, and telephone number. Expense content information includes, for example, types such as item of expense, amount of expense, date of use, and merchandise purchased.
　アンケート情報は、ユーザに対して実施したアンケートに関する情報である。アンケート情報は、例えば、１以上の質問情報、各質問情報に対する回答情報、回答者情報、実施者情報、アンケートの配布日、回答日を有する。回答者情報は、例えば、回答者の氏名、メールアドレス、電話番号を有する。実施者情報は、アンケートの実施者である会社名、当該会社の担当者情報を有する。担当者情報は、担当者の氏名、メールアドレス、電話番号を有する。 　Questionnaire information is information related to the questionnaires conducted for users. The questionnaire information has, for example, one or more question information, answer information for each question information, respondent information, implementer information, questionnaire distribution date, and answer date. The respondent information includes, for example, the respondent's name, email address, and telephone number. The information on the implementer includes the name of the company that implements the questionnaire and information on the person in charge of the company. The information on the person in charge has the name, email address, and telephone number of the person in charge.
　入館情報は、例えば、入館者情報、建物情報、入館日を有する。入館者情報は、入館者に関する情報である。入館者情報は、例えば、入館者の氏名、メールアドレス、電話番号を有する。建物情報は、例えば、入館された建物等の所有者情報、建物等の住所を有する。所有者情報は、所有者である会社名、当該会社の代表者情報、建物等を管理する管理者情報を有する。代表者情報は、例えば、会社の代表者の氏名、メールアドレス、電話番号を有する。管理者情報は、管理者の氏名、メールアドレス、電話番号を有する。 The entry information includes, for example, visitor information, building information, and entry date. Visitor information is information about visitors. The visitor information includes, for example, the visitor's name, e-mail address, and telephone number. The building information includes, for example, the owner information of the building that has been entered, and the address of the building. The owner information includes the name of the company that owns the building, information about the representative of the company, and information about the manager who manages the building. The representative information includes, for example, the company representative's name, email address, and telephone number. The manager information includes the manager's name, email address, and telephone number.
　バーチャル空間チェックイン情報は、ユーザがバーチャル空間にチェックインしたことに関する情報である。バーチャル空間チェックイン情報を、適宜、チェックイン情報と言う。チェックイン情報は、例えば、バーチャル空間にチェックインしたチェックイン者情報、バーチャル空間に関する空間情報、チェックインした日を有する。チェックイン者情報は、チェックインしたユーザの氏名、メールアドレス、電話番号を有する。空間情報は、バーチャル空間の名称、バーチャル空間の運営者情報を有する。運営者情報は、運営者の会社名、当該会社の運営者の氏名、メールアドレス、電話番号を有する。 　Virtual space check-in information is information about the user's check-in to the virtual space. The virtual space check-in information is arbitrarily referred to as check-in information. The check-in information includes, for example, check-in person information who has checked in to the virtual space, spatial information about the virtual space, and check-in date. The check-in person information includes the name, email address, and telephone number of the user who has checked in. The space information includes the name of the virtual space and information on the operator of the virtual space. The operator information includes the company name of the operator, the name of the operator of the company, the e-mail address, and the telephone number.
　交流関係情報は、２または３以上のユーザの間で交流があったこと、または交流があることを示す情報である。交流関係情報は、交流関係が特定できる情報であれば良い。交流関係情報は、通常、他ユーザ情報とユーザ識別子とを対応付ける情報である。交流関係情報は、他ユーザ情報とユーザ識別子とを有する情報でも良いし、交流関係情報は、他ユーザ情報とユーザ識別子とのリンクの情報でも良いし、ユーザ識別子と対応付いた他ユーザ情報等でも良い。交流関係情報は、２または３以上のユーザの間で交流があったこと、または交流があることを示す情報であれば良く、そのデータ構造や内容は問わない。ユーザ識別子は、ユーザを識別する情報である。ユーザ識別子は、例えば、ユーザＩＤ、メールアドレス、電話番号、ユーザが使用する端末装置３の端末識別子等であるが、ユーザを識別可能な情報であれば何でも良い。端末装置３の識別子は、例えば、ＩＰアドレス、ＭＡＣアドレスである。他ユーザ情報は、他ユーザに関する情報である。他ユーザは、他ユーザ情報が対応付くユーザ識別子で識別されるユーザ以外のユーザである。他ユーザ情報は、例えば、他ユーザのユーザ識別子、他ユーザの１以上のユーザ属性値のうちの１または２以上情報である。ユーザ属性値は、例えば、氏名、ユーザが所属する組織の組織識別子、役職、電話番号、ＦＡＸ番号、住所、ＵＲＬである。組織識別子は、例えば、会社名、団体名である。住所は、例えば、所属する組織の住所、自宅の住所である。ＵＲＬは、所属する組織のホームページのＵＲＬである。 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 in the user information storage unit 111 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. The interaction relationship information is information specifying interaction with other users of the user identified by the user identifier. Contact information typically corresponds to a user identifier. The interaction relationship information usually corresponds to other user identifiers of other users who have an interaction relationship with the user identified by the user identifier. It should be noted that corresponding to the user identifier (including other user identifiers) may include 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", "chat", "telephone", "bill", "contract", "event", 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. "Chat" is information indicating that there was an exchange using the chat system. "Telephone" is information indicating that there was an exchange (a call was made) by telephone. "Bill" is information indicating that bills were exchanged and there was interaction. "Contract" is information indicating that the contract was exchanged and there was interaction. This is information indicating that there was interaction in the "event". "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 . The user identifier acquisition unit 131 acquires, for example, one user identifier corresponding to the friendship information. 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. Also, the user identifier acquired by the user identifier acquiring unit 131 may be a user identifier acquired by the other user information acquiring unit 134, which will be described later.
　交流情報決定部１３２は、１または２以上の交流情報を格納する格納部１１から、交流情報を決定する。ここでの格納部１１は、情報サーバ２のサーバ格納部２１でも良い。 The exchange information determination unit 132 determines exchange information from the storage unit 11 that stores one or more exchange information. The storage unit 11 here may be the server storage unit 21 of the information server 2 .
　交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する交流情報を、１以上の交流情報の中から決定する。交流情報決定部１３２は、取得し得るすべての交流情報を決定しても良い。取得し得る交流情報は、例えば、格納部１１の交流情報である。取得し得る交流情報は、例えば、アクセス可能な１または２以上の情報サーバ２に格納されている交流情報である。 The exchange information determination unit 132, for example, determines the exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 from among one or more pieces of exchange information. The exchange information determination unit 132 may determine all obtainable exchange information. Acquirable exchange information is, for example, exchange information in the storage unit 11 . Acquirable exchange information is, for example, exchange information stored in one or more accessible information servers 2 .
　交流情報決定部１３２は、２以上の種類の交流情報の中から、１または２以上の交流情報を決定することは好適である。つまり、交流情報決定部１３２は、２以上の各種類識別子に対応付く交流情報の中から、１または２以上の交流情報を決定することは好適である。言い換えれば、交流情報決定部１３２が決定する交流情報は、２種類以上の交流情報であることは好適である。２種類以上の交流情報は、例えば、対応する種類識別子が「メール」「カレンダー」「ウェブ会議」「チャット」「電話」「請求書」「契約書」「イベント」「問合」「ギフト」「営業活動」「顧客」「採用」「パンフレット」「経費」「アンケート」「入館」「バーチャル空間チェックイン」「名刺」のうちの２種類の交流情報である。 It is preferable that the exchange information determination unit 132 determines one or more pieces of exchange information from among two or more types of exchange information. In other words, it is preferable that the exchange information determination unit 132 determines one or more pieces of exchange information from pieces of exchange information associated with two or more types of identifiers. In other words, the exchange information determined by the exchange information determination unit 132 is preferably two or more types of exchange information. Two or more types of exchange information, for example, have corresponding type identifiers of "email", "calendar", "web conference", "chat", "telephone", "invoice", "contract", "event", "inquiry", "gift", " There are two types of exchange information: sales activities, customers, recruitment, pamphlets, expenses, questionnaires, admission, virtual space check-ins, and business cards.
　交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の交流情報を決定することは好適である。 It is preferable that the interaction information determination unit 132 determines one or more pieces of interaction information corresponding to the user identifier acquired by the user identifier acquisition unit 131 .
　交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する交流情報であり、予め決められた条件を満たす交流情報を、１以上の交流情報の中から決定する。なお、１以上の交流情報は、情報サーバ２から、直接的または間接的に取得した情報である。１以上の交流情報は、例えば、受信部１２が受信した１以上の交流情報、格納部１１に格納されている１以上の交流情報、１または２以上の各情報サーバ２に格納されている１以上の交流情報、１以上の各情報サーバ２から取得した図示しない情報処理装置に格納されている１以上の交流情報である。交流情報は、元々、情報サーバ２に格納されていた情報であることは好適である。交流情報は、例えば、メール、予定情報である。交流情報は、元々、情報サーバ２に格納されていた情報を加工した情報でも良い。 The exchange information determination unit 132 determines, for example, exchange information corresponding to the user identifier acquired by the user identifier acquisition unit 131 and satisfying a predetermined condition from among one or more pieces of exchange information. 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 one or two or more information servers 2. The exchange information described above is 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 .
　予め決められた条件は、例えば、内容条件である。内容条件は、例えば、交流情報が有する文字列に関する条件である。 A predetermined condition is, for example, a content condition. The content condition is, for example, a condition regarding a character string that exchange information has.
　予め決められた条件は、例えば、頻度条件である。頻度条件は、交流の頻度に関する条件である。頻度条件は、例えば、交流の回数が閾値以上または閾値より大きいことである。頻度条件は、例えば、メールでのやり取りが閾値以上であることである。頻度条件は、例えば、カレンダー情報に対応するユーザ識別子に組の数が閾値以上であることである。頻度条件は、例えば、ウェブ会議の開催回数が閾値以上であることである。頻度条件は、例えば、チャットの回数が閾値以上であることである。頻度条件は、例えば、電話での通話回数が閾値以上であることである。頻度条件は、例えば、一のユーザの問合せ回数が閾値以上であることである。頻度条件は、例えば、一のユーザのギフトの贈呈回数が閾値以上であることである。頻度条件は、例えば、一のユーザへの営業回数が閾値以上であることである。頻度条件は、例えば、一のユーザの注文回数が閾値以上であることである。なお、「閾値以上」は「閾値より大きい」と置き換えても良い。 A predetermined condition is, for example, a frequency condition. The frequency condition is a condition regarding the frequency of alternating current. The frequency condition is, for example, that the number of times of alternating current is greater than or equal to a threshold. The frequency condition is, for example, that exchanges by e-mail are equal to or greater than a threshold. The frequency condition is, for example, that the number of pairs of user identifiers corresponding to calendar information is equal to or greater than a threshold. The frequency condition is, for example, that the number of web conferences held is equal to or greater than a threshold. The frequency condition is, for example, that the number of chats is equal to or greater than a threshold. The frequency condition is, for example, that the number of telephone calls is equal to or greater than a threshold. The frequency condition is, for example, that the number of inquiries made by one user is equal to or greater than a threshold. The frequency condition is, for example, that the number of gift presentations by one user is equal to or greater than a threshold. The frequency condition is, for example, that the number of sales to one user is equal to or greater than a threshold. The frequency condition is, for example, that the number of orders placed by one user is equal to or greater than a threshold. Note that "greater than or equal to the threshold" may be replaced with "greater than the threshold".
　予め決められた条件は、例えば、時期条件である。時期条件は、交流の時期に関する条件である。時期条件は、例えば、交流の時期が予め決められた時期であること、時期条件は、例えば、交流の時期が予め決められた時期でないことである。予め決められた期間は、例えば、お中元期間（例えば、７月）、お歳暮期間（例えば、１２月）である。予め決められた期間でない期間は、例えば、クリスマスの時期（例えば、１２／２４から１２／２５）である。時期条件は、ビジネルにおける交流のための期間であることは好適である。 A predetermined condition is, for example, a time condition. The timing condition is a condition regarding the timing of the exchange. The timing condition is, for example, that the timing of the exchange is a predetermined timing, and the timing condition is that the timing of the exchange is not a predetermined timing, for example. The predetermined period is, for example, the mid-year gift period (for example, July) and the year-end gift period (for example, December). A non-predetermined period is, for example, Christmas time (eg, December 24th to December 25th). It is preferable that the time condition is a period for interaction in business.
　交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する交流情報であり、ビジネス交流条件を満たす交流情報を決定する。 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.
　メールアドレスに関する条件は、相手先（例えば、メールの送信元、メールの送信先）のメールアドレスが、所定の文字列（例えば、「co.jp」「ac.jp」等）を含むことである。メールアドレスに関する条件は、相手先のメールアドレスが、所定の文字列を含まないことである。メールアドレスに関する条件は、例えば、相手先のメールアドレスが、個人メールのアドレスと考えられるメールアドレス（例えば、「gmail.com」または「yahoo.co.jp」を含むアドレス）でないことである。 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").
　メールの内容に関する条件（内容条件）は、例えば、スパムメールではないことである。なお、スパムメールであるか否かを判断する技術は、公知のメーラーの技術が使用可能である。また、メールの内容に関する条件は、例えば、図示しないビジネス用語辞書に格納されている用語を多く含むメールであることである。用語を多く含むメールとは、閾値以上または閾値より多い数の用語を含むこと、閾値以上または閾値より多い割合の用語を含むことである。また、メールの内容に関する条件は、例えば、機械学習の分類器（学習モデル、学習器等と言っても良い）を用いて、分類処理（予測処理と言っても良い）を行った結果、ビジネスメールであると判断されることである。なお、かかる分類器は、ビジネスメールである１以上の正例と、ビジネスメールでない１以上の負例とを教師データとして用いて、機械学習のアルゴリズムにより学習処理を行って取得されたデータである。なお、機械学習は、いわゆる深層学習、ランダムフォレスト、決定木、ＳＶＭ等が利用可能であるが、そのアルゴリズムは問わない。また、機械学習として、例えば、TensorFlowの各種のモジュール、R言語のランダムフォレストのモジュール、TinySVM等が使用可能である。なお、ビジネス用語辞書は、ビジネスで使用される２以上の用語が蓄積されたデータベースまたはファイル等の記憶領域である。ビジネス用語は、句や文でも良い。句や文は、例えば、「いつもお世話になっております」「今後ともよろしくお願いいたします」「King Regards」等である。 The condition regarding the content of the email (content condition) 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.
　交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の予定情報から、予め決められた条件を満たす予定情報を決定する。かかる予め決められた条件を、適宜、予定条件と言う。 For example, 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 exchange information determination unit 132 determines exchange information using, for example, communication system information. The communication system information is e-mail, web conference reservation information, chat history information, or call history information, for example.
　交流情報決定部１３２は、例えば、非コミュニケーションシステム情報を用いて、交流情報を決定する。非コミュニケーションシステム情報は、例えば、請求書情報、契約書情報、登録情報、問合情報、ギフト情報、営業活動情報、顧客情報、注文情報、採用情報、パンフレット取得情報、経費情報、アンケート情報、入館情報、またはバーチャル空間チェックイン情報である。 The exchange information determination unit 132 determines exchange information using, for example, non-communication system information. Non-communication system information, for example, invoice information, contract information, registration information, inquiry information, gift information, sales activity information, customer information, order information, employment information, brochure acquisition information, expense information, questionnaire information, admission information, or virtual space check-in information.
　交流情報決定部１３２は、例えば、格納部１１の１以上のチャット履歴情報から、１以上のチャット履歴情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１または２以上のチャット履歴情報を決定する。交流情報決定部１３２は、例えば、格納部１１の１以上のチャット履歴情報から、予め決められた条件を満たす１以上のチャット履歴情報を決定する。予め決められた条件は、例えば、ビジネス交流条件、頻度条件である。 The exchange information determination unit 132 determines one or more pieces of chat history information from, for example, one or more pieces of chat history information in the storage unit 11 . For example, the exchange information determination unit 132 determines one or more pieces of chat history information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . The exchange information determination unit 132 determines, for example, one or more pieces of chat history information that satisfy a predetermined condition from the one or more pieces of chat history information in the storage unit 11 . The predetermined conditions are, for example, business interaction conditions and frequency conditions.
　チャット履歴情報に関する内容条件は、例えば、ビジネス交流条件である。かかる内容条件は、例えば、チャット履歴情報が有する文字列の中に、格納部１１に格納されているビジネス用語が含まれることである。チャット履歴情報に関するビジネス交流条件は、例えば、チャット履歴情報の中の文字列（文章など）のクラスが「ビジネス」であることである。なお、文字列のクラスを決定する処理は公知技術である。交流情報決定部１３２は、例えば、文字列とクラス（例えば、「ビジネス」か否か）とを有する２以上の教師データを機械学習のアルゴリズムにより学習処理した結果、取得された二値分類の学習器を用いる。つまり、交流情報決定部１３２は、例えば、当該学習器とチャット履歴情報とを、機械学習の予測処理のモジュールに与え、当該モジュールを実行し、チャット履歴情報のクラスが「ビジネス」か否かを決定する。そして、交流情報決定部１３２は、クラス「ビジネス」に対応する１以上のチャット履歴情報を決定する。 The content conditions for chat history information are, for example, business exchange conditions. Such a content condition is, for example, that the business term stored in the storage unit 11 is included in the character string of the chat history information. A business exchange condition for chat history information is, for example, that the class of a character string (text, etc.) in the chat history information is "business." Note that the process of determining the class of a character string is a known technique. For example, the exchange information determination unit 132 learns the acquired binary classification as a result of learning processing of two or more teacher data having a character string and a class (for example, "business" or not) by a machine learning algorithm. Use a vessel. In other words, the interaction information determining unit 132, for example, supplies the learning device and the chat history information to a machine learning prediction processing module, executes the module, and determines whether the class of the chat history information is “business”. decide. Then, the exchange information determination unit 132 determines one or more pieces of chat history information corresponding to the class "business".
　チャット履歴情報に関する頻度条件は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザがチャットを行った回数が閾値以上または閾値より多い相手のユーザに対応するチャット履歴情報であることである。つまり、交流情報決定部１３２は、例えば、決定する候補の１以上の各チャット履歴情報に対応する２以上のユーザ識別子の中に、閾値以上または閾値より多い出現頻度の２つのユーザ識別子の組が存在するか否かを判断し、かかる出現頻度の２つのユーザ識別子の組に対応するチャット履歴情報を決定する。なお、交流情報決定部１３２は、交流関係情報を構成する２つのユーザ識別子を取得しても良い。 The frequency condition regarding the chat history information is, for example, that the chat history information corresponds to the other user with whom the user identified by the user identifier acquired by the user identifier acquiring unit 131 has chatted more times than or equal to a threshold. is. That is, for example, the exchange information determination unit 132 determines that, among the two or more user identifiers corresponding to the one or more pieces of chat history information to be determined, there is a set of two user identifiers whose frequency of appearance is equal to or greater than the threshold. Whether or not it exists is determined, and the chat history information corresponding to the set of two user identifiers having such frequency of occurrence is determined. Note that the interaction information determination unit 132 may acquire two user identifiers forming the interaction relationship information.
　交流情報決定部１３２は、例えば、格納部１１の１以上の通話履歴情報から、１以上の通話履歴情報を決定する。交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１または２以上の通話履歴情報を決定する。交流情報決定部１３２は、例えば、格納部１１の１以上の通話履歴情報から、予め決められた条件を満たす１以上の通話履歴情報を決定する。予め決められた条件は、例えば、ビジネス交流条件、頻度条件である。なお、通話履歴情報は、例えば、音声の通話を音声認識し、取得された文字列を含む。 The exchange information determination unit 132 determines one or more pieces of call history information from, for example, one or more pieces of call history information in the storage unit 11 . Exchange information determination unit 132 determines one or more pieces of call history information corresponding to the user identifier acquired by user identifier acquisition unit 131 . The exchange information determination unit 132 determines, for example, one or more pieces of call history information that satisfy a predetermined condition from the one or more pieces of call history information in the storage unit 11 . The predetermined conditions are, for example, business interaction conditions and frequency conditions. Note that the call history information includes, for example, a character string obtained by recognizing a voice call.
　通話履歴情報に関する内容条件は、例えば、ビジネス交流条件である。かかる内容条件は、例えば、通話履歴情報が有する文字列の中に、格納部１１に格納されているビジネス用語が含まれることである。通話履歴情報に関するビジネス交流条件は、例えば、通話履歴情報の中の文字列（文章など）のクラスが「ビジネス」であることである。なお、文字列のクラスを決定する処理は、上述したように公知技術である。交流情報決定部１３２は、公知技術を用いて、通話履歴情報のクラスが「ビジネス」か否かを決定する。そして、交流情報決定部１３２は、クラス「ビジネス」に対応する１以上の通話履歴情報を決定する。 　The content conditions related to call history information are, for example, business exchange conditions. Such a content condition is, for example, that the business term stored in the storage unit 11 is included in the character string of the call history information. A business interaction condition for call history information is, for example, that the class of character strings (such as sentences) in the call history information is "business." Note that the process of determining the class of a character string is a known technique as described above. The exchange information determination unit 132 determines whether or not the class of the call history information is "business" using a known technique. Then, the exchange information determination unit 132 determines one or more pieces of call history information corresponding to the class "business".
　通話履歴情報に関する頻度条件は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザが通話を行った回数が閾値以上または閾値より多い相手のユーザに対応する通話履歴情報であることである。つまり、交流情報決定部１３２は、例えば、決定する候補の１以上の各通話履歴情報に対応する２以上のユーザ識別子の中に、閾値以上または閾値より多い出現頻度の２つのユーザ識別子の組が存在するか否かを判断し、かかる出現頻度の２つのユーザ識別子の組に対応する通話履歴情報を決定する。なお、交流情報決定部１３２は、交流関係情報を構成する２つのユーザ識別子を取得しても良い。 The frequency condition regarding the call history information is, for example, that the user identified by the user identifier acquired by the user identifier acquiring unit 131 is the call history information corresponding to the user with whom the number of times the user has made a call is equal to or greater than the threshold. is. That is, for example, the exchange information determination unit 132 determines that, among the two or more user identifiers corresponding to the one or more pieces of call history information to be determined, there is a set of two user identifiers whose frequency of appearance is equal to or greater than the threshold. It determines whether or not it exists, and determines the call history information corresponding to the set of two user identifiers with such frequency of occurrence. Note that the interaction information determination unit 132 may acquire two user identifiers forming the interaction relationship information.
　交流情報決定部１３２は、例えば、格納部１１の１以上の請求書情報から、１以上の請求書情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の請求書情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の請求書情報から、予め決められた条件を満たす１以上の請求書情報を決定しても良い。予め決められた条件は、例えば、頻度条件である。予め決められた条件は、例えば、内容条件、頻度条件である。 The exchange information determination unit 132 determines one or more items of invoice information from, for example, one or more items of invoice information in the storage unit 11 . The interaction information determination unit 132 determines, for example, one or more items of invoice information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more items of bill information that satisfy a predetermined condition from among the items of bill information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . A predetermined condition is, for example, a frequency condition. Predetermined conditions are, for example, content conditions and frequency conditions.
　請求書情報の内容条件は、請求書が有する情報に関する条件である。請求書情報の内容条件は、例えば、「請求書情報が有する金額が閾値以上または閾値より大きいこと」「請求書が有する項目名（購入した商品名など）が、予め決められた項目名であること」である。頻度条件は、一の請求書情報に対応する２つのユーザ識別子の組の出現頻度が閾値以上または閾値より多いことである。なお、請求書情報に対応するユーザ識別子は、請求書情報と対になるユーザ識別子でも良いし、請求書情報に含まれる請求元識別情報、請求書情報に含まれる請求先識別情報でも良い。 　Conditions for the content of invoice information are conditions for the information contained in the invoice. The content conditions of the invoice information are, for example, ``the amount of the invoice information is equal to or greater than the threshold value'', and ``the item name of the invoice (such as the name of the product purchased) is a predetermined item name. That is. The frequency condition is that the appearance frequency of a pair of two user identifiers corresponding to one piece of billing information is equal to or greater than a threshold. Note that the user identifier corresponding to the bill information may be a user identifier paired with the bill information, billing source identification information included in the bill information, or billing destination identification information included in the bill information.
　交流情報決定部１３２は、例えば、格納部１１の１以上の契約書情報から、１以上の契約書情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の契約書情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の契約書情報から、予め決められた条件を満たす１以上の契約書情報を決定しても良い。予め決められた条件は、例えば、内容条件、頻度条件である。 The exchange information determination unit 132 determines one or more pieces of contract information from, for example, one or more pieces of contract information in the storage unit 11 . The interaction information determination unit 132 determines, for example, one or more pieces of contract information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the interaction information determination unit 132 may determine one or more pieces of contract information that satisfy a predetermined condition from among one or more pieces of contract information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, content conditions and frequency conditions.
　契約書情報の内容条件は、契約書が有する情報に関する条件である。契約書情報の内容条件は、例えば、「契約書情報が有する金額が閾値以上または閾値より大きいこと」「契約書が有するタイトルがが、予め決められた特定のタイトル（例えば、「共同研究契約書」「売買契約書」）であること、予め決められた特定のタイトル（例えば、「売買契約」）でないことである。契約書情報の頻度条件は、一の契約書情報に対応する２つのユーザ識別子の組の出現頻度が閾値以上または閾値より多いことである。なお、契約書情報に対応するユーザ識別子は、契約書情報と対になるユーザ識別子でも良いし、契約書情報に含まれる請求元識別情報、契約書情報に含まれる請求先識別情報でも良い。 The conditions for the content of the contract information are the conditions for the information contained in the contract. Content conditions of the contract information include, for example, ``the amount of money included in the contract information is equal to or greater than the threshold value'', and ``the title of the contract is a predetermined specific title (for example, ``collaborative research contract "Sales Agreement") and not a predetermined specific title (eg, "Sales Agreement"). The contract information frequency condition is that the frequency of appearance of a pair of two user identifiers corresponding to one piece of contract information is equal to or greater than a threshold. The user identifier corresponding to the contract information may be a user identifier paired with the contract information, or may be billing party identification information included in the contract information or billing party identification information included in the contract information.
　交流情報決定部１３２は、例えば、格納部１１の１以上の登録情報から、１以上の登録情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の登録情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の登録情報から、予め決められた条件を満たす１以上の登録情報を決定しても良い。予め決められた条件は、例えば、内容条件、頻度条件である。 For example, the exchange information determination unit 132 determines one or more registration information items from the one or more registration information items in the storage unit 11 . The interaction information determining unit 132 determines one or more pieces of registration information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example. For example, the exchange information determination unit 132 may determine one or more pieces of registration information that satisfy a predetermined condition from among one or more pieces of registration information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, content conditions and frequency conditions.
　登録情報の内容条件は、登録情報の内容に関する条件である。登録情報の内容条件は、例えば、「登録情報に対応するセミナーがビジネス向けのセミナーであること」である。ビジネス向けのセミナーか否かは、例えば、登録情報に対応するセミナーのタイトルを用いて決定される。交流情報決定部１３２は、例えば、登録情報に対応するセミナーのタイトルの中にビジネス用語が含まれる場合に、ビジネス向けのセミナーであると決定する。交流情報決定部１３２は、例えば、上述した予測処理であり、文字列であるセミナーのタイトルを機械学習の予測処理により、ビジネスか否かを示すクラスを取得する。登録情報の頻度条件は、一の登録情報に対応する２つのユーザ識別子の組の出現頻度が閾値以上または閾値より多いことである。なお、登録情報に対応するユーザ識別子は、登録情報に含まれるユーザ識別子（例えば、セミナーに申し込んだユーザの識別子）と、登録情報に対応するユーザ識別子（例えば、セミナーの主催者の識別子）である。 　Registration information content conditions are conditions related to the content of registration information. The content condition of the registration information is, for example, "the seminar corresponding to the registration information is a seminar for business". Whether or not the seminar is for business is determined using, for example, the title of the seminar corresponding to the registration information. For example, when a business term is included in the title of the seminar corresponding to the registered information, the interaction information determination unit 132 determines that the seminar is for business. For example, the exchange information determining unit 132 acquires a class indicating whether or not the seminar title, which is a character string, is a business or not through machine learning prediction processing, which is the prediction processing described above. The registration information frequency condition is that the appearance frequency of a pair of two user identifiers corresponding to one piece of registration information is equal to or greater than a threshold. The user identifier corresponding to the registration information is the user identifier included in the registration information (for example, the identifier of the user who applied for the seminar) and the user identifier corresponding to the registration information (for example, the identifier of the seminar organizer). .
　交流情報決定部１３２は、例えば、格納部１１の１以上の問合情報から、１以上の問合情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の問合情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の問合情報から、予め決められた条件を満たす１以上の問合情報を決定しても良い。予め決められた条件は、例えば、内容条件、頻度条件である。 The interaction information determination unit 132 determines one or more pieces of inquiry information from, for example, one or more pieces of inquiry information in the storage unit 11 . The interaction information determination unit 132 determines, for example, one or more pieces of inquiry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more pieces of inquiry information that satisfy a predetermined condition from among one or more pieces of inquiry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, content conditions and frequency conditions.
　問合情報の内容条件は、登録情報の内容に関する条件である。問合情報の内容条件は、例えば、問合情報が有する内容情報（文字列）がビジネスに関する内容の情報であることである。内容情報がビジネスに関する内容の情報であるか否かは、上述した文字列のクラス分類技術により判断可能である。 The content conditions of the inquiry information are conditions related to the content of the registration information. The content condition of the inquiry information is, for example, that the content information (character string) included in the inquiry information is information about the content of business. Whether or not the content information is business-related content information can be determined by the above-described character string class classification technique.
　交流情報決定部１３２は、例えば、格納部１１の１以上のギフト情報から、１以上のギフト情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のギフト情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のギフト情報から、予め決められた条件を満たす１以上のギフト情報を決定しても良い。予め決められた条件は、例えば、時期条件、内容条件である。 For example, the exchange information determination unit 132 determines one or more pieces of gift information from the one or more items of gift information in the storage unit 11 . The exchange information determination unit 132 determines, for example, one or more pieces of gift information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more pieces of gift information that satisfy a predetermined condition from among the one or more pieces of gift information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . The predetermined conditions are, for example, timing conditions and content conditions.
　ギフト情報の時期条件は、ギフト情報が有するギフト送付受領日に関する条件である。時期条件は、例えば、ギフト送付受領日がお中元期間（例えば、７月）の日であること、ギフト送付受領日がお歳暮期間（例えば、１２月）の日であること、ギフト送付受領日がクリスマスの時期（例えば、１２／２４から１２／２５）の日でないことである。 The timing conditions of the gift information are the conditions related to the gift sending and receiving date that the gift information has. The time conditions are, for example, that the date of receipt of the gift delivery falls on a day during the mid-year gift period (eg, July), that the date of receipt of the gift delivery falls on a day during the year-end gift period (eg, December), and that the date of receipt of the gift delivery falls on a day during the Christmas period. (for example, from 12/24 to 12/25).
　ギフト情報の内容条件は、ギフト情報が有する内容情報に関する条件である。内容条件は、例えば、ギフト情報が有する内容情報が特定の情報（例えば「開業祝」「設立祝」）を含むことである。 　Gift information content conditions are conditions related to content information possessed by gift information. The content condition is, for example, that the content information of the gift information includes specific information (for example, "opening celebration" or "establishment celebration").
　交流情報決定部１３２は、例えば、格納部１１の１以上の営業活動情報から、１以上の営業活動情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の営業活動情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の営業活動情報から、予め決められた条件を満たす１以上の営業活動情報を決定しても良い。予め決められた条件は、例えば、頻度条件、内容条件である。 The interaction information determination unit 132 determines one or more pieces of business activity information from, for example, one or more pieces of business activity information in the storage unit 11 . For example, the exchange information determination unit 132 determines one or more pieces of business activity information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more sales activity information items that satisfy a predetermined condition from the one or more sales activity information items corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, frequency conditions and content conditions.
　営業活動情報の頻度条件は、例えば、営業活動情報において、一の営業担当者に対応する一の顧客の営業顧客情報が閾値以上または閾値より多い数、存在すること（営業回数が多いこと）である。 The frequency condition of the sales activity information is, for example, that the number of sales customer information of one customer corresponding to one salesperson in the sales activity information is equal to or greater than a threshold or greater than the threshold (the number of sales is large). be.
　営業活動情報の内容条件は、例えば、営業活動情報が、営業の結果、成約したことを示す情報を含む場合である。 The content condition of the sales activity information is, for example, the case where the sales activity information includes information indicating that a contract has been concluded as a result of sales.
　交流情報決定部１３２は、例えば、格納部１１の１以上の顧客情報から、１以上の顧客情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の顧客情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の顧客情報から、予め決められた条件を満たす１以上の顧客情報を決定しても良い。予め決められた条件は、例えば、頻度条件、内容条件である。 The interaction information determination unit 132 determines one or more pieces of customer information from, for example, one or more pieces of customer information in the storage unit 11 . The interaction information determination unit 132 determines, for example, one or more pieces of customer information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more pieces of customer information that satisfy a predetermined condition from among the pieces of customer information corresponding to the user identifiers acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, frequency conditions and content conditions.
　顧客情報の頻度条件は、例えば、顧客情報において、一の担当者に対応する一の顧客の顧客情報が閾値以上または閾値より多い数、存在すること（担当者と顧客との関係の機会が多いこと）である。 The customer information frequency condition is, for example, that the customer information of one customer corresponding to one person in charge exists in a number equal to or greater than a threshold value (the number of opportunities for the relationship between the person in charge and the customer is high). that).
　顧客情報の内容条件は、例えば、顧客情報が、成約したことを示す情報を含む場合である。 Content conditions for customer information are, for example, when the customer information includes information indicating that a contract has been concluded.
　交流情報決定部１３２は、例えば、格納部１１の１以上の注文情報から、１以上の注文情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の注文情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の注文情報から、予め決められた条件を満たす１以上の注文情報を決定しても良い。予め決められた条件は、例えば、頻度条件、内容条件である。 The interaction information determination unit 132 determines one or more pieces of order information from, for example, one or more pieces of order information in the storage unit 11 . The interaction information determination unit 132 determines one or more items of order information corresponding to the user identifier acquired by the user identifier acquisition unit 131, for example. For example, the exchange information determination unit 132 may determine one or more pieces of order information that satisfy a predetermined condition from the one or more pieces of order information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, frequency conditions and content conditions.
　注文情報の頻度条件は、例えば、注文情報において、一の注文先に対応する一の発注者の発注者情報が閾値以上または閾値より多い数、存在すること（一の注文先に一の発注者が頻度高く注文していること）である。 The order information frequency condition is, for example, that the number of orderer information of one orderer corresponding to one orderer in the order information is greater than or equal to a threshold value (one orderer for one orderer) are ordering frequently).
　注文情報の内容条件は、例えば、注文情報が有する取引金額に関する条件、注文情報が有する商品名に関する条件である。取引金額に関する条件は、例えば、取引金額が閾値以上または閾値より大きいことである。商品名に関する条件は、例えば、商品名が予め決められた商品名であることである。 The content conditions of the order information are, for example, the conditions related to the transaction amount contained in the order information and the conditions related to the product name contained in the order information. The condition regarding the transaction amount is, for example, that the transaction amount is greater than or equal to a threshold. The condition regarding the product name is, for example, that the product name is a predetermined product name.
　交流情報決定部１３２は、例えば、格納部１１の１以上の採用情報から、１以上の採用情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の採用情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の採用情報から、予め決められた条件を満たす１以上の採用情報を決定しても良い。予め決められた条件は、例えば、内容条件である。 The exchange information determination unit 132 determines one or more pieces of employment information from, for example, one or more pieces of employment information in the storage unit 11 . The exchange information determining unit 132 determines one or more pieces of employment information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example. For example, the exchange information determination unit 132 may determine one or more pieces of employment information that satisfy a predetermined condition from among one or more pieces of employment information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . A predetermined condition is, for example, a content condition.
　採用情報の内容条件は、例えば、採用情報が有する応募内容情報に関する条件、または採用情報が有する結果情報に関する条件である。応募内容情報に関する条件は、例えば、職種が特定の職種であること、正社員か否かを示す情報が「正社員」であることである。結果情報に関する条件は、例えば、段階情報が採用のステップの特定の段階までいったことを示す情報であること、面接実施情報が「面接を行ったこと」を示す情報であること、採用結果情報が「採用に至った」ことを示す情報であることである。 The content conditions of the employment information are, for example, the conditions related to the application content information contained in the employment information, or the conditions related to the result information contained in the employment information. The conditions for the application content information are, for example, that the occupation is a specific occupation, and that the information indicating whether or not the applicant is a regular employee is "regular employee." Conditions related to the result information are, for example, that the stage information is information indicating that the hiring step has reached a specific stage, that the interview implementation information is information that indicates that an interview was conducted, and that the recruitment result information. is information that indicates that the applicant has been "adopted".
　交流情報決定部１３２は、例えば、格納部１１の１以上のパンフレット取得情報から、１以上のパンフレット取得情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のパンフレット取得情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のパンフレット取得情報から、予め決められた条件を満たす１以上のパンフレット取得情報を決定しても良い。予め決められた条件は、例えば、内容条件である。 The exchange information determination unit 132 determines one or more pamphlet acquisition information from, for example, one or more pamphlet acquisition information in the storage unit 11 . For example, the exchange information determination unit 132 determines one or more pieces of pamphlet acquisition information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more pamphlet acquisition information that satisfies a predetermined condition from one or more pamphlet acquisition information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . A predetermined condition is, for example, a content condition.
　パンフレット取得情報の内容条件は、例えば、パンフレット取得情報が有する内容情報に関する条件、種類情報に関する条件である。内容情報に関する条件は、例えば、内容情報がビジネス用語を含むことである。種類情報に関する条件は、例えば、種類情報が予め決められた種類の情報であることである。 The content conditions of the pamphlet acquisition information are, for example, the conditions related to the content information and the type information contained in the pamphlet acquisition information. A condition regarding the content information is, for example, that the content information includes business terms. The condition regarding the type information is, for example, that the type information is information of a predetermined type.
　交流情報決定部１３２は、例えば、格納部１１の１以上の経費情報から、１以上の経費情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の経費情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の経費情報から、予め決められた条件を満たす１以上の経費情報を決定しても良い。予め決められた条件は、例えば、内容条件、頻度条件である。 The exchange information determination unit 132 determines one or more pieces of expense information from, for example, one or more items of expense information in the storage unit 11 . The exchange information determination unit 132 determines, for example, one or more pieces of expense information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the exchange information determination unit 132 may determine one or more expense information items that satisfy a predetermined condition from among the one or more expense information items corresponding to the user identifiers acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, content conditions and frequency conditions.
　経費情報の内容条件は、例えば、経費の科目が予め決められた科目であること、金額が閾値以上または閾値より大きいこと、購入した商品等の種類が予め決められた種類であることである。 The content conditions for the expense information are, for example, that the item of expense is a predetermined item, that the amount is equal to or greater than the threshold, and that the type of product purchased is of a predetermined type.
　経費情報の頻度条件は、一の申請者が閾値以上または閾値より多い回数、経費の申請をしていること、単位期間に、一の申請者が閾値以上または閾値より多い回数、経費の申請をしていることである。 The frequency condition of expense information is that one applicant applies for expenses more than or equal to the threshold, and that one applicant applies for expenses more than or equal to the threshold in a unit period. It is what we are doing.
　交流情報決定部１３２は、例えば、格納部１１の１以上のアンケート情報から、１以上のアンケート情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のアンケート情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のアンケート情報から、予め決められた条件を満たす１以上のアンケート情報を決定しても良い。予め決められた条件は、例えば、内容条件、頻度条件である。 The interaction information determination unit 132 determines one or more pieces of questionnaire information from, for example, one or more pieces of questionnaire information in the storage unit 11 . The interaction information determination unit 132 determines, for example, one or more pieces of questionnaire information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . For example, the interaction information determination unit 132 may determine one or more pieces of questionnaire information that satisfy a predetermined condition from among one or more pieces of questionnaire information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . Predetermined conditions are, for example, content conditions and frequency conditions.
　アンケート情報の内容条件は、例えば、回答情報を含むこと、回答情報が予め決められた条件を満たすことである。 The conditions for the contents of the questionnaire information are, for example, that it contains answer information and that the answer information satisfies predetermined conditions.
　アンケート情報の頻度条件は、例えば、一のユーザが閾値以上または閾値より多い回数、アンケートの回答を送信してきていることである。 The condition for the frequency of questionnaire information is, for example, that one user has sent answers to the questionnaire more than or equal to the threshold.
　交流情報決定部１３２は、例えば、格納部１１の１以上の入館情報から、１以上の入館情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の入館情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上の入館情報から、予め決められた条件を満たす１以上の入館情報を決定しても良い。予め決められた条件は、例えば、頻度条件である。 The interaction information determination unit 132 determines one or more pieces of admission information from, for example, one or more pieces of admission information in the storage unit 11 . The interaction information determining unit 132 determines, for example, one or more pieces of museum admission information corresponding to the user identifier acquired by the user identifier acquiring unit 131 . For example, the exchange information determination unit 132 may determine one or more pieces of hall entry information that satisfy a predetermined condition from the one or more pieces of hall entry information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . A predetermined condition is, for example, a frequency condition.
　入館情報の頻度条件は、例えば、一のユーザ識別子に対応付く入館情報が、閾値以上または閾値より多い数、存在すること（多い回数、入館したこと）である。 The condition for the frequency of admission information is, for example, that the number of admission information associated with one user identifier is greater than or equal to a threshold (the number of visits to the facility is large).
　交流情報決定部１３２は、例えば、格納部１１の１以上のチェックイン情報から、１以上のチェックイン情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のチェックイン情報を決定する。交流情報決定部１３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子に対応する１以上のチェックイン情報から、予め決められた条件を満たす１以上のチェックイン情報を決定しても良い。予め決められた条件は、例えば、頻度条件である。 The exchange information determination unit 132 determines one or more pieces of check-in information from, for example, one or more pieces of check-in information in the storage unit 11 . The interaction information determining unit 132 determines one or more pieces of check-in information corresponding to the user identifier acquired by the user identifier acquiring unit 131, for example. For example, the exchange information determination unit 132 may determine one or more pieces of check-in information that satisfy a predetermined condition from among one or more pieces of check-in information corresponding to the user identifier acquired by the user identifier acquisition unit 131 . A predetermined condition is, for example, a frequency condition.
　チェックイン情報の頻度条件は、例えば、一のユーザ識別子に対応付くチェックイン情報が、閾値以上または閾値より多い数、存在すること（多い回数、チェックインしたこと）である。 The check-in information frequency condition is, for example, that the number of check-in information associated with one user identifier is greater than or equal to a threshold (a large number of check-ins).
　質問部１３３は、交流関係情報を蓄積するか否かをユーザに問い合わせる。ユーザに問い合わせることは、例えば、ユーザの端末装置３に送信することであるが、積極的な問合せで無くても良く、問合せ方法は問わない。また、ユーザへのかかる問い合わせのタイミングやトリガーも問わない。 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, for example, one user identifier corresponding to the interaction information acquired by the interaction information determination unit 132 . Further, the other user information acquisition unit 134 acquires other user information including, for example, another user identifier that is different from the one user identifier and that corresponds to the interaction information acquired by the interaction information determination unit 132. . Here, the acquisition of one user identifier by the other user information acquisition unit 134 may be acquisition of one user identifier acquired by the user identifier acquisition unit 131, or acquisition of the interaction information acquired by the interaction information determination unit 132. may be used to obtain one user identifier. Acquiring one user identifier may be information identified by one user identifier, information about the user, and information constituting interaction information.
　他ユーザ情報取得部１３４は、例えば、交流情報を用いて、他ユーザ情報を取得する。他ユーザ情報取得部１３４は、例えば、交流情報に対応する情報を用いて、他ユーザ情報を取得する。 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.
　他ユーザ情報取得部１３４は、コミュニケーションシステム情報を用いて、他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires other user information using the communication system information.
　交流情報決定部１３２は、非コミュニケーションシステム情報を用いて、他ユーザ情報を取得する。 The exchange information determination unit 132 uses the non-communication system information to acquire other user information.
　以下、交流情報の種類ごとの他ユーザ情報取得部１３４の動作を説明する。
（１）交流情報がメールである場合 The operation of the other user information acquisition unit 134 for each type of exchange information will be described below.
(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.
　なお、他ユーザ情報取得部１３４がメールの中からシグネチャーの文字列を検知する方法は問わない。他ユーザ情報取得部１３４は、例えば、メールの中の文字を有する最下位の行から上の行を検査し、文字を有さない空行を検知し、当該空行の次の行から文字を有する最下位の行までをシグネチャーの領域の文字列として取得する。他ユーザ情報取得部１３４は、例えば、メールの１行目から検査し、所定の文字列を有する行であるシグネチャー区切り行（例えば、文字“＊”または“━”または”＋”等）を連続して所定数以上有する行）の次の行から、当該行の下位行であるシグネチャー区切り行の一つ上の行までをシグネチャーの領域の文字列として取得する。他ユーザ情報取得部１３４は、例えば、メールの中の特定の文字列を含む行（例えば、「Best Regards」「よろしくお願いいたします。」等を含む行）の直下の所定数の行の文字列をシグネチャーの領域の文字列として取得する。 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 of .
　他ユーザ情報取得部１３４は、例えば、当該組織識別子とメールの中の氏名を用いて、ユーザ情報格納部１１１を検索し、マッチするユーザ情報が有する１以上のユーザ属性値を有する他ユーザ情報を取得する。 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 .
(5) When exchange information is chat history information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したチャット履歴情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したチャット履歴情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the chat history information determined by the exchange information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the chat history information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチャット履歴情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。かかる１以上の各ユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザとチャットで交流したユーザの識別子である。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を含む１以上の他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the chat history information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has interacted with the user identified by the user identifier acquired by the user identifier acquisition unit 131 through chat. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチャット履歴情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子をキーとして、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the chat history information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more of the acquired user identifiers as a key, and obtains part or all of the matching user information. Get user information.
　なお、他ユーザ情報取得部１３４が一のユーザ識別子を取得する場合、他ユーザ情報取得部１３４が他ユーザ情報を取得する方法と同じ方法（例えば、ユーザ情報格納部１１１を検索する方法）で取得することは好適である。
（６）交流情報が通話履歴情報である場合 In addition, when the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to
(6) When exchange information is call history information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した通話履歴情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した通話履歴情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the call history information determined by the exchange information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the call history information determined by the exchange information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した通話履歴情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。かかる１以上の各ユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザと電話で通話したユーザの識別子である。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を含む１以上の他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the call history information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has made a telephone call with the user identified by the user identifier acquired by the user identifier acquisition unit 131 . Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した通話履歴情報に対応付いている１または２以上のユーザ識別子（例えば、電話番号）であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子をキーとして、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers (for example, telephone numbers) associated with the call history information determined by the interaction information determination unit 132, and the user identifier acquisition unit 131 acquires Acquire one or more user identifiers paired with the user identifier. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more of the acquired user identifiers as a key, and obtains part or all of the matching user information. Get user information.
　他ユーザ情報取得部１３４は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる通話履歴情報に含まれる文字列を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該文字列（例えば、「もしもし　Ａ株式会社の山田太郎さんは居られますか？　・・・」）を形態素解析し、当該解析結果から、１以上の属性値を取得し、当該１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。なお、１以上の属性値は、例えば、会社名（例えば、「Ａ株式会社」）、氏名（例えば、「山田太郎」）、名前（例えば、「山田」）である。 For example, the other user information acquisition unit 134 acquires a character string included in the call history information paired with the user identifier acquired by the user identifier acquisition unit 131. Next, the other user information acquisition unit 134, for example, performs morphological analysis on the character string (for example, "Hello, Mr. Taro Yamada from A Co., Ltd. is there?"), and from the analysis result, 1 The above attribute values are acquired, the user information storage unit 111 is searched using the one or more attribute values, and other user information having part or all of the matching user information is acquired. Note that the one or more attribute values are, for example, a company name (eg, "A Corporation"), a name (eg, "Taro Yamada"), and a name (eg, "Yamada").
　なお、他ユーザ情報取得部１３４が一のユーザ識別子を取得する場合、他ユーザ情報取得部１３４が他ユーザ情報を取得する方法と同じ方法（例えば、ユーザ情報格納部１１１を検索する方法）で取得することは好適である。
（７）交流情報が請求書情報である場合 In addition, when the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to
(7) When exchange information is invoice information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した請求書情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した請求書情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the invoice information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the invoice information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した請求書情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。かかる１以上の各ユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザと請求書のやり取りをしたユーザの識別子である。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を含む１以上の他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the invoice information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has exchanged bills with the user identified by the user identifier acquired by the user identifier acquisition unit 131 . Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した請求書情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the invoice information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more acquired user identifiers, and obtains a part or all of the matching user information. Get user information.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した請求書情報から１以上の属性値（例えば、会社名、部署名、代表者の氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more attribute values (eg, company name, department name, representative name) from the invoice information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more attribute values, and obtains other user information having part or all of the matching user information. to get
　なお、他ユーザ情報取得部１３４が一のユーザ識別子を取得する場合、他ユーザ情報取得部１３４が他ユーザ情報を取得する方法と同じ方法（例えば、ユーザ情報格納部１１１を検索する方法）で取得することは好適である。
（８）交流情報が契約書情報である場合 In addition, when the other user information acquisition unit 134 acquires one user identifier, it is acquired by the same method as the method by which the other user information acquisition unit 134 acquires other user information (for example, a method of searching the user information storage unit 111). It is preferable to
(8) When exchange information is contract information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した契約書情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した契約書情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the contract information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the contract information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した契約書情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。かかる１以上の各ユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザと契約を交わしたユーザまたは契約を交わすユーザの識別子である。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を含む１以上の他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the contract information determined by the exchange information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Obtain one or more user identifiers. Each of the one or more user identifiers is an identifier of a user who has made a contract with the user identified by the user identifier acquired by the user identifier acquisition unit 131 or who has made a contract. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した契約書情報から１以上の属性値（例えば、契約書情報の中に存在する甲または乙に対応する会社名、甲または乙に対応する代表者の氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の属性値を含む他ユーザ情報を取得する。 Other user information acquisition unit 134, for example, from the contract information determined by exchange information determination unit 132, one or more attribute values name of the representative corresponding to Next, the other user information acquisition unit 134 acquires other user information including the one or more attribute values, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した契約書情報から１以上の属性値（例えば、契約書情報の中に存在する甲または乙に対応する会社名、甲または乙に対応する代表者の氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 Other user information acquisition unit 134, for example, from the contract information determined by exchange information determination unit 132, one or more attribute values name of the representative corresponding to Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more attribute values, and obtains other user information having part or all of the matching user information. to get
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した契約書情報から１以上の属性値（例えば、契約書情報の中に存在する甲および乙に対応する会社名、甲および乙に対応する代表者の氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該甲の１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する一のユーザのユーザ情報を取得する。なお、一のユーザのユーザ情報は、一のユーザのユーザ識別子でも良く、一のユーザのユーザ識別子を含んでいても良い。また、他ユーザ情報取得部１３４は、例えば、当該乙の１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。また、上記において、甲と乙とを入れ替えても良い。
（９）交流情報が登録情報である場合 Other user information acquisition unit 134, for example, from the contract information determined by exchange information determination unit 132, one or more attribute values name of the representative corresponding to Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more attribute values of A, and finds one that has some or all of the matching user information. Get the user information of the user of . Note that the user information of one user may be the user identifier of one user, or may include the user identifier of one user. In addition, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, one or more attribute values of the user B, and searches other users having part or all of the matching user information Get information. In addition, in the above, A and B may be exchanged.
(9) When exchange information is registered information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した登録情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した登録情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the registration information determined by the interaction information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the registration information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した登録情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。かかる１以上の各ユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子で識別されるユーザとイベントで交流のあったユーザの識別子である。次に、他ユーザ情報取得部１３４は、例えば、取得した１以上の各ユーザ識別子を含む１以上の他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the registration information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Acquire the above user identifiers. Each of the one or more user identifiers is an identifier of a user who interacted with the user identified by the user identifier acquired by the user identifier acquisition unit 131 at the event. Next, the other user information acquisition unit 134 acquires, for example, one or more other user information including each of the acquired one or more user identifiers.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した登録情報に対応付いている１または２以上のユーザ識別子であり、ユーザ識別子取得部１３１が取得したユーザ識別子と対になる１以上のユーザ識別子を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の各ユーザ識別子を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 is, for example, one or more user identifiers associated with the registration information determined by the interaction information determination unit 132, and is paired with the user identifier acquired by the user identifier acquisition unit 131. Acquire the above user identifiers. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more user identifiers, and searches for other users having part or all of the matching user information. Get information.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した登録情報が有する１以上の属性値（例えば、会社名、部署名、氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の属性値を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more attribute values (eg, company name, department name, name) of the registration information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more attribute values, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した登録情報が有する１以上の属性値（例えば、会社名、部署名、氏名）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。
（１０）交流情報が問合情報である場合 The other user information acquisition unit 134 acquires, for example, one or more attribute values (for example, company name, department name, name) of the registration information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more attribute values, and obtains other user information having part or all of the matching user information. to get
(10) When exchange information is inquiry information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した問合情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した問合情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the inquiry information determined by the exchange information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the inquiry information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した問合情報が有する１以上の質問者属性値（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の質問者属性値を含む他ユーザ情報を取得する。 Other user information acquisition unit 134, for example, one or more questioner attribute values (eg, name, company name, department name, title, email address, telephone number) possessed by the inquiry information determined by the interaction information determination unit 132 get. Next, the other user information acquisition unit 134 acquires other user information including the one or more questioner attribute values, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した問合情報が有する１以上の質問者属性値（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の質問者属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。
（１１）交流情報がギフト情報である場合 Other user information acquisition unit 134, for example, one or more questioner attribute values (eg, name, company name, department name, title, email address, telephone number) possessed by the inquiry information determined by the interaction information determination unit 132 get. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more questioner attribute values, and has part or all of the matching user information Get user information.
(11) When exchange information is gift information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したギフト情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したギフト情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the gift information determined by the exchange information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the gift information determined by the exchange information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したギフト情報が有する１以上の受贈者属性値（例えば、氏名、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の受贈者属性値を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more beneficiary attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more beneficiary attribute values, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したギフト情報が有する１以上の贈呈者属性値（例えば、氏名、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の贈呈者属性値を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more presenter attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the one or more presenter attribute values, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したギフト情報が有する１以上の受贈者属性値（例えば、氏名、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の受贈者属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more beneficiary attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more beneficiary attribute values, and obtains part or all of the matching user information. Get user information.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したギフト情報が有する１以上の贈呈者属性値（例えば、氏名、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の贈呈者属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more presenter attribute values (eg, name, email address, phone number) included in the gift information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more presenter attribute values, and obtains a part or all of the matching user information. Get user information.
　なお、他ユーザ情報取得部１３４は、上述した贈呈者に対応するユーザ情報の一部または全部の情報を一のユーザの情報として取得し、上述した受贈者に対応するユーザ情報の一部または全部の情報を他ユーザ情報として取得しても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 acquires part or all of the user information corresponding to the above-described gift giver as information of one user, and obtains part or all of the user information corresponding to the above-described beneficiary. information may be acquired as other user information. Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した受贈者に対応するユーザ情報の一部または全部の情報を一のユーザの情報として取得し、上述した贈呈者に対応するユーザ情報を他ユーザ情報として取得しても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１２）交流情報が営業活動情報である場合 Further, the other user information acquisition unit 134 acquires part or all of the user information corresponding to the above-described giftee as information of one user, and acquires the above-described user information corresponding to the giftee as other user information. You can get it. User information of such one user corresponds to one user identifier.
(12) When exchange information is sales activity information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した営業活動情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した営業活動情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the business activity information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the business activity information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した営業活動情報が有する１以上の顧客の情報（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の顧客の情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more customer information (eg, name, company name, department name, title, email address, phone number) included in the business activity information determined by the interaction information determination unit 132. do. Next, the other user information acquisition unit 134 acquires other user information including information on the one or more customers, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した営業活動情報が有する営業担当者情報（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該営業担当者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, sales person information (eg, name, company name, department name, title, email address, telephone number) included in the sales activity information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the salesperson information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した営業活動情報が有する１以上の顧客の情報（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の顧客の情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more customer information (eg, name, company name, department name, title, email address, phone number) included in the business activity information determined by the interaction information determination unit 132. do. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the information of the one or more customers, for example, and searches for other users who have part or all of the matching user information. Get information.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した営業活動情報が有する営業担当者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該営業担当者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, salesperson information included in the sales activity information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the salesperson information, and obtains other user information having part or all of the matching user information. get.
　なお、他ユーザ情報取得部１３４は、上述した顧客の情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した営業担当者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 may associate the other user information acquired using the customer information described above with the other user information acquired using the salesperson information described above as information on one user. good. Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した顧客の情報を用いて取得する他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１３）交流情報が顧客情報である場合 Moreover, the other user information acquisition part 134 may match with other user information acquired using the customer's information mentioned above. User information of such one user corresponds to one user identifier.
(13) When exchange information is customer information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した顧客情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した顧客情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the customer information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the customer information determined by the interaction information determination unit 132 . Note that such one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した顧客情報が有する１以上の顧客属性値（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の顧客の情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more customer attribute values (eg, name, company name, department name, title, email address, phone number) of the customer information determined by the interaction information determination unit 132. . Next, the other user information acquisition unit 134 acquires other user information including information on the one or more customers, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した顧客情報が有する担当者情報（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, the person in charge information (eg, name, company name, department name, title, email address, telephone number) included in the customer information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した顧客情報が有する１以上の顧客属性値（例えば、氏名、会社名、部署名、役職、メールアドレス、電話番号）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該１以上の顧客属性値を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, one or more customer attribute values (eg, name, company name, department name, title, email address, phone number) of the customer information determined by the interaction information determination unit 132. . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the one or more customer attribute values, and searches for other users having part or all of the matching user information. Get information.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した顧客情報が有する担当者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, the person in charge information included in the customer information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した担当者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した１以上の顧客属性値を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 In addition, the other user information acquisition unit 134 treats the other user information acquired using the person in charge information described above as the information of one user, and associates it with the other user information acquired using the one or more customer attribute values described above. can be Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した１以上の顧客属性値を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した担当者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１４）交流情報が注文情報である場合 In addition, the other user information acquisition unit 134 treats the other user information acquired using the one or more customer attribute values described above as information of one user, and associates the other user information acquired using the person in charge information described above with the other user information. can be User information of such one user corresponds to one user identifier.
(14) When exchange information is order information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した注文情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した注文情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the order information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the order information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した注文情報が有する発注者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該発注者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, orderer information (for example, name, address, telephone number, email address) included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the orderer information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した注文情報が有する注文先情報（例えば、氏名、会社名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該注文先情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, order destination information (for example, name, company name, address, telephone number, email address) included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the order destination information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した注文情報が有する発注者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該発注者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, orderer information included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the orderer information, for example, and acquires other user information having part or all of the matching user information. do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した注文情報が有する注文先情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該注文先情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 For example, the other user information acquisition unit 134 acquires order destination information included in the order information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the orderer information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した発注者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した注文先情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 may regard the other user information acquired using the orderer information described above as the information of one user, and associate it with the other user information acquired using the order destination information described above. . Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した注文先情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した発注者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１４）交流情報が採用情報である場合 In addition, the other user information acquisition unit 134 may regard the other user information acquired using the order destination information described above as the information of one user and associate it with the other user information acquired using the orderer information described above. . User information of such one user corresponds to one user identifier.
(14) When exchange information is employment information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した採用情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した採用情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the employment information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the employment information determined by the exchange information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した採用情報が有する応募者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該応募者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, applicant information (eg, name, address, phone number, email address) included in the employment information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the applicant information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した採用情報が有する応募先情報が有する担当者の情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者の情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, the information (eg, name, email address) of the person in charge contained in the applicant information contained in the employment information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including, for example, the information of the person in charge.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した採用情報が有する応募者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該応募者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, applicant information included in the employment information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the applicant information, and acquires other user information having part or all of the matching user information. do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した採用情報が有する応募先情報が有する担当者の情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者の情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 For example, the other user information acquisition unit 134 acquires the information of the person in charge contained in the applicant information contained in the employment information determined by the exchange information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the information of the person in charge, and obtains other user information having part or all of the matching user information. get.
　なお、他ユーザ情報取得部１３４は、上述した応募者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した担当者の情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 In addition, the other user information acquisition unit 134 may associate the other user information acquired using the applicant information described above with the other user information acquired using the information of the person in charge described above as information of one user. good. Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した担当者の情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した応募者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１５）交流情報がパンフレット取得情報である場合 In addition, the other user information acquisition unit 134 may associate the other user information acquired using the above-described information of the person in charge with the other user information acquired using the above-described applicant information as the information of one user. good. User information of such one user corresponds to one user identifier.
(15) When exchange information is pamphlet acquisition information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したパンフレット取得情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したパンフレット取得情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the pamphlet acquisition information determined by the interaction information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the pamphlet acquisition information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したパンフレット取得情報が有する取得者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該取得者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires acquirer information (for example, name, address, telephone number, email address) included in the pamphlet acquisition information determined by the interaction information determination unit 132, for example. Next, the other user information acquisition unit 134 acquires other user information including the acquirer information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したパンフレット取得情報が有する提供企業の担当者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, information on the person in charge of the providing company (eg, name, email address) included in the pamphlet acquisition information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したパンフレット取得情報が有する取得者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該取得者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires acquirer information included in the pamphlet acquisition information determined by the interaction information determination unit 132, for example. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the acquirer information, for example, and acquires other user information having part or all of the matching user information. do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したパンフレット取得情報が有する担当者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, person-in-charge information included in the pamphlet acquisition information determined by the exchange information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した取得者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した担当者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 It should be noted that the other user information acquisition unit 134 may regard the other user information acquired using the acquirer information described above as the information of one user, and associate it with the other user information acquired using the person in charge information described above. . Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した担当者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した取得者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１６）交流情報が経費情報である場合 Further, the other user information acquisition unit 134 may set the other user information acquired using the person in charge information described above as the information of one user, and may associate it with the other user information acquired using the acquirer information described above. . User information of such one user corresponds to one user identifier.
(16) When exchange information is expense information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した経費情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した経費情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the expense information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the expense information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した経費情報が有する申請者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該申請者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires applicant information (eg, name, address, phone number, email address) included in the expense information determined by the interaction information determination unit 132, for example. Next, other user information acquisition part 134 acquires other user information including the applicant information concerned, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した経費情報が有する許可者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該許可者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, authorized person information (eg, name, email address) included in the expense information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the authorized person information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した経費情報が有する申請者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該申請者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, the applicant information included in the expense information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the applicant information, for example, and acquires other user information having part or all of the matching user information do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した経費情報が有する許可者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該許可者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 For example, the other user information acquisition unit 134 acquires the permitter information included in the expense information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the authorized person information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した申請者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した許可者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 may set the other user information acquired using the applicant information described above as the information of one user, and may associate it with the other user information acquired using the permitter information described above. . Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した許可者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した申請者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１７）交流情報がアンケート情報である場合 Further, the other user information acquisition unit 134 may set the other user information acquired using the above-described permitter information as information of one user, and may associate the other user information acquired using the above-described applicant information. . User information of such one user corresponds to one user identifier.
(17) When exchange information is questionnaire information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したアンケート情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したアンケート情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the questionnaire information determined by the interaction information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the questionnaire information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したアンケート情報が有する回答者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該回答者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, respondent information (eg, name, address, phone number, email address) included in the questionnaire information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the answerer information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したアンケート情報が有する実施者情報に含まれる担当者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, person-in-charge information (eg, name, email address) included in the information on the person conducting the questionnaire contained in the questionnaire information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the person in charge information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したアンケート情報が有する回答者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該回答者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, respondent information included in the questionnaire information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the answerer information, for example, and acquires other user information having part or all of the matching user information do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したアンケート情報が有する担当者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該担当者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, the person-in-charge information included in the questionnaire information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the person-in-charge information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した回答者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した担当者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 In addition, the other user information acquisition unit 134 may set the other user information acquired using the respondent information described above as the information of one user and associate it with the other user information acquired using the person in charge information described above. . Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した担当者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した回答者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１８）交流情報が入館情報である場合 In addition, the other user information acquisition unit 134 may set the other user information acquired using the person in charge information described above as the information of one user, and associate it with the other user information acquired using the respondent information described above. . User information of such one user corresponds to one user identifier.
(18) When exchange information is admission information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した入館情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定した入館情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the building entry information determined by the exchange information determination unit 132 . The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the admission information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する入館者情報（例えば、氏名、住所、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該入館者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, visitor information (eg, name, address, phone number, email address) included in the admission information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 acquires other user information including the visitor information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する代表者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該代表者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, representative information (eg, name, email address) included in the admission information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the representative information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する管理者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該管理者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, administrator information (eg, name, email address) included in the admission information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the administrator information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する入館者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該入館者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, visitor information included in the admission information determined by the interaction information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the visitor information, for example, and acquires other user information having part or all of the matching user information. do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する代表者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該代表者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, representative information included in the admission information determined by the exchange information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the representative information, and acquires other user information having part or all of the matching user information. do.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定した入館情報が有する管理者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該管理者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, administrator information included in the building entry information determined by the exchange information determination unit 132 . Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the administrator information, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述した入館者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した代表者情報または管理者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 treats the other user information acquired using the visitor information described above as the information of one user, and corresponds to the other user information acquired using the representative information or administrator information described above. You can attach it. Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した代表者情報または管理者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した入館者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。
（１９）交流情報がチェックイン情報である場合 In addition, the other user information acquisition unit 134 treats the other user information acquired using the above-described representative information or administrator information as information of one user, and corresponds to the other user information acquired using the above-described visitor information. You can attach it. User information of such one user corresponds to one user identifier.
(19) When exchange information is check-in information
　他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したチェックイン情報に対応する他ユーザ情報を取得する。他ユーザ情報取得部１３４は、交流情報決定部１３２が決定したチェックイン情報に対応する一のユーザ識別子と他ユーザ情報とを取得しても良い。なお、かかる一のユーザ識別子は、ユーザ識別子取得部１３１が取得したユーザ識別子であっても良い。 The other user information acquisition unit 134 acquires other user information corresponding to the check-in information determined by the interaction information determination unit 132. The other user information acquisition unit 134 may acquire one user identifier and other user information corresponding to the check-in information determined by the interaction information determination unit 132 . Note that the one user identifier may be the user identifier acquired by the user identifier acquisition unit 131 .
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチェックイン情報が有するチェックイン者情報（例えば、氏名、電話番号、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該チェックイン者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, check-in person information (eg, name, phone number, email address) included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the check-in person information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチェックイン情報が有する運営者情報（例えば、氏名、メールアドレス）を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該運営者情報を含む他ユーザ情報を取得する。 The other user information acquisition unit 134, for example, acquires operator information (eg, name, email address) included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 acquires other user information including the operator information, for example.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチェックイン情報が有するチェックイン者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該チェックイン者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 The other user information acquisition unit 134 acquires, for example, check-in person information included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using, for example, the check-in person information, and searches for other user information having part or all of the matching user information. get.
　他ユーザ情報取得部１３４は、例えば、交流情報決定部１３２が決定したチェックイン情報が有する運営者情報を取得する。次に、他ユーザ情報取得部１３４は、例えば、当該運営者情報を用いて、ユーザ情報格納部１１１を検索し、合致するユーザ情報のうちの一部または全部の情報を有する他ユーザ情報を取得する。 For example, the other user information acquisition unit 134 acquires operator information included in the check-in information determined by the interaction information determination unit 132. Next, the other user information acquisition unit 134 searches the user information storage unit 111 using the operator information, for example, and acquires other user information having part or all of the matching user information. do.
　なお、他ユーザ情報取得部１３４は、上述したチェックイン者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述した運営者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザの情報は、一のユーザ識別子に対応する。 Note that the other user information acquisition unit 134 may associate the other user information acquired using the check-in person information described above with the other user information acquired using the operator information described above as information of one user. good. Such one user information corresponds to one user identifier.
　また、他ユーザ情報取得部１３４は、上述した運営者情報を用いて取得する他ユーザ情報を一のユーザの情報とし、上述したチェックイン者情報を用いて取得した他ユーザ情報に対応付けても良い。かかる一のユーザのユーザ情報は、一のユーザ識別子に対応する。 Further, the other user information acquisition unit 134 may associate the other user information acquired using the operator information described above with the other user information acquired using the check-in person information described above as information of one user. good. User information of such one user corresponds to one user identifier.
　交流関係蓄積部１３５は、他ユーザ情報とユーザ識別子とを対応付ける交流関係情報を蓄積する。なお、ここでの他ユーザ情報は、他ユーザ情報取得部１３４が取得した情報である。また、ここでのユーザ識別子は、例えば、ユーザ識別子取得部１３１が取得した情報である。また、ユーザ識別子は、例えば、他ユーザ情報取得部１３４が取得した情報でも良い。 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, for example, information acquired by the user identifier acquiring unit 131 . Also, the user identifier may be information acquired by the other user information acquiring unit 134, for example.
　交流関係蓄積部１３５は、例えば、ユーザ識別子に対応付けて、他ユーザ情報取得部１３４が取得した他ユーザ情報である交流関係情報を蓄積する。 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.
　交流関係蓄積部１３５は、例えば、ユーザ識別子と他ユーザ情報取得部１３４が取得した他ユーザ情報とを有する交流関係情報を蓄積する。 The interaction relationship storage unit 135 stores, for example, interaction relationship information having a user identifier and 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 the other user information acquired by the other user information acquisition unit 134, in association with the user identifier.
　交流関係蓄積部１３５が交流関係情報を蓄積する先は、問わない。交流関係蓄積部１３５は、例えば、交流関係格納部１１４に交流関係情報を蓄積する。ただし、交流関係蓄積部１３５は、図示しない他の装置に交流関係情報を蓄積しても良い。交流関係蓄積部１３５は、交流関係情報を利用する装置に交流関係情報を蓄積することは好適である。 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.
　なお、予め決められた処理とは、異動情報の通知、異動情報のウェブページへの掲載、変化があった他ユーザ情報または当該他ユーザ情報に含まれる１以上のユーザ属性値を送信することなどである。異動情報とは、ユーザが異動になったこと、ユーザに変化があったこと等を示す情報である。また、異動情報は、変化後の１以上のユーザ属性値を含むことは好適である。ただし、異動情報は、例えば、氏名と変化があったことを示す情報だけでも良い。異動情報の通知とは、他ユーザの異動情報を、お知らせする処理である。 Predetermined processing includes notification of change information, posting of change information on a web page, transmission of other user information that has changed, or one or more user attribute values included in the other user information. is. 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. Each email is associated with, for example, the email address of the recipient who receives the email. 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.
　情報サーバ２がチャットサーバである場合、サーバ格納部２１には、１または２以上のチャット履歴情報が格納される。チャット履歴情報には、チャットを行った１以上の各ユーザのユーザ識別子が対応付いている。なお、一のユーザのチャットサーバのユーザ識別子と、一のユーザの交流管理装置１が使用するユーザ識別子とは、異なっていても良い。ただし、２つのユーザ識別子が異なっている場合、格納部１１には、２つのユーザ識別子の対応が管理されている、とする。 When the information server 2 is a chat server, the server storage unit 21 stores one or more pieces of chat history information. The chat history information is associated with user identifiers of one or more users who have chatted. The user identifier of one user's chat 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 telephone server, the server storage unit 21 stores one or more pieces of call history information. The call history information is associated with user identifiers of two or more users who have made calls. Note that the user identifier of the telephone 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.
　情報サーバ２が請求書管理サーバである場合、サーバ格納部２１には、１または２以上の請求書情報が格納される。請求書情報には、請求書を発行したユーザのユーザ識別子、請求書を受け付けるユーザのユーザ識別子のうちの１以上のユーザ識別子が対応付いている。なお、一のユーザの請求書管理サーバのユーザ識別子と、一のユーザの交流管理装置１が使用するユーザ識別子とは、異なっていても良い。ただし、２つのユーザ識別子が異なっている場合、格納部１１には、２つのユーザ識別子の対応が管理されている、とする。 When the information server 2 is an invoice management server, the server storage unit 21 stores one or more items of invoice information. The invoice information is associated with one or more user identifiers of the user identifier of the user who issued the invoice and the user identifier of the user who accepts the invoice. The user identifier of one user's bill management 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 contract management server, the server storage unit 21 stores one or more pieces of contract information. The contract information is associated with user identifiers of one or more users who conclude the contract. The user identifier of one user's contract management 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 registration server, the server storage unit 21 stores one or more pieces of registration information. The registration information is associated with the user identifier of the user who registered for the event. The registration information may be associated with the user identifiers of the parties involved in the event. A person concerned is, for example, an organizer of an event, a speaker at the event, or the like. Note that the user identifier of the registration 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 instruction, exchange information (e.g., mail, schedule information, chat history information, call history information or call voice, bill information, contract information, registration information). The exchange information transmission instruction is an instruction to transmit exchange information. The server reception unit 22 receives, for example, interaction information associated with the user identifier.
　サーバ処理部２３は、各種の処理を行う。各種の処理とは、例えば、受信された交流情報をサーバ格納部２１に蓄積する処理である。各種の処理とは、例えば、交流情報の送信指示に対応する交流情報をサーバ格納部２１から取得する処理である。サーバ処理部２３は、例えば、受信された交流情報をユーザ識別子に対応付けてサーバ格納部２１に蓄積する処理である。なお、かかるユーザ識別子は、交流情報を送信したユーザのユーザ識別子、交流情報に対応して受信された交流情報である。 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 processing unit 23 is, for example, a process of storing the received exchange information in the server storage unit 21 in association with the user identifier. The user identifier is the user identifier of the user who transmitted the exchange information, and the exchange information received corresponding to the exchange information.
　サーバ送信部２４は、各種の情報を送信する。各種の情報とは、交流情報である。 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. Note that the timing of acquiring the exchange information is, for example, when the instruction is received or when a predetermined time comes, but the timing does not matter.
　（ステップＳ４０２）処理部１３は、カウンタｉに１を代入する。 (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, 1 or 2 or more out of 8 types of exchange information: mail, calendar server schedule information, web conference server schedule information, chat history information, call history information, invoice information, contract information, registration information types of exchange information exist.
　（ステップＳ４０４）処理部１３は、カウンタｊに１を代入する。 (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. The judgment as to whether or not the user identifier of the j-th user exists may be considered to be the same as the judgment as to whether or not the j-th exchange information exists.
　（ステップＳ４０６）処理部１３は、交流関係情報処理を行う。交流関係情報処理の例について、図５のフローチャートを用いて説明する。 (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. The business card information processing is processing such as obtaining contact information using business card information.
　（ステップＳ４１１）受信部１２は、交流情報を受信したか否かを判断する。交流情報を受信した場合はステップＳ４１２に行き、交流情報を受信しなかった場合はステップＳ４０１に戻る。 (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, for example, 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. Here, the exchange information determination unit 132 may acquire all the i-th exchange information without determining whether the i-th exchange information satisfies a predetermined condition. In such a case, step S504 is unnecessary.
　（ステップＳ５０５）他ユーザ情報取得部１３４は、ｉ番目の交流情報を用いて、他ユーザ情報を取得する。他ユーザ情報取得部１３４が他ユーザ情報を取得するアルゴリズムは種々あり得ることは、上述した通りである。 (Step S505) The other user information acquisition unit 134 acquires other user information using the i-th exchange information. As described above, there are various possible algorithms for the other user information acquisition unit 134 to acquire other user 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.
　例えば、質問部１３３は、ステップＳ５０５で取得された他ユーザ情報または、当該他ユーザ情報に対応する交流情報が予め決められた質問条件を満たすと判断した場合に、質問部１３３は、ユーザに問い合わせると判断する。なお、質問条件は、例えば、交流情報が特定の交流情報の種類ではないこと、交流情報が特定の交流情報の種類であることである。質問条件は、例えば、交流情報または他ユーザ情報が有する文字列が特定の用語を含むこと、交流情報または他ユーザ情報が有する文字列が特定の用語を含まないことである。 For example, when the questioning unit 133 determines that the other user information acquired in step S505 or the interaction information corresponding to the other user information satisfies a predetermined question condition, the questioning unit 133 inquires of the user. I judge. Note that the question conditions are, for example, that the exchange information is not of a specific type of exchange information and that the exchange information is of a specific type of exchange information. The question condition is, for example, that the character string possessed by the interaction information or other user information contains a specific term, or that the character string possessed by the exchange information or other user information does not contain a specific term.
　（ステップＳ５０７）質問部１３３は、ステップＳ５０５で取得された他ユーザ情報に対応する交流関係情報を蓄積するか否かをユーザに問い合わせる。 (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. The storage destination of the interaction relationship information is, for example, the interaction relationship storage unit 114 of the interaction management device 1, but may be another device.
　（ステップＳ５１２）変化判断部１３６は、ステップＳ５０５で取得された他ユーザ情報が、対応するユーザ情報と比較して、変更されているか（異動等が合ったか）を判断する。変更されている場合はステップＳ５１３に行き、変更されていない場合はステップＳ５１４に行く。 (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 another 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 if information indicating changes such as transfer information can be notified to other users with whom the user who has undergone a change such as a transfer can communicate.
　次に、ステップＳ４１０の名刺情報処理の例について、図７のフローチャートを用いて説明する。 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", "telephone number", 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")". "Chat (e.g. '5')" "Phone (e.g. '6')" "Bill (e.g. '7')" "Contract (e.g. '8')" 'Registration (e.g. '9') )”. "Additional information" is additional information in the exchange relationship information, such as mail-related information, business card exchange-related information, calendar-related information, web conference-related information, chat strings, call strings, and billing information. , all or part of contract information, and all or part of registration 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".
　ここで、「ＩＤ＝１」のビジネス交流条件は、相手側のメールアドレスに“co.jp”または”ac.jp”等のうちのいずれかを含むことである。また、「ＩＤ＝２」のビジネス交流条件は、２回以上のメールのやりとりがあること（メール送信に対する１回以上の返信があること）である。また、「ＩＤ＝３」のビジネス交流条件は、メールの中の文字列において、ビジネス用語の数が、非ビジネス用語の数より多いことである。また、「ＩＤ＝４」のビジネス交流条件は、カレンダーの予定情報の中にビジネス用語を含むことである。また、「ＩＤ＝５」のビジネス交流条件は、カレンダーの予定情報が土日祝日以外の日（通常、勤務日）であり、かつ予定情報が示す時間帯が９：００から１８：００の間であることである。また、「ＩＤ＝７」のビジネス交流条件は、異なる機会（例えば、異なる日）において、２回以上のチャットでのやりとりがあるである。また、「ＩＤ＝８」のビジネス交流条件は、チャット履歴情報の中の文字列において、ビジネス用語の数が閾値以上（例えば、「５以上」）であることである。また、「ＩＤ＝１０」のビジネス交流条件は、登録情報に対応する「タイトル」の文字列の中にビジネス用語が含まれることである。なお、「タイトル」は、イベントのタイトルであり、登録情報に対応付く情報である、とする。 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. Also, the business interaction condition for "ID=7" is that there are two or more chat interactions on different occasions (for example, different days). Also, the business interaction condition for "ID=8" is that the number of business terms in the character string in the chat history information is equal to or greater than a threshold (for example, "5 or more"). Also, the business exchange condition for "ID=10" is that a business term is included in the character string of "title" corresponding to the registration information. It should be noted that "title" is the title of the event and is information associated with the registration information.
　また、種類識別子が「メール」である場合、ここでは、交流情報決定部１３２は、「ＩＤ＝１」ＡＮＤ「ＩＤ＝２」ＡＮＤ「ＩＤ＝３」を満たすメールを、交流関係情報を取得する元になる交流情報として決定する、ものとする。 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.
　また、種類識別子が「ウェブ会議」である場合、ここでは、交流情報決定部１３２は、「ＩＤ＝６」を満たすカレンダー予定情報を、交流関係情報を取得する元になる交流情報として決定する、ものとする。 Further, when 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
　また、種類識別子が「チャット」である場合、ここでは、交流情報決定部１３２は、「ＩＤ＝７」ＡＮＤ「ＩＤ＝８」を満たすチャット履歴情報を、交流関係情報を取得する元になる交流情報として決定する、ものとする。 If the type identifier is "chat", the interaction information determination unit 132 selects the chat history information that satisfies "ID=7" AND "ID=8" as the interaction from which the interaction information is acquired. shall be determined as information.
　また、種類識別子が「電話」である場合、ここでは、交流情報決定部１３２は、「ＩＤ＝９」を満たす通話履歴情報を、交流関係情報を取得する元になる交流情報として決定する、ものとする。 Further, when the type identifier is "telephone", here, the exchange information determination unit 132 determines the call history information that satisfies "ID=9" as the exchange information from which the exchange relationship information is acquired. and
　さらに、種類識別子が「イベント」である場合、ここでは、交流情報決定部１３２は、「ＩＤ＝１０」を満たす登録情報を、交流関係情報を取得する元になる交流情報として決定する、ものとする。 Further, when the type identifier is "event", here, the exchange information determination unit 132 determines the registration information that satisfies "ID=10" as the exchange information from which the exchange relationship information is acquired. do.
　なお、種類識別子が「請求書」または「契約書」である場合、交流情報決定部１３２は、対象となるすべての請求書情報または契約書情報を、交流情報として決定する、ものとする。 It should be noted that if the type identifier is "invoice" or "contract", the exchange information determination unit 132 determines all target bill information or contract information as exchange information.
　そして、交流管理システムＡは、情報サーバ２として、１以上の各ユーザのメールを管理するメールサーバ２（１）、１以上の各ユーザのカレンダー予定情報を管理するカレンダーサーバ２（２）、１以上の各ユーザのウェブ会議予定情報を管理するウェブ会議サーバ２（３）、１以上の各ユーザのチャット履歴情報を管理するチャットサーバ２（４）、１以上の各ユーザの通話履歴情報を管理する電話サーバ２（５）、１以上の各ユーザの請求書情報を管理する請求書管理サーバ２（６）、１以上の各ユーザの契約書情報を管理する契約書管理サーバ２（７）、１以上の各ユーザの登録情報を管理する登録サーバ２（８）を有する、とする。 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, The web conference server 2 (3) that manages the above web conference schedule information of each user, the chat server 2 (4) that manages chat history information of one or more users, and manages call history information of one or more users. a telephone server 2 (5) that manages bill information of one or more users; a bill management server 2 (6) that manages bill information of one or more users; a contract management server 2 (7) that manages contract information of one or more users; It is assumed that there is a registration server 2 (8) that manages the registration information of one or more users.
　カレンダーサーバ２（２）のサーバ格納部２１には、図１４に示すカレンダー予定情報管理表が格納されている。カレンダー予定情報管理表は、「ＩＤ」「ユーザ識別子」「開始日時」「終了日時」「タイトル」などを有する１以上のレコードを管理している。 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.
　かかる状況において、以下の８つの具体例について説明する。具体例１は、メール、カレンダー予定情報、およびウェブ会議予定情報を用いて、交流情報を決定し、当該交流情報に対応する他ユーザ情報を蓄積するまでの処理である。なお、蓄積された他ユーザ情報は、交流関係情報の元になり得る情報である。具体例２は、蓄積された他ユーザ情報を用いて、ユーザに、交流関係情報を蓄積するか否かを問合せ、蓄積するとの回答である他ユーザ情報に対して、交流関係情報を蓄積する処理を説明する具体例である。具体例３は、名刺交換した相手の名刺情報を受信した場合に、交流関係情報を蓄積する例である。具体例４は、チャット履歴情報を受信した場合に、交流関係情報を蓄積する例である。具体例５は、通話履歴情報を受信した場合に、交流関係情報を蓄積する例である。具体例６は、請求書情報を受信した場合に、交流関係情報を蓄積する例である。具体例７は、契約書情報を受信した場合に、交流関係情報を蓄積する例である。具体例８は、登録情報を受信した場合に、交流関係情報を蓄積する例である。 Under these circumstances, the following eight 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 4 is an example of accumulating exchange relationship information when chat history information is received. Specific example 5 is an example of accumulating exchange relationship information when call history information is received. Specific example 6 is an example of accumulating exchange relationship information when bill information is received. Specific example 7 is an example of accumulating exchange relationship information when contract information is received. Specific example 8 is an example of accumulating exchange relationship information when registration information 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.
　次に、交流情報決定部１３２は、図１６のメール（１６０１，１６０２等）が、図１３の「ＩＤ＝１，２，３」のすべてのビジネス交流条件を満たすか否かを判断する。ここで、交流情報決定部１３２は、図１６のメール１６０１の送信元のメールアドレスが「ay@s.co.jp」であるので、「ＩＤ＝１」のビジネス交流条件を満たすと判断した、とする。また、交流情報決定部１３２は、本メールに対して、ユーザ識別子「１００１」で識別される山田一郎は応答していることを、読み出したメール（図示しない）から検知し、「ＩＤ＝２」のビジネス交流条件を満たすと判断した、とする。さらに、交流情報決定部１３２は、メール１６０１の＜タイトル＞と対になる文字列、および＜本文＞と対になる文字列を形態素解析し、１以上の用語を取得し、図１１のビジネス用語辞書を参照し、メール１６０１の中のビジネス用語の数を取得する。また、交流情報決定部１３２は、図１２の非ビジネス用語辞書を参照し、メール１６０１の中の非ビジネス用語の数を取得する。そして、交流情報決定部１３２は、「ＩＤ＝３」のビジネス交流条件を満たすと判断した、とする。以上より、交流情報決定部１３２は、図１６のメール１６０１を、予め決められた条件を満たす交流情報として決定する。 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, the exchange information determination 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.co.jp". and 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.
　次に、他ユーザ情報取得部１３４は、交流情報を用いて、他ユーザ情報を取得する。具体的には、他ユーザ情報取得部１３４は、メール１６０１からシグネチャーの部分の文字列「Ｓ株式会社　業務部　主任　山本Ａ子　〒１０５－００００　東京都・・・」を取得する。また、他ユーザ情報取得部１３４は、取得したシグネチャーの部分の文字列を用いて、図８のユーザ情報管理表を検索する。次に、他ユーザ情報取得部１３４は、図８のユーザ情報管理表から、他ユーザ情報「＜ユーザ識別子＞１３８４　＜氏名＞山本Ａ子　＜メールアドレス＞ay@s.co.jp　＜会社名＞Ｓ株式会社・・・・」を取得する。なお、ここで、他ユーザ情報取得部１３４は、メールからシグネチャーの部分の文字列を取得し、当該文字列を用いて、ユーザ情報管理表から他ユーザ情報を取得した。しかし、他ユーザ情報取得部１３４は、メールからシグネチャーの部分の文字列を用いて、他ユーザ情報を取得しても良い。 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> Aiko Yamamoto <e-mail address> ay@s.co.jp <company name> from the user information management table of FIG. S Co., Ltd.”. 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.
　次に、交流情報決定部１３２は、図１６のメール１６０２が、図１３の「ＩＤ＝１，２，３」のすべてのビジネス交流条件を満たすか否かを判断する。ここで、交流情報決定部１３２は、図１６のメール１６０１の送信元のメールアドレスが「star@google.com」であるので、「ＩＤ＝１」のビジネス交流条件を満たさないと判断した、とする。つまり、交流情報決定部１３２は、図１６のメール１６０２は、ビジネス交流条件を満たさない、と判断し、予め決められた条件を満たす交流情報として選択しない。 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.
　次に、他ユーザ情報取得部１３４は、交流情報を用いて、他ユーザ情報を取得する。具体的には、他ユーザ情報取得部１３４は、タイトル「○○打合せ＠Ｙ会社　青木次郎さん」の「Ｙ会社」「青木次郎」を用いて、図８のユーザ情報管理表を検索し、「ＩＤ＝３」のレコードにマッチする、と判断する。そして、他ユーザ情報取得部１３４は、他ユーザ情報「＜ユーザ識別子＞１００３　＜氏名＞青木次郎　＜メールアドレス＞aoki@y.com　＜会社名＞Ｙ会社・・・・」を取得する。 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.
　次に、他ユーザ情報取得部１３４は、当該交流情報を用いて、他ユーザ情報を取得する。具体的には、他ユーザ情報取得部１３４は、トピックスの文字列から「株式会社Ｘ」「鈴木Ｂ子」を抽出し、当該用語を用いて、図８のユーザ情報管理表を検索し、あるレコード（図示せず）にマッチする、と判断する。そして、他ユーザ情報取得部１３４は、他ユーザ情報「＜ユーザ識別子＞１０５８　＜氏名＞鈴木Ｂ子　＜メールアドレス＞sb@x.com　＜会社名＞株式会社Ｘ・・・・」を取得した、とする。 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.
（具体例４）
　今、チャットサーバ２（４）のサーバ格納部２１には、図１９に示すチャット管理表が格納されている。チャット管理表は、２以上のユーザ間で行われたチャットの情報であるチャット履歴情報が管理されている表である。チャット管理表は、「ＩＤ」「ユーザ識別子」「日時」「チャット文字列」を有する１以上のレコードを管理する表である。「ＩＤ」は、一連のチャットでのやりとりを識別する識別子である。「ユーザ識別子」は、チャット文字列を入力したユーザのＩＤである。「日時」は、チャット文字列が受信された日時である。「チャット文字列」は、ユーザにより入力された文字列である。 (Specific example 4)
A chat management table shown in FIG. 19 is now stored in the server storage unit 21 of the chat server 2(4). The chat management table is a table in which chat history information, which is information on chats between two or more users, is managed. The chat management table is a table for managing one or more records having "ID", "user identifier", "date and time", and "chat character string". "ID" is an identifier that identifies a series of chat interactions. "User identifier" is the ID of the user who entered the chat string. “Date and time” is the date and time when the chat string was received. "Chat string" is a string entered by the user.
　そして、予め決まられた時刻となり、交流管理装置１の処理部１３は、交流情報を取得するタイミングである、と判断した、とする。 Then, 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, assume that the user identifier acquisition unit 131 has acquired the first user identifier "1001" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子「１００１」に対応するチャット履歴情報を、チャットサーバから取得する。ここで、交流情報決定部１３２は、チャット管理表の「ＩＤ＝２」のチャット履歴情報を取得した、とする。 Next, the exchange information determination unit 132 acquires chat history information corresponding to the user identifier "1001" from the chat server. Here, it is assumed that the exchange information determining unit 132 has acquired the chat history information of "ID=2" in the chat management table.
　次に、交流情報決定部１３２は、当該チャット履歴情報は、図１３の「ＩＤ＝７」および「ＩＤ＝８」のビジネス交流を満たさないと判断した、とする。 Next, assume that the exchange information determining unit 132 determines that the chat history information does not satisfy the business exchanges of "ID=7" and "ID=8" in FIG.
　次に、ユーザ識別子取得部１３１は、２番目のユーザ識別子「１００２」を、ユーザ情報管理表から取得した、とする。 Next, assume that the user identifier acquisition unit 131 has acquired the second user identifier "1002" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子「１００２」に対応するチャット履歴情報を、チャットサーバから取得する。ここで、交流情報決定部１３２は、チャット管理表の「ＩＤ＝１」と「ＩＤ＝１８」のチャット履歴情報を取得した、とする。 Next, the exchange information determination unit 132 acquires chat history information corresponding to the user identifier "1002" from the chat server. Here, it is assumed that the exchange information determination unit 132 has acquired the chat history information of "ID=1" and "ID=18" in the chat management table.
　次に、交流情報決定部１３２は、「ＩＤ＝１」と「ＩＤ＝１８」のチャット履歴情報が、図１３の「ＩＤ＝７」および「ＩＤ＝８」のビジネス交流条件を満たすと判断する。なお、交流情報決定部１３２は、ユーザ識別子「１００２」のユーザとユーザ識別子「１００３」のユーザとのチャットにおける交流が２回あったことを、「ＩＤ＝１」と「ＩＤ＝１８」のチャット履歴情報から判断し、「ＩＤ＝７」のビジネス交流条件を満たす、と判断する。また、交流情報決定部１３２は、取得したチャット履歴情報の中に「お世話になっております」「会議」「株式会社」等のビジネス用語が５回以上出現すると判断し、「ＩＤ＝８」のビジネス交流も満たす、と判断する。 Next, the exchange information determination unit 132 determines that the chat history information of "ID=1" and "ID=18" satisfy the business exchange conditions of "ID=7" and "ID=8" in FIG. . Note that the interaction information determination unit 132 determines that the user with the user identifier “1002” and the user with the user identifier “1003” have interacted twice in the chats. Judging from the history information, it is determined that the business exchange condition of "ID=7" is satisfied. In addition, the exchange information determination unit 132 determines that business terms such as "thank you for your help", "meeting", and "corporation" appear five or more times in the acquired chat history information. Business exchanges also meet, judge.
　次に、他ユーザ情報取得部１３４は、「ＩＤ＝１」または「ＩＤ＝１８」のチャット履歴情報からユーザ識別子「１００２」と対になるユーザ識別子「１００３」を取得する。 Next, the other user information acquisition unit 134 acquires the user identifier "1003" paired with the user identifier "1002" from the chat history information of "ID=1" or "ID=18".
　次に、交流関係蓄積部１３５は、ユーザ識別子「１００２」、ユーザ識別子「１００３」、および種類識別子「チャット」を対にして、当該他ユーザ情報を格納部１１に蓄積する。 Next, the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "chat" and accumulates the other user information in the storage unit 11.
　なお、他ユーザ情報取得部１３４は、チャット履歴情報を送信したチャットサーバに対応する種類識別子「チャット」を、例えば、格納部１１から取得する。つまり、格納部１１には、各情報サーバ２を識別する情報（例えば、ＩＰアドレス、ＵＲＬ等）に対応付けて、種類識別子が格納されている、とする。 Note that the other user information acquisition unit 134 acquires from the storage unit 11, for example, the type identifier "chat" corresponding to the chat server that has transmitted the chat history information. In other words, it is assumed that the storage unit 11 stores type identifiers in association with information identifying each information server 2 (for example, IP address, URL, etc.).
　また、ここで、他ユーザ情報は、例えば「１００２，１００３，チャット」である。また、他ユーザ情報は、例えば、図１０に示すレコードの構造でも良い。つまり、交流関係蓄積部１３５は、「ＩＤ＝１」または／および「ＩＤ＝１８」のチャット履歴情報から付加情報を取得しても良い。付加情報は、例えば、「ＩＤ＝１」または「ＩＤ＝１８」のチャット文字列の全部または一部を含む。付加情報は、例えば、「ＩＤ＝１」または「ＩＤ＝１８」の＜日時＞の全部または一部（例えば、日「２０２１／１／１９」「２０２１／１／２０」）を含む。 Also, here, the other user information is, for example, "1002, 1003, chat". Further, the other user information may be, for example, the record structure shown in FIG. In other words, the interaction storage unit 135 may acquire additional information from the chat history information of "ID=1" and/or "ID=18". The additional information includes, for example, all or part of the chat string "ID=1" or "ID=18". The additional information includes, for example, all or part of the <date and time> of “ID=1” or “ID=18” (eg, date “2021/1/19” and “2021/1/20”).
　そして、ユーザ識別子取得部１３１、交流情報決定部１３２、他ユーザ情報取得部１３４、および交流関係蓄積部１３５は、３番目以降のユーザに対しても同様の処理を行う。 Then, the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
（具体例５）
　今、電話サーバ２（４）のサーバ格納部２１には、図２０に示す通話管理表が格納されている。通話管理表は、２以上のユーザ間で行われた電話による通話の情報である通話履歴情報が管理されている表である。通話管理表は、「ＩＤ」「ユーザ識別子」「日時」「通話文字列」を有する１以上のレコードを管理する表である。「ＩＤ」は、一連の通話でのやり取りを識別する識別子である。「ユーザ識別子」は、通話文字列に対応する音声を発したユーザの電話番号である。「日時」は、通話文字列に対応する音声が受信された日時である。「通話文字列」は、ユーザにより発声された音声に対して音声認識処理を行い、取得された文字列である。なお、電話サーバには、音声が格納されており、当該音声を受信した交流管理装置１が当該音声に対して音声認識処理をし、通話文字列を取得しても良い。 (Specific example 5)
A call management table shown in FIG. 20 is now stored in the server storage unit 21 of the telephone server 2(4). The call management table is a table in which call history information, which is information on telephone calls made between two or more users, is managed. The call management table is a table for managing one or more records having "ID", "user identifier", "date and time", and "call character string". "ID" is an identifier that identifies an interaction in a series of calls. "User Identifier" is the telephone number of the user who made the voice corresponding to the call string. “Date and time” is the date and time when the voice corresponding to the call character string was received. A “call character string” is a character string obtained by performing speech recognition processing on the voice uttered by the user. Note that the telephone server stores voice, and the exchange management device 1 that receives the voice may perform voice recognition processing on the voice and acquire a call character string.
　そして、予め決まられた時刻となり、交流管理装置１の処理部１３は、交流情報を取得するタイミングである、と判断した、とする。 Then, 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, it is assumed that the user identifier acquisition unit 131 acquired the telephone number "03-1111-1122" paired with the first user identifier "1001" from the user information management table.
　次に、交流情報決定部１３２は、電話番号「０３－１１１１－１１２２」に対応する通話履歴情報を、電話サーバから取得する。ここで、交流情報決定部１３２は、通話管理表の「ＩＤ＝２」の通話履歴情報を取得した、とする。 Next, the exchange information determination unit 132 acquires call history information corresponding to the telephone number "03-1111-1122" from the telephone server. Here, it is assumed that the exchange information determination unit 132 has acquired the call history information of "ID=2" in the call management table.
　次に、交流情報決定部１３２は、当該通話履歴情報は、図１３の「ＩＤ＝７」および「ＩＤ＝８」のビジネス交流を満たさないと判断した、とする。 Next, assume that the exchange information determination unit 132 determines that the call history information does not satisfy the business exchanges of "ID=7" and "ID=8" in FIG.
　次に、ユーザ識別子取得部１３１は、２番目のユーザ識別子「１００２」と対になる電話番号「０３－２２２２－２２２２」を、ユーザ情報管理表から取得した、とする。 Next, it is assumed that the user identifier acquisition unit 131 acquired the telephone number "03-2222-2222" paired with the second user identifier "1002" from the user information management table.
　次に、交流情報決定部１３２は、電話番号「０３－２２２２－２２２２」に対応する通話履歴情報を、電話サーバから取得する。ここで、交流情報決定部１３２は、通話管理表の「ＩＤ＝１」と「ＩＤ＝１８」の通話履歴情報を取得した、とする。 Next, the exchange information determination unit 132 acquires call history information corresponding to the telephone number "03-2222-2222" from the telephone server. Here, it is assumed that the exchange information determination unit 132 has acquired the call history information of "ID=1" and "ID=18" in the call management table.
　次に、交流情報決定部１３２は、「ＩＤ＝１」と「ＩＤ＝１８」の通話履歴情報が、図１３の「ＩＤ＝９」のビジネス交流条件を満たすと判断した、とする。なお、交流情報決定部１３２は、図１１の辞書を参照し、取得した通話履歴情報の中に「お世話になっております」「会議」「株式会社」等のビジネス用語を取得し、当該ビジネス用語の数を取得する。また、交流情報決定部１３２は、図１２の辞書を参照し、取得した通話履歴情報の中から非ビジネス用語を取得し、当該非ビジネス用語の数を取得する。そして、交流情報決定部１３２は、「ビジネス用語の数＞＝該非ビジネス用語の数」を満たす、と判断する。 Next, assume that the exchange information determination unit 132 determines that the call history information of "ID=1" and "ID=18" satisfies the business exchange condition of "ID=9" in FIG. Note that the exchange information determination unit 132 refers to the dictionary of FIG. Get the number of terms. Also, the exchange information determination unit 132 refers to the dictionary of FIG. 12, acquires non-business terms from the acquired call history information, and acquires the number of non-business terms. Then, the interaction information determining unit 132 determines that the condition "number of business terms >= number of non-business terms" is satisfied.
　次に、他ユーザ情報取得部１３４は、「ＩＤ＝１」または「ＩＤ＝１８」の通話履歴情報から電話番号「０３－２２２２－２２２２」と対になる電話番号「０３－３３３３－３３３３」を取得する。次に、他ユーザ情報取得部１３４は、電話番号「０３－３３３３－３３３３」と対になるユーザ識別子「１００３」を、図８のユーザ情報管理表から取得する。 Next, the other user information acquisition unit 134 retrieves the telephone number "03-3333-3333" paired with the telephone number "03-2222-2222" from the call history information of "ID=1" or "ID=18". get. Next, the other user information acquisition unit 134 acquires the user identifier "1003" paired with the telephone number "03-3333-3333" from the user information management table of FIG.
　次に、交流関係蓄積部１３５は、ユーザ識別子「１００２」、ユーザ識別子「１００３」、および種類識別子「電話」を対にして、当該他ユーザ情報を格納部１１に蓄積する。ここで、他ユーザ情報は、例えば「１００２，１００３，電話」である。また、他ユーザ情報は、例えば、図１０に示すレコードの構造でも良い。つまり、交流関係蓄積部１３５は、「ＩＤ＝１」または／および「ＩＤ＝１８」の通話履歴情報から付加情報を取得しても良い。付加情報は、例えば、「ＩＤ＝１」または「ＩＤ＝１８」の通話文字列の全部または一部を含む。付加情報は、例えば、「ＩＤ＝１」または「ＩＤ＝１８」の＜日時＞の全部または一部（例えば、日「２０２１／１／１９」「２０２１／１／２０」）を含む。 Next, the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "telephone" and accumulates the other user information in the storage unit 11. Here, the other user information is, for example, "1002, 1003, telephone". Further, the other user information may be, for example, the record structure shown in FIG. In other words, the interaction relationship storage unit 135 may acquire additional information from the call history information of "ID=1" and/or "ID=18". The additional information includes, for example, all or part of the call character string "ID=1" or "ID=18". The additional information includes, for example, all or part of the <date and time> of “ID=1” or “ID=18” (eg, date “2021/1/19” and “2021/1/20”).
　そして、ユーザ識別子取得部１３１、交流情報決定部１３２、他ユーザ情報取得部１３４、および交流関係蓄積部１３５は、３番目以降のユーザに対しても同様の処理を行う。 Then, the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
　なお、本具体例において、図２０の通話履歴情報がユーザ識別子を有する場合、他ユーザ情報取得部１３４は、ユーザ情報管理表を参照することなく、他ユーザ情報を構成するユーザ識別子を、通話履歴情報から取得する。 In this specific example, when the call history information of FIG. 20 has a user identifier, the other user information acquisition unit 134 acquires the user identifiers constituting the other user information from the call history without referring to the user information management table. Get from information.
（具体例６）
　今、請求書管理サーバ２（５）のサーバ格納部２１には、図２１に示す請求書管理表が格納されている。請求書管理表は、送付元のユーザから送付先のユーザに送付された請求書情報が管理されている表である。請求書管理表は、「ＩＤ」「送付元ユーザ識別子」「送付先ユーザ識別子」「送付元会社名」「送付先会社名」「請求金額」「請求書画像」を有する１以上のレコードを管理する表である。「ＩＤ」は、一の請求書に対応する識別情報である。「送付元ユーザ識別子」は、請求書を送付したユーザのＩＤである。「送付先ユーザ識別子」は、請求書を受け付けたユーザのＩＤである。「送付元会社名」は、送付元ユーザの属する会社名である。「送付先会社名」は、送付先ユーザの属する会社名である。 (Specific example 6)
Currently, the bill management table shown in FIG. 21 is stored in the server storage unit 21 of the bill management server 2(5). The bill management table is a table in which bill information sent from a sender user to a recipient user is managed. The bill management table manages one or more records having "ID", "sender user identifier", "destination user identifier", "sender company name", "destination company name", "billing amount", and "invoice image". It is a table that "ID" is identification information corresponding to one invoice. "Sender User Identifier" is the ID of the user who sent the invoice. "Destination User Identifier" is the ID of the user who received the invoice. “Sender company name” is the company name to which the sender user belongs. "Destination company name" is the name of the company to which the destination user belongs.
　そして、予め決まられた時刻となり、交流管理装置１の処理部１３は、交流情報を取得するタイミングである、と判断した、とする。 Then, 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, assume that the user identifier acquisition unit 131 has acquired the first user identifier "1001" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子「１００１」と対になる交流情報を請求書管理サーバ２（５）から取得する。ここで、交流情報決定部１３２は、図２１の「ＩＤ＝２」のレコードを取得する。 Next, the interaction information determination unit 132 acquires interaction information paired with the user identifier "1001" acquired by the user identifier acquisition unit 131 from the invoice management server 2 (5). Here, the exchange information determination unit 132 acquires the record of “ID=2” in FIG. 21 .
　次に、交流情報決定部１３２は、当該交流情報の送付元ユーザ識別子「１００１」と送付先ユーザ識別子「１００２」とを取得する。 Next, the exchange information determination unit 132 acquires the sender user identifier "1001" and the recipient user identifier "1002" of the exchange information.
　次に、交流情報決定部１３２は、ユーザ識別子「１００１」とユーザ識別子「１００２」との組は、既に図１０の表に存在する、と判断する。つまり、交流情報決定部１３２は、請求書管理サーバ２（５）から取得した当該交流情報を使用しない、と決定する。 Next, the exchange information determination unit 132 determines that the set of the user identifier "1001" and the user identifier "1002" already exists in the table of FIG. In other words, the exchange information determination unit 132 determines not to use the exchange information acquired from the invoice management server 2(5).
　次に、ユーザ識別子取得部１３１は、２番目のユーザ識別子「１００２」を、ユーザ情報管理表から取得した、とする。 Next, assume that the user identifier acquisition unit 131 has acquired the second user identifier "1002" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子「１００２」と対になる交流情報を請求書管理サーバ２（５）から取得する。ここで、交流情報決定部１３２は、図２１の「ＩＤ＝１」のレコードを取得する。 Next, the interaction information determination unit 132 acquires interaction information paired with the user identifier "1002" acquired by the user identifier acquisition unit 131 from the invoice management server 2 (5). Here, the exchange information determining unit 132 acquires the record of “ID=1” in FIG. 21 .
　次に、交流情報決定部１３２は、当該交流情報の送付元ユーザ識別子「１００２」と送付先ユーザ識別子「１００３」とを取得する。 Next, the exchange information determination unit 132 acquires the sender user identifier "1002" and the recipient user identifier "1003" of the exchange information.
　次に、交流情報決定部１３２は、ユーザ識別子「１００２」とユーザ識別子「１００３」との組は、図１０の表に存在しない、と判断する。つまり、交流情報決定部１３２は、請求書管理サーバ２（５）から取得した当該交流情報を使用する、と決定する。 Next, the interaction information determination unit 132 determines that the set of the user identifiers "1002" and "1003" does not exist in the table of FIG. In other words, the exchange information determination unit 132 determines to use the exchange information acquired from the invoice management server 2(5).
　次に、他ユーザ情報取得部１３４は、ユーザ識別子「１００２」とユーザ識別子「１００３」とを取得する。 Next, the other user information acquisition unit 134 acquires the user identifier "1002" and the user identifier "1003".
　次に、交流関係蓄積部１３５は、請求書管理サーバ２（５）に対応する種類識別子「請求書」を格納部１１から取得する。次に、交流関係蓄積部１３５は、ユーザ識別子「１００２」、ユーザ識別子「１００３」、および種類識別子「請求書」を対にして、当該他ユーザ情報を格納部１１に蓄積する。ここで、他ユーザ情報は、例えば「１００２，１００３，請求書」である。また、他ユーザ情報は、例えば、図１０に示すレコードの構造でも良い。つまり、交流関係蓄積部１３５は、「ＩＤ＝１」の請求書情報から付加情報を取得しても良い。付加情報は、例えば、「ＩＤ＝１」の請求書情報の全部または一部を含む。 Next, the interaction relationship storage unit 135 acquires from the storage unit 11 the type identifier "invoice" corresponding to the invoice management server 2 (5). Next, the interaction relationship accumulation unit 135 pairs the user identifier “1002”, the user identifier “1003”, and the type identifier “bill” and accumulates the other user information in the storage unit 11 . Here, the other user information is, for example, "1002, 1003, invoice". Further, the other user information may be, for example, the record structure shown in FIG. In other words, the interaction relationship accumulating unit 135 may acquire additional information from the invoice information with "ID=1". The additional information includes, for example, all or part of the invoice information of "ID=1".
　そして、ユーザ識別子取得部１３１、交流情報決定部１３２、他ユーザ情報取得部１３４、および交流関係蓄積部１３５は、３番目以降のユーザに対しても同様の処理を行う。 Then, the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
（具体例７）
　今、契約書管理サーバ２（６）のサーバ格納部２１には、図２２に示す契約書管理表が格納されている。契約書管理表は、契約当事者「甲」のユーザと契約当事者「乙」のユーザとの間の契約を示す契約書情報が管理されている表である。契約書管理表は、「ＩＤ」「甲ユーザ識別子」「乙ユーザ識別子」「甲会社名」「乙会社名」「契約金額」「契約書本文」を有する１以上のレコードを管理する表である。「ＩＤ」は、一の契約書に対応する識別情報である。「甲ユーザ識別子」は、契約の当事者「甲」のユーザのＩＤである。「乙ユーザ識別子」は、契約の当事者「乙」のユーザのＩＤである。「甲会社名」は、甲の会社名である。「乙会社名」は、乙の会社名である。 (Specific example 7)
At present, the contract management table shown in FIG. 22 is stored in the server storage unit 21 of the contract management server 2 (6). The contract management table is a table in which contract information indicating a contract between a user of a contracting party "A" and a user of a contracting party "B" is managed. The contract management table is a table for managing one or more records having "ID", "user identifier", "user identifier", "company name", "company name", "contract amount", and "text of contract". . "ID" is identification information corresponding to one contract. "A User Identifier" is the ID of the user of "A" who is a party to the contract. "B user identifier" is the ID of the user of "B", the party to the contract. "Party A company name" is the company name of Party A. "Company name of B" is the name of the company of B.
　そして、予め決まられた時刻となり、交流管理装置１の処理部１３は、交流情報を取得するタイミングである、と判断した、とする。 Then, 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, assume that the user identifier acquisition unit 131 has acquired the first user identifier "1001" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子「１００１」と対になる交流情報を契約書管理サーバ２（６）から取得する。ここで、交流情報決定部１３２は、図２１の「ＩＤ＝２」のレコードを取得する。 Next, the interaction information determination unit 132 acquires interaction information paired with the user identifier "1001" acquired by the user identifier acquisition unit 131 from the contract management server 2 (6). Here, the exchange information determination unit 132 acquires the record of “ID=2” in FIG. 21 .
　次に、交流情報決定部１３２は、当該交流情報の送付元ユーザ識別子「１００１」と送付先ユーザ識別子「１００２」とを取得する。 Next, the exchange information determination unit 132 acquires the sender user identifier "1001" and the recipient user identifier "1002" of the exchange information.
　次に、交流情報決定部１３２は、ユーザ識別子「１００１」とユーザ識別子「１００２」との組は、既に図１０の表に存在する、と判断する。つまり、交流情報決定部１３２は、契約書管理サーバ２（６）から取得した当該交流情報を使用しない、と決定する。 Next, the exchange information determination unit 132 determines that the set of the user identifier "1001" and the user identifier "1002" already exists in the table of FIG. That is, the exchange information determination unit 132 determines not to use the exchange information acquired from the contract management server 2 (6).
　次に、ユーザ識別子取得部１３１は、２番目のユーザ識別子「１００２」を、ユーザ情報管理表から取得した、とする。 Next, assume that the user identifier acquisition unit 131 has acquired the second user identifier "1002" from the user information management table.
　次に、交流情報決定部１３２は、ユーザ識別子取得部１３１が取得したユーザ識別子「１００２」と対になる交流情報を契約書管理サーバ２（６）から取得する。ここで、交流情報決定部１３２は、図２２の「ＩＤ＝１」のレコードを取得する。 Next, the interaction information determination unit 132 acquires interaction information paired with the user identifier "1002" acquired by the user identifier acquisition unit 131 from the contract management server 2 (6). Here, the exchange information determination unit 132 acquires the record of “ID=1” in FIG. 22 .
　次に、交流情報決定部１３２は、当該交流情報の送付元ユーザ識別子「１００２」と送付先ユーザ識別子「１００３」とを取得する。 Next, the exchange information determination unit 132 acquires the sender user identifier "1002" and the recipient user identifier "1003" of the exchange information.
　次に、交流情報決定部１３２は、ユーザ識別子「１００２」とユーザ識別子「１００３」との組は、図１０の表に存在しない、と判断する。つまり、交流情報決定部１３２は、契約書管理サーバ２（６）から取得した当該交流情報を使用する、と決定する。 Next, the interaction information determination unit 132 determines that the set of the user identifiers "1002" and "1003" does not exist in the table of FIG. That is, the exchange information determination unit 132 determines to use the exchange information acquired from the contract management server 2 (6).
　次に、他ユーザ情報取得部１３４は、ユーザ識別子「１００２」とユーザ識別子「１００３」とを取得する。 Next, the other user information acquisition unit 134 acquires the user identifier "1002" and the user identifier "1003".
　次に、交流関係蓄積部１３５は、契約書管理サーバ２（６）に対応する種類識別子「契約書」を格納部１１から取得する。次に、交流関係蓄積部１３５は、ユーザ識別子「１００２」、ユーザ識別子「１００３」、および種類識別子「契約書」を対にして、当該他ユーザ情報を格納部１１に蓄積する。ここで、他ユーザ情報は、例えば「１００２，１００３，契約書」である。また、他ユーザ情報は、例えば、図１０に示すレコードの構造でも良い。つまり、他ユーザ情報取得部１３４は、「ＩＤ＝１」の契約書情報から付加情報を取得しても良い。付加情報は、例えば、「ＩＤ＝１」の契約書情報の全部または一部を含む。 Next, the interaction relationship storage unit 135 acquires from the storage unit 11 the type identifier "contract" corresponding to the contract management server 2 (6). Next, the interaction relationship accumulation unit 135 pairs the user identifier “1002”, the user identifier “1003”, and the type identifier “contract” and accumulates the other user information in the storage unit 11 . Here, the other user information is, for example, "1002, 1003, contract". Further, the other user information may be, for example, the record structure shown in FIG. That is, the other user information acquisition unit 134 may acquire the additional information from the contract information of "ID=1". The additional information includes, for example, all or part of the contract information of "ID=1".
　そして、ユーザ識別子取得部１３１、交流情報決定部１３２、他ユーザ情報取得部１３４、および交流関係蓄積部１３５は、３番目以降のユーザに対しても同様の処理を行う。 Then, the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the third and subsequent users.
（具体例８） 
　今、登録サーバ２（７）のサーバ格納部２１には、図２３に示す登録管理表が格納されている。登録管理表は、１以上のイベントへの参加を申請した１以上の各ユーザの登録情報が管理されている表である。登録管理表は、「ＩＤ」「氏名」「会社名」「役職」「イベント識別子」を有する１以上のレコードを管理する表である。「ＩＤ」は、レコードを識別する情報である。「イベント識別子」は、ユーザが参加申請したイベントを識別する情報である。 (Specific example 8)
A registration management table shown in FIG. 23 is now stored in the server storage unit 21 of the registration server 2 (7). The registration management table is a table in which registration information of each of one or more users who have applied for participation in one or more events is managed. The registration management table is a table for managing one or more records having "ID", "name", "company name", "position", and "event identifier". “ID” is information for identifying a record. The “event identifier” is information that identifies the event for which the user applied for participation.
　また、登録サーバ２（７）のサーバ格納部２１には、図２４に示すイベント管理表が格納されている。イベント管理表は、１以上のイベント情報を管理する表である。イベント管理表は、「ＩＤ」「イベント識別子」「タイトル」「開催日時」を有する１以上のレコードを管理する表である。「ＩＤ」は、レコードを識別する情報である。「タイトル」は、イベントのタイトルである。 Also, the event management table shown in FIG. 24 is stored in the server storage unit 21 of the registration server 2 (7). The event management table is a table for managing one or more pieces of event information. The event management table is a table for managing one or more records having "ID", "event identifier", "title", and "date and time". “ID” is information for identifying a record. "Title" is the title of the event.
　そして、予め決まられた時刻となり、交流管理装置１の処理部１３は、交流情報を取得するタイミングである、と判断した、とする。 Then, 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.
　処理部１３は、登録サーバ２（７）から、登録管理表（図２３）が有する登録情報を取得する。また、処理部１３は、登録サーバ２（７）から、イベント管理表（図２４）が有するイベント情報を取得する。 The processing unit 13 acquires registration information contained in the registration management table (FIG. 23) from the registration server 2 (7). Also, the processing unit 13 acquires event information contained in the event management table (FIG. 24) from the registration server 2 (7).
　次に、交流情報決定部１３２は、取得した図２３の「ＩＤ＝１」の登録情報のイベント識別子「Ｅ１」に対応するイベント情報を取得する。かかるイベント情報は、タイトル「他社とのアライアンスに関して」、代表者「青木次郎」、会社名「Ｙ会社」を含む（図２４「ＩＤ＝１」のレコードを参照）。 Next, the exchange information determination unit 132 acquires the event information corresponding to the event identifier "E1" of the acquired registration information with "ID=1" in FIG. Such event information includes the title "Regarding Alliances with Other Companies", the representative "Jiro Aoki", and the company name "Y Company" (see the record of "ID=1" in FIG. 24).
　次に、交流情報決定部１３２は、取得した「ＩＤ＝１」の登録情報のタイトル「他社とのアライアンスに関して」の中にビジネス用語「アライアンス」を含むので、当該登録情報は、図１３の「ＩＤ＝１０」のビジネス交流条件を満たすと判断した、とする。 Next, exchange information determining unit 132 includes the business term "alliance" in the title "Regarding alliances with other companies" in the acquired registration information with "ID=1". It is assumed that it is determined that the business exchange condition of "ID=10" is satisfied.
　次に、ユーザ識別子取得部１３１は、「ＩＤ＝１」の登録情報が有する氏名「田中花子」、会社名「株式会社Ｘ」、および役職「取締役」を取得する。次に、ユーザ識別子取得部１３１は、氏名「田中花子」、会社名「株式会社Ｘ」、および役職「取締役」をキーとして、図８のユーザ情報管理表を検索し、ユーザ識別子「１００２」を取得する。 Next, the user identifier acquisition unit 131 acquires the name "Hanako Tanaka", the company name "Co., Ltd. X", and the title "Director" included in the registration information with "ID=1". Next, the user identifier acquisition unit 131 searches the user information management table of FIG. get.
　次に、他ユーザ情報取得部１３４は、イベント情報が有する代表者「青木次郎」、会社名「Ｙ会社」をキーとして、図８のユーザ情報管理表を検索し、ユーザ識別子「１００３」を取得する。 Next, the other user information acquisition unit 134 searches the user information management table of FIG. 8 using the representative “Jiro Aoki” and the company name “Y company” included in the event information as keys, and acquires the user identifier “1003”. do.
　次に、交流関係蓄積部１３５は、ユーザ識別子「１００２」、ユーザ識別子「１００３」、および種類識別子「イベント」を対にして、当該他ユーザ情報を格納部１１に蓄積する。ここで、他ユーザ情報は、例えば「１００２，１００３，イベント」である。また、他ユーザ情報は、例えば、図１０に示すレコードの構造でも良い。つまり、交流関係蓄積部１３５は、取得した「ＩＤ＝１」のイベント情報から付加情報を取得しても良い。付加情報は、例えば、「ＩＤ＝１」のイベント情報の全部または一部を含む。付加情報は、例えば、「ＩＤ＝１」のタイトル、関係者情報のうちの１以上の情報を含む。 Next, the interaction relationship accumulation unit 135 pairs the user identifier "1002", the user identifier "1003", and the type identifier "event" and accumulates the other user information in the storage unit 11. Here, the other user information is, for example, "1002, 1003, event". Further, the other user information may be, for example, the record structure shown in FIG. In other words, the interaction relationship accumulation unit 135 may acquire additional information from the acquired event information of “ID=1”. The additional information includes, for example, all or part of the event information of "ID=1". The additional information includes, for example, one or more information among the title of "ID=1" and related party information.
　そして、ユーザ識別子取得部１３１、交流情報決定部１３２、他ユーザ情報取得部１３４、および交流関係蓄積部１３５は、２番目以降のユーザに対しても同様の処理を行う。 Then, the user identifier acquisition unit 131, the interaction information determination unit 132, the other user information acquisition unit 134, and the interaction relationship storage unit 135 perform similar processing for the second and subsequent users.
　以上、本実施の形態によれば、メール、カレンダー予定情報、ウェブ会議予定情報、通話履歴情報、請求書情報、契約書情報、登録情報等の交流情報を用いて、ユーザ間の結びつきに関する交流関係情報を取得し、管理できる。 As described above, according to the present embodiment, using communication information such as email, calendar schedule information, web conference schedule information, call history information, invoice information, contract information, registration information, etc., exchange relationships related to connections between users Obtain and manage 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, the software that implements the exchange management device 1 in the present embodiment is the following program. In other words, this program comprises: a computer, an exchange information determination unit for acquiring exchange information from a storage unit that stores one or more pieces of exchange information that are information related to exchanges between two or more users; One user identifier corresponding to the exchange information acquired by the determination unit, and another user identifier different from the one user identifier, the other user including the other user identifier corresponding to the exchange information acquired by the exchange information determination unit It is a program for functioning as an other user information acquisition unit that acquires information and as an interaction relationship storage unit that stores interaction relationship information that associates the one user identifier with the other user information.
　（実施の形態２）
　実施の形態１では、ユーザ間の関係を示す交流関係情報を取得し、蓄積した。しかし、本実施の形態において、１以上の交流情報を用いて、組織と個人との関係情報、または組織と組織との関係情報を取得し、蓄積する交流管理装置について説明する。なお、本実施の形態において、実施の形態１における個人と個人との関係に関する関係情報を取得し、蓄積しても良い。また、交流関係情報は、関係情報と言っても良い。 (Embodiment 2)
In the first embodiment, exchange relationship information indicating relationships between users is acquired and accumulated. However, in the present embodiment, an exchange management apparatus that acquires and accumulates relationship information between organizations and individuals or between organizations using one or more exchange information will be described. Incidentally, in the present embodiment, the relationship information relating to the relationship between individuals in the first embodiment may be acquired and accumulated. Also, the exchange relationship information may be referred to as relationship information.
　また、本実施の形態において、２以上の交流情報から予め決められた条件を満たす交流情報（例えば、ビジネス交流情報）のみを用いて、関係情報を取得し、蓄積する交流管理装置について説明する。 In addition, in the present embodiment, an exchange management device that acquires and accumulates relational information using only exchange information that satisfies a predetermined condition (for example, business exchange information) from two or more pieces of exchange information will be described.
　また、本実施の形態において、関係情報を蓄積するか否かをユーザに問合せ、蓄積するとの回答の場合に、関係情報を蓄積する交流管理装置について説明する。 In addition, in the present embodiment, an exchange management apparatus that inquires of a user whether or not to accumulate relational information and accumulates the relational information when the answer is yes will be described.
　また、本実施の形態において、交流情報等を用いて、対象情報格納部から正確な組織情報または正確なユーザ情報を取得し、当該他ユーザ情報を用いて関係情報を取得し、蓄積する交流管理装置について説明する。 In addition, in the present embodiment, using exchange information, etc., accurate organization information or accurate user information is acquired from the target information storage unit, and related information is acquired using the other user information, and exchange management is performed. The device will be explained.
　また、本実施の形態において、名刺情報をも受け付け、蓄積する交流管理装置について説明する。また、名刺情報をも受け付けた場合に、当該名刺情報を用いて関係情報を取得し、蓄積する交流管理装置について説明する。 Also, in this embodiment, an exchange management device that also accepts and accumulates business card information will be described. Also, an exchange management apparatus that acquires and accumulates related information using business card information when business card information is also received will be described.
　さらに、本実施の形態において、関係情報を用いた所定のアクションを行う交流管理装置について説明する。 Furthermore, in this embodiment, an exchange management device that performs a predetermined action using relationship information will be described.
　本実施の形態における交流管理システムＢの概念図は、交流管理装置４の符号を除いて、図１と同じである。交流管理システムＢは、交流管理装置４、１または２以上の情報サーバ２、および１または２以上の端末装置３を備える。 The conceptual diagram of the exchange management system B in this embodiment is the same as FIG. 1 except for the reference numerals of the exchange management device 4. The exchange management system B includes an exchange management device 4 , one or more information servers 2 , and one or more terminal devices 3 .
　交流管理装置４は、関係情報を取得し、蓄積する装置である。交流管理装置４は、交流管理装置１が行う処理の全部えることは好適である。つまり、交流管理装置４は、交流管理装置１が有する構成の全部を具備することは好適である。交流管理装置１は、通常、いわゆるサーバであり、例えば、クラウドサーバ、ＡＳＰサーバ等である。なお、交流管理装置４の種類は問わない。また、交流関係情報の詳細については、後述する。 The exchange management device 4 is a device that acquires and accumulates related information. It is preferable that the exchange management device 4 includes all the processes performed by the exchange management device 1 . In other words, it is preferable that the exchange management device 4 has all the components of the exchange management device 1 . The exchange management device 1 is usually a so-called server, such as a cloud server or an ASP server. It should be noted that the type of the exchange management device 4 does not matter. Further, the details of the interaction relationship information will be described later.
　交流管理装置４は、１または２以上の各情報サーバ２、および１または２以上の各端末装置３と、インターネット、ＬＡＮ等のネットワークにより、通信可能であることは好適である。 The exchange management device 4 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. 25 is a block diagram of the exchange management device 4 that constitutes the exchange management system B in this embodiment. The exchange management device 4 includes a storage section 41 , a reception section 42 , a processing section 43 and a transmission section 44 .
　格納部４１は、対象情報格納部４１１、名刺情報格納部１１２、ドメイン情報格納部１１３、および交流関係格納部４１４を備える。対象情報格納部４１１は、ユーザ情報格納部１１１、および組織情報格納部４１１１を備える。受信部４２は、名刺情報受付部１２１を備える。処理部４３は、ユーザ識別子取得部１３１、交流決定部４３１、質問部１３３、関係取得部４３２、関係蓄積部４３３、変化判断部１３６、および交流処理部１３７を備える。 The storage unit 41 includes a target information storage unit 411, a business card information storage unit 112, a domain information storage unit 113, and an interaction relationship storage unit 414. The target information storage section 411 includes a user information storage section 111 and an organization information storage section 4111 . The reception unit 42 includes a business card information reception unit 121 . Processing unit 43 includes user identifier acquisition unit 131 , interaction determination unit 431 , question unit 133 , relationship acquisition unit 432 , relationship accumulation unit 433 , change determination unit 136 , and interaction processing unit 137 .
　交流管理装置４を構成する格納部４１には、各種の情報が格納される。各種の情報は、例えば、後述する対象情報、名刺情報、ドメイン情報、１または２種類以上の交流情報、関係情報、各種の画面情報である。 Various types of information are stored in the storage unit 41 that constitutes the exchange management device 4 . The various types of information are, for example, target information, business card information, domain information, one or more types of interaction information, relationship information, and various screen information, which will be described later.
　なお、ここでの交流情報は、二者以上の間での交流に関する情報である。格納部４１の２種類以上の交流情報は、各々、異なる情報サーバ２から取得された情報であることは好適である。また、格納部４１が情報サーバ２に含まれる構成である場合、２種類以上の各種類の交流情報は、各々、異なる格納部４１に存在することは好適である。 It should be noted that the exchange information here is information related to exchanges between two or more parties. It is preferable that the two or more types of exchange information in the storage unit 41 are information acquired from different information servers 2 respectively. Moreover, when the storage unit 41 is included in the information server 2 , it is preferable that two or more types of exchange information exist in different storage units 41 .
　対象情報格納部４１１には、１または２以上の対象情報が格納される。対象情報は、正確な関係情報を取得しようとする場合に、検索される対象の情報である。対象情報は、ユーザ情報または後述する組織情報である。 The target information storage unit 411 stores one or more target information. The target information is information to be searched when trying to acquire accurate relational information. The target information is user information or organization information described later.
　対象情報は、対象識別子と１または２以上の対象属性値とを有する。対象識別子は、対象を識別する情報である。対象とは、ユーザまたは組織である。対象識別子は、ユーザ識別子または組織識別子である。対象属性値は、ユーザ属性値または組織属性値である。組織属性値は、組織の情報である。組織属性値は、例えば、組織の名称（例えば、会社名）、住所、電話番号、代表者情報である。代表者情報は、例えば、代表者の氏名、代表者のメールアドレス、代表者の電話番号である。 The target information has a target identifier and one or more target attribute values. A target identifier is information that identifies a target. A target is a user or an organization. A subject identifier is a user identifier or an organizational identifier. A target attribute value is a user attribute value or an organization attribute value. The organization attribute value is organization information. Organization attribute values are, for example, organization name (eg, company name), address, telephone number, and representative information. The representative information is, for example, the name of the representative, the e-mail address of the representative, and the telephone number of the representative.
　組織情報格納部４１１１には、１または２以上の組織情報が格納される。組織情報は、組織に関する情報である。組織情報は、例えば、組織識別子、会社名、会社の電話番号、会社の住所、会社の代表者情報を有する。組織識別子は、組織を識別する情報であり、例えば、組織のＩＤ、会社名である。代表者情報は、例えば、代表者の氏名、代表者のメールアドレス、代表者の電話番号を有する。なお、組織情報は、組織識別子に対応付いていることは好適である。なお、組織情報格納部４１１１は、適宜、組織ＤＢと言う。また、ユーザ情報格納部１１１は、適宜、ユーザＤＢと言う。 The organization information storage unit 4111 stores one or more pieces of organization information. The organization information is information about the organization. The organization information includes, for example, an organization identifier, company name, company phone number, company address, and company representative information. The organization identifier is information for identifying an organization, such as an organization ID or company name. The representative information includes, for example, the name of the representative, the e-mail address of the representative, and the telephone number of the representative. The organization information is preferably associated with an organization identifier. Note that the organization information storage unit 4111 is appropriately called an organization DB. Also, the user information storage unit 111 is appropriately referred to as a user DB.
　交流関係格納部４１４には、１または２以上の関係情報が格納される。関係情報とは、二者の間の関係に関する情報である。二者は、組織と組織または組織と個人（ユーザ）であることは好適であるが、個人と個人でも良い。関係情報は、二者間に関係があることを示す情報である、と言える。関係情報は、二者の交流関係が特定できる情報であれば良い。関係情報は、２つの対象識別子を対応付ける情報である。２つの対象識別子とは、第一識別子と第二識別子である。対象識別子は、組織を識別する組織識別子または個人を識別するユーザ識別子である。関係情報は、例えば、組織と組織との関係情報、組織と個人との関係情報である。ただし、関係情報は、個人と個人との関係情報でも良い。 The exchange relationship storage unit 414 stores one or more pieces of relationship information. Relationship information is information about the relationship between two parties. The two parties are preferably an organization and an organization or an organization and an individual (user), but they may be an individual and an individual. It can be said that the relationship information is information indicating that there is a relationship between two parties. The relationship information may be any information that can identify the interaction relationship between the two. Relationship information is information that associates two target identifiers. The two target identifiers are the first identifier and the second identifier. A subject identifier is an organization identifier that identifies an organization or a user identifier that identifies an individual. The relationship information is, for example, relationship information between organizations and relationship information between organizations and individuals. However, the relationship information may be relationship information between individuals.
　組織と組織の関係情報は、例えば、二つの組織識別子を有する情報、第一の組織の組織識別子に対応付く第二の組織の組織情報、第一の組織の組織識別子と第二の組織の組織情報とを有する情報、二者の組織の組織情報を有する情報である。 The relationship information between organizations is, for example, information having two organization identifiers, organization information of the second organization corresponding to the organization identifier of the first organization, organization identifier of the first organization and organization of the second organization. Information that has information and information that has organizational information of two organizations.
　組織と個人の関係情報は、例えば、組織識別子とユーザ識別子とを有する情報、組織識別子とユーザ情報とを有する情報、組織情報とユーザ識別子とを有する情報、組織情報とユーザ情報とを有する情報である。 The relationship information between an organization and an individual is, for example, information having an organization identifier and a user identifier, information having an organization identifier and user information, information having an organization information and a user identifier, and information having an organization information and a user information. be.
　個人と個人の関係情報は、実施の形態１で説明した交流関係情報である。 The relationship information between individuals is the exchange relationship information described in the first embodiment.
　受信部４２は、各種の情報を受信する。各種の情報は、例えば、開始指示、交流情報、名刺情報、ユーザ識別子、各種の情報の送信指示である。受信部４２は、受信部１２と同じでも良い。 The receiving unit 42 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 receiver 42 may be the same as the receiver 12 .
　処理部４３は、各種の処理を行う。各種の処理とは、例えば、ユーザ識別子取得部１３１、交流情報決定部４３２、質問部１３３、関係取得部４３２、関係蓄積部４３３、変化判断部１３６、交流処理部１３７が行う処理である。 The processing unit 43 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 432, the question unit 133, the relationship acquisition unit 432, the relationship storage unit 433, the change determination unit 136, and the interaction processing unit 137.
　交流決定部４３１は、格納部４１から、１または２以上の交流情報を取得する。ここでの格納部４１は、情報サーバ２のサーバ格納部２１でも良い。交流決定部４３１は、交流決定部１３２と同じでも良い。 The exchange determination unit 431 acquires one or more pieces of exchange information from the storage unit 41 . The storage unit 41 here may be the server storage unit 21 of the information server 2 . The alternating current determining section 431 may be the same as the alternating current determining section 132 .
　交流決定部４３１は、例えば、格納部４１から、２種類以上の交流情報を取得する。 The exchange determination unit 431 acquires two or more types of exchange information from the storage unit 41, for example.
　交流決定部４３１は、例えば、格納部４１から、予め決められた条件を満たす交流情報を取得する。 The exchange determination unit 431 acquires, for example, exchange information that satisfies predetermined conditions from the storage unit 41 .
　関係取得部４３２は、交流決定部４３１が取得した交流情報に対応する二者の各々の対象識別子を対応付けた関係情報を取得する。二者の各対象識別子は、第一識別子と第二識別子である。第一識別子または第二識別子は、組織識別子またはユーザ識別子である。第一識別子または第二識別子の少なくとも一方は、組織識別子であることは好適であるが、両方ともユーザ識別子でも良い。なお、両方ともユーザ識別子である場合の交流決定部４３１の処理は、他ユーザ情報取得部１３４と同じ処理で良い。また、かかる処理について、実施の形態１で説明されている。また、組織識別子は、組織を識別できる情報であれば良い。ユーザ識別子は個人を識別できる情報であれば良い The relationship acquisition unit 432 acquires relationship information in which the object identifiers of the two parties corresponding to the interaction information acquired by the interaction determination unit 431 are associated. Each subject identifier of the two parties is a first identifier and a second identifier. The first identifier or second identifier is an organization identifier or a user identifier. At least one of the first identifier or the second identifier is preferably an organizational identifier, but both may be user identifiers. Note that the processing of the exchange determination unit 431 when both are user identifiers may be the same processing as that of the other user information acquisition unit 134 . Also, such processing is described in the first embodiment. Also, the organization identifier may be any information that can identify the organization. The user identifier should be information that can identify an individual.
　関係取得部４３２は、交流決定部４３１が決定した交流情報に含まれる文字列または交流情報に対応する対象識別子を用いて、対象情報格納部４１１を検索し、検索結果を用いて、関係情報を取得する。 The relationship acquisition unit 432 searches the target information storage unit 411 using the character string included in the interaction information determined by the interaction determination unit 431 or the target identifier corresponding to the interaction information, and uses the search result to obtain the relationship information. get.
　関係取得部４３２は、例えば、第一識別子と名刺情報に対応する第二識別子とを対応付けた関係情報を取得する。 The relationship acquisition unit 432 acquires, for example, relationship information that associates the first identifier with the second identifier corresponding to the business card information.
　関係取得部４３２は、コミュニケーションシステム情報を用いて、関係情報を取得する。また、関係取得部４３２は、非コミュニケーションシステム情報を用いて、関係情報を取得する。 The relationship acquisition unit 432 acquires relationship information using communication system information. Also, the relationship acquisition unit 432 acquires relationship information using non-communication system information.
　以下、交流情報の種類ごとの関係取得部４３２の動作例を説明する。なお、関係取得部４３２が個人と個人との関係に関する関係情報を取得する場合の動作は、他ユーザ情報取得部１３４の動作と同じで良いので、ここでの説明は省略する。
交流情報が通話履歴情報である場合
（１－１）組織と個人との関係情報を構成する場合 An operation example of the relationship acquisition unit 432 for each type of exchange information will be described below. It should be noted that the operation when the relationship acquisition unit 432 acquires the relationship information regarding the relationship between individuals may be the same as the operation of the other user information acquisition unit 134, so the description is omitted here.
When the exchange information is call history information (1-1) When forming relationship information between an organization and an individual
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した通話履歴情報に対応付いている電話番号を取得する。なお、かかる電話番号は、例えば、会社の電話番号である。次に、関係取得部４３２は、例えば、当該電話番号と対になる会社名または組織識別子を組織ＤＢから取得する。次に、関係取得部４３２は、例えば、ユーザ識別子取得部１３１が取得したユーザ識別子と、取得した会社名または組織識別子とを対応付ける関係情報を構成する。なお、ここでのユーザ識別子は、例えば、一の会社に電話をかけたユーザを識別する情報である。 For example, the relationship acquisition unit 432 acquires the telephone number associated with the call history information determined by the exchange information determination unit 132. Note that such a telephone number is, for example, a company's telephone number. Next, the relationship acquisition unit 432 acquires, for example, the company name or organization identifier paired with the telephone number from the organization DB. Next, the relationship acquisition unit 432 configures, for example, relationship information that associates the user identifier acquired by the user identifier acquisition unit 131 with the acquired company name or organization identifier. Note that the user identifier here is, for example, information for identifying the user who made a call to one company.
　また、関係取得部４３２は、ユーザ識別子を取得する場合に、通話履歴情報に対応付いている電話番号をキーとしてユーザＤＢを検索し、ユーザ識別子を取得しても良い。かかる場合の電話番号は、電話をかけたユーザの電話番号である。 Also, when acquiring the user identifier, the relationship acquisition unit 432 may search the user DB using the telephone number associated with the call history information as a key to acquire the user identifier. The phone number in such a case is the phone number of the user who made the call.
　また、関係取得部４３２は、会社名を取得する場合に、通話履歴情報に含まれる文字列（例えば、「もしもし　Ａ株式会社でしょうか？　・・・」）を形態素解析し、当該解析結果から、会社名（例えば、「Ａ株式会社」）を取得しても良い。なお、関係取得部４３２は、会社名を取得する場合に、通話履歴情報に含まれる会社名をキーとして、組織ＤＢを検索し、当該会社名と対になる組織識別子を取得し、当該組織識別子と取得したユーザ識別子とを対応付ける関係情報を構成しても良い。
（１－２）組織間の関係情報を取得する場合 In addition, when acquiring a company name, the relationship acquiring unit 432 morphologically analyzes a character string included in the call history information (for example, "Hello, is it A Corporation? ..."), and from the analysis result, A company name (for example, “A Corporation”) may be obtained. When acquiring a company name, the relationship acquisition unit 432 searches the organization DB using the company name included in the call history information as a key, acquires an organization identifier paired with the company name, and obtains the organization identifier. and the acquired user identifier may be configured.
(1-2) When obtaining relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した通話履歴情報に対応付いている２つの電話番号を取得する。次に、関係取得部４３２は、例えば、一の電話番号と対になる会社名または組織識別子を組織ＤＢから取得する。また、関係取得部４３２は、例えば、他の電話番号と対になる会社名または組織識別子を組織ＤＢから取得する。次に、関係取得部４３２は、例えば、２つの会社名、または２つの組織識別子を対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, two telephone numbers associated with the call history information determined by the exchange information determination unit 132. Next, the relationship acquisition unit 432 acquires, for example, a company name or organization identifier paired with one telephone number from the organization DB. Also, the relationship acquisition unit 432 acquires, for example, a company name or an organization identifier paired with another telephone number from the organization DB. Next, the relationship acquisition unit 432 configures relationship information that associates, for example, two company names or two organization identifiers.
　なお、関係取得部４３２は、会社名を取得する場合に、通話履歴情報に含まれる文字列（例えば、「もしもし　Ａ株式会社でしょうか？　・・・」）を形態素解析し、当該解析結果から、会社名（例えば、「Ａ株式会社」）を取得しても良い。 When acquiring the company name, the relationship acquiring unit 432 morphologically analyzes the character string included in the call history information (for example, "Hello, is it A Corporation? ..."), and from the analysis result, A company name (for example, “A Corporation”) may be acquired.
　また、関係取得部４３２が、通話履歴情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（２）交流情報が請求書情報である場合
（２－１）組織と個人との関係情報を構成する場合
（２－１－１）請求元のユーザと請求先の組織との関係情報を構成する場合 Moreover, the method by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the call history information does not matter.
(2) When exchange information is invoice information (2-1) When configuring relationship information between organizations and individuals (2-1-1) Configuring relationship information between invoicing users and invoicing organizations When to
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した請求書情報が有する請求元担当者識別子（請求元のユーザ識別子（例えば、ユーザＩＤ、氏名）に該当する）と請求先担当者識別子（請求先のユーザ識別子に該当する）とを取得する。次に、関係取得部４３２は、請求先のユーザ識別子をキーとして、ユーザＤＢを検索し、会社名を取得する。次に、関係取得部４３２は、当該請求元のユーザ識別子と当該請求先の会社名とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 obtains, for example, a billing person in charge identifier (corresponding to a billing person's user identifier (e.g., user ID, name)) and a billing person in charge identifier included in the invoice information determined by the interaction information determination unit 132. (corresponding to the billing user identifier). Next, the relationship acquisition unit 432 searches the user DB using the billing user identifier as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the user identifier of the billing party with the company name of the billing party.
　なお、関係取得部４３２は、請求書情報に対応付けられた請求元のユーザの氏名や会社名をキーとしてユーザＤＢを検索し、請求元のユーザ識別子を取得し、当該ユーザ識別子と当該請求先の会社名とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using the user name and company name of the invoicing party associated with the invoice information as keys, acquires the user identifier of the invoicing party, and obtains the user identifier and the invoicing party. You may constitute the relationship information which matches with the company name of.
　また、関係取得部４３２は、請求書情報が有する請求先の会社名を取得し、当該会社名と請求元のユーザ識別子とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 may acquire the company name of the billing party included in the invoice information, and configure relationship information that associates the company name with the user identifier of the billing party.
　また、関係取得部４３２は、取得した会社名等をキーとして組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と請求元のユーザ識別子とを対応付ける関係情報を構成しても良い。
（２－１－２）請求先のユーザと請求元の組織との関係情報を構成する場合 Also, the relationship acquisition unit 432 may search the organization DB using the acquired company name or the like as a key, acquire an organization identifier, and configure relationship information that associates the organization identifier with the billing user identifier.
(2-1-2) When configuring relationship information between billing user and billing organization
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した請求書情報に対応付いている請求先のユーザ識別子（例えば、ユーザＩＤ、氏名）と請求元のユーザ識別子とを取得する。次に、関係取得部４３２は、請求元のユーザ識別子をキーとして、ユーザＤＢを検索し、会社名を取得する。次に、関係取得部４３２は、当該請求先のユーザ識別子と当該請求元の会社名とを対応付ける関係情報を構成する。 For example, the relationship acquisition unit 432 acquires the user identifier of the billing party (for example, user ID, name) and the user identifier of the billing party associated with the invoice information determined by the exchange information determination unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the user identifier of the invoicing party as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the user identifier of the invoicing party with the company name of the invoicing party.
　なお、関係取得部４３２は、請求書情報に対応付けられた請求先のユーザの氏名や会社名をキーとしてユーザＤＢを検索し、請求先のユーザ識別子を取得し、当該ユーザ識別子と当該請求元の会社名とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using the user name and company name of the billing party associated with the bill information as keys, acquires the user identifier of the billing party, You may constitute the relationship information which matches with the company name of.
　また、関係取得部４３２は、請求書情報が有する請求元の会社名を取得し、当該会社名と請求先のユーザ識別子とを対応付ける関係情報を構成しても良い。 Also, the relationship acquisition unit 432 may acquire the company name of the billing party included in the invoice information, and configure relationship information that associates the company name with the user identifier of the billing party.
　また、関係取得部４３２は、取得した会社名等をキーとして組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と請求先のユーザ識別子とを対応付ける関係情報を構成しても良い。
（２－２）組織間の関係情報を構成する場合 Further, the relationship acquisition unit 432 may search the organization DB using the acquired company name or the like as a key, acquire an organization identifier, and configure relationship information that associates the organization identifier with the billing user identifier.
(2-2) When configuring relationship information between organizations
　関係取得部４３２は、例えば、請求書情報に含まれる請求元の会社名と請求先の会社名とを取得する。次に、関係取得部４３２は、例えば、当該２つの会社名を対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, the billing company name and the billing company name included in the invoice information. Next, the relationship acquisition unit 432 configures, for example, relationship information that associates the two company names.
　なお、関係取得部４３２は、請求元または請求先の会社名を取得する場合に、交流情報決定部１３２が決定した請求書情報に対応付いている請求元のユーザ識別子を取得し、当該ユーザ識別子をキーとしてユーザＤＢを検索し、会社名を取得しても良い。 Note that when acquiring the company name of the billing party or the billing destination, the relationship acquisition unit 432 acquires the user identifier of the billing party associated with the invoice information determined by the interaction information determination unit 132, and obtains the user identifier of the billing party. may be used as a key to search the user DB to obtain the company name.
　また、関係取得部４３２は、取得した２つの各会社名等（例えば、会社名と電話番号）をキーとして組織ＤＢを検索し、当該２つの各会社名等に対応する組織識別子を取得し、当該２つの組織識別子を対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the organization DB using the acquired two company names (for example, company name and telephone number) as keys, acquires the organization identifiers corresponding to the two company names, etc., Relational information that associates the two organization identifiers may be configured.
　なお、関係取得部４３２が、請求書情報を用いて、請求元または請求先のユーザ識別子、請求元または請求先の会社名等を取得する方法は問わない。
（３）交流情報が契約書情報である場合
（３－１）組織と個人との関係情報を構成する場合 Any method may be used by which the relationship acquisition unit 432 acquires the user identifier of the billing party or the billing party, the company name of the billing party or the billing party, etc., using the invoice information.
(3) When exchange information is contract information (3-1) When constituting relationship information between an organization and an individual
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した契約書情報が有する２つの担当者識別子（ユーザ識別子に該当する）を取得する。次に、関係取得部４３２は、例えば、一のユーザ識別子と対になる会社名をユーザＤＢから取得する。次に、関係取得部４３２は、例えば、当該会社名と他のユーザ識別子とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, two person-in-charge identifiers (corresponding to user identifiers) included in the contract information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 acquires, for example, a company name paired with one user identifier from the user DB. Next, the relationship acquisition unit 432 configures relationship information that associates the company name with another user identifier, for example.
　なお、関係取得部４３２は、会社名を取得する場合に、契約書情報に含まれる会社名（例えば、甲に対応する会社名、または乙に対応する会社名）を取得しても良い。また、関係取得部４３２は、会社名を取得する場合に、契約書情報に含まれる２以上の会社名から、上記の他のユーザ識別子と対になる会社名をユーザＤＢから取得し、当該会社名ではない会社名を、関係情報を構成する会社名として採用しても良い。
（３－２）組織間の関係情報を取得する場合 When obtaining the company name, the relationship obtaining unit 432 may obtain the company name included in the contract information (for example, the company name corresponding to Party A or the company name corresponding to Party B). Further, when acquiring a company name, the relationship acquiring unit 432 acquires from the user DB a company name paired with the other user identifier from two or more company names included in the contract information, A company name that is not a name may be adopted as the company name that constitutes the related information.
(3-2) When acquiring relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した契約書情報が有する２つのユーザ識別子を取得する。次に、関係取得部４３２は、例えば、２つの各ユーザ識別子と対になる会社名をユーザＤＢから取得する。次に、関係取得部４３２は、例えば、当該２つの会社名を対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, two user identifiers included in the contract information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 acquires, for example, the company name paired with each of the two user identifiers from the user DB. Next, the relationship acquisition unit 432 configures, for example, relationship information that associates the two company names.
　なお、関係取得部４３２は、２つの会社名を取得する場合に、契約書情報に含まれる２つの会社名（例えば、甲および乙に対応する会社名）を取得しても良い。 When acquiring two company names, the relationship acquiring unit 432 may acquire two company names (for example, company names corresponding to A and B) included in the contract information.
　なお、関係取得部４３２が、契約書情報を用いて、会社名やユーザ識別子等を取得する方法は問わない。
（４）交流情報が登録情報である場合
（４－１）組織と個人との関係情報を構成する場合
（４－１－１）イベントへの登録者（参加者）とイベントの主催組織との関係情報を構成する場合 It should be noted that any method by which the relationship acquisition unit 432 acquires the company name, user identifier, or the like using the contract information may be used.
(4) When exchange information is registration information (4-1) When forming relationship information between an organization and an individual When configuring relationship information
　関係取得部４３２は、交流情報決定部１３２が決定した登録情報が有する登録者識別情報（ユーザ識別子に該当する）と主催者識別情報（ユーザ識別子に該当する）とを取得する。次に、関係取得部４３２は、主催者識別情報をキーとしてユーザＤＢを検索し、会社名を取得する。次に、関係取得部４３２は、登録者識別情報と会社名とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires the registrant identification information (corresponding to the user identifier) and the organizer identification information (corresponding to the user identifier) included in the registration information determined by the exchange information determining unit 132. Next, the relationship acquisition unit 432 searches the user DB using the organizer identification information as a key and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the registrant identification information with the company name.
　なお、関係取得部４３２は、登録情報が有する登録者識別情報を取得することに代えて、登録情報が有する登録者の氏名や会社名をキーとしてユーザＤＢを検索し、ユーザ識別子を取得しても良い。 Note that, instead of acquiring the registrant identification information included in the registration information, the relationship acquisition unit 432 searches the user DB using the name and company name of the registrant included in the registration information as keys, and acquires the user identifier. Also good.
　また、関係取得部４３２は、主催者側の会社名を取得する場合に、登録情報が有する主催者側の会社名を取得しても良い。
（４－１－２）イベントへの登録者の組織とイベントの担当者等との関係情報を構成する場合 Further, when acquiring the company name of the organizer, the relationship acquisition unit 432 may acquire the company name of the organizer included in the registration information.
(4-1-2) When configuring relationship information between the organization of registrants for the event and the person in charge of the event, etc.
　関係取得部４３２は、交流情報決定部１３２が決定した登録情報が有する登録者の会社名と主催者識別情報（ユーザ識別子に該当する）とを取得する。次に、関係取得部４３２は、当該会社名と当該主催者識別情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires the registrant's company name and organizer identification information (corresponding to the user identifier) included in the registration information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the company name with the organizer identification information.
　なお、関係取得部４３２は、登録者の会社名を取得する場合に、登録情報が有する氏名や電話番号と対になる会社名をユーザＤＢから取得しても良い。 When acquiring the company name of the registrant, the relationship acquiring unit 432 may acquire the company name paired with the name and telephone number included in the registration information from the user DB.
　また、関係取得部４３２は、主催者識別情報を取得する場合に、登録情報が有する主催者の氏名や電話番号等をキーとしてユーザＤＢを検索し、ユーザ識別子を取得しても良い。
（４－２）組織間の関係情報を取得する場合 Further, when acquiring the organizer identification information, the relationship acquisition unit 432 may search the user DB using the organizer's name, telephone number, etc. included in the registration information as keys, and acquire the user identifier.
(4-2) When obtaining relationship information between organizations
　関係取得部４３２は、交流情報決定部１３２が決定した登録情報が有する登録者の会社名と主催者の会社名とを取得する。次に、関係取得部４３２は、当該２つの会社名を対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires the registrant's company name and the sponsor's company name included in the registration information determined by the exchange information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the two company names.
　なお、関係取得部４３２が、登録情報を用いて、会社名やユーザ識別子等を取得する方法は問わない。
（５）交流情報が問合情報である場合
（５－１）組織と個人との関係情報を構成する場合
（５－１－１）質問者と問合せの対応組織との関係情報を構成する場合 It should be noted that any method may be used by which the relationship acquisition unit 432 acquires the company name, user identifier, etc. using the registration information.
(5) When exchange information is inquiry information (5-1) When forming relational information between an organization and an individual (5-1-1) When forming relational information between an inquirer and an organization responding to an inquiry
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する１以上の質問者属性値を取得する。次に、関係取得部４３２は、当該１以上の質問者属性値をキーとしてユーザＤＢを検索し、ユーザ識別子を取得する。また、関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する対応組織の担当者名または対応組織の担当者のユーザ識別子を取得する。次に、関係取得部４３２は、例えば、取得した担当者名等をキーとしてユーザＤＢを検索し、会社名を取得する。次に、関係取得部４３２は、取得したユーザ識別子と会社名とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as a key to acquire a user identifier. Further, the relationship acquiring unit 432 acquires, for example, the name of the person in charge of the corresponding organization or the user identifier of the person in charge of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the acquired person-in-charge name or the like as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the acquired user identifier with the company name.
　なお、関係取得部４３２は、質問者のユーザ識別子を取得する場合に、問合情報が有するユーザ識別子を取得しても良い。 Note that the relationship acquisition unit 432 may acquire the user identifier of the inquiry information when acquiring the questioner's user identifier.
　また、関係取得部４３２は、会社名を取得する場合に、問合情報が有する対応組織の会社名を取得しても良い。
（５－１－２）質問者の組織と問合せの対応組織（例えば、フォーム作成組織）の担当者との関係情報を構成する場合 Further, when acquiring the company name, the relationship acquiring unit 432 may acquire the company name of the corresponding organization included in the inquiry information.
(5-1-2) When constructing relational information between the questioner's organization and the person in charge of the inquiry-response organization (for example, form creation organization)
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する１以上の質問者属性値を取得する。次に、関係取得部４３２は、当該１以上の質問者属性値をキーとしてユーザＤＢを検索し、会社名を取得する。また、関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する対応組織の担当者名と会社名等を取得する。次に、関係取得部４３２は、当該担当者名等をキーとしてユーザＤＢを検索し、ユーザ識別子を取得する。次に、関係取得部４３２は、取得した会社名とユーザ識別子とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as keys, and acquires the company name. Also, the relationship acquisition unit 432 acquires, for example, the name of the person in charge of the corresponding organization and the name of the company included in the inquiry information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the name of the person in charge or the like as a key, and acquires the user identifier. Next, the relationship acquisition unit 432 configures relationship information that associates the acquired company name with the user identifier.
　なお、関係取得部４３２は、会社名を取得する場合に、問合情報が有する質問者の会社名を取得しても良い。 When acquiring the company name, the relationship acquisition unit 432 may acquire the questioner's company name included in the inquiry information.
　また、関係取得部４３２は、対応組織の担当者のユーザ識別子を取得する場合に、問合情報が有するユーザ識別子を取得しても良い。
（５－２）組織間の関係情報を取得する場合 Further, when acquiring the user identifier of the person in charge of the corresponding organization, the relationship acquiring unit 432 may acquire the user identifier included in the inquiry information.
(5-2) When obtaining relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する１以上の質問者属性値を取得する。次に、関係取得部４３２は、当該１以上の質問者属性値をキーとしてユーザＤＢを検索し、会社名を取得する。また、関係取得部４３２は、例えば、交流情報決定部１３２が決定した問合情報が有する対応組織の担当者名または対応組織の担当者のユーザ識別子を取得する。次に、関係取得部４３２は、例えば、取得した担当者名等をキーとしてユーザＤＢを検索し、会社名を取得する。次に、関係取得部４３２は、取得した２つの会社名を対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, one or more questioner attribute values included in the inquiry information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 searches the user DB using the one or more questioner attribute values as keys, and acquires the company name. Further, the relationship acquiring unit 432 acquires, for example, the name of the person in charge of the corresponding organization or the user identifier of the person in charge of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 . Next, the relationship acquisition unit 432 searches the user DB using the acquired person-in-charge name or the like as a key, and acquires the company name. Next, the relationship acquisition unit 432 configures relationship information that associates the two acquired company names.
　なお、関係取得部４３２は、質問者の会社名を取得する場合に、交流情報決定部１３２が決定した問合情報が有する質問者の会社名を取得しても良い。また、関係取得部４３２は対応組織の会社名を取得する場合に、交流情報決定部１３２が決定した問合情報が有する対応組織の会社名を取得しても良い。 It should be noted that, when acquiring the questioner's company name, the relationship acquisition unit 432 may acquire the questioner's company name included in the inquiry information determined by the interaction information determination unit 132 . Further, when acquiring the company name of the corresponding organization, the relationship acquiring unit 432 may acquire the company name of the corresponding organization included in the inquiry information determined by the exchange information determining unit 132 .
　なお、関係取得部４３２が、問合情報を用いて、会社名やユーザ識別子等を取得する方法は問わない。
（６）交流情報が営業活動情報である場合
（６－１）組織と個人との関係情報を構成する場合
（６－１－１）営業担当者と営業先組織との関係情報を取得する場合 It should be noted that any method may be used by which the relationship acquisition unit 432 acquires the company name, user identifier, etc. using the inquiry information.
(6) When exchange information is sales activity information (6-1) When forming relationship information between organizations and individuals (6-1-1) When acquiring relationship information between sales representatives and sales organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した営業活動情報が有する営業担当者情報（例えば、営業担当者の氏名）と営業顧客情報（例えば、顧客の会社名）とを取得する。次に、関係取得部４３２は、営業担当者情報と営業顧客情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, the salesperson information (eg, the name of the salesperson) and the sales customer information (eg, the customer's company name) included in the sales activity information determined by the interaction information determination unit 132. . Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
　なお、関係取得部４３２は、例えば、営業活動情報が有する営業担当者情報を用いてユーザＤＢを検索し、当該営業担当者情報に対応するユーザ識別子を取得し、当該ユーザ識別子と営業顧客情報とを対応付ける関係情報を構成しても良い。 In addition, for example, the relationship acquisition unit 432 searches the user DB using the salesperson information included in the sales activity information, acquires the user identifier corresponding to the salesperson information, and combines the user identifier with the sales customer information. may be configured to correspond to the relationship information.
　また、関係取得部４３２は、営業顧客情報（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、顧客の会社名を取得し、ユーザ識別子と当該会社名とを対応付ける関係情報を構成しても良い。
（６－１－２）営業担当者の組織と営業先組織の担当者との関係情報を取得する場合 Also, the relationship acquisition unit 432 searches the user DB using sales customer information (for example, the customer's name and department name), acquires the customer's company name, and acquires relationship information that associates the user identifier with the company name. may be configured.
(6-1-2) When acquiring relationship information between the organization of the sales representative and the person in charge of the sales organization
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した営業活動情報が有する営業担当者情報（例えば、営業担当者の会社名）と営業顧客情報（例えば、顧客の氏名、顧客の会社名）とを取得する。次に、関係取得部４３２は、営業担当者情報と営業顧客情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, salesperson information (for example, the company name of the salesperson) and sales customer information (for example, the name of the customer, the company name of the customer, etc.) included in the sales activity information determined by the interaction information determination unit 132. ) and get Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
　なお、関係取得部４３２は、例えば、営業活動情報が有する営業担当者情報を用いてユーザＤＢを検索し、当該営業担当者情報に対応する会社名を取得し、当該会社名と営業顧客情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432, for example, searches the user DB using the salesperson information included in the sales activity information, acquires the company name corresponding to the salesperson information, and combines the company name with the sales customer information. may be configured to correspond to the relationship information.
　また、関係取得部４３２は、営業顧客情報（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、当該顧客のユーザ識別子を取得し、当該ユーザ識別子と営業担当者の会社名とを対応付ける関係情報を構成しても良い。
（６－２）組織間の関係情報を取得する場合 In addition, the relationship acquisition unit 432 searches the user DB using the sales customer information (for example, the customer's name and department name), acquires the user identifier of the customer, and combines the user identifier with the company name of the salesperson. may be configured to correspond to the relationship information.
(6-2) When obtaining relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した営業活動情報が有する営業担当者情報（例えば、営業担当者の会社名）と営業顧客情報（例えば、顧客の会社名）とを取得する。次に、関係取得部４３２は、営業担当者情報と営業顧客情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, salesperson information (eg, salesperson's company name) and sales customer information (eg, customer's company name) included in the sales activity information determined by the interaction information determination unit 132. do. Next, the relationship acquisition unit 432 configures relationship information that associates the salesperson information and the sales customer information.
　なお、関係取得部４３２は、例えば、営業活動情報が有する営業担当者情報（例えば、担当者の氏名、電話番号）を用いてユーザＤＢを検索し、当該営業担当者情報に対応する会社名を取得し、当該会社名と営業顧客情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using, for example, the salesperson information (for example, the name and telephone number of the person in charge) possessed by the sales activity information, and obtains the company name corresponding to the salesperson information. It is also possible to configure relationship information that is acquired and associates the company name with the sales customer information.
　また、関係取得部４３２は、営業顧客情報（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、顧客の会社名を取得し、営業担当者情報と当該会社名とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the sales customer information (for example, the customer's name and department name), acquires the customer's company name, and obtains the relationship that associates the sales representative information with the company name. information may be configured.
　なお、関係取得部４３２が、営業活動情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（７）交流情報が顧客情報である場合
（７－１）組織と個人との関係情報を構成する場合
（７－１－１）担当者と顧客の組織との関係情報を取得する場合 Any method may be used by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the sales activity information.
(7) When the exchange information is customer information (7-1) When configuring relationship information between an organization and an individual (7-1-1) When acquiring relationship information between a person in charge and a customer's organization
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した顧客情報が有する担当者情報（例えば、担当者の氏名）と１以上の顧客属性値（例えば、顧客の会社名）とを取得する。次に、関係取得部４３２は、担当者情報と１以上の顧客属性値とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, the person in charge information (for example, the name of the person in charge) included in the customer information determined by the exchange information determination unit 132 and one or more customer attribute values (for example, the customer's company name). . Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
　なお、関係取得部４３２は、例えば、顧客情報が有する担当者情報を用いてユーザＤＢを検索し、当該担当者情報に対応するユーザ識別子を取得し、当該ユーザ識別子と１以上の顧客属性値とを対応付ける関係情報を構成しても良い。 Note that, for example, the relationship acquisition unit 432 searches the user DB using the person-in-charge information included in the customer information, acquires the user identifier corresponding to the person-in-charge information, and combines the user identifier with one or more customer attribute values. may be configured to correspond to the relationship information.
　また、関係取得部４３２は、１以上の顧客属性値（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、顧客の会社名を取得し、担当者情報と当該会社名とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's company name, and obtains the person in charge information and the company name. Corresponding relationship information may be configured.
　なお、関係取得部４３２は、顧客情報が有する担当者情報（例えば、担当者の氏名、電話番号）をキーとしてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と１以上の顧客属性値（例えば、顧客の会社名）とを対応付ける関係情報を構成しても良い。
（７－１－２）担当者の組織と顧客との関係情報を取得する場合 Note that the relationship acquisition unit 432 searches the user DB using the person-in-charge information (for example, name and phone number of the person-in-charge) included in the customer information as a key, acquires a user identifier, and acquires the user identifier and one or more customer attributes. You may configure the relationship information which associates with a value (for example, a customer's company name).
(7-1-2) When acquiring relationship information between the organization of the person in charge and the customer
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した顧客情報が有する担当者情報（例えば、営業担当者の会社名）と１以上の顧客属性値（例えば、顧客の氏名、顧客の会社名）とを取得する。次に、関係取得部４３２は、担当者情報と１以上の顧客属性値とを対応付ける関係情報を構成する。 For example, the relationship acquisition unit 432 acquires the person in charge information (eg, the company name of the salesperson) included in the customer information determined by the interaction information determination unit 132 and one or more customer attribute values (eg, the customer's name, the customer's company first name). Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
　なお、関係取得部４３２は、例えば、顧客情報が有する担当者情報を用いてユーザＤＢを検索し、当該担当者情報に対応する会社名を取得し、当該会社名と１以上の顧客属性値（例えば、顧客の氏名）とを対応付ける関係情報を構成しても良い。 Note that, for example, the relationship acquisition unit 432 searches the user DB using the person-in-charge information included in the customer information, acquires the company name corresponding to the person-in-charge information, and obtains the company name and one or more customer attribute values ( For example, the customer's name) may be associated with relational information.
　また、関係取得部４３２は、１以上の顧客属性値（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、顧客のユーザ識別子を取得し、当該ユーザ識別子と担当者の会社名とを対応付ける関係情報を構成しても良い。
（７－２）組織間の関係情報を取得する場合 In addition, the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's user identifier, and acquires the user identifier and the company name of the person in charge. You may comprise the relationship information which matches.
(7-2) When obtaining relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した顧客情報が有する担当者情報（例えば、営業担当者の会社名）と１以上の顧客属性値（例えば、顧客の会社名）とを取得する。次に、関係取得部４３２は、担当者情報と１以上の顧客属性値とを対応付ける関係情報を構成する。 The relationship acquisition unit 432, for example, acquires the person-in-charge information (for example, the company name of the salesperson) and one or more customer attribute values (for example, the company name of the customer) included in the customer information determined by the interaction information determination unit 132. get. Next, the relationship acquisition unit 432 configures relationship information that associates the person-in-charge information with one or more customer attribute values.
　なお、関係取得部４３２は、例えば、顧客情報が有する担当者情報（例えば、担当者の氏名、電話番号）を用いてユーザＤＢを検索し、当該担当者情報に対応する会社名を取得し、当該会社名と１以上の顧客属性値を対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using, for example, the person in charge information (for example, the name and phone number of the person in charge) possessed by the customer information, acquires the company name corresponding to the person in charge information, Relationship information may be configured to associate the company name with one or more customer attribute values.
　また、関係取得部４３２は、１以上の顧客属性値（例えば、顧客の氏名、部署名）を用いてユーザＤＢを検索し、顧客の会社名を取得し、担当者情報と当該会社名とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using one or more customer attribute values (for example, the customer's name and department name), acquires the customer's company name, and obtains the person in charge information and the company name. Corresponding relationship information may be configured.
　なお、関係取得部４３２は、取得した会社名等を用いて、組織ＤＢを検索し、組織識別子を取得し、当該組織識別子を用いた関係情報を構成しても良い。 Note that the relationship acquisition unit 432 may search the organization DB using the acquired company name or the like, acquire an organization identifier, and configure relationship information using the organization identifier.
　また、関係取得部４３２が、顧客情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（８）交流情報が注文情報である場合
（８－１）組織と個人との関係情報を構成する場合
（８－１－１）注文者と注文を受けた組織との関係情報を構成する場合 Also, any method may be used by which the relationship acquisition unit 432 acquires an organization identifier, a user identifier, or the like using customer information.
(8) When exchange information is order information (8-1) When forming relationship information between an organization and an individual (8-1-1) When forming relationship information between an orderer and an organization that received an order
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した注文情報が有する発注者情報（例えば、氏名、電話番号）と注文先情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該発注者情報と当該注文先情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, orderer information (eg, name, telephone number) and order destination information (eg, company name) included in the order information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
　なお、関係取得部４３２は、注文情報が有する発注者情報を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と注文先情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 may search the user DB using the orderer information included in the order information, acquire the user identifier, and configure relationship information that associates the user identifier with the orderer information.
　また、関係取得部４３２は、注文先情報（例えば、注文を受けた者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と発注者情報とを対応付ける関係情報を構成しても良い。 Also, the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the orderer information. Relationship information may be configured.
　また、関係取得部４３２は、取得した会社名を用いて、組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と発注者情報とを対応付ける関係情報を構成しても良い。
（８－１－２）注文者の組織と注文を受けた組織の担当者との関係情報を構成する場合 Also, the relationship acquisition unit 432 may search the organization DB using the acquired company name, acquire an organization identifier, and configure relationship information that associates the organization identifier with the orderer information.
(8-1-2) When configuring relationship information between the orderer's organization and the person in charge of the organization that received the order
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した注文情報が有する発注者情報（例えば、会社名）と注文先情報（例えば、注文先の担当者の氏名、会社名）とを取得する。次に、関係取得部４３２は、当該発注者情報と当該注文先情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, orderer information (for example, company name) and order recipient information (for example, the name of the person in charge of the order recipient, company name) included in the order information determined by the interaction information determination unit 132. do. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
　なお、関係取得部４３２は、注文情報が有する発注者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と注文先情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information. may be configured.
　また、関係取得部４３２は、注文先情報（例えば、注文を受けた者の氏名、会社名）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と発注者情報とを対応付ける関係情報を構成しても良い。 Also, the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name of the person who received the order, the company name), acquires the user identifier, and associates the user identifier with the orderer information. Relationship information may be configured.
　また、関係取得部４３２は、取得した会社名を用いて、組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と注文先情報とを対応付ける関係情報を構成しても良い。
（８－２）組織間の関係情報を取得する場合 Also, the relationship acquisition unit 432 may search an organization DB using the acquired company name, acquire an organization identifier, and configure relationship information that associates the organization identifier with order destination information.
(8-2) When acquiring relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した注文情報が有する発注者情報（例えば、会社名）と注文先情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該発注者情報と当該注文先情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, orderer information (eg, company name) and order destination information (eg, company name) included in the order information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
　なお、関係取得部４３２は、注文情報が有する発注者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と注文先情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using orderer information (for example, name and telephone number) included in the order information, acquires the company name, and associates the company name with the orderer information. may be configured.
　また、関係取得部４３２は、注文先情報（例えば、注文を受けた者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と発注者情報とを対応付ける関係情報を構成しても良い。 Also, the relationship acquisition unit 432 searches the user DB using the orderer information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the orderer information. Relationship information may be configured.
　また、関係取得部４３２は、取得した２つの各会社名（発注者の会社の名称、注文先の会社の名称）を用いて、組織ＤＢを検索し２つの、組織識別子を取得し、当該２つの組織識別子を対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the organization DB using the two acquired company names (the name of the orderer's company and the name of the company to which the order is placed), acquires two organization identifiers, and obtains the two organization identifiers. It is also possible to configure relationship information that associates two organization identifiers.
　なお、関係取得部４３２が、注文情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（９）交流情報が採用情報である場合 Any method may be used by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the order information.
(9) When exchange information is employment information
　関係取得部４３２は、採用情報を用いて、応募者と応募先の組織との関係情報を構成する。 The relationship acquisition unit 432 uses the employment information to compose relationship information between the applicant and the organization to which the applicant applies.
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した採用情報が有する応募者情報（例えば、氏名）と応募先情報（例えば、応募先の会社名）とを取得する。次に、関係取得部４３２は、当該応募者情報と当該応募先情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, applicant information (eg, name) and applicant information (eg, company name of the applicant) contained in the employment information determined by the exchange information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the applicant information with the applicant information.
　なお、関係取得部４３２は、採用情報が有する応募者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と応募先情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using the applicant information (for example, name and telephone number) included in the employment information, acquires the user identifier, and associates the user identifier with the applicant information. may be configured.
　また、関係取得部４３２は、応募先情報（例えば、注文を受けた者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と応募者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the applicant information (for example, the name and telephone number of the person who received the order), acquires the company name, and associates the company name with the applicant information. Relationship information may be configured.
　また、関係取得部４３２は、応募先情報（例えば、応募先の会社名、電話番号）を用いて、組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と応募者情報とを対応付ける関係情報を構成しても良い。 Also, the relationship acquisition unit 432 searches the organization DB using the applicant information (for example, the company name and telephone number of the applicant), acquires the organization identifier, and associates the organization identifier with the applicant information. information may be configured.
　なお、関係取得部４３２が、採用情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（１０）交流情報がパンフレット取得情報である場合 Any method may be used by which the relationship acquisition unit 432 acquires an organization identifier, a user identifier, or the like using employment information.
(10) When exchange information is pamphlet acquisition information
　関係取得部４３２は、パンフレット取得情報を用いて、パンフレットの取得者とパンフレットに関する組織との関係情報を構成する。 The relationship acquisition unit 432 uses the pamphlet acquisition information to compose relationship information between the pamphlet acquirer and the pamphlet-related organization.
　関係取得部４３２は、例えば、交流情報決定部１３２が決定したパンフレット取得情報が有する取得者情報（例えば、氏名）とパンフレットの提供組織に関する組織情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該取得者情報と当該組織情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, acquirer information (eg, name) contained in the pamphlet acquisition information determined by the interaction information determination unit 132 and organization information (eg, company name) relating to the organization providing the pamphlet. Next, the relationship acquisition unit 432 configures relationship information that associates the acquirer information with the organization information.
　なお、関係取得部４３２は、取得者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と組織情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 may search the user DB using acquirer information (eg, name and phone number), acquire a user identifier, and configure relationship information that associates the user identifier with organization information. good.
　また、関係取得部４３２は、組織情報が有するパンフレットの提供企業の担当者情報（例えば、担当者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と取得者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using information on the person in charge of the company providing the pamphlet included in the organization information (for example, the name and telephone number of the person in charge), acquires the company name, and obtains the company name. It is also possible to configure relationship information that correlates with acquirer information.
　また、関係取得部４３２は、組織情報（例えば、会社名、電話番号）を用いて、組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と取得者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the organization DB using organization information (for example, company name, telephone number), acquires an organization identifier, and configures relationship information that associates the organization identifier with acquirer information. can be
　なお、関係取得部４３２が、パンフレット取得情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（１１）交流情報が経費情報である場合 Any method may be used by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the pamphlet acquisition information.
(11) When exchange information is expense information
　関係取得部４３２は、経費情報を用いて、申請者と経費処理を行う組織との関係情報を構成する。 The relationship acquisition unit 432 uses the expense information to compose relationship information between the applicant and the organization that processes the expense.
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した経費情報が有する申請者情報（例えば、氏名）と経費処理を行う組織に関する組織情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該申請者情報と当該組織情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, applicant information (eg, name) included in the expense information determined by the exchange information determination unit 132 and organization information (eg, company name) related to the organization that handles expense processing. Next, the relationship acquisition unit 432 configures relationship information that associates the applicant information and the organization information.
　なお、関係取得部４３２は、申請者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と組織情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using the applicant information (eg, name, phone number), acquires the user identifier, and configures relationship information that associates the user identifier with the organization information. good.
　また、関係取得部４３２は、組織情報が有する許可者情報（例えば、許可者の氏名、メールアドレス）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と申請者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the permitter information (for example, the permitter's name and email address) that the organization information has, acquires the company name, and combines the company name and the applicant information. Corresponding relationship information may be configured.
　また、関係取得部４３２は、組織情報（例えば、会社名と電話番号）を用いて組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と申請者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the organization DB using organization information (for example, company name and phone number), acquires an organization identifier, and configures relationship information that associates the organization identifier and applicant information. Also good.
　なお、関係取得部４３が、経費情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（１２）交流情報がアンケート情報である場合
（１２－１）組織と個人との関係情報を構成する場合
（１２－１－１）アンケートの回答者とアンケートの実施組織との関係情報を構成する場合 Any method may be used by which the relationship acquisition unit 43 acquires the organization identifier, the user identifier, etc. using the expense information.
(12) When exchange information is questionnaire information (12-1) When configuring relationship information between an organization and an individual (12-1-1) Configuring relationship information between a questionnaire respondent and a questionnaire implementing organization case
　関係取得部４３２は、例えば、交流情報決定部１３２が決定したアンケート情報が有する回答者情報（例えば、氏名）と実施者情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該回答者情報と当該実施者情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, respondent information (eg, name) and implementer information (eg, company name) included in the questionnaire information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 constructs relationship information that associates the respondent information and the implementer information.
　なお、関係取得部４３２は、回答者情報（例えば、氏名、メールアドレス）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と実施者情報とを対応付ける関係情報を構成しても良い。 The relationship acquisition unit 432 searches the user DB using respondent information (e.g., name, email address), acquires a user identifier, and composes relationship information that associates the user identifier with the executor information. Also good.
　また、関係取得部４３２は、実施者情報（例えば、担当者の氏名、メールアドレス）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と回答者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and email address of the person in charge), acquires the company name, and acquires relationship information that associates the company name with the respondent information. may be configured.
　また、関係取得部４３２は、実施者情報（例えば、会社名、電話番号）を用いて組織ＤＢを検索し、組織識別子を取得し、当該会社名と組織識別子とを対応付ける関係情報を構成しても良い。
（１２－１－２）アンケートの回答者の組織とアンケートの実施組織の担当者との関係情報を構成する場合 In addition, the relationship acquisition unit 432 searches the organization DB using the executor information (eg, company name, telephone number), acquires the organization identifier, and configures relationship information that associates the company name and the organization identifier. Also good.
(12-1-2) When configuring relationship information between the organization of the respondent to the questionnaire and the person in charge of the organization conducting the questionnaire
　関係取得部４３２は、例えば、交流情報決定部１３２が決定したアンケート情報が有する回答者情報（例えば、回答者が属する会社名）と実施者情報（例えば、担当者の氏名）とを取得する。次に、関係取得部４３２は、当該回答者情報と当該実施者情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, respondent information (for example, company name to which the respondent belongs) and implementer information (for example, the name of the person in charge) included in the questionnaire information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 constructs relationship information that associates the respondent information and the implementer information.
　なお、関係取得部４３２は、回答者情報（例えば、氏名、メールアドレス）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と実施者情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using respondent information (for example, name and email address), acquires a company name, and composes relationship information that associates the company name with the executor information. Also good.
　また、関係取得部４３２は、実施者情報（例えば、担当者の氏名、メールアドレス）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と回答者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and email address of the person in charge), acquires the user identifier, and acquires the relationship information that associates the user identifier with the respondent information. may be configured.
　また、関係取得部４３２は、回答者情報（例えば、会社名、電話番号）を用いて組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と実施者情報とを対応付ける関係情報を構成しても良い。
（１２－２）組織間の関係情報を取得する場合 In addition, the relationship acquisition unit 432 searches the organization DB using respondent information (e.g., company name, telephone number), acquires an organization identifier, and configures relationship information that associates the organization identifier with the implementer information. can be
(12-2) When acquiring relationship information between organizations
　関係取得部４３２は、例えば、交流情報決定部１３２が決定したアンケート情報が有する回答者情報（例えば、会社名）と実施者情報（例えば、会社名）とを取得する。次に、関係取得部４３２は、当該発注者情報と当該注文先情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, respondent information (eg company name) and implementer information (eg company name) included in the questionnaire information determined by the interaction information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the orderer information with the orderer information.
　なお、関係取得部４３２は、回答者情報（例えば、回答者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と実施者情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using the respondent information (for example, the respondent's name and telephone number), acquires the company name, and acquires relationship information that associates the company name with the implementer information. may be configured.
　また、関係取得部４３２は、実施者情報（例えば、担当者の氏名、電話番号）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と回答者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using the information on the implementer (for example, the name and telephone number of the person in charge), acquires the company name, and acquires relationship information that associates the company name with the respondent information. may be configured.
　また、関係取得部４３２は、アンケートの回答者の会社名と、アンケートの実施組織の会社名を取得し、当該２つの各会社名を用いて、組織ＤＢを検索し、２つの組織識別子を取得し、当該２つの組織識別子を対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 acquires the company name of the questionnaire respondent and the company name of the organization implementing the questionnaire, searches the organization DB using the two company names, and acquires two organization identifiers. Then, relationship information may be configured to associate the two organization identifiers.
　なお、関係取得部４３２が、アンケート情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（１３）交流情報が入館情報である場合 Any method may be used by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the questionnaire information.
(13) When exchange information is admission information
　関係取得部４３２は、入館情報を用いて、入館者と建物等の関係組織との関係情報を構成する。 The relationship acquisition unit 432 uses the building entry information to configure relationship information between visitors and related organizations such as buildings.
　関係取得部４３２は、例えば、交流情報決定部１３２が決定した入館情報が有する入館者情報（例えば、氏名）と建物情報（例えば、所有者情報であり、例えば、会社名）とを取得する。次に、関係取得部４３２は、当該入館者情報と当該建物情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, visitor information (eg, name) and building information (eg, owner information, such as company name) contained in the admission information determined by the interaction information determination unit 132. Next, the relationship acquisition unit 432 configures relationship information that associates the visitor information with the building information.
　なお、関係取得部４３２は、入館者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と建物情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 may search the user DB using visitor information (eg, name, phone number), acquire a user identifier, and configure relationship information that associates the user identifier with building information. good.
　また、関係取得部４３２は、建物情報が有する管理者情報（例えば、管理者の氏名、メールアドレス）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名と入館者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using administrator information (for example, the name and email address of the administrator) included in the building information, acquires the company name, and obtains the company name and visitor information. Corresponding relationship information may be configured.
　また、関係取得部４３２は、建物情報（例えば、所有者情報であり、例えば、会社名）を用いて組織ＤＢを検索し、組織識別子を取得し、当該組織識別子と入館者情報とを対応付ける関係情報を構成する。 In addition, the relationship acquisition unit 432 searches the organization DB using building information (eg, owner information, eg, company name), acquires an organization identifier, and associates the organization identifier with visitor information. configure information;
　なお、関係取得部４３２が、入館情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。
（１４）交流情報がチェックイン情報である場合 It should be noted that any method may be used by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, and the like using the museum entry information.
(14) When exchange information is check-in information
　関係取得部４３２は、チェックイン情報を用いて、チェックイン者と空間情報の関係組織との関係情報を構成する。 The relationship acquisition unit 432 uses the check-in information to compose relationship information between the check-in person and the organization related to the spatial information.
　関係取得部４３２は、例えば、交流情報決定部１３２が決定したチェックイン情報が有するチェックイン者情報（例えば、氏名）と運営者情報（例えば、運営者の会社名）とを取得する。次に、関係取得部４３２は、当該チェックイン者情報と当該運営者情報とを対応付ける関係情報を構成する。 The relationship acquisition unit 432 acquires, for example, check-in person information (eg, name) and operator information (eg, operator's company name) included in the check-in information determined by the exchange information determination unit 132 . Next, the relationship acquisition unit 432 configures relationship information that associates the check-in person information with the operator information.
　なお、関係取得部４３２は、チェックイン者情報（例えば、氏名、電話番号）を用いてユーザＤＢを検索し、ユーザ識別子を取得し、当該ユーザ識別子と運営者情報とを対応付ける関係情報を構成しても良い。 Note that the relationship acquisition unit 432 searches the user DB using check-in person information (eg, name, phone number), acquires a user identifier, and configures relationship information that associates the user identifier with operator information. can be
　また、関係取得部４３２は、運営者情報（例えば、運営者の氏名、メールアドレス）を用いてユーザＤＢを検索し、会社名を取得し、当該会社名とチェックイン者情報とを対応付ける関係情報を構成しても良い。 In addition, the relationship acquisition unit 432 searches the user DB using operator information (for example, the operator's name and email address), acquires the company name, and associates the company name with the check-in person information. may be configured.
　また、関係取得部４３２は、例えば、交流情報決定部１３２が決定したチェックイン情報が有する運営者情報（例えば、運営者の会社名）を用いて組織ＤＢを検索し、組織識別子を取得し、当該組織識別子とチェックイン者情報とを対応付ける関係情報を構成しても良い。 Further, the relationship acquisition unit 432 searches the organization DB using, for example, the operator information (for example, the operator's company name) included in the check-in information determined by the interaction information determination unit 132, acquires an organization identifier, Relationship information may be configured to associate the organization identifier and check-in person information.
　なお、関係取得部４３２が、チェックイン情報を用いて、組織識別子やユーザ識別子等を取得する方法は問わない。 It should be noted that the method by which the relationship acquisition unit 432 acquires the organization identifier, the user identifier, etc. using the check-in information does not matter.
　関係蓄積部４３３は、関係取得部４３２が取得した関係情報を蓄積する。関係蓄積部４３３が関係情報を蓄積する蓄積先は問わない。関係蓄積部４３３は、例えば、交流関係格納部４１４に関係情報を蓄積するが、図示しない外部の装置に関係情報を蓄積しても良い。 The relationship accumulation unit 433 accumulates the relationship information acquired by the relationship acquisition unit 432. The storage destination in which the relationship storage unit 433 stores the relationship information does not matter. For example, the relationship storage unit 433 stores the relationship information in the exchange relationship storage unit 414, but may store the relationship information in an external device (not shown).
　関係蓄積部４３３は、質問部１３３による問合せの結果が、関係情報を蓄積するとの結果である場合のみ、関係情報を蓄積することは好適である。 It is preferable that the relationship accumulation unit 433 accumulates the relationship information only when the result of the inquiry by the question unit 133 is to accumulate the relationship information.
　送信部４４は、各種の情報を送信する。各種の情報は、例えば、関係情報が蓄積された旨の情報、各種の情報の送信指示に対応する各種の情報を送信する。送信部４４は、例えば、関係情報の送信指示に対応する１以上の関係情報を送信する。送信部４４は、例えば、端末装置３に各種の情報を送信する。 The transmission unit 44 transmits various types of information. Various types of information are transmitted, for example, information to the effect that related information has been accumulated, and various types of information corresponding to various information transmission instructions. The transmitting unit 44, for example, transmits one or more related information corresponding to the related information transmission instruction. The transmission unit 44 transmits various kinds of information to the terminal device 3, for example.
　格納部４１、対象情報格納部４１１、交流関係格納部４１４、および組織情報格納部４１１１は、不揮発性の記録媒体が好適であるが、揮発性の記録媒体でも実現可能である。 The storage unit 41, the target information storage unit 411, the exchange relationship storage unit 414, and the organization information storage unit 4111 are preferably non-volatile recording media, but can also be realized with volatile recording media.
　格納部４１等に情報が記憶される過程は問わない。例えば、記録媒体を介して情報が格納部４１等で記憶されるようになってもよく、通信回線等を介して送信された情報が格納部４１等で記憶されるようになってもよく、あるいは、入力デバイスを介して入力された情報が格納部４１等で記憶されるようになってもよい。 The process by which information is stored in the storage unit 41 or the like does not matter. For example, information may be stored in the storage unit 41 or the like via a recording medium, or information transmitted via a communication line or the like may be stored in the storage unit 41 or the like. Alternatively, information input via an input device may be stored in the storage unit 41 or the like.
　受信部４２は、通常、無線または有線の通信手段で実現されるが、放送を受信する手段で実現されても良い。 The receiving unit 42 is usually realized by wireless or wired communication means, but may be realized by means for receiving broadcast.
　処理部４３、関係取得部４３２、および関係蓄積部４３３は、通常、プロセッサやメモリ等から実現され得る。処理部４３等の処理手順は、通常、ソフトウェアで実現され、当該ソフトウェアはＲＯＭ等の記録媒体に記録されている。但し、ハードウェア（専用回路）で実現しても良い。なお、プロセッサは、ＣＰＵ、ＭＰＵ、ＧＰＵ等であり、その種類は問わない。 The processing unit 43, the relationship acquiring unit 432, and the relationship accumulating unit 433 can usually be implemented by a processor, memory, or the like. The processing procedure of the processing unit 43 and the like 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 may be a CPU, MPU, GPU, or the like, and may be of any type.
　送信部４４は、通常、無線または有線の通信手段で実現されるが、放送手段で実現されても良い。 The transmission unit 44 is usually realized by wireless or wired communication means, but may be realized by broadcasting means.
　次に、交流管理装置４の動作例について、図２６のフローチャートを用いて説明する。図２６のフローチャートにおいて、図４のフローチャートと同一のステップについて、説明を省略する。 Next, an operation example of the exchange management device 4 will be described using the flowchart of FIG. In the flow chart of FIG. 26, description of the same steps as those of the flow chart of FIG. 4 will be omitted.
　（ステップＳ２６０１）処理部４３は、交流関係情報処理を行う。交流関係情報処理とは、交流情報を用いて関係情報を取得する処理である。交流関係情報処理の例について、図２７のフローチャートを用いて説明する。 (Step S2601) The processing unit 43 performs exchange relation information processing. The interaction related information processing is a process of acquiring relationship information using interaction information. An example of the interaction relation information processing will be described with reference to the flowchart of FIG. 27 .
　なお、図２６のフローチャートにおいて、電源オフや処理終了の割り込みにより処理は終了する。 It should be noted that in the flowchart of FIG. 26, the process ends when the power is turned off or an interrupt to end the process occurs.
　次に、ステップＳ２６０１の交流関係情報処理の例について、図２７のフローチャートを用いて説明する。図２７のフローチャートにおいて、図５のフローチャートと同一のステップについて、説明を省略する。 Next, an example of the interaction relation information processing in step S2601 will be described using the flowchart of FIG. In the flow chart of FIG. 27, description of the same steps as those of the flow chart of FIG. 5 will be omitted.
　（ステップＳ２７０１）関係取得部４３２は、関係情報取得処理を行う。関係情報取得処理の例について、図２８のフローチャートを用いて説明する。 (Step S2701) The relationship acquisition unit 432 performs relationship information acquisition processing. An example of related information acquisition processing will be described with reference to the flowchart of FIG. 28 .
　（ステップＳ２７０２）関係蓄積部４３３は、ステップＳ２７０１で取得された１以上の関係情報を蓄積する。なお、関係蓄積部４３３は、図示しないバッファから１以上の関係情報を取得し、関係情報ごとに、交流関係格納部４１４に蓄積する。なお、関係蓄積部４３３が蓄積する関係情報は、例えば、個人と組織との関係情報、組織間の関係情報である。関係蓄積部４３３は、異なる種類の関係情報を、異なる記憶領域（例えば、異なるデータベース、異なる装置）に蓄積することは好適である。 (Step S2702) The relationship storage unit 433 stores one or more pieces of relationship information acquired in step S2701. Note that the relationship storage unit 433 acquires one or more pieces of relationship information from a buffer (not shown), and stores each relationship information in the exchange relationship storage unit 414 . The relational information accumulated by the relational accumulation unit 433 is, for example, relational information between an individual and an organization, and relational information between organizations. The relationship storage unit 433 preferably stores different types of relationship information in different storage areas (for example, different databases, different devices).
　次に、ステップＳ２７０１の関係情報取得処理の例について、図２８のフローチャートを用いて説明する。 Next, an example of related information acquisition processing in step S2701 will be described using the flowchart of FIG.
　（ステップＳ２８０１）関係取得部４３２は、カウンタｉに１を代入する。 (Step S2801) The relationship acquisition unit 432 substitutes 1 for the counter i.
　（ステップＳ２８０２）関係取得部４３２は、使用する交流情報を用いて取得し得るｉ番目の関係情報が存在するか否かを判断する。ｉ番目の関係情報が存在する場合はステップＳ２８０３に行き、存在しない場合は上位処理にリターンする。 (Step S2802) The relationship acquisition unit 432 determines whether there is i-th relationship information that can be acquired using the exchange information to be used. If the i-th relational information exists, go to step S2803; otherwise, return to the higher-level processing.
　なお、ｉ番目の関係情報は、組織と個人の関係情報、組織間の関係情報のうちのいずれかである。そのような関係情報を取得するかは、交流情報の種類によって、予め決まっている。また、組織と個人の関係情報は、通常、１または２つである。 It should be noted that the i-th relational information is either relational information between an organization and an individual, or relational information between organizations. Whether to acquire such relationship information is determined in advance depending on the type of exchange information. Also, there are usually one or two pieces of relationship information between an organization and an individual.
　（ステップＳ２８０３）関係取得部４３２は、使用する交流情報を用いて、第一識別子を取得する。 (Step S2803) The relationship acquisition unit 432 acquires the first identifier using the exchange information to be used.
　（ステップＳ２８０４）関係取得部４３２は、使用する交流情報を用いて、第二識別子を取得する。 (Step S2804) The relationship acquisition unit 432 acquires the second identifier using the exchange information to be used.
　（ステップＳ２８０５）関係取得部４３２は、第一識別子と第二識別子とを用いて関係情報を構成し、図示しないバッファに一時蓄積する。 (Step S2805) The relationship acquisition unit 432 constructs relationship information using the first identifier and the second identifier, and temporarily stores it in a buffer (not shown).
　（ステップＳ２８０６）関係取得部４３２は、カウンタｉを１，インクリメントする。ステップＳ２８０２に戻る。 (Step S2806) The relationship acquisition unit 432 increments the counter i by 1. Return to step S2802.
　なお、図２８のフローチャートにおいて、関係取得部４３２が関係情報を構成する処理の種々の具体例は、上述した。 In the flowchart of FIG. 28, various specific examples of the process of configuring the relationship information by the relationship acquisition unit 432 have been described above.
　以下、本実施の形態における交流管理システムＢの具体的な動作例について説明する。 A specific operation example of the exchange management system B in this embodiment will be described below.
　今、ユーザ情報格納部１１１には、図８に示すユーザ情報管理表が格納されている、とする。 Assume that the user information management table shown in FIG. 8 is stored in the user information storage unit 111 now.
　また、組織情報格納部４１１１には、図２９に示す組織情報管理表が格納されている。組織情報管理表は、１以上の組織情報を管理する表である。組織情報は、ここでは、「組織識別子」「会社名」「電話番号」を有する。 Also, the organization information storage unit 4111 stores an organization information management table shown in FIG. The organization information management table is a table for managing one or more pieces of organization information. The organization information here has "organization identifier", "company name" and "telephone number".
　また、交流関係格納部４１４には、図３０に示す構造を有する第一関係管理表が格納されている、とする。第一関係管理表は、個人と組織（ここでは、会社）との関係を特定する第一関係情報を管理する表である。第一関係管理表は、「ＩＤ」「第一識別子（ユーザ識別子）」「第二識別子」「種類」を有する１以上のレコードを管理する。「ＩＤ」はレコードを識別する情報である。「第一識別子（ユーザ識別子）」は、関係情報を構成する第一識別子であり、ここではユーザ識別子である。「第二識別子」は、「会社名」「組織識別子」を有する。「第二識別子」の一部または全部は、関係情報を構成する第二識別子である。第二識別子は、ここでは、「会社名」、「組織識別子」、または「会社名」と「組織識別子」である。「種類」は、関係情報を取得する元になった交流情報の種類を特定する情報である。ここでは、例えば、「契約書」「請求書」または「イベント」である。 It is also assumed that the interaction relationship storage unit 414 stores a first relationship management table having the structure shown in FIG. The first relationship management table is a table for managing first relationship information that specifies the relationship between individuals and organizations (here, companies). The first relationship management table manages one or more records having "ID", "first identifier (user identifier)", "second identifier" and "type". "ID" is information for identifying a record. The "first identifier (user identifier)" is the first identifier that constitutes the relationship information, and is a user identifier here. "Secondary identifier" has "company name" and "organization identifier". Part or all of the "second identifier" is a second identifier that constitutes the relationship information. The second identifier here is "company name", "organization identifier", or "company name" and "organization identifier". "Type" is information specifying the type of exchange information from which the relationship information is acquired. Here, for example, "contract", "invoice" or "event".
　また、交流関係格納部４１４には、図３１に示す構造を有する第二関係管理表が格納されている、とする。第二関係管理表は、組織と組織との関係を特定する第二関係情報を管理する表である。第二関係管理表は、「ＩＤ」「第一識別子」「第二識別子」「種類」を有する１以上のレコードを管理する。図３１の「第一識別子」「第二識別子」は、それぞれ「会社名」「組織識別子」を有する。 It is also assumed that the interaction relationship storage unit 414 stores a second relationship management table having the structure shown in FIG. The second relationship management table is a table for managing second relationship information specifying relationships between organizations. The second relationship management table manages one or more records having "ID", "first identifier", "second identifier" and "type". The "first identifier" and "second identifier" in FIG. 31 respectively have "company name" and "organization identifier".
　かかる状況において、以下の２つの具体例について説明する。具体例１は、個人と組織との関係を特定する第一関係情報を取得する場合である。具体例２は、組織と組織との関係を特定する第二関係情報を取得する場合である。 In this situation, the following two specific examples will be explained. A specific example 1 is a case of acquiring the first relationship information specifying the relationship between an individual and an organization. Concrete example 2 is a case of acquiring second relational information specifying a relationship between organizations.
（具体例１）
　交流管理装置４の受信部４２は、端末装置３から、関係情報を取得する指示である開始指示を受信した、とする。そして、処理部４３は、交流情報を取得するタイミングである、と判断する。 (Specific example 1)
It is assumed that the reception unit 42 of the exchange management device 4 receives a start instruction, which is an instruction to acquire the relationship information, from the terminal device 3 . Then, the processing unit 43 determines that it is time to acquire the exchange information.
　次に、処理部４３は、請求書情報を管理する情報サーバ２（請求書管理サーバ）から図２１に示す請求書管理表を取得し、格納部４１に一時蓄積した、とする。また、処理部４３は、契約書情報を管理する情報サーバ２（契約書管理サーバ）から図２２に示す契約書管理表を取得し、格納部４１に一時蓄積した、とする。さらに、処理部４３は、登録情報を管理する情報サーバ２（登録サーバ）から図２３に示す登録管理表を取得し、格納部４１に一時蓄積した、とする。 Next, it is assumed that the processing unit 43 acquires the invoice management table shown in FIG. 22 from the information server 2 (contract management server) that manages contract information, and temporarily stores it in the storage unit 41. FIG. 23 from the information server 2 (registration server) that manages registration information, and temporarily stores it in the storage unit 41. FIG.
　次に、関係取得部４３２は、上述した手順で、請求書管理表（図２１）から、１以上の第一関係情報を取得する。ここで、関係取得部４３２は、図２１の「ＩＤ＝１」のレコードを用いて、２つの第一関係情報「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」「＜第一識別子＞１００３　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」を取得する。また、関係取得部４３２は、図２１の「ＩＤ＝２」のレコードを用いて、２つの第一関係情報「＜第一識別子＞１００１　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞ＡＢ株式会社　＜組織識別子＞Ｃ０３＜／第二識別子＞」を取得する。また、関係取得部４３２は、取得した４つの各第一関係情報に、種類「請求書」を付加する。 Next, the relationship acquisition unit 432 acquires one or more pieces of first relationship information from the invoice management table (Fig. 21) according to the procedure described above. Here, the relationship acquisition unit 432 uses the record of "ID=1" in FIG. >C01</second identifier>" and "<first identifier>1003 <second identifier> <company name> Co., Ltd. X <organization identifier>C02</second identifier>". Also, the relationship acquisition unit 432 uses the record of "ID=2" in FIG. >C02</second identifier>" "<first identifier>1002 <second identifier> <company name> AB Corporation <organization identifier>C03</second identifier>". In addition, the relationship acquisition unit 432 adds the type “bill” to each of the acquired four pieces of first relationship information.
　次に、関係蓄積部４３３は、取得された４つの各第一関係情報が第一関係管理表に存在するか否かを判断する。ここで、関係蓄積部４３３は、４つの第一関係情報が第一関係管理表に存在しない、と判断した、とする。そして、関係蓄積部４３３は、４つの第一関係情報と種類「請求書」とを第一関係管理表に蓄積する。 Next, the relationship accumulation unit 433 determines whether or not each of the four obtained pieces of first relationship information exists in the first relationship management table. Here, it is assumed that the relationship accumulation unit 433 has determined that the four pieces of first relationship information do not exist in the first relationship management table. Then, the relationship accumulation unit 433 accumulates the four pieces of first relationship information and the type "bill" in the first relationship management table.
　次に、関係取得部４３２は、上述した手順で、契約書管理表（図２２）から、１以上の第一関係情報を取得する。ここで、関係取得部４３２は、図２２の「ＩＤ＝１」のレコードを用いて、２つの第一関係情報「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」「＜第一識別子＞１００３　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」を取得する。また、関係取得部４３２は、図２２の「ＩＤ＝２」のレコードを用いて、２つの第一関係情報「＜第一識別子＞１００１　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞ＡＢ株式会社　＜組織識別子＞Ｃ０３＜／第二識別子＞」を取得する。また、関係取得部４３２は、取得した４つの各第一関係情報に、種類「契約書」を付加する。 Next, the relationship acquisition unit 432 acquires one or more pieces of first relationship information from the contract management table (Fig. 22) according to the procedure described above. Here, the relationship acquisition unit 432 uses the record of "ID=1" in FIG. >C01</second identifier>" and "<first identifier>1003 <second identifier> <company name> Co., Ltd. X <organization identifier>C02</second identifier>". Also, the relationship acquisition unit 432 uses the record of "ID=2" in FIG. >C02</second identifier>" "<first identifier>1002 <second identifier> <company name> AB Corporation <organization identifier>C03</second identifier>". In addition, the relationship acquisition unit 432 adds the type “contract” to each of the acquired four pieces of first relationship information.
　次に、関係蓄積部４３３は、取得された４つの各第一関係情報が第一関係管理表に存在する、と判断する。そして、関係蓄積部４３３は、４つの各第一関係情報が種類「契約書」には対応付いていないことを検知し、４つの各第一関係情報と対になる属性値「種類」に「契約書」を付加する。 Next, the relationship accumulation unit 433 determines that each of the acquired four pieces of first relationship information exists in the first relationship management table. Then, the relationship accumulation unit 433 detects that each of the four pieces of first relationship information is not associated with the type "contract", and sets the attribute value "type" paired with each of the four pieces of first relationship information to " Add "Contract".
　次に、関係取得部４３２は、上述した手順で、登録管理表（図２３）とイベント管理表（図２４）とを参照し、１以上の第一関係情報を取得する。ここで、関係取得部４３２は、図２３の「ＩＤ＝１」のレコードを用いて、「＜氏名＞田中花子　＜会社名＞株式会社Ｘ」を取得し、当該「＜氏名＞田中花子　＜会社名＞株式会社Ｘ」をキーとしてユーザＤＢ（図８）を検索し、ユーザ識別子「１００２」を取得する。また、関係取得部４３２は、図２３の「ＩＤ＝１」のレコードを用いて、「＜イベント識別子＞Ｅ１」を取得し、当該「＜イベント識別子＞Ｅ１」をキーとしてイベント管理表（図２４）を検索し、「＜会社名＞Ｙ会社」を取得する。また、関係取得部４３２は、「＜会社名＞Ｙ会社」をキーとして、組織ＤＢ（図２９）を検索し、組織識別子「Ｃ０１」を取得する。そして、関係取得部４３２は、第一関係情報「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」を構成する。 Next, the relationship acquisition unit 432 acquires one or more pieces of first relationship information by referring to the registration management table (FIG. 23) and the event management table (FIG. 24) according to the procedure described above. Here, the relationship acquisition unit 432 acquires "<name> Hanako Tanaka <company name> Co., Ltd. X" using the record of "ID=1" in FIG. The user DB (FIG. 8) is searched using "name>corporation X" as a key, and the user identifier "1002" is acquired. Also, the relationship acquisition unit 432 acquires “<event identifier>E1” using the record “ID=1” in FIG. ) to obtain “<company name> Y company”. Also, the relationship acquisition unit 432 searches the organization DB (FIG. 29) using “<company name>Y company” as a key, and acquires the organization identifier “C01”. Then, the relationship acquisition unit 432 configures the first relationship information "<first identifier>1002 <second identifier> <company name> Y company <organization identifier> C01</second identifier>".
　また、関係取得部４３２は、図２３の「ＩＤ＝２」のレコードを用いて、「＜氏名＞青木次郎　＜会社名＞Ｙ会社」を取得し、当該「＜氏名＞青木次郎　＜会社名＞Ｙ会社」をキーとしてユーザＤＢ（図８）を検索し、ユーザ識別子「１００３」を取得する。また、関係取得部４３２は、図２３の「ＩＤ＝２」のレコードを用いて、「＜イベント識別子＞Ｅ２」を取得し、当該「＜イベント識別子＞Ｅ２」をキーとしてイベント管理表（図２４）を検索し、「＜会社名＞株式会社Ｑ」を取得する。また、関係取得部４３２は、「＜会社名＞株式会社Ｑ」をキーとして、組織ＤＢ（図２９）を検索し、組織識別子「Ｃ０４」を取得する。そして、関係取得部４３２は、第一関係情報「＜第一識別子＞１００３　＜第二識別子＞＜会社名＞株式会社Ｑ　＜組織識別子＞Ｃ０４＜／第二識別子＞」を構成する。 In addition, the relationship acquisition unit 432 acquires "<Name> Jiro Aoki <Company name> Company Y" using the record of "ID=2" in FIG. The user DB (FIG. 8) is searched using "Company Y" as a key, and the user identifier "1003" is obtained. Also, the relationship acquisition unit 432 acquires “<event identifier>E2” using the record “ID=2” in FIG. ) to obtain “<company name> Co., Ltd. Q”. Also, the relationship acquisition unit 432 searches the organization DB (FIG. 29) using "<company name> Co. Q" as a key, and acquires the organization identifier "C04". Then, the relationship acquisition unit 432 constructs the first relationship information "<first identifier>1003<second identifier><company name>Q Inc.<organization identifier>C04</second identifier>".
　また、関係取得部４３２は、図２３の「ＩＤ＝３」のレコードを用いて、「＜氏名＞田中花子　＜会社名＞株式会社Ｘ」を取得し、当該「＜氏名＞田中花子　＜会社名＞株式会社Ｘ」をキーとしてユーザＤＢ（図８）を検索し、ユーザ識別子「１００２」を取得する。また、関係取得部４３２は、図２３の「ＩＤ＝３」のレコードを用いて、「＜イベント識別子＞Ｅ２」を取得し、当該「＜イベント識別子＞Ｅ２」をキーとしてイベント管理表（図２４）を検索し、「＜会社名＞株式会社Ｑ」を取得する。また、関係取得部４３２は、「＜会社名＞株式会社Ｑ」をキーとして、組織ＤＢ（図２９）を検索し、組織識別子「Ｃ０４」を取得する。そして、関係取得部４３２は、第一関係情報「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞株式会社Ｑ　＜組織識別子＞Ｃ０４＜／第二識別子＞」を構成する。また、関係取得部４３２は、取得した３つの各第一関係情報に、種類「イベント」を付加する。 In addition, the relationship acquisition unit 432 acquires "<name> Hanako Tanaka <company name> Co., Ltd. X" using the record of "ID=3" in FIG. > Co. X" as a key to retrieve the user identifier "1002" by searching the user DB (FIG. 8). Also, the relationship acquisition unit 432 acquires “<event identifier>E2” using the record “ID=3” in FIG. ) to obtain “<company name> Co., Ltd. Q”. Also, the relationship acquisition unit 432 searches the organization DB (FIG. 29) using "<company name> Co. Q" as a key, and acquires the organization identifier "C04". Then, the relationship acquisition unit 432 configures the first relationship information "<first identifier>1002<second identifier><company name>Q Inc.<organization identifier>C04</second identifier>". Also, the relationship acquiring unit 432 adds the type “event” to each of the three pieces of first relationship information acquired.
　次に、関係蓄積部４３３は、取得された３つの各第一関係情報が第一関係管理表に存在するか否かを判断する。そして、関係蓄積部４３３は、「＜第一識別子＞１００２　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」は、既に第一関係管理表に存在する、と判断する。そして、関係蓄積部４３３は、当該第一関係情報が種類「イベント」には対応付いていないことを検知し、当該第一関係情報と対になる属性値「種類」に「イベント」を付加する。かかるレコードは、図３１の「ＩＤ＝１」のレコードである。 Next, the relationship accumulation unit 433 determines whether or not each of the three acquired first relationship information exists in the first relationship management table. Then, the relationship storage unit 433 determines that "<first identifier>1002<second identifier><company name>Y company <organization identifier>C01</second identifier>" already exists in the first relationship management table. I judge. Then, the relationship accumulation unit 433 detects that the first relationship information is not associated with the type "event", and adds "event" to the attribute value "type" paired with the first relationship information. . Such a record is the record of "ID=1" in FIG.
　また、関係蓄積部４３３は、他の２つの第一関係情報は、第一関係管理表に存在しない、と判断する。そして、関係蓄積部４３３は、当該２つの第一関係情報と種類「イベント」とを第一関係管理表に蓄積する。かかるレコードは、「ＩＤ＝１２８，１２９」のレコードである。 Also, the relationship storage unit 433 determines that the other two pieces of first relationship information do not exist in the first relationship management table. Then, the relationship accumulation unit 433 accumulates the two pieces of first relationship information and the type "event" in the first relationship management table. Such records are records of "ID=128, 129".
　以上、本具体例によれば、２種類以上の交流情報を用いて、２以上の第一関係情報を蓄積できた。 As described above, according to this specific example, it was possible to accumulate two or more pieces of first relational information using two or more types of exchange information.
（具体例２）
　交流管理装置４の格納部４１には、具体例１で述べた処理により、図２１に示す請求書管理表、図２２に示す契約書管理表、および図２３に示す登録管理表が格納されている、とする。 (Specific example 2)
21, the contract management table shown in FIG. 22, and the registration management table shown in FIG. Suppose there is.
　次に、関係取得部４３２は、上述した手順で、請求書管理表（図２１）を用いて、１以上の第二関係情報を取得する。ここで、関係取得部４３２は、２つの第二関係情報「＜第一識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第一識別子＞　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」「＜第一識別子＞＜会社名＞ＡＢ株式会社　＜組織識別子＞Ｃ０３＜／第一識別子＞　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」を取得する。また、関係取得部４３２は、取得した２つの各第二関係情報に、種類「請求書」を付加する。なお、関係取得部４３２は、会社名を用いて、組織ＤＢを検索し、組織識別子を取得するものとする。 Next, the relationship acquisition unit 432 acquires one or more pieces of second relationship information using the invoice management table (Fig. 21) according to the procedure described above. Here, the relationship acquisition unit 432 obtains the two pieces of second relationship information "<first identifier><company name> Co., Ltd. X<organization identifier>C02</first identifier><second identifier><company name>Y company <Organization Identifier> C01 </Second Identifier>" "<First Identifier> <Company Name> AB Co. <Organization Identifier> C03 </ First Identifier> <Second Identifier> <Company Name> Co. X <Organization Identifier>C02</Second Identifier>”. In addition, the relationship acquisition unit 432 adds the type “bill” to each of the two pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the organization DB using the company name and acquires the organization identifier.
　次に、関係蓄積部４３３は、取得された２つの各第二関係情報が第二関係管理表に存在するか否かを判断する。ここで、関係蓄積部４３３は、２つの第二関係情報が第二関係管理表に存在しない、と判断した、とする。そして、関係蓄積部４３３は、２つの第二関係情報と種類「請求書」とを第二関係管理表に蓄積する。 Next, the relationship accumulation unit 433 determines whether or not each of the two pieces of acquired second relationship information exists in the second relationship management table. Here, it is assumed that the relationship accumulation unit 433 determines that the two pieces of second relationship information do not exist in the second relationship management table. Then, the relationship accumulation unit 433 accumulates the two pieces of second relationship information and the type "bill" in the second relationship management table.
　次に、関係取得部４３２は、上述した手順で、契約書管理表（図２２）を用いて、１以上の第二関係情報を取得する。ここで、関係取得部４３２は、図２２を用いて、２つの第二関係情報「＜第一識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第一識別子＞　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」「＜第一識別子＞＜会社名＞ＡＢ株式会社　＜組織識別子＞Ｃ０３＜／第一識別子＞　＜第二識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第二識別子＞」を取得する。また、関係取得部４３２は、取得した２つの各第二関係情報に、種類「契約書」を付加する。なお、関係取得部４３２は、会社名を用いて、組織ＤＢを検索し、組織識別子を取得するものとする。 Next, the relationship acquisition unit 432 acquires one or more pieces of second relationship information using the contract management table (Fig. 22) according to the procedure described above. Here, using FIG. 22, the relationship acquisition unit 432 obtains the two pieces of second relationship information "<first identifier><company name> Co., Ltd. X<organization identifier>C02</first identifier><second identifier> <Company name> Company Y <Organization Identifier> C01</Second Identifier>" "<First Identifier> <Company Name> AB Corporation <Organization Identifier> C03</First Identifier> <Second Identifier> <Company Name > Co., Ltd. X <organization identifier>C02</second identifier>”. Also, the relationship acquiring unit 432 adds the type “contract” to each of the two pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the organization DB using the company name and acquires the organization identifier.
　次に、関係蓄積部４３３は、取得された２つの各第二関係情報が第二関係管理表に存在する、と判断する。そして、関係蓄積部４３３は、２つの各第二関係情報が種類「契約書」には対応付いていないことを検知し、４つの各第一関係情報と対になる属性値「種類」に「契約書」を付加する。 Next, the relationship accumulating unit 433 determines that the acquired two sets of second relationship information exist in the second relationship management table. Then, the relationship accumulation unit 433 detects that each of the two pieces of second relationship information is not associated with the type "contract", and sets the attribute value "type" paired with each of the four pieces of first relationship information to " Add "Contract".
　次に、関係取得部４３２は、上述した手順で、登録管理表（図２３）とイベント管理表（図２４）とを参照し、１以上の第二関係情報を取得する。関係取得部４３２は、上述した手順で、図２３、図２４を用いて、３つの第二関係情報「＜第一識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第一識別子＞　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」「＜第一識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第一識別子＞　＜第二識別子＞＜会社名＞株式会社Ｑ　＜組織識別子＞Ｃ０４＜／第二識別子＞」「＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第一識別子＞　＜第二識別子＞＜会社名＞株式会社Ｑ　＜組織識別子＞Ｃ０４＜／第二識別子＞」を取得する。また、関係取得部４３２は、取得した３つの各第二関係情報に、種類「イベント」を付加する。なお、関係取得部４３２は、図２３のイベント識別子をキーとして、図２４のイベント管理表を検索し、会社名を取得する。また、関係取得部４３２は、当該会社名をキーとして組織ＤＢを検索し、組織識別子を取得する。 Next, the relationship acquisition unit 432 acquires one or more pieces of second relationship information by referring to the registration management table (FIG. 23) and the event management table (FIG. 24) according to the procedure described above. The relationship acquisition unit 432 uses FIGS. 23 and 24 to obtain the three pieces of second relationship information "<first identifier><company name><organization identifier>C02</first identifier> <Second Identifier><Company Name>Company Y <Organization Identifier>C01</Second Identifier>" "<First Identifier><Company Name>Company Y <Organization Identifier>C01</First Identifier><Second Identifier> > <Company name> Co., Ltd. Q <Organization identifier> C04 </second identifier>" "<Company name> Co., Ltd. X <Organization identifier> C02 </ first identifier> <Second identifier> <Company name> Co., Ltd. Q <organization identifier>C04</second identifier>". Also, the relationship acquiring unit 432 adds the type “event” to each of the three pieces of acquired second relationship information. Note that the relationship acquisition unit 432 searches the event management table of FIG. 24 using the event identifier of FIG. 23 as a key to acquire the company name. The relationship acquisition unit 432 also searches the organization DB using the company name as a key to acquire an organization identifier.
　次に、関係蓄積部４３３は、取得された第二関係情報「＜第一識別子＞＜会社名＞株式会社Ｘ　＜組織識別子＞Ｃ０２＜／第一識別子＞　＜第二識別子＞＜会社名＞Ｙ会社　＜組織識別子＞Ｃ０１＜／第二識別子＞」が第二関係管理表に存在する、と判断する。また、関係蓄積部４３３は、当該第二関係情報が種類「イベント」には対応付いていないことを検知し、当該第二関係情報と対になる属性値「種類」に「イベント」を付加する。かかるレコードは、図３１の「ＩＤ＝１」のレコードである。 Next, the relationship accumulation unit 433 stores the acquired second relationship information "<first identifier><company name> Co., Ltd. X<organization identifier>C02</first identifier><second identifier><company name>Y Company <Organization Identifier>C01</Second Identifier>" is determined to exist in the second relationship management table. Further, the relationship accumulation unit 433 detects that the second relationship information is not associated with the type "event", and adds "event" to the attribute value "type" paired with the second relationship information. . Such a record is the record of "ID=1" in FIG.
　また、関係蓄積部４３３は、取得された残る２つの第二関係情報は第二関係管理表に存在しない、と判断する。そして、関係蓄積部４３３は、２つの第二関係情報を取類「イベント」に対応付けて蓄積する。かかるレコードは、図３１の「ＩＤ＝５８，５９」のレコードである。 Also, the relationship accumulation unit 433 determines that the remaining two acquired second relationship information do not exist in the second relationship management table. Then, the relationship accumulating unit 433 associates the two pieces of second relation information with the class "event" and accumulates them. Such a record is the record of "ID=58, 59" in FIG.
　以上、本実施の形態によれば、交流情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できる。 As described above, according to the present embodiment, it is possible to acquire and manage relational information relating to the connection between two parties using exchange information.
　また、本実施の形態によれば、２種類以上の交流情報を用いて、関係情報を取得し、管理できる。 Also, according to the present embodiment, it is possible to acquire and manage related information using two or more types of exchange information.
　また、本実施の形態によれば、適切な交流情報のみを用いて、関係情報を取得し、管理できる。 Also, according to the present embodiment, it is possible to acquire and manage related information using only appropriate exchange information.
　また、本実施の形態によれば、ユーザにとって必要な関係情報のみを蓄積できる。 Also, according to the present embodiment, it is possible to accumulate only the relevant information necessary for the user.
　さらに、本実施の形態によれば、対象情報格納部を用いて、正確な関係情報を取得し、管理できる。 Furthermore, according to the present embodiment, accurate relational information can be obtained and managed using the target information storage unit.
　なお、本実施の形態における交流管理装置４を実現するソフトウェアは、以下のようなプログラムである。つまり、このプログラムは、コンピュータを、二者以上の間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流決定部と、前記交流決定部が取得した交流情報に対応する二者の各々の対象識別子である第一識別子と第二識別子とを対応付けた関係情報を取得する関係取得部と、前記関係取得部が取得した関係情報を蓄積する関係蓄積部として機能させるためのプログラムである。 The software that implements the exchange management device 4 in this embodiment is the following program. In other words, the program comprises: an exchange determination unit that acquires exchange information from a storage unit that stores one or more exchange information that is information related to an exchange between two or more parties; A relationship acquisition unit that acquires relationship information in which a first identifier and a second identifier, which are object identifiers of each of two parties corresponding to the acquired interaction information, are associated with each other, and accumulates the relationship information acquired by the relationship acquisition unit. This is a program for functioning as a relation storage unit.
　また、図３２は、本明細書で述べたプログラムを実行して、上述した種々の実施の形態の交流管理装置４等を実現するコンピュータの外観を示す。上述の実施の形態は、コンピュータハードウェア及びその上で実行されるコンピュータプログラムで実現され得る。図３２は、このコンピュータシステム３００の概観図であり、図３３は、システム３００のブロック図である。 Also, FIG. 32 shows the appearance of a computer that executes the programs described in this specification and realizes the exchange management device 4 and the like of the various embodiments described above. The embodiments described above may be implemented in computer hardware and computer programs running thereon. FIG. 32 is an overview diagram of this computer system 300, and FIG. 33 is a block diagram of the system 300. As shown in FIG.
　図３２において、コンピュータシステム３００は、ＣＤ－ＲＯＭドライブを含むコンピュータ３０１と、キーボード３０２と、マウス３０３と、モニタ３０４とを含む。 In FIG. 32, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303 and a monitor 304.
　図３３において、コンピュータ３０１は、ＣＤ－ＲＯＭドライブ３０１２に加えて、ＭＰＵ３０１３と、ＣＤ－ＲＯＭドライブ３０１２等に接続されたバス３０１４と、ブートアッププログラム等のプログラムを記憶するためのＲＯＭ３０１５と、ＭＰＵ３０１３に接続され、アプリケーションプログラムの命令を一時的に記憶するとともに一時記憶空間を提供するためのＲＡＭ３０１６と、アプリケーションプログラム、システムプログラム、及びデータを記憶するためのハードディスク３０１７とを含む。ここでは、図示しないが、コンピュータ３０１は、さらに、ＬＡＮへの接続を提供するネットワークカードを含んでも良い。 33, 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 computer system 300 to execute the functions of exchange management device 4 of the above-described embodiment may be stored in CD-ROM 3101, inserted into CD-ROM drive 3012, and transferred to 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 4 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.
　以上のように、本発明にかかる交流管理装置４は、交流に関する交流情報を用いて、二者間の結びつきに関する関係情報を取得し、管理できるという効果を有し、交流情報を管理するサーバ等として有用である。 As described above, the exchange management device 4 according to the present invention has the effect of being able to acquire and manage relational information concerning the connection between two parties using exchange information concerning exchanges, and a server or the like that manages exchange information. is useful as

Claims (11)

  1. 二者以上の間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流決定部と、
    前記交流決定部が取得した交流情報に対応する二者の各々の対象識別子である第一識別子と第二識別子とを対応付けた関係情報を取得する関係取得部と、
    前記関係取得部が取得した関係情報を蓄積する関係蓄積部とを具備する交流管理装置。     an exchange determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information about exchanges between two or more parties;
    a relationship acquisition unit that acquires relationship information that associates a first identifier and a second identifier, which are object identifiers of each of two parties corresponding to the interaction information acquired by the interaction determination unit;
    and a relationship storage unit that stores the relationship information acquired by the relationship acquisition unit.
  2. 前記格納部に格納されている２以上の交流情報には、２種類以上の交流情報が含まれ、
    前記交流決定部は、
    前記格納部から、２種類以上の交流情報を取得する請求項１記載の交流管理装置。     The two or more pieces of exchange information stored in the storage unit include two or more types of exchange information,
    The alternating current determination unit
    2. The exchange management device according to claim 1, wherein two or more types of exchange information are acquired from said storage unit.
  3. 前記交流決定部は、
    前記格納部から、予め決められた条件を満たす交流情報を取得する請求項１または請求項２記載の交流管理装置。     The alternating current determination unit
    3. The exchange management device according to claim 1, wherein the exchange information that satisfies a predetermined condition is acquired from the storage unit.
  4. 前記関係情報を蓄積するか否かをユーザに問い合わせる質問部をさらに具備し、
    前記関係蓄積部は、
    前記質問部による問合せの結果が、前記関係情報を蓄積するとの結果である場合のみ、前記関係情報を蓄積する請求項１から請求項３いずれか一項に記載の交流管理装置。     further comprising an inquiry unit for inquiring of the user whether to store the relevant information;
    The relationship storage unit
    4. The exchange management device according to any one of claims 1 to 3, wherein the relationship information is stored only when the result of the inquiry by the question unit is to store the relationship information.
  5. 前記関係取得部は、
    前記交流決定部が決定した交流情報に含まれる文字列または前記交流情報に対応する対象識別子を用いて、当該対象識別子と１以上の対象属性値とを有する１以上の対象情報が格納される対象情報格納部を検索し、当該検索結果を用いて、前記関係情報を取得する請求項１から請求項４いずれか一項に記載の交流管理装置。     The relationship acquisition unit
    Objects in which one or more pieces of object information having the object identifier and one or more object attribute values are stored using a character string included in the exchange information determined by the exchange determination unit or an object identifier corresponding to the exchange information 5. The exchange management device according to any one of claims 1 to 4, wherein an information storage unit is searched and the relevant information is acquired using the search result.
  6. 前記交流情報は、ユーザ間で行われたチャットにおけるチャット履歴情報、ユーザ間の電話での通話の履歴の情報である通話履歴情、請求書情報、契約書情報、イベントに登録した登録者の登録情報、組織のウェブサイト上の問い合わせフォームに対して入力された問合情報、贈り元から贈り先に送信されるギフトに関するギフト情報、営業活動情報、顧客情報、注文情報、採用情報、パンフレット取得情報、経費情報、アンケート情報、入館情報、またはバーチャル空間チェックイン情報である請求項１から請求項５いずれか一項に記載の交流管理装置。 The exchange information includes chat history information in chats conducted between users, call history information that is information on the history of telephone calls between users, invoice information, contract information, and registration of registrants registered in the event. Information, inquiry information entered in the inquiry form on the organization's website, gift information regarding gifts sent from the gift giver to the gift recipient, sales activity information, customer information, order information, employment information, information on obtaining brochures , expense information, questionnaire information, admission information, or virtual space check-in information.
  7. 第一識別子に対応付けて他のユーザの名刺に関する名刺情報を受け付ける名刺情報受付部と、
    前記関係取得部は、
    前記第一識別子と前記名刺情報に対応する第二識別子とを対応付けた前記関係情報を取得する請求項１から請求項６いずれか一項に記載の交流管理装置。     a business card information reception unit that receives business card information related to business cards of other users in association with the first identifier;
    The relationship acquisition unit
    7. The exchange management device according to claim 1, wherein the relationship information in which the first identifier and the second identifier corresponding to the business card information are associated is acquired.
  8. 前記交流情報に対応する前記第二識別子で識別されるユーザの情報である他ユーザ情報に変化があるか否かを判断する変化判断部と、
    変化があると前記変化判断部が判断した場合に、予め決められた処理を行う交流処理部とをさらに具備する請求項１から請求項７いずれか一項に記載の交流管理装置。     a change determination unit that determines whether or not there is a change in other user information, which is the information of the user identified by the second identifier corresponding to the exchange information;
    8. The exchange management apparatus according to any one of claims 1 to 7, further comprising an exchange processing unit that performs predetermined processing when the change judgment unit judges that there is a change.
  9. 前記交流情報は、
    二者以上の間でのコミュニケーションを直接的な目的とはしない情報システムにおいて蓄積された非コミュニケーションシステム情報である請求項１から請求項８いずれか一項に記載の交流管理装置。     The exchange information is
    9. The exchange management device according to any one of claims 1 to 8, which is non-communication system information accumulated in an information system whose direct purpose is not communication between two or more parties.
  10. 交流決定部と、関係取得部と、関係蓄積部とにより実現される交流管理方法であって、
    前記交流決定部が、二者以上の間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流決定ステップと、
    前記関係取得部が、前記交流決定部が取得した交流情報に対応する二者の各々の対象識別子である第一識別子と第二識別子とを対応付けた関係情報を取得する関係取得ステップと、
    前記関係蓄積部が、前記関係取得部が取得した関係情報を蓄積する関係蓄積ステップとにより実現される交流管理方法。     An exchange management method implemented by an exchange determination unit, a relationship acquisition unit, and a relationship storage unit,
    an exchange decision step in which the exchange decision unit acquires exchange information from a storage unit that stores one or more exchange information, which is information about an exchange between two or more parties;
    a relationship acquisition step in which the relationship acquisition unit acquires relationship information in which a first identifier and a second identifier, which are object identifiers of each of two parties corresponding to the interaction information acquired by the interaction determination unit, are associated with each other;
    and a relationship storage step in which the relationship storage unit stores the relationship information acquired by the relationship acquisition unit.
  11. コンピュータを、
    二者以上の間での交流に関する情報である１または２以上の交流情報を格納する格納部から、交流情報を取得する交流決定部と、
    前記交流決定部が取得した交流情報に対応する二者の各々の対象識別子である第一識別子と第二識別子とを対応付けた関係情報を取得する関係取得部と、
    前記関係取得部が取得した関係情報を蓄積する関係蓄積部として機能させるためのプログラム。     the computer,
    an exchange determination unit that acquires exchange information from a storage unit that stores one or more pieces of exchange information that are information about exchanges between two or more parties;
    a relationship acquisition unit that acquires relationship information that associates a first identifier and a second identifier, which are object identifiers of each of two parties corresponding to the interaction information acquired by the interaction determination unit;
    A program for functioning as a relationship storage unit that stores relationship information acquired by the relationship acquisition unit.
PCT/JP2022/008005 2021-03-05 2022-02-25 Interaction management device, interaction management method, and program WO2022186085A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2023503788A JPWO2022186085A1 (en) 2021-03-05 2022-02-25

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2021035197 2021-03-05
JP2021-035197 2021-03-05
JP2022025057 2022-02-21
JP2022-025057 2022-02-21

Publications (1)

Publication Number Publication Date
WO2022186085A1 true WO2022186085A1 (en) 2022-09-09

Family

ID=83154395

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/008005 WO2022186085A1 (en) 2021-03-05 2022-02-25 Interaction management device, interaction management method, and program

Country Status (2)

Country Link
JP (1) JPWO2022186085A1 (en)
WO (1) WO2022186085A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7401044B1 (en) 2023-04-19 2023-12-19 株式会社immedio How to handle user inquiries for your company

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004240676A (en) * 2003-02-05 2004-08-26 Seiko Epson Corp System and program for managing business card
JP2009129239A (en) * 2007-11-26 2009-06-11 Sansan Inc Apparatus, method and program for transfer information notification
JP2019101935A (en) * 2017-12-06 2019-06-24 Sansan株式会社 Information processor, information processor, and program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004240676A (en) * 2003-02-05 2004-08-26 Seiko Epson Corp System and program for managing business card
JP2009129239A (en) * 2007-11-26 2009-06-11 Sansan Inc Apparatus, method and program for transfer information notification
JP2019101935A (en) * 2017-12-06 2019-06-24 Sansan株式会社 Information processor, information processor, and program

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7401044B1 (en) 2023-04-19 2023-12-19 株式会社immedio How to handle user inquiries for your company

Also Published As

Publication number Publication date
JPWO2022186085A1 (en) 2022-09-09

Similar Documents

Publication Publication Date Title
Chen et al. A symbolic interactionism perspective of using social media for personal and business communication
CN102150161A (en) Ranking search results based on affinity criteria
US20110161253A1 (en) Systems and methods for managing social internetwork services
US20030078833A1 (en) Marketing supporting method and device using electronic message
Bergquist et al. Genres in action: Negotiating genres in practice
US20040215502A1 (en) Evaluation apparatus and evaluation method
WO2022186085A1 (en) Interaction management device, interaction management method, and program
O’Kane et al. Communication without frontiers: The impact of technology upon organizations
CN103246975A (en) Task data sharing system and method
Murnan Expanding communication mechanisms: they're not just e-mailing anymore
JP2008293345A (en) Business activity support system, business activity support program and server device
WO2022185556A1 (en) Interaction management device, interaction management method, and recording medium
JP2002230271A (en) Method of replying to inquiry, and program
Bean et al. Electronic mail appraisal: a buyer and seller survey
JP2002203039A (en) Server for recruitment management system
JP5069762B2 (en) CRM server, e-mail transmission / reception method and program
JP5105265B2 (en) Will collection method, will confirmation system, and will collection system
JP6290620B2 (en) Information provision and collection system using communication terminals
JP5382753B1 (en) Information provision and collection system using communication terminals
US10733252B2 (en) Expanding activity channels in an online network
Wojciechowski Supporting social networks by event-driven mobile notification services
Grace Using Communication and Information Technologies To Empower Women in Rural Communities.
Dos Santos et al. The Internet: a key tool for today's human resource professional
Das Reaching Consumers with Effective Email Marketing Strategy
TW202141409A (en) Community care system for establishing interpersonal network comprising a resource planning host, a first application program and a second application program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22763141

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023503788

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22763141

Country of ref document: EP

Kind code of ref document: A1