JP2024027949A - Telephone management system, telephone management method and telephone management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: 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

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to a telephone management system, a telephone management method, and a telephone management program. In particular, the present invention relates to a telephone management system, a telephone management method, and a telephone management program for dealing with nuisance calls.

In recent years, technology has been developed to deal with nuisance calls such as forced solicitations and sales calls. For example, Patent Document 1 discloses a technique for rejecting incoming calls from telephone numbers registered in a rejection list (blacklist) provided by the police or businesses.

Japanese Patent Application Publication No. 2017-046076

The following analysis was made from the perspective of the present invention. In addition, each disclosure of the above-mentioned prior art documents is incorporated into this book by reference.

Patent Document 1 has a problem in that it is not possible to reject calls from telephone numbers that are not registered in the rejection list provided by the police or business operators. Further, even if a user personally creates a rejection list, there is a problem in that the user must perform an operation.

Therefore, it is an object of the present invention to provide a technology that contributes to dealing with nuisance calls without user operations.

According to the first aspect of the present invention,
at least two gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call;
Each of the gateway devices
a calling history requesting unit that requests a calling history from the calling device when a session start request is received from the calling device;
a calling history reply unit that returns its own calling history to the called device when receiving a request for the calling history from the called device;
a determination unit that analyzes the calling history received from the calling device to determine whether or not to accept the session start request;
A telephone management system is provided.

According to a second aspect of the present invention, at least two computers serving as gateway devices that can serve as either a calling device that makes a call and a called device that receives a call,
When receiving a session start request from the calling device, requesting the calling device for a call history;
When receiving a request for the calling history from the called device, a step of replying its own calling history to the called device;
analyzing the call history received from the calling device to determine whether to accept the session start request;
A telephone management method is provided.

According to a third aspect of the present invention, at least two computers as gateway devices that can serve as either a calling device that makes a call and a called device that receives a call,
When a session start request is received from a calling device, a process of requesting a call history from the calling device;
When receiving a request for the calling history from the called device, a process of replying the calling history to the called device;
Analyzing the call history received from the calling device to determine whether to accept the session start request;
A telephone management program is provided to run the telephone management program.

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 calls without user operations.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram for explaining an overview of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram for explaining an overview of the present invention. FIG. 2 is a block diagram illustrating an example of a transmitting-side GW device 2100 according to the first embodiment. FIG. 2 is a block diagram illustrating an example of a receiving-side GW device 2200 according to the first embodiment. FIG. 2 is a flowchart diagram illustrating an example of the overall flow of processing in the telephone management system 1000 of the first embodiment. It is a flowchart figure which shows an example of the flow regarding update (S201) of a rejection list based on a caller number. FIG. 7 is a flowchart diagram illustrating an example of a flow related to confirming a caller number (S304). It is a figure which shows an example of an incoming call history management table. It is a figure showing an example of a rejection list. FIG. 3 is a flowchart illustrating an example of a flow related to updating the rejection list (S203) based on the call history received from the calling side GW device 2100. FIG. 7 is a flowchart diagram illustrating an example of a flow related to analysis of call history (S510). It is a figure showing an example of call history. It is a flowchart figure which shows an example of the flow regarding incoming call rejection (S204) based on a rejection list. It is a flowchart figure which shows an example of the flow regarding establishment of a telephone line (S205). FIG. 3 is a block diagram illustrating an example of a transmitting-side GW device 2100 according to the second embodiment. FIG. 3 is a block diagram showing an example of a receiving-side GW device 2200 according to Embodiment 2. FIG. 7 is a flowchart diagram illustrating an example of processing in the telephone management system 1000 according to the second embodiment. FIG. 2 is a diagram showing an example of a computer as a gateway device 2000. FIG.

Preferred embodiments of the present invention will be described in detail with reference to the drawings. Note that the drawing reference numerals added to the following description are added to each element for convenience as an example to aid understanding, and are not intended to limit the present invention to the illustrated embodiment. Furthermore, connection lines between blocks in each figure include both bidirectional and unidirectional connections. The unidirectional arrows schematically indicate the main signal (data) flow, and do not exclude bidirectionality. Furthermore, in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc. shown in the present disclosure, although not explicitly stated, an input port and an output port are present at the input end and output end of each connection line, respectively. The same applies to the input/output interface.

First, an overview of the present invention will be explained. As shown in FIG. 1, 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. Hereinafter, the gateway device 2000 is considered to be a calling side device and is referred to as a calling side GW device 2100, and the gateway device 2000 is considered to be a receiving side device and is referred to as a receiving side GW (gateway) device 2200.

The calling side GW device 2100 and the receiving side GW device 2200 each include a calling history requesting section 2001, a calling history replying section 2002, and a determining section 2003. When receiving a session start request from the calling GW device 2100, the calling history requesting unit 2001 of the receiving GW device 2200 requests the calling history from the calling GW device 2100. When the calling history reply unit 2002 of the calling side GW device 2100 receives a request for calling history from the called side GW device 2200, it returns the calling history of the calling side GW device 2100 to the called side device. The determining unit 2003 of the receiving GW device 2200 analyzes the call history received from the calling GW device 2100 and determines whether to accept the session start request.

To explain with a specific example, when the calling user performs an operation to make a call from the calling phone 2400 to the called phone 2500 as shown in FIG. A call is requested to the device 2100 (S101). The originating GW device 2100 transmits an INVITE (session start request) to the terminating GW device 2200 (S102). Upon receiving the INVITE, the calling history requesting unit 2001 of the receiving side GW device 2200 suspends sending the RINGER to the called side telephone 2500 (S103), and instead sends the calling history to the calling side GW device 2100. (S104). In response to the request, the calling history reply unit 2002 of the calling side GW device 2100 returns the calling history to the receiving side GW device 2200 (S105).

The determining unit 2003 of the receiving GW device 2200 analyzes the received call history of the calling GW device 2100 and determines whether to add the telephone number of the calling device 2400 to the rejection list (S106). For example, assume that the determining unit 2003 of the receiving GW device 2200 obtains an analysis result from the calling history of the calling GW device 2100 that the calling GW device 2100 has made calls to three or more locations within 15 minutes in the past. . In this case, the determination unit 2003 of the receiving side GW device 2200 determines that there is a high possibility that the incoming call from the calling side telephone 2400 to the receiving side telephone 2500 is a nuisance call for the purpose of sales or solicitation, and makes the call. Add the phone number of side phone 2400 to the rejection list.

Subsequently, 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 send a RINGER to the called side telephone 2500, but sends a call rejection (INVITE rejection) to the calling side telephone 2400 via the calling side GW device 2100. (S107). As a result, the session start request is rejected for the telephone number added to the rejection list, so it can be said that the determination unit 2003 of the receiving side GW device 2200 determines whether or not to accept the session start request. In addition, the receiving side GW device 2200 will also reject incoming calls from phone numbers registered in the rejection list provided by the police or business operators.

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

As described above, according to the telephone management system 1000 of the present invention, it is possible to deal with nuisance calls without any user operation. In other words, the receiving-side GW device 2200 automatically adds the telephone number for which it is determined that the session start request should be rejected to the rejection list, so no operation is required by the user. Furthermore, in the telephone management system 1000 of the present invention, when a session start request is received, it is determined on the spot whether or not to accept the session start request. Therefore, it is possible to deal with nuisance calls without impairing real-time performance.

[Embodiment 1]
Below, as Embodiment 1, the above-mentioned telephone management system 1000 will be described in more detail.

[Configuration of telephone management system 1000]
Similar to the above overview, the telephone management system 1000 has at least two gateway devices 2000, and the gateway devices 2000 are a calling side GW device 2100 for making a call and a receiving side GW device 2200 for receiving a call. It can be either. Note that, below, the originating side GW device 2100 will be explained mainly with reference to FIG. 3, but as shown in FIG. 4, the receiving side GW device 2200 also basically has the same configuration as the originating side GW device 2100. .

As shown in FIG. 3, the originating GW device 2100 includes a control section 2110, a storage section 2120, a determination section 2130, a network interface 2140, and a telephone interface 2150. In the receiving side GW device 2200 (FIG. 4), these are called a control section 2210, a storage section 2220, a determination section 2230, a network interface 2240, and a telephone interface 2250.

The control unit 2110 has a function of controlling the entire originating side GW device 2100, and includes a storage unit control unit 2111, a determination unit control unit 2112, a network control unit 2113, and a telephone function control unit 2114. In the receiving side GW device 2200 (FIG. 4), they are referred to as a storage unit control unit 2211, a determination unit control unit 2212, a network control unit 2213, and a telephone function control unit 2214.

The storage unit control unit 2111 writes data to the storage unit 2120 and reads data from the storage unit 2120. The determination unit control unit 2112 transmits data necessary for 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. Telephone function control unit 2114 performs telephone control such as calling, receiving, holding, and disconnecting calls to calling side telephone 2400, and controlling voice announcement transmission, etc., via telephone interface 2150. The telephone function control unit 2214 of the receiving side GW device 2200 performs telephone control such as calling, receiving, holding, and disconnecting the receiving side telephone 2500 via the telephone interface 2250, and controls the sending of announcement voice.

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. Note that the storage unit 2120 may be provided outside the originating 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 receiving side GW device 2200, these are called an incoming call history storage section 2221, an outgoing call history storage section 2222, and a rejection list storage section 2223.

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

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, outgoing call history, and caller information.

Network interface 2140 is a physical interface with Internet 2300. Telephone interface 2150 is the physical interface with calling telephone 2400.

The Internet 2300 is a network that exchanges data between the originating GW device 2100 and the terminating GW device 2200, and includes a SIP (Session Initiation Protocol) server. The calling side telephone 2400 is a telephone connected to the calling side GW device 2100, and the called side telephone 2500 is a phone connected to the called side GW device 2200.

[Processing in telephone management system 1000]
The flow of processing in telephone management system 1000 will be explained. In the telephone management system 1000 as a whole, as shown in FIG. 5, first, the rejection list is updated based on the caller number (S201). Subsequently, the rejection list is updated based on the call history of the receiving side GW device 2200 (S202), the rejection list is updated based on the call history received from the calling side GW device 2100 (S203), and the call is rejected based on the rejection list (S204). will be held. Finally, a telephone line is established (S205). Below, details of S201 to S205 will be explained.

[Update of rejection list based on caller number (S201)]
The process of updating the rejection list based on the caller number (S201) will be described with reference to FIGS. 6 to 9. As shown in FIG. 6, when the calling side telephone 2400 makes a call via the calling side GW device 2100 (S301), the calling side GW device 2100 sends an INVITE to the called side GW device 2200 via the SIP server. (S302) (S303). Receiving side GW device 2200 which received INVITE confirms the caller number (telephone number of calling side telephone 2400) (S304).

The receiving side GW device 2200 performs the process shown in FIG. 7 in confirming the caller number (S304). That is, upon receiving the INVITE (S401), the receiving side GW device 2200 checks whether the caller number is a number already registered in the rejection list (S402). If the caller number is not registered in the rejection list (S402, No), the receiving side GW device 2200 checks whether the caller number is in an area registered in the rejection list (S403). If the caller number is not from an area registered in the rejection list (S403, No), the receiving side GW device 2200 checks the incoming call history management table stored in the incoming call history storage unit 2221 (S404). The incoming call history management table is a table in which the incoming date and time, caller number, call time, and speaking time are recorded in association with each other, as shown in FIG. 8, for example.

If it is determined that the caller number should be added to the rejection list (S405, Yes), the receiving side GW device 2200 adds the currently received caller number to the rejection list stored in the rejection list storage unit 2223 (S406). The rejection 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.

After adding the caller number, the receiving side GW device 2200 transmits 180 RINGING to the calling side GW device 2100 (S407, proceed to S305 in FIG. 6). Similarly, if the caller number is registered in the rejection list (S402, Yes) and if the caller number is from an area registered in the rejection list (S403, Yes), the receiving side GW device 2200 also sends 180 Send RINGING. If the caller number is not added to the rejection list (S405, No), the receiving-side GW device 2200 proceeds to update the rejection list based on the incoming call history of the receiving-side GW device 2200 (S202).

Returning to FIG. 6, the called GW device 2200 sends 180 RINGING to the calling GW device 2100 (S305) (S306), and the calling GW device 2100 sends RBT to the calling phone 2400. (S307).

[Updating the rejection list based on the incoming call history of the receiving side GW device 2200 (S202)]
Next, the process (S202) of updating the rejection 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 incoming GW device 2200 stores the incoming call information management table shown in FIG. Here, the receiving side GW device 2200 determines whether to register in the rejection list based on these statistical information. For example, if the caller is speaking one-sidedly, there is a high possibility that the call is a sales or solicitation call. Therefore, the receiving side GW device 2200 may add to the rejection list those caller numbers for which the speaking time from the receiving side telephone accounts for less than 10% of the call time. Furthermore, if you receive multiple calls within a few days from an area where the possibility of receiving calls is low, there is a high possibility that these are sales or solicitation calls. Therefore, the receiving side GW device 2200 uses the upper six digits up to the area code to add caller numbers that have received calls from the same area code three or more times within five days to the rejection list. You may. If it is determined by these determination processes that the caller number needs to be added to the rejection list, the receiving side GW device 2200 adds the caller number and registration form to the rejection list. The rejection list storage unit 2223 stores the rejection list shown in FIG. In the examples of FIGS. 8 and 9, the receiving GW device 2200 receives calls from the same area code three or more times within five days regarding caller numbers 03-1234-aaaa and 03-1234-cccc. The phone number 03-1234-xxxx has been added to the rejection list. In Figure 9, xxxx represents a combination of all numbers (that is, 03-1234-0001 to 03-1234-9999), and aaaa, etc. in Figures 8 and 9 represent individual numbers (that is, individual phone numbers). represents. Note that these determination processes are merely examples, and the method of utilizing statistical information for determination, the threshold value, etc. may be arbitrary values. Further, the statistical information used to determine whether to add the call to the rejection list is not limited to the date and time of incoming call, the duration of the call, and the duration of the utterance, but other statistical information may also be used.

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

In response to this request, the originating GW device 2100 returns the origination history stored in the origination history storage unit 2122 to the destination GW device 2200 (S509). This process is performed by the control unit 2110 of the originating GW device 2100. That is, the control unit 2110 in FIG. 3 also functions as the call history reply unit 2002 in FIG. 1.

The receiving side GW device 2200 analyzes the received call history (S510). The receiving side GW device 2200 performs the process shown in FIG. 11 in analyzing the calling history (S510). That is, the receiving side GW device 2200 acquires and analyzes the calling history (S601) (S602). The receiving side GW device 2200 determines whether the caller number should be added to the rejection list from this statistical information (S603). If it is determined 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 call based on the rejection list (S204). If the caller number is not added to the rejection list (S603, No), the receiving side GW device 2200 directly proceeds to reject the call based on the rejection list (S204).

The determination of whether or not to register the caller number in the rejection list (S603) will be explained in more detail. First, it is assumed that the receiving side GW device 2200 has received the outgoing call history shown in FIG. From the outgoing call history in FIG. 12, an analysis result is obtained that the called GW device 2200 makes outgoing calls to three or more locations within 15 minutes. Therefore, the receiving side GW device 2200 determines that there is a high possibility that the incoming call from the calling side phone 2400 to the called side phone 2500 is a nuisance call for the purpose of sales or solicitation. phone number) to the block list. In addition, similar to the method of updating the rejection list using the incoming call history, the caller number can also be updated in the rejection list when the caller is speaking in a one-sided manner (for example, the caller's speaking time is 90% or more). Good to add to. Further, these determination processes are merely examples, and the method of utilizing statistical information for determination, the threshold value, etc. may be arbitrary values. Further, the statistical information used to determine whether to add the call to the rejection list is not limited to the date and time of incoming call, the duration of the call, and the duration of the utterance, but other statistical information may also be used. Here, the statistical information is information that indicates the tendency of the calling history of the nuisance vendor that has been statistically analyzed, and when the calling history received by the receiving side GW device 2200 matches the tendency of the calling history of the nuisance vendor, You may also add the caller ID to the block list. Note that this process is performed by the control unit 2210 or the determination unit 2230 of the receiving-side GW device 2200.

[Call Rejection Based on Rejection List (S204)]
Next, the process (S204) of rejecting an incoming call based on the rejection list of the receiving side GW device 2200 will be explained. As shown in FIG. 13, the rejection list determination unit 2231 of the receiving side GW device 2200 reads the rejection list from the rejection list storage unit 2223 (S701), and the receiving side GW device 2200 determines that the caller number is registered in the rejection list. It is confirmed whether or not (S702). Here, if the caller number is registered in the rejection list (S702, Yes), the rejection list determination unit 2231 rejects the incoming call (rejects the INVITE) to the originating 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 user on the receiving side ends up rejecting the call without even recognizing that there was a call from the calling side.

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

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

As described above, according to the telephone management system 1000 of the present invention, it is possible to deal with nuisance calls without any user operation. That is, the receiving side GW device 2200 can automatically add a telephone number for which it has been determined that the session start request should be rejected to the rejection list. Further, the telephone management system 1000 of the present invention achieves real-time performance in that it is possible to reject incoming calls even if the telephone number is not registered on a rejection list (blacklist) provided by the police or a business.

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

As shown in FIG. 15, the storage unit 2120 of the originating GW device 2100 further includes a permission list storage unit 2124, and the determination unit 2130 further includes a permission list determination unit 2132. Similarly, the receiving side GW device 2200 further includes a permission list storage section 2224 and a permission list determination section 2232, as shown in FIG.

As shown in FIG. 17, when the calling user performs an operation to make a call from the calling phone 2400 to the called phone 2500, the calling phone 2400 requests the calling GW device 2100 to make a call. (S1001). The originating GW device 2100 transmits an INVITE (session start request) to the terminating GW device 2200 (S1002). When the receiving GW device 2200 receives the INVITE, it does not send the RINGER to the receiving phone 2500 and puts it on hold (S1003), but instead requests the calling history from the calling GW device 2100 (S1004). . In response to the request, the originating GW device 2100 returns the origination history to the terminating GW device 2200 (S1005).

The receiving side GW device 2200 analyzes the received call history of the calling side GW device 2100 and determines whether to add the telephone number of the calling side telephone 2400 to the permission list (S1006). For example, assume that the receiving GW device 2200 obtains an analysis result from the calling history of the calling GW device 2100 that the calling GW device 2100 has made a call to the same telephone number three or more times in the past. In this case, the receiving side GW device 2200 determines that there is a low possibility that the incoming call from the calling side telephone 2400 to the receiving side telephone 2500 is a nuisance call for the purpose of sales or solicitation. Then, the receiving side GW device 2200 adds the telephone number of the calling side telephone 2400 to the permission list stored in the permission list storage section 2224. Also, from the calling history of the calling side GW device 2100, if the speaking time of the caller and the called party is almost the same, or the calling time is shorter (for example, the ratio of the calling time is less than 50%) You can also add the caller ID to the allowed list.

Subsequently, 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 a RINGER to the called side telephone 2500, but sends a call rejection (INVITE rejection) 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 transmits RINGER to the receiving side telephone 2500. Then, after confirming the OFF-Hook of the receiving side telephone 2500, the receiving side GW device 2200 notifies the calling side GW device 2100 that it has accepted the session start request, and starts a call.

As described above, according to the telephone management system 1000 of the present invention, it is possible to deal with nuisance calls without any user operation. That is, even if the troublesome business operator does not install the gateway device 2000 of the present invention and does not return the call history, the receiving side gateway device 2200 will reject the call.

Note that, for example, the permission list may be updated based not only on the calling history of the calling side GW device 2100 but also on the calling history of the receiving side GW device 2200. For example, the telephone number registered in the calling history of the receiving side GW device 2200 is a phone number to which the receiving side user voluntarily made a call in the past. ). Therefore, the telephone number registered in the calling history of the receiving side GW device 2200 may be registered in the permission list. Further, for example, in the calling history of the receiving side GW device 2200, if the speaking time of the caller and the called party is approximately the same, or the speaking time of the called party is longer, there is a high possibility that the callers are acquaintances. Therefore, if the speaking time of the called party accounts for 50% or more of the call time, the destination number may be added to the permission list. Also, if you have been calling the same number in a short period of time, there is a high possibility that the number you are calling is someone you know, so if you have called the same number three or more times within a week, that number will be added to your allowed list. may be added to. Furthermore, if you make a call to the same area within a short period of time, there is a high possibility that you have many acquaintances in that area, so if you make a call to a 6-digit number that includes the same area code three or more times within an hour, You may also add a six-digit number, including area code, to the allowed list.

[Variation form]
The present invention can be implemented as a telephone management method using a computer 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, a computer serving as the gateway device 2000 includes a CPU (Central Processing Unit: equivalent to control units 2110 and 2210), a memory (corresponding to storage units 2120 and 2220), and an interface. The present invention can be realized by the CPU reading a program from memory and implementing modules corresponding to the calling history requesting section 2001, the calling history replying section 2002, and the determining section 2003.

Part or all of the above embodiments may be described as in the following additional notes, but are not limited to the following.

(Additional note 1)
at least two gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call;
Each of the gateway devices
a calling history requesting unit that requests a calling history from the calling device when a session start request is received from the calling device;
a calling history reply unit that returns its own calling history to the called device when receiving a request for the calling history from the called device;
a determination unit that analyzes the calling history received from the calling device to determine whether or not to accept the session start request;
A telephone management system equipped with

(Additional note 2)
Each of the gateway devices
a rejection list storage unit that stores a rejection list listing telephone numbers whose session start requests are determined to be rejected by the determination unit;
a request rejection unit that rejects a session start request from a telephone number registered in the rejection list;
The telephone management system according to supplementary note 1, further comprising:

(Additional note 3)
The telephone management system according to appendix 1, wherein the determination unit rejects the session start request if it is found from the call history that the number of calls within a predetermined time exceeds a threshold value.

(Additional note 4)
The telephone management system according to supplementary note 1, wherein the determination unit rejects the session start request when finding a call history in which a ratio of speaking time to call time exceeds a threshold value.

(Appendix 5)
The telephone management system according to supplementary note 1, wherein the determination unit rejects the session start request based on statistical information of a call history.

(Appendix 6)
Each of the gateway devices
a permission list storage unit that stores a permission list listing telephone numbers determined by the determination unit to accept a session start request;
a session initiator that starts a session from a phone number registered in the permission list;
The telephone management system according to supplementary note 1, further comprising:

(Appendix 7)
At least two computers serving as gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call,
When receiving a session start request from the calling device, requesting the calling device for a call history;
When receiving a request for the calling history from the called device, a step of replying its own calling history to the called device;
analyzing the call history received from the calling device to determine whether to accept the session start request;
How to manage your phone.

(Appendix 8)
at least two computers serving as gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call;
When a session start request is received from a calling device, a process of requesting a call history from the calling device;
When receiving a request for the calling history from the called device, a process of replying the calling history to the called device;
Analyzing the call history received from the calling device to determine whether to accept the session start request;
A phone management program that runs

It should be noted that the disclosures of the above-mentioned patent documents and the like cited above are incorporated into this book by reference, and can 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 claims), changes and adjustments to the embodiments and examples are possible based on the basic technical idea thereof. In addition, various combinations or selections 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 within the framework of the entire disclosure of the present invention. (including partial deletion) is possible. That is, it goes without saying that the present invention includes the entire disclosure including the claims and various modifications and modifications that a person skilled in the art would be able to make in accordance with the technical idea. In particular, numerical ranges stated herein should be construed as specifically stating any numerical value or subrange within the range, even if not otherwise stated. Furthermore, each of the disclosures in the documents cited above may be used, in part or in whole, in combination with the statements in this book as part of the disclosure of the present invention, if necessary, in accordance with the spirit of the present invention. It is deemed to be included in the disclosure of this application.

1000: Telephone management system 2000: Gateway device 2001: Call history request unit 2002: Call history reply unit 2003: Judgment unit 2100: Calling side GW device 2110: Control unit 2111: Storage unit control unit 2112: Judgment unit control unit 2113: Network Control unit 2114: Telephone function control unit 2120: Storage unit 2121: Incoming call history storage unit 2122: Outgoing call history storage unit 2123: Rejection list storage unit 2124: Permission list storage unit 2130: Determination unit 2131: Rejection list determination unit 2132: Permission list Judgment unit 2140: Network interface 2150: Telephone interface 2200: Receiving side GW device 2210: Control unit 2211: Storage unit control unit 2212: Judgment unit control unit 2213: Network control unit 2214: Telephone function control unit 2220: Storage unit 2221: Incoming call History storage unit 2222 : Call history storage unit 2223 : Rejection list storage unit 2224 : Permission list storage unit 2230 : Determination unit 2231 : Rejection list determination unit 2232 : Permission list determination unit 2240 : Network interface 2250 : Telephone interface 2300 : Internet 2400 : Calling side telephone 2500: Receiving side telephone

Claims (8)

at least two gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call;
Each of the gateway devices
a calling history requesting unit that requests a calling history from the calling device when a session start request is received from the calling device;
a calling history reply unit that returns its own calling history to the called device when receiving a request for the calling history from the called device;
a determination unit that analyzes the calling history received from the calling device to determine whether or not to accept the session start request;
A telephone management system equipped with Each of the gateway devices
a rejection list storage unit that stores a rejection list listing telephone numbers whose session start requests are determined to be rejected by the determination unit;
a request rejection unit that rejects a session start request from a telephone number registered in the rejection list;
The telephone management system according to claim 1, further comprising: The telephone management system according to claim 1, wherein the determination unit rejects the session start request if it is found from the call history that the number of calls within a predetermined time exceeds a threshold value. The telephone management system according to claim 1, wherein the determination unit rejects the session start request when finding a call history in which the ratio of speaking time to call time exceeds a threshold value. The telephone management system according to claim 1, wherein the determination unit rejects the session start request based on statistical information of a call history. Each of the gateway devices
a permission list storage unit that stores a permission list listing telephone numbers determined by the determination unit to accept a session start request;
a session initiator that starts a session from a phone number registered in the permission list;
The telephone management system according to claim 1, further comprising: At least two computers serving as gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call,
When receiving a session start request from the calling device, requesting the calling device for a call history;
When receiving a request for the calling history from the called device, a step of replying its own calling history to the called device;
analyzing the call history received from the calling device to determine whether to accept the session start request;
How to manage your phone. at least two computers serving as gateway devices that can serve as either a calling device for making a call and a receiving device for receiving a call;
When a session start request is received from a calling device, a process of requesting a call history from the calling device;
When receiving a request for the calling history from the called device, a process of replying the calling history to the called device;
Analyzing the call history received from the calling device to determine whether to accept the session start request;
A phone management program that runs

Images