JP2006295651A - Number management device and its method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a number management server in which a called terminal can specify a calling terminal even when communication between the called terminal and the calling terminal is not held. <P>SOLUTION: When the calling terminal 10 and the called terminal 20 implements communication with each other, the number management server 30 is arranged in a system where transmission and proper numbers of the calling terminal 10 are different from each other. The number management server 30 includes a communication history holding section 35 for associating the calling terminal 10 and the called terminal 20 with each other to hold the terminals, a user information holding section 34 for associating the proper and transmitting numbers of the calling terminal 10 with each other to hold the numbers, an acquisition request judging section 32 for judging whether the communication between the calling terminal 10 and the called terminal 20 has been implemented or not in response to an inquiry request from the called terminal 20, and an acquisition request replying section 33 for replying the proper number of the calling terminal 10 to the receiving terminal 20. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a number management device and a number management method for managing a number of a calling terminal.

  Conventionally, a portable terminal such as a cellular phone has a terminal-specific telephone number (for example, a number starting from 090 and 080).

  When this portable terminal is placed under a gateway device such as a wireless LAN or an access point, the calling number from the portable terminal is a telephone number issued by the gateway device (for example, a number starting from 050). The telephone number paid out by the gateway device is dynamically assigned / released by movement of the portable terminal.

  Specifically, when there is a call from a mobile terminal under its control, the gateway device assigns an unused number to the portable terminal and performs a call to the receiving terminal. In this case, the receiving terminal only recognizes the calling number assigned by the gateway device, and cannot specify the telephone number of the calling terminal.

For this reason, in peer-to-peer communication, a technique for inquiring information about a calling side terminal such as a telephone number of the calling side terminal from the receiving side terminal to the calling side terminal is disclosed (for example, refer to Patent Document 1).
JP 2005-26952 A

  However, in the above-described conventional technology, only when peer-to-peer communication is maintained, the receiving terminal can obtain information on the calling terminal, and when the calling terminal moves out of service area or when communication is It is difficult to obtain information when communication is not maintained, such as after completion.

  Therefore, in view of the above-described problems, the present invention provides a number management apparatus and a number management method that allow a receiving terminal to identify a calling terminal even when communication between the calling terminal and the receiving terminal is not maintained. The purpose is to provide.

  In order to achieve the above object, the first feature of the present invention is that when the calling terminal and the called terminal communicate, the calling number of the calling terminal notified to the called terminal and the uniqueness of the calling terminal A number management device arranged in a system having a different number, wherein (a) a communication monitoring unit that monitors communication between a transmission side terminal and a reception side terminal, and (b) a transmission side terminal monitored by the communication monitoring unit And a communication history holding unit that holds the caller terminal in association with each other, and (c) a user information holding unit that holds the unique number of the caller terminal and the caller number used for communication of the caller terminal in association with each other. And (d) referring to the communication history holding unit in response to the inquiry request for the unique number of the caller terminal from the callee terminal, and determining whether the communication between the callee terminal and the caller terminal has been in the past. An acquisition request determination unit, and (e) an acquisition request determination unit Therefore, it is a number management device provided with an acquisition request answering unit that refers to the user information holding unit and answers the unique number of the calling terminal to the receiving terminal when it is determined that there has been communication in the past And

  According to the number management device according to the first feature, in order to retain the past communication history and user information, even if communication between the caller terminal and the callee terminal is not maintained, the callee terminal changes the caller terminal. Can be identified.

  In addition, the acquisition request determination unit of the number management device according to the first feature verifies whether or not the called terminal that has made the inquiry request is a valid terminal. You may respond.

  According to this number management device, the unique number of the calling terminal can be answered only in response to an inquiry request from a valid receiving terminal.

  The communication history holding unit of the number management apparatus according to the first feature holds a counter that counts the number of times of communication and the number of inquiry requests, and the acquisition request determination unit refers to the counter and inquires from the number of times of communication. When the number of requests is large, it is not necessary to respond to the inquiry request.

  According to this number management device, when the number of inquiries is greater than the number of past communications, the inquiry request is not responded, so that the unique number of the calling terminal is not unnecessarily notified.

  The second feature of the present invention is that a number in a system in which a calling number of a calling terminal notified to the called terminal is different from a unique number of the calling terminal when the calling terminal and the called terminal communicate with each other. (A) a step of monitoring communication between a caller terminal and a callee terminal; (b) a step of associating and holding the monitored caller terminal and callee terminal; (c) ) A step of associating and holding the unique number of the caller terminal and the caller number used for communication of the caller terminal; and (d) responding to an inquiry request for the unique number of the caller terminal from the callee terminal. In the step of determining whether or not the communication between the receiving side terminal and the calling side terminal has occurred in the past, and in the step of (e) determining, if it is determined that there has been communication in the past, the calling side terminal Reply with device's unique number And summarized in that a number management method comprising the steps.

  According to the number management method according to the second feature, since the past communication history and user information are retained, even if communication between the caller terminal and the callee terminal is not maintained, the callee terminal changes the caller terminal. Can be identified.

  According to the present invention, it is possible to provide a number management device and a number management method that allow a receiving terminal to specify information regarding the calling terminal even when communication between the calling terminal and the receiving terminal is not maintained. it can.

  Next, embodiments of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, it should be noted that the drawings are schematic.

(Number management system)
As shown in FIG. 1, the number management system according to the present embodiment includes a plurality of terminals (for example, portable terminals such as mobile phones) 10 and 20 and a number management server (number management device) 30. Here, when the calling terminal 10 and the receiving terminal 20 communicate with each other, the calling number of the calling terminal 10 notified to the receiving terminal 20 (used for communication) and the unique number of the calling terminal 10 are communicated. Is assumed to be different.

  For example, the terminals 10 and 20 have terminal-specific telephone numbers (for example, numbers starting from 090 and 080). When the terminals 10 and 20 are placed under a gateway device such as a wireless LAN or an access point, the calling number from the terminals 10 and 20 is a telephone number (for example, a number starting from 050) issued by the gateway device. It becomes.

  That is, when the originating terminal 10 under the gateway device starts communication with the terminating terminal 20, the terminating terminal 20 recognizes the telephone number issued by the gateway device, not the unique telephone number of the originating terminal 10. To do.

  As shown in FIG. 1, the receiving terminal 20 includes a communication unit 21 and a user information acquisition request unit 22.

  The communication unit 21 communicates with the caller terminal 10.

  The user information acquisition request unit 22 makes an inquiry request to the number management server 30 to acquire user information related to the caller terminal 10. User information includes terminal location information and the like in addition to a telephone number unique to the terminal.

  The calling terminal 10 also has the same configuration as the receiving terminal 20.

  The number management server 30 includes a communication monitoring unit 31, a user information holding unit 34, a communication history holding unit 35, an acquisition request determining unit 32, and an acquisition request answering unit 33. The number management server 30 is arranged on the network, but the arrangement location is not particularly limited as long as the communication between the calling terminal 10 and the receiving terminal 20 can be monitored. For example, each functional unit of the number management server 30 may be arranged inside the caller terminal 10.

  The communication monitoring unit 31 monitors communication between the transmitting terminal 10 and the receiving terminal 20.

  The user information holding unit 34 holds the unique number of the caller terminal 10 and the caller number used for communication of the caller terminal 10 in association with each other. For example, as shown in FIG. 2, the user information holding unit 34 assigns an arbitrary identification number to each terminal, the terminal-specific number (090 number shown in FIG. 2), and the transmission number used for communication (FIG. 2). 050 number shown in FIG. 5) and the location information of the terminal are stored in association with each other. The data held in the user information holding unit 34 is set in advance, and is updated every time the data is changed by the communication monitoring unit 31.

  The communication history holding unit 35 holds the calling terminal 10 and the receiving terminal 20 that are monitored by the communication monitoring unit 31 in association with each other. For example, as shown in FIG. 3, the communication history holding unit 35 assigns an arbitrary identification number for each communication, and the transmission side terminal 10, the reception side terminal 20, the communication start time, the communication end time, and the communication The number of times and a counter that counts the number of inquiry requests from the receiving terminal 20 are held in association with each other. Here, for example, the counter is incremented by 1 when communication is performed, and is decremented by 1 when an inquiry request is performed. The data held in the communication history holding unit 35 is set in advance and is updated every time the data is changed by the communication monitoring unit 31.

  The acquisition request determination unit 32 refers to the communication history holding unit 35 in response to an inquiry request for the unique number of the transmission side terminal 10 from the reception side terminal 20, and communication between the reception side terminal 20 and the transmission side terminal 10 is performed. Determine if it was in the past.

  In addition, the acquisition request determination unit 32 verifies whether or not the receiving-side terminal 20 that has made the inquiry request is a valid terminal, and responds to the inquiry request only when it is a valid terminal. This verification is performed using, for example, signature verification.

  Furthermore, the acquisition request determination unit 32 refers to the counter of the communication history holding unit 35 and does not respond to the inquiry request when the number of inquiry requests is larger than the number of communication.

  The acquisition request answering unit 33 holds the user information when the acquisition request determining unit 32 determines that there has been communication in the past, and the receiving terminal 20 is a valid terminal and the number of inquiry requests is not greater than the number of communication. Referring to the unit 34, the caller terminal 20 is answered with the unique number of the caller terminal 10.

  Note that the user information holding unit 34 and the communication history holding unit 35 described above may use an internal storage device such as a RAM or an external storage device such as a hard disk or a flexible disk.

  In addition, the number management server 30 according to the present embodiment can be configured to include a communication monitoring unit 31, an acquisition request determination unit 32, an acquisition request answering unit 33, and the like as modules in a CPU. These modules can be realized by executing a dedicated program for using a predetermined program language in a general-purpose computer such as a personal computer.

  Although not shown, the number management server 30 may include a program holding unit that stores a program for causing the CPU to execute an acquisition request determination process, an acquisition request reply process, and the like. The program holding unit is a recording medium such as a RAM, a ROM, a hard disk, a flexible disk, a compact disk, an IC chip, and a cassette tape. According to such a recording medium, it is possible to easily store, transport, and sell programs.

(Number management method)
Next, regarding the number management method according to the present embodiment, the operation of the number management server 30 will be described with reference to FIG.

  First, in step S <b> 101, the acquisition request determination unit 32 receives an inquiry request for information regarding the caller terminal 10 from the callee terminal 20. This inquiry request may be transmitted while the callee terminal 10 is being called from the caller terminal 10, and if the callee terminal 20 cannot communicate when called, the callee terminal 20 May be transmitted after communication in accordance with the incoming call history remaining in

  Next, in step S <b> 102, the acquisition request determination unit 32 refers to the communication history holding unit 35 and searches for a communication history related to the receiving terminal 20.

  Next, in step S <b> 103, the acquisition request determination unit 32 determines whether communication between the transmission-side terminal 10 and the reception-side terminal 20 has occurred in the past. If there is communication, the process proceeds to step S104. If not, the process proceeds to step S107, and the acquisition request reply unit 33 does not respond to the inquiry from the receiving terminal 20.

  Next, in step S104, the acquisition request determination unit 32 verifies whether the inquired receiving terminal 20 is a valid terminal. If it is a legitimate terminal, the process proceeds to step S105. If not, the process proceeds to step S107, and the acquisition request answering unit 33 does not respond to an inquiry from the receiving terminal 20.

  Next, in step S105, the acquisition request determination unit 32 refers to the communication history holding unit 35 and determines whether or not the number of inquiries is greater than the number of past communications. When there are not many, it progresses to step S106, and when there are many, it progresses to step S107, and the acquisition request reply part 33 does not respond to the inquiry from the receiving terminal 20.

  Next, in step S <b> 106, the acquisition request answering unit 33 refers to the user information holding unit 34 and replies to the receiving terminal 20 with the unique number of the calling terminal 10.

(Action and effect)
According to the number management server (number management apparatus) 30 and the number management method according to the present embodiment, communication between the caller terminal 10 and the callee terminal 20 is not maintained in order to retain past communication history and user information. Even in this case, the receiving terminal 20 can identify the calling terminal 10. In addition, in order to respond to an inquiry request from the receiving terminal 20 only when the communication between the receiving terminal 20 and the calling terminal 10 has been in the past, the unique number of the calling terminal 10 is notified to an unauthorized terminal. There is no.

  Therefore, for example, even when the receiving terminal 20 cannot communicate and the calling number of the calling terminal 10 (for example, a number starting with 050) remains in the incoming call history, the receiving terminal 20 manages the number. By making an inquiry to the server 30, a unique telephone number (for example, a number starting with 090) of the calling terminal 10 can be acquired.

  In addition, when each functional unit of the number management server 30 is arranged inside the caller terminal 10, the caller terminal 10 can make an acquisition request determination, reply, communication monitoring, etc. An inquiry is made to the temporary address of the caller terminal 10. Note that since the address of the calling terminal 10 changes after the terminal moves, this sequence is particularly effective from the moment the calling terminal 20 is called by the calling terminal 10 until the calling terminal 10 moves. It can be used effectively.

  In addition, when the incoming call terminal 20 cannot communicate, the outgoing call number of the outgoing call terminal 10 (for example, a number starting with 050) remains in the incoming call history, and redialing is performed from the incoming call terminal 20. Even when the caller terminal 10 has already moved and communication is not possible, a unique telephone number (for example, a number starting with 090) of the caller terminal 10 is obtained by making an inquiry to the number management server 30. Can do.

  In addition, according to the present embodiment, not only the inquiry of the incoming call history but also the caller terminal 10 from the callee terminal 20 while the caller terminal 10 calls the callee terminal 20 (while the so-called ringing melody flows). By the inquiry, the unique telephone number of the calling terminal 10 can be acquired. Furthermore, the receiving terminal 20 can display the caller by referring to the telephone book that is held.

  In addition, the acquisition request determination unit 32 verifies whether or not the receiving-side terminal 20 that has made the inquiry request is a valid terminal, and responds to the inquiry request only when it is a valid terminal. For this reason, the unique number of the calling terminal 10 can be answered only in response to an inquiry request from the valid receiving terminal 20.

  The communication history holding unit 35 holds a counter for counting the number of times of communication and the number of inquiry requests. The acquisition request determining unit 32 refers to the counter, and inquires when the number of inquiry requests is larger than the number of communication times. Does not meet the request. For this reason, when the number of inquiries is large with respect to the past number of communications, the inquiry request is not responded, so that the unique number of the calling terminal 10 is not unnecessarily notified.

(Other embodiments)
Although the present invention has been described according to the above-described embodiments, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art.

  For example, in the above embodiment, the description has been made assuming that the terminals 10 and 20 are cellular phones. However, the terminals 10 and 20 are not limited to this, and the present invention is applicable to portable devices such as notebook computers, PHS, and PDAs. Applicable.

  As described above, the present invention naturally includes various embodiments not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

It is a block diagram of the configuration of a number management system according to the present embodiment. It is an example of the data which the user information holding part of the number management server which concerns on this embodiment hold | maintains. It is an example of the data which the communication history holding | maintenance part of the number management server which concerns on this embodiment hold | maintains. It is a flowchart which shows the number management method which concerns on this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Originating side terminal 11 ... Communication part 12 ... User information acquisition request part 20 ... Incoming side terminal 21 ... Communication part 22 ... User information acquisition request part 30 ... Number management server 31 ... Communication monitoring part 32 ... Acquisition request judgment part 33 ... Acquisition request reply unit 34 ... user information holding unit 35 ... communication history holding unit

Claims (4)

A number management device arranged in a system in which a calling number of the calling terminal notified to the called terminal and a unique number of the calling terminal are different when the calling terminal and the called terminal communicate with each other There,
A communication monitoring unit for monitoring communication between the calling terminal and the called terminal;
A communication history holding unit that holds the calling terminal and the receiving terminal that are monitored by the communication monitoring unit in association with each other;
A user information holding unit that holds the unique number of the calling terminal and the calling number used for communication of the calling terminal;
In response to an inquiry request for the unique number of the caller terminal from the callee terminal, the communication history holding unit is referred to determine whether communication between the callee terminal and the caller terminal has occurred in the past. An acquisition request determination unit,
When the acquisition request determination unit determines that there has been communication in the past, the acquisition request response unit refers to the user information holding unit and returns a unique number of the calling terminal to the receiving terminal. A number management device characterized by that.   The acquisition request determining unit verifies whether or not the receiving terminal that has made the inquiry request is a valid terminal, and responds to the inquiry request only when the terminal is a valid terminal. Item 2. The number management device according to Item 1. The communication history holding unit holds a counter that counts the number of times of communication and the number of times of the inquiry request,
The number management apparatus according to claim 1, wherein the acquisition request determination unit refers to the counter and does not respond to the inquiry request when the number of inquiry requests is greater than the number of communication. A number management method in a system in which a calling number of the calling terminal notified to the called terminal and a unique number of the calling terminal are different when the calling terminal and the called terminal communicate with each other,
Monitoring communication between the originating terminal and the terminating terminal;
Holding the monitored originating terminal and the called terminal in association with each other;
A step of associating and holding the unique number of the calling terminal and the calling number used for communication of the calling terminal;
Determining whether or not communication between the receiving terminal and the calling terminal has occurred in the past in response to an inquiry request for the unique number of the calling terminal from the receiving terminal;
And a step of responding to the receiving terminal with a unique number of the calling terminal when it is determined that there has been communication in the past in the determining step.

Images