JP5986009B2 - Inquiry system and inquiry method - Google Patents

Description

  The present invention relates to an inquiry system and an inquiry method.

  Conventionally, an IP telephone service, an IP messaging service, and the like are known as communication services between users. In the current IP telephone service and IP messaging service, when connecting between the arrival and departure terminals, both terminals of the users need to subscribe to the same service.

  For example, when a user uses a plurality of services and makes / receives calls with other user terminals, the application of the same service is started and logged in at both user terminals. Then, the calling user terminal connects the same service on the receiving side between the calling and receiving terminals.

Skype “Let's create Skype account (Preparation)” [online], [Search February 5, 2013], Internet <http://fibonacci.cc.niigata-u.ac.jp/mikawa/tech/skype /skype_account.html>

  However, in the conventional technology described above, there is a problem that communication between users may be troublesome when a plurality of services are used, which hinders communication between users from being promoted.

  For example, when connecting between the arrival and departure terminals, both terminals of the users have to subscribe to the same service, launch an application of the same service, and log in. Further, for example, when a plurality of services are used, it is necessary that the user terminal on the transmission side knows the user ID in the same service of the user terminal on the reception side. For this reason, it takes time to communicate between users, which may hinder the promotion of communication between users.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and an object thereof is to reduce the effort required for communication between users and promote communication between users.

  In order to solve the above-described problems and achieve the object, the inquiry system stores, for each user, the service type of the service used by the user and the contact information for using the service in association with each other. A storage unit; a receiving unit that receives an inquiry about contact information of a service used by a second user terminal other than the first user terminal from a first user terminal among user terminals used by the user; When the inquiry is received by the reception unit, the storage unit acquires the service type and the contact information corresponding to the second user terminal from the storage unit and the acquisition unit acquires the service type and the contact information. And a transmission unit that transmits the service type and contact information to the first user terminal.

  The inquiry method is an inquiry method executed by an inquiry system, and the inquiry system includes, for each user, a service type of a service used by the user, contact information when using the service, and Inquiry of contact information of services used by second user terminals other than the first user terminal from the first user terminal among user terminals used by the user Receiving step, and when the inquiry is received by the receiving step, the storage unit acquires the service type and the contact information corresponding to the second user terminal from the storage unit. A transmitter that transmits the service type and contact information acquired by the acquisition step to the first user terminal. And wherein the containing when the.

  The inquiry system and the inquiry method disclosed in the present application can reduce the effort required for communication between users and promote communication between users.

FIG. 1 is a diagram illustrating an example of a configuration of an inquiry system according to the first embodiment. FIG. 2 is a diagram for explaining the configuration of the inquiry server according to the first embodiment. FIG. 3 is a diagram illustrating an example of information stored by the user ID storage unit according to the first embodiment. FIG. 4 is a diagram illustrating an example of processing when registering a user ID. FIG. 5 is a diagram illustrating an example of processing when registering a user ID. FIG. 6 is a diagram illustrating an example of processing when managing user IDs. FIG. 7 is a diagram illustrating an example of user ID grouping processing. FIG. 8 is a diagram illustrating an example of processing for confirming the identity of a user ID. FIG. 9 is a diagram illustrating an example of a process of collecting presence status of user IDs. FIG. 10 is a diagram illustrating an example of a user ID inquiry process. FIG. 11 is a diagram illustrating an example of an interconnection process between different services. FIG. 12 is a sequence diagram showing a flow of inquiry processing by the inquiry system according to the first embodiment. FIG. 13 is a sequence diagram showing a flow of interconnection processing by the inquiry system according to the first embodiment. FIG. 14 is a diagram illustrating a computer that executes an inquiry program.

  Hereinafter, embodiments of an inquiry system and an inquiry method according to the present invention will be described in detail with reference to the accompanying drawings. In addition, this invention is not limited by this embodiment.

[First embodiment]
In the following embodiments, the configuration of the inquiry system according to the first embodiment, the configuration of the inquiry server, and the flow of processing by the inquiry system will be described in order, and finally the effects of the first embodiment will be described.

[System configuration]
First, an example of the configuration of an inquiry system 100 to which the inquiry server 10 according to the first embodiment is applied will be described. FIG. 1 is a diagram illustrating an example of a configuration of an inquiry system according to the first embodiment. As shown in FIG. 1, an inquiry system 100 according to the first embodiment includes an inquiry server 10, a plurality of user terminals 20A and 20B, and a service A server 30A and a service B server 30B that provide different services. . Each server 10, 30A, 30B and user terminals 20A, 20B are connected to each other via, for example, the Internet (not shown). The system configuration is not limited to the example shown in FIG.

  The user terminals 20A and 20B are connected to the Internet such as a mobile phone, a PHS (Personal Handyphone System), a PDA (Personal Digital Assistant), a tablet PC (Personal Computer), etc., and connected to the inquiry server 10 and other user terminals. Any device can be used as long as it can transmit and receive information between them. Moreover, it is not limited to a portable terminal, You may use the computer installed in the home or the office as user terminal 20A, 20B. Note that the user terminals 20 </ b> A and 20 </ b> B are referred to as user terminals 20 when they are described without particular distinction.

  The service A server 30A is a server that provides the service A, and the service B server 30B is a server that provides the service B. Note that the service A server 30A and the service B server 30B are referred to as the service server 30 when they are described without particular distinction. The service server 30 is a server that provides services such as Skype (registered trademark) and LINE (registered trademark), which are IP telephone services, for example, and subscribes to the same service using available media such as text, voice, and video. The communication between the logged-in user terminals 20 is controlled.

  The inquiry server 10 receives an inquiry about the service type and user ID (contact information such as a user ID, a mobile phone number, and a mail address in various services) of the service used by the other user terminal 20 from the user terminal 20. And the inquiry server 10 will acquire the service classification and user ID corresponding to the other user terminal 20 from the user ID memory | storage part 13a mentioned later, if an inquiry is received. Then, the inquiry server 10 returns the acquired service type and user ID to the user terminal 20 that made the inquiry. Hereinafter, the configuration of the inquiry server 10 will be described with reference to FIG.

[Configuration of inquiry server]
Next, the configuration of the inquiry server 10 shown in FIG. 1 will be described with reference to FIG. FIG. 2 is a diagram for explaining the configuration of the inquiry server according to the first embodiment. As illustrated in FIG. 2, the inquiry server 10 includes a communication processing unit 11, a control unit 12, and a storage unit 13.

  The communication processing unit 11 controls communication related to various information exchanged between the connected user terminal 20 and the service server 30. For example, the communication processing unit 11 receives a user ID registration, change, or deletion request from the user terminal 20 or a user ID grouping instruction.

  As shown in FIG. 2, the storage unit 13 includes a user ID storage unit 13a. The storage unit 13 is, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk.

  For each user terminal 20 used by the user, the user ID storage unit 13a stores the service type of the service used by the user terminal 20 and the user ID used when using the service in association with each other. For example, as illustrated in FIG. 3, the user ID storage unit 13 a includes a “service type” that indicates a service type, “contact information” that is information about a contact for using the service, a service type, The “group” indicating the group to which the contact information belongs and the “presence state” indicating the current connection state with respect to the service of the user terminal 20 are stored in association with each other. The example shown in FIG. 3 shows an example of information related to one user terminal 20 (or one user). Besides the information shown in FIG. 3, the user ID storage unit 13 a Similarly, the service types and contact information are stored for the plurality of users.

  Returning to FIG. 2, the control unit 12 includes a registration unit 12a, an authentication unit 12b, a collection unit 12c, a reception unit 12d, an acquisition unit 12e, a transmission unit 12f, and a connection unit 12g. Here, the control unit 12 is an electronic circuit such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

  When the registration unit 12a receives a registration request for the service type and user ID of the service used by the user of the user terminal 20 from the user terminal 20, the registration unit 12a registers the service type and user ID in the user ID storage unit 13a. To do.

  For example, the registration unit 12a accepts a registration request from the user terminal 20, and accepts a setting of a user ID that permits transmission to another user terminal 20 among the user IDs that accepted the registration request. Here, a process when registering a user ID will be described using the examples of FIGS. 4 and 5. 4 and 5 are diagrams illustrating an example of processing when registering a user ID. As illustrated in FIG. 4, for example, the inquiry server 10 registers the user X when receiving a user registration request from the user terminal 20 </ b> A owned by the user X.

  Then, as illustrated in FIG. 5, the registered user terminal 20 </ b> A uses a dedicated application (for example, an application for various OSs or a web application) to obtain a user ID such as a VoIP service under its management. sign up. In the example of FIG. 5, the user terminal 20 </ b> A registers a mobile number “090xxxxxxxx”, a mail address “◯@xxx.ne.jp”, and “USER_ID_A” as user IDs.

  The registration unit 12a accepts registration, change, and deletion of a user ID that has been registered once. Here, a process when managing user IDs will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of processing when managing user IDs. As illustrated in FIG. 6, the inquiry server 10 receives a registration, change, or deletion request for its own user ID from the user terminal 20 </ b> A, and performs registration, change, or deletion of the user ID according to the received request. For example, the user terminal 20A logs into the inquiry server 10 as necessary, and registers, changes, or deletes registration information of various user IDs, and edits the registration information.

  The registration unit 12a accepts a registration request from the user terminal 20, and accepts a setting for dividing a set of a plurality of service types and user IDs for which the registration request is accepted into a predetermined group. Here, user ID grouping processing will be described with reference to the example of FIG. FIG. 7 is a diagram illustrating an example of user ID grouping processing. As illustrated in FIG. 7, for example, when receiving a setting request from the user terminal 20 </ b> A, the inquiry server 10 performs grouping of user IDs according to the received setting request. For example, in the example of FIG. 7, the inquiry server 10 divides “mobile phone number”, “mobile mail address”, and “service B ID” into “groups for business persons” as the user ID of the user X, “Service A ID”, “Service C ID”, and “Service D ID” are divided into “groups for friends in school days”.

  For example, when setting the grouping, the user X groups user IDs according to the community using the service. In addition, for example, the user X performs grouping of registered user IDs in consideration of a range that “if a user knows this ID, the ID of another service may be notified”.

  When the registration request is accepted by the registration unit 12a, the authentication unit 12b requests authentication information for confirming whether or not the user of the user terminal 20 is the registrant to the user terminal 20 that has made the registration request. To do.

  Here, with reference to FIG. 8, a specific processing example when the identity confirmation of the user ID is performed will be described. FIG. 8 is a diagram illustrating an example of processing for confirming the identity of a user ID. As shown in (1) of FIG. 8, the user X who owns the user terminal 20A logs in to the inquiry server 10 and registers a telephone number, a mail address, and user IDs of various services.

  Then, in order to confirm that the owner of the user ID is definitely the person, the inquiry server 10 transmits the passcode by a method in which the passcode can be confirmed only when logged in with the account of the user ID. For example, if the ID of the IP messaging service is confirmed, the passcode is sent in a private message that can be viewed only by the person who has logged in to the service.

  Thereafter, the inquiry server 10 causes the user ID to be confirmed by inputting the passcode transmitted to the user X again. For example, when the user X logs in to the inquiry server 10 again and inputs the transmitted passcode to prove that the user has the registered telephone number or user ID, the inquiry server 10 identifies the user ID. The state is confirmed.

  In addition, when a user registers for a new service, the user ID and password registered in the inquiry server 10 are used for authentication, so that the identity verification work such as a telephone number can be omitted. For example, as shown in FIG. 8B, when the user terminal 20B owned by the user Y registers a new service for the service B, the user name and password in the inquiry server 10 are stored in the service B server 30. Notice. Then, the service B server 30 requests the inquiry server 10 to inquire about the user name and password in the inquiry server 10 input by the user Y. If the service B server 30 is successful, the identity verification such as the telephone number is completed. As described above, the inquiry server 10 performs the identity verification on behalf of the user, thereby providing, for example, a business model for obtaining compensation from an IP messenger or an IP telephone service provider.

  The collection unit 12c collects the presence status of each user terminal for each service from the service server 30 that provides the service, and stores the presence status in the user ID storage unit 13a. Here, the process of collecting the presence status of the user ID will be described using the example of FIG. FIG. 9 is a diagram illustrating an example of a process of collecting presence status of user IDs. As illustrated in FIG. 9, the inquiry server 10 collects information on the presence status of each service A and B from the service A server 30A and the service B server 30B.

  For example, using the registered user ID, the collection unit 12c acquires presence states such as various IP messaging and VoIP services, and stores the presence states in the user ID storage unit 13a. For example, in the example of FIG. 9, it is assumed that the presence status of service A is that user X and user Z are “online” and user Y is “offline”. Further, it is assumed that the presence status of service B is that user Y and user Z are “online” and user X is “offline”. Here, the presence status of the service is “online” means, for example, a state where the user terminal 20 is logged in by starting an application for using the service. Further, the collected presence status is not limited to “online” or “offline”. For example, the collection unit 12c is set for each service such as “busy” or “disconnected”. Information indicating the connection state may be collected, or information indicating the user's own state that can be freely set by the user, such as “being away” or “mealing”, may be collected.

  The receiving unit 12 d receives an inquiry about a user ID of a service used by another user terminal 20 from the user terminal 20 among the user terminals 20. Specifically, the receiving unit 12d receives an inquiry about the user ID of the service used by the other user terminal 20 from the user terminal 20, and at least one of the one or more used by the other user terminal 20. The service type and user ID are received. For example, when the user X who is the calling side makes an inquiry about the user Y who is the receiving side, the receiving unit 12d receives the user ID of the service A used by the user Y known by the user X.

  When the inquiry is received by the reception unit 12d, the acquisition unit 12e acquires, from the user ID storage unit 13a, the service type and the user ID corresponding to the user terminal 20 as the inquiry destination in the user ID storage unit 13a. For example, when the receiving unit 12d receives the user ID of the service used by the user Y ascertained by the user X by the receiving unit 12d, the acquiring unit 12e The presence status of those IDs is acquired at once. In addition, the acquisition unit 12e acquires from the user ID storage unit 13a a service type and user ID belonging to the same group as the set of service type and user ID received by the reception unit 12d.

  The transmission unit 12f transmits the service type and user ID acquired by the acquisition unit 12e to the user terminal 20 that made the inquiry. Specifically, the transmission unit 12f sends the inquiry about the service type and user ID acquired by the acquisition unit 12e, as well as information on the presence status of other user terminals for the service of the service type and user ID. Send to.

  Here, the user ID inquiry process will be described with reference to FIG. FIG. 10 is a diagram illustrating an example of a user ID inquiry process. As illustrated in FIG. 10, the inquiry server 10 divides “mobile phone number”, “mobile mail address”, and “service B ID” into “groups for business persons” as the user ID of the user Z. “Service A ID”, “Service C ID”, and “Service D ID” are divided into “groups for friends in school days” and stored.

  In the example of FIG. 10, the user ID that the user X knows about the user Z is only the user ID of the service A, and the user ID that the user Y knows about the user Z is the mobile phone number, the mobile mail address, and the service. It is assumed that the user ID is C.

  In such a case, when the inquiry server 10 receives the user ID of the service A from the user terminal 20A of the user X, the “service A” belonging to the same group “group for friends in school days” as the user ID of the service A Together with “ID of service”, “ID of service C”, and “ID of service D”, the presence status for each service is returned to user terminal 20A.

  Further, when the inquiry server 10 receives the mobile phone number, the mobile mail address, and the user ID of the service C from the user terminal 20B of the user Y, the “inquiry group” and the “group for friends in school days” The presence status for each service is returned to the user terminal 20B together with the mobile phone numbers and mobile mail addresses belonging to both groups and the user IDs of services A to D.

  As described above, the user transmits one or more “user IDs of some service” to the inquiry server 10 within the range of grasping the “user ID of some service”, and in response, the user IDs of the services belonging to the same group and their presence states are transmitted. get.

  When the service used by the user terminal 20 is different from the service used by the other user terminal 20, the connection unit 12g mutually converts communication information transmitted and received by both services, and the user terminal 20 and the other user terminal Relay communication with 20.

  Here, an interconnection process between different services will be described using the example of FIG. FIG. 11 is a diagram illustrating an example of an interconnection process between different services. In the example of FIG. 11, it is assumed that the user X uses the service B and the user Y uses the service A.

  Then, when it is determined that the user Y who wants to communicate is in a state where only the service A is available, the user X requests from the user terminal 20A that he / she wants to connect to the user Y who uses the service A using the service B. It transmits to the inquiry server 10. As a result, the inquiry server 10 uses the service B to connect to the user terminal 20A that is the connection request source, and uses the service A to connect to the user terminal 20B that is the connection request destination. If the media are different, the inquiry server 10 converts the media in real time and relays communication between the user terminal 20A and the user terminal 20B.

  In other words, the inquiry server 10 is intended to realize voice calls, video / audio communication, messaging, etc. between users using different applications, and when the ID is returned, the inquiry server 10 can use the inquiry user. If there is a difference between “Non-Service” and “Service Available to Inquiry User”, it is possible to select whether or not to perform interconnection.

  Then, when the user wishes to connect to each other, for example, in the case of a voice telephone, the voice telephone that can be used by each of the inquiry source user terminal 20A and the inquiry destination user terminal 20B in response to a call from the inquiry server 10 When a call is made to the service and the two respond, the call is relayed. When mutual service implementation methods (codec / clock synchronization, etc.) are different, mutual conversion (media conversion) is performed. Here, the term “interconnect” also applies to those with different media types, and the voice call service user and the messaging service user send the voice call service voice as a media file and send it as an attachment to the messaging service. Including such interconnections.

[Processing by inquiry system]
Next, processing by the inquiry server 10 according to the first embodiment will be described with reference to FIGS. 12 and 13. FIG. 12 is a sequence diagram showing a flow of inquiry processing by the inquiry system according to the first embodiment. FIG. 13 is a sequence diagram showing a flow of interconnection processing by the inquiry system according to the first embodiment. In the example of FIGS. 12 and 13, the user X's transmission side terminal is described as the user terminal 20A, and the user Y's reception side terminal is described as the user terminal 20B.

  As shown in FIG. 12, the inquiry server 10 logs in to the service A server 30A and the service B server 30B in advance (step S101). In the example of FIG. 12, a case is described in which the service A server 30 </ b> A and the service B server 30 </ b> B are previously logged in, but it is assumed that the other service server 30 is also logged in.

  Then, the user terminal 20A logs in to the service A server 30A and the user terminal 20B logs in the service B server 30B as the user terminal 20B of the user Y (step S102). Then, the user terminal 20B transmits a presence request for confirming the presence state of the user Y to the inquiry server 10 (step S103). Here, it is assumed that the presence status for all services is confirmed.

  As a result, the inquiry server 10 transmits a presence request to the service B server 30B in order to confirm the presence status of the user Y (step S104), and receives a presence response from the service B server 30B (step S105). Here, in the presence response, the presence status of the service B for the user Y is “online”, and for example, the available media are “text”, “voice”, and “video” as information. ing. As media that can be used here, for example, text messaging (“text”), voice call (“voice”), and videophone (“video”) can be used in communication tools such as LINE and Skype. ing. Note that this usable media differs depending on the service, terminal, setting, etc. used by the user.

  Then, the inquiry server 10 returns a presence response to the user terminal 20A (step S106). Here, the presence response includes information about the presence status of the service B for the user Y being “online” and the available media being “text”, “voice”, and “video”. .

  Here, when the user X of the user terminal 20A uses the service B, the user X can communicate with the user Y using the service B. On the other hand, when the user X is not using the service B, the interrogation is requested to the inquiry server 10. Here, the processing when the interconnection is requested will be described with reference to FIG.

  As illustrated in FIG. 13, the user terminal 20 </ b> A that is the transmission side of the user X transmits a connection request to the inquiry server 10 (step S <b> 201). When making this connection request, the inquiry server 10 is notified that the service used by itself is A, the service used by the other party is B, the other user is Y, and the medium used is voice. .

  Then, the inquiry server 10 requests user information from the service A server 30A (step S202), and receives the user information as a response (step S203). Specifically, the inquiry server 10 requests the user information as a connection source user's A account for which the connection source user is an account of the own device, the connection destination user is X, and receives the IP address of the connection destination terminal as a response. To do.

  Subsequently, the inquiry server 10 requests user information from the service B server 30B (step S204), and receives the user information as a response (step S205). Specifically, the inquiry server 10 requests user information as the connection source user's B interconnection account that is the account of the own device, the connection destination user is Y, and receives the IP address of the connection destination terminal as a response. To do.

  Then, the inquiry server 10 makes a voice communication utterance to the user terminal 20A by using the A interconnection account for which the connection source user is an account of the own device, the connection destination user is X, and the medium is voice (step S206). A voice communication utterance is made to the user terminal 20B, with the former user being the B interconnection account that is the account of the own device, the destination user being Y, and the media being voice (step S207). Thereafter, the inquiry server 10 relays a voice call response while performing mutual conversion (step S208).

[Effect of the first embodiment]
As described above, the inquiry server 10 according to the first embodiment stores, for each user, the service type of the service used by the user and the contact information for using the service in association with each other. Store in the unit 13. And the inquiry server 10 receives the inquiry of the contact information of the service used by the second user terminal other than the first user terminal from the first user terminal among the user terminals, and when the inquiry is received. The service type and contact information corresponding to the second user terminal are acquired from the storage unit 13. Then, the inquiry server 10 transmits the acquired service type and contact information to the first user terminal. For this reason, since the service type and contact information used by the users who want to communicate can be acquired, it is possible to reduce the time required for communication between users and promote communication between users.

  The inquiry server 10 registers the service type and contact information in the storage unit 13 when a request for registration of the service type and contact information of the service used by the user of the user terminal is received from the user terminal. To do. For this reason, the user can register only an arbitrary service in the inquiry server 10.

  Further, when a registration request is accepted, the inquiry server 10 requests authentication information for confirming whether the user of the user terminal is the registrant himself / herself from the user terminal that made the registration request. For this reason, it is possible to confirm whether or not the user is a valid owner of a telephone number or an e-mail address, and it is possible to unify authentication and reduce the burden on both the user service provider.

  In addition, the inquiry server 10 accepts a registration request from the user terminal and accepts the setting of contact information that permits transmission to other user terminals out of the contact information that has accepted the registration request. For this reason, since the inquiry server 10 can disclose information only to the other party that the user wants to disclose at the user's discretion, privacy can be protected.

  In addition, the inquiry server 10 receives a registration request from the user terminal, and accepts a setting for dividing a set of a plurality of service types and contact information that have received the registration request into a predetermined group. Then, the service type and contact information of the service used by the second user terminal are received from the first user terminal, and the service type and contact information used by the second user terminal are received. . Then, the inquiry server 10 acquires from the storage unit 13 the service type and contact information belonging to the same group as the set of the received service type and contact information. For this reason, for example, the user manages the user ID for each group in consideration of the range that “if the user knows this user ID, the user ID of other services may be known”. It becomes possible.

  Further, the inquiry server 10 collects the connection status of each service of the user terminal from the server that provides the service, and stores the connection status in the storage unit 13. And the information regarding the connection state of the 2nd user terminal with respect to the service of a service classification and contact information is transmitted to a 1st user terminal with the acquired service classification and contact information. For this reason, the user can grasp the service availability status of other users.

  In the inquiry server 10, the user can make and receive calls after grasping the service availability status of other users by a query to the inquiry server 10 without starting each service application. In addition, battery consumption due to constant activation of applications is regarded as a problem in mobile devices, and this can be reduced.

[System configuration, etc.]
Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the registration unit 12a and the authentication unit 12b may be integrated. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  Also, among the processes described in the present embodiment, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

[program]
It is also possible to create a program in which the processing executed by the inquiry server 10 described in the above embodiment is described in a language that can be executed by a computer. For example, it is possible to create an inquiry program in which processing executed by the inquiry server 10 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the inquiry program, the same effect as in the above embodiment can be obtained. Further, the inquiry program may be recorded on a computer-readable recording medium, and the inquiry processing program recorded on the recording medium may be read by the computer and executed to realize the same processing as in the first embodiment. Good. An example of a computer that executes an inquiry program that realizes the same function as the inquiry server 10 shown in FIG. 2 will be described below.

  FIG. 14 is a diagram illustrating a computer 1000 that executes an inquiry program. As illustrated in FIG. 14, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to, for example, a mouse 1051 and a keyboard 1052 as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 14, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the inquiry program is stored in, for example, the hard disk drive 1031 as a program module in which a command executed by the computer 1000 is described.

  The various data described in the above embodiment is stored as program data, for example, in the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1031 to the RAM 1012 as necessary, and executes various processing procedures.

  Note that the program module 1093 and the program data 1094 related to the inquiry program are not limited to being stored in the hard disk drive 1031, but may be stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. Good. Alternatively, the program module 1093 and the program data 1094 related to the inquiry program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and via the network interface 1070. May be read by the CPU 1020.

DESCRIPTION OF SYMBOLS 10 Inquiry server 11 Communication processing part 12 Control part 12a Registration part 12b Authentication part 12c Collection part 12d Reception part 12e Acquisition part 12f Transmission part 12g Connection part 13 Storage part 13a User ID memory | storage part 20A, 20B User terminal 30A Service A server 30B Service B server 100 inquiry system

Claims (6)

An inquiry system having each user terminal used by each user and an inquiry server connected to each user terminal so as to communicate with each other,
The inquiry server is
A storage unit that stores, for each user, the service type of the service used by the user and the contact information for using the service in association with each other;
A connection state indicating whether or not the application for using each communication service of each user terminal is activated and logged in is collected from a server providing the service, and the connection state is stored in the storage unit. A collecting unit for storing;
Of Kiyu over The terminal front, and from the first user terminal, receiving unit second user terminal other than the first user terminal receives the inquiry about the contact information of the services that are available,
When the inquiry is received by the receiving unit, the storage unit acquires the service type and the contact information corresponding to the second user terminal from the storage unit;
A transmission unit that transmits information about a connection state of the second user terminal to the service of the service type and the contact information, together with the service type and contact information acquired by the acquisition unit, to the first user terminal;
When the service used by the first user terminal is different from the service used by the second user terminal, communication information that is text data, audio data, or video data transmitted and received by both services is mutually converted. A connection unit that relays communication between the first user terminal and the second user terminal;
An inquiry system comprising: The inquiry server is
A registration unit for registering the service type and the contact information in the storage unit when a registration request for the service type and contact information of the service used by the user of the user terminal is received from the user terminal; The inquiry system according to claim 1, further comprising: The inquiry server is
When a registration request is received by the registration unit, the authentication unit further includes an authentication unit that requests authentication information for confirming whether or not the user of the user terminal is the registrant of the user terminal that has made the registration request The inquiry system according to claim 2.   The registration unit receives the registration request from the user terminal, and accepts a setting of contact information that permits transmission to another user terminal among contact information that has received the registration request. Item 4. The inquiry system according to item 2 or 3. The registration unit accepts the registration request from the user terminal and accepts a setting for dividing a set of a plurality of service types and contact information that has accepted the registration request into a predetermined group,
The receiving unit receives, from the first user terminal, a service type of a service used by the second user terminal and an inquiry about contact information, and a service type used by the second user terminal and Receive contact information,
5. The acquisition unit according to claim 2, wherein the acquisition unit acquires, from the storage unit, a service type and contact information belonging to the same group as the set of service type and contact information received by the reception unit. The inquiry system according to any one of the above. An inquiry method executed by an inquiry server that is communicably connected to each user terminal used by each user ,
The inquiry server includes , for each user, a storage unit that stores a service type of a service used by the user and contact information when using the service in association with each other,
A connection state indicating whether or not the inquiry server is in a state in which an application for using each communication service of each user terminal is started and logged in is collected from the server providing the service, and the connection state Collecting in the storage unit;
The query server, among Kiyu over The terminal front, from a first user terminal, a receiving step of receiving an inquiry of contact information of the service by the second user terminal other than the first user terminal is using,
When the inquiry server receives an inquiry in the receiving step, the storage unit acquires the service type and the contact information corresponding to the second user terminal from the storage unit;
The inquiry server transmits, to the first user terminal, information related to the connection status of the second user terminal for the service type and the contact information service, together with the service type and contact information acquired in the acquisition step. Sending process;
When the service used by the first user terminal is different from the service used by the second user terminal, the inquiry server is text data, voice data, or video data transmitted / received by both services. A connection step of mutually converting information and relaying communication between the first user terminal and the second user terminal;
Inquiry method characterized by including.

Images