Telephone number investigation device, investigation method, investigation program, and information provision system

Abstract

To determine the usage status of telephone numbers in an IMS network by using an IMS interconnection interface for interconnection between operators.SOLUTION: A telephone number investigation device 10 is connected to a plurality of IMS terminals 50 connected to a terminating mobile IMS network 30 via an originating fixed IMS network 20, applies SDP parameters to an INVITE request for the IMS terminal 50 to be investigated, sends the INVITE request to the originating fixed IMS network 20, receives a response message via the originating fixed IMS network 20, and determines the usage status of the telephone number of the IMS terminal 50 to be investigated on the basis of the response message.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for investigating telephone numbers. [Background technology]

[0002] A known prior art for determining telephone number information is a telephone number information determination device using a computer server connected to a plurality of terminals via an Internet network, the device comprising: a database for storing usage history information of a plurality of telephone numbers; search information receiving means for receiving authentication information from the terminal and receiving a telephone number as search information from the terminal on condition that the authentication means permits login; and system control means for searching the database using the telephone number received by the search information receiving means, analyzing a change in the telephone number field to a missing number to determine whether there are a plurality of histories in the telephone number history information that transition from a subscription state to a missing number state, and / or analyzing a valid change in the telephone number field to determine whether there are a plurality of histories in the telephone number history information that transition from a missing number state to a subscription state, and generating history determination information for determining that the telephone number in the search information is a predetermined subscriber number by referring to unaccumulated history in the telephone number history information, a missing number history that is the most recent investigation record in the telephone number history information, a missing number history that is the investigation record one before the most recent investigation record, and a plurality of call termination histories in the telephone number history information, and displaying this history determination information on the terminal via the Internet network (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-060796 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, with the transition from PSTN (Public Switched Telephone Networks) to NGN (Next Generation Networks), the interconnection interface between carriers will also change from the common channel signaling system SS7 (Signaling System No. 7) to the IP (Internet Protocol) system SIP (Session Initiation Protocol).As a result, specific SIP messages from calling terminals (e.g. telephone number research devices) will reach the IMS (IP Multimedia Subsystem) network, the NGN network, and the IP telephone network (VoIP: Voice over Internet Protocol).

[0005] IMS is a standard for converting services that have previously been provided via fixed networks and mobile communications into IP, thereby enabling integrated multimedia services, and mobile communications systems and NGNs are examples of systems that have been built in accordance with this standard.

[0006] For this reason, it is necessary to ensure a smooth transition to the new system infrastructure by introducing a SIP protocol-based telephone number investigation tool that can connect to the originating IMS network via a UNI (User Network Interface), utilizing an IMS interconnection interface for interconnection between carriers and determining the usage status of telephone numbers in the destination IMS network.

[0007] Therefore, in one aspect, the present invention aims to provide a technique capable of determining the usage status of a telephone number in an IMS network by using an IMS interconnection interface or the like for interconnection between carriers. [Means for solving the problem]

[0008] In order to solve the above problem, a telephone number investigation device according to the present invention is a telephone number investigation device connected via an originating fixed IMS network to a plurality of IMS terminals connected to a terminating mobile IMS network, and includes: a message exchange control unit that adds SDP parameters to an INVITE request for the IMS terminal to be investigated, transmits the INVITE request to the originating fixed IMS network, and receives a response message via the originating fixed IMS network; and a telephone number investigation determination unit that determines a usage status of the telephone number of the IMS terminal to be investigated in accordance with the response message, wherein the SDP parameters may be described as a network protocol of IPv4, a media type of audio only, a media transport protocol of RTP / AVP only, and a voice codec including G.711 μ-law and G.722.

[0009] The telephone number investigation device of the present invention may be configured so that the telephone number investigation determination unit determines that the telephone number of the IMS terminal to be investigated actually exists when the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, and determines that the telephone number of the IMS terminal to be investigated is a missing number when the response message is code 404 Not Found.

[0010] The telephone number investigation device according to the present invention may be configured so that, when the response message is code 183 Session Progress or code 180 Ringing, the telephone number investigation determination unit determines that the telephone number of the IMS terminal to be investigated exists, and the message switching control unit sends a CANCEL request to the calling fixed IMS network, thereby stopping ringing of the call bell of the IMS terminal to be investigated if a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated.

[0011] Furthermore, a telephone number investigation method according to the present invention is a telephone number investigation method for investigating usage status of telephone numbers of IMS terminals to be investigated by using an apparatus connected to a plurality of IMS terminals connected to a terminating mobile IMS network via an originating fixed IMS network, and includes the steps of: the apparatus adding SDP parameters to an INVITE request for the IMS terminal to be investigated and transmitting the INVITE request to the originating fixed IMS network; receiving a response message via the originating fixed IMS network; and determining the usage status of the telephone number of the IMS terminal to be investigated according to the response message, and the SDP parameters may be described as a network protocol of IPv4, a media type of only audio, a media transport protocol of only RTP / AVP, and a voice codec including G.711 μ-law and G.722.

[0012] A telephone number investigation method according to the present invention is a telephone number investigation method for investigating the usage status of telephone numbers of IMS terminals to be investigated by using an apparatus connected to a plurality of IMS terminals connected to a terminating mobile IMS network via an originating fixed IMS network, and includes the steps of: the apparatus adding SDP parameters to an INVITE request for the IMS terminal to be investigated and transmitting the INVITE request to the originating fixed IMS network; receiving a response message via the originating fixed IMS network; and determining the usage status of the telephone number of the IMS terminal to be investigated in accordance with the response message, wherein the SDP parameters may describe a network protocol as IPv6, a media type as audio only, a media transport protocol as RTP / AVP only, and a voice codec as G.711 μ-law only.

[0013] The telephone number investigation method according to the present invention may determine that the telephone number of the IMS terminal to be investigated actually exists when the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, and determine that the telephone number of the IMS terminal to be investigated is a missing number when the response message is code 404 Not Found.

[0014] The telephone number investigating method according to the present invention may determine that the telephone number of the IMS terminal to be investigated exists when the response message is code 183 Session Progress or code 180 Ringing, and send a CANCEL request to the originating fixed IMS network, thereby stopping ringing of the call bell of the IMS terminal to be investigated when a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated.

[0015] In addition, a telephone number investigation program according to the present invention may cause a computer connected via an originating fixed IMS network to a plurality of IMS terminals connected to a terminating mobile IMS network to execute at least the following processes: a process of causing a computer connected via an originating fixed IMS network to add SDP parameters to an INVITE request for the IMS terminal to be investigated and transmit the INVITE request to the originating fixed IMS network; a process of causing a computer to receive a response message via the originating fixed IMS network; and a process of determining a usage status of the telephone number of the IMS terminal to be investigated according to the response message, wherein the SDP parameters are described as a network protocol of IPv4, a media type of only audio, a media transport protocol of only RTP / AVP, and a voice codec including G.711 μ-law and G.722.

[0016] The telephone number investigation program of the present invention may determine that the telephone number of the IMS terminal to be investigated actually exists when the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, and may determine that the telephone number of the IMS terminal to be investigated is a missing number when the response message is code 404 Not Found.

[0017] The telephone number investigation program according to the present invention may be configured to determine that the telephone number of the IMS terminal to be investigated exists when the response message is code 183 Session Progress or code 180 Ringing, and to stop ringing of the call bell of the IMS terminal to be investigated by sending a CANCEL request to the originating fixed IMS network when a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated.

[0018] Furthermore, a telephone number information provision system according to the present invention may include any one of the telephone number investigation devices described above and a user terminal, and may further include a network interface unit that, when the telephone number investigation device receives a telephone number investigation information provision request for the IMS terminal from the user terminal, transmits the telephone number usage status of the IMS terminal determined by the telephone number investigation determination unit to the user terminal from which the telephone number investigation information provision request was made, via an IP network. Effect of the Invention

[0019] According to one aspect of the present invention, it is possible to determine the usage status of a telephone number in an IMS network by using an IMS interconnection interface or the like for interconnection between carriers. [Brief description of the drawings]

[0020] [Figure 1] 1 is a schematic diagram showing a network connection form of a telephone number research device according to an embodiment of the present invention; [Diagram 2] FIG. 10 is a diagram for explaining a basic sequence pattern 1 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Diagram 3] FIG. 10 is a diagram illustrating a basic sequence pattern 2 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Figure 4] FIG. 11 is a diagram illustrating pattern 3 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Diagram 5] FIG. 11 is a diagram illustrating pattern 4 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Figure 6]FIG. 11 is a diagram illustrating a basic sequence pattern 5 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Figure 7] FIG. 11 is a diagram illustrating a basic sequence pattern 6 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Figure 8] FIG. 11 is a diagram illustrating a basic sequence pattern 7 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is not busy. [Figure 9] FIG. 11 is a diagram illustrating pattern 8 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone actually exists as a called device and is not busy. [Figure 10] FIG. 1 is a diagram for explaining a basic sequence pattern 1 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is busy. [Figure 11] FIG. 11 is a diagram illustrating a pattern 2 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a mobile phone is actually present as a called device and is busy. [Figure 12] FIG. 1 is a diagram illustrating a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when the called device has an unused number. [Figure 13] FIG. 2 is a block diagram showing the configuration of the telephone number investigation device of FIG. 1. [Figure 14] FIG. 10 is a diagram illustrating a first operation sequence when a mobile phone actually exists as an IMS terminal to be investigated and is not busy. [Figure 15] FIG. 11 is a diagram illustrating the second operation sequence when a mobile phone actually exists as the IMS terminal to be investigated and is not busy. [Figure 16]FIG. 11 is a diagram illustrating the third operation sequence when a mobile phone actually exists as the IMS terminal to be investigated and is not busy. [Figure 17] FIG. 10 is a diagram for explaining a first operation sequence when a mobile phone actually exists as the IMS terminal to be investigated and is busy. [Figure 18] FIG. 11 is a diagram illustrating a second operational sequence when a mobile phone actually exists as the IMS terminal to be surveyed and is busy. [Figure 19] 13 is a diagram illustrating an operation sequence when the IMS terminal to be investigated has a missing number. [Figure 20] FIG. 13 is a diagram for explaining the operation sequence when the IMS terminal to be investigated has a missing number (IPv4, G.711 μ-law only). [Figure 21] FIG. 1 is a diagram for explaining a basic sequence pattern 1 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a data communication-only terminal actually exists as a called device. [Figure 22] FIG. 11 is a diagram for explaining a pattern 2 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a data communication-only terminal actually exists as a called device. [Figure 23] FIG. 11 is a diagram for explaining a pattern 3 of a basic sequence of operations between a calling device, a calling fixed IMS network, and a called mobile IMS network when a data communication-only terminal actually exists as a called device. [Figure 24] FIG. 11 is a diagram illustrating a basic sequence pattern 4 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a data communication-only terminal actually exists as a called device. [Diagram 25] FIG. 11 is a diagram illustrating a basic sequence pattern 5 of an operation between a calling device, a calling fixed IMS network, and a called mobile IMS network when a data communication-only terminal actually exists as a called device. [Figure 26] FIG. 10 is a diagram for explaining a first operation sequence in the case where a data communication-only terminal actually exists as the IMS terminal to be investigated. [Figure 27] FIG. 11 is a diagram for explaining the second operation sequence in the case where a data communication-only terminal actually exists as the IMS terminal to be investigated. [Figure 28] FIG. 11 is a diagram for explaining the third basic sequence in the case where a data communication-only terminal actually exists as the IMS terminal to be investigated. [Figure 29] FIG. 4 is a diagram for explaining the fourth basic sequence in the case where a data communication-only terminal actually exists as the IMS terminal to be investigated. [Diagram 30] FIG. 5 is a diagram for explaining the fifth basic sequence in the case where a data communication-only terminal actually exists as the IMS terminal to be investigated. [Diagram 31] FIG. 1 is a diagram showing a method for investigating the usage status of telephone numbers of IMS terminals. [Diagram 32] 1 is a system configuration diagram of a telephone number information providing system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

[0022] (Network connection type) FIG. 1 is a schematic diagram showing a network connection form of a telephone number research device 10 according to an embodiment, as an example of a specific configuration mode of a telephone number research device according to the present invention.

[0023] A telephone number investigation device 10 according to the embodiment is connected to a plurality of mobile phone terminals (specifically, IMS terminals 50a, 50b, 50c) to be investigated, which are connected to a receiving mobile IMS network 30 (specifically, for example, an IP telephone network (VoIP: Voice over Internet Protocol)) via a calling fixed IMS network 20 (specifically, for example, an NGN network). In the explanation of the embodiment, when there is no need to distinguish between the IMS terminals 50a, 50b, 50c for each network (in other words, for each contracted carrier or contracted business), they will simply be referred to as "IMS terminals 50."

[0024] The originating fixed IMS network 20 includes a SIP server 20a, which manages and controls the operation of the originating fixed IMS network 20. The terminating mobile IMS network 30 includes SIP servers 30a, 30b, and 30c, which manage and control the operation of the terminating mobile IMS network 30.

[0025] The terminating mobile IMS network 30 is constructed for each telecommunications carrier (in the example shown in FIG. 1, carrier A, carrier B, and carrier C), and IMS terminals 50a, 50b, and 50c are connected to each network (in other words, for each contracted carrier or contracted business) via SIP servers 30a, 30b, and 30c managed and operated by each of the networks.

[0026] The terminating mobile IMS network 30 supports at least the IP (Internet Protocol) v4 network protocol (in other words, the Internet Protocol, IP version) for SDP (Session Description Protocol) parameters, supports audio as the media type, supports RTP / AVP as the media transport protocol, and requires G.711 μ-law as the audio codec.

[0027] Assume that the IMS terminal 50 is a mobile phone (mobile terminal) having a 0A0 type (specifically, for example, 090, 080, and 070) telephone number or a terminal dedicated to data communication, and is connected to the terminating mobile IMS network 30, which is the network on the receiving side.

[0028] In the configuration shown in Fig. 1, the telephone number investigation device 10, which is a calling device, dials the telephone numbers of the IMS terminals 50a, 50b, and 50c connected to the called mobile IMS network 30 as the telephone numbers of the called telephone terminals, and routing is performed in the order of the SIP server 20a in the calling fixed IMS network 20, the calling IBCF (Inter-connection Border Control Function) 21, the called IBCF 31, the SIP servers 30a, 30b, and 30c, and the called IMS terminals 50a, 50b, and 50c. In the telephone number investigation method according to the present invention, as described below, the telephone number investigation device 10, which is a calling device, sets the calling number to be withheld (specifically, adds the number "184" before the telephone number of the called party), and transmits the telephone number.

[0029] At this time, a UNI connection is ensured between the telephone number research device 10 and the originating fixed IMS network 20, and the inter-operator interconnection between the originating fixed IMS network 20 and the terminating mobile IMS network 30 is ensured as an IMS interconnection via an IMS interconnection interface (specifically, the originating IBCF 21 and the terminating IBS 31), etc., and a specific SIP message (details will be described later) sent from the telephone number research device 10 in accordance with the SIP signaling method reaches the terminating mobile IMS network 30.

[0030] In the example shown in Figure 1, the NNI (Network-Network Interface), which is a common interface for interconnection between IMS operators via IP-IP connections, is specified in the TTC standard JJ-90.30 (TTC: Telecommunication Technology Committee; a general incorporated association).

[0031] According to SIP, in order to carry out real-time communication, it is necessary for terminals to negotiate the encoding method of packets containing media information and the addresses of packet destinations, etc. A description language called SDP (Session Description Protocol) is required for this negotiation, and is defined in the TTC standard RFC4566.

[0032] To establish a session using SIP, the calling party first sends a request that describes media information in a SIP message, and the called party then replies with a response in which it selects supported media from that request, thereby sharing the media information to be used for communication between the calling party and the called party.

[0033] Sending a SIP message with media information to start a session is called an offer, and returning compatible media information in response is called an answer. This offer / answer model is defined in the TTC standard RFC3264. Furthermore, the SDP media negotiation procedure in IMS is specified in the TTC standard JJ-90.26.

[0034] In the example shown in FIG. 1, when the telephone number research device 10 sends an SDP offer (called an "INVITE request") of an INVITE method to the IMS terminal 50 to be researched via the originating fixed IMS network 20 (including SIP server 20a) and the terminating mobile IMS network 30 (including SIP servers 30a, 30b, and 30c), the device adds (in other words, writes) a predetermined SDP parameter (called an "SDP parameter for determination") to the SDP offer and transmits it.

[0035] The SDP parameters for determination that are added to the SDP parameters when an INVITE request is sent are the network protocol (in other words, the Internet Protocol, IP version), the media type, the media transport protocol, and the audio codec.

[0036] In response to the INVITE request, the IMS terminal 50 on the receiving side compares the SDP parameters included in the INVITE request with the SDP parameters that it can use, and depending on the result of the comparison (i.e., whether the SDP parameters match or mismatch), returns a response with a specified code in the SIP session as a response message.

[0037] Then, the telephone number research device 10 judges whether the called party IMS terminal 50 exists or does not exist (and further, whether the telephone number of the IMS terminal 50 exists or is missing) based on the received response of the predetermined code.

[0038] (Basic sequence) 2 to 12 are diagrams for explaining a basic sequence of operations between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30 when the IMS terminal 50 as the called device is a mobile phone by the INVITE method in IMS interconnection. Note that the basic sequence of operations related to the calling device according to the embodiment (specifically, the telephone number research device 10) and the IMS terminal 50 which is a mobile phone is not limited to the contents shown in Figs. 2 to 12, and may conform to the contents specified in, for example, TTC standard JJ-90.30, TTC standard JJ-90.26, TTC standard JF-IETF-RFC3398, TTC standard TR-1088, TTC standard JT-Q850, and TTC specification TS-1025.

[0039] Communication is carried out between the calling device and the called device (specifically, a mobile phone) connected to the called mobile IMS 30 via the calling fixed IMS network 20, the calling IBCF 21, the called IBCF 31, and the called mobile IMS network 30.

[0040] (In the real world / Pattern 1) FIG. 2 is a diagram explaining a basic sequence pattern 1 of an operation by the INVITE method in IMS interconnection between a calling device, an originating fixed IMS network 20, and a terminating mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0041] Fig. 2 is a diagram for explaining a basic sequence when the setting to reject incoming calls is not made, particularly when the caller has set the phone number to be withheld. Here, the setting to reject incoming calls can be made by using a service provided by a carrier (communications operator) (referred to as a "withheld call rejection service") or by using a function provided in the IMS terminal 50 main body (referred to as a "withheld call rejection function"). Fig. 2 is a diagram for explaining a basic sequence when the withheld call rejection service and withheld call rejection function are not set.

[0042] The calling device sends an INVITE request to the called device via the calling fixed IMS network 20 and then via the called mobile IMS network 30, such as a mobile phone network of the contracted carrier of the called device (F1). In response to this, the calling fixed IMS network 20 sends an INVITE request to the called mobile IMS network 30 (F2).

[0043] In response to this, the terminating mobile IMS network 30 returns a code 100 Trying response to the originating fixed IMS network 20 indicating that the request has been accepted in the SIP session (F3), and in response to this, the originating fixed IMS network 20 returns a code 100 Trying response to the calling device (F4).

[0044] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), and in response, a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the calling device (F6).

[0045] At this time, the call bell of the receiving device (specifically, a mobile phone) rings, and an RBT (Ringing Back Tone) is transmitted as an RTP (Real time Transport Protocol) from the receiving mobile IMS network 30 to the calling device via the originating fixed IMS network 20 (F7).

[0046] Next, a code 200 OK response is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F8), indicating that the request (specifically, the INVITE request and confirmation of SDP information) has been successfully processed in the SIP session. In response to this, a code 200 OK response is returned from the originating fixed IMS network 20 to the calling device (F9).

[0047] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, the calling fixed IMS network 20 returns an ACK response to the called mobile IMS network 30 (F11). Then, a session is established between the calling device and the called device, and communication (a call) is started.

[0048] After that, (in the example shown in FIG. 2, when the calling device disconnects the communication) a BYE request indicating the termination of the SIP session is sent from the calling device to the calling fixed IMS network 20 (F12), and in response to this, a BYE request is sent from the calling fixed IMS network 20 to the terminating mobile IMS network 30 (F13).

[0049] In response to this (in the example shown in FIG. 2), the terminating mobile IMS network 30 returns a code 200 OK response to the originating fixed IMS network 20 indicating that the request (specifically, the BYE request) has been normally processed in the SIP session (F14), and in response to this, the originating fixed IMS network 20 returns a code 200 OK response to the calling device (F15). This ends the session between the calling device and the called device, i.e., the communication (call) between the calling device and the called device is disconnected.

[0050] (In the real case / Pattern 2) FIG. 3 is a diagram explaining a basic sequence pattern 2 of an operation by the INVITE method in IMS interconnection between a calling device, an originating fixed IMS network 20, and a terminating mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0051] Fig. 3 is a diagram for explaining a basic sequence in a case where the anonymous call rejection service and anonymous call rejection function are not set, similarly to Fig. 2. Note that the basic sequence pattern 1 shown in Fig. 2 and the basic sequence pattern 2 shown in Fig. 3 may differ depending on the contracted carrier of the IMS terminal 50, for example, and the contents are different due to this.

[0052] The operations F1 to F7 in pattern 2 of the basic sequence shown in FIG. 3 are similar to the operations F1 to F7 in pattern 1 of the basic sequence shown in FIG.

[0053] In pattern 2 of the basic sequence shown in Figure 3, an RBT (Ringing Back Tone) is transmitted as an RTP (Real time Transport Protocol) from the terminating mobile IMS network 30 to the calling device via the originating fixed IMS network 20 (F7), and a code 180 Ringing response indicating that a ringtone is ringing in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F8). In response to this, a code 180 Ringing response is returned from the originating fixed IMS network 20 to the calling device (F9).

[0054] In the basic sequence pattern 2 shown in Fig. 3, the operations of F10 to F17 after the code 180 Ringing response is returned (F8, F9) are the same as the operations of F8 to F15 in the basic sequence pattern 1 shown in Fig. 2. Then, the session between the calling device and the called device is ended, that is, the communication (call) between the calling device and the called device is disconnected.

[0055] (In the real world / Pattern 3) FIG. 4 is a diagram illustrating a basic sequence pattern 3 of an operation according to the INVITE method in IMS interconnection between a calling device, an originating fixed IMS network 20, and a terminating mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0056] FIG. 4 is a diagram illustrating the basic sequence in which (at least) the anonymous call rejection service is set for the receiving device (i.e., mobile phone) and the calling device is set to anonymous caller number (specifically, by adding the number "184" before the called device's telephone number) and makes a call.

[0057] The operations F1 to F6 in pattern 3 of the basic sequence shown in FIG. 4 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0058] In the basic sequence pattern 3 shown in Fig. 4, the terminating mobile IMS network 30 returns a code 183 Session Progress response to the calling device via the originating fixed IMS network 20 (F5, F6), and also sends an incoming call rejection guidance as RTP (Real time Transport Protocol) (F7) to inform the caller that the call has been rejected because the caller has set their phone number to be withheld. At this time, the calling device does not ring (because the call has been rejected), and no call history is left on the called device.

[0059] Next, a code 200 OK response is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F8) indicating that the request (specifically, the INVITE request and confirmation of SDP information) has been successfully processed in the SIP session (however, the incoming call is actually rejected), and in response, a code 200 OK response is returned from the originating fixed IMS network 20 to the calling device (F9).

[0060] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F11).

[0061] Thereafter, (when the calling device receives the incoming call rejection guidance and disconnects the communication), a BYE request indicating the termination of the SIP session is sent from the calling device to the calling fixed IMS network 20 (F12), and in response, a BYE request is sent from the calling fixed IMS network 20 to the called mobile IMS network 30 (F13).

[0062] In response to this, the terminating mobile IMS network 30 returns a code 200 OK response to the originating fixed IMS network 20, indicating that the request (specifically, the BYE request) has been normally processed in the SIP session (F14), and in response to this, the originating fixed IMS network 20 returns a code 200 OK response to the calling device (F15). This ends the session between the calling device and the called device, i.e., the communication (call) between the calling device and the called device is disconnected.

[0063] (In the real case / Pattern 4) FIG. 5 is a diagram illustrating a basic sequence pattern 4 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0064] Fig. 5 is a diagram for explaining a basic sequence in a case where (at least) the anonymous call rejection service is set for the device on the receiving side (i.e., the mobile phone) and then the device on the sending side sets the caller number to anonymous (specifically, adds the number "184" before the telephone number of the receiving side, which is the destination) and sends the call. Note that the basic sequence pattern 3 shown in Fig. 4 and the basic sequence pattern 4 shown in Fig. 5 may differ depending on, for example, the contract carrier of the IMS terminal 50, and the contents are different due to this.

[0065] The operations F1 to F6 in pattern 4 of the basic sequence shown in FIG. 5 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0066] In the basic sequence pattern 4 shown in Fig. 5, the terminating mobile IMS network 30 returns a code 183 Session Progress response to the calling device via the originating fixed IMS network 20 (F5, F6), and also sends an incoming call rejection guidance as RTP (Real time Transport Protocol) (F7) to inform the caller that the call has been rejected because the caller has set their phone number to be withheld. At this time, the calling device does not ring (because the call has been rejected), and no call history is left on the called device.

[0067] Next, the terminating mobile IMS network 30 returns a code 433 Anonymity Disallowed response to the originating fixed IMS network 20, indicating that anonymity is not permitted at the terminating device in the SIP session (F8), and in response, the originating fixed IMS network 20 returns a code 433 Anonymity Disallowed response to the originating device (F9).

[0068] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F11).

[0069] Then, the session related to the INVITE request from the calling device is terminated.

[0070] (In the real case / Pattern 5) FIG. 6 is a diagram illustrating a basic sequence pattern 5 of an operation according to the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0071] FIG. 6 is a diagram illustrating the basic sequence when the receiving device (i.e., a mobile phone) is set with an anonymous call rejection function (and the anonymous call rejection service is not set), and the calling device is set to anonymous caller ID (specifically, by adding the number "184" before the called party's telephone number) and makes a call.

[0072] The operations F1 to F6 in pattern 5 of the basic sequence shown in FIG. 6 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0073] 6, the terminating mobile IMS network 30 returns a code 183 Session Progress response to the calling device via the originating fixed IMS network 20 (F5, F6), and also transmits an RBT (Ringing Back Tone) as an RTP (Real time Transport Protocol) (F7). At this time, the calling device does not ring (because the call has been rejected), and the called device retains a call history.

[0074] Next, the terminating mobile IMS network 30 returns a code 403 Forbidden response to the originating fixed IMS network 20, indicating that access to the media resource requested by the originating side in the SIP session (i.e., the terminating side's equipment) is prohibited (F8). In response to this, the originating fixed IMS network 20 returns a code 403 Forbidden response to the originating side's equipment (F9).

[0075] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F11).

[0076] Then, the session related to the INVITE request from the calling device is terminated.

[0077] (In the real case / Pattern 6) FIG. 7 is a diagram illustrating a basic sequence pattern 6 of an operation by the INVITE method in IMS interconnection between a calling device, an originating fixed IMS network 20, and a terminating mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0078] Fig. 7 is a diagram for explaining a basic sequence in a case where the anonymous call rejection function is set for the receiving device (i.e., mobile phone) (and the anonymous call rejection service is not set), and the calling device sets the calling number to anonymous (specifically, adds the number "184" before the called phone number) and makes a call. Note that the basic sequence patterns 5 to 8 shown in Figs. 6 to 9 may differ depending on the contracted carrier of the IMS terminal 50, for example, and the contents of the patterns differ from one another due to this.

[0079] The operations F1 to F6 in pattern 6 of the basic sequence shown in FIG. 7 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0080] In pattern 6 of the basic sequence shown in Figure 7, after a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the originating device (F6), a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F7), and in response to this, a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the originating device (F8).

[0081] Furthermore, silence data is transmitted as RTP (Real time Transport Protocol) from the terminating mobile IMS network 30 to the calling device via the originating fixed IMS network 20 (F9). At this time, the calling device does not ring (because the call has been rejected), and the called device retains a call history.

[0082] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F10), and in response, a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the calling device (F11).

[0083] Next, the terminating mobile IMS network 30 returns a code 603 Decline response to the originating fixed IMS network 20, indicating that the terminating device has rejected the SIP session (F12), and in response, the originating fixed IMS network 20 returns a code 603 Decline response to the originating device (F13).

[0084] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F14), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F15).

[0085] Then, the session related to the INVITE request from the calling device is terminated.

[0086] (In the real case / Pattern 7) FIG. 8 is a diagram illustrating a basic sequence pattern 7 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0087] Fig. 8 is a diagram for explaining a basic sequence in a case where the anonymous call rejection function is set for the receiving device (i.e., mobile phone) (and the anonymous call rejection service is not set), and the calling device sets the calling number to anonymous (specifically, adds the number "184" before the called party's telephone number) and makes a call. Note that the basic sequence patterns 5 to 8 shown in Figs. 6 to 9 may differ depending on the contracted carrier of the IMS terminal 50, for example, and therefore the contents are different from each other.

[0088] The operations F1 to F4 in pattern 7 of the basic sequence shown in FIG. 8 are similar to the operations F1 to F4 in pattern 1 of the basic sequence shown in FIG.

[0089] 8, in pattern 7 of the basic sequence shown in FIG. 8, after a code 100 Trying response is sent from the originating fixed IMS network 20 to the originating device (F4), a code 486 Busy Here response is sent from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), indicating that the media resource requested by the originating device in the SIP session is currently busy and the session cannot be started, and in response to this, a code 486 Busy Here response is sent from the originating fixed IMS network 20 to the originating device (F6). At this time, the calling device does not ring (because the incoming call has been rejected).

[0090] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F7), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F8).

[0091] Then, the session related to the INVITE request from the calling device is terminated.

[0092] (In the real case / Pattern 8) FIG. 9 is a diagram illustrating a basic sequence pattern 8 of an operation according to the INVITE method in IMS interconnection between a calling device, an originating fixed IMS network 20, and a terminating mobile IMS network 30, when a mobile phone is actually present as the called device and is not busy, and the calling device disconnects communication.

[0093] Fig. 9 is a diagram for explaining a basic sequence in a case where the anonymous call rejection function is set for the receiving device (i.e., mobile phone) (the anonymous call rejection service is not set), and the calling device sets the calling number to anonymous (specifically, adds the number "184" before the called phone number) and makes a call. Note that the basic sequence patterns 5 to 8 shown in Figs. 6 to 9 may differ depending on the contracted carrier of the IMS terminal 50, for example, and the contents of the patterns differ from one another due to this.

[0094] The operations F1 to F6 in pattern 8 of the basic sequence shown in FIG. 9 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0095] 9, the terminating mobile IMS network 30 returns a code 183 Session Progress response to the calling device via the originating fixed IMS network 20 (F5, F6), and transmits silent data or a busy tone indicating that the called device is busy as RTP (Real time Transport Protocol) (F7). At this time, the calling device does not ring (because the call has been rejected).

[0096] Next, a code 180 Ringing response indicating that an incoming call is ringing in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F8), and in response, a code 180 Ringing response is returned from the originating fixed IMS network 20 to the calling device (F9).

[0097] Next, the terminating mobile IMS network 30 returns a code 486 Busy Here response to the originating fixed IMS network 20 (F10), indicating that the media resource requested by the originating side in the SIP session is currently busy and the session cannot be started, and in response, the originating fixed IMS network 20 returns a code 486 Busy Here response to the originating side's equipment (F11).

[0098] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F12), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F13).

[0099] Then, the session related to the INVITE request from the calling device is terminated.

[0100] Note that the operations of F10 to F13 in pattern 8 of the basic sequence shown in FIG. 9 may differ from the contents (operations) shown in FIG. 9, but this does not affect the configuration of the present invention (specifically, the operation sequence related to determining the usage status of a telephone number).

[0101] (If busy / Part 1) 10 is a diagram for explaining a basic sequence pattern 1 of an operation by the INVITE method in IMS interconnection when a mobile phone is actually present and busy as a called device among a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30. This basic sequence is defined in the TTC standard TR-1088.

[0102] The calling device sends an INVITE request to the called device via the calling fixed IMS network 20 and then via the called mobile IMS network 30, such as a mobile phone network of the contracted carrier of the called device (F1). In response to this, the calling fixed IMS network 20 sends an INVITE request to the called mobile IMS network 30 (F2).

[0103] In response to this, the terminating mobile IMS network 30 returns a code 100 Trying response to the originating fixed IMS network 20 indicating that the request has been accepted in the SIP session (F3), and in response to this, the originating fixed IMS network 20 returns a code 100 Trying response to the calling device (F4).

[0104] Next, the terminating mobile IMS network 30 returns a code 486 Busy Here response to the originating fixed IMS network 20 (F5), indicating that the media resource requested by the originating side in the SIP session is currently busy and the session cannot be started. In response to this, the originating fixed IMS network 20 returns a 486 Busy Here response to the originating side's equipment (F6).

[0105] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F7), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F8). This ends the session related to the INVITE request from the calling device.

[0106] (If the phone is busy / Part 2) Fig. 11 is a diagram for explaining pattern 2 of a basic sequence of an operation by the INVITE method in IMS interconnection when a mobile phone is actually present and busy as a receiving device between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30. Note that the basic sequence pattern 1 shown in Fig. 10 and the basic sequence pattern 2 shown in Fig. 11 may differ depending on, for example, the contracted carrier of the IMS terminal 50, and the contents thereof are different due to this.

[0107] The calling device sends an INVITE request to the called device via the calling fixed IMS network 20 and then via the called mobile IMS network 30, such as a mobile phone network of the contracted carrier of the called device (F1). In response to this, the calling fixed IMS network 20 sends an INVITE request to the called mobile IMS network 30 (F2).

[0108] In response to this, the terminating mobile IMS network 30 returns a code 100 Trying response to the originating fixed IMS network 20 indicating that the request has been accepted in the SIP session (F3), and in response to this, the originating fixed IMS network 20 returns a code 100 Trying response to the calling device (F4).

[0109] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), and in response, a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the calling device (F6).

[0110] Furthermore, a busy tone indicating that the receiving device is busy is sent as RTP (Real time Transport Protocol) from the receiving mobile IMS network 30 to the calling device via the originating fixed IMS network 20 (F7).

[0111] Next, the terminating mobile IMS network 30 returns a code 487 Request Terminated response to the originating fixed IMS network 20, indicating the termination of the request in the SIP session (in other words, the end of the session) (F8), and in response, the originating fixed IMS network 20 returns a code 487 Request Terminated response to the calling device (F9).

[0112] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, the calling fixed IMS network 20 returns an ACK response to the called mobile IMS network 30 (F11). This ends the session related to the INVITE request from the calling device.

[0113] (In case of missing number) 12 is a diagram explaining a basic sequence of operations in IMS interconnection by the INVITE method when the called device (in other words, the telephone number) is a missing number between the calling device, the calling fixed IMS network 20, and the called mobile IMS network 30. This basic sequence is defined in the TTC standard TR-1088.

[0114] The calling device sends an INVITE request to the called device via the calling fixed IMS network 20 and then via the called mobile IMS network 30, such as a mobile phone network of the contracted carrier of the called device (F1). In response to this, the calling fixed IMS network 20 sends an INVITE request to the called mobile IMS network 30 (F2).

[0115] In response to this, the terminating mobile IMS network 30 returns a code 100 Trying response to the originating fixed IMS network 20 indicating that the request has been accepted in the SIP session (F3), and in response to this, the originating fixed IMS network 20 returns a code 100 Trying response to the calling device (F4).

[0116] Next, the terminating mobile IMS network 30 returns a code 404 Not Found response to the originating fixed IMS network 20, indicating that the media resource requested by the originating side in the SIP session cannot be found (F5), and in response, the originating fixed IMS network 20 returns a 404 Not Found response to the originating side's equipment (F6).

[0117] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F7), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F8). This ends the session related to the INVITE request from the calling device.

[0118] (Phone number investigation device) FIG. 13 is a block diagram showing a configuration of a telephone number research device 10 according to an embodiment.

[0119] The telephone number investigation device 10 of the embodiment is connected to a plurality of IMS terminals 50 connected to a terminating mobile IMS network 30 via an originating fixed IMS network 20, and sends an INVITE request to the originating fixed IMS network 20 (toward the IMS terminal 50 to be investigated) by adding SDP parameters to the INVITE request for the IMS terminal 50 to be investigated, and receives a response message via the originating fixed IMS network 20, and determines the usage status of the telephone number of the IMS terminal 50 to be investigated based on the response message.

[0120] The telephone number research device 10 includes a network interface unit 11, a message exchange control unit 12, a telephone number research determination unit 13, a telephone number history generation unit 14, and a telephone number history database (DB) 15.

[0121] The network interface unit 11 functions as a communication interface for the telephone number research device 10 to carry out communication in accordance with the SIP protocol.

[0122] The message exchange control unit 12 sends an INVITE request including SDP parameters for determination to the IMS terminal 50 being investigated, and also receives a message (e.g., a response with a specified code in a SIP session) from the terminating mobile IMS network 30 (including SIP servers 30a, 30b, and 30c).

[0123] The telephone number investigation determination unit 13 determines whether or not the IMS terminal 50 being investigated on the receiving side actually exists, depending on the message received via the message exchange control unit 12 (for example, a response with a specified code in a SIP session), and ultimately determines the validity of the telephone number of the IMS terminal 50 being investigated (in other words, the usage status of the telephone number).

[0124] The telephone number history generating unit 14 constructs a telephone number history database 15 by adding a time stamp indicating the date and time of judgment to each judgment result in the telephone number investigation judgment unit 13 and recording them in chronological order on a recording medium.

[0125] Although the data structure of the telephone number history database 15 (in other words, the recorded data items) is not limited to a specific structure or items, the telephone number history information stored in the telephone number history database 15 may include, for example, a combination of the “telephone number” to be investigated for each investigation (in other words, each time an INVITE request is sent), the “error code” returned from the terminating mobile IMS network 30, the “investigation date” (i.e., a timestamp), the “existent / missing number determination result”, and “other layer information” regarding the layer returned from the terminating mobile IMS network 30.

[0126] In addition to the data items mentioned above, the telephone number history information stored in the telephone number history database 15 may also include, for example, the type of IMS terminal 50 being investigated (specifically, a mobile phone or a data communication-only terminal), the "new subscriber number" which is the transfer destination or contact telephone number identified during the investigation, the "corporate name / individual name" which owns the telephone number, "attribute information" such as address and age, "map link information," and "credit information" for evaluating credit.

[0127] Then, for example, when the telephone number investigation device 10 investigates the usage of the telephone number "090-XXXX-XXXX", the investigation information is recorded sequentially in the telephone number history database 15 for each determination made by the telephone number investigation determination unit 13, and is accumulated and stored as history information.

[0128] The telephone number history database 15 may be implemented in a large-capacity recording medium, such as a semiconductor memory, a hard disk, or an optical memory such as a DVD (Digital Versatile Disc).

[0129] The telephone number research device 10 is configured to include a microprocessor having built-in memory (not shown) in which a predetermined program (including the telephone number research program of the embodiment) is recorded, or a microprocessor to which an external memory (not shown) in which a predetermined program is recorded, and an LSI (Large Scale Integration) that performs peripheral control including communication control.

[0130] The microprocessor sequentially reads out and executes predetermined programs (including the telephone number research program of the embodiment) recorded in a memory (not shown), thereby configuring the network interface unit 11, the message exchange control unit 12, the telephone number research determination unit 13, and the telephone number history generation unit 14, and realizing the predetermined functions of the telephone number research device 10.

[0131] (How to research phone numbers) As an example of a specific configuration of the telephone number investigation method according to the present invention, the telephone number investigation method according to the embodiment is a method of investigating the usage status of the telephone number of the IMS terminal 50 to be investigated by using a computer (specifically, a telephone number investigation device 10) connected to a plurality of IMS terminals 50 connected to the terminating mobile IMS network 30 via the originating fixed IMS network 20, and includes the steps of adding an SDP parameter to the INVITE request for the IMS terminal 50 to be investigated and transmitting the INVITE request to the originating fixed IMS network 20 (to the IMS terminal 50 to be investigated), receiving a response message via the originating fixed IMS network 20, and determining the usage status of the telephone number of the IMS terminal 50 to be investigated according to the response message, in which the SDP parameters are described as the network protocol being IPv4, the media type being only audio, the media transport protocol being only RTP / AVP, and the voice codec including G.711 μ-law and G.722.

[0132] Here, in the telephone number investigation method according to the present invention, the calling device (specifically, the telephone number investigation device 10) sets the telephone number to be withheld (specifically, adds "184" to the called telephone number) and transmits the telephone number of the IMS terminal 50 to be investigated. This makes it possible to prevent the ringer of the IMS terminal 50 to be investigated from ringing when at least one of the withheld call rejection service and withheld call rejection function is set in the investigation of the usage status of the telephone number of the IMS terminal.

[0133] The telephone number research method described below can be implemented, for example, by executing a telephone number research program in a computer (specifically, telephone number research device 10) and executing each corresponding procedure in accordance with the program.

[0134] As SDP parameters, among the determination SDP parameters, IPv4 is described (in other words, used) for the network protocol (in other words, Internet Protocol, IP version) and offered, and other determination SDP parameters are described as follows. The following description of the determination SDP parameters is referred to as "SDP for IPv4". Media type: audio only Media transport protocol: RTP / AVP only ○ Audio Codecs: Includes G.711 μ-law and G.722

[0135] (Reality test / part 1) FIG. 14 is a diagram illustrating a first operation sequence when an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for judgment, and a mobile phone actually exists as the IMS terminal 50 to be investigated but is not busy.

[0136] Fig. 14 is a diagram for explaining the operation sequence in the case where the setting to reject incoming calls is not made when the caller sets the phone number to be withheld, i.e., Fig. 14 is a diagram for explaining the operation sequence in the case where the anonymous call rejection service and anonymous call rejection function are not set.

[0137] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as the mobile telephone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0138] In response to this, a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4).

[0139] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6).

[0140] At this time, the call bell of the IMS terminal 50 being investigated on the receiving side rings, and an RBT (Ringing Back Tone) is sent as an RTP (Real time Transport Protocol) from the receiving mobile IMS network 30 to the telephone number investigation device 10 (specifically, the message exchange control unit 12) via the calling fixed IMS network 20 (F7).

[0141] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0142] Next, the message exchange control unit 12 of the telephone number researching device 10 transmits a CANCEL request, which is an instruction to terminate the SIP session, to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F8, F9).

[0143] That is, when the message exchange control unit 12 of the telephone number research device 10 receives the code 183 Session Progress response, it immediately (more specifically, almost simultaneously with receiving the code 183 Session Progress response) transmits a CANCEL request in order to stop the ringing of the call bell of the IMS terminal 50 being researched on the called side. As a result, the ringing of the call bell of the IMS terminal 50 being researched on the called side stops in an extremely short time.

[0144] Here, in the basic sequence of operations, for example, pattern 1 and pattern 2 (i.e., the basic sequence when the anonymous call rejection service and anonymous call rejection function are not set; see Figs. 2 and 3) between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30 by the INVITE method in IMS interconnection, when a mobile phone is actually present as a called device and is not busy, a normal sequence is an operation in which a code 183 Session Progress response (F5, F6) is returned in response to an INVITE request (F1, F2) from the calling device. However, depending on the contracted carrier of the IMS terminal 50, an irregular case may be considered in which a code 180 Ringing response is returned without a code 183 Session Progress response being returned. Therefore, even if the telephone number investigation determination unit 13 of the telephone number investigation device 10 receives a code 180 Ringing response without receiving a code 183 Session Progress response (F5, F6), it determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (i.e., the telephone number of the IMS terminal 50 to be investigated actually exists).Then, the message exchange control unit 12 of the telephone number investigation device 10 transmits a CANCEL request, which is an instruction to end the session in the SIP session, to the receiving mobile IMS network 30 via the calling fixed IMS network 20.

[0145] That is, when the telephone number investigation determination unit 13 of the telephone number investigation device 10 receives a code 183 Session Progress response or a code 180 Ringing response in response to the INVITE request, it determines that a mobile phone exists as the IMS terminal 50 to be investigated on the called side (that is, the telephone number of the IMS terminal 50 to be investigated exists). Then, the message exchange control unit 12 of the telephone number investigation device 10 transmits a CANCEL request. That is, when the message exchange control unit 12 of the telephone number investigation device 10 receives a code 18X response, it transmits a CANCEL request, thereby quickly stopping the ringing of the call bell of the called side device (that is, the mobile phone as the IMS terminal 50 to be investigated) if the anonymous call rejection service and anonymous call rejection function are not set for the IMS terminal 50 to be investigated on the called side (specifically, the mobile phone).

[0146] In response to a CANCEL request from the calling device (specifically, the telephone number research device 10), a code 200 OK response indicating that the request (specifically, the CANCEL request) has been successfully processed in the SIP session is returned from the called mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the calling fixed IMS network 20 (F10, F11), and a code 487 Request Terminated response indicating the cancellation of the request (in other words, the end of the session) is returned in the SIP session (F12, F13).

[0147] In response to this, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F14, F15). This ends the session between the telephone number researching device 10 and the terminating IMS terminal 50 to be investigated.

[0148] (Reality test / part 2) FIG. 15 is a diagram illustrating a second operation sequence when an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a mobile phone actually exists as the IMS terminal 50 to be investigated but is not busy.

[0149] FIG. 15 is a diagram for explaining an operation sequence in a case where at least one of the anonymous call rejection service and anonymous call rejection function is set.

[0150] The operations F1 to F6 in the second operation sequence shown in Fig. 15 are the same as the operations F1 to F6 in the first operation sequence shown in Fig. 14. Note that, as an SDP parameter included in the INVITE request, the above SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0151] 15, the terminating mobile IMS network 30 returns a code 183 Session Progress response to the telephone number researching device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6), and also sends an incoming call rejection guidance or an RBT (Ringing Back Tone) as RTP (Real time Transport Protocol) to inform the caller that the call has been rejected because the caller has set the telephone number to be withheld (F7). At this time, the call bell does not ring on the terminating IMS terminal 50 to be investigated (because the call has been rejected).

[0152] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0153] The operations from F8 to F15 in the operation sequence part 2 shown in Fig. 15 are the same as the operations from F8 to F15 in the operation sequence part 1 shown in Fig. 14. However, since the call bell of the IMS terminal 50 to be investigated on the called side is not ringing to begin with, the call bell of the IMS terminal 50 to be investigated on the called side does not stop ringing by transmitting the CANCEL request. Then, the session between the telephone number research device 10 and the IMS terminal 50 to be investigated on the called side is terminated.

[0154] (Reality test / part 3) FIG. 16 is a diagram illustrating the third operation sequence when an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and when a mobile phone actually exists as the IMS terminal 50 to be investigated but is not busy.

[0155] FIG. 16 is a diagram for explaining the operation sequence in the case where the anonymous call rejection function is set (however, the anonymous call rejection service is not set).

[0156] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as the mobile telephone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0157] In response to this, a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4).

[0158] Next, a code 486 Busy Here response indicating that the media resource requested by the calling side in the SIP session is currently busy and the session cannot be started is returned to the telephone number research device 10 (specifically, the message exchange control unit 12) from the called side mobile IMS network 30 via the calling side fixed IMS network 20 (F5, F6). At this time, the call bell does not ring on the called side IMS terminal 50 to be researched (because the incoming call has been rejected).

[0159] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0160] Next, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session between the telephone number researching device 10 and the terminating IMS terminal 50 to be investigated.

[0161] (Determining the presence of a line when it is busy / Part 1) FIG. 17 is a diagram illustrating a first operation sequence in which an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for judgment, and a mobile phone actually exists as the IMS terminal 50 to be investigated and is in use.

[0162] FIG. 17 is a diagram for explaining an operation sequence in the case where the anonymous call rejection service and anonymous call rejection function are not set.

[0163] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as the mobile telephone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0164] In response to this, a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4).

[0165] Next, a code 486 Busy Here response is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20, indicating that the media resource requested by the originating side in the SIP session is currently busy and the session cannot be started (F5, F6).

[0166] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0167] Next, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session between the telephone number researching device 10 and the terminating IMS terminal 50 to be investigated.

[0168] (Determining the presence of a line when it is busy / Part 2) FIG. 18 is a diagram illustrating a second operation sequence in which an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a mobile phone actually exists as the IMS terminal 50 to be investigated and is in use.

[0169] Fig. 18 is a diagram for explaining an operation sequence in the case where the anonymous call rejection service and anonymous call rejection function are not set. Note that the operation sequence 1 shown in Fig. 17 and the operation sequence 2 shown in Fig. 18 may differ depending on the contracted carrier of the IMS terminal 50, for example, and the contents are different due to this.

[0170] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as the mobile telephone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0171] In response to this, a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4).

[0172] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6), and a busy tone indicating that the terminating device (i.e., the IMS terminal 50 being researched) is busy is transmitted as RTP (Real time Transport Protocol) (F7).

[0173] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a mobile phone actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0174] Next, the message exchange control unit 12 of the telephone number researching device 10 transmits a CANCEL request, which is an instruction to terminate the SIP session, to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F8, F9).

[0175] That is, when the message exchange control unit 12 of the telephone number researching device 10 receives the code 183 Session Progress response, it immediately transmits a CANCEL request (more precisely, almost simultaneously with receiving the code 183 Session Progress response).

[0176] In response to a CANCEL request from the calling device (specifically, the telephone number research device 10), a code 200 OK response indicating that the request (specifically, the CANCEL request) has been successfully processed in the SIP session is returned from the called mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the calling fixed IMS network 20 (F10, F11), and a code 487 Request Terminated response indicating the cancellation of the request (in other words, the end of the session) is returned in the SIP session (F12, F13).

[0177] In response to this, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F14, F15). This ends the session between the telephone number researching device 10 and the terminating IMS terminal 50 to be investigated.

[0178] (Missing number determination) FIG. 19 is a diagram illustrating the operation sequence when an offer is made by describing IPv4 as the network protocol as the SDP parameters and the above-mentioned SDP for IPv4 as the judgment SDP parameters, and the IMS terminal 50 to be investigated (in other words, the telephone number) is an unused number.

[0179] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as a mobile phone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0180] In response to this, the receiving mobile IMS network 30 returns a code 100 Trying response indicating that the request has been accepted in the SIP session to the telephone number investigation device 10 (specifically, the message exchange control unit 12) via the calling fixed IMS network 20 (F3, F4).

[0181] Next, a code 404 Not Found response indicating that the media resource requested by the calling side in the SIP session cannot be found is returned from the called mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the called fixed IMS network 20 (F5, F6).

[0182] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that the IMS terminal 50 to be investigated on the called side is an unused number (i.e., the telephone number of the IMS terminal 50 to be investigated is an unused number). Note that an unused number includes a case where the IMS terminal 50 to be investigated on the called side has been cancelled.

[0183] Next, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session related to the INVITE request from the telephone number researching device 10.

[0184] (False positive) 20 is a diagram for explaining an operation sequence when an IMS terminal 50 (in other words, a telephone number) to be investigated is missing, when an offer is made with IPv4 described as the network protocol in the SDP parameters and only G.711 μ-law described as the voice codec in the SDP for IPv4 described as the SDP parameters for determination (in other words, without G.722). The basic sequence on which this operation sequence is based is specified in the TTC standard TR-1088.

[0185] In this case, in response to an INVITE request (F1, F2) from the telephone number research device 10 (specifically, the message exchange control unit 12), a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4), and a code 183 Session Progress response indicating the progress of the call in the SIP session is also returned (F5, F6).

[0186] This response is the same as the operation sequence (part 1, part 2) when a mobile phone actually exists as the IMS terminal 50 to be investigated on the called party (see Figs. 14 and 15).

[0187] As a result, even though the IMS terminal 50 being investigated (in other words, the telephone number) is actually a missing number, the telephone number investigation determination unit 13 of the telephone number investigation device 10 erroneously determines that a mobile phone actually exists as the IMS terminal 50 being investigated on the receiving side (and the message exchange control unit 12 sends a CANCEL request).

[0188] For this reason, when offering an SDP parameter that describes IPv4 as the network protocol among the SDP parameters for determination, the other SDP parameters for determination are described to include G.722 in addition to G.711 μ-law as the audio codec (i.e., offering G.711 μ-law and G.722 simultaneously).

[0189] As a result, as shown in FIG. 19, in response to an INVITE request (F1, F2) from the telephone number researching device 10 (specifically, the message exchange control unit 12), a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number researching device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4), and a code 404 Not Found response indicating that the media resource requested by the calling side cannot be found in the SIP session is returned (F5, F6). This makes it possible to correctly determine that the IMS terminal 50 (in other words, the telephone number) being investigated on the terminating side is a missing number.

[0190] (Data communication only terminal) 21 to 25 are diagrams for explaining a basic sequence of operations between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30 when the IMS terminal 50 as a called device is a data communication-only terminal by the INVITE method in IMS interconnection. Note that the basic sequence of operations related to the calling device according to the embodiment (specifically, the telephone number research device 10) and the IMS terminal 50 which is a data communication-only terminal is not limited to the contents shown in Figs. 21 to 25, and may conform to the contents specified in, for example, TTC standard JJ-90.30, TTC standard JJ-90.26, TTC standard JF-IETF-RFC3398, TTC standard TR-1088, TTC standard JT-Q850, and TTC specification TS-1025.

[0191] Communication is carried out between the calling device and the called device (specifically, a data communication-only terminal) connected to the called mobile IMS network 30 via the calling fixed IMS network 20, the calling IBCF 21, the called IBCF 31, and the called mobile IMS network 30.

[0192] (Basic sequence / pattern 1) FIG. 21 is a diagram explaining a basic sequence pattern 1 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a data communication-only terminal actually exists as a called device.

[0193] The calling device sends an INVITE request to the called device via the calling fixed IMS network 20 and then via the called mobile IMS network 30, such as a mobile phone network of the contracted carrier of the called device (F1). In response to this, the calling fixed IMS network 20 sends an INVITE request to the called mobile IMS network 30 (F2).

[0194] In response to this, the terminating mobile IMS network 30 returns a code 100 Trying response to the originating fixed IMS network 20 indicating that the request has been accepted in the SIP session (F3), and in response to this, the originating fixed IMS network 20 returns a code 100 Trying response to the calling device (F4).

[0195] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), and in response, a code 183 Session Progress response is returned from the originating fixed IMS network 20 to the calling device (F6).

[0196] Furthermore, the terminating mobile IMS network 30 transmits a guidance to the calling device via the originating fixed IMS network 20, indicating that the called device is dedicated to data communication (F7).

[0197] Next, the terminating mobile IMS network 30 returns a code 480 Temporarily Unavailable response to the originating fixed IMS network 20, indicating that the media resource requested by the originating side in the SIP session (i.e., the terminating side's equipment) is temporarily unavailable (F8). In response to this, the originating fixed IMS network 20 returns a code 480 Temporarily Unavailable response to the originating side's equipment (F9).

[0198] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, the calling fixed IMS network 20 returns an ACK response to the called mobile IMS network 30 (F11). This ends the session related to the INVITE request from the calling device.

[0199] (Basic sequence / pattern 2) FIG. 22 is a diagram explaining a basic sequence pattern 2 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a data communication-only terminal actually exists as a called device.

[0200] It should be noted that the basic sequence patterns 1 to 5 shown in FIGS. 21 to 25 may differ depending on, for example, the contracted carrier or contract type of the IMS terminal 50, and as a result, the contents of the patterns differ from one another.

[0201] The operations F1 to F6 in pattern 2 of the basic sequence shown in FIG. 22 are similar to the operations F1 to F6 in pattern 1 of the basic sequence shown in FIG.

[0202] Then, in pattern 2 of the basic sequence shown in Figure 22, following the operation of F6, guidance is sent from the terminating mobile IMS network 30 to the calling device via the originating fixed IMS network 20, indicating that the terminating device cannot be reached (in other words, cannot be connected) (F7).

[0203] Next, the terminating mobile IMS network 30 returns a code 403 Forbidden response to the originating fixed IMS network 20, indicating that access to the media resource (i.e., the terminating device) requested by the originating device in the SIP session is prohibited (F8), and in response, the originating fixed IMS network 20 returns a code 403 Forbidden response to the originating device (F9).

[0204] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F10), and in response to this, the calling fixed IMS network 20 returns an ACK response to the called mobile IMS network 30 (F11). This ends the session related to the INVITE request from the calling device.

[0205] (Basic sequence / pattern 3) FIG. 23 is a diagram explaining a basic sequence pattern 3 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a data communication-only terminal actually exists as a called device.

[0206] The operations F1 to F4 in pattern 3 of the basic sequence shown in FIG. 23 are similar to the operations F1 to F4 in pattern 1 of the basic sequence shown in FIG.

[0207] Then, in pattern 3 of the basic sequence shown in FIG. 23, following the operation of F4, a code 487 Request Terminated response indicating the termination of the request in the SIP session (in other words, the end of the session) is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), and in response to this, a code 487 Request Terminated response is returned from the originating fixed IMS network 20 to the calling device (F6).

[0208] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F7), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F8). This ends the session related to the INVITE request from the calling device.

[0209] (Basic sequence / pattern 4) FIG. 24 is a diagram explaining a basic sequence pattern 4 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a data communication-only terminal actually exists as a called device.

[0210] The operations F1 to F4 in pattern 4 of the basic sequence shown in FIG. 24 are similar to the operations F1 to F4 in pattern 1 of the basic sequence shown in FIG.

[0211] Then, in pattern 4 of the basic sequence shown in FIG. 24, following the operation of F4, a code 500 Server Internal Error response is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20, indicating that an error has occurred inside the server in the SIP session (F5), and in response to this, the originating fixed IMS network 20 returns a 500 Server Internal Error response to the calling device (F6).

[0212] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the originating device to the terminating mobile IMS network 30 (F7), and in response to this, an ACK response is returned from the originating fixed IMS network 20 to the terminating mobile IMS network 30 (F8). This ends the session related to the INVITE request from the originating device.

[0213] (Basic sequence / pattern 5) FIG. 25 is a diagram explaining a basic sequence pattern 5 of an operation by the INVITE method in IMS interconnection between a calling device, a calling fixed IMS network 20, and a called mobile IMS network 30, when a data communication-only terminal actually exists as a called device.

[0214] The operations F1 to F4 in pattern 5 of the basic sequence shown in FIG. 25 are similar to the operations F1 to F4 in pattern 1 of the basic sequence shown in FIG.

[0215] Then, in pattern 5 of the basic sequence shown in FIG. 25, following the operation of F4, a code 488 Not Acceptable Here response indicating that acceptance has been rejected by the terminating device in the SIP session is returned from the terminating mobile IMS network 30 to the originating fixed IMS network 20 (F5), and in response to this, a code 488 Not Acceptable Here response is returned from the originating fixed IMS network 20 to the originating device (F6).

[0216] In response to this, an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session is returned from the calling device to the calling fixed IMS network 20 (F7), and in response to this, an ACK response is returned from the calling fixed IMS network 20 to the called mobile IMS network 30 (F8). This ends the session related to the INVITE request from the calling device.

[0217] (Reality test / part 1) FIG. 26 is a diagram illustrating a first operation sequence in which an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a data communication-only terminal actually exists as the IMS terminal 50 to be investigated.

[0218] The operation sequence shown in Figure 26 is an operation sequence in which the basic sequence of operations between a calling device, the calling fixed IMS network 20, and the called mobile IMS network 30, when a data communication-only terminal actually exists as a called device, follows pattern 1 of the basic sequence shown in Figure 21.

[0219] The message exchange control unit 12 of the telephone number investigation device 10 transmits an INVITE request addressed to the IMS terminal 50 to be investigated via the originating fixed IMS network 20 and the terminating mobile IMS network 30 such as a mobile phone network of the contracted carrier of the IMS terminal 50 to be investigated (F1, F2). At this time, as an SDP parameter included in the INVITE request, the above-mentioned SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0220] In response to this, a code 100 Trying response indicating that the request has been accepted in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F3, F4).

[0221] Next, a code 183 Session Progress response indicating the progress of the call in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6).

[0222] Furthermore, guidance is sent from the terminating mobile IMS network 30 to the originating equipment via the originating fixed IMS network 20, indicating that the terminating equipment (i.e., the IMS terminal 50 being investigated) is for data communication only (F7).

[0223] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a data communication dedicated terminal actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0224] Next, the message exchange control unit 12 of the telephone number researching device 10 transmits a CANCEL request, which is an instruction to terminate the SIP session, to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F8, F9).

[0225] In response to this, the terminating mobile IMS network 30 returns a code 200 OK response to the telephone number researching device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20, indicating that the request (specifically, a CANCEL request here) has been processed normally in the SIP session (F10, F11), and also returns a code 487 Request Terminated response indicating the cancellation of the request (in other words, the end of the session) in the SIP session (F12, F13).

[0226] In response to this, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F14, 15). This ends the session related to the INVITE request from the telephone number researching device 10.

[0227] (Reality test / part 2) FIG. 27 is a diagram illustrating a second operation sequence in which an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a data communication-only terminal actually exists as the IMS terminal 50 to be investigated.

[0228] The operation sequence shown in Figure 27 is an operation sequence in which the basic sequence of operations between a calling device, the calling fixed IMS network 20, and the called mobile IMS network 30, when a data communication-only terminal actually exists as a called device, follows pattern 2 of the basic sequence shown in Figure 22.

[0229] The operations F1 to F6 in the operation sequence part 2 shown in Fig. 27 are the same as the operations F1 to F6 in the operation sequence part 1 shown in Fig. 26. Note that as an SDP parameter included in the INVITE request, the above SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0230] Then, in the second operation sequence shown in FIG. 27, following the operation of F6, a guidance is sent from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20, indicating that the terminating device cannot be connected (in other words, cannot be connected) (F7).

[0231] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a data communication dedicated terminal actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0232] The operations F8 to F15 in the operation sequence part 2 shown in FIG. 27 are similar to the operations F8 to F15 in the operation sequence part 1 shown in FIG.

[0233] Then, the session related to the INVITE request from the telephone number research device 10 ends.

[0234] (Reality test / part 3) FIG. 28 is a diagram explaining the third basic sequence in the case where an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a data communication-only terminal actually exists as the IMS terminal 50 to be investigated.

[0235] The operation sequence shown in Figure 28 is an operation sequence in which the basic sequence of operations between a calling device, the calling fixed IMS network 20, and the called mobile IMS network 30, when a data communication-only terminal actually exists as a called device, follows pattern 3 of the basic sequence shown in Figure 23.

[0236] The operations F1 to F4 in the operation sequence No. 3 shown in Fig. 28 are similar to the operations F1 to F4 in the operation sequence No. 1 shown in Fig. 26. Note that as an SDP parameter included in an INVITE request, the above SDP for IPv4 is described for a determination SDP parameter (note that the network protocol is IPv4).

[0237] Then, in the third operation sequence shown in FIG. 28, following the operation of F4, a code 487 Request Terminated response indicating the termination of the request (in other words, the end of the session) in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6).

[0238] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a data communication dedicated terminal actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0239] Then, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session related to the INVITE request from the telephone number researching device 10.

[0240] (Reality test / part 4) FIG. 29 is a diagram explaining the fourth basic sequence in the case where an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and a data communication-only terminal actually exists as the IMS terminal 50 to be investigated.

[0241] The operation sequence shown in Figure 29 is an operation sequence in which the basic sequence of operations between a calling device, the calling fixed IMS network 20, and the called mobile IMS network 30, when a data communication-only terminal actually exists as a called device, follows pattern 4 of the basic sequence shown in Figure 24.

[0242] The operations F1 to F4 in the operation sequence No. 4 shown in Fig. 29 are similar to the operations F1 to F4 in the operation sequence No. 1 shown in Fig. 26. Note that as an SDP parameter included in an INVITE request, the above SDP for IPv4 is described for a determination SDP parameter (note that the network protocol is IPv4).

[0243] Then, in part 4 of the operation sequence shown in Figure 29, following the operation of F4, a code 500 Server Internal Error response indicating that an error has occurred inside the server in the SIP session is returned from the terminating mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6).

[0244] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a data communication dedicated terminal actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0245] Then, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session related to the INVITE request from the telephone number researching device 10.

[0246] (Reality test / part 5) Figure 30 is a diagram explaining the fifth basic sequence when an offer is made by describing IPv4 as the network protocol as the SDP parameters and describing the above-mentioned SDP for IPv4 as the SDP parameters for determination, and when a data communication-only terminal actually exists as the IMS terminal 50 to be investigated.

[0247] The operation sequence shown in Figure 30 is an operation sequence in which the basic sequence of operations between a calling device, an originating fixed IMS network 20, and a called mobile IMS network 30 when a data communication-only terminal actually exists as a called device follows pattern 5 of the basic sequence shown in Figure 25.

[0248] The operations F1 to F4 in the operation sequence No. 5 shown in Fig. 30 are the same as the operations F1 to F4 in the operation sequence No. 1 shown in Fig. 26. Note that, as an SDP parameter included in the INVITE request, the above SDP for IPv4 is described for the determination SDP parameter (note that the network protocol is IPv4).

[0249] Then, in No. 5 of the operation sequence shown in FIG. 30, following the operation of F4, a code 488 Not Acceptable Here response indicating that acceptance has been rejected by the receiving device in the SIP session is returned from the receiving mobile IMS network 30 to the telephone number research device 10 (specifically, the message exchange control unit 12) via the originating fixed IMS network 20 (F5, F6).

[0250] In this case, the telephone number investigation determination unit 13 of the telephone number investigation device 10 determines that a data communication dedicated terminal actually exists as the IMS terminal 50 to be investigated on the receiving side (that is, the telephone number of the IMS terminal 50 to be investigated actually exists).

[0251] Then, the message exchange control unit 12 of the telephone number researching device 10 returns an ACK (Acknowledgment) response indicating an acknowledgment in the SIP session to the terminating mobile IMS network 30 via the originating fixed IMS network 20 (F7, F8). This ends the session related to the INVITE request from the telephone number researching device 10.

[0252] (How to research phone numbers) FIG. 31 shows a summary of a method for investigating the usage status (specifically, existence (free, busy), and missing numbers) of the telephone number of an IMS terminal 50 (specifically, for example, the telephone number of a mobile phone having a 0A0 type telephone number or a terminal dedicated to data communication) based on the above-mentioned operational sequence.

[0253] Regarding the usage status of telephone numbers of mobile phones and data communication-only terminals having 0A0 type telephone numbers (specifically, for example, 090, 080, and 070) of IMS terminal 50 connected to a telecommunications operator (in other words, a communications carrier), it is possible to accurately determine whether the number is real (free or busy) or missing by describing IPv4 as the network protocol (in other words, Internet Protocol, IP version) among the SDP parameters and making an SDP offer (i.e., an INVITE request) using SDP for IPv4 for other SDP parameters.

[0254] (Phone number search program) As an example of a specific configuration aspect of the telephone number research program of the present invention, the telephone number research program of the embodiment is a program implemented in a telephone number research device 10 (see Figures 1 and 13) connected via an originating fixed IMS network 20 to multiple IMS terminals 50 connected to a terminating mobile IMS network 30.

[0255] The telephone number investigation program in the embodiment is configured to cause a computer (specifically, a telephone number investigation device 10) connected to a plurality of IMS terminals 50 connected to a terminating mobile IMS network 30 via an originating fixed IMS network 20 to execute at least the following processes: adding SDP parameters to an INVITE request for the IMS terminal 50 to be investigated and transmitting the INVITE request to the originating fixed IMS network 20 (toward the IMS terminal 50 to be investigated); receiving a response message via the originating fixed IMS network 20; and determining the usage status of the telephone number of the IMS terminal 50 to be investigated based on the response message.

[0256] The telephone number research program of the embodiment is configured so that the SDP parameters are described as follows: network protocol is IPv4, media type is audio only, media transport protocol is RTP / AVP only, and audio codec includes G.711 μ-law and G.722 (i.e., SDP for IPv4).

[0257] (Telephone number information system) FIG. 32 is a system configuration diagram of a telephone number information providing system 100 according to an embodiment, as an example of a specific configuration mode of the telephone number information providing system according to the present invention.

[0258] The telephone number information provision system 100 of the embodiment includes one or more user terminals 90, and a telephone number research server (specifically, a telephone number research device 10) connected to the user terminals 90 via an IP network 80 and also connected to a network not shown in the figure (for example, a calling fixed IMS network 20).

[0259] The telephone number information provision system 100 according to the embodiment has a telephone number research server (specifically, a telephone number research device 10) and a user terminal 90, and is provided with a network interface unit 11 that, when the telephone number research server (specifically, the telephone number research device 10) receives a telephone number research information provision request for the IMS terminal 50 from the user terminal 90, transmits the telephone number usage status of the IMS terminal 50 determined by the telephone number research determination unit 13 to the user terminal 90 that has made the telephone number research information provision request via the IP network 80 (see FIG. 13).

[0260] When the telephone number research server (specifically, telephone number research device 10) receives a request for telephone number research information regarding the telephone number to be researched from a user terminal 90 via the IP network 80, it refers to a recording medium (specifically, telephone number history database 15) in which telephone number history information recorded in chronological order with a timestamp indicating the date and time of the judgment results of the telephone number usage status being assigned to each of the judgment results, and transmits the telephone number history information via the IP network 80 to the user terminal 90 that made the request for telephone number research information.

[0261] The recording medium in which the telephone number history information is stored (specifically, the telephone number history database 15) may be distributed separately to users who need it. The recording medium in which the telephone number history information is stored (the telephone number history database 15) is a recording medium in which the existence or non-existence of the telephone number to be investigated is recorded, for example, by the telephone number investigation device 10 connected to the telecommunications carrier network via a dedicated line, and may be used for search in the system to which it is distributed.

[0262] The recording medium in which the telephone number history information is stored (specifically, telephone number history database 15) is a collection of results of judging the validity of the usage status of the telephone number of the receiving telephone terminal (specifically, a mobile phone or a data communication-only terminal as an IMS terminal 50), and for example, each judgment result is given a timestamp indicating the date and time of judgment and is recorded in chronological order.

[0263] The distribution of the recording medium on which the telephone number history information is stored (specifically, telephone number history database 15) is not limited to distribution in the form of a database recorded on a DVD or hard disk, but also includes distribution using a communication line.

[0264] (Action and effect) The telephone number research device 10 according to the embodiment makes it possible to use an IMS interconnection interface or the like for interconnection between carriers to realize an accurate research of the usage status of telephone numbers in the terminating mobile IMS network 30. Therefore, by introducing a telephone number research tool based on the SIP protocol that can be connected to the originating fixed IMS network 20 via UNI, a smooth transition to the new system platform becomes possible.

[0265] The telephone number research device 10 according to the embodiment can also accurately determine whether the telephone number of the IMS terminal 50 is in use (valid (actual)) or not in use (invalid (missing)). Therefore, by introducing a telephone number research tool based on the SIP protocol that can be connected to the originating fixed IMS network 20 via UNI, a smooth transition to the new system infrastructure becomes possible.

[0266] According to the telephone number investigation program of the embodiment, the telephone number investigation device 10 sequentially reads and executes the program recorded in a memory (not shown), thereby making it possible to realize an accurate investigation of the usage status of telephone numbers in the terminating mobile IMS network 30 by using an IMS interconnection interface for inter-operator interconnection. Therefore, by introducing a telephone number investigation tool based on the SIP protocol that can be UNI connected to the originating fixed IMS network 20, a smooth transition to the new system platform becomes possible.

[0267] According to the telephone number information provision system 100 of the embodiment, it is possible to provide a user who needs the information on whether a telephone number is in use (valid (actual)) or not in use (invalid (missing)) as determined by the telephone number investigation device 10. Also, by distributing a recording medium (specifically, telephone number history database 15) in which telephone number history information is stored to a user who needs the information, it is possible to utilize the information on the user side and provide information useful for, for example, credit.

[0268] The above describes an embodiment of the present invention, but the specific configuration of the present invention is not limited to the above embodiment, and the present invention also includes embodiments in which modifications and changes are made to the above embodiment without departing from the gist of the present invention.

[0269] For example, in the above embodiment, IPv4 is described (in other words, used) as the network protocol (in other words, Internet Protocol, IP version) as an SDP parameter and offered, but IPv6 may be described and offered as the network protocol. In this case, too, by describing the SDP parameters as follows, the same basic sequence and operation sequence as in the above embodiment are obtained.

[0270] Specifically, when offering an SDP parameter that describes (i.e., uses) IPv6 as the network protocol (in other words, Internet Protocol, IP version) among the SDP parameters for determination, the other SDP parameters for determination are described as follows: Media type: audio only Media transport protocol: RTP / AVP only Audio codec: G.711 μ-law only [Explanation of symbols]

[0271] 10 Telephone number investigation device 11 Network Interface Unit 12 Message exchange control section 13 Telephone Number Investigation and Judgment Department 14 Phone number history generation unit 15 Phone Number History Database 20 Originating fixed IMS network 20a SIP Server 21 Originating IBCF 30 Destination mobile IMS network 30a SIP Server 30b SIP Server 30c SIP Server 31 Terminating IBCF 50 IMS terminals 50a IMS terminal 50b IMS terminal 50c IMS terminal 90 User terminals 100 Information provision system

Claims

1. A telephone number research device connected to a plurality of IMS terminals connected to a destination mobile IMS network via a source fixed IMS network, a message exchange control unit that adds an SDP parameter to an INVITE request for the IMS terminal to be investigated, transmits the INVITE request to the originating fixed IMS network, and receives a response message via the originating fixed IMS network; a telephone number investigation determination unit that determines a usage status of the telephone number of the IMS terminal to be investigated in response to the response message, The SDP parameters are described as follows: network protocol is IPv4, media type is audio only, media transport protocol is RTP / AVP only, and audio codec includes G.711 μ-law and G.722; A telephone number investigation device characterized by:

2. The telephone number investigation determination unit, If the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, it is determined that the telephone number of the IMS terminal being investigated is real; If the response message is a code 404 Not Found, it is determined that the telephone number of the IMS terminal to be investigated is a missing number.

2. The telephone number investigation device according to claim 1,

3. If the response message is code 183 Session Progress or code 180 Ringing, The telephone number investigation determination unit determines that the telephone number of the IMS terminal to be investigated is real, the message exchange control unit transmits a CANCEL request to the originating fixed IMS network, thereby stopping ringing of the call bell of the IMS terminal to be investigated when a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated; 2. The telephone number investigation device according to claim 1,

4. A telephone number investigation method for investigating the usage status of telephone numbers of IMS terminals to be investigated using a device connected to a plurality of IMS terminals connected to a terminating mobile IMS network via an originating fixed IMS network, comprising: The apparatus, adding SDP parameters to an INVITE request for the IMS terminal to be investigated, and sending the INVITE request to the originating fixed IMS network; receiving a response message via the originating fixed IMS network; determining a usage status of the telephone number of the IMS terminal being surveyed in response to the response message; The SDP parameters are described as follows: network protocol is IPv4, media type is audio only, media transport protocol is RTP / AVP only, and audio codec includes G.711 μ-law and G.722; A method for investigating telephone numbers.

5. A telephone number investigation method for investigating the usage status of telephone numbers of IMS terminals to be investigated using a device connected to a plurality of IMS terminals connected to a terminating mobile IMS network via an originating fixed IMS network, comprising: The apparatus, adding SDP parameters to an INVITE request for the IMS terminal to be investigated, and sending the INVITE request to the originating fixed IMS network; receiving a response message via the originating fixed IMS network; determining a usage status of the telephone number of the IMS terminal being surveyed in response to the response message; The SDP parameters state that the network protocol is IPv6, the media type is audio only, the media transport protocol is RTP / AVP only, and the audio codec is G.711 μ-law only. A method for investigating telephone numbers.

6. If the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, it is determined that the telephone number of the IMS terminal being investigated is real; If the response message is a code 404 Not Found, it is determined that the telephone number of the IMS terminal to be investigated is a missing number.

6. The method for investigating a telephone number according to claim 4 or 5.

7. If the response message is code 183 Session Progress or code 180 Ringing, determining that the telephone number of the IMS terminal being investigated is real; sending a CANCEL request to the originating fixed IMS network, stopping ringing of the call bell of the IMS terminal to be investigated when a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated; 6. The method for investigating a telephone number according to claim 4 or 5.

8. A computer connected to a plurality of IMS terminals connected to a terminating mobile IMS network via an originating fixed IMS network, a process of adding an SDP parameter to an INVITE request for the IMS terminal to be investigated and transmitting the INVITE request to the originating fixed IMS network; receiving a response message via the originating fixed IMS network; and determining a usage status of the telephone number of the IMS terminal to be surveyed in response to the response message; The SDP parameters are described as follows: network protocol is IPv4, media type is audio only, media transport protocol is RTP / AVP only, and audio codec includes G.711 μ-law and G.722; A telephone number research program comprising:

9. If the response message is code 183 Session Progress, code 180 Ringing, code 487 Request Terminated, code 488 Not Acceptable Here, code 500 Server Internal Error, or code 486 Busy Here, it is determined that the telephone number of the IMS terminal being investigated is real; If the response message is a code 404 Not Found, it is determined that the telephone number of the IMS terminal to be investigated is a missing number.

9. The telephone number research program according to claim 8.

10. If the response message is code 183 Session Progress or code 180 Ringing, determining that the telephone number of the IMS terminal being investigated is real; sending a CANCEL request to the originating fixed IMS network, stopping ringing of the call bell of the IMS terminal to be investigated when a anonymous call rejection service and a anonymous call rejection function are not set for the IMS terminal to be investigated; 9. The telephone number research program according to claim 8.

11. A telephone number investigation device according to any one of claims 1 to 3; A user terminal, the telephone number investigation device includes a network interface unit that, when receiving a telephone number investigation information provision request for the IMS terminal from the user terminal, transmits the telephone number usage status of the IMS terminal determined by the telephone number investigation determination unit to the user terminal that has made the telephone number investigation information provision request via an IP network; A telephone number information providing system comprising:

Images