JP2009188825A - Destination management server, destination management system, and destination management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a destination control server, a destination control system and a destination control method, which can simply register the information on a communication partner. <P>SOLUTION: A phonebook control server 20a is equipped with a store information database 21 which stores one or a plurality of store informations, in which a destination information which shows the destination of communication partner and an attribute information which shows the attribution of the communication partner are matched, a receiver 221 which receives the phonebook information comprising one or a plurality of destination informations from a mobile phone 10a, a phonebook recesiation unit 222 which compares the received phonebook information with the store information memorized in the store information database 21 and which fills up the phonebook information employing the store information based on the result of the comparison and a transmitting unit 225 which transmits the filled-up phonebook information to the mobile phone 10a. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a destination management server, a destination management system, and a destination management method for managing destination information.

  Conventionally, a method for storing and managing destination information (for example, a telephone number and a mail address of a communication partner) stored in a communication terminal on the server side is also known. As a result, the destination information registered by the user can be backed up and restored. With regard to such a technique, Patent Document 1 below discloses an address book synchronization method for synchronizing address book data stored in a communication terminal such as a mobile phone with address book data stored on a server. . Specifically, the communication terminal detects the update of the address book data on its own terminal, collects the types of information constituting the address book data and the input contents, and uploads the updated address book data to the server To do.

When a user registers destination information, it is common to manage attribute information (for example, name, address, etc.) of a communication partner as well. This is because adding various attribute information to the destination information improves the usability of the destination information. For example, the address data storage / update system described in Patent Document 2 below recognizes characters such as business cards, and based on the recognized character information, such as a telephone number, an e-mail ID, a name, a company name, and a company address. Store information.
Japanese Patent Laid-Open No. 2005-130009 JP 2003-131991 A

  However, since it is usually necessary to manually register the attribute information of the communication partner, a certain load is imposed on the user. Although the method described in Patent Document 2 uses character recognition for data input processing, it is not convenient because it is necessary to prepare a device for character reading or the accuracy of character recognition is low.

  SUMMARY An advantage of some aspects of the invention is that it provides a destination management server, a destination management system, and a destination management method capable of easily registering information of a communication partner.

  The destination management server of the present invention includes a storage unit that stores one or a plurality of partner basic information in which destination information indicating a destination of a communication partner and attribute information indicating an attribute of the communication partner are associated, and one or a plurality of destinations The destination receiving means for receiving destination management information including information from the communication terminal, the destination management information received by the destination receiving means and the partner basic information stored in the storage means are compared, and based on the result of the comparison, Replenishment means for replenishing the destination management information using the partner basic information, and destination transmission means for transmitting the destination management information supplemented by the replenishment means to the communication terminal.

  The destination management system of the present invention is a destination management system comprising a communication terminal and a destination management server that can communicate with the communication terminal. The communication terminal includes one or a plurality of pieces of destination information indicating a destination of a communication partner. A destination-side destination transmission unit that transmits destination management information including the terminal-side destination reception unit that receives destination management information transmitted from the destination management server in response to transmission by the terminal-side destination transmission unit. A storage unit that stores one or more partner basic information in which destination information indicating the destination of the communication partner and attribute information indicating the attribute of the communication partner are associated with each other, and destination management transmitted by the terminal-side destination transmitting unit The server-side destination receiving means for receiving the information, the destination management information received by the server-side destination receiving means and the partner basic information stored in the storage means are compared, and based on the result of the comparison And replenishment means for replenishing the destination management information using the partner basic information, and server-side destination transmission means for transmitting the destination management information replenished by the replenishment means to the communication terminal. .

  According to such a destination management server and destination management system, the other party basic information in which the destination information and the attribute information are associated is compared with the destination management information received from the communication terminal, and based on the comparison result. The destination management information is supplemented using the other party basic information. Then, the replenished destination management information is transmitted to the communication terminal. This makes it possible to easily register information on the communication partner without causing the user of the communication terminal to register the attribute of the communication partner.

  The destination management method of the present invention can communicate with a database that stores one or more partner basic information in which destination information indicating a destination of a communication partner and attribute information indicating an attribute of the communication partner are associated with each other. A destination management method in a communication device that stores destination management information including a plurality of destination information, wherein the communication device compares the destination management information stored in the communication device with the partner basic information stored in the database. A replenishment step of replenishing the destination management information using the partner basic information based on the comparison result; and a storage step in which the communication device stores the destination management information replenished in the replenishment step. It is characterized by.

  According to such a destination management method, the destination management information is compared with the partner basic information in which the destination information and the attribute information are associated, and based on the comparison result, the destination management information is used. Information is supplemented. Then, the replenished destination management information is stored. This makes it possible to easily register information on the communication partner without having the user register the attribute of the communication partner.

  The destination management server of the present invention further includes history receiving means for receiving a communication history including the destination information from the communication terminal, and the supplementing means extracts and extracts the destination information included in the communication history received by the history receiving means. Preferably, the destination management information is supplemented using the other party basic information corresponding to the destination information.

  In this case, since the destination management information is supplemented using the other party basic information of the communication partner who has communicated in the past, it is limited to information of the communication partner that is highly likely to be contacted in the future, that is, information that is highly required to be registered. Can be replenished.

  In the destination management server of the present invention, the replenishing means calculates the number of communications for each destination information based on the communication history received by the history receiving means, and extracts destination information for which the computed number of communications is a predetermined value or more. The destination management information is preferably supplemented using the other party basic information corresponding to the extracted destination information.

  In this case, since the destination management information is supplemented by using the other party basic information of the communication partner that has communicated more than a predetermined number in the past, the information of the communication partner that is highly likely to be contacted in the future, that is, the necessity for registration is high. It becomes possible to supplement only information.

  In the destination management server of the present invention, the replenishment means extracts destination information that exists in the communication history and does not exist in the destination management information, and adds partner basic information corresponding to the extracted destination information to the destination management information. It is preferable that the destination management information is supplemented.

  In this case, even if the destination information of the communication partner that has communicated before is not registered in advance in the destination management information of the communication terminal, the basic information of the other party of the communication partner is added to the destination management information based on the communication history. Is done. Therefore, the user of the communication terminal can acquire the partner basic information of the partner without registering the destination information of the partner with whom the contact has been made in advance.

  In the destination management server of the present invention, the replenishment means extracts attribute information that exists in the partner basic information and does not exist in the destination management information for each destination information, and for each destination information, the extracted attribute information is the destination information. It is preferable to replenish the destination management information by associating with.

  In this case, since only attribute information that is not yet associated with destination information is added, it is possible to replenish attribute information without changing already registered attribute information.

  In the destination management server of the present invention, it is preferable that the replenishment means replenishes the destination management information using the partner basic information corresponding to the destination information of the fixed terminal.

  In this case, since the destination management information is supplemented using only the other party basic information corresponding to the fixed terminal such as the fixed telephone or the desktop computer, the information can be registered only for the information of the communication partner having the fixed terminal. It becomes possible.

  According to the destination management server, the destination management system, and the destination management method, the destination basic information including the attribute information is compared with the destination management information of the communication terminal, and the destination management information is supplemented using the destination basic information. Therefore, the information of the communication partner can be registered easily.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the description of the drawings, the same or equivalent elements are denoted by the same reference numerals, and redundant description is omitted.

(First embodiment)
First, the telephone directory management system 1a according to the first embodiment will be described with reference to FIGS. FIG. 1 is a diagram showing a configuration of the telephone directory management system 1a. FIG. 2 is a diagram illustrating an example of phone book information. FIG. 3 is a diagram illustrating an example of store information. FIG. 4 is a diagram illustrating an example of supplementation of telephone directory information.

  The telephone directory management system (destination management system) 1a includes a mobile phone (communication terminal) 10a and a telephone directory management server (destination management server) 20a. The mobile phone 10a and the telephone directory management server 20a can communicate with each other via a network (not shown). The phone book management server 20a can store a backup of phone book information in the mobile phone 10a, and the mobile phone 10a can use the phone book information stored in the phone book management server 20a to store the phone book information in its own terminal. Information can be restored. For simplicity, only one mobile phone 10a is shown in FIG. 1, but a plurality of mobile phones 10a may be provided.

  The mobile phone 10a is a mobile communication terminal having a call function, a mail transmission function, and the like. The cellular phone 10 a includes a telephone directory storage unit 101, a transmission unit (terminal-side destination transmission unit) 102, and a reception unit (terminal-side destination reception unit) 103 as functional components.

  The phone book storage unit 101 is means for storing phone book information (destination management information) that is a set of partner information indicating communication partners. The partner information includes at least destination information for identifying the communication partner, and can further include attribute information indicating an attribute of the communication partner. The destination information is information for specifying a communication partner at the time of communication, such as a telephone number or a mail address. The attribute information is information representing the characteristics of the communication partner, such as a name or address, and can be arbitrarily set depending on the type of the communication partner. For example, if the communication partner is an individual, the job title, birthday, etc. can be included in the attribute information, and if the communication partner is a company or store, business hours, regular holidays, URL (Uniform Resource Locator), etc. Can be included in the attribute information.

  An example of the phone book information stored in the phone book storage unit 101 is shown in FIG. The phone book information shown in FIG. 2 includes four pieces of partner information, and each partner information includes five types of information: name, phone number, mail address, address, and memo. Of these five types of information, the telephone number and the mail address are information that can be the destination information, and in the present embodiment, the telephone number is the destination information. Of course, a mail address may be used as the destination information, and both a telephone number and a mail address may be used as the destination information.

  The transmitting unit 102 is means for transmitting data to the telephone directory management server 20a. Specifically, the transmission unit 102 transmits the phone book information stored in the phone book storage unit 101 and synchronizes the phone book information in the own terminal with the phone book information in the phone book management server 20a. Sends synchronization instructions.

  When transmitting the phone book information, the transmission unit 102 receives a backup instruction input from a phone book management agent program (not shown), and reads the phone book information from the phone book storage unit 101. At this time, the transmitting unit 102 may read all the partner information (the entire phone book information), or may read only the partner information (a part of the phone book information) changed after the previous transmission. Subsequently, the transmitting unit 102 associates a terminal ID for identifying the mobile phone 10a with the read phonebook information and transmits it to the phonebook management server 20a. The transmission of the phone book information may be automatically executed by the agent program, or may be executed (manual execution) when the agent program accepts the button operation of the user of the mobile phone 10a.

  When transmitting the synchronization instruction, the transmission unit 102 receives the synchronization instruction input from the agent program in response to the synchronization execution request from the telephone directory management server 20a, and transmits the synchronization instruction. This synchronization instruction includes the terminal ID of the mobile phone 10a.

  The receiving unit 103 is means for receiving data from the telephone directory management server 20a. Specifically, the receiving unit 103 receives the synchronization execution request for requesting the mobile phone 10a to execute synchronization of the phone book information, and the phone book information transmitted from the phone book management server 20a in response to the transmission of the synchronization instruction. And receive.

  When receiving the synchronous execution request, the receiving unit 103 outputs the synchronous execution request to an agent program (not shown). As a result, the agent program and the transmission unit 102 can transmit a synchronization instruction.

  When the phone book information is received, the receiving unit 103 outputs the phone book information to the phone book storage unit 101. Thus, the same phone book information stored on the phone book management server 20a is stored in the phone book storage unit 101, and the synchronization of the phone book information is completed. At this time, the telephone directory storage unit 101 adds an additional mark to the partner information to which the attribute information is added. This additional mark is information indicating that supplementation has been performed in the telephone directory management server 20a.

  The telephone directory management server 20a is a computer system that manages the telephone directory information of the mobile phone 10a and includes a store information database (storage means) 21 and a telephone directory storage server 22. The configuration of the telephone directory management server 20a is not limited to this, and one computer system may have the functions of the store information database 21 and the telephone directory storage server 22.

  The store information database 21 is a computer system that stores store information. The store information is partner basic information including destination information and attribute information, similar to the partner information stored in the mobile phone 10a.

  An example of store information stored in the store information database 21 is shown in FIG. FIG. 3 shows four pieces of store information, and each piece of store information is composed of six types of information: store name, telephone number, e-mail address, address, business hours, and regular holidays. Of these six types of information, the telephone number and the mail address are information that can be the destination information, and in this embodiment, the telephone number is the destination information. What is used as the destination information is arbitrary as in the phone book information (partner information).

  The telephone directory storage server 22 is a computer system that stores a backup of telephone directory information of the mobile phone 10a and transmits the backup to the mobile phone 10a in response to a request from the mobile phone 10a. The telephone book keeping server 22 includes, as functional components, a receiving unit (destination receiving unit, server side destination receiving unit) 221, a telephone book supplementing unit (supplementing unit) 222, a telephone book database 223, a telephone book acquisition unit 224, A transmission unit (destination transmission unit, server-side destination transmission unit) 225 is provided.

  The receiving unit 221 is means for receiving data from the mobile phone 10a. Specifically, the receiving unit 221 receives telephone book information and a synchronization instruction. When receiving the phone book information, the receiving unit 221 outputs the phone book information to the phone book supplementing unit 222. When receiving the synchronization instruction, the reception unit 221 outputs the synchronization instruction to the telephone directory acquisition unit 224.

  The phone book supplementing unit 222 compares the phone book information received by the receiving unit 221 with the store information stored in the store information database 21, and based on the comparison result, the phone book information using the store information. It is means to replenish.

  First, the phone book supplementing unit 222 extracts partner information whose destination information is a telephone number of a fixed telephone from the input phone book information, and extracts store information corresponding to each extracted partner information from the store information database 21. . Subsequently, the telephone directory replenishment unit 222 compares the partner information and the store information for each destination information, and extracts attribute information that exists in the store information and does not exist in the partner information for each destination information. Subsequently, the telephone directory supplementing unit 222 adds the extracted attribute information to the partner information for each destination information. Thereby, the contents of the store information are reflected in the partner information.

  A specific example of replenishment of phone book information will be described on the assumption that the inputted phone book information is as shown in FIG. 2 and the store information stored in the store information database 21 is as shown in FIG. . First, the partner information of the company B, the store C, and the store D whose telephone numbers are those of the fixed phone is extracted from the phone book information of FIG. Whether or not the telephone number is a fixed number can be determined based on a number system stored in advance. Subsequently, store information of stores C and D is extracted. Since store information corresponding to company B does not exist, the attribute information of company B is not added. Subsequently, the other party information and the store information are compared for the stores C and D. This comparison is shown in FIG. In FIG. 4, the partner information of stores C and D is T, and the store information corresponding to these is S. In this case, the address of the store C, business hours, and regular holidays (location surrounded by a broken line P) are information that exists in the store information S and does not exist in the partner information T. Therefore, the address of shop C, business hours, and regular holiday information are added to the partner information of shop C (a part surrounded by a broken line Q).

  As described above, in the example illustrated in FIGS. 2 to 4, only the partner information of the store C is supplemented. The partner information of the friend A is not supplemented because it is the telephone number of the mobile phone, and the partner information of the company B is not supplemented because there is no corresponding store information. Further, the partner information of the store D is not replenished because it already includes all the attribute information existing in the store information.

  The telephone directory supplementing unit 222 outputs the supplemented telephone directory information to the telephone directory database 223. In addition, the phone book replenishment unit 222 generates a synchronization execution request for requesting the mobile phone 10 a to execute synchronization of the phone book information, and outputs it to the transmission unit 225.

  The phone book database 223 is means for storing phone book information of the mobile phone 10a. Specifically, the phone book database 223 stores the phone book information input from the phone book supplementing unit 222. The phone book information stored in the phone book database 223 is associated with the terminal ID of the mobile phone 10a.

  When a synchronization instruction is input from the reception unit 221, the phone book acquisition unit 224 extracts a terminal ID from the synchronization instruction, and reads out phone book information associated with the terminal ID from the phone book database 223. Then, the phone book acquisition unit 224 outputs the read phone book information to the transmission unit 225.

  The transmission unit 225 is means for transmitting data to the mobile phone 10a. Specifically, the transmission unit 225 transmits the synchronization execution request input from the phone book replenishment unit 222 and transmits the phone book information input from the phone book acquisition unit 224.

  Next, processing of the telephone directory management system 1a shown in FIG. 1 will be described with reference to FIG. 5, and a telephone directory management method (destination management method) according to the present embodiment will be described. FIG. 5 is a sequence diagram showing processing of the telephone directory management system 1a.

  First, when backup is instructed by an agent program (not shown) in the mobile phone 10a (step S11), the transmission unit 102 reads the phone book information from the phone book storage unit 101 (step S12), and the phone book management server It transmits to 20a (step S13).

  In the telephone directory management server 20a, the receiving unit 221 receives the telephone directory information and outputs it to the telephone directory supplementing unit 222. Subsequently, the phone book supplementing unit 222 supplements the phone book information by comparing the phone book information with the store information in the store information database 21. Specifically, the telephone directory supplementing unit 222 extracts partner information whose destination information is a telephone number of a fixed telephone, and supplements the extracted partner information by comparing the extracted partner information with store information corresponding to the partner information. The attribute information that should be extracted. Here, when there is no attribute information to be replenished (step S14; NO, replenishment step), the telephone directory replenishment unit 222 ends the process. On the other hand, when there is attribute information to be supplemented (step S14; YES, supplement step), the telephone directory supplementing unit 222 supplements the telephone directory information by adding the extracted attribute information to the partner information ( Step S15, replenishment step).

  Subsequently, the phone book replenishing unit 222 stores the phone book information in the phone book database 223 (step S16, storage step), and generates a synchronization execution request and outputs it to the transmission unit 225. Subsequently, the transmission unit 225 transmits the synchronization execution request to the mobile phone 10a (step S17).

  In the mobile phone 10a, the receiving unit 103 receives the synchronization execution request, and the transmitting unit 102 transmits a synchronization instruction in response to this request (step S18).

  Thereafter, in the telephone directory management server 20 a, the receiving unit 221 receives the synchronization instruction and outputs it to the telephone directory acquisition unit 224. Subsequently, the telephone directory acquisition unit 224 reads the supplemented telephone directory information from the telephone directory database 223 (step S19). Subsequently, the transmitting unit 225 transmits the supplemented phone book information to the mobile phone 10a (step S20).

  Thereafter, in the mobile phone 10a, the receiving unit 103 receives the supplemented phone book information and outputs it to the phone book storage unit 101. The phone book storage unit 101 adds a postscript mark to the supplemented partner information (step S21), and stores the supplemented phone book information (step S22, storage step). Thereby, the user of the mobile phone 10a can use the phone book information supplemented with attribute information.

  Next, screen transition of the mobile phone 10a before and after the above-described replenishment process will be described with reference to FIG. FIG. 6 is a schematic diagram showing the screen transition.

  Assume that the partner information before supplementing the attribute information is as shown in FIG. When the phone book information including the partner information is supplemented by the phone book management server 20a, and the supplemented phone book information is stored in the phone book storage unit 101 of the mobile phone 10a, a notification screen shown in FIG. 6B is displayed. Is displayed. The screen of FIG. 6B shows that the replenishment (update) of the phone book information has been completed.

  After that, the screen shown in FIG. 6C is displayed by a button operation by the user of the mobile phone 10a. The screen of FIG. 6C represents the history of processing executed by the mobile phone 10a, and the user can select one processing (message) from the history and check its details. For example, as shown in FIG. 6C, when a message related to the telephone directory update process is selected, as shown in FIG. 6D, which partner information is specifically updated is displayed. When the user selects one partner information here, the partner information is displayed. FIG. 6E shows partner information of the store C after replenishment. Comparing FIG. 6 (a) and FIG. 6 (e), it can be seen that information on the address, URL, business hours, and regular holidays is supplemented.

  As described above, according to the first embodiment, the store information including the attribute information is compared with the phone book information of the mobile phone 10a, and the phone book information is supplemented using the store information based on the comparison. The Then, the supplemented phone book information is transmitted to the mobile phone 10a. This makes it possible to easily register information on the communication partner without having the user of the mobile phone 10a register the attribute of the communication partner.

  Also, according to the first embodiment, only attribute information that is not yet associated with destination information is added, so that it is possible to replenish attribute information without changing already registered attribute information. .

  Further, according to the first embodiment, it becomes possible to register partner information limited to information of a communication partner (store) having a fixed telephone.

(Second Embodiment)
FIG. 7 is a diagram showing a configuration of a telephone directory management system (destination management system) 1b according to the second embodiment. The telephone directory management system 1b includes a cellular phone (communication terminal) 10b and a telephone directory management server (destination management server) 20b instead of the cellular phone 10a and the telephone directory management server 20a in the first embodiment.

  The cellular phone 10b includes a telephone directory storage unit 111, a transmission unit (terminal-side destination transmission unit) 112, a reception unit (terminal-side destination reception unit) 113, and a communication history storage unit 114. The functions of the telephone directory storage unit 111 and the reception unit 113 are the same as those of the telephone directory storage unit 101 and the reception unit 103 in the first embodiment, respectively, and thus description thereof is omitted.

  The communication history storage unit 114 is a means for storing a communication history including destination information of a communication partner. There are two types of communication history stored in the communication history storage unit 114: transmission history and reception history. The outgoing call history is a record of outgoing calls from the mobile phone 10b to other telephones, and includes the name, telephone number, and outgoing date / time of the communication partner. On the other hand, the reception history is a history of incoming calls from other telephones and includes the name, telephone number, and incoming date / time of the communication partner. The communication history storage unit 114 records the contents whenever there is an outgoing or incoming call. FIG. 8 is an example of the communication history stored in the communication history storage unit 114, and particularly shows only the transmission history.

  The transmission unit 112 has a function of transmitting the outgoing call history to the telephone directory management server 20b in addition to the same function (transmission of telephone directory information and synchronization instruction) as the transmission unit 102 in the first embodiment.

  When transmitting a transmission history, the transmission unit 112 receives a transmission history transmission instruction input from an agent program (not shown), and reads the transmission history from the communication history storage unit 114. At this time, the transmitting unit 112 may read all of the outgoing call history or only a part of the outgoing call history. Subsequently, the transmission unit 112 associates the terminal ID with the read call history and transmits it to the telephone directory management server 20b. The transmission of the outgoing call history is preferably performed periodically (automatically), but may be performed based on a user's button operation.

  The telephone directory management server 20b includes the same store information database (storage means) 21 as that of the first embodiment and a telephone directory storage server 23. Below, the telephone directory custody server 23 different from 1st Embodiment is demonstrated.

  The telephone book keeping server 23 includes a receiving unit (address receiving means, history receiving means, server side address receiving means) 231, a telephone book supplementing unit (supplementing means) 232, a telephone book database 233, a telephone book acquisition unit 234 and a transmission unit ( Destination transmission means, server-side destination transmission means) 235. The functions of the telephone directory acquisition unit 234 and the transmission unit 235 are the same as those of the telephone directory acquisition unit 224 and the transmission unit 225 in the first embodiment, respectively, and thus description thereof is omitted.

  The receiving unit 231 is means for receiving data from the mobile phone 10b. When the phone book information is received, the receiving unit 231 outputs the phone book information to the phone book database 233. When receiving the synchronization instruction, the reception unit 231 outputs the synchronization instruction to the telephone directory acquisition unit 234. When receiving the outgoing call history, the receiving unit 231 outputs the outgoing call history to the telephone directory supplementing unit 232.

  The phone book database 233 stores the phone book information input from the receiving unit 231 or the phone book supplementing unit 232.

  The telephone directory replenishment unit 232 calculates the number of transmissions for each communication partner (destination information) based on the transmission history input from the reception unit 231, extracts a communication partner whose calculated number of transmissions is a predetermined value or more, This is means for supplementing telephone directory information using the extracted store information of the communication partner.

  First, the telephone directory replenishing unit 232 receives a call history from the receiving unit 231. Subsequently, the telephone directory supplementing unit 232 reads out telephone directory information corresponding to the terminal ID associated with the outgoing call history from the telephone directory database 233. Subsequently, the telephone directory replenishment unit 232 calculates the number of calls for each communication partner based on the input call history. Subsequently, the telephone directory replenishment unit 232 compares a threshold stored in advance with each number of outgoing calls, and extracts a communication partner that has transmitted more than the threshold by the mobile phone 10b as a supplement candidate. Subsequently, the telephone directory supplementing unit 232 reads out the extracted store information of the communication partner from the store information database 21. Then, the phone book supplementing unit 232 compares the read store information with the partner information in the phone book information, and adds the attribute information in the store information to the partner information. In addition, how to set the threshold value used in such processing is arbitrary.

  As an example, the case where the read telephone directory information, store information, and outgoing call history are those shown in FIGS. In this case, the telephone directory replenishing unit 232 determines that the number of calls to the friend A, the store B, and the store D is 1 and the number of calls to the store C is 3 times.

  Here, if the threshold value stored in advance is 3 (times), the telephone directory replenishment unit 232 extracts the store C as a supplement candidate and reads the store information of the store C. Then, the telephone directory replenishment unit 232 adds attribute information to the partner information of the store C as in the case shown in FIG.

  Separately from this, when the threshold value stored in advance is 1 (times), the telephone directory replenishment unit 232 extracts the partner information of the friend A and the stores B, C, and D existing in the outgoing call history as supplement candidates. Subsequently, the telephone directory replenishment unit 232 reads store information corresponding to the extracted partner information. At this time, the telephone directory replenishment unit 232 may exclude the friend A from the replenishment target because the destination information is not the telephone number of the fixed telephone, or may search the store information without performing such exclusion processing. Good. In any case, the telephone directory replenishment unit 232 reads store information of stores B, C, and D in this case. Subsequently, the telephone directory replenishing unit 232 compares the partner information and the store information for the stores B, C, and D.

  An example of comparison and replenishment will be described with reference to FIG. In FIG. 9, the partner information of the stores C and D in the phone book information is T ′, and the read store information of the stores B, C, and D is S ′. In this case, the entire store information of the store B, the address of the store C, business hours, and regular holidays (location surrounded by a broken line P ′) are information that exists in the store information S ′ and does not exist in the partner information T ′. is there. Accordingly, the entire store information of the store B is added as partner information, and the address, business hours, and fixed holiday information of the store C are added to the partner information of the store C (a portion surrounded by a broken line Q ′).

  The telephone directory supplementing unit 232 outputs the supplemented telephone directory information to the telephone directory database 233. In addition, the phone book replenishment unit 232 generates a synchronization execution request for requesting the mobile phone 10 b to execute synchronization of the phone book information, and outputs the request to the transmission unit 235.

  Next, processing of the telephone directory management system 1b shown in FIG. 7 will be described with reference to FIGS. FIG. 10 is a sequence diagram showing a backup process of the phone book information, and FIG. 11 is a sequence diagram showing a process of supplementing and synchronizing the phone book information.

  First, it demonstrates using FIG. The process of steps S31 to S33 is the same as the process of steps S11 to S13 in the first embodiment. Thereafter, in the phone book management server 20b, the phone book database 233 stores the phone book information received by the receiving unit 231 (step S34). Thereby, the backup of the phone book information is completed.

  Thereafter, replenishment and synchronization of the phone book information is performed as shown in FIG. When a transmission history transmission instruction is output from an agent program (not shown) (step S41), the transmission unit 112 of the mobile phone 10b reads the transmission history from the communication history storage unit 114 (step S42), and the telephone directory management server It transmits to 20b (step S43).

  In the telephone directory management server 20 b, the receiving unit 231 receives the outgoing call history and outputs it to the telephone directory supplementing unit 232. Subsequently, the phone book supplementing unit 232 supplements the phone book information based on the outgoing call history, the phone book information of the mobile phone 10b that is the transmission source of the outgoing call history, and the store information in the store information database 21. . Specifically, the telephone directory replenishment unit 232 calculates the number of transmissions for each communication partner based on the transmission history, and extracts a communication partner whose number of transmissions is a predetermined threshold or more as a supplement candidate. Then, the telephone directory supplementing unit 232 extracts attribute information to be supplemented by comparing the store information corresponding to the extracted communication partner and the partner information. Here, when there is no attribute information to be replenished (step S44; NO, replenishment step), the telephone directory replenishment unit 232 ends the process. On the other hand, when there is attribute information to be replenished (step S44; YES, replenishment step), the telephone directory supplementing unit 232 supplements the telephone directory information by adding the attribute information in the store information to the partner information. (Step S45, replenishment step).

  The processes in steps S46 to S52 performed thereafter are the same as the processes in steps S16 to S22 in the first embodiment.

  Note that the screen transition of the mobile phone 10b before and after such a replenishment process is the same as that in the first embodiment, and a description thereof will be omitted.

  As described above, according to the second embodiment, since the phone book information is supplemented using store information of a communication partner who has communicated more than a preset threshold value, communication with a high possibility of contacting in the future. It is possible to supplement only the information of the other party, that is, information that is highly necessary for registration.

  In addition, according to the second embodiment, even if the destination information of a communication partner who has communicated before is not registered in advance in the phone book information of the mobile phone 10b, the store of the communication partner based on the outgoing call history Information is added to the phone book information. Therefore, the user can acquire the store information of the other party without registering in advance the telephone number or mail address of the other party who has contacted.

  The present invention has been described in detail based on the embodiments. However, the present invention is not limited to the above embodiment. The present invention can be modified in various ways as described below without departing from the scope of the invention.

  In the second embodiment, the phone book information is supplemented and synchronized with the transmission of the call history, but not only when the call history is transmitted, but also when the phone book information is backed up as in the first embodiment. May also be replenished and synchronized. Thereby, the mobile phone 10b can acquire the phone book information supplemented with the attribute information earlier.

  In the second embodiment, the phone book information is supplemented based on the transmission history, but the phone book information may be supplemented based on the reception history, or the phone book information is supplemented based on both the transmission and reception histories. May be.

  In each of the above embodiments, only the partner information of the communication partner whose destination information is the telephone number of the fixed telephone is supplemented. However, the partner information may be supplemented regardless of the type of the destination information. For example, the partner information having the telephone number of a mobile communication terminal such as a mobile phone may be supplemented.

  In each of the above embodiments, the phone book information is supplemented on the server side. However, the mobile phone may directly acquire the store information from the store information database 21 and perform the supplement processing in the own device. In this case, the mobile phone includes functional components corresponding to the telephone directory supplementing units 222 and 232. In this case, the mobile phone can replenish the phone book information without performing synchronization processing with the server.

  In each of the above embodiments, the phone book information is used as the destination management information, but other types of information may be used as the destination management information.

  In each said embodiment, although shop information was used as partner basic information, the kind of partner basic information is not limited. For example, mobile phone user information or company information may be used as the partner basic information. It is optional to store these information in one database or in different databases.

  In each of the above embodiments, the phone book information is supplemented by adding only the attribute information that is not yet associated with the destination information without changing the already registered attribute information. The information having the same attribute as the existing attribute information may be supplemented as information separate from the registered attribute information. In this case, information input by the user (hereinafter referred to as “manual input information”) and information supplemented by the telephone directory management system (hereinafter referred to as “supplement information”) may coexist for a certain attribute.

  Regardless of the presence or absence of manual input information, the attribute to be supplemented is arbitrary. For example, an address, URL, business hours, and regular holidays can be set as such attributes. In this case, for example, even if the address “address x”, the URL “URL (y)”, and the business hours “time z” of the store X are already registered in the phone book information, the phone book management system stores the basic information on the partner of the store X. Based on the information, the address “address x ′”, the URL “URL (y ′)” and the business time “time z ′” of the store X are supplemented to the telephone directory information. At this time, the contents of the manually input information may match the contents of the supplement information.

  The supplement information is displayed separately from the manually input information on the screen of the communication terminal. In the example shown in FIG. 12, the supplement information is displayed in the display field F. By switching the tab Fa of the display field F, the user can view three types of information: address, URL, and memo (for example, information such as business hours and regular holidays). The display field F may not be edited.

  In each of the above embodiments, a mobile phone is used as a communication terminal. However, various devices such as a portable information terminal (Personal Digital Assistant, PDA) and a desktop computer may be used as a communication terminal.

It is a figure which shows the structure of the telephone directory management system which concerns on 1st Embodiment. It is a figure which shows the example of telephone directory information. It is a figure which shows the example of shop information. It is a figure which shows the example of supplementation of telephone directory information. It is a sequence diagram which shows the process of the telephone directory management system shown in FIG. It is a schematic diagram which shows the screen transition of the mobile telephone shown in FIG. It is a figure which shows the structure of the telephone directory management system which concerns on 2nd Embodiment. It is a figure which shows the example of a communication log | history (transmission log | history). It is a figure which shows the example of supplementation of telephone directory information. It is a sequence diagram which shows the process of the telephone directory management system shown in FIG. It is a sequence diagram which shows the process of the telephone directory management system shown in FIG. It is a figure which shows the example of a display of supplement information.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1a, 1b ... Phonebook management system (destination management system), 10a, 10b ... Mobile phone (communication terminal), 20a, 20b ... Phonebook management server (destination management server), 21 ... Store information database (storage means), 22 , 23 ... Phonebook storage server, 101, 111 ... Phonebook storage unit, 102, 112 ... Transmission unit (terminal side destination transmission means), 103, 113 ... Reception unit (terminal side destination reception means), 114 ... Communication history storage , 221... Receiving unit (destination receiving unit, server side destination receiving unit) 231 (destination receiving unit, history receiving unit, server side destination receiving unit)... Receiving unit, 222, 232. , 223, 233 ... telephone book database, 224, 234 ... telephone book acquisition unit, 225, 235 ... transmission unit (destination transmission means, server side destination transmission means)

Claims (8)

Storage means for storing one or more partner basic information in which destination information indicating a destination of a communication partner is associated with attribute information indicating an attribute of the communication partner;
Destination receiving means for receiving destination management information including one or more of the destination information from a communication terminal;
Replenishment that compares the destination management information received by the destination receiving means with the other party basic information stored in the storage means and replenishes the destination management information using the other party basic information based on the comparison result Means,
Destination transmission means for transmitting the destination management information supplemented by the supplement means to the communication terminal;
A destination management server comprising: A history receiving means for receiving a communication history including the destination information from the communication terminal;
The replenishing means extracts the destination information included in the communication history received by the history receiving means, and replenishes the destination management information using the partner basic information corresponding to the extracted destination information;
The destination management server according to claim 1. The replenishing means calculates the number of communications for each destination information based on the communication history received by the history receiving means, extracts destination information whose calculated number of communications is a predetermined value or more, and extracts the extracted destination Replenishing the destination management information using the partner basic information corresponding to the information;
The destination management server according to claim 2. The replenishing means extracts the destination information that exists in the communication history and does not exist in the destination management information, and adds the partner basic information corresponding to the extracted destination information to the destination management information. Replenish management information,
The destination management server according to claim 2 or 3. The replenishment means extracts attribute information that exists in the partner basic information and does not exist in the destination management information for each destination information, and associates the extracted attribute information with the destination information for each destination information. , Replenish the destination management information,
The destination management server according to any one of claims 1 to 4. The replenishment means replenishes the destination management information using the partner basic information corresponding to the destination information of the fixed terminal;
The destination management server according to any one of claims 1 to 5. A destination management system comprising a communication terminal and a destination management server capable of communicating with the communication terminal,
The communication terminal is
Terminal-side destination transmission means for transmitting destination management information including one or a plurality of destination information indicating destinations of communication partners;
Terminal-side destination receiving means for receiving destination management information transmitted from the destination management server in response to transmission by the terminal-side destination transmitting means;
With
The destination management server is
Storage means for storing one or more partner basic information in which destination information indicating a destination of a communication partner is associated with attribute information indicating an attribute of the communication partner;
Server-side destination receiving means for receiving destination management information transmitted by the terminal-side destination transmitting means;
The destination management information received by the server-side destination receiving means is compared with the other party basic information stored in the storage means, and the destination management information is supplemented using the other party basic information based on the comparison result. Replenishment means to
Server-side destination transmission means for transmitting destination management information supplemented by the supplement means to the communication terminal;
Comprising
A destination management system characterized by that. A destination that can communicate with a database that stores one or more partner basic information in which destination information indicating a destination of a communication partner and attribute information indicating an attribute of the communication partner are associated with each other, and includes one or a plurality of the destination information A destination management method in a communication device that stores management information,
The communication device compares the destination management information stored in the communication device with the other party basic information stored in the database, and based on the result of the comparison, uses the other party basic information to determine the destination management information. A replenishment step to replenish;
A storage step in which the communication device stores the destination management information supplemented in the supplementing step;
A destination management method comprising:

Images