JP2010062894A - Telephone device performing interrupt call request notification - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for decreasing chances wherein a telephone call is disturbed, and for giving a chance to accept a call request to a user who makes a telephone call. <P>SOLUTION: A telephone body 20 determines whether there is a speech communication device which has an in-standby status and has a ringing rejection flag set OFF, and makes the speech communication device perform call request notification when the device is present. When there is not such a speech communication device, the telephone body 20 makes the speech communication device which has an in-calling status and also has a ringing rejection flag set OFF, perform interrupt call request notification. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a telephone device. In particular, the present invention relates to a telephone device capable of executing an interrupt call request notification. Note that the term “notified call request notification” is to be interpreted in the broadest sense, and refers to various methods capable of notifying the user that a call request has been received by the telephone device during the call. It is a concept that includes. As an example of the interrupt call request notification, it is possible to output sound at the call device, vibrate the call device, or the like.

  For example, as in Patent Document 1, there is a telephone device having a plurality of slave units. In this telephone device, when a call request is received during a call in any of the plurality of slave units, a call request notification is executed only in another standby slave unit.

Japanese Patent Laid-Open No. 2001-24815

  However, a call is not always started by a slave unit that is in a standby state where a call request notification is executed. Even if it is certain that the user of the slave unit that is waiting does not intend to respond to the call request, and the user of the slave unit that is talking may possibly respond to the call request, the above patent In the technique of Literature 1, it is not notified that a call request has been received by a slave unit that is in a call. Therefore, the user who is talking cannot know that the call request has been received. For this reason, the opportunity which can respond to a telephone call request will decrease.

  The present specification provides a technique that can give a user who is in a call an opportunity to respond to a call request.

  The telephone device disclosed in this specification includes status acquisition means, call request reception means, call request notification means, call request notification stop means, and interrupt call request notification means. This telephone device may perform telephone communication using a general public network (PSTN (Public Switched Telephony Network) or ISDN (Integrated Services Digital Network)), or may use an IP network. A telephone communication may be performed. That is, the telephone device may be a general telephone or an IP telephone. Further, the telephone device may perform telephone communication using both a general public line network and an IP network. Note that the telephone device may have only a telephone communication function, or may be a multi-function device having a telephone communication function and other functions (for example, a facsimile communication function).

  The status acquisition means acquires the status of each of the plurality of call devices. Examples of the status of the calling device include a busy status and a standby status. The call request receiving means receives a call request. The call request notification means causes the call device having the standby status to execute a call request notification on condition that the call request is received by the call request receiving means. Note that the call request notification means may give notification by sound, for example, may give a predetermined display, or may vibrate. When the call request notification is executed, the user can know that a call has been received.

  For example, the telephone device may have a parent device and a child device as a calling device. In this case, the call request notification means may transmit a call request notification instruction to the child device. When receiving the call request notification instruction, the slave unit may execute the call request notification. In this case, call request notification means by means for instructing call request notification to the slave unit (means possessed by the master unit) and means for executing call request notification in accordance with the call request notification instruction (means possessed by the slave unit) Will be configured. Further, the telephone device may be configured only by the parent device. The call device of the parent device may be a cordless type or a type that is connected to the parent device main body by wire. In the former case, the call request notification means may transmit a call request notification instruction to the call device of the parent device, for example. When the call device of the parent device receives the call request notification instruction, the call device may execute the call request notification.

  The call request notification stop means stops the call request notification on the condition that the first operation is executed in the call device that is executing the call request notification. The user can stop the call request notification while the call request notification (for example, a ringing tone) is being executed. Call request notification when the user does not want to answer the call (for example, when he wants to make a call) even if the call device is not used for a call (waiting status) when the call request is received Can be stopped. The method for executing the first operation is not particularly limited. For example, the user may perform the first operation by operating a predetermined key (for example, a numeric keypad) disposed on the call device.

  The interrupt call request notification means interrupts a call to the call device on the condition that the first operation is executed in all the call devices executing the call request notification and there is a call device having a busy status. Request notification is executed. That is, the interrupt call request notification means causes the call device having the busy status to execute the interrupt call request notification when all the call devices having the standby status do not respond to the call request. For example, the interrupt call request notification means may notify by sound, may display a predetermined display, or may vibrate. When the interrupt call request notification is executed, the user can know that a call has been received during a call.

  Note that the term “provided that the first operation is executed in all the call devices that are executing the call request notification and there is a call device having a busy status” is the other condition ( The addition of an AND condition and / or an OR condition is not excluded. Even in the following description, when the term “as a condition” is used, it does not exclude the addition of other conditions (AND condition and / or OR condition).

  The interrupt call request notification means may cause all call devices to execute an interrupt call request notification when all the call devices have a busy status when the call request is received. In this case, the first operation is not executed in any of the call devices, but the interrupt call request notification means can execute the interrupt call request notification.

  According to the above telephone apparatus, when a call request is received, a call device with a waiting status can be notified preferentially to a call device with a waiting status (a call request notification is executed) over a call device with a calling status. . Since the interrupt call request notification is not executed in the calling device during a call, the call is not disturbed. You can reduce the chance of disturbing the call. On the other hand, when the call request cannot be satisfied in all the call devices having the standby status (that is, when the first operation is executed), the interrupt call request notification is executed to the call device having the call status. As a result, the user during the call can know that the call request has been received and can respond to the call request. It can suppress that the opportunity which can respond to a telephone call request reduces.

  The telephone device may further include a call request transmission unit. The call request transmission means may transmit a call request on condition that a call preparation operation is executed in any of the call devices. The interrupt call request notifying means is configured to receive a call request by the call request receiving means while the busy status is established as a result of execution of the call preparation operation in the call device on which the first operation is executed. It may be prohibited to cause the call device to execute an interrupt call request notification.

  If the user makes a call after performing the first operation, the call is likely to be important. According to the above configuration, since the interrupt call request notification is not executed when the user makes a call after executing the first operation, the call that is expected to be important is not disturbed.

  The telephone device may further include interrupt call request notification stop means. The interrupt call request notification stop means executes the second operation on the condition that the second operation is executed on the call device while the call device having the busy status is executing the interrupt call request notification. The interrupt call request notification may be stopped while maintaining the call ready state constructed in the call device. According to this configuration, even if the interrupt call request notification is executed during a call, the user can stop the interrupt call request notification if the user does not want to disturb the call.

  The method for executing the second operation is not particularly limited. For example, the user may perform the second operation by operating a predetermined key (for example, a numeric keypad) disposed on the call device. Further, the first operation and the second operation may be the same operation or different operations.

  The telephone device may further include a negative response transmission unit. The negative response transmission means transmits a negative response to the call request received by the call request reception means on condition that the second operation has been executed in all the call devices that are executing the interrupt call request notification. May be. This “state in which the second operation is executed in all the calling devices that are executing the interrupt call request notification” means that the users of all the calling devices having the calling status and the standby status cannot answer the call. is there. In this case, the negative response transmission means may notify the transmission source of the call request as a negative response that the call request cannot be answered, or send the voice message for answering that has been set in advance to transmit the call request. It may be sent to the original. The latter case is equivalent to sending a negative response.

  The negative response transmission means is a call received by the call request receiving means on condition that a predetermined time has elapsed without executing the second operation in all the call devices that are executing the interrupt call request notification. A negative response to the request may be sent. In this case, a negative response is transmitted even if the second operation is not executed.

  The call request notifying means is provided to the first call device while the second operation is executed in the first call device that is executing the interrupt call request notification and the second call device is executing the interrupt call request notification. The call request notification may be executed by the first call device on condition that the built-in call available state is disconnected.

  According to this configuration, not only can the second call device execute the interrupt call request notification, but also the first call device that has finished the call can execute the call request notification. Opportunities for responding to call requests can be further increased.

  The call request notification means is configured to execute the second operation on the first call device that is executing the interrupt call request notification, and the first call device while the second call device is executing the call request notification. The call request notification may be executed by the first call device on the condition that the call has ended.

Here, some of the features of the techniques described in the following embodiments are summarized.
(Mode 1) The telephone device may perform telephone communication using an IP network.
(Mode 2) The telephone device may perform telephone communication using SIP (Session Initiation Protocol). Other protocols may be used. For example, “H.323”, “MGCP (Media Gateway Control Protocol)”, “H.248 / MEGACO (Media Gateway Control)”, or the like may be used.
(Mode 3) In the case of mode 2, the call request may be an INVITE command. The positive response to the call request may be 200 OK. The negative response to the call request may be 486 Busy Here.
(Mode 4) In the case of mode 2, the data communication session may be RTP (Real-time Transport Protocol). RTP can be rephrased as a real-time data communication protocol.

(Mode 5) The interrupt call request notifying means does not execute the second operation while the call ready state is established, and calls by the call request receiving means while the call enable state is established. The interrupt call request notification may be executed on condition that the request is received. The interrupt call request notifying means is executing the second operation while the call ready state is established, and the call request receiving means has received the call request while the call enable state is being established. On the condition of this, execution of the interrupt call request notification may be prohibited.

(Mode 6) In the telephone device, a value storage unit capable of storing the first value or the second value, and a state in which a call can be made is constructed in a state where the first value is stored in the value storage unit. On the condition that the second value is stored in the value storage means on the condition that the second operation has been executed in the meantime, and that the call available state is disconnected while the second value is stored in the value storage means Storage control means for storing the first value in the value storage means may be further provided. The interrupt call request notifying means is configured to provide an interrupt call request on condition that a call request is received by the call request receiving means while a call ready state is established with the first value stored in the value storage means. Notification may be executed. The interrupt call request notifying means receives an interrupt call request on the condition that the call request is received by the call request receiving means while the call ready state is established with the second value stored in the value storage means. It may be prohibited to execute the notification.

  Embodiments will be described with reference to the drawings. FIG. 1 shows a telephone network system 2 of the present embodiment. The telephone network system 2 includes a plurality of extension networks 10 and 110, the Internet 104, a SIP server 106, and the like. Although only two extension networks 10 and 110 are shown in FIG. 1, there are actually a large number of extension networks.

  A plurality of SIP URIs are assigned to the extension network 10. The extension network 10 includes a telephone body 20 and a plurality of call devices 50, 70, 80. Note that SIP URIs are not allocated individually to each of the call devices 50, 70, 80, but a plurality of SIP URIs are allocated for each extension network 10. The telephone body 20 is connected to the Internet 104 (IP network). Each of the call devices 50, 70, 80 configuring the extension network 10 can perform telephone communication using the Internet 104. That is, the extension network 10 functions as an IP phone.

  A plurality of SIP URIs are also assigned to the extension network 110. The extension network 110 includes a telephone main body 120 and a plurality of call devices 150 and 160. The telephone main body 120 is connected to the Internet 104. Each of the call devices 150 and 160 constituting the extension network 110 can perform telephone communication using the Internet 104. That is, the extension network 110 functions as an IP phone.

  The SIP server 106 stores SIP URIs of the extension networks 10 and 110 (that is, telephone identification information of the extension networks 10 and 110). The SIP server 106 is connected to the Internet 104. The SIP server 106 controls telephone communication between the extension networks 10 and 110 using SIP. That is, various commands communicated for telephone communication between the extension network 10 and the extension network 110 are transmitted via the SIP server 106.

(Configuration of the phone body)
The configuration of the telephone body 20 will be described. The telephone main body 20 controls the telephone communication of each of the call devices 50, 70, 80 in an integrated manner. That is, each of the call devices 50, 70, 80 can perform telephone communication with the outside of the extension network 10 via the telephone main body 20. FIG. 2 shows the configuration of the telephone body 20. The telephone main body 20 includes a main body side control unit 22, a wireless communication interface 24, a network interface 26, a storage unit 28, an operation unit 34, a display unit 36, and the like. The main body side control unit 22 executes various processes in accordance with programs stored in the storage unit 28. The contents of the process executed by the main body side control unit 22 will be described in detail later. The wireless communication interface 24 is an interface for performing wireless communication with each of the call devices 50, 70, 80. A LAN line 100 is connected to the network interface 26. The LAN line 100 is connected to the Internet 104. The telephone body 20 can access the Internet 104 via the network interface 26 and the LAN line 100.

  The storage unit 28 includes a ROM, an EEPROM, a RAM, and the like. The storage unit 28 includes a call device information storage area 30 and other storage areas 32. The call device information storage area 30 stores call device information of the call devices 50, 70, and 80. FIG. 3 shows an example of the stored contents of the call device information storage area 30. The call device information storage area 30 can store a plurality of combination data 300, 302, and 304. Each combination data 300, 302, and 304 is obtained by associating a call device ID 310, a status 312, and a ringing rejection flag 314. In the present embodiment, the call device ID 310 of the call device 50 is “1”. The call device ID 310 of the call device 70 is “2”. The call device ID 310 of the call device 80 is “3”.

  In this embodiment, two statuses of “standby” and “busy” are adopted as the status of the calling device. The ringing rejection flag 314 employs two values “ON” and “OFF”. When the ring rejection flag 314 of the call device is OFF, the main body side control unit 22 causes the call device to execute a call request notification and an interrupt call request notification described later. When the ring rejection flag 314 of the call device is ON, the main body side control unit 22 prohibits the call device from executing a call request notification and an interrupt call request notification described later. How information is stored in the call device information storage area 30 will be described in detail later. The storage area 32 can store information other than the information to be stored in the call device information storage area 30.

  The operation unit 34 has a plurality of keys. The user can input various information to the telephone body 20 by operating the operation unit 34. The display unit 36 can display various information.

(Call device configuration)
Next, the configuration of the call device 50 will be described. The call devices 70 and 80 have the same configuration as the call device 50. For this reason, detailed description of the call devices 70 and 80 is omitted. The telephone device 50 of this embodiment is a cordless type. FIG. 4 shows the configuration of the call device 50. The call device 50 includes a device-side control unit 52, a wireless communication interface 54, an operation unit 56, a display unit 58, a speaker 60, a microphone 62, a storage unit 64, and the like. The device-side control unit 52 executes various processes according to programs stored in the storage unit 64. Details of processing executed by the device-side control unit 52 will be described in detail later. The wireless communication interface 54 is an interface for performing wireless communication with the telephone body 20. The call device 50 is set with a call device ID (see reference numeral 310 in FIG. 3). When the call device 50 transmits information to the telephone body 20 using the wireless communication interface 54, the call device 50 adds the call device ID set for the call device 50 to the above information. Thereby, the telephone main body 20 can specify which of the call devices 50, 70, 80 is the information.

  The operation unit 56 has a plurality of keys. For example, the operation unit 56 includes a hook key and a numeric keypad. The call device 50 is in an on-hook state when not in use. The user can operate the hook key when making a call using the call device 50. Thereby, the telephone device 50 enters an off-hook state. Next, the user inputs the telephone identification information (SIPURI) of the destination of INVITE into the call device 50 by operating the numeric keypad (or operating a speed dial or the like). Thereby, the user can make a phone call. Hereinafter, inputting the telephone identification information with the hook key in the off-hook state is referred to as “call preparation operation”. In addition, the user can put the call device 50 in an off-hook state by operating the hook key while a call is being made (during a call request notification). Thereby, the user can take a telephone call. Hereinafter, setting an off-hook state in a state where a call is received is referred to as a “call start operation”.

  The user can stop the call request notification by operating a predetermined key of the operation unit 56 in a state where a call is received. Further, the user can stop the interrupt call request notification by operating the predetermined key of the operation unit 56 in a state where a call is received during a call. Hereinafter, stopping the call request notification or the interrupt call request notification is collectively referred to as a “ring rejection operation”. The predetermined key is referred to as a “ring rejection key”. In addition, the user can place the calling device 50 in an on-hook state by operating a hook key in a calling state. Thereby, the user can disconnect the telephone. Hereinafter, the on-hook state in a call state is referred to as “call end operation”.

  The display unit 58 can display various information. The user can make a call using the speaker 60 and the microphone 62. The storage unit 64 stores a program to be executed by the device side control unit 52. Further, the storage unit 64 can store its own call device ID, data generated in the process of the device side control unit 52 executing the process, and the like.

  The telephone main body 120 constituting the extension network 110 has the same configuration as the telephone main body 20. The telephone main body 120 can access the Internet 104 via the LAN line 102. Further, the call devices 150 and 160 constituting the extension network 110 have the same configuration as the call device 50.

(Processing executed by the phone itself)
Then, the content of the process which the main body side control part 22 of the telephone main body 20 performs is demonstrated. 5 to 7 show a flowchart of the telephone main process.

  The main body side control unit 22 determines whether a call preparation instruction has been received from the call devices 50, 70, 80 (S10). In the case of YES here, the main body side control unit 22 executes the processes shown in S12 to S20. In the case of NO in S10, the main body side control unit 22 proceeds to S24.

  The processing after S12 will be described by taking as an example a case where a call preparation instruction is received from the calling device 50 in S10. The call preparation instruction includes the ID of the call device 50 and the SIP URI (for example, the SIP URI of the extension network 110) input by the user. The main body side control unit 22 changes the stored contents stored in the call device information storage area 30 (S12). Specifically, the main body control unit 22 changes the status 312 of the calling device 50 from “standby” to “busy”.

  The main body side control unit 22 transmits INVITE to the SIP server 106 (S14). This INVITE includes the SIP URI of the extension network 10 that is the transmission source and the SIP URI of the extension network 110 that is the transmission destination. In S14, the main body side control unit 22 may create information (call ID in this embodiment) for identifying individual INVITEs and transmit INVITEs including the call IDs. The call ID may be stored in the call device information storage area 30 in association with the call device 50 (that is, the call device ID “1”). INVITE is transferred to the extension network 110 (the telephone main body 120) by the SIP server 106.

  The main body side control unit 22 monitors that 200 OK is received from the SIP server 106 (S16). When a call start operation is executed in any of the call devices 150 and 160 of the extension network 110, the telephone main body 120 transmits 200 OK as a response to INVITE. The 200 OK is transferred to the extension network 10 by the SIP server 106. In the case of YES in S16, the main body side control unit 22 transmits ACK to the SIP server 106 (S18). The ACK is transferred to the extension network 110 by the SIP server 106. As a result, the main body control unit 22 establishes a call-enabled state between the extension network 10 and the extension network 110 (S20). That is, an RTP session is established. The user of the call device 50 can make a call with the user to whom INVITE is transmitted.

  Note that, in the present embodiment, when “Y is transmitted as a response to X” is described, Y is information specifying that it is a response to X, and the Y transmission source (that is, the X transmission destination). It means that the information and the information of the Y transmission destination (that is, the X transmission source) are included. For example, in the case of the above description “200 OK is transmitted as a response to INVITE”, the information specifying that 200 OK is a response to INVITE, the SIP URI of the extension network 110 that is the transmission source of 200 OK, 200 SIP transmission destination SIP URI of the extension network 10 is included.

  In S24, the main body side control unit 22 determines whether or not INVITE has been received. If YES here, INVITE reception processing is executed (S26). If NO in S24, the process proceeds to S44 in FIG.

  The INVITE reception process executed in S26 will be described. FIG. 8 shows a flowchart of the INVITE reception process. The processing of FIG. 8 will be described by taking as an example the case where INVITE is received from the extension network 110 in S24 of FIG. The main body side control unit 22 turns OFF the ringing refusal flag 314 of the combination data 300, 302, and 304 having the “standby” status 312 by referring to the stored contents of the call device information storage area 30 (S28). . In this process, if the ringing rejection flag 314 is ON for a call device having a standby status, it is changed to OFF. On the other hand, when the ringing rejection flag 314 is OFF, it is maintained.

  Subsequently, the main body control unit 22 refers to the stored contents of the call device information storage area 30 to determine whether there is a call device whose ringing rejection flag 314 is OFF (S30). If NO here, the process proceeds to S40. If YES in S30, the main body control unit 22 transmits 180 Ringing as a response to the INVITE received in S24 (S32). The 180 Ringing is transferred to the telephone main body 120 of the extension network 110 by the SIP server 106. Thereby, the user of the INVITE transmission source can know that the call request is being notified (calling).

  In S <b> 34, the main body control unit 22 refers to the stored contents of the call device information storage area 30 to determine whether there is a call device that is in the standby status and whose ringing rejection flag 314 is OFF. to decide. In the case of YES here, the main body side control unit 22 transmits a call request notification instruction to a call device that is in the standby status and whose ringing rejection flag 314 is OFF (S36). For example, when the content shown in FIG. 3 is stored in the call device information storage area 30, the main body control unit 22 transmits a call request notification instruction to the call device (that is, the call device 50) of the combination data 300. When S36 ends, the process proceeds to S40.

  On the other hand, in the case of NO in S34, there is a call device (call device 70 with call device ID “2” in the example of FIG. 3) that is in a call status and whose ringing rejection flag 314 is OFF. The main body side control unit 22 identifies the above-described call device by referring to the stored contents of the call device information storage area 30. The main body side control unit 22 transmits an interrupt call request notification instruction to the specified call device (for example, the call device 70) (S38). When S38 ends, the process proceeds to S40.

  In S <b> 40, the main body control unit 22 transmits 486 Busy Here to the SIP server 106. The user of the INVITE transmission source can know that a call cannot be made. When S40 ends, the INVITE reception process ends.

  Although not shown in the flowchart, even if a call request notification instruction or an interrupt call request notification instruction is transmitted to the call device in S36 or S38, if there is no response described later from any call device, a predetermined You may perform the process of S40 on the condition that time passed. The user of the INVITE transmission source can know that a call cannot be made.

  In S44 of FIG. 6, the main body side control unit 22 determines whether or not a call start instruction is received from the call device after receiving INVITE. If NO here, the process proceeds to S56. If YES in S44, the main body control unit 22 executes the processes shown in S46 to S54. If a call start operation is executed in the call device that is executing the call request notification, YES is determined in S44 as a result of the call start instruction being transmitted from the call device having the standby status. On the other hand, when a call start operation is executed in the call device that is executing the interrupt call request notification, YES is determined in S44 as a result of the call start instruction being transmitted from the call device having the busy status.

  The main body side control unit 22 changes the stored content of the status 312 of the calling device that has transmitted the call start instruction to “busy” (S46). For example, when a call start instruction is received from the call device 50 in the standby status, the main body side control unit 22 sets the status 312 of the call device 50 (combination data 300) stored in the call device information storage area 30. Change the stored content to “During a call”.

  Subsequently, the main body side control unit 22 transmits a call request notification stop instruction to all the call devices (S48). The call request notification stop instruction is an instruction for stopping both the call request notification and the interrupt call request notification. By transmitting the call request notification stop instruction, the call request notification can be stopped when the call device 50, 70, 80 is executing the call request notification, and the call device 50, 70, 80 is notified of the interrupt call request. When the call is executed, the interrupt call request notification can be stopped.

  When the main body side control unit 22 transmits the call request notification stop instruction in S48, the main body side control unit 22 identifies the call device that is executing the call request notification and / or the interrupt call request notification, and requests the call only from the call device. A notification stop instruction may be transmitted.

  The main body side control unit 22 transmits 200 OK to the SIP server 106 (S50). The telephone body 20 receives an ACK from the SIP server 106 (S52). The main body control unit 22 establishes a call-enabled state between the INVITE transmission source and the call device 50 that has transmitted the call start instruction (S54).

  Note that if YES is determined in S44 as a result of a call start instruction being transmitted from a call device having a busy status, the call device has a busy status. For this reason, the process of S46 is skipped. .

  Although not shown in the flowchart, if it is determined YES in S44 as a result of a call start instruction being transmitted from a call device having a busy status, a process for switching the call partner of the call device is executed. The

  In S <b> 56, the main body control unit 22 determines whether or not a ringing refusal instruction has been received from the call devices 50, 70, and 80. If NO here, the process proceeds to S62 in FIG. In the case of YES in S56, the main body side control unit 22 executes the processes shown in S58 to S60.

  In S58, the main body side control unit 22 transmits a call request notification stop instruction to the call device that has transmitted the ringing rejection instruction. The call request notification stop instruction is an instruction for stopping both the call request notification and the interrupt call request notification.

  Next, the main body side control unit 22 changes the stored contents of the call device information storage area 30 (S60). That is, the main body side control unit 22 turns on the ringing rejection flag 314 of the calling device that has transmitted the ringing rejection instruction. When S60 ends, the process proceeds to S30 in FIG.

  By proceeding to S30 of the INVITE reception process after S60, various processes are executed as follows. These processes will be described in detail.

(1) For example, when a call request notification is executed in all the call devices 50, 70, 80, and a ringing rejection instruction is received from one of the call devices 50, YES is determined in S56 of FIG. Is done. Since the ringing rejection flag of the calling devices 70 and 80 is OFF, YES is determined in S30 of FIG. Moreover, since the call devices 70 and 80 have the standby status and the ringing rejection flag is OFF, YES is determined in S34. Accordingly, a call request notification instruction is transmitted to the call devices 70 and 80 (S36). Since the call devices 70 and 80 have already executed a call request notification, the main body side control unit 22 does not have to transmit a call request notification instruction. Next, when a ringing rejection instruction is received from the calling device 70, YES is determined again in S56 of FIG. Since the ringing rejection flag of the call device 80 is OFF, YES is determined in S30 of FIG. Since the calling device 80 has a standby status and the ringing rejection flag is OFF, YES is determined in S34. Accordingly, a call request notification instruction is transmitted to the call device 80 (S36). Subsequently, when a ringing rejection instruction is received from the calling device 80, YES is determined again in S56 of FIG. Since there is no call device whose ringing rejection flag is OFF, NO is determined in S30 of FIG. As a result, 486 Busy Here is transmitted to the SIP server 106.

(2) For example, when a call request notification is executed in the call device 50, the call devices 70 and 80 have a busy status, and a ringing rejection instruction from the call device 50 is received, 6 is determined to be YES. When the ringing rejection flag is ON in both of the call devices 70 and 80, NO is determined in S30 of FIG. As a result, 486 Busy Here is transmitted to the SIP server 106. On the other hand, if the ringing rejection flag is OFF in at least one of the call devices 70 and 80, YES is determined in S30 of FIG. Moreover, since the calling devices 70 and 80 have a busy status, NO is determined in S34. Therefore, an interrupt call request notification instruction is transmitted to the call devices 70 and 80 (S38).

(3) For example, when an interrupt call request notification is executed in all the call devices 50, 70, and 80, and a ringing rejection instruction is received from one of the call devices 50, YES in S56 of FIG. To be judged. Since the ringing rejection flag of the calling devices 70 and 80 is OFF, YES is determined in S30 of FIG. Moreover, since the calling devices 70 and 80 have a busy status, NO is determined in S34. Therefore, an interrupt call request notification instruction is transmitted to the call devices 70 and 80 (S38). Since the call devices 70 and 80 have already executed the interrupt call request notification, the main body side control unit 22 does not need to transmit the interrupt call request notification instruction.

  In S62 of FIG. 7, the main body side control unit 22 determines whether or not a call end instruction has been received from the call device. If NO here, the process proceeds to S72. In the case of YES in S62, the main body side control unit 22 executes the processes shown in S64 to S70.

  The process shown in S64 to S70 will be described by taking as an example a case where a call end instruction from the call device 50 is received in S62. The main body control unit 22 transmits a call request notification stop instruction to the call device 50 that has transmitted the call end instruction (S64). If the call device 50 is executing the interrupt call request notification when the call device 50 transmits the call end instruction, the interrupt call request notification is stopped. If the call device 50 has not executed the interrupt call request notification when the call device 50 has transmitted the call end instruction, the call device 50 ignores the call request notification stop instruction transmitted in S64. .

  Although not shown in the flowchart, the main body side control unit 22 executes a process for determining whether or not the call device 50 is executing an interrupt call request notification, and if it is determined to be YES, the call request is performed. A notification stop instruction may be transmitted.

  Next, the main body side control unit 22 disconnects the call enabled state of the call device 50 (S65). Subsequently, the main body side control unit 22 turns off the ringing rejection flag 314 of the calling device 50 (S66). Further, the main body side control unit 22 changes the stored content of the status 312 of the call device 50 (combination data 300) to “standby”.

  Next, the main body control unit 22 determines whether or not it is in a state of waiting for reception of a call start instruction after receiving INVITE in S24 of FIG. 5 (S70). This state is, for example, that no call start instruction has been received from any of the call devices 50, 70, 80 since INVITE was received, 486 Busy Here has not been transmitted to the INVITE, and The BYE from the INVITE transmission source is not received. Hereinafter, this state is referred to as an incoming call.

  If YES in S70, the process proceeds to S34 in FIG. Since the ringing refusal flag of the calling device 50 is turned off (S66) and the status of the calling device 50 is changed to the standby status (S68), YES is determined in S34. As a result, the main body side control unit 22 transmits a call request notification instruction to the call device 50 that has ended the call (S36). Accordingly, when the call device 50 is receiving a call when the call is finished, the call device 50 can be notified of a call request. Opportunities for responding to call requests can be increased.

  When a call start operation is executed in the call device (for example, call device 50) in response to the interrupt call request notification, the call device 50 has a call ready state established with one of the other call partners. The call-enabled state with the other call partner is on hold. In this state, if a call end operation is executed in the call device 50 and YES is determined in S62, the call-enabled state with the one other party is disconnected in S65. Next, although not shown in the flowchart, the main body side control unit 22 again establishes a call-enabled state with the other call partner in the hold state (that is, switches the call partner). The main body side control unit 22 skips S66 to S70.

  In the case of NO in S62, the main body control unit 22 determines whether BYE has been received (S72). If YES here, the process proceeds to S64. If NO in S72, the process returns to S10 in FIG. 5 and the telephone main process is executed again.

(Processing performed by the calling device)
Next, the contents of processing executed by the device side control unit 52 of the call device 50 will be described. The processing executed by the calling devices 70 and 80 is the same as that of the calling device 50. 9 to 10 show flowcharts of the call device main process.

  The device-side control unit 52 determines whether a call preparation operation has been executed by the user (S80). If NO here, the process proceeds to S90. If YES in S80, the device-side control unit 52 transmits a call preparation instruction to the telephone body 20 (S82). The call preparation instruction includes the ID of the call device 50 and the SIP URI of the INVITE transmission destination (for example, the extension network 110). The SIP URI of the INVITE transmission destination can be input by the user operating the operation unit 56 of the call device 50 in advance and stored in the storage unit 64. When the process of S82 is executed, the main body control unit 22 determines YES in S10 of FIG. 5 and executes the processes of S12 to S20. A callable state is established in the call device 50. A call can be initiated between the user of the call device 50 and the user of the call device (eg, call device 150) of the extension network 110.

  In S90, the device-side control unit 52 determines whether or not a call request notification instruction transmitted from the telephone body 20 is received in the process of S36 in FIG. If NO here, the process proceeds to S94. If YES in S90, the device-side control unit 52 executes a call request notification (S92). In S94, the device-side control unit 52 determines whether or not the interrupt call request notification instruction transmitted from the telephone main body 20 is received in the process of S38 in FIG. If NO here, the process proceeds to S98. If YES in S94, the device-side control unit 52 executes an interrupt call request notification (S96).

  In S98, the device-side control unit 52 determines whether or not a call start operation has been executed by the user. In the case of YES here, the device-side control unit 52 executes the processes shown in S100 to S104. If NO in S98, the process proceeds to S108 in FIG.

  In S <b> 100, the device-side control unit 52 transmits a call start instruction to the telephone body 20. The main body control unit 22 determines YES in S44 of FIG. 6 and executes the processes of S46 to S54. The calling device 50 receives the call request notification stop instruction transmitted from the telephone body 20 in S48 of FIG. 6 (S102). Next, the device-side control unit 52 executes a call request notification stop process (S104). With this process, the device-side control unit 52 stops the call request notification. Thereafter, a call-enabled state is established between the calling device 50 and the calling device (for example, the calling device 150) of the INVITE transmission source (S54 in FIG. 6).

  The device-side control unit 52 executes a call request notification stop process to stop the call request notification when the call device 50 is executing a call request notification, and the call device 50 issues an interrupt call request notification. When it is running, the interrupt call request notification is stopped. That is, the call request notification stop instruction is an instruction for stopping both the call request notification and the interrupt call request notification.

  In S108, the device-side control unit 52 determines whether or not a ringing refusal operation has been performed by the user. The user can execute the ring rejection operation by operating the ring rejection key while the call request notification or the interrupt call request notification is being executed on his / her call device. That is, if the user does not want to respond to the call request when the call request notification is executed (or cannot respond), the ringing refusal operation can be executed. Alternatively, when the interrupt call request notification is executed during a call, if the user does not want to respond (or cannot respond) to the call request received during the call, the ringing rejection operation can be executed. In the case where S108 is YES, the device-side control unit 52 executes the processes shown in S110 to S114. If NO in S108, the process proceeds to S116.

  In S <b> 110, the device side control unit 52 transmits a ringing refusal instruction to the telephone body 20. When the process of S110 is executed, the main body control unit 22 determines YES in S56 of FIG. 6, and executes the processes of S58 and S60. The call device 50 receives the call request notification stop instruction transmitted from the telephone body 20 in S58 of FIG. 6 (S112). The device-side control unit 52 executes a call request notification stop process (S114). When the call device 50 is executing the call request notification, the device-side control unit 52 stops the call request notification when the call device 50 is executing the call request notification, and the call device 50 executes the interrupt call request notification. If it is, the interrupt call request notification is stopped.

  In S116, the device-side control unit 52 determines whether a call end operation has been executed by the user. In the case of YES here, the device-side control unit 52 executes the processes shown in S118 to S124.

  In S <b> 118, the device-side control unit 52 transmits a call end instruction to the telephone body 20. When the process of S118 is executed, the main body control unit 22 determines YES in S62 of FIG. 7, and executes the processes of S64 to S70. Next, the call device 50 receives the call request notification stop instruction transmitted from the telephone body 20 in S64 of FIG. 7 (S120). The device-side control unit 52 determines whether or not an interrupt call request notification is being executed (S122). In the case of YES here, the device-side control unit 52 executes a call request notification stop process (S124).

  As described above, when BYE is received by the telephone main body 20 in S72 of FIG. 7, the main body side control unit 22 transmits a call request notification stop instruction to the telephone device 50 (S64 of FIG. 7). In this case, the device-side control unit 52 executes the processes of S120 to S124 described above.

  The contents of the flowchart have been described above. Note that a method for the user to operate the operation unit 56 of the call device 50 in each process is not particularly limited. For example, the call start operation and the call end operation may be the same operation or different operations. Alternatively, the call start operation and the ringing rejection operation may be the same operation or different operations.

  In the telephone network system 2 of the present embodiment, it is possible to cause a call device having a busy status to execute an interrupt call request notification. As a result, it is possible to notify the user who is on the call that the call request has been received. In addition, when a call device with a standby status does not respond to a call request, a call device having a call status can execute an interrupt call request notification. This can reduce the chance that the user of the calling device having the busy status is disturbed by the interrupt call request notification.

  Further, the interrupt call request notification can be stopped when the user operates the call device while the interrupt call request notification is being executed. As a result, the user can talk without being interrupted by the interrupt call request notification. Also, once interrupt call request notification is stopped during a call, the interrupt call request notification is not executed during the call. The user can prohibit the interrupted call request notification from being executed many times during one call and interrupting the call each time.

  Specific examples of the present invention have been described in detail above, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. The modifications of the above embodiment are listed below.

(1) In the above embodiment, telephone communication is performed using the Internet 104. However, the extension network 10 may perform communication using a general public network (PSTN or ISDN). The extension network 10 may perform communication using both the Internet 104 and the general public network.

(2) The main body side control unit 22 of the telephone main body 20 transmits 486 Busy Here in S40 of FIG. However, voice mail data for voice recording may be stored in the storage area 32 and the voice data for voice recording stored in the storage area 32 may be transmitted to the telephone main body 120 before transmitting 486 Busy Here. You may transmit 486 Busy Here to the telephone main body 120, after transmitting voice mail data for answering machines and predetermined time passes.

(3) In the above-described embodiment, when a ringing rejection operation is performed during the interrupt call request notification, the interrupt call request notification can be stopped. Furthermore, even if another call request is received during the call after the ringing rejection operation is performed, the interrupt call request notification is not executed. However, the main body-side control unit 22 receives an interrupt call request notification (second notification) in a form different from the interrupt call request notification that is normally executed (referred to as a first interrupt call request notification) when the other call request is received. May be executed). The second interrupt call request notification is preferably in a form that does not disturb the call. For example, a sound smaller than the first interrupt call request notification may be generated by the second interrupt call request notification. Alternatively, the first interrupt call request notification may be a notification by sound, while the second interrupt call request notification may be a notification by blinking light. According to this configuration, the user can know that there was an incoming call during a call without hindering the call even after the ringing refusal operation has been performed once.

(4) In the above embodiment, when a call end operation is executed, the call available state is disconnected. However, it may be possible to execute the first and second call end operations. When the first call end operation is executed, the call ready state may be disconnected, and when the second call end operation is executed, the call ready state may be put on hold. According to this configuration, the first call termination operation is performed when a callable state is established with one of the other parties and the callable state with the other party is on hold. When it is executed, the state where communication with the one other party is made is disconnected, and a state where communication is possible with the other party is established. In this case, it is not possible to re-establish a call available state with one of the other parties. On the other hand, a second call termination operation is executed when a call-enabled state is established with one call partner and the call-ready state with the other call partner is on hold. As a result, the state where communication with the one other party is held is put on hold, and a state where communication is possible with the other party is established. In this case, it is possible to re-establish a call-capable state with the one other party by disconnecting the call-permitted state with the other party. The other party can be switched over and over again to one of the other party and the other party.

  The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

1 shows an example of the configuration of a telephone network system. An example of a structure of a telephone main body is shown. An example of the storage content of the call device information storage area is shown. An example of a structure of a call device is shown. The flowchart of a telephone main body main process is shown. FIG. 6 is a flowchart continued from FIG. 5. FIG. FIG. 7 is a flowchart continued from FIG. 6. FIG. 6 shows a flowchart of an INVITE reception process. The flowchart of a telephone call device main process is shown. FIG. 10 is a flowchart continued from FIG. 9. FIG.

Explanation of symbols

2: Telephone network system 10, 110: Extension network 20: Telephone main body 22: Main body side control unit 24: Wireless communication interface 26: Network interface 28: Storage unit 30: Call device information storage area 40: Operation unit 42: Display unit 50 , 70, 80: Call device 104: Internet 106: SIP server 312: Status 314: Ring rejection flag

Claims (5)

Status acquisition means for acquiring the status of each of a plurality of calling devices;
A call request receiving means for receiving a call request;
A call request notification means for causing a call device having a waiting status to execute a call request notification on the condition that the call request is received by the call request receiving means;
Call request notification stop means for stopping the call request notification on condition that the first operation has been executed in the call device that is executing the call request notification;
An interrupt call that causes the call device to execute an interrupt call request notification on condition that the first operation is performed in all the call devices that are executing the call request notification and there is a call device having a busy status. A telephone device comprising: request notification means; Call request transmission means for transmitting a call request on the condition that a call preparation operation has been executed in any of the call devices,
The interrupt call request notifying means is configured to receive a call request by the call request receiving means while a busy status is established as a result of executing the call preparation operation in the call device on which the first operation has been executed. The telephone device according to claim 1, wherein the telephone device is prohibited from executing an interrupt call request notification. Constructed in the call device when the second operation is executed on the condition that the second operation is executed in the call device while the call device having the busy status is executing the interrupt call request notification The telephone device according to claim 1, further comprising an interrupt call request notification stop unit that stops the interrupt call request notification while maintaining a call enabled state. Negative response transmitting means for transmitting a negative response to the call request received by the call request receiving means on condition that the second operation has been executed in all the call devices that are executing the interrupt call request notification. The telephone device according to claim 3, further comprising: The call request notification means is configured to execute the second operation in the first call device that is executing the interrupt call request notification, and the first call device while the second call device is executing the interrupt call request notification. 5. The telephone device according to claim 3, wherein the first call device is caused to execute a call request notification on condition that the call ready state constructed in step 1 is disconnected.

Images