JP5651075B2 - Profile server, management system, and profile information management method - Google Patents

Description

  The present invention relates to a profile server, a management system, and a profile information management method that manage profile information of a plurality of users in association with each other.

  Phone book data including names / names, phone numbers or email addresses for multiple mobile phone users is collected through a communication network, and the relationship between users is managed as a social line using the accumulated phone book data. A telephone directory management system has been proposed (see, for example, Patent Document 1). In this telephone directory management system, for example, by tracing a social line set in the telephone directory data, profiles of other users associated with the social line can be searched.

JP 2010-4229 A

  By the way, the latest profile acquisition service which acquires the newest profile information of an other party user on the assumption that the connection relation between users is built by collating profile information and telephone directory data, and this built connection relation can be considered. However, when trying to obtain the latest profile information of all the other users registered in the phone book data of the user terminal, there is a possibility that the phone book data of the user terminal is updated and the relationship construction is performed asynchronously. In such a situation, there is a possibility that the requesting user may wait for a long time before acquiring the latest profile of the other user.

  The present invention has been made in view of such problems, and a profile server, a profile information management system, and a profile information management system capable of responding quickly without causing the requesting user to wait for an acquisition request for the latest profile from the user terminal, And it aims at providing the profile information management method.

  The profile server of the present invention includes an acquisition request receiving unit that receives an acquisition request related to the latest profile information of a partner user registered in the user terminal from the user terminal of the request source user, and the request source user between the acquisition request and the request source user. In the case where a partner user whose connection relationship is not established is included, a determination unit that determines whether or not a time required for a response to the acquisition request exceeds a predetermined time, and the determination unit before the response transmission If it is determined that the time required exceeds a predetermined time, a response transmission unit that transmits the latest profile information of the partner user excluding the partner user for whom the connection relationship is not established to the user terminal of the requesting user, and the acquisition request The latest profile information about the other user for whom the connection relationship included in Characterized by comprising a notification unit that notifies the user terminal of the requesting user, information indicating that.

  According to this configuration, even if a partner user for whom a connection relationship has not been established is included in the acquisition request, it is determined whether or not the time required for a response to the acquisition request exceeds a predetermined time, and the response transmission is required. When it is determined that the time exceeds the predetermined time, the latest profile information of the partner user excluding the partner user for whom the connection relationship is not established is transmitted to the user terminal of the requesting user without waiting for the requesting user. The first updated profile response can be completed.

  According to the present invention, it is possible to provide a profile server, a management system, and a profile information management method capable of quickly responding without causing the requesting user to wait for the latest profile acquisition request from the user terminal.

It is a schematic block diagram of the system containing the social telephone directory management system which concerns on this Embodiment. It is a figure shown about the specific example of the profile data registered into a profile database. It is a figure shown about the specific example of a telephone directory database. It is a figure shown about the specific example of a connection relation database. It is a figure which shows the function structure of the profile server in this Embodiment. It is a figure which shows the state of the telephone directory data of a user terminal, and a telephone directory database. It is a sequence diagram explaining operation | movement of a management system. It is a flowchart explaining operation | movement of the social telephone directory management system at the time of acquisition of the newest profile information.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a network configuration diagram including a social telephone directory management system according to the present embodiment. The social telephone directory management system 1 manages connection relationship information indicating a relationship (connection relationship) between users. A plurality of social network service (SNS) providing servers (hereinafter simply referred to as SNS servers) 3a to 3c are connected to the social telephone directory management system 1 via the Internet 2, and a core network 4 operated by a communication carrier and User terminals 6 a to 6 d are connected via the radio base station 5.

  The social telephone directory management system 1 is a profile server 11 that manages connection relation information between users and provides the latest profile information, and a profile in which profile information of each user that is uploaded from each of the user terminals 6a to 6d is registered. A database (profile DB) 12, a phone book database (phone book DB) 13 in which phone book data uploaded from each of the user terminals 6a to 6d is registered, and a connection relationship database (in which connection relationship information between users is registered) Connection relation DB) 14. In response to requests from the user terminals 6a to 6d, the profile server 11 registers the profile information of each user uploaded from the user terminals 6a to 6d in the profile DB 12, and the phone book data uploaded from the user terminals 6a to 6d. Is registered in the telephone directory DB 13. In the user terminals 6a to 6d, the phone book data of each user is stored, and information such as the telephone number and mail address of the other user is updated (added, changed, deleted) by an application launched on the user terminal appropriately ) Further, the profile server 11 generates connection relationship information from the profile information and the phone book data and registers it in the connection relationship DB 14.

  When there is an acquisition request regarding the latest profile information of the other user from the user terminals 6a to 6d (hereinafter referred to as the latest profile request), the social telephone directory management system 1 sends the latest profile information of the other user to the user terminals 6a to 6d. Is configured to send. Specifically, the social telephone directory management system 1 refers to the connection relationship DB 14 to establish a connection relationship between the requesting user who issued the latest profile request and the other user included in the latest profile request. The latest profile information of the other user is acquired and transmitted to the requesting user terminals 6a to 6d on the condition that the request is made.

  The user terminals 6 a to 6 d are terminal devices capable of wireless communication such as mobile phones, and are configured to upload profile information and phone book data to the social phone book management system 1. Moreover, this Embodiment makes all the other users registered into the telephone directory data preserve | saved at user terminal 6a-6d the acquisition object of the newest profile information. Therefore, the user terminals 6a to 6d transmit the phone book data stored in the own terminal to the social phone book management system 1, thereby requesting the latest profile request regarding the other user registered in the phone book data of the own terminal. I do. The user terminals 6a to 6d have functions such as voice call, e-mail, and SMS (Short Message Service), and can communicate with other user terminals 6a to 6d by these functions. ing. In addition, in this Embodiment, although the terminal device which can communicate wirelessly is illustrated as user terminal 6a-6d, user terminal 6a-6d is a terminal device which communicates with the social telephone directory management system 1 etc. by wire. There may be.

  The social telephone directory management system 1 and the user terminals 6a to 6d have hardware including a communication interface, a processor, a memory, a transmission / reception circuit, a display, operation keys, a touch panel, and the like, and the memory is executed by the processor. A software module is stored. A functional configuration to be described later may be realized by the hardware described above, may be realized by a software module executed by a processor, or may be realized by a combination of both.

  The profile information described above includes the telephone numbers and mail addresses of the user terminals 6a to 6d, the name and address of the user who is the user of the user terminals 6a to 6d, and the identification information of the SNS in which the user participates (users in the SNS servers 3a to 3c) ID, e-mail address used in SNS, etc.) can be configured. The profile information may include identification information of external services other than the social network service.

  When the profile server 11 registers the profile information of each of the user terminals 6a to 6d in the profile DB 12 in response to requests from the user terminals 6a to 6d, the social phone provided by the social phone book management system 1 is included in each profile information A user identification number (hereinafter referred to as SABID) uniquely assigned on the book service is assigned. Thereby, in profile DB12, the some information which comprises profile information is mutually linked | related by SABID, and is managed for every user (every user terminal).

  FIG. 2 is a diagram showing a specific example of profile data registered in the profile DB 12. In FIG. 2, the part regarding the main profile information of the four users (user AD) corresponding to the user terminals 6a-6d shown in FIG. 1 is shown. However, the specific configuration of the profile DB 12 is not limited to that shown in FIG. Profile DB12 should just be comprised so that the profile information of the several user who participates in a social telephone directory service may be registered. In the profile DB 12, the names of the four users A to D, the telephone numbers paid to the user terminals 6a to 6d with which the users are contracted, and the mail addresses are registered as key information in association with the SABID. For example, the profile information of the user A who uses the user terminal 6a is centrally managed by the SABID “1001”. In the present embodiment, the SABID is expressed by a 4-digit number string, but the configuration of the SABID is not particularly limited. It suffices if a SABID that can identify all users (all user terminals) participating in the social telephone directory service can be given.

  Phonebook data is stored in each of the user terminals 6a to 6d. In the phone book data, user information such as the name, phone number, and mail address of the other user registered by the user is stored in association with a registration number (CID) assigned to each user. In the present embodiment, the CID that specifies the user information on the user terminal is represented by a 4-digit number string, but the configuration of the CID is not particularly limited.

  The acquisition request for the latest profile received by the profile server 11 from the user terminals 6a to 6d includes the CID associated with the user information in the phone book data stored in the user terminals 6a to 6d.

  FIG. 3 is a diagram illustrating a specific example of the telephone directory DB 13. In the phone book DB 13, each phone book data uploaded from the user terminals 6a to 6d is registered. The phone book data of a plurality of users stored in the phone book DB 13 is managed by SABID. For example, the phone book data to which the SABID “1001” is assigned (the portion surrounded by a thick line in FIG. 3) corresponds to the phone book data stored and uploaded in the user terminal 6a used by the user A.

  The phone book data stored in the phone book DB 13 is given the CID registered in the phone book data when the phone book data is uploaded. For example, in the phone book data managed by SABID “1001”, CID “0001” is assigned to the user information related to user C, and CID “0002” is assigned to the user information related to user B.

  Since the CID is a number uniquely assigned to each of the user terminals 6a to 6d, if the SABID is different, the associated information is different even if the CID is the same. For example, in the phone book data managed by the SABID “1001” (that is, the phone book data of the user terminal 6a), the user information related to the user C is associated with the CID “0001”, but the user information is managed with the SABID “2002”. In the phone book data (that is, the phone book data of the user terminal 6b), user information related to the user D is associated with the CID “0001”. For this reason, the user registered in the phone book data of the phone book DB 13 is specified by a set of SABID and CID.

  The connection relationship information is information indicating a connection relationship between users constructed by collating phone book data and profile data uploaded from each user. Therefore, the connection relationship information defines the connection relationship between users. Specifically, if the telephone number or mail address included in the user A's profile is registered as user information in the phone book data stored in the user terminal of another user B, a connection relationship is established. Thus, the connection relationship information is information that associates the SABID and CID set in the phone book DB 13 with the SABID in the profile DB 12. This connection relationship information indicates that the user specified by SABID and CID in the telephone directory DB 13 and the user specified by SABID in the profile DB 12 are the same person. This indicates that there is a connection relationship between the user using the phone book data specified by SABID in the phone book DB 13 and the user specified by SABID in the profile DB 12.

  FIG. 4 is a diagram illustrating a specific example of the connection relationship DB 14. In FIG. 4, the part regarding the connection relation information corresponding to the user terminals 6a to 6d shown in FIG. 1 is shown. However, the specific configuration of the connection relationship DB 14 is not limited to that shown in FIG. In the connection relationship DB 14, connection relationship information obtained by associating the SABID of the profile DB 12 with the set of SABID and CID in the telephone directory DB 13 is registered. For example, in the telephone directory DB 13, the user C is specified by SABID “1001” and CID “0001”. In the profile DB 12, the user C is specified by SABID “3003”. For this reason, the set of SABID “1001” and CID “0001” in the telephone directory DB 13 and the SABID “3003” in the profile DB 12 are associated with each other and registered in the connection relationship DB 14 (the portion surrounded by a thick line in FIG. 4). In this case, there is a connection relationship between the user A who uses the phone book data specified by the SABID “1001” in the phone book DB 13 and the user C specified by the SAB ID “3003” in the profile DB 12.

  FIG. 5 is a diagram mainly showing a functional configuration of the profile server 11. As illustrated in FIG. 5, the profile server 11 includes an acquisition request receiving unit 111 that receives the latest profile request transmitted from each of the user terminals 6 a to 6 d, and an update necessity that determines whether or not connection relationship information needs to be updated. The determination unit 112, the connection relationship information generation unit 113 that generates connection relationship information by matching processing between profile information and phone book data, and the latest profile information that acquires the latest profile information from the profile DB 12 with reference to the connection relationship DB 14 An acquisition unit 114, a notification unit 116 that notifies the user terminals 6a to 6d about profile acquisition, and a response that includes the latest profile information acquired by the latest profile information acquisition unit 114 for each user terminal 6a to 6d. And a response transmission unit 115 for transmission.

  The acquisition request receiving unit 111 receives the latest profile request from each of the user terminals 6a to 6d, and notifies the update necessity determining unit 112 of the CID of the user information registered in the phone book data included in the latest profile request. . In the latest profile request, each of the user terminals 6a to 6d does not need to include all information constituting the phone book data, and it is sufficient that at least the CID is included.

  The update necessity determination unit 112 determines whether or not the partner user corresponding to the CID notified from the acquisition request reception unit 111 is registered as the partner user whose connection relationship is established in the connection relationship DB 14. When the connection relationship between the requesting user and the partner user has already been established, it is determined that the connection relationship information need not be updated. On the other hand, when the connection relationship between the requesting user and the partner user is not established, it is determined that the connection relationship information with the partner user needs to be updated.

  For example, when there is a latest profile request from the user terminal 6a, the update necessity determination unit 112 searches the connection relation DB 14 for a term of SABID “1001” indicating that the phone book data of the user terminal 6a. When the CID notified from the user terminal 6a exists in the section of SABID “1001” and the SUBID associated with the CID exists, it is determined that the connection relationship has already been established and the connection relationship information does not need to be updated. To do. In other cases, it is determined that the connection relationship information needs to be updated.

  In addition, when it is determined that the connection relationship information needs to be updated, the update necessity determination unit 112 determines whether the connection relationship information needs to be updated for a predetermined time or longer, and performs subsequent processing according to the determination result. It is configured to be selectable. For example, when it is determined that a predetermined time or more is required for updating the connection relationship information, the update necessity determination unit 112 updates the latest profile information acquisition unit 114 so as to acquire the latest profile information of the user whose connection relationship has already been established. The response transmission unit 115 is instructed to send back the latest profile information as a response. In addition, the notification unit 116 is instructed to notify the user terminals 6a to 6d of the requesting user that the latest profile information regarding some users has not been acquired.

  The connection relationship information generation unit 113 constructs a new connection relationship between the requesting user and the other user and determines the existing connection relationship information when the update necessity determination unit 112 determines that the connection relationship information needs to be updated. It is configured to be updatable. For example, when there is a latest profile request from the user terminal 6a as described above, if the CID notified from the user terminal 6a does not exist in the section of the SABID “1001” in the connection relationship DB 14, that is, the user A and the other user If the connection relationship is not established, the key information (telephone number, e-mail address, etc.) associated with the CID is searched for in the profile DB 12. When the same key information exists in the profile DB 12, a connection relationship is established between the user A and the other user. That is, the connection relationship information generation unit 113 builds a new connection relationship by associating the SABID and CID pair corresponding to the key information in the telephone directory DB 13 and the SABID corresponding to the key information in the profile DB 12, and Update. The updated connection relationship information is recorded in the connection relationship DB 14.

  The latest profile information acquisition unit 114 is configured to acquire the latest profile information from the profile DB 12 with reference to the connection relationship DB 14 based on an instruction from the update necessity determination unit 112. The latest profile information acquired by the latest profile information acquisition unit 114 is sent to the response transmission unit 115. The response transmission unit 115 is configured to be able to distribute the latest profile information sent from the latest profile information acquisition unit 114 to the user terminals 6a to 6d.

  The notification unit 116 is configured to be able to make a predetermined notification to the user terminals 6a to 6d of the request source user according to the process selected by the update necessity determination unit 112. For example, when it is determined that a predetermined time or more is required for updating the connection relationship information, information indicating that the latest profile information regarding some users cannot be acquired is notified to the user terminals 6a to 6d of the requesting user. To do.

  In addition, the communication system mentioned above enables information management of various aspects using the connection relation information between users by centrally managing information regarding users who subscribe to the social telephone directory service. For example, since the social telephone directory management system 1 manages the identification information and the like of each user in the SNS servers 3a to 3c, each user can access information published on the SNS. If this is utilized, it will become possible for the user himself / herself to acquire information disclosed by other users on the SNS without accessing the SNS servers 3a to 3c. Specifically, for example, the social telephone directory management system 1 periodically acquires information disclosed by a certain user on the SNS, and permits another user connected to the user to access the information. What is necessary is just to make it a proper structure.

  Next, operations of the communication system according to the present embodiment will be described with reference to FIGS. In the following, the case where the user terminal 6a shown in FIG. 1 requests acquisition of the latest profile information will be described in particular, but the same applies to the case where another user terminal requests acquisition of the latest profile information.

  FIG. 6 is a diagram showing the state of the phone book data and the phone book DB 13 of the user terminal 6a. As shown in FIG. 6A, information related to the user D for whom the connection relationship with the user A is not established in the connection relationship DB 14 is added to the phone book data of the user terminal 6a. That is, in FIG. 6A, the CID “0003” relating to the user D is added to the phone book data of the user terminal 6a, but the connection relation DB 14 includes the item “SABID“ 1001 ”corresponding to the phone book data of the user terminal 6a. No CID “0003” is registered (the portion surrounded by a thick line in FIG. 6A).

  FIG. 7 is a sequence diagram for explaining the operation of the communication system in the case shown in FIG. 6A. As shown in FIG. 7, the user terminal 6a transmits the phone book data corresponding to the users B, C, and D to the profile server 11 to request the latest profile information of the users B, C, and D (step S101). . Then, the acquisition request reception unit 111 of the profile server 11 notifies the update necessity determination unit 112 of the CID of the phone book data corresponding to the users B, C, and D.

  When receiving the CID from the acquisition request receiving unit 111, the update necessity determining unit 112 determines whether the connection relationship information needs to be updated based on the CID (step S102). Specifically, the SABID “1001” item indicating the phonebook data of the user terminal 6a is searched in the connection relation DB 14, and the registration status of the CID notified from the user terminal 6a is confirmed. Here, as shown in FIG. 6A, the CID “0003” related to the user D is not registered in the SABID “1001” section of the connection relationship DB 14. For this reason, the necessity determination part 112 for an update determines with the connection relationship regarding the user D not being constructed | assembled, but the update of connection relationship information being required.

  When the update necessity determination unit 112 determines that the connection relationship information needs to be updated, the update necessity determination unit 112 determines whether or not the connection relationship information update process is completed within a predetermined time (step). S103). The update process of the connection relationship information is performed by comparing the key information associated with the CID indicating the user whose connection relationship is not established with the profile information registered in the profile DB 12. For this reason, the time required for the update process of the connection relationship information depends on the amount of search processing determined by the number of key information related to the user for which the connection relationship is not established, the number of profile information registered in the profile DB 12, and the like. Here, the number of key information necessary for specifying the user D that is not registered in the connection relation DB 14 is 2 (the telephone number (1) of the user D and the mail address (1)) and needs to be searched. The number of profile information is 4 (total of profile information of users A to D). When the search processing amount is large and the processing takes a predetermined time or more, it is determined that the connection relationship information update processing does not end within the predetermined time. When the search processing amount is small and the processing does not take a predetermined time or more, it is determined that the connection relationship information update processing is completed within the predetermined time. In this way, the time required for the update process can be appropriately determined based on the number of key information associated with the CID, the amount of search processing determined by the number of profile information registered in the profile DB 12, and the like.

  When the update necessity determination unit 112 determines that the connection relationship information update process does not end within a predetermined time, the update necessity determination unit 112 has already established a connection relationship with the latest profile information acquisition unit 114. Instruct users to get the latest profile information about the user. That is, the update necessity determination unit 112 instructs to acquire the latest profile information of the users B and C except for the user D. Further, the update necessity determination unit 112 instructs the response transmission unit 115 to transmit a response including the latest profile information of the users B and C to the user terminal 6a, and notifies the notification unit 116 of the determination result regarding the processing time. Tell them.

  When the latest profile information acquisition unit 114 receives an instruction from the update necessity determination unit 112, the latest profile information acquisition unit 114 refers to the connection relationship DB 14 and the profile DB 12, and includes the latest profile information regarding users (users B and C) that have already established a connection relationship. To get. Specifically, the SABID “2002” associated with the CID “0002” representing the user B is acquired in the SABID “1001” item of the connection relation DB 14, and the SABID “2002” item of the profile DB 12 is referred to. The latest profile information of user B is acquired. In addition, the SABID “3003” associated with the CID “0001” representing the user C is acquired in the SABID “1001” section of the connection relationship DB 14, and the user C is referred to by referring to the SABID “3003” section of the profile DB 12. Get the latest profile information for. When the latest profile information of the users B and C is acquired, the latest profile information acquisition unit 114 sends these information to the notification unit 116.

  When the response transmission unit 115 receives the latest profile information regarding the users (users B and C) whose connection relationship is established from the latest profile information acquisition unit 114, the response transmission unit 115 transmits a response including this to the user terminal 6a (step S104). . In addition, the notification unit 116 notifies the user terminal 6a that the latest profile information about the user (user D) whose connection relationship is not established has not been acquired (step S105). The notification is performed using SMS or the like. As described above, the latest profile information of the users (users B and C) who have already established the connection relationship is distributed first before the acquisition of the latest profile information of the user (user D) who has not established the connection relationship. This is because the response to the user terminal 6a is significantly delayed and the convenience of the communication system is reduced when the connection relationship information update process performed in (1) is not completed within a predetermined time. In the social telephone directory management system 1 according to the present embodiment, a response in such a case is appropriately made. Therefore, it is possible to suppress the delay of the response to the user terminal 6a and improve the convenience of the communication system. In FIG. 7, step 104 is performed after step S103, but these steps may be performed simultaneously.

  Before and after Steps S104 and S105 described above, the update necessity determination unit 112 instructs the connection relationship information generation unit 113 to update the connection relationship information. Upon receiving this instruction, the connection relationship information generation unit 113 performs a connection relationship information update process (step S106). That is, the key information regarding the user (user D) for whom the connection relationship is not established is compared with the profile information registered in the profile DB 12 to construct a new connection relationship. Specifically, a matching process between the key information (phone number or mail address) of the user D and the key information registered in the profile DB 12 is performed. When the key information matches, the connection relationship information generation unit 113 associates the CID with the SABID of the profile DB 12. Here, since the telephone number and the mail address which are the key information of the user D exist in the profile DB 12, as shown in FIG. 6B, the SABID of the profile DB 12 corresponds to the CID “0003” in the section of the SABID “1001”. The connection relation information is updated by associating “5001”. The updated connection relationship information is recorded in the connection relationship DB 14.

  When the connection relationship information generation unit 113 completes the update of the connection relationship information, the connection relationship information generation unit 113 notifies the notification unit 116 to that effect. Then, the notification unit 116 notifies the user terminal 6a that the preparation for acquiring the latest profile information of the user (user D) whose connection relationship has not been established has been completed (step S107). The notification is performed using SMS or the like. When the user terminal 6a that has received the notification makes a latest profile request to the profile server 11 again (step S108), the profile server 11 performs the above-described steps on the user B, C, The latest profile information of D is distributed (step S109).

  FIG. 8 is a flowchart for explaining the operation of the social telephone directory management system 1 that has received the latest profile request. In the social phone book management system 1, when the profile server 11 receives the latest profile request including the latest phone book data stored in the user terminal 6a from the user terminal 6a, the update necessity determination unit 112 reads the phone book data. Is searched for whether or not there is a CID associated with the SABID of the requesting user of the user terminal 6a on the connection relation DB 14 (step S201).

  When all the CIDs (partner users) registered in the phone book data received from the user terminal 6a are connected to the requesting user of the user terminal 6a on the connection DB 14 (step S201: NO), The update necessity determination unit 112 determines that the construction of a new connection relationship (update of connection relationship information) is unnecessary, and instructs the latest profile information acquisition unit 114 to acquire the latest profile information. When the latest profile information acquisition unit 114 receiving the instruction acquires the latest profile information of the target partner user from the profile DB 12, the latest profile information is transferred to the response transmission unit 115, and the response transmission unit 115 receives the latest profile information. As a response to the user terminal 6a (step S202).

  On the other hand, the CID registered in the phone book data related to the latest profile request includes a CID (additional CID) that is not linked to the SABID of the requesting user of the user terminal 6a on the connection relationship DB 14. In the case (step S201: YES), the update necessity determination unit 112 attempts to establish a connection relationship with the counterpart user corresponding to the additional CID. That is, when trying to build a new connection relationship, it is determined that the connection relationship information needs to be updated. In this case, the update necessity determination unit 112 determines whether or not the time required for the connection relationship information update process is equal to or longer than a predetermined time (step S203). If the time required for the connection relationship information update process is less than the predetermined time (step S203: NO), the connection relationship information generation unit 113 performs a new relationship with the partner user corresponding to the additional CID as the connection relationship information update process. A connection relationship is constructed and reflected in the connection relationship DB 14. When the update process is completed, the latest profile information acquisition unit 114 acquires the latest profile information for all the other users registered in the phone book data related to the latest profile request (including the other users of the additional CID), and the response transmission unit 115 The latest profile information of all the partner users (including the partner users of the additional CID) is transmitted as a response to the user terminal 6a (step S204).

  On the other hand, when it is determined that the time required for the update process of the connection relationship information is equal to or longer than the predetermined time (step S203: YES), the update necessity determination unit 112 has already established a connection relationship with the latest profile information acquisition unit 114. And instructing the user to acquire the latest profile information of the user who does not need to update the connection information. A connection relationship has already been established with the partner user of the CID linked to the SABID of the requesting user of the user terminal 6a on the connection relationship DB. When the latest profile information acquisition unit 114 refers to the connection relationship DB 14 and the profile DB 12 and acquires the latest profile information of the other user corresponding to the CID (not including the additional CID) registered in the phone book data, the response transmission unit 116 Transmits the acquired latest profile information not including the partner user of the additional CID as a response to the user terminal 6a (step S205). At this time, the notification unit 116 notifies the user terminal 6a that the latest profile information of some partner users (additional CIDs) for which no connection relationship has been established has not been acquired (step S206). SMS can be used for notification that the latest profile information has not been acquired in step S206.

  In addition, the update necessity determination unit 112 newly establishes a connection relationship between the counterpart user corresponding to the additional CID and the user of the user terminal 6a that is the request source user, with respect to the connection relationship information generation unit 113. And instructing the connection relationship information on the connection relationship DB 14 to be updated. The connection relationship information generation unit 113 attempts to newly establish a connection relationship between the counterpart user corresponding to the additional CID and the user of the user terminal 6a. If the connection relationship is established, the connection relationship information between the partner user of the additional CID and the user of the user terminal 6a is additionally registered (update process) (step S207). When the update process of the connection relationship information is completed, the notification unit 116 notifies the user terminal 6a that the preparation for acquiring the latest profile information of all users is completed (step S208).

  As described above, according to the social telephone directory system 1 according to the present embodiment, the CID registered in the telephone directory data related to the latest profile request is linked to the SABID of the requesting user of the user terminal 6a on the connection relation DB 14. CID (additional CID) that is not attached is included, and when it is determined that the predetermined time is exceeded for returning the latest profiles of all the other users, the additional CID is registered among the CIDs registered in the phone book data. Since only the latest profile of the partner user of the excluded CID is returned, the first latest profile can be quickly returned to the requesting user.

  In addition, this invention is not limited to the said embodiment, A various change can be implemented. For example, only some of the other users registered in the phone book data stored in the user terminal may be acquired from the latest profile information. Moreover, the social telephone directory management system may be comprised with one profile server, and may be comprised with the some profile server. The social telephone directory management system may include a node for interface with the Internet or a core network. The number of SNS servers, wireless base stations, user terminals, etc. is not limited to the configuration of the above-described embodiment. In addition, the present invention can be implemented with appropriate modifications without departing from the scope of the present invention.

  The profile server, the profile information management system, and the profile information management method of the present invention can be applied to, for example, a communication system that can access by managing identification information of external services.

DESCRIPTION OF SYMBOLS 1 Social telephone directory management system 2 Internet 3a-3c SNS server 4 Core network 5 Wireless base station 6a-6d User terminal 11 Profile server 12 Profile DB
13 Phonebook DB
14 Connection DB
DESCRIPTION OF SYMBOLS 111 Acquisition request receiving part 112 Update necessity determination part 113 Connection relation information generation part 114 Latest profile information acquisition part 115 Response transmission part 116 Notification part

Claims (8)

An acquisition request receiving unit that receives an acquisition request regarding the latest profile information of the other user registered in the user terminal from the user terminal of the requesting user;
A determination unit that determines whether or not a time required for a response to the acquisition request exceeds a predetermined time when the acquisition request includes a partner user whose connection relationship with the request source user is not established When,
When it is determined by the determination unit that the time required for the response transmission exceeds a predetermined time, the latest profile information of the partner user excluding the partner user for whom the connection relationship is not established is transmitted to the user terminal of the requesting user A response transmitter to
A notification unit for notifying the requesting user's user terminal of information indicating that the latest profile information related to the other user for whom the connection relationship included in the acquisition request is not established;
A profile server characterized by comprising: A connection relationship information generating unit that generates connection relationship information between the requesting user and the other user for whom the connection relationship included in the acquisition request is not established;
The notification unit, when the generation of connection relationship information related to a partner user for which the connection relationship is not established in the connection relationship information generation unit, indicates that preparation for acquiring the latest profile information related to the partner user is completed The profile server according to claim 1, wherein:   Even if the partner user included in the acquisition request includes a partner user whose connection relationship is not established, the determination unit determines that the time required for the response transmission does not exceed a predetermined time. If the connection relationship information generation unit generates connection relationship information regarding the other user for whom the connection relationship is not established, the response transmission unit transmits a response including the latest profile information of all the other users. The profile server according to claim 2, characterized in that: The management number of the other user registered in the phone book data held in the user terminal of the request source user and the user registered in the phone book data, and a connection relationship with the request source user is established. A connection relationship storage unit that stores an identification number on the profile server of the other user in association with each other,
The determination unit is connected to the acquisition request with the request source user if the management number of the other user included in the acquisition request is not registered in the connection relationship storage unit in association with the request source user. The profile server according to claim 1 or 2, wherein it is determined that a partner user whose relationship is not established is included. A profile storage unit storing profile information of each user;
A phone book storage unit storing phone book data of each user in which the management number on the user terminal and the counterpart user information are associated;
The connection relationship information generation unit generates connection relationship information based on the correspondence between the user information registered in the phone book data of each user and the profile information of the counterpart user, and stores the connection relationship information in the connection relationship storage unit The profile server according to claim 4.   The determination unit has a predetermined time required for response transmission based on the number of key information included in the user information associated with the management number and the number of profile information registered in the profile storage unit. 6. The profile server according to claim 5, wherein it is determined whether or not time is exceeded. A management system comprising: a profile server; and a user terminal of a requesting user that transmits an acquisition request regarding the latest profile information of the other user to the profile server,
The profile server
An acquisition request receiving unit that receives an acquisition request regarding the latest profile information of the other user registered in the user terminal from the user terminal of the requesting user;
A determination unit that determines whether or not a time required for a response to the acquisition request exceeds a predetermined time when the acquisition request includes a partner user whose connection relationship with the request source user is not established When,
When it is determined by the determination unit that the time required for the response transmission exceeds a predetermined time, the latest profile information of the partner user excluding the partner user for whom the connection relationship is not established is transmitted to the user terminal of the requesting user A response transmitter to
A notification unit for notifying the user terminal of the requesting user of information indicating that the latest profile information regarding the other user for whom the connection relationship included in the acquisition request is not established has not been acquired. Management system featuring. Receiving an acquisition request regarding the latest profile information of the other user registered in the user terminal from the user terminal of the requesting user;
A step of determining whether or not a time required for a response to the acquisition request exceeds a predetermined time when the acquisition request includes a partner user whose connection relationship with the requesting user is not established; ,
If it is determined that the time required for the response transmission exceeds a predetermined time, transmitting the latest profile information of the partner user excluding the partner user for which the connection relationship is not established to the user terminal of the requesting user;
Notifying the requesting user's user terminal of information indicating that the latest profile information regarding the other user for whom the connection relationship included in the acquisition request is not established has not been acquired;
A profile information management method characterized by comprising:

Images