Telephone management system, telephone management method, and telephone management program

Abstract

To provide a telephone management system, method and program which cope with troublesome telephone without operation by a user.SOLUTION: A telephone management system includes a computer as at least two gateway units 2100 and 2200 which can be used as an outgoing side device on a side of making a call and an incoming side device on a side of receiving a call. When receiving a session start request from the outgoing side device (S102), the incoming side device requests an outgoing history of the outgoing side device (S104). When receiving the request of the outgoing history from the incoming side device, the outgoing side device replies the outgoing history of itself to the incoming side device (S105). The incoming side device analyzes the outgoing history received from the outgoing side device (S106), and determines whether or not to receive the session start request.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a telephone management system, a telephone management method, and a telephone management program, and more particularly to a telephone management system, a telephone management method, and a telephone management program that deal with nuisance calls. [Background technology]

[0002] In recent years, technologies have been developed to deal with nuisance calls such as aggressive solicitations and sales calls. For example, Patent Document 1 discloses a technology that blocks calls from telephone numbers registered on a blacklist provided by the police or businesses. [Prior art documents] [Patent documents]

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

[0004] The following analysis has been made from the perspective of the present invention, and the disclosures of the above-mentioned prior art documents are incorporated herein by reference.

[0005] The problem with Patent Document 1 is that it is not possible to reject calls from telephone numbers that are not registered in the rejection list provided by the police or the company. In addition, even if a user creates a personal rejection list, the problem is that the user must perform an operation.

[0006] Therefore, an object of the present invention is to provide a technique that contributes to dealing with nuisance calls without requiring any operation by the user. [Means for solving the problem]

[0007] According to a first aspect of the present invention, At least two gateway devices each capable of being either a calling device that makes a call or a called device that receives a call, Each of the gateway devices a call history request unit for requesting a call history from a calling device when a session start request is received from the calling device; an outgoing call history return unit that returns its own outgoing call history to the receiving device when a request for the outgoing call history is received from the receiving device; a determination unit that analyzes a call history received from a call-out device and determines whether or not to accept the session initiation request; A telephone management system is provided, comprising:

[0008] According to a second aspect of the present invention, there is provided a method for communicating with a call receiving device by using at least two gateway devices, the gateway devices being capable of functioning as a call receiving device and a call originating device, the method comprising: a step of requesting a call history from a calling device when a session initiation request is received from the calling device; a step of returning its own call history to the receiving device when a request for the call history is received from the receiving device; analyzing a call history received from a call originating device to determine whether to accept the session initiation request; A call management method is provided that performs the above steps.

[0009] According to a third aspect of the present invention, there is provided a method for communicating with a computer as at least two gateway devices that can be either a calling device that makes a call or a called device that receives a call, comprising: a process of requesting a call history from a calling device when a session initiation request is received from the calling device; a process of returning its own call history to the receiving device when a request for the call history is received from the receiving device; a process of analyzing a call history received from a call-out device and determining whether or not to accept the session initiation request; A telephone management program is provided that executes the following: Effect of the Invention

[0010] According to each aspect of the present invention, a telephone management system, a telephone management method, and a telephone management program are provided that contribute to dealing with nuisance telephone calls without user operation. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram for explaining an overview of the present invention. [Diagram 2] FIG. 1 is a diagram for explaining an overview of the present invention. [Diagram 3] 2 is a block diagram showing an example of a call-out side GW device 2100 of the first embodiment. [Figure 4] 2 is a block diagram showing an example of a receiving side GW device 2200 of the first embodiment. FIG. [Diagram 5] FIG. 2 is a flowchart illustrating an example of an overall flow of processing in the telephone management system 1000 of the first embodiment. [Figure 6] FIG. 11 is a flowchart showing an example of a flow relating to updating of the rejection list based on the caller number (S201). [Figure 7] FIG. 11 is a flowchart showing an example of a flow relating to confirmation of a caller number (S304). [Figure 8] FIG. 13 is a diagram showing an example of an incoming call history management table; [Figure 9] FIG. 13 is a diagram showing an example of a rejection list. [Figure 10] 13 is a flowchart showing an example of a flow relating to updating (S203) of a refusal list based on an outgoing call history received from an outgoing call side GW device 2100. FIG. [Figure 11] FIG. 13 is a flowchart showing an example of a flow relating to analysis of an outgoing call history (S510). [Figure 12] FIG. 11 is a diagram showing an example of an outgoing call history. [Figure 13]FIG. 13 is a flowchart showing an example of a flow relating to an incoming call rejection based on the rejection list (S204). [Figure 14] FIG. 11 is a flowchart showing an example of a flow relating to establishment of a telephone line (S205). [Figure 15] FIG. 11 is a block diagram showing an example of a call-out side GW device 2100 of the second embodiment. [Figure 16] FIG. 11 is a block diagram showing an example of a receiving side GW device 2200 of the second embodiment. [Figure 17] FIG. 11 is a flowchart illustrating an example of processing in the telephone management system 1000 of the second embodiment. [Figure 18] FIG. 2 illustrates an example of a computer serving as a gateway device 2000. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] A preferred embodiment of the present invention will be described in detail with reference to the drawings. Note that the reference numerals in the drawings are attached to each element for convenience as an example to aid in understanding, and are not intended to limit the present invention to the illustrated embodiment. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. A unidirectional arrow is a schematic representation of the flow of a main signal (data), and does not exclude bidirectionality. Furthermore, although not explicitly shown, input and output ports exist at the input and output ends of each connecting line in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, and the like shown in the present disclosure. The same is true for input and output interfaces.

[0013] First, an overview of the present invention will be described. As shown in Fig. 1, a telephone management system 1000 includes at least two gateway devices 2000. The gateway device 2000 can be either a calling device that makes a call or a called device that receives a call. In the following, the gateway device 2000 is regarded as a calling device and is referred to as a calling side GW device 2100, and the gateway device 2000 is regarded as a called device and is referred to as a called side GW (gateway) device 2200.

[0014] The originating side GW device 2100 and the terminating side GW device 2200 each include an outgoing call history request unit 2001, an outgoing call history return unit 2002, and a determination unit 2003. When the originating side GW device 2200 receives a session start request from the originating side GW device 2100, the outgoing call history request unit 2001 requests the originating side GW device 2100 for an outgoing call history. When the originating side GW device 2100 receives a request for an outgoing call history from the terminating side GW device 2200, the outgoing call history return unit 2002 returns the outgoing call history of the originating side GW device 2100 to the terminating side device. The determination unit 2003 of the terminating side GW device 2200 analyzes the outgoing call history received from the originating side GW device 2100, and determines whether or not to accept the session start request.

[0015] To explain a specific example, as shown in Fig. 2, when a user on the calling side performs an operation to make a call from the calling side telephone 2400 to the called side telephone 2500, the calling side telephone 2400 requests the calling side GW device 2100 to make a call (S101). The calling side GW device 2100 transmits an INVITE (session start request) to the called side GW device 2200 (S102). When the calling side GW device 2200 receives the INVITE, the calling history request unit 2001 does not transmit a RINGER to the called side telephone 2500 but holds it (S103), and instead requests the calling side GW device 2100 for a calling history (S104). In response to the request, the calling history return unit 2002 of the calling side GW device 2100 returns the calling history to the called side GW device 2200 (S105).

[0016] The determination unit 2003 of the receiving side GW device 2200 analyzes the received call history of the originating side GW device 2100 and determines whether or not to add the telephone number of the originating side telephone 2400 to the reject list (S106). For example, the determination unit 2003 of the receiving side GW device 2200 obtains an analysis result from the call history of the originating side GW device 2100 that the originating side GW device 2100 has made calls to three or more places within the past 15 minutes. In this case, the determination unit 2003 of the receiving side GW device 2200 determines that the call from the originating side telephone 2400 to the receiving side telephone 2500 is likely to be a nuisance call intended for sales or solicitation, and adds the telephone number of the originating side telephone 2400 to the reject list.

[0017] Next, the receiving side GW device 2200 checks whether the telephone number of the INVITE received in S103 is registered in the rejection list. If registered, the receiving side GW device 2200 does not transmit RINGER to the receiving side telephone 2500, but transmits an incoming call rejection (rejection of the INVITE) to the transmitting side telephone 2400 via the transmitting side GW device 2100 (S107). Since the session initiation request is ultimately rejected for telephone numbers added to the rejection list, it can be said that the determination unit 2003 of the receiving side GW device 2200 determines whether to accept the session initiation request. The receiving side GW device 2200 also rejects incoming calls from telephone numbers registered in the rejection list provided by the police or a business.

[0018] If the caller number does not exist in the rejection list (if the received call is not rejected), the called-side GW device 2200 establishes a telephone line as usual. That is, the called-side GW device 2200 transmits RINGER to the called-side telephone 2500. Then, after confirming that the called-side telephone 2500 is OFF-Hook, the called-side GW device 2200 notifies the calling-side GW device 2100 that the session start request has been accepted, and starts the call.

[0019] As described above, the telephone management system 1000 of the present invention makes it possible to deal with nuisance calls without user operation. That is, the called-side GW device 2200 automatically adds a telephone number for which it has determined that a session initiation request should be rejected to the rejection list, so no user operation is required. Also, when the telephone management system 1000 of the present invention receives a session initiation request, it immediately determines whether or not to accept the session initiation request. Therefore, it is possible to deal with nuisance calls without impairing real-time performance.

[0020] [Embodiment 1] In the following, the above-mentioned telephone management system 1000 will be described in more detail as a first embodiment.

[0021] [Configuration of telephone management system 1000] As in the above overview, the telephone management system 1000 has at least two gateway devices 2000, and the gateway device 2000 can be either an originating side GW device 2100 that originates a call or a terminating side GW device 2200 that receives a call. Note that, in the following, the originating side GW device 2100 will be mainly described with reference to Fig. 3, but the terminating side GW device 2200 also has basically the same configuration as the originating side GW device 2100, as shown in Fig. 4.

[0022] 3, the originating side GW device 2100 has a control unit 2110, a storage unit 2120, a determination unit 2130, a network interface 2140, and a telephone interface 2150. In the terminating side GW device 2200 (FIG. 4), these are referred to as a control unit 2210, a storage unit 2220, a determination unit 2230, a network interface 2240, and a telephone interface 2250.

[0023] The control unit 2110 has a function of controlling the entirety of the calling side GW device 2100, and includes a memory control unit 2111, a determination unit control unit 2112, a network control unit 2113, and a telephone function control unit 2114. In the called side GW device 2200 (FIG. 4), these are referred to as a memory control unit 2211, a determination unit control unit 2212, a network control unit 2213, and a telephone function control unit 2214.

[0024] The memory control unit 2111 writes data to the memory unit 2120 and reads data from the memory unit 2120. The determination unit control unit 2112 transmits data required for the rejection list determination to the determination unit 2130 and receives the rejection list determination result from the determination unit 2130. The network control unit 2113 receives data from the Internet 2300 and transmits data to the Internet 2300 via the network interface 2140. The telephone function control unit 2114 controls telephone operations such as calling, receiving, holding, and disconnecting calls to the calling telephone 2400, and controlling the transmission of voice announcements, etc., via the telephone interface 2150. The telephone function control unit 2214 of the called side GW device 2200 controls telephone operations such as calling, receiving, holding, and disconnecting calls to the called telephone 2500, and controlling the transmission of voice announcements, etc., via the telephone interface 2250.

[0025] The storage unit 2120 has a function of holding general data of the calling side GW device 2100, and includes an incoming call history storage unit 2121, an outgoing call history storage unit 2122, and a rejection list storage unit 2123. The storage unit 2120 may be provided outside the calling side GW device 2100. For example, a server functioning as the storage unit 2120 may be provided on the Internet 2300, and the data may be managed by the server. In the called side GW device 2200, these are referred to as an incoming call history storage unit 2221, an outgoing call history storage unit 2222, and a rejection list storage unit 2223.

[0026] The incoming call history storage unit 2121 stores data such as the incoming call time and call duration of calls received via the Internet 2300. The outgoing call history storage unit 2122 stores data such as the outgoing call time and call duration of calls made from the calling telephone 2400. The rejection list storage unit 2123 stores data of telephone numbers added to the rejection list.

[0027] The determination unit 2130 has a function of determining whether or not to update the rejection list, and includes a rejection list determination unit 2131 (referred to as a rejection list determination unit 2231 in the receiving side GW device 2200). The rejection list determination unit 2131 determines whether or not to update the rejection list based on the incoming call history, the outgoing call history, and the caller information.

[0028] The network interface 2140 is a physical interface with the Internet 2300. The telephone interface 2150 is a physical interface with the calling telephone 2400.

[0029] The Internet 2300 is a network for exchanging data between the originating side GW device 2100 and the terminating side GW device 2200, and includes a SIP (Session Initiation Protocol) server. The originating side telephone 2400 is a telephone connected to the originating side GW device 2100, and the terminating side telephone 2500 is a telephone connected to the terminating side GW device 2200.

[0030] [Processing in the telephone management system 1000] The flow of processing in the telephone management system 1000 will be described. In the telephone management system 1000, as a whole, as shown in Fig. 5, first, a rejection list is updated based on a caller number (S201). Next, the rejection list is updated based on the incoming call history of the incoming side GW device 2200 (S202), the rejection list is updated based on the outgoing call history received from the outgoing side GW device 2100 (S203), and incoming call is rejected based on the rejection list (S204). Finally, a telephone line is established (S205). Details of S201 to S205 will be described below.

[0031] [Update of rejection list based on caller number (S201)] The process (S201) of updating the rejection list based on the caller number will be described with reference to Fig. 6 to Fig. 9. As shown in Fig. 6, when the caller telephone 2400 makes a call via the caller GW device 2100 (S301), the caller GW device 2100 transmits an INVITE to the callee GW device 2200 via the SIP server (S302) (S303). The callee GW device 2200, which has received the INVITE, checks the caller number (the telephone number of the caller telephone 2400) (S304).

[0032] The receiving side GW device 2200 performs the process shown in Fig. 7 in confirming the caller number (S304). That is, when the receiving side GW device 2200 receives an INVITE (S401), it confirms whether the caller number is a number registered in the refusal list (S402). If the caller number is not registered in the refusal list (S402, No), the receiving side GW device 2200 confirms whether the caller number is in an area registered in the refusal list (S403). If the caller number is not in an area registered in the refusal list (S403, No), the receiving side GW device 2200 confirms the call history management table stored in the call history storage unit 2221 (S404). The call history management table is a table in which the call date and time, the caller number, the call duration, and the talk duration are recorded in association with each other, as shown in Fig. 8, for example.

[0033] If it is determined that the caller number should be added to the reject list (S405, Yes), the called side GW device 2200 adds the currently received caller number to the reject list stored in the reject list storage unit 2223 (S406). The reject list is a table in which telephone numbers and registration forms are recorded in association with each other, as shown in Fig. 9, for example.

[0034] After adding the caller number, the called side GW device 2200 transmits 180 RINGING to the called side GW device 2100 (S407, proceed to S305 in FIG. 6). Similarly, if the caller number is registered in the reject list (S402, Yes) or if the caller number is in an area registered in the reject list (S403, Yes), the called side GW device 2200 transmits 180 RINGING. If the caller number is not added to the reject list (S405, No), the called side GW device 2200 proceeds to update the reject list based on the call history of the called side GW device 2200 (S202).

[0035] Returning to FIG. 6, the receiving side GW device 2200 transmits 180 RINGING to the calling side GW device 2100 (S305) (S306), and the calling side GW device 2100 transmits an RBT to the calling side telephone 2400 (S307).

[0036] [Updating the rejection list based on the call history of the called side GW device 2200 (S202)] Next, the process (S202) of updating the refusal list based on the incoming call history of the receiving side GW device 2200 will be described. It is assumed that the incoming call history storage unit 2221 of the receiving side GW device 2200 stores the incoming call information management table shown in FIG. 8. Here, the receiving side GW device 2200 judges whether to register a call in the refusal list based on these statistical information. For example, when the caller side is talking one-sidedly, it is highly likely that the call is a sales call or a solicitation call. Therefore, the receiving side GW device 2200 may add to the refusal list a caller number in which the ratio of the speech time from the receiving side telephone to the total call time is less than 10%. Also, when a call is received many times within a few days from an area where the possibility of receiving a call is low, it is highly likely that the call is a sales call or a solicitation call. Therefore, the receiving side GW device 2200 may add to the refusal list a caller number that has received calls from the same area code three or more times within five days, using the first six digits up to the area code. When it is determined by these determination processes that the caller number needs to be added to the rejection list, the called side GW device 2200 adds the caller number and the registration type to the rejection list. The rejection list storage unit 2223 stores the rejection list shown in FIG. 9. In the example of FIG. 8 and FIG. 9, the called side GW device 2200 determines that the caller numbers 03-1234-aaaa and 03-1234-cccc received calls from the same area code three or more times within five days, and adds the telephone number 03-1234-xxxx to the rejection list. In FIG. 9, xxxx represents all combinations of numbers (i.e., 03-1234-0001 to 03-1234-9999), and aaaa and the like in FIG. 8 and FIG. 9 represent individual numerical values ​​(i.e., individual telephone numbers). In addition, these determination processes are examples, and the method of utilizing statistical information for the determination, the threshold value, and the like may be any value. Furthermore, the statistical information used to determine whether or not to add a call to the rejection list is not limited to the incoming call date and time, call duration, and talk time, and other statistical information may also be used.

[0037] [Updating the rejection list based on the call history received from the call-receiving side GW device 2100 (S203)] Next, the process (S203) of updating the rejection list based on the outgoing call history received from the calling-side GW device 2100 will be described. As shown in Fig. 10, after S305 to S307, the called-side GW device 2200 transmits to the calling-side GW device 2100 a message requesting the outgoing call history of the calling-side telephone 2400 (S508). This process is performed by the control unit 2210 of the called-side GW device 2200. That is, the control unit 2210 in Fig. 4 also functions as the outgoing call history request unit 2001 in Fig. 1.

[0038] In response to this request, the calling side GW device 2100 returns the calling history stored in the calling history storage unit 2122 to the called side GW device 2200 (S509). This process is performed by the control unit 2110 of the calling side GW device 2100. That is, the control unit 2110 in FIG. 3 also functions as the calling history return unit 2002 in FIG.

[0039] The receiving side GW device 2200 analyzes the received outgoing call history (S510). In analyzing the outgoing call history (S510), the receiving side GW device 2200 performs the process shown in FIG. 11. That is, the receiving side GW device 2200 acquires and analyzes the outgoing call history (S601) (S602). The receiving side GW device 2200 judges from this statistical information whether or not the caller number should be added to the rejection list (S603). If it is judged that the caller number should be registered in the rejection list (S603, Yes), the receiving side GW device 2200 updates the rejection list (S604) and proceeds to reject the incoming call based on the rejection list (S204). If the caller number is not to be added to the rejection list (S603, No), the receiving side GW device 2200 proceeds directly to reject the incoming call based on the rejection list (S204).

[0040] The determination of whether to register the caller number in the reject list (S603) will be described in more detail. First, it is assumed that the called side GW device 2200 receives the call history shown in FIG. 12. From the call history in FIG. 12, an analysis result is obtained that the called side GW device 2200 has made calls to three or more places within 15 minutes. Therefore, the called side GW device 2200 determines that the call from the calling side telephone 2400 to the called side telephone 2500 is highly likely to be a nuisance call for the purpose of sales or solicitation, and adds the caller number (the telephone number of the calling side telephone 2400) to the reject list. Note that, similar to the method of updating the reject list using the incoming call history, the caller number may also be added to the reject list when the caller is talking unilaterally (for example, the percentage of the caller's speaking time is 90% or more). Also, these determination processes are merely examples, and the method of utilizing statistical information for the determination, the threshold value, etc. may be any value. Also, the statistical information used to determine whether to add to the reject list may be other statistical information in addition to the incoming call date and time, the call duration, and the speech duration. Here, the statistical information is information showing the tendency of the call history of the nuisance carrier that has been statistically analyzed, and when the call history received by the called side GW device 2200 matches the tendency of the call history of the nuisance carrier, the caller number may be added to the rejection list. This process is performed by the control unit 2210 or the determination unit 2230 of the called side GW device 2200.

[0041] [Rejecting incoming calls based on the rejection list (S204)] Next, the process of rejecting an incoming call based on the rejection list of the called-side GW device 2200 (S204) will be described. As shown in FIG. 13, the rejection list determination unit 2231 of the called-side GW device 2200 reads the rejection list from the rejection list storage unit 2223 (S701), and the called-side GW device 2200 checks whether the caller number is registered in the rejection list (S702). If the caller number is registered in the rejection list (S702, Yes), the rejection list determination unit 2231 transmits an incoming call rejection (rejection of INVITE) to the calling-side GW device 2100 via the SIP server (S703). Here, the called-side GW device 2200 does nothing to the called-side telephone 2500, so the called-side telephone 2500 does not ring. As a result, the called-side user is not even aware that there was a call from the calling side and the call is rejected.

[0042] On the other hand, if the caller number is not registered in the rejection list (S702, No), the process proceeds to establishing a telephone line (S205).

[0043] [Establishing a telephone line (S205)] Next, the process of establishing a telephone line (S205) will be described. As shown in Fig. 14, the receiving side GW device 2200 transmits RINGER to the receiving side telephone 2500 (S811). When the receiving side GW device 2200 detects OFF-Hook of the receiving side telephone 2500 (S812), the receiving side GW device 2200 responds with 200 OK to the calling side GW device 2100 via the SIP server (S813) (S814). The calling side GW device 2100 returns an ACK (acknowledgement) to the receiving side GW device 2200 (S815), and starts a call between the calling side telephone 2400 and the receiving side telephone 2500 (S816).

[0044] As described above, the telephone management system 1000 of the present invention can deal with nuisance calls without user operation. That is, the called-side GW device 2200 can automatically add a telephone number for which it has determined that a session start request should be rejected to the rejection list. In addition, the telephone management system 1000 of the present invention achieves real-time performance, which allows rejection of incoming calls even from telephone numbers that are not registered in the rejection list (blacklist) provided by the police or a company.

[0045] [Embodiment 2] In the first embodiment, the case where an incoming call from a telephone number registered in the rejection list is rejected, that is, the case where an incoming call is accepted if the telephone number is not registered in the rejection list, is described. However, it is also possible to accept only incoming calls from telephone numbers registered in the allowance list and reject all incoming calls from other telephone numbers.

[0046] 15, the memory unit 2120 of the calling side GW device 2100 further includes a permission list memory unit 2124, and the determination unit 2130 further includes a permission list determination unit 2132. Similarly, the called side GW device 2200 further includes a permission list memory unit 2224 and a permission list determination unit 2232, as shown in FIG.

[0047] 17, when a user on the calling side performs an operation to make a call from the calling side telephone 2400 to the called side telephone 2500, the calling side telephone 2400 requests the calling side GW device 2100 to make a call (S1001). The calling side GW device 2100 transmits an INVITE (session start request) to the called side GW device 2200 (S1002). When the called side GW device 2200 receives the INVITE, it does not transmit a RINGER to the called side telephone 2500 but holds it (S1003), and instead requests the calling side GW device 2100 for a call history (S1004). In response to the request, the calling side GW device 2100 returns the call history to the called side GW device 2200 (S1005).

[0048] The receiving side GW device 2200 analyzes the received call history of the originating side GW device 2100 and judges whether or not to add the telephone number of the originating side telephone 2400 to the permission list (S1006). For example, the receiving side GW device 2200 obtains an analysis result from the call history of the originating side GW device 2100 that the originating side GW device 2100 has made calls to the same telephone number three or more times in the past. In this case, the receiving side GW device 2200 judges that the call from the originating side telephone 2400 to the receiving side telephone 2500 is unlikely to be a nuisance call intended for sales or solicitation. Then, the receiving side GW device 2200 adds the telephone number of the originating side telephone 2400 to the permission list stored in the permission list storage unit 2224. In addition, if the call history of the calling side GW device 2100 shows that the calling time of the caller and the called party is almost the same or the calling time of the caller is shorter (for example, the calling time of the caller is less than 50%), the calling number may be added to the permission list.

[0049] Next, the receiving side GW device 2200 checks whether the telephone number of the INVITE received in S1003 is registered in the permission list. If it is not registered, the receiving side GW device 2200 does not send RINGER to the receiving side telephone 2500, but sends an incoming call rejection (rejection of the INVITE) to the calling side telephone 2400 via the calling side GW device 2100 (S1007). If the caller number is registered in the permission list, the receiving side GW device 2200 establishes a telephone line as usual. That is, the receiving side GW device 2200 sends RINGER to the receiving side telephone 2500. Then, after checking the OFF-Hook of the receiving side telephone 2500, the receiving side GW device 2200 notifies the calling side GW device 2100 that the session start request has been accepted, and starts the call.

[0050] As described above, the telephone management system 1000 of the present invention makes it possible to deal with nuisance calls without user operation. That is, even if a nuisance caller does not install the gateway device 2000 of the present invention and does not return a call history, the called side GW device 2200 will reject the call.

[0051] For example, the permission list may be updated based on not only the call history of the calling side GW device 2100 but also the call history of the called side GW device 2200. For example, the telephone number registered in the call history of the called side GW device 2200 is a telephone number to which the called side user has made a call of his / her own accord in the past, and therefore is considered to be an acquaintance's telephone number (at least the caller knows who the other party is). Therefore, the telephone number registered in the call history of the called side GW device 2200 may be registered in the permission list. Also, for example, in the call history of the called side GW device 2200, if the call times of the caller and the called party are almost the same or the call time of the called party is longer, it is highly likely that the caller is an acquaintance. Therefore, if the ratio of the call time of the called party to the total call time is 50% or more, the callee number may be added to the permission list. Also, if the same number is called in a short period of time, it is highly likely that the callee number is an acquaintance, so if the same number is called three or more times within one week, the callee number may be added to the permission list. Additionally, if you are calling the same area in a short period of time, there is a high chance that you have many acquaintances in that area, so if you call the same six-digit number including the area code three or more times within an hour, you may want to add that six-digit number including the area code to your allow list.

[0052] [Transformation form] The present invention can also be realized as a telephone management method by a computer serving as the telephone management system 1000 or the gateway device 2000, or as a telephone management program executed by the computer. That is, as shown in Fig. 18, the computer serving as the gateway device 2000 includes a CPU (Central Processing Unit: equivalent to the control units 2110 and 2210), a memory (equivalent to the storage units 2120 and 2220), and an interface. The present invention can be realized by the CPU reading out a program from the memory and realizing modules equivalent to the outgoing call history request unit 2001, the outgoing call history return unit 2002, and the determination unit 2003.

[0053] A part or all of the above-described embodiments may be described as, but is not limited to, the following supplementary notes.

[0054] (Appendix 1) At least two gateway devices each capable of being either a calling device that makes a call or a called device that receives a call, Each of the gateway devices a call history request unit for requesting a call history from a calling device when a session start request is received from the calling device; an outgoing call history return unit that returns its own outgoing call history to the receiving device when a request for the outgoing call history is received from the receiving device; a determination unit that analyzes a call history received from a call-out device and determines whether or not to accept the session initiation request; A telephone management system comprising:

[0055] (Appendix 2) Each of the gateway devices a rejection list storage unit that stores a rejection list that lists telephone numbers whose session initiation requests have been judged by the judgment unit to be rejected; a request refusal unit that rejects a session initiation request from a telephone number registered in the refusal list; 2. The telephone management system of claim 1, further comprising:

[0056] (Appendix 3) 2. The telephone management system according to claim 1, wherein the determination unit rejects the session start request when it finds from the call history that the number of calls made within a predetermined period of time exceeds a threshold value.

[0057] (Appendix 4) 2. The telephone management system according to claim 1, wherein the determination unit rejects the session start request when it finds an outgoing call history in which the ratio of speech time to call time exceeds a threshold value.

[0058] (Appendix 5) 2. The telephone management system according to claim 1, wherein the determination unit rejects the session start request based on statistical information of an outgoing call history.

[0059] (Appendix 6) Each of the gateway devices an authorization list storage unit that stores an authorization list that lists telephone numbers for which the determination unit has determined that a session initiation request should be accepted; a session initiation unit for initiating a session from a telephone number registered in the permission list; 2. The telephone management system of claim 1, further comprising:

[0060] (Appendix 7) At least two computers serving as gateway devices, each capable of functioning as a calling device that makes a call and a called device that receives a call, a step of requesting a call history from a calling device when a session initiation request is received from the calling device; a step of returning its own call history to the receiving device when a request for the call history is received from the receiving device; analyzing a call history received from a call originating device to determine whether to accept the session initiation request; A phone management method to perform.

[0061] (Appendix 8) At least two computers serving as gateway devices, each capable of functioning as a calling device that makes a call and a called device that receives a call, a process of requesting a call history from a calling device when a session initiation request is received from the calling device; a process of returning its own call history to the receiving device when a request for the call history is received from the receiving device; a process of analyzing a call history received from a call-out device and determining whether or not to accept the session initiation request; A telephone management program that runs

[0062] The disclosures of the above cited patent documents are incorporated herein by reference and may be used as the basis or part of the present invention as necessary. Within the scope of the entire disclosure of the present invention (including the scope of claims), modifications and adjustments of the embodiments and examples are possible based on the basic technical ideas. Furthermore, within the scope of the entire disclosure of the present invention, various combinations or selections (including partial deletions) of various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes various modifications and corrections that a person skilled in the art would be able to make according to the entire disclosure including the scope of claims and the technical ideas. In particular, with regard to the numerical ranges described in this document, any numerical value or small range included in the range should be interpreted as being specifically described even if not otherwise specified. Furthermore, the disclosures of the above cited documents may be used in part or in whole in combination with the disclosures of this document as part of the disclosure of the present invention in accordance with the spirit of the present invention as necessary, and are deemed to be included in the disclosures of this application. [Explanation of symbols]

[0063] 1000: Telephone management system 2000: Gateway equipment 2001: Call history request section 2002: Call history reply section 2003: Judgment Department 2100: Call originating GW device 2110: Control unit 2111: Memory control unit 2112: Judgment unit control unit 2113: Network control section 2114: Telephone function control unit 2120: Storage section 2121: Call history memory section 2122: Call history memory unit 2123: Rejection list storage unit 2124: Permission list storage unit 2130: Judgment section 2131: Rejection list decision unit 2132: Permission list judgment section 2140: Network interface 2150: Telephone interface 2200: Terminating side GW device 2210: Control section 2211: Memory control unit 2212: Judgment unit control unit 2213: Network control section 2214: Telephone function control unit 2220: Storage section 2221: Call history memory section 2222: Call history memory unit 2223: Rejection list storage unit 2224: Permission list storage unit 2230: Judgment section 2231: Rejection list decision section 2232: Permission list judgment section 2240: Network interface 2250: Telephone interface 2300: Internet 2400: Calling party's telephone 2500: Called phone number

Claims

1. At least two gateway devices each capable of being either a calling device that makes a call or a called device that receives a call, Each of the gateway devices a call history request unit for requesting a call history from a calling device when a session start request is received from the calling device; an outgoing call history return unit that returns its own outgoing call history to the receiving device when a request for the outgoing call history is received from the receiving device; a determination unit that analyzes a call history received from a call-out device and determines whether or not to accept the session initiation request; A telephone management system comprising:

2. Each of the gateway devices a rejection list storage unit that stores a rejection list that lists telephone numbers whose session initiation requests have been judged by the judgment unit to be rejected; a request refusal unit that rejects a session initiation request from a telephone number registered in the refusal list; The telephone management system of claim 1 further comprising:

3. 2. The telephone management system according to claim 1, wherein the determination unit rejects the session start request when it finds from the call history that the number of calls made within a predetermined period of time exceeds a threshold value.

4. 2. The telephone management system according to claim 1, wherein the determination unit rejects the session start request when it finds from the call history that the ratio of speech time to call time exceeds a threshold value.

5. the determination unit rejects the session start request based on statistical information of an outgoing call history; 2. The telephone management system according to claim 1, wherein the statistical information is information showing a trend of a statistically analyzed call history of a nuisance caller.

6. Each of the gateway devices an authorization list storage unit that stores an authorization list that lists telephone numbers for which the determination unit has determined that a session initiation request should be accepted; a session initiation unit for initiating a session from a telephone number registered in the permission list; The telephone management system of claim 1 further comprising:

7. At least two computers serving as gateway devices, each capable of functioning as a calling device that makes a call and a called device that receives a call, a step of requesting a call history from a calling device when a session initiation request is received from the calling device; a step of returning its own call history to the receiving device when a request for the call history is received from the receiving device; analyzing a call history received from a call originating device to determine whether to accept the session initiation request; A phone management method to perform.

8. At least two computers serving as gateway devices, each capable of functioning as a calling device that makes a call and a called device that receives a call, a process of requesting a call history from a calling device when a session initiation request is received from the calling device; a process of returning its own call history to the receiving device when a request for the call history is received from the receiving device; a process of analyzing a call history received from a call-originating device and determining whether or not to accept the session initiation request; A telephone management program that runs

Images